That is such a typical bug report to a large company. A user who spent a lot of time debugging and finding the root cause of an issue, and a few faceless peons at the large company spending a few minutes on it, realizing it’s not a priority, and abandoning it.
Not really. There wasn’t a true patch attempt submitted, as far as I can see. There was some helpful info about how commenting out a couple lines could work around the issue, but doing a real engineering evaluation to check spec compliance and make sure it’s all covered in the Bluetooth testing infrastructure is a much bigger task.
And not a small bug either. This large an interoperability issue and it takes a nerd not in the employ of Google to fix their shit? This is why Apple's vertical integration makes it one of richest companies in the world. Google's only up there because of their success in that one business of theirs.
What does Apple being Apple have to do with Google not paying somebody to work on getting Airpods, which presumably should conform to some Bluetooth spec, in order to get Airpods to work on Android?
>>...due to a bug in the Android Bluetooth implementation.
The issue can be resolved because an android bug can be debugged by a contributor. A similar issue can't even be analyzed from the apple side by anyone but an apple employee.
We are assuming there are bugs in iOS, but their closed sourceness can mislead people to believe there aren't. Then, yes, their vertical integration makes them rich, which in this case is bad for users, in the guise of being good.
