Bluetooth LE Error 133 triggers disconnection

Question

I'm calling mBluetoothGatt.readCharacteristic(data) in my app which is connected to a Bluetooth LE device. Sometimes the corresponding onCharacteristicRead() method is called with status 133. Immediately after this error, the device will be disconnected by Android (state changes to disconnected).

Does anybody know, why the error 133 occurs and why the device gets disconnected by Android afterwards? How can the disconnection be prevented?

Thanks Ben

Answer 1

I've had a status 133 when connecting to a bluetooth device where I've connected to before, but the firmware has changed in the since the last time I was connected to it. I've been able to fix this by clearing the bluetooth cache of the android device (by turning bluetooth on and off).