Power: Confusing battery level reported for laptops with a touchscreen / digitizer (Wacom AES)
The battery level reported in the Power panel is currently quite confusing as a user on a Dell Latitude 7275 with its Wacom AES digitizer and an HP Active Pen G2. I'm not quite sure if this is device-specific and if this can be improved on the GNOME side, but here is my user experience with GNOME 40.4 on Debian:
1/ The Power panel exposes a 0% battery level by default after boot when no stylus pen is in proximity (or simply if the user has no stylus at all) => it shouldn't display anything at this stage in my opinion, this is very disturbing to have a device with "0% battery" reported corresponding to no actual peripheral
2/ The AES sensor exposes the stylus battery level when one is in proximity. The Power panel will then display the last known battery level (let's say 25%) as a fixed value for as long as no stylus is in proximity and until the next reboot (when it will default back to 0% again, cf. 1/ above). => why not, let's say this is the last known battery level. Possible improvement: could there be a timer to display this battery-level information only for a certain amount of time, when the stylus has been used recently?
3/ The above battery level is linked to a device named "Wacom HID 4804" on my Dell laptop, not obvious for a user that this is the actual battery level of a stylus recently used with its screen digitizer => could there be a way to report the name of the recently used stylus instead? => or something generic like "Dell Latitude 7275 (Wacom) stylus"?
4/ A connected Bluetooth stylus (such as an HP Active Pen G2 in my case) will appear with its own line in the Power settings too, somehow duplicating the "Wacom HID 4804" one => could there be a way to merge the two lines into one in this case?
5/ The battery level reported by the "HP Active Pen G2" line is erroneously stuck at 100% => not sure yet if this stylus model can report its battery level on its own via Bluetooth
This is an overall feedback, it certainly contains several independent issues, let me know if it would be useful to open a few separate issues. Feel free to point me to open some issue into different open source projects.
Thanks a lot, Jérôme