Using SDK 15.3 on the embedded side and Android 10 I think it is on the mobile side.
We've implemented whitelists and hanging onto the bonding information on the embedded side. The idea is that once the mobile side is talking to us we only want to talk to that particular device until we explicitly change to another one.
This works fine across power cycles on both sides. Once paired and bonded and everything, the mobile side and embedded side exist in married bliss.
Now, pull up nRF connect and run a DFU on the embedded side. Once the embedded side comes back (and it is keeping all the bonding information and whitelists and all that across this as far as I can tell), Android wants to pair again...
I just don't understand why this is. We've got the bonding information both sides as far as I know. Why does the Android side really want to pair again? Am I missing something on the embedded side?