Multipoint connectivity is part of the spec but apparently AirPods only support it if you pretend to be an Apple device.
https://www.bluetooth.com/specifications/specs/core-specific...
The Battery Service 1.0 spec was officially adopted in 2011:
https://www.bluetooth.com/specifications/specs/battery-servi...
The first airpods were released in 2016...
Please consider that simping for a trillion dollar company might actually not be in your best personal interests...
https://www.bluetooth.com/specifications/specs/multi-profile...
They support HFP and A2DP and AVRCP, and properly, including all of those features working on android phones and proper switching between them as needed...
How you could argue that this is a good thing tells me you're either too drunk on the corporate kool-aid or that you have some financial incentive to ignore the obvious problems with these facts.
Either way this is my last message in this thread as googling things for you is a bore.
This entire thread started with you claiming Apple was somehow trying to prevent issues by hiding these features, and you've twice tried to move the goalposts to irrelevant points when given evidence to the contrary.
If you can't even defend your original position then I have no interest in continuing a discussion with Apple's most useful idiot.
Hyper-fixating on an issue with one part of the spec doesn't dismiss the larger problem being discussed. It's baffling (and kind of sad) how hard you guys feel the need to defend a trillion dollar company making obviously anti-consumer decisions.
If you know the average of those three, what does it tell you?
What other manufacturers have figured out how to report three devices that represent to a Bluetooth host as one device in a standards conforming way that will work across multiple hosts?
It’s not that I am defending a trillion dollar company - the idea of averaging three completely different devices is non sensical and provides absolutely no benefit to the end user. If you want ti complain about anyone - complain about the standards body.
This entire thread started with someone trying to claim that Apple was not in the wrong by restricting these features, of which battery reporting is A SINGLE ONE.
No, I don't have a perfect solution for this one specific part of the problem, but that's also not been the my focus the entire time. Getting dragged into the weeds only serves to distract from the actually important point here, which is that what Apple is doing is anti-consumer.
Let's first agree that Apple should play on even ground with everyone else, and then we can whinge over how to correctly report the battery of three components over a single connection. Yeesh.
You claimed other manufacturers have “figured this out” - how?
Every single thing that you say Apple should do is about how Apple can do that in a method that conforms to the spec - you kind of have to “fixate” upon the spec if you claim that Apple isn’t conforming to the spec.
The battery reporting is the one you brought up and had only horrible ideas.
The reality is the sort of compatibility being talked about is a new feature with design choices, not just unwired functionality.
I'd rather them work on features to report charging time or expected playback time on iOS, or write their own app for Android, than try to arbitrarily increase their bluetooth profile compatibility checklist.