Bonding error 132 with HID example.

RE: Bonding error 132 with HID example.

Einar Thorsrud — Thu, 22 Aug 2019 11:11:00 GMT

In case anyone has a similar issue later, the issue was found and it turns out that Android assumes that a device has keyboard input as long as the appearance is set to BLE_APPEARANCE_HID_KEYBOARD even if the IO capabilities of the peripheral is set to display only. So the fix, in this case, was to change the appearance to something else.

RE: Bonding error 132 with HID example.

Einar Thorsrud — Wed, 21 Aug 2019 09:23:48 GMT

Perfect. I will test and get back to you.

RE: Bonding error 132 with HID example.

NamoAton — Wed, 21 Aug 2019 08:58:12 GMT

[quote userid="7377" url="~/f/nordic-q-a/51187/bonding-error-132-with-hid-example/205220"]Does it run on the DK?[/quote]

yes it run on dk. I created..

RE: Bonding error 132 with HID example.

Einar Thorsrud — Wed, 21 Aug 2019 08:52:29 GMT

Hi,

Yes, that could be useful. Please make a new private question and refer to this thread, and upload your code there. Please upload the complete project so that I can drop t in the SDK and build it out of the box. Does it run on the DK? Also, please specify SDK version and a simple test procedure.

RE: Bonding error 132 with HID example.

NamoAton — Wed, 21 Aug 2019 05:05:34 GMT

[quote userid="7377" url="~/f/nordic-q-a/51187/bonding-error-132-with-hid-example/205050"]which version of Android does it use?[/quote]

Samsung S9, Android 9.
I can send you code in pm. Maybe this would be useful to resolve porblem..

RE: Bonding error 132 with HID example.

Einar Thorsrud — Tue, 20 Aug 2019 13:09:08 GMT

Hi,

[quote user="NamoAton"]When I try the same procedure with my "HID" device, the pop-up window appeared for a second with no line for passkey, but with numbers instead.[/quote]

That is odd. When the initiator (phone) supports display and keyboard and the responder (nRF) supports display only, the MITM protection should always be in the form of passkey entry where the responder displays the key and it is input on the initiator. This is the same for both LE legacy and LE secure pairing.

The fact that you see numbers instead, could be that it is for numeric comparison. Is there also a Yes/No button there? However, if you really set the IO capabilities to BLE_GAP_IO_CAPS_DISPLAY_ONLY, then the numeric comparison is not possible per Bluetooth specification. The error 132 (0x84) is BLE_GAP_SEC_STATUS_CONFIRM_VALUE, which typically indicates that the wrong passkey was entered or that the numeric comparison was rejected (pressed no). In any case, numeric comparison should not be an option in this setup. Which phone model are you testing with, and which version of Android does it use?

RE: Bonding error 132 with HID example.

NamoAton — Tue, 20 Aug 2019 12:43:31 GMT

Ok. I take for a base glucose app. When I tried to connect to nrf52 device from android phone. I got pop-up window with line for passkey enter.
When I try the same procedure with my "HID" device, the pop-up window appeared for a second with no line for passkey, but with numbers instead.

RE: Bonding error 132 with HID example.

Einar Thorsrud — Tue, 20 Aug 2019 12:34:49 GMT

Hi,

Is it so that your HID device has a display (or another method to display the passkey)? That is what you have specified (BLE_GAP_IO_CAPS_DISPLAY_ONLY), but I just want to be sure.

[quote user=""]But it don`t want to connect as primary example. It no asking a passkey from phone. Just appeared for a second.[/quote]

It is not clear to me what is happening. Can you elaborate on the problem?

Also, it would be interesting to know more about your implementation. As you can see from the Glucose Application (which use passkey), there is not much you need to do other than configuring the IO capabilities and MITM as you have, and display the passkey when you get a BLE_GAP_EVT_PASSKEY_DISPLAY event.