https://devzone.nordicsemi.com/f/nordic-q-a/121769/android-15-introduces-bug-where-bonded-devices-cannot-be-disconnectedWe use several Nordic chips in our BLE sensors. We bond to the devices from Android, connect to update configurations, then disconnect such that the device then advertises beacon information periodically. The problem we just hit with Android 15 (it worksen-USTelligent Community 13Thu, 26 Jun 2025 12:42:32 GMThttps://devzone.nordicsemi.com/thread/540584?ContentTypeID=1Thu, 26 Jun 2025 12:42:32 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8f76993d-b43d-4fcf-a5cb-1837a680a6a1tesc<p>Hi,</p> <p>I see there has been no responses yet here. Is this still unresolved?</p> <p>We are unable to reproduce this locally, as disconnection works fine here from Android 15. What phone, and what specific version, is this, and what app, library or other method are you using on the Android side?</p> <p>Also, if you have any logs, error messages, sniffer logs or other info highlighting what is happening, it might be possible for us to have a look to see if we find anything to be off.</p> <p>If it turns out you that do indeed need a workaround on the nRF for things to work, then at least you could reset the timer when communication does take place, in order to avoid timing out from active sessions. Alternatively, I guess you can provide a custom service where the android can request to the nRF that it wants the nRF to end the connection. Nevertheless, both of these would be a last resort if no other solution is found.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>