bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Wan, Shuang]

Hi,

Just attempt to pair with a fixed pin device using bluetooth-wizard that doesn't have 0000 as its pin..I have a Gear4-Blackbox Mini (which is a headset/a2dp device) which has a fixed pin of 1234. When I try to pair the device it fails after attempting to use 0000, with no opportunity to enter any other pin.

It might be caused by the hard code in bluez-gnome, see bluez-gnome-1.8 source code wizard/main.c
static gboolean pincode_callback(DBusGMethodInvocation *context,
                                        DBusGProxy *device, gpointer user_data)
{
..............

        /* Most headsets are using 0000 as pincode */
        if (target_type == BLUETOOTH_TYPE_HEADSET ||
                                target_type == BLUETOOTH_TYPE_HEADPHONE)
                pincode = "0000";
...........
}

Anyone has come across this similar issue? Any suggestions?

Thanks!
Wan Shuang

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[John Frankish]

-----Original Message-----
From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of Wan, Shuang
Sent: 13 July, 2009 05:40
To: linux-bluetooth@vger.kernel.org
Subject: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

Hi,

Just attempt to pair with a fixed pin device using bluetooth-wizard that doesn't have 0000 as its pin..I have a Gear4-Blackbox Mini (which is a headset/a2dp device) which has a fixed pin of 1234. When I try to pair the device it fails after attempting to use 0000, with no opportunity to enter any other pin.

It might be caused by the hard code in bluez-gnome, see bluez-gnome-1.8 source code wizard/main.c
static gboolean pincode_callback(DBusGMethodInvocation *context,
                                        DBusGProxy *device, gpointer user_data)
{
..............

        /* Most headsets are using 0000 as pincode */
        if (target_type == BLUETOOTH_TYPE_HEADSET ||
                                target_type == BLUETOOTH_TYPE_HEADPHONE)
                pincode = "0000";
...........
}

Anyone has come across this similar issue? Any suggestions?

Thanks!
Wan Shuang

--
Does it work with simple-agent?

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Wan, Shuang]

