A sibling noted the H1 chip and whatnot. I don't know how much the specific chip matters for that piece (certainly key for battery life & having both buds appear as a single device). After all, their Bluetooth stack was better than the competition even back when they were using off the shelf chips. Still, it's possible off the shelf chips for acting as the master are somehow simpler than the chips for acting as a slave (or maybe you notice it more).
TBF, can't blame them. Apple has pretty much a single stack. Android is about as fragmented as the PC world.
Google has had a single Bluetooth stack for quite a while although variable quality vendor implementation. IIRC BlueDroid took over more of the stack than Bluez did so we're talking about 10 years here where Android has had a single monolithic stack.
The main explanation I've heard is that Apple has much fewer Bluetooth chips to support but I don't know that explains it because there's generally not that many chips in the market that all phones choose from (granted Apple is now in-house but still, they didn't use to be).
Also, I have no wires now other than a couple of chargers. It is freedom. Never do I have to untangle some EarPods from my keys five times a day.
The custom Bluetooth processor seems to be letting Apple solve a lot of pain points that every other Bluetooth headphone just makes you live with.
I could switch devices and the one I was using could connect up easy without having to do the whole disconnect from the other device first thing.
I suspect on connect it was also issuing a disconnect to the previous sender as well because I never had an issue of a device reconnecting overtop.
Multiple devices could be paired at the same time and it just latched on to whichever device tried to connect last.
Even apple doesn't do well at this. Apple also has all kinds of weird bugs and sound issues. They are still nice for walking around though so I won't be ditching them anytime soon.
Sound is pretty nice upgrade though even for someone like me that can't tell. Noise cancelling helps a lot over COVID too.
There are very few people who are both passionate about the problem of wireless devices and who understand all of the stack enough to make a driver that is fast, resilient, and standards-compliant. I hear that Apple sometimes bends the "standards-compliant" part - which is why their airpods only work with their devices.
Apple has done a great job giving this team of <100 engineers the space they need to succeed, and it's a huge feat. Most other companies don't even try to write their own BT stack (for good reason) and just use a vendor solution, so their user experience is subpar.
Still better than the competition though. Had a Sony Xm something or another before, but the Airpods are way easier and more comfortable by a huge margin.
I thought I heard Airpods were the best Bluetooth headset on Android, too
I continue to hold the view that Tesla's success is because they are really a software company, not a car company.
A toggle on the headphones -- a slide switch for Device A or B.
(Auto software switching would be better if it worked 99%+ of the time.)
What kind of switch would you suggest they use?
Last time this happened was with the OG iPhone of course. Still remember Maddox’s tear down of the iPhone lol. https://maddox.xmission.com/c.cgi?u=iphone/
Having no wires was not life changing, I don't really care about that. Running out of battery sucks though. The noise canceling really is great, but they never last a full flight, so I always need backup headphones.
I always switch to the cable if I want to use them with my Linux laptop as repairing is a pain in the arse.
I've also found the cable to be very useful for anything that requires both sound quality and a microphone at the same time. Over Bluetooth and even on my Apple stuff they seem to switch to the headset profile to use the mic and the sound then becomes aweful.
It took a long time to realize that the most compelling devices have good, well maintained software.
I don’t mean to say that software devs are geniuses or that these orgs have to hire the best of the best. No, they just need to create an org that prioritizes software dev. Low attrition, increased visibility, the usual. You don’t need fancy new features. Just make sure the intern who wrote your v1 Bluetooth driver feels compelled enough to stay on to become a staff engineer running a team that still assures bugs get fixed. Simple.