This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

After Android phone cancel pair, can not connect

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?

Parents
  • 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.

  • 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

Reply
  • 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

Children
No Data
Related