Re:Bluetooth remains an 'unusually painful' technology after...
by seanalltogether on Wednesday July 20, 2022 @09:16AM
(#32165347)
> The one thing nobody seems to do is stick to the standards provided, because they simply aren't broad enough for the creative stuff that people do with Bluetooth and Bluetooth LE.
Yeah, I've been working with BLE now for clients for 3 years, it seems like most people think of their devices as little CRUD servers (unless you're doing genuine pairing with constant data streams). BLE would be much better using a simple REST model than the GATT table model.
> Also, the bluetooth library in Android started out terrible and didn't improve despite being replaced
One thing I'll give Apple credit for is having a very solid bluetooth stack. We've had only a handful of BLE connection failures on our testers apples devices over the past 3 years, whereas on android test devices we get at least one connection failure DAILY that interrupts test cases from running. Furthermore Android devices just reach a point of critical failure where you need to just restart the device to resume BLE.
Yeah, I've been working with BLE now for clients for 3 years, it seems like most people think of their devices as little CRUD servers (unless you're doing genuine pairing with constant data streams). BLE would be much better using a simple REST model than the GATT table model.
> Also, the bluetooth library in Android started out terrible and didn't improve despite being replaced
One thing I'll give Apple credit for is having a very solid bluetooth stack. We've had only a handful of BLE connection failures on our testers apples devices over the past 3 years, whereas on android test devices we get at least one connection failure DAILY that interrupts test cases from running. Furthermore Android devices just reach a point of critical failure where you need to just restart the device to resume BLE.