kbluepin not showing up when trying to pair phone to pc

johngreenwood · 02-14-2007, 02:29 AM

Hi everyone, I have been trying to get bluetooth on my Slackware 11 system for a while now. I think I am finally getting somewhere but now I'm stuck.
Here is what I am using:
kdebluetooth
kmobiletools
kbluepin
sdpd

I have edited the /etc/bluetooth/hcid.conf file so the pin helper is kbluepin.

Everything seems fine, I can see the services available on my phone in Konqueror, can send files to the phone, but not recieve them, and can detect the computer by doing a scan with the phone. Whenever I try to pair the two devices, the kdebluetooth system tray icon flashes like mad but no pin dialog appears. I have searched for quite some time on this, but haven't found anything.

Hope someone can help.

John

johngreenwood · 02-15-2007, 02:03 PM

Anyone? No-one? Surely there must be someone with some experience of this.

johngreenwood · 02-16-2007, 02:02 AM

I have been looking through syslog, and this is what I found:

Code:

Feb 16 07:44:14 greenwood hcid[12900]: Can't open config file /C/bluezbuild//etc/bluetooth/hcid.conf
Feb 16 07:44:14 greenwood hcid[12900]: Config load failed
Feb 16 07:44:14 greenwood hcid[12900]: Can't open system message bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Feb 16 07:44:14 greenwood hcid[12900]: Unable to get on D-Bus
Feb 16 07:45:13 greenwood hcid[12909]: Unknown option 'pin_helper' line 18
Feb 16 07:45:13 greenwood hcid[12909]: syntax error line 18
Feb 16 07:45:13 greenwood hcid[12909]: Can't open system message bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Feb 16 07:45:13 greenwood hcid[12909]: Unable to get on D-Bus

Unfortuntely, I have no idea what it means, it says pin_helper is an unknown option, yet this is what the documentation says to use.

I can't understand it, somebody please help.

johngreenwood · 02-17-2007, 05:18 PM

I've finally done it, and for anyone else with the same problem, here's how (although this may not work for you!)
I am using Slackware-current

I am assuming you have all relevant packages installed.

This stuff you can put in a script, but I prefer to do it manually until I know whats going on.

as root (# is prompt, don't enter it!):

Code:

# sdpd

make sure dbus-daemon isn't running and remove the pid file:

Code:

# rm /var/run/dbus/pid

Code:

# /etc/rc.d/rc.bluetooth start

/etc/rc.d/rc.bluetooth start should start hcid and bring up hci0, at least, that's what happens to mine.

if not, do:

Code:

# hcid
# hciconfig hci0 up

The phone doesn't detect the computer if either pscan or iscan is not enabled, I don't know which, so check it with:

Code:

# hciconfig

The rsulting output will be something like:

Code:

hci0:   Type: USB
        BD Address: 00:02:72:B0:00:26 ACL MTU: 120:20 SCO MTU: 64:0
        UP RUNNING PSCAN
        RX bytes:1146912 acl:7199 sco:0 events:3892 errors:1
        TX bytes:146928 acl:3799 sco:0 commands:332 errors:0

This shows the device is a USB device, the BD address, and shows the device is up and running, with pscan enabled. As you can see there is no iscan, and my phone won't detect it, so do:

Code:

# hciconfig hci0 piscan

Check hciconfig again and both should be enabled.
Try to detect your phone with:

Code:

# hcitool scan

If your phone is detected, you have bluetooth (obviously).

You wil need to set a PIN for incoming connections, this is set in /etc/bluetooth/hcid.conf
The "pin_helper" option is no longer used, so comment that out to prevent the useless message in syslog as in the above post.
Look for this line

Code:

passkey "1234";

and change it to something else, or keep it, it's up to you.

I had an error message about hcid.conf not being in /C/bluezbuild//etc/bluetooth/hcid.conf, so I created the directories and copied hid.conf to it. I'm not sure if this is necessary, but you can use the -f option with hcid to specify a config file.

Start kbluetoothd, get your phones bdaddress with

Code:

# hcitool scan

again, and open Konquerer. In the address bar type

Code:

sdp://[00:00:00:00:00:00]

where the zeros are the bdaddress of your phone. This should bring up a list of services available for your phone, like ObexFTP, Dial-up Networking etc. Look for a serial port, I used COM1, try to open it. In the dialog box which appears asking if you want to save the file, look for a number indicating the channel, COM1 on my phone is channel 3.

To use kmobile tools, you need to bind this serial port to a device node like this.

Code:

# mknod /dev/rfcomm0 c 216 4
# rfcomm bind 0 00:00:00:00:00 3

the first 0 is /dev/rfcomm0
00:00:00:00:00:00 is your phones bdaddress
and 3 is the channel of your phones serial port.
Adjust accordingly.

Now you should be able to add your phone to the devices on kmobiletools and use it. You can send/recieve files also.

You might want to change the settings on your phone and kbluetoothd, so that your computer and phone can talk to each other without askng each time, or you might not.

But like I said at the beginning, this might not work for you.

I hope this helps somebody,

John