←back to thread

1424 points moonleay | 2 comments | | HN request time: 0.672s | source
Show context
isoprophlex ◴[] No.45943174[source]
From a bit further down the page

> Bluetooth DID (Device Identification) Hook > Turns out, if you change the manufacturerid to that of Apple, you get access to several special features!

I hope Apple gets slammed hard by some regulatory body. Apparently there's absolutely zero magic reasons why their airpods are unable to connect to non-Apple devices; pretend you're an iPhone and you're in.

EDIT: read "unable to connect" => "unable to expose advanced functionality", ofc they connect just fine

replies(15): >>45943218 #>>45943230 #>>45943299 #>>45943335 #>>45943389 #>>45943452 #>>45943491 #>>45943620 #>>45943639 #>>45943933 #>>45944000 #>>45945287 #>>45945990 #>>45946884 #>>45950063 #
matwood ◴[] No.45943218[source]
> Apparently there's absolutely zero magic reasons why their airpods are unable to connect to non-Apple devices

I've had almost all of the versions of AirPods and AirPod Pros and they have connected to non-Apple devices just fine.

replies(6): >>45943380 #>>45943430 #>>45943479 #>>45944029 #>>45944106 #>>45946746 #
realusername ◴[] No.45943430[source]
Personally I've tried the ones of my wife on my Galaxy S23 and I have frequent audio cuts, since it's the only Bluetooth device I've ever experienced that, there's some shenanigans for sure in their firmware.
replies(2): >>45943847 #>>45946767 #
1. maccard ◴[] No.45943847[source]
I had a slightly older galaxy as my last android phone, and had this problem with the galaxy buds and with the anker ones I got to replace them. My experience with audio on android (Samsung and pixel) was overwhelmingly “this sucks” so I’m more inclined to blame android than apple here
replies(1): >>45943995 #
2. realusername ◴[] No.45943995[source]
Personally I never had any audio issues at all apart from pairing (but I also had this issue on iPhone, this is a general case of Bluetooth pairing sucks)