GNOME Bugzilla – Bug 560605
Acoustic Research ARWH1 can't pair
Last modified: 2010-01-02 13:56:05 UTC
Similar to : http://bugzilla.gnome.org/show_bug.cgi?id=560315 Because of the new fixed random+hardcoded pin, this device cannot be paired anymore : 1)adilson@cartman:~$ hcitool scan Scanning ... XX:XX:XX:XX:XX:XX ARWH1 2)adilson@cartman:~$ hcitool inq XX:XX:XX:XX:XX:XX Inquiring ... XX:XX:XX:XX:XX:XX clock offset: 0x3e14 class: 0x08010c XX:XX:XX:XX:XX:XX clock offset: 0x4f55 class: 0x240404 3)default pin Will confirm it as soon as the device owners does it
(In reply to comment #0) <snip> > 1)adilson@cartman:~$ hcitool scan > Scanning ... > XX:XX:XX:XX:XX:XX ARWH1 > > 2)adilson@cartman:~$ hcitool inq XX:XX:XX:XX:XX:XX > Inquiring ... > XX:XX:XX:XX:XX:XX clock offset: 0x3e14 class: 0x08010c > XX:XX:XX:XX:XX:XX clock offset: 0x4f55 class: 0x240404 And which one of those two is the same as the device above? I also need at least the first three hex numbers for the device (the OUI number that identifies the vendor).
Hello. There you have it. Both lines are from the same device. It's a headset which has some sort of small joystick control in it. I believe that's why the 2 lines. adilson@cartman:~$ hcitool scan Scanning ... 00:18:16:XX:XX:XX ARWH1 adilson@cartman:~$ hcitool inq 00:18:16:35:80:93 Inquiring ... 00:18:16:XX:XX:XX clock offset: 0x4c37 class: 0x240404 00:06:6E:XX:XX:XX clock offset: 0x212e class: 0x08010c
infos have been provided, removing NEEDINFO
(In reply to comment #2) > Hello. There you have it. > Both lines are from the same device. It's a headset which has some sort of > small joystick control in it. I believe that's why the 2 lines. Unlikely. Bluetooth has other ways to show separate services and devices, and it's your computer (your laptop actually) showing up on the second line. > adilson@cartman:~$ hcitool scan > Scanning ... > 00:18:16:XX:XX:XX ARWH1 > > adilson@cartman:~$ hcitool inq 00:18:16:35:80:93 > Inquiring ... > 00:18:16:XX:XX:XX clock offset: 0x4c37 class: 0x240404 > 00:06:6E:XX:XX:XX clock offset: 0x212e class: 0x08010c (In reply to comment #3) > infos have been provided, removing NEEDINFO The only reason this device wouldn't pair properly would be if the PIN code wasn't 0000. So what is it?
You are correct. The second line is actually a webpad I had aroud that I thought was turned off. First like is the correct one. The PIN code is 0000 and the bluetooth manager asks for a random PIN that I cannot enter on the device of course thus, cannot pair it.
I mean, the first *line* is the correct one.
Which icon do you see next to the device in the wizard? Does it change if you wait?
It shows a sort of circuit board.
(In reply to comment #8) > It shows a sort of circuit board. That's supposed to be a sound-card looking thing. Then the wizard already knows you have a headset, and will use 0000 as the pincode: 73 /* Most headsets are using 0000 as pincode */ 74 if (target_type == BLUETOOTH_TYPE_HEADSET || 75 target_type == BLUETOOTH_TYPE_HEADPHONE) 76 pincode = "0000"; You might want to test with this patch though: http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=commitdiff;h=ee257197c40978ea2699c564f7e996216f2a68b9 If you had selected the device before the right icon appeared the wizard wouldn't have known about the type of device.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!