Obsolete
Status Update
Comments
yb...@google.com <yb...@google.com> #2
I can confirm this on Android 4.4.4 with Cyanogen Oneplus.
jo...@fueledbycaffeine.com <jo...@fueledbycaffeine.com> #3
Still present in Android Lollipop 5.0.1 on Nexus 5 and Nexus 6. Is anyone at Google actually reading the bug reports? This one is quite old and should be very easy to fix...
wo...@gmail.com <wo...@gmail.com> #5
In what way is this obsolete?
As you can see, this is still present in the master branch athttps://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/bluetooth/BluetoothGatt.java .
Why not just fix it by moving "mAutoConnect = autoConnect;" above "if (!registerApp(callback)) {"?
As you can see, this is still present in the master branch at
Why not just fix it by moving "mAutoConnect = autoConnect;" above "if (!registerApp(callback)) {"?
ra...@gmail.com <ra...@gmail.com> #6
I just got 5.1.1 update on Samsung Galaxy S6 and it triggered the same error. Cant connect to BLE devices, always getting GATT 133 error.
Description