3 ms·
I have lots of bad experiences with Bluetooth. On Moto G1, Nexus 5x, Pixel 1, Aquaris X, Dell laptop with recent Windows 10, ARM Chromebook, x86 Chromebook, Ubu
by hawski 6y ago
I have lots of bad experiences with Bluetooth. On Moto G1, Nexus 5x, Pixel 1, Aquaris X, Dell laptop with recent Windows 10, ARM Chromebook, x86 Chromebook, Ubuntu. While connecting between those devices, connecting to a Jabra headset, Lenco soundbar, noname mobile speaker, OneAudio headset, Renault Laguna audio system. Issues varying between: can't see any device at all; can't see the device I'm trying to connect to; can't connect; can connect, but the device freezes and needs a restart; can connect, but the sound still comes out of an internal speaker; can connect everything works, but then it stops working and above apply; everything works, but have to pair every time.
It's dreadful everywhere. I think I had somewhat better experience with a Macbook, but at this stage I use bluetooth as little as possible, so can't really say.
Sorry, I guess I'm just venting...
- yrro 6y agoThis is a generalization, but these devices are very likely only tested until they barely work on Windows and Mac OS. And if they have to choose between a quick fix that makes it work on those two, and implementing the spec properly, they'll pick the first option. So it's on Linux to discover and work around all the brokenness (in the bluetooth host device as well as the speakers, phones, peripherals, etc...)
- viraptor 6y agoBluetooth is just massively (and possible needlessly) complex. The combinations of supported profiles and options are likely more numerous than IPsec ciphers. I've not seen a stack that doesn't spectacularly fail with at least one of my devices. It's not vendor/product specific.