Comment by TheDong
9 hours ago
No one has presented a remotely correct fix anywhere on that issue, or elsewhere to my knowledge.
You're welcome to write an actually correct patch for android if you want, one that isn't just commenting out code and probably breaking some spec-compliant bluetooth devices.
Make sure to test your patch against all the bluetooth devices in existence to make sure it doesn't regress.
Do that, make a PR, wait the average third-party-android-PR review time (approximately 5 years), and then if your PR isn't accepted at that point we can maybe say Google is intentionally ignoring this issue.
https://issuetracker.google.com/issues/371713238#comment829 seems fine and only has the potential to break other Apple BT hardware, which is relatively easy to test.
Nobody actually productively commenting in the thread thinks it's a conspiracy theory and everyone acknowledges that the Apple hardware is off-spec. It would be nice to see Android add this workaround.
You have linked me to what sounds like an AI generated comment. AI comments cannot be trusted. AI will make up believable sounding gunk and cannot be trusted.