Fixed
Status Update
No update yet.
Comments
ao...@gmail.com
We have the same problem.
ch...@google.com
dh...@gmail.com
I have the same bug on LG Nexus 4
pr...@gmail.com
Do you know, how this error can raise?
It would be interesting if it comes from the BLE device or from the Android stack.
It would be interesting if it comes from the BLE device or from the Android stack.
ch...@google.com
I am working on an app that connects to many devices and was getting the callback exception - it is because the Gatt connection is closed before the disconnect event has fired. So either you need to wait for the disconnect event, or what I do now is just call close. It seems to tidy away the connection without generating a disconnect event.
However, I am also sometimes getting BLE into a state where on connection, I immediately get a disconnect event and have to restart BLE to resolve. In my case I am getting status 133 not 22
However, I am also sometimes getting BLE into a state where on connection, I immediately get a disconnect event and have to restart BLE to resolve. In my case I am getting status 133 not 22
ci...@gmail.com
Ok. I have changed my implementation so that I am closing only after a disconnect which works for me now.
But I still get the status code 22. I remember that I also got a status 133 or 8 which are both not documented. I was not able to reproduce them so I do not exactly know when these status come up.
Another thing I found out is that after getting a successful disconnect from the callback the device is sometimes not disconnected and then I am not able to disconnect it anymore. It is then possible to connect it again and retry another disconnect which sometimes works.
I also observed that I got successfully disconnected but the callback did not fire. This leads to the problem that close won't be called, so a loose a BLE slot for connection which is a problem on devices where you only have 5.
But I still get the status code 22. I remember that I also got a status 133 or 8 which are both not documented. I was not able to reproduce them so I do not exactly know when these status come up.
Another thing I found out is that after getting a successful disconnect from the callback the device is sometimes not disconnected and then I am not able to disconnect it anymore. It is then possible to connect it again and retry another disconnect which sometimes works.
I also observed that I got successfully disconnected but the callback did not fire. This leads to the problem that close won't be called, so a loose a BLE slot for connection which is a problem on devices where you only have 5.
ch...@google.com
FYI: On the LG Nexus 4 with Android 5.1.1 I get disconnection with status 22 almost every time after connection to BLE device. Device is in the connected state about 30 seconds. And after that I get disconnection. That happens if BLE device is NOT paired with phone. Pairing helps to avoid such behaviour
ch...@gmail.com
Ok, but BLE devices should not need to be paired, only bonding should be needed.
So you pair a BLE device inside your app?
I try to avoid pairing, as this is not a standard BLE approach.
So you pair a BLE device inside your app?
I try to avoid pairing, as this is not a standard BLE approach.
Description
Version used: 22.0.0
I'm having this issue running my own code and running Chris Banes' example project (
The problem is that when the toolbar is expanded, the icons are way too high. And when collapsed, they are simply gone. See screenshots.
I'm trying this on a Moto X running 5.0. I know this happens on a Nexus 7 as well, but works fine on Nexus 5 running 5.1.1.