Earlier quoted context omitted.
I hope LE audio will fix that
By the way, what LE stands for? Legendary Edition?
The Bluetooth 5 spec is over a thousand pages long.
The Lite Edition spec is "only" a few hundred, IIRC.
71–80 of 599 posts
I tried to learn why BT is still somehow painful to use, and the article basically does not have an answer. My take from comments here and my experience: - Makers of BT devices can't agree on many important common things (easy discovery / pairing mode, priority, etc), and have little incentive to seek agreement. It's like phone chargers before USB. - Makers of BT devices tend to cut corners and/or add not-entirely-st…
> It's like phone chargers before USB. No, it's like phone chargers before EU regulators stepped in.
And even in the pre-smartphone days, phone chargers always worked reliably. Phone charging is and was the complete opposite of what bluetooth is today.
Let me pass on to you some ancient Chinese... er, German engineering wisdom: He who understands wireless communication uses cables.
- There is no decent support on web so we need to rely on the mercy of Apple/iOS (RIP to Web Bluetooth API).
- Some Android devices don't work well with Bluetooth (e.g. Motorola, OnePlus). Data packages are gibberish, connectivity is lost on random occasions, etc.
And from customer perspective: device manufacturers can't agree which pairing strategy is best, so they are keep experimenting leading to massive confusion. That's frustrating.
I’m building something that uses Bluetooth and largely for the classes of device I’m using everything seems to work fine? Isn’t all this like everything, largely Apple and premium devices work well and cheap crappy stuff barely works? Sort of implies it’s not necessarily the the standard at fault…
My Denon amplifier has an arbitrary limit of 8 paired devices. When you pair a 9th the oldest is forgotten. Storage is cheap, why have the limit!
Earlier quoted context omitted.
That sounds more like an Apple Bluetooth stack issue at their OS level rather than something wrong with the Bluetooth chip/tech itself. It's where you should complain to Apple or ask for refunds/replacements. Granted, Apple is not alone here since both Google and Microsoft really botched their Bluetooth stacks on their OSs. Especially Google who hasn't learned you can't treat your C driver/embedded SW like front-end…
Apple have really, really weird BT stack issues.
Earlier quoted context omitted.
> It's like phone chargers before USB. No, it's like phone chargers before EU regulators stepped in.
Everyone except Apple was already on USB. And even in the pre-smartphone days, phone chargers always worked reliably. Phone charging is and was the complete opposite of what bluetooth is today.
Earlier quoted context omitted.
'It's not Bluetooth's fault, Apple is just using it wrong'
And Microsoft. And Google. According to the parent.