Rodolfo Medina wrote: >>>> I just bought a bluetooth adapter and plugged it in the PC, which can see >>>> it: >>>> >>>> $ lsusb >>>> Bus 003 Device 001: ID 0000:0000 >>>> Bus 002 Device 001: ID 0000:0000 >>>> Bus 002 Device 006: ID 1131:1001 Integrated System Solution Corp. >>>> Bus 002 Device 005: ID 0421:0410 Nokia Mobile Phones 6630 Imaging >>>> Smartphone >>>> Bus 001 Device 001: ID 0000:0000 >>>> >>>> But my Nokia 6630 doesn't see the PC's bluetooth device: it searches for >>>> bluetooth devices and says: noone found. What am I missing? >>>>
Dal <[EMAIL PROTECTED]> writes: >>> maybe your computer is invisible, check >>> /var/lib/bluetooth/<mac_of_your_bt_adapter>/config >>> >>> and there should be on the first line something like >>> mode connectable (or something like that, it means it's not discoverable, >>> just connectable) >>> >>> You can set it discoverable using this: >>> >>> $ dbus-send --system --type=method_call --print-reply --dest=org.bluez >>> /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable >>> but this will work until timeout, so you need to run this >>> $ dbus-send --system --type=method_call --print-reply --dest=org.bluez >>> /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:0 >>> You set discoverable timeout to 0. Rodolfo: >> Thanks indeed. >> Yes, the file /var/lib/bluetooth/00:11:67:64:CB:18/config contains the line >> >> mode discoverable >> >> ; since I gave the second command you suggest, a second line appeared: >> >> discovto 0 >> >> , but that command seems to produce no result. Instead, the first command >> you >> suggest seems to work, but only for a limited time. Dal: > actually the second command should set up the timeout to 0, so no limited > time, when I run it it produces: > dbus-send --system --type=method_call --print-reply --dest=org.bluez > /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:0 > method return sender=:1.4 -> dest=:1.11 reply_serial=2 > > and in that config file is > mode discoverable > discovto 0 > > And it works just fine with my SE. Anyway I'm not sure, but I had some > problems with N6230i and bluetooth, that my laptop it didn't see even if it > was discoverable. Just after pairing it saw that phone. > > Try to run hcid by hand and don't let him to fork. > hcid -n -f /etc/bluetooth/hcid.conf and watch what it prints, maybe it'll > help. > (you have to kill the hcid daemon automatically started by > /etc/init.d/bluetooth script. > > > Have you possibility to try bluetooth with other BT device or non-Nokia mobile > phone? No, the only BT device I have is my Nokia 6630. But it's strange, because the second command you suggest gives the following output: $ dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:0 method return sender=:1.0 -> dest=:1.3 and nothing happens, whereas the first one: $ dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable method return sender=:1.0 -> dest=:1.4 works, i.e. the PC is recognized by the phone after pairing them, but - according to my last test - only for a limited time. the hcid command is `not found' by my system. Cheers, Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
