SOLVED: Re: Bluetooth problem
I guess I should have done this first, but I searched the Debian list archives and came up with the following: https://lists.debian.org/debian-user/2016/03/msg00164.html Upon following this solution, my problem was also solved. This leaves the question: Should this be reported as a bug (probably against the gdm3 package) in order to have the client.conf file added to the package as a default? On 08/29/2016 09:08 AM, Michael Milliman wrote: Additional information, I grep'ed the device address in all log files and got the following for one instance of a connection attempt: kern.log:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input: 30:21:48:DD:53:44 as /devices/virtual/input/input26 messages:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input: 30:21:48:DD:53:44 as /devices/virtual/input/input26 messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input driver 'evdev' for '30:21:48:DD:53:44' messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: always reports core events messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Found keys messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) syslog:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input: 30:21:48:DD:53:44 as /devices/virtual/input/input26 syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input driver 'evdev' for '30:21:48:DD:53:44' syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: always reports core events syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Found keys syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input driver 'evdev' for '30:21:48:DD:53:44' user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: always reports core events user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Found keys user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) Xorg.0.log:[ 2898.563] (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) Xorg.0.log:[ 2898.563] (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" Xorg.0.log:[ 2898.563] (II) Using input driver 'evdev' for '30:21:48:DD:53:44' Xorg.0.log:[ 2898.563] (**) 30:21:48:DD:53:44: always reports core events Xorg.0.log:[ 2898.563] (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" Xorg.0.log:[ 2898.563] (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 Xorg.0.log:[ 2898.563] (--) evdev: 30:21:48:DD:53:44: Found keys Xorg.0.log:[ 2898.563] (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard Xorg.0.log:[ 2898.564] (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id
Re: Bluetooth problem
Talk about flakey software! :-( On Mon, 29 Aug 2016, Michael Milliman wrote: Date: Mon, 29 Aug 2016 09:48:01 From: Michael Milliman <michael.e.milli...@gmail.com> To: debian-user@lists.debian.org Subject: Bluetooth problem Resent-Date: Mon, 29 Aug 2016 13:48:31 + (UTC) Resent-From: debian-user@lists.debian.org I am running Debian 8.5 on a Toshiba Satellite L755D-S5106 laptop and having the following problem: When trying to connect my bluetooth speakers to the machine, I get all indications that the device is paired and connected. The speaker gives its indication that it is paired and connected as well. However, the speaker never shows up in PulseAudio. Upon further investigation, I find in the Xorg.log.o file that it has been configured as a keyboard, not as a speaker (which would explain why it didn't show up in PulseAudio). The speaker is most definitely not a keyboard!! Any ideas as to how to solve this problem? It is worth noting that this does not happen every time. On occasion, everything works just fine. However, the vast majority of the time, I cannot get it to work properly. Will be glad to post additional information as necessary. --
Re: Bluetooth problem
Additional information, I grep'ed the device address in all log files and got the following for one instance of a connection attempt: kern.log:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input: 30:21:48:DD:53:44 as /devices/virtual/input/input26 messages:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input: 30:21:48:DD:53:44 as /devices/virtual/input/input26 messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input driver 'evdev' for '30:21:48:DD:53:44' messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: always reports core events messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Found keys messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard messages:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) syslog:Aug 29 08:39:38 lap-02 kernel: [ 2899.476316] input: 30:21:48:DD:53:44 as /devices/virtual/input/input26 syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input driver 'evdev' for '30:21:48:DD:53:44' syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: always reports core events syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Found keys syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard syslog:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) Using input driver 'evdev' for '30:21:48:DD:53:44' user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) 30:21:48:DD:53:44: always reports core events user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (--) evdev: 30:21:48:DD:53:44: Found keys user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard user.log:Aug 29 08:39:38 lap-02 gdm-Xorg-:0[617]: (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) Xorg.0.log:[ 2898.563] (II) config/udev: Adding input device 30:21:48:DD:53:44 (/dev/input/event13) Xorg.0.log:[ 2898.563] (**) 30:21:48:DD:53:44: Applying InputClass "evdev keyboard catchall" Xorg.0.log:[ 2898.563] (II) Using input driver 'evdev' for '30:21:48:DD:53:44' Xorg.0.log:[ 2898.563] (**) 30:21:48:DD:53:44: always reports core events Xorg.0.log:[ 2898.563] (**) evdev: 30:21:48:DD:53:44: Device: "/dev/input/event13" Xorg.0.log:[ 2898.563] (--) evdev: 30:21:48:DD:53:44: Vendor 0 Product 0 Xorg.0.log:[ 2898.563] (--) evdev: 30:21:48:DD:53:44: Found keys Xorg.0.log:[ 2898.563] (II) evdev: 30:21:48:DD:53:44: Configuring as keyboard Xorg.0.log:[ 2898.564] (II) XINPUT: Adding extended input device "30:21:48:DD:53:44" (type: KEYBOARD, id 13) Clearly, the majority of this is redundant, but I included it for the sake of completeness. On 08/29/2016 08:48 AM, Michael Milliman wrote: I am running Debian 8.5 on a Toshiba Satellite L755D-S5106 laptop and having the following problem: When trying to connect my bluetooth speakers to the machine, I get all indications that the device is paired and connected. The speaker gives its indication that it is paired and connected as well. However, the speaker never shows up in PulseAudio. Upon further investigation, I find in the
Bluetooth problem
I am running Debian 8.5 on a Toshiba Satellite L755D-S5106 laptop and having the following problem: When trying to connect my bluetooth speakers to the machine, I get all indications that the device is paired and connected. The speaker gives its indication that it is paired and connected as well. However, the speaker never shows up in PulseAudio. Upon further investigation, I find in the Xorg.log.o file that it has been configured as a keyboard, not as a speaker (which would explain why it didn't show up in PulseAudio). The speaker is most definitely not a keyboard!! Any ideas as to how to solve this problem? It is worth noting that this does not happen every time. On occasion, everything works just fine. However, the vast majority of the time, I cannot get it to work properly. Will be glad to post additional information as necessary. -- 73's Mike, WB5VQX
Re: bluetooth problem
Good look :D it had resolved my problem. Thanks so much -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/04490e28855b88f049c2622ac631df8f.squir...@newmail.bilkent.edu.tr
bluetooth problem
Hi i have problem with bluetooth blueoothd is working. applet in gnome3 is presented. It shows that bluetooth is on but i can not switch on visibility. blutooth setting dialog box can be opened but everything in this dialog is disabled What should i do? bluetooth device is presented in my host # hcitool scan Device is not available: No such device thanks in advance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2d9c7f3733b1302598bb706131f0fba0.squir...@newmail.bilkent.edu.tr
Re: bluetooth problem
- Original Message - From: andrey.ry...@bilkent.edu.tr Sent: 05/06/13 05:14 PM To: debian-user@lists.debian.org Subject: bluetooth problem Hi i have problem with bluetooth blueoothd is working. applet in gnome3 is presented. It shows that bluetooth is on but i can not switch on visibility. blutooth setting dialog box can be opened but everything in this dialog is disabled What should i do? bluetooth device is presented in my host # hcitool scan Device is not available: No such device thanks in advance Hi, I experienced that problem too, I solved installing the Atheros Firmware from the non-free repository, maybe this is your problem, search for the firmware of your hardware: http://packages.debian.org/sid/firmware-atheros Good look :D -- Gean Michel Ceretta - geancere...@linuxmail.org - geancere...@gmail.com - +55 046 9111 8829
[solved] Re: A bluetooth problem
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 : Bus 002 Device 001: ID : 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 : 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) [...] try to run dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:0 as second command, run dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable first and that command before sets discoverable time to 0 - never timeouts, so never goes out of discoverable mode. [...] Just put it to /etc/init.d/rc.local dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetMode string:discoverable dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/hci0 org.bluez.Adapter.SetDiscoverableTimeout uint32:0 [...] and now try to run that 2 commands in that order. [...] Now if it is again in connect mode, so you can't see it, check [...] /var/lib/bluetooth/mac_addres/config if there is mode discoverable or connect It seems to be solved now: I followed your indications and now it seems to be all right: the phone `sees'the PC and it can send and receive data from and to it. Your help was precious, thanks indeed! :) Cheers Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A bluetooth problem
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 : Bus 002 Device 001: ID : 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 : 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. 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. Any other hint? Thanks, cheers Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A bluetooth problem
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 : Bus 002 Device 001: ID : 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 : 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]
A bluetooth problem
I just bought a bluetooth adapter and plugged it in the PC, which can see it: $ lsusb Bus 003 Device 001: ID : Bus 002 Device 001: ID : 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 : 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? Thanks for any help Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A bluetooth problem
You need to install the software for that hardware, looki for into the repository for controllers bluetooth. aptitude search bluetooth. google is very usefull too. 2007/10/15, Rodolfo Medina [EMAIL PROTECTED]: I just bought a bluetooth adapter and plugged it in the PC, which can see it: $ lsusb Bus 003 Device 001: ID : Bus 002 Device 001: ID : 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 : 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? Thanks for any help Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- __ ? ___ / ¯ ¯ ¯\ | / ¯ ¯ ¯\ | |¯¯| \ / | \ |_| / \ / \___ / ¯¯¯ Linux user number 448596...
Re: A bluetooth problem
Hi Rodolfo, 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. I hope it will be useful. Dal. 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 : Bus 002 Device 001: ID : 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 : 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? Thanks for any help Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
