[SkyPuncher]

This was a major issue that drove me away from Android. In addition to first party bugs, I got tired of 3rd party accessories not working correctly.

My theory was iPhone probably got tested on most 3rd party accessories. However, the fragmentation in the Android space meant I’d have no idea what devices they actually tested with.

This is further compounded by the fact that Android isn’t really an open platform, at least in a practical sense. I can’t just load up a patch for something (assuming it exists) without fully switching to some open source ROM that’s going to come with its own issues.

[eddieroger]

There's also only one Bluetooth stack on Apple's platforms (presumably shared), so testing is more straightforward. And if so inclined, there's also the Made for iPhone program that requires validation, but again that's with one device in two form factors. It's not a fair challenge comparing Android device support because the task is bigger, though Google could probably do some stuff to make that less painful.

[SkyPuncher]

As a consumer, I just don't care whether it's fair or not. Android and iOS are competing, almost identical platforms. They both do what I need, but only one of them doesn't always break.

Saying it's not fair to compare them is like saying it's not fair to compare a minivan to an SUV when making a car purchase. They're different, but similar enough.

[londons_explore]

Google could just say "Here is our official bluetooth hardware/software. Either use the official hardware/software, or use something else but we will kick you out of the android program if your implementation and ours ever have any kind of difference that is noticeable to a user".

[AtlasBarfed]

It's almost like there should be a, I don't know, STANDARD test suite that peripherals, phones, and chips that want to use the Bluetooth STANDARD would have to pass in order to advertise being compatible with the Bluetooth STANDARD, as directed and administered by the Bluetooth STANDARD organization.

Bluetooth is so old that it was coming into use when Computer Shopper was still published. It's been a dumpster fire of compatibility since its inception.

There's one of two culprits on the Android side: either its the device drivers, or the OS itself. Device drivers should be capable of being subjected to stringent acceptance standards in order to advertise "Bluetooth". If it's the OS, that's even worse since it is higher up the abstraction stack. At least the device drivers being closer to hardware have an excuse.

Bluetooth is 26 years old. A 26 year old industry standard should be better than a coinflip as to whether some bluetooth thingamajig will work with a mobile OS. It's just sad.

[Bluestein]

> year old industry standard should be better

Ballpark as old as USB if not mistaken, and that's saying lots ...