Custom `BleManager` implementation about android-nrf-toolbox HOT 4 CLOSED

Hi, the most recent one (constantly supported) is in nRF Toolbox (and Wear for Android Wear). I guess the differences aren't big... if any? Others may be a forked from this one from some moment in time.

from android-nrf-toolbox.

Hi, thanks for your reply. The changes are minor yes, but they are some because the implementation is not totally projet independent.

I would like to known how you handle the fact that the BLE stack can be busy. From the nextRequest method, you call the low-level primitives to write to a characteristic (ATT write command for instance), but you don't handle the return code given by the stack... How do you handle messages retransmissions ? What is the common pattern do you use ?

from android-nrf-toolbox.

We don't handle retransmissions. Actually, I don't know if it would be that easy... from my experience, when Bluetooth hangs, you have to reset the adapter, or sometimes the phone as it just automatically turns on again (so in fact can't even turn off). It's such a critical problem, that users see it as "this application doesn't work and killed my Bluetooth! 0 stars!".

from android-nrf-toolbox.

Thanks for answer. I will investigate a bit more but if I remember correctly any ATT read/write commands from the BluetoothGattCharacteristic class can return false, and this was the case quite frequently. The reason why false is returned is not very clear for me (radio busy or something similar) and don't seems to be documented. If false is returned, IMO it should be handle correctly, but I did not find a good pattern yet.

from android-nrf-toolbox.