Bounding for some phones fails with PM_EVT_ERROR_UNEXPECTED

[hutorny]

Details: SoftDevice 132, nRF5_SDK_15.2.0_9412b96, Peer Manager, nRF52832-QFAA-0E, nRF Connect 4.22.3, Android 5.1, Android 7.1

Symptoms:

nRF Connect on Android 7.1 fails bounding with application running on nRF52832 (which is getting PM_EVT_ERROR_UNEXPECTED)
In the same setup Android 5.1 bounds fine. Order of bounding does not matter, symptoms appears on a freshly erased/programmed chip
Both phones able bounding with an SDK example application.

What could be wrong?

[run_ar]

Have you tried to compare the Peer manager settings between the working SDK example and the failing application?

Could you also capture a sniffer trace that show the failing bond procedure?

[hutorny]

In my app ble_gap_sec_params_t.lesc was set to true. After setting it to false both phones bounds with success. However, after bonding with Android 7.1 application seems to "hang" for some time. With Android 5 works as expected.

Could it be caused by stack overflow?

[hutorny]

I think I've figured out with this issue - in process of bonding, peer manager seems to disable interrupts for long period causing my application to miss some events and face unexpected state. That I've sorted out.
Though, there is still an issue with peer manager and Android 7, but with different symptoms. Should start another topic for that or reuse this one?

[run_ar]

Glad to hear you figured this out. If it's a different problem you should probably start a new thread. But if you think it could be the same you are free to continue this one. logs and air traces are often required to understand what the problem is, so please also consider adding that. thanks.