https://bugs.kde.org/show_bug.cgi?id=523648
Jakob Petsovits <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|[email protected] |[email protected] CC| |[email protected], | |[email protected], | |[email protected] Target Milestone|1.0 |--- Component|Power and Battery widget |general Version First|6.7.3 |unspecified Reported In| | Product|plasmashell |neon --- Comment #4 from Jakob Petsovits <[email protected]> --- Thanks. Going by these numbers, your system would only start charging below 20% capacity and then stop charging when it's at or above 20%. This is what the kernel tells us, so Plasma can't do much about the number that gets shown. So this means it's a bug on a lower level; perhaps a firmware bug, but it's possible that the kernel can work around it with a fix. Generally this should be reported to the kernel bugzilla. But the kernel bugzilla says that only bugs for upstream kernels should be reported, so in your case the report should go to KDE neon. Which is also handled on the KDE Bugzilla here. But it uses an Ubuntu kernel. It's a bit of a maze. Not your fault, sorry about the bug bureaucracy. I'll assign this to neon for now; hopefully it can be forwarded to the right kernel people with you included? --- As extra info, people will probably need more information about your actual laptop model, ideally with firmware ("BIOS") version. It would also be interesting to see how the shown numbers behave if you only set one of the two values (*) at a time. You can play around with this by writing numbers directly to these files without Plasma: sudo bash -c 'echo 80 > /sys/class/power_supply/BAT0/charge_control_end_threshold' Try setting the end threshold first, then check if any of the printed numbers (`cat` command from earlier) change. Then do the same thing with the start threshold: sudo bash -c 'echo 25 > /sys/class/power_supply/BAT0/charge_control_start_threshold' This might give the kernel people some idea about how things are going wrong exactly. (*) `charge_control_end_threshold` and `charge_stop_threshold` is always the same (they show the same kernel value) just like `charge_control_start_threshold` and `charge_start_threshold` is always the same. They introduced the `charge_control_*` names later for better consistency, but kept the old names around because the Linux kernel doesn't remove existing interfaces as long as they are used by anyone. --- The reason that PowerDevil shows 50% instead of 20% is that the number field has a lower bound of 50. Because it makes no sense for a user to charge the laptop up to less than 50%. (At 60% full, a lithium-ion battery already keeps incredibly well, no reason to go below that for a maximum value.) I guess I could make the field have a lower bound of the currently stored value and 50%, in order to show the right thing while still providing a practical selection range in general. -- You are receiving this mail because: You are watching all bug changes.
