Author Topic: Invalid Bluetooth passkey (Read 3332 times)

hansolox1 · « **on:** May 06, 2004, 07:01:27 pm »

I am using an Zaurus 5500 with a Motorola Timeport phone. the Sharp Rom is 3.10 and the bluetooth adaptor is an Amicom bt2000 cf.

I have followed BlueZ\'s instructions.

When I choose to connect, I get prompted for a pass code on my phone. I typed in the passcode 1234 and my phone said invalid passcode. I then edited the givepin file in /etc/bluetooth and changed the passcode to 1 and then restarted bluetooth on the zaurus.

I attempted to reconnect and I entered 1 when prompted on my phone. It said invalid passcode again.

What am I doing wrong?

hansolox1 · « **Reply #1 on:** May 06, 2004, 08:02:04 pm »

It must be a problem with the Timeport. I tried it on a nokia 3650 and it connected ok. For some reason, when connected with the nokia, the network connection would stop working after a few minutes but it would still say that it is connected. Strange.

Is there some kind of trick to getting the Timeport to work properly?

Why is the nokia initially connecting and working properly but after a few minutes losing network connectivity? Any why is the zaurus still saying that it is connected?

Thanks for your help

tumnus · « **Reply #2 on:** May 06, 2004, 08:08:41 pm »

It could be a slight incompatibility between your phone and BT card. It sounds like you have got it right. You could try turning on syslog messages and see what the BlueZ drivers are saying when it tries to pair.

DrWowe · « **Reply #3 on:** May 06, 2004, 08:15:40 pm »

The Timeport (270c, right?) is a very old phone that only supports an older revision of the Bluetooth standard. It\'s not entirely surprising that there are some compatibility glitches.

hansolox1 · « **Reply #4 on:** May 06, 2004, 10:42:20 pm »

Yeah, I have had the Timeport for a few years. I can just use the nokia instead. I am still not sure why the nokia network connectivity stops funtioning after a few minutes even though the zaurus says that it is still connected.

How do I turn on syslog messages?

tumnus · « **Reply #5 on:** May 07, 2004, 11:43:44 am »

To turn on syslog messages, edit /etc/syslog.conf and make sure the line with *.info does not have a # at the very beginning. Save that and then run the command:

/etc/rc.d/init.d/syslog start

All this needs to be done as root. The syslog messages will appear in /var/log/messages. Also run the following command when you have finished debugging this, since /var/log/messages can get fairly big quite quickly:

/etc/rc.d/init.d/syslog stop

hansolox1 · « **Reply #6 on:** May 07, 2004, 08:39:43 pm »

Thanks for the help tumnus

News:

Author Topic: Invalid Bluetooth passkey (Read 3332 times)