|
|
|
|
|
by Zetaphor
212 days ago
|
|
The obvious solution would be to report the lowest number, as multiple replies to you have already proposed, but you again chose to ignore because it doesn't serve your agenda. 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. |
|
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.