Android code with autoconnect implemented

RE: Android code with autoconnect implemented

Aleksander Nowakowski — Fri, 08 Sep 2017 09:40:55 GMT

You can't call gatt.close() when it disconnects as this will release the gatt object. Also, the first connection should be with autoConnect=false, as it's much faster (active connection). When you get a callback onConnectionStateChange with State disconnected you there call gatt.connect() which (if you check the source code) will use true since then. We recommend using the BleManager class from nRF Toolbox. It handles it and common errors automatically. Source code for nRF Toolbox is on GitHub, for nRF Connect is not public.

RE: Android code with autoconnect implemented

vineeshvs — Thu, 07 Sep 2017 16:56:27 GMT

It works with nRf connect. Then it should work in our app also if implemented in the same phone right? We are in the autoconnect logic. What should be the logic in implementing autoconnect? Which all functions we need to call and in what order? Any help is appreciated.

RE: Android code with autoconnect implemented

Petter Myhre — Thu, 07 Sep 2017 07:00:55 GMT

And it works with nRF Connect? Apparently some phones do not support autoconnect, see this.

RE: Android code with autoconnect implemented

vineeshvs — Thu, 07 Sep 2017 03:45:50 GMT

I have already tried making autoconnect = true. Still it is now working. Once disconnected, it's not connecting back

RE: Android code with autoconnect implemented

Petter Myhre — Tue, 05 Sep 2017 11:36:41 GMT

I'm not an Android expert, but this seems to be a bool you set when you call [connectGatt()](developer.android.com/.../BluetoothDevice.html, boolean, android.bluetooth.BluetoothGattCallback))?