https://bugs.kde.org/show_bug.cgi?id=502201

Jakob Petsovits <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #6 from Jakob Petsovits <[email protected]> ---
(In reply to slartibart70 from comment #5)
> systemsetting battery-settings are winning over the data provided by 'upower 
> -d'
> I'm just complaining about the misalignment.

This is true, and the reason is that UPower does not read from the battery's
own state. It gets its values from 1. an entry in "hwdb" (via system-wide
config file) for the particular hardware, or 2. if no particular entry exists,
a fallback which is the 75%-80% range that you see. UPower will apply this to
the battery, however it doesn't adopt any existing battery settings.

UPower also doesn't (currently) offer an API for desktops to customize the
system-wide settings, which is one reason why we can't yet switch to UPower by
default as a backend / source of truth for charge limits.

> (and, of course, the 'magic' systemsettings does behind the curtain: where
> is this persisted? udev-rules? sth. else?)

System Settings in its current state has no magic at all, it writes the values
straight to the battery/firmware (via kernel file interface) and hopes that
they get stored there. If the firmware doesn't persist the thresholds, System
Settings forgets everything. This is what UPower promises to solve.

I proposed a change that will give users a config file option to use UPower for
charge limits: https://invent.kde.org/plasma/powerdevil/-/merge_requests/574 -
a first step in this direction. If this is enabled, users will only have a
checkbox for optimized battery charge behavior in System Settings, instead of
configurable percentages. In return, UPower will apply battery charge
thresholds on every boot, and there won't be any misalignment obviously. For
the time being, users who opt into this can only customize thresholds via hwdb
config file.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to