https://bugs.kde.org/show_bug.cgi?id=445965
John <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from John <[email protected]> --- (In reply to Rafael from comment #4) > So in summary, we'd have two or three charging profiles: > - battery longevity > - max charge, once off (goes back to longevity once plugged) > - max charge, continuous (doesn't switch to battery longevity) This seems like the ideal case - I often want to "boost charge" the computer - sometimes only with a few minutes notice. E.g. I get called out to a site from the office. Flipping to "full charge" mode for a few minutes to fill the battery would be convenient. In this case (max charge one off) is appropriate. However, sometimes I'm in an environment where I want to charge to 100% always, like when travelling and the next access to power is uncertain. So even when you get AC, you don't want to reset to battery-longevity mode. You could imagine a fourth mode: full charge until power restored for X hours (a simple "smart" way to handle a part of https://bugs.kde.org/show_bug.cgi?id=443761, perhaps) In either case, clicking though to the settings and fiddling with them is a bit annoying and easy to forget to restore. A fully-featured UI for this might be: - List of modes (e.g. the set of three/four above) - Each mode has: - Two threshold values - The mode to return to when the AC power is next restored, or "stay in this mode forever" - the timeout for the mode change if one is set Alternatively, keep it simpler and have it more like: - Battery longevity mode thresholds - Battery full charge thresholds - Optional timeout value for going back to longevity mode - Mode: - longevity always - full charge once and back to longevity on next power after timeout - full charge always -- You are receiving this mail because: You are watching all bug changes.
