NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Sigurd — Wed, 13 Sep 2017 12:20:06 GMT

Since this only happens on a few phones, I suspect that this issue is bug in the BLE stack on the phones that is affected.

Error 133, defined as: #define GATT_ERROR 0x85 is a general BLE error. It usually appears when a device is not reachable or when Android stack expected something or received something unexpectedly. Doing a new scan might have reset some internal state, and made it possible to connect again.

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Prasad — Tue, 12 Sep 2017 06:57:24 GMT

I get GATT error 133.

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Sigurd — Mon, 11 Sep 2017 16:12:37 GMT

When you try to connect from the device's tab, do you get any information in the log(swipe from left to right when in the device tab, to show the log) ?

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Prasad — Fri, 08 Sep 2017 10:27:38 GMT

I am observing this issue on Moto G3 as well(Android marshmallow). Can anyone please let me know what is going on in NRF connect when I refresh the scan screen due to which I am able to connect again to the devices?

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Hung Bui — Wed, 12 Jul 2017 12:46:59 GMT

We haven't heard others complain about this issue. I would assume that it's only on a some particular phones (or only Motorola C) that having this issue.

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Prasad — Wed, 12 Jul 2017 12:21:23 GMT

I got my hands on a samsung J7 phone. As you said the issue doesn't appear on this phone. I guess this issue isn't there for samsung phones.

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Prasad — Wed, 12 Jul 2017 12:18:04 GMT

My nrfconnect application version is 4.12.0, I think this is the latest available. Yes, I am waiting long enough. Actually when I turn off bluetooth, "enable" button appears on nrfconnect and not the connection status. My peripheral device also indicates that it is in disconnected state and it is advertising.

I tested this issue on Motorola E phone as well, this issue doesnt occur on Moto E.

RE: NRF connect doesn't reconnect when phone bluetooth is turned off and then back to on again

Hung Bui — Tue, 11 Jul 2017 11:21:22 GMT

I don't see that issue on my phone (Galaxy S8) . I was suspecting the BluetoothDevice instance was not free-ed up after the disconnection caused by turning off BLE on your phone. When you switch to scan panel, the instance is killed and new instance used to connect when you press connect there.

But then it should show the same thing on my phone. It didn't.

Have you updated the nRF Connect to latest version ?

When you turn off Bluetooth have you waited long enough so the status on nRFConnect says "Disconnected" ?