You are not logged in.
Pages: 1
I cannot get my mobile phone to talk to my laptop and vice versa. hcitool scan does not return anything.
dmesg|grep Blue
[ 3.590455] Bluetooth: Core ver 2.16
[ 3.590539] Bluetooth: HCI device and connection manager initialized
[ 3.590548] Bluetooth: HCI socket layer initialized
[ 3.590554] Bluetooth: L2CAP socket layer initialized
[ 3.590573] Bluetooth: SCO socket layer initialized
[ 3.597402] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 53.888121] Bluetooth: RFCOMM TTY layer initialized
[ 53.888140] Bluetooth: RFCOMM socket layer initialized
[ 53.888147] Bluetooth: RFCOMM ver 1.11
[ 54.989298] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 55.990231] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 1C:4B:D6:15:B1:1E ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1641 acl:0 sco:0 events:64 errors:0
TX bytes:750 acl:0 sco:0 commands:58 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'myhost-0'
Class: 0x400100
Service Classes: Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.1 (0x4) Revision: 0x149c
LMP Version: 2.1 (0x4) Subversion: 0x149c
Manufacturer: Cambridge Silicon Radio (10)
Offline
run
$ rfkill list
if some info like
Soft blocked: yes
Hard blocked: no
appears, run
# rfkill unblock 0 #0 corresponds to your bluetooth device number
Now, stoping the bluetooth daemon run it as a foreground job for debug infos:
# /etc/rc.d/bluetooth stop
# bluetoothd -n -d
then try
# hciconfig hci0 up
$ hcitool dev #should give your bdevice addr
$ hcitool scan
I myself am a bit lost with getting the bluetooth thing working, but managed it to .
If all of the above works, you can install blueman which is a frontend for bluetooth operations.
Offline
@debdj
rfkill output:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Yet, no success. Running bluetoothd in the foreground does not seem to reveal anything significant. hcitool scan still returns nothing.
Also, my phone will see other mobile phones but not the laptop.
Last edited by marxav (2012-02-16 22:04:16)
Offline
Do you have the /var/run/dbus directory?
If not, if you have dbus in the deamon listing in your /etc/rc.conf (generally at the end of the file) or in ~/.Xinitrc , stop and start it with
# /etc/rc.d/dbus stop
# /etc/rc.d/dbus start
make sure bluetooth deamon is already stopped.
Then start up the bluetooth deamon again.Now note what 'hcitool dev' gives. Often there persists some problems when dbus is started after bluetooth damon.You could also see if something can be modified in /etc/bluetooth/main.conf which is the general configuration file for the blue daemon.
The arch wiki has a bunch of info regarding bluetooth setup : https://wiki.archlinux.org/index.php/Bluetooth
my phone will see other mobile phones but not the laptop.
as for that, your previous post already shows that you have both piscan and iscan enabled. I dont know..
Last edited by debdj (2012-02-17 18:50:00)
Offline
Pages: 1