After Android phone cancel pair, can not connect

[Chaw]

Dear NORDIC I have one strange issue:

My nRF52 app work well, then I use Android phone connect to it, it's OK. Then Android phone cancel pair, so nRF52 disconnect,

then Android phone can search nRF52, but can not connect successfully,

Android phone show "nRF52 refued" or "can not communication to nRF52".

Then, I use ble_app_template(SDK12 example), foud that it is same. Could you help me check why?

[Hung Bui]

Hi Chaw,

What do you mean by "cancel pair" ? Was that you clicked pairing and then you canceled it ?

Have you tried to use nRFConnect app to connect and pair ?

Could you record a sniffer trace ?

[Chaw]

I means:

1. nRF52 power on, adversiting

2. Android Phone enable BT, scan, find nRF52

3. Android Phone press nRF52 to connect, then connect successfully

4. Android Phone remove nRF52 in BT paired devices list (cancel pair)

5. Android Phone start to scan again, find nRF52

6. Android Phone press nRF52 to connect, but show (nRF52 refused or can not communication)

Sorry, I can not get sniffer trace, but SDK example ble_app_templated can reproduce, could you test?

[Hung Bui]

Hi Chaw,

It's most likely because you configured the peer manager to reject re-pairing (default). This is to avoid attacker can spoof a central (copy your phone address) and tell the nRF5 to re-bond therefore delete the genuine bond information.

If you want to allow re-pairing, you need to set allow_repairing = true in PM_EVT_CONN_SEC_CONFIG_REQ event in pm_evt_handler() if you are using the example in the SDK.

[Chaw]

Thanks. It work well.

[annapalu]

Hi Hung,

is there a sort of tutorial that explain how the softedevice memorize the bonding information? I expected that when i delete the bonding information, i delete everthing, also the old bonding device.

And why i have this problem when i have added the withelist, before it i can rapairing with a already bonding device withou problem, also with flag set to false.

thank, Anna