←back to thread

1424 points moonleay | 1 comments | | HN request time: 0.222s | source
Show context
moonleay ◴[] No.45941605[source]
A cool project, when you want to use AirPods outside of Apples ecosystem. Sadly, you have to use a rooted android device with a small patch due to a bug in the Android Bluetooth implementation. https://issuetracker.google.com/issues/371713238
replies(6): >>45942063 #>>45942373 #>>45942451 #>>45943437 #>>45943943 #>>45944340 #
jmgao ◴[] No.45942451[source]
It doesn't seem obvious to me that this is actually a bug in the Android implementation, it seems like this is due to AirPods violating the spec and requiring a special handshake before responding to standard requests. It doesn't seem reasonable to expect Android to work around a device that appears to be intentionally breaking the spec for vendor lock-in purposes: the possibility of them just OTAing an update that breaks in some other way means that you'd have to be entirely bug compatible with iOS's bluetooth implementation.
replies(7): >>45942490 #>>45942736 #>>45942932 #>>45943032 #>>45943140 #>>45944246 #>>45944276 #
helsinkiandrew ◴[] No.45942932[source]
Apple have been ‘extending’ the Bluetooth stack for quite awhile. They introduced some BLE features before the spec was finished (I think some 3rd party hearing aids were also compatible).

I haven’t used non apple earphones for awhile but the seamless connectivity performance of AirPods would suggest this was done for performance, not to deliberately lock in devices.

This 2020 paper is great at breaking down some of the extensions: https://www.usenix.org/system/files/woot20-paper-heinze.pdf

replies(1): >>45942970 #
xethos ◴[] No.45942970[source]
> They introduced some BLE features before the spec was finished

In their defence, they went with Lightning shortly before the USB-C spec was finalized. Then, to avoid their customers being screwed over by constantly changing the connector, they kind of had to stick with it for a decade.

People will complain if they push features that are ahead of the spec, and they'll complain if they let the spec be finalized before they use it. Being guided by "What's the best we can do for UX, assuming out users are our users in every product category we enter" seems to be their reasonable middle ground.

replies(3): >>45943026 #>>45943116 #>>45943132 #
vee-kay ◴[] No.45943132[source]
The only reason Apple ditched Lightning port and finally gave USB-C port in the iDevices, is because EU forced Apple to do so. But do you think your oh-so-common USB-C cables will work with a new iPhone?

In my country (India), Apple still doesn't sell charger and cable along with its new iDevices, even though those gadgets are exorbitantly expensive. And Apple doesn't allow custom repair here, even though my country mandated the Right to Repair, like EU did so. My old Mac Mini 2012 is gathering dust in a cupboard, because Apple service center refused to upgrade it to new RAM and new SATA SSD, citing Apple policies.

replies(4): >>45943219 #>>45943729 #>>45943800 #>>45946272 #
raw_anon_1111 ◴[] No.45946272[source]
The higher end iPads started coming with USB C long before the EU mandate
replies(2): >>45947249 #>>45953913 #
1. monocasa ◴[] No.45947249[source]
That seemed like a product segmentation choice to encourage more laptop like use cases out of the higher end iPads.

Less friction for devices like passkeys, external hard drives, etc.

It doesn't seem like they were keen on moving that down the product line since they had to be dragged kicking and screaming to do so.