- read low latency / in-ear detection status
- react on changes
These might have been changed from a different phone, so we cannot
assume our stored values to be correct.
After using Google Fast Pair the buds will have their bluetooth name suffixed
with some identification text, thus the exact match won't work anymore and they
get detected as generic headphones instead.
When the In-Ear detection state changes on the device (via a 2nd
connected phone) handle the change indicated by the buds and update the
value accordingly.
When the buds change their audio / ANC mode (via buds touch, or a 2nd
connected phone) they send the current state using a different command.
Handle that so the state is updated properly.
Newer buds send 6 bytes for ANC status instead of 3. Since the relevant
information is in the first 3 bytes and identical allow extra trailing
bytes when parsing.
Confirmed on the Buds 2 Plus. Likely also applies to Ear(a) (see #3994),
possibly other models as well.
Some Buds support additional ANC modes "medium" and "adaptive".
Add them to the available modes.
- Buds 2 Plus
- Ear(a) (see #3994)
Likely also applies to other models.
Dominik Riebeling
