nRF52 stuck after disconnect from android.

RE: nRF52 stuck after disconnect from android.

run_ar — Thu, 11 May 2017 09:37:46 GMT

You have to look at the timing event (or use a sniffer to look at the connection request) to see what the supervision timeout is. I don't think the SDK function that checks the connection parameters checks the supervision timeout. Which means the other parameters could be within the desired range while the timeout is huge. As a test you could send the connection parameter update request regardless of peer parameters.

RE: nRF52 stuck after disconnect from android.

dc — Wed, 10 May 2017 16:48:59 GMT

Device side supervision timeout is 4 sec. Android side i am using nRF connect.

RE: nRF52 stuck after disconnect from android.

run_ar — Wed, 10 May 2017 11:05:07 GMT

What is the connection supervision timeout in this case? I have seen up to 20 seconds by default on Androind, and that is a long time to wait for the disconnected event.

RE: nRF52 stuck after disconnect from android.

dc — Wed, 10 May 2017 10:55:01 GMT

Thanks for Reply! This issue happens even I off android Bluetooth when device continuous sending notification.

RE: nRF52 stuck after disconnect from android.

run_ar — Wed, 10 May 2017 10:21:09 GMT

Might be that android keeps the connection alive. Even though the app is trying to disconnect. Try exiting the app completely and make sure you don't have any other apps that might use the device running. Appart from that you will get a disconnection event when disconnected. A sniffer trace would be helpful.