You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Battery block is missing the ability to blacklist battery percentage sources in battery block.
I say this because of problem I recently encountered:
I got a new Dell keyboard/mouse, which is actually manufactured by Logitech, and implements some kind of HID device that that should report the battery status of both keyboard and mouse.
Apart from the fact that those values are not related to the laptop battery, and they are thrown into the overall calculation, they don't really seem to work on my keyboard/mouse and are reporting zero values.
This causes of course, a weird battery level on my i3-bar.
lsusb for reference:
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Values that acpi reports:
Battery 0: Discharging, 0%, rate information unavailable
Battery 1: Full, 100%
Battery 2: Discharging, 0%, rate information unavailable
I'd try to implement such a feature myself, but it seems this will require a change in the way the battery block queries the battery percentage currently, and I'm not sure which way this should go, thus I'd like to open this up for conversation.
The text was updated successfully, but these errors were encountered:
Battery block is missing the ability to blacklist battery percentage sources in battery block.
I say this because of problem I recently encountered:
I got a new Dell keyboard/mouse, which is actually manufactured by Logitech, and implements some kind of HID device that that should report the battery status of both keyboard and mouse.
Apart from the fact that those values are not related to the laptop battery, and they are thrown into the overall calculation, they don't really seem to work on my keyboard/mouse and are reporting zero values.
This causes of course, a weird battery level on my i3-bar.
lsusb for reference:
Values that acpi reports:
ls /sys/class/power_supply
upower -e
I'd try to implement such a feature myself, but it seems this will require a change in the way the battery block queries the battery percentage currently, and I'm not sure which way this should go, thus I'd like to open this up for conversation.
The text was updated successfully, but these errors were encountered: