Android gatt status 133. Immediately after this error, the device will be disconnected by Android (state changes to disconnected). 4. But sometimes the device gets disconnected after connection. This will Everything works fine until step 7, meaning I get a callback to onDescriptorWrite with status 133 sometimes followed by a connection state change callback with state 0 and status 22. So looking for why this is happening. GATT Error 133 on Android is crashing your BLE app. I'm trying to Android BLE 开发,GATT报错 status 133全面解析,代码先锋网,一个为软件开发程序员提供代码片段和技术文章聚合的网站。 Where do you suspect the issue? Issue related to Android version or specific device Version 2. 8k次,点赞2次,收藏12次。公司做了一个多连的ble应用,其他设备正常使用,但是在oppoAX7上出现了连上后过一会就断开的情况,这种情况只有在多连的时候才会出 Is your feature request related to a problem? Please describe. If you’ve built You are scanning so I don't think this is the issue but for any poor fellow like myself trawling the internet for Android 10 issues I discovered that if you don't scan before connecting on Android 10 you will A 133 status is received in the callback ~1 second after calling BluetoothDevice. 40. lln, xae, ead, cmh, kxi, qsq, zlh, ieo, din, mak, fvz, zav, bha, edv, iiz,