Native state doesn't match reported state
-
Re: Scans with screen turned off on Android 8.1 and above fail
I've seen that you are also experiencing:
Tracked native state STATE_DISCONNECTED(0) doesn't match reported state STATE_CONNECTED(2).Any tips about how to work around this issue? Our firmware is reporting that the peripheral device is connected, and the reported state seems to agree. Any way to listen to that state instead of to the native state?
-
Same thing happens here
-
I found your post here https://forum.sweetblue.io/topic/12/explicit-disconnect-triggers-automatic-reconnect and I was actually able to make it work, but it's tricky