←back to thread

1424 points moonleay | 2 comments | | HN request time: 0.535s | 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 #
monerozcash ◴[] No.45943800[source]
>But do you think your oh-so-common USB-C cables will work with a new iPhone?

They seem to work just fine, yeah.

replies(1): >>45944377 #
toyg ◴[] No.45944377[source]
"Seem". Until they don't. I've had multiple instances of Airpods stopping to connect with phones until I charged them at least once with original Apple cables. They might work fine for months, then stop ehaving unless connected through an all-Apple power pipeline (cable and charger). It's probably firmware updates requiring some sort of validation every now and then.
replies(3): >>45946662 #>>45957773 #>>45958384 #
vee-kay ◴[] No.45958384[source]
I know that Apple MFI certified Lightning cables work well with iDevices, but I found that third-party non-MFI-certified Lightning cables to be finicky with iDevices. But I never faced such problem with USB cables for non-Apple devices (Android phones, cameras, etc.).

Apple MFI certifies USB-C cables also, so I'm not sure if it is throttling its iDevices to be finicky with non-MFI USB-C cables.

I know for a fact that Apple did software updates to older iPhones to make them sluggish and drain battery quickly. I realised this when I went to Apple Genius Bar to get my iPhone 7 Plus battery replaced after it started draining too quickly daily, but even with new battery same problem persisted. The friendly staff member unofficially told me it is because of the recent software updates by Apple for older iPhones, and advised not to hold out hope that any future software update will fix the problem. Even a year later, his warning remained true. I gave away the iPhone to my nephew as a backup device for his studies, but he sold it soon, as it was a nightmare to keep charging it frequently.

Apple has faced multiple fines for deliberately slowing down older iPhones without informing users, including a €25 million fine in France and a $41 million fine for deceptive marketing practices. The company admitted to slowing down devices to prevent unexpected shutdowns due to aging batteries, but critics argued it was misleading.

These days, I wouldn't trust Apple with a barge pole, let alone the money from my wallet.

replies(1): >>45958789 #
monerozcash ◴[] No.45958789[source]
>Apple has faced multiple fines for deliberately slowing down older iPhones without informing users, including a €25 million fine in France and a $41 million fine for deceptive marketing practices. The company admitted to slowing down devices to prevent unexpected shutdowns due to aging batteries, but critics argued it was misleading.

These cases are much less convincing than they may seem if you just take a moment to read about them. iDevices would throttle the cpu to make the battery last longer as it's capacity falls, this kind of throttling is not uncommon and not malicious.

This wasn't misleading, and isn't something that warrants any genuine criticism.

replies(1): >>45961608 #
1. vee-kay ◴[] No.45961608[source]
In my experience, the only 2 mobile phone companies whose phones drain battery too fast are Apple and Samsung. Apple does this deliberately for older phones, whereas Samsung has this problem even for new phones.

You will not find this quick battery drain problem in Motorola, Nokia, Oppo, Sony, etc. Their phones last several years even with ageing batteries. An 10+ years old Oppo phone I have, still holds almost full charge at idle, throughout the day.

As batteries get older, their capacity to hold charge reduces, but if a phone battery is draining too fast even in idle mode, it is likely due to software, not hardware. And if it is due to software, then the manufacturer company is to blame.

replies(1): >>45966679 #
2. monerozcash ◴[] No.45966679[source]
I don't think you can find any evidence of a Apple actually deliberately doing things to make batteries drain faster on older models.

That would either require hurting the battery life on all models or require distinguishable behaviours that only occur on specific models and would be relatively simple to prove through reverse engineering.

Apple has been fined for the throttling, but hasn't ever been credibly accused of actually deliberately taking steps to reduce battery life on older devices.