RE: BluetoothLeAdvertiser.stopAdvertising() causes device to disconnect

Aleksander Nowakowski — Wed, 05 Dec 2018 14:45:27 GMT

Btw, there are some phones, for example Meizu 2 with Android 5.1, where calling `server.connect(device, autoConnect)` will actually call `onConnectionStateChanged callback again. So make sure you don't fall into a loop.

RE: BluetoothLeAdvertiser.stopAdvertising() causes device to disconnect

Aleksander Nowakowski — Wed, 05 Dec 2018 14:38:01 GMT

Hello,

First of all, sorry for the devzone experience. Don't know what to say, I'm not responsible for this 😞

Coming to your question: advertising is independent from the connections. On Android a phone may actually advertise with many different advertising sets, each with a different, changing from time to time address, etc. You control advertising separately from connections.

Your approach to stop advertising when a remote device connects is correct. Remember to call `server.connect(device, autoConnect)` after a device connected. This is to let the system know that you're now going to use the connection, otherwise the system may close it if you don't do `device.connectGatt(...)` (which also tells the system, that you will actively use the connection in your app). When you are done, call `server.cancelConnection(device)`. If `server.connect(...)` won't help, call `connectGatt(..)` to get access to the device`s services.

Stopping advertising should not disconnect anything, just like it doesn't disconnect in nRF Connect when you stop advertising. It may be either the automatic disconnection, which happens a second after last client disconnected (or when your device connected, but no client connected to it), or some mistake in your code.

Hope that helped!

BR, Aleksander

RE: BluetoothLeAdvertiser.stopAdvertising() causes device to disconnect

MichaelNordicUser — Sat, 01 Dec 2018 22:35:15 GMT

I can't even edit my own post, this new Q&A website is regression from the previous version IMO. I almost don't even want to ask for help.