Android Template App: Problems with reconnection

RE: Android Template App: Problems with reconnection

Hephaestus — Mon, 05 Jun 2017 16:27:40 GMT

Any further comments?

RE: Android Template App: Problems with reconnection

Hephaestus — Thu, 11 May 2017 20:34:41 GMT

The phone is only used for development and there is nothing else running except this app.

RE: Android Template App: Problems with reconnection

Aleksander Nowakowski — Thu, 11 May 2017 20:27:19 GMT

Are you sure you don't have any other app running in the bg that connects to the same device? For example nrf connect? Please, close nrf connect with the back button, not home and try again. Or any other app that'susing Gatt Server (perhaps even yours?).

RE: Android Template App: Problems with reconnection

Hephaestus — Thu, 11 May 2017 20:21:59 GMT

Hi, Thanks for the response. I have not modified the internal code at all. I'm starting to wonder if the device is not being disconnected at all. Which would explain why its not on the list and why rebooting the device does cause it to show up on the list. I have been depending on the onConnectClick link from the button to the internal BleManager code, but have recently moved to a different button. What is the correct method to call from my main activity to disconnect a device?

RE: Android Template App: Problems with reconnection

Aleksander Nowakowski — Thu, 11 May 2017 13:46:45 GMT

Hi, I've checked the Template in nRF Toolbox 2.4 Out-of-the-box and after disconnecting I was able to see my device on the list. That means that the scanner and disconnection worked OK. Did you do any changes in the scanner? Perhaps it doesn't show a device with the same address that was already there before, but it's something you must have written on your own. I tried the Template with HRM sample from SDK 8 (as this one was laying on my desk).

RE: Android Template App: Problems with reconnection

Hephaestus — Thu, 11 May 2017 00:50:16 GMT

I get that. You are saying that an out-of-the-box version of the nRF Toolkit works fine. Clearly something in the app is different. I'm guessing that an object in the BleManager is not getting cleared onDisconnect. Can you recommend what object holds the state of the last connection? Or is there a call I can make into the BleManager to clear the state?

RE: Android Template App: Problems with reconnection

FormerMember — Tue, 09 May 2017 13:42:35 GMT

I just tested here with Nexus 5X, Android 7.1.2, nRF Toolbox v. 2.4.0 --> Template, and nRF52-DK, SDK12.1 -> ble_app_hrs, S132 v.3.1.0, and it is no problem to reconnect the nRF52-DK..

RE: Android Template App: Problems with reconnection

Hephaestus — Mon, 08 May 2017 08:18:17 GMT

Android SDK is nRF toolbox v2.4.0. The mobile phone is a Nexus 5X with Android 7.1.1. The device is running an nRF51 with SDK 12.1 and BLE 4.2.

RE: Android Template App: Problems with reconnection

FormerMember — Mon, 08 May 2017 08:15:05 GMT

Which phone, version of Android, and version of nRF Toolbox do you have?

RE: Android Template App: Problems with reconnection

Hephaestus — Fri, 05 May 2017 07:25:10 GMT

@Kristin. Thank you for the response. Using the nRF Connect app (Android), I can connect and disconnect repeatedly without a problem. Also, if I do the following:

Press Connect. Our device is listed on the Available Device page.
Choose our device. Connection is successful.
Disconnect by pressing the Disconnect button. Disconnection is successful.
Press Connect. Our device is not listed.
Reset/restart our device. Our device is still not listed.

If our device had stopped advertising after the disconnect, then I believe that it will reengage advertising after the reboot.

RE: Android Template App: Problems with reconnection

FormerMember — Fri, 05 May 2017 07:19:11 GMT

When the phone disconnects from the device, could you double check that the device actually starts to advertise? Do you see the same problem if you use nRF Connect (Android)?