[lugip] Problems with Bluetooth
sakuramboo
sakuramboo at gmail.com
Tue Oct 23 23:01:38 EDT 2007
i have been trying for the life of me to get my desktop to sync up to
any of my cell phones via bluetooth, but nothing seems to work. i have
tried it with three different model cell phones and all produce the same
result. the phones do, however, work fine with other devices. i am
positive that its not the phone at fault here.
this is what happens, i enable bluetooth on my phone, then i plug the
bluetooth dongle to my desktop. it gets detected and properly assigned a
device driver. the modules are all loaded and functioning properly. i
launch the gnome-phone-manager and it tries to connect. i type i the pin
number on the phone and it fails.
these are all the relative outputs...
[sakuramboo@~]$ /usr/sbin/hciconfig -a
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 678:8 SCO MTU: 48:10
UP RUNNING PSCAN
RX bytes:4757 acl:31 sco:0 events:120 errors:0
TX bytes:1045 acl:36 sco:0 commands:50 errors:0
Features: 0xbf 0xfe 0x8d 0x78 0x08 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'ISSCBTA'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 1.2 (0x2) HCI Rev: 0x1fe LMP Ver: 1.2 (0x2) LMP Subver:
0x1fe
Manufacturer: Integrated System Solution Corp. (57)
[sakuramboo@~]$ hcitool scan
Scanning ...
00:12:D2:0C:77:1D The phone
[root at localhost bluetooth]# hcitool info 00:12:D2:0C:77:1D
Requesting information ...
BD Address: 00:12:D2:0C:77:1D
Device Name: The phone
LMP Version: 1.2 (0x2) LMP Subversion: 0xdb0
Manufacturer: Texas Instruments Inc. (13)
Features: 0xbf 0xee 0x0f 0x00 0x18 0x18 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <sniff mode> <RSSI>
<channel quality> <SCO link> <HV3 packets> <u-law log>
<A-law log> <CVSD> <paging scheme> <power control>
<transparent SCO> <AFH cap. slave> <AFH class. slave>
<AFH cap. master> <AFH class. master>
[root at localhost sakuramboo]# gnokii --identify
GNOKII Version 0.6.14
LOG: debug mask is 0x1
phone instance config:
model: 6510
port_device: 00:12:D2:0C:77:1D
connection_type: 5
init_length: 0
serial_baudrate: 19200
serial_write_usleep: -1
hardware_handshake: 0
require_dcd: 0
smsc_timeout: 100
connect_script:
disconnect_script:
rfcomm_cn: 1
sm_retry: off
Connecting
Serial device: opening device 00:12:D2:0C:77:1D
Can't connect: Connection refused
Couldn't open PHONET device: Connection refused
Error in link initialisation: 1
Telephone interface init failed: Command failed.
Quitting.
Command failed.
Serial device: closing device
that was one of the parts where it fails.
now, i think what the problem is, is that the desktop doesnt have a pin
to check against the one inputted into the phone. the thing is,
/etc/bluetooth/hcid.conf has the entry for the pin number. i have tried
it with and without the quotes around it, same result. i have researched
this and a lot of places say to use a pin-helper, unfortunately, i have
looked and it seems like the Bluez bluetooth stack devs stopped
supporting the pin-helper, wanting to just type the pin into hcid.conf
instead. plus, all th docs i found online are from 3+ years ago. so, i
took a guess and added the line to the hcid.conf file...
pin_helper /etc/bluetooth/pin
and in that file, it has...
00:12:D2:0C:77:1D 1234 "The phone"
i then read another article that said to point the pin_helper to a bash
script...
[sakuramboo@/etc/bluetooth]$ cat feed-bin.sh
#!/bin/sh
echo "PIN:1234"
alas, the same results everytime.
i have looked through the fedora repos for pin helpers and found one,
but it wont install because its depreciated (wanting to just use the
config files instead).
now, whats even weirder still is, i can detect my desktop from my phone.
it comes up on my phone as "The machine" and i can even connect to it. i
havent tried sending anything from my phone to my desktop, but, when i
try to connect to my phone again, while connected vice-versa, it just
continues to try to connect, never actually making the connection.
any help would be greatly loved. :)
More information about the Lugip
mailing list