SGkgSm9obiwNCg0KCVRoYW5rcyBmb3IgeW91ciByZXBseS4gQWN0dWFsbHkgaXQncyBhIGJ1ZyBy
ZXBvcnRlZCB0byBtb2JsaW4yIGJ1Z3ppbGxhOg0KaHR0cDovL2J1Z3ppbGxhLm1vYmxpbi5vcmcv
c2hvd19idWcuY2dpP2lkPTM3MDQNClRvIHJlcHJvZHVjZSB0aGF0LCBJIG1vZGlmaWVkIHRoZSBz
b3VyY2UgdG8gYmVsbG93Og0KICAgICAgICAvKiBNb3N0IGhlYWRzZXRzIGFyZSB1c2luZyAwMDAw
IGFzIHBpbmNvZGUgKi8NCiAgICAgICAgaWYgKHRhcmdldF90eXBlID09IEJMVUVUT09USF9UWVBF
X0hFQURTRVQgfHwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgdGFyZ2V0X3R5cGUg
PT0gQkxVRVRPT1RIX1RZUEVfSEVBRFBIT05FKQ0KICAgICAgICAgICAgICAgIC8vcGluY29kZSA9
ICIwMDAwIjsNCiAgICAgICAgICAgICAgICBwaW5jb2RlID0gIjEyMzQiOw0KLi4uLi4NCkFuZCBw
YWlyaW5nIHdpdGggdGhlIGZpeGVkIHBpbiBjb2RlIDAwMDAgaGVhZHNldCwgZmluYWxseSBtZXQg
dGhlIHNpbWlsYXIgcHJvYmxlbS4NCg0KUmVnYXJkcw0KU2h1YW5nDQoNCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IGxpbnV4LWJsdWV0b290aC1vd25lckB2Z2VyLmtlcm5lbC5v
cmcgW21haWx0bzpsaW51eC1ibHVldG9vdGgtb3duZXJAdmdlci5rZXJuZWwub3JnXSBPbiBCZWhh
bGYgT2YgSm9obiBGcmFua2lzaA0KU2VudDogMjAwOcTqN9TCMTPI1SAxMjowMQ0KVG86IGxpbnV4
LWJsdWV0b290aEB2Z2VyLmtlcm5lbC5vcmcNClN1YmplY3Q6IFJFOiBibHVldG9vdGgtd2l6YXJk
IHBpbiBmaXhlZCBhdCAwMDAwIHdoaWNoIGlzIHVuYWJsZSB0byBwYWlyIHdpdGggaGVhZHNldCB3
aXRoIG90aGVyIHBpbnMNCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBs
aW51eC1ibHVldG9vdGgtb3duZXJAdmdlci5rZXJuZWwub3JnIFttYWlsdG86bGludXgtYmx1ZXRv
b3RoLW93bmVyQHZnZXIua2VybmVsLm9yZ10gT24gQmVoYWxmIE9mIFdhbiwgU2h1YW5nDQpTZW50
OiAxMyBKdWx5LCAyMDA5IDA1OjQwDQpUbzogbGludXgtYmx1ZXRvb3RoQHZnZXIua2VybmVsLm9y
Zw0KU3ViamVjdDogYmx1ZXRvb3RoLXdpemFyZCBwaW4gZml4ZWQgYXQgMDAwMCB3aGljaCBpcyB1
bmFibGUgdG8gcGFpciB3aXRoIGhlYWRzZXQgd2l0aCBvdGhlciBwaW5zDQoNCkhpLA0KDQpKdXN0
IGF0dGVtcHQgdG8gcGFpciB3aXRoIGEgZml4ZWQgcGluIGRldmljZSB1c2luZyBibHVldG9vdGgt
d2l6YXJkIHRoYXQgZG9lc24ndCBoYXZlIDAwMDAgYXMgaXRzIHBpbi4uSSBoYXZlIGEgR2VhcjQt
QmxhY2tib3ggTWluaSAod2hpY2ggaXMgYSBoZWFkc2V0L2EyZHAgZGV2aWNlKSB3aGljaCBoYXMg
YSBmaXhlZCBwaW4gb2YgMTIzNC4gV2hlbiBJIHRyeSB0byBwYWlyIHRoZSBkZXZpY2UgaXQgZmFp
bHMgYWZ0ZXIgYXR0ZW1wdGluZyB0byB1c2UgMDAwMCwgd2l0aCBubyBvcHBvcnR1bml0eSB0byBl
bnRlciBhbnkgb3RoZXIgcGluLg0KDQpJdCBtaWdodCBiZSBjYXVzZWQgYnkgdGhlIGhhcmQgY29k
ZSBpbiBibHVlei1nbm9tZSwgc2VlIGJsdWV6LWdub21lLTEuOCBzb3VyY2UgY29kZSB3aXphcmQv
bWFpbi5jDQpzdGF0aWMgZ2Jvb2xlYW4gcGluY29kZV9jYWxsYmFjayhEQnVzR01ldGhvZEludm9j
YXRpb24gKmNvbnRleHQsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
REJ1c0dQcm94eSAqZGV2aWNlLCBncG9pbnRlciB1c2VyX2RhdGEpDQp7DQouLi4uLi4uLi4uLi4u
Lg0KDQogICAgICAgIC8qIE1vc3QgaGVhZHNldHMgYXJlIHVzaW5nIDAwMDAgYXMgcGluY29kZSAq
Lw0KICAgICAgICBpZiAodGFyZ2V0X3R5cGUgPT0gQkxVRVRPT1RIX1RZUEVfSEVBRFNFVCB8fA0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB0YXJnZXRfdHlwZSA9PSBCTFVFVE9PVEhf
VFlQRV9IRUFEUEhPTkUpDQogICAgICAgICAgICAgICAgcGluY29kZSA9ICIwMDAwIjsNCi4uLi4u
Li4uLi4uDQp9DQoNCkFueW9uZSBoYXMgY29tZSBhY3Jvc3MgdGhpcyBzaW1pbGFyIGlzc3VlPyBB
bnkgc3VnZ2VzdGlvbnM/DQoNClRoYW5rcyENCldhbiBTaHVhbmcNCg0KLS0NCkRvZXMgaXQgd29y
ayB3aXRoIHNpbXBsZS1hZ2VudD8NCi0tDQpUbyB1bnN1YnNjcmliZSBmcm9tIHRoaXMgbGlzdDog
c2VuZCB0aGUgbGluZSAidW5zdWJzY3JpYmUgbGludXgtYmx1ZXRvb3RoIiBpbg0KdGhlIGJvZHkg
b2YgYSBtZXNzYWdlIHRvIG1ham9yZG9tb0B2Z2VyLmtlcm5lbC5vcmcNCk1vcmUgbWFqb3Jkb21v
IGluZm8gYXQgIGh0dHA6Ly92Z2VyLmtlcm5lbC5vcmcvbWFqb3Jkb21vLWluZm8uaHRtbA0K

