https://bugs.kde.org/show_bug.cgi?id=473281
--- Comment #6 from andretia...@protonmail.com ---
(In reply to Nate Graham from comment #5)
> Indeed, we do. In powerdevil/daemon/chargethresholdhelper.cpp:
>
> if (threshold < 0 || threshold > 100) {
> qWarning() << file.fileName() << "contains invalid threshold" <<
> threshold;
> continue;
> }
>
> The question now is whether these negative threshold numbers are valid and
> we should adjust our code to be more lenient, or whether they're invalid and
> this needs to be reported to the kernel folks.
Yeah that's what i ended up discovering too :)
After doing some experimenting I found out that after using the following
commands:
echo 60 | sudo tee /sys/class/power_supply/BAT1/charge_control_end_threshold
echo 50 | sudo tee /sys/class/power_supply/BAT1/charge_control_end_threshold
The battery thresholds appear in advanced power settings!
I then did a EC reset on my laptop and tried again, then I used the command:
/sys/devices/ | grep charge_ | xargs tail -n
> +1 and it showed those -138 and -128 values again, also the battery
> thresholds disappeared again in advanced power settings.
--
You are receiving this mail because:
You are watching all bug changes.
