Scope
Linux
Problem or use case
I was testing support across different models of Airpods (specifically on the Airpod 4s) and I noticed that it was showing the battery was 100% while my phone was showing a battery status that was not full. Looking at the application I saw that it was because it was also picking up my Airpod Pro 2s and that battery status was superseding the Airpod 4s.
Theres an image of both the tray icon and the app view below:
Proposed solution
I imagine it would be pretty simple to show all the status on hover of the tray icon, something like:
Battery Status
Airpods Pro 2nd Gen:
L: --% | R: 100% | C: --%
Airpods 4
L: --% | R: 89% | C: --%
Alternatives considered
Alternatively, the tray application could expand to have different circles for each device, perhaps with an icon within the center of the ring representing the different models and showing the name & battery status for just the device of the circle being hovered over -- I think this is actually a more complete solution, but it seems overkill for what is likely a mode edge-case situation.
Scope
Linux
Problem or use case
I was testing support across different models of Airpods (specifically on the Airpod 4s) and I noticed that it was showing the battery was 100% while my phone was showing a battery status that was not full. Looking at the application I saw that it was because it was also picking up my Airpod Pro 2s and that battery status was superseding the Airpod 4s.
Theres an image of both the tray icon and the app view below:
Proposed solution
I imagine it would be pretty simple to show all the status on hover of the tray icon, something like:
Battery Status
Airpods Pro 2nd Gen:
L: --% | R: 100% | C: --%
Airpods 4
L: --% | R: 89% | C: --%
Alternatives considered
Alternatively, the tray application could expand to have different circles for each device, perhaps with an icon within the center of the ring representing the different models and showing the name & battery status for just the device of the circle being hovered over -- I think this is actually a more complete solution, but it seems overkill for what is likely a mode edge-case situation.