Re: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Bastien Nocera]

On Mon, 2009-07-13 at 09:40 +0800, Wan, Shuang wrote:
> Hi,
> 
> Just attempt to pair with a fixed pin device using bluetooth-wizard
> that doesn't have 0000 as its pin..I have a Gear4-Blackbox Mini (which
> is a headset/a2dp device) which has a fixed pin of 1234. When I try to
> pair the device it fails after attempting to use 0000, with no
> opportunity to enter any other pin.

This is fixed in gnome-bluetooth.

Cheers

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Wan, Shuang]

R3JlYXQhIEkgd2lsbCB0cnkgdXNpbmcgYmx1ZXotZ25vbWUgZ2l0IHRyZWUuDQoNClRoYW5rcyEN
CldhbiBTaHVhbmcNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEJhc3RpZW4g
Tm9jZXJhIFttYWlsdG86aGFkZXNzQGhhZGVzcy5uZXRdIA0KU2VudDogMjAwOcTqN9TCMTPI1SAx
ODo0OA0KVG86IFdhbiwgU2h1YW5nDQpDYzogbGludXgtYmx1ZXRvb3RoQHZnZXIua2VybmVsLm9y
Zw0KU3ViamVjdDogUmU6IGJsdWV0b290aC13aXphcmQgcGluIGZpeGVkIGF0IDAwMDAgd2hpY2gg
aXMgdW5hYmxlIHRvIHBhaXIgd2l0aCBoZWFkc2V0IHdpdGggb3RoZXIgcGlucw0KDQpPbiBNb24s
IDIwMDktMDctMTMgYXQgMDk6NDAgKzA4MDAsIFdhbiwgU2h1YW5nIHdyb3RlOg0KPiBIaSwNCj4g
DQo+IEp1c3QgYXR0ZW1wdCB0byBwYWlyIHdpdGggYSBmaXhlZCBwaW4gZGV2aWNlIHVzaW5nIGJs
dWV0b290aC13aXphcmQNCj4gdGhhdCBkb2Vzbid0IGhhdmUgMDAwMCBhcyBpdHMgcGluLi5JIGhh
dmUgYSBHZWFyNC1CbGFja2JveCBNaW5pICh3aGljaA0KPiBpcyBhIGhlYWRzZXQvYTJkcCBkZXZp
Y2UpIHdoaWNoIGhhcyBhIGZpeGVkIHBpbiBvZiAxMjM0LiBXaGVuIEkgdHJ5IHRvDQo+IHBhaXIg
dGhlIGRldmljZSBpdCBmYWlscyBhZnRlciBhdHRlbXB0aW5nIHRvIHVzZSAwMDAwLCB3aXRoIG5v
DQo+IG9wcG9ydHVuaXR5IHRvIGVudGVyIGFueSBvdGhlciBwaW4uDQoNClRoaXMgaXMgZml4ZWQg
aW4gZ25vbWUtYmx1ZXRvb3RoLg0KDQpDaGVlcnMNCg0K

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Bastien Nocera]

On Mon, 2009-07-13 at 20:14 +0800, Wan, Shuang wrote:
> Great! I will try using bluez-gnome git tree.

Not bluez-gnome, gnome-bluetooth, as available in the GNOME git repo.

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Mario_Limonciello]

> Not bluez-gnome, gnome-bluetooth, as available in the GNOME git repo.

If there is not going to be any more development happening against the
bluez-gnome git tree, can it be formally killed with some indication
that people should work on development with gnome-bluetooth and/or
blueman then?

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Bastien Nocera]

On Mon, 2009-07-13 at 09:34 -0500, Mario_Limonciello@Dell.com wrote:
> > Not bluez-gnome, gnome-bluetooth, as available in the GNOME git repo.
> 
> If there is not going to be any more development happening against the
> bluez-gnome git tree, can it be formally killed with some indication
> that people should work on development with gnome-bluetooth and/or
> blueman then?

I believe Marcel wants to keep it to play around with the UI, for new
features.

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Marcel Holtmann]

Hi Bastien,

> > > Not bluez-gnome, gnome-bluetooth, as available in the GNOME git repo.
> > 
> > If there is not going to be any more development happening against the
> > bluez-gnome git tree, can it be formally killed with some indication
> > that people should work on development with gnome-bluetooth and/or
> > blueman then?
> 
> I believe Marcel wants to keep it to play around with the UI, for new
> features.

correct. And I am not killing a tree just for the fun of it. It is a
good history lesson and good to have the code around.

We can update www.bluez.org. I invite anybody to have an account there.

Regards

Marcel

RE: bluetooth-wizard pin fixed at 0000 which is unable to pair with headset with other pins

[Wan, Shuang]

SGkgTWFyY2VsLA0KDQoJU28gdGhlIGdub21lLWJsdWV0b290aCB3aWxsIGJlIHJlY29tbWVuZGVk
IFVJIGZvciBibHVlej8gQW5kIGJsdWV6LWdub21lIHdpbGwgYmUgbm8gbG9uZ2VyIG1haW50YWlu
ZWQgYnV0IHN0aWxsIGxpdmUgaW4gdGhlIGJsdWV6Lm9yZz8NCg0KVGhhbmtzIQ0KU2h1YW5nDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBNYXJjZWwgSG9sdG1hbm4gW21haWx0
bzptYXJjZWxAaG9sdG1hbm4ub3JnXSANClNlbnQ6IDIwMDnE6jfUwjE0yNUgMTA6MjMNClRvOiBC
YXN0aWVuIE5vY2VyYQ0KQ2M6IE1hcmlvX0xpbW9uY2llbGxvQERlbGwuY29tOyBXYW4sIFNodWFu
ZzsgbGludXgtYmx1ZXRvb3RoQHZnZXIua2VybmVsLm9yZw0KU3ViamVjdDogUkU6IGJsdWV0b290
aC13aXphcmQgcGluIGZpeGVkIGF0IDAwMDAgd2hpY2ggaXMgdW5hYmxlIHRvIHBhaXIgd2l0aCBo
ZWFkc2V0IHdpdGggb3RoZXIgcGlucw0KDQpIaSBCYXN0aWVuLA0KDQo+ID4gPiBOb3QgYmx1ZXot
Z25vbWUsIGdub21lLWJsdWV0b290aCwgYXMgYXZhaWxhYmxlIGluIHRoZSBHTk9NRSBnaXQgcmVw
by4NCj4gPiANCj4gPiBJZiB0aGVyZSBpcyBub3QgZ29pbmcgdG8gYmUgYW55IG1vcmUgZGV2ZWxv
cG1lbnQgaGFwcGVuaW5nIGFnYWluc3QgdGhlDQo+ID4gYmx1ZXotZ25vbWUgZ2l0IHRyZWUsIGNh
biBpdCBiZSBmb3JtYWxseSBraWxsZWQgd2l0aCBzb21lIGluZGljYXRpb24NCj4gPiB0aGF0IHBl
b3BsZSBzaG91bGQgd29yayBvbiBkZXZlbG9wbWVudCB3aXRoIGdub21lLWJsdWV0b290aCBhbmQv
b3INCj4gPiBibHVlbWFuIHRoZW4/DQo+IA0KPiBJIGJlbGlldmUgTWFyY2VsIHdhbnRzIHRvIGtl
ZXAgaXQgdG8gcGxheSBhcm91bmQgd2l0aCB0aGUgVUksIGZvciBuZXcNCj4gZmVhdHVyZXMuDQoN
CmNvcnJlY3QuIEFuZCBJIGFtIG5vdCBraWxsaW5nIGEgdHJlZSBqdXN0IGZvciB0aGUgZnVuIG9m
IGl0LiBJdCBpcyBhDQpnb29kIGhpc3RvcnkgbGVzc29uIGFuZCBnb29kIHRvIGhhdmUgdGhlIGNv
ZGUgYXJvdW5kLg0KDQpXZSBjYW4gdXBkYXRlIHd3dy5ibHVlei5vcmcuIEkgaW52aXRlIGFueWJv
ZHkgdG8gaGF2ZSBhbiBhY2NvdW50IHRoZXJlLg0KDQpSZWdhcmRzDQoNCk1hcmNlbA0KDQoNCg==