Automatically handle charge thresholds for Thinkpad laptops?
As a user, I would like my system (in my case, Fedora Workstation) to do whatever it needs to prolong the life of my battery in the long term. On https://www.thinkwiki.org/wiki/Maintenance#Battery_treatment it is mentioned that it is preferrable to have batteries not charge to 100%, and to keep it between 30 and 85 (or I guess 95) percent charge. I've heard something about avoiding charging when the battery is not discharged enough to warrant doing a charge cycle.
There seemed to be tp_smapi, then TLP, or probably a bunch of things and the advice and documentation is scattered and confusing. For example:
- https://www.reddit.com/r/thinkpad/comments/30dbsv/x220_battery_maintenance_setting_upper_and_lower/
- https://www.reddit.com/r/MatebookXPro/comments/9iakhu/battery_charge_thresholds_on_linux/
- https://www.reddit.com/r/thinkpad/comments/bisse4/limit_charging_of_my_t480s_internal_battery_when/
- https://www.reddit.com/r/linux4noobs/comments/5yf6jp/limiting_battery_charge_in_linux/
And when I think "TLP" is probably the "correct" solution (is it?), and therefore look at https://linrunner.de/tlp/faq/battery.html and have to crawl through a bunch of other doc pages and see that it needs some manual systemd config (I think) I find myself thinking "why is this, why can't the OS just figure that out for me by default? I just want to use my computer, or my aunt to use her Thinkpad without having a CS degree."
So I'm thinking it would be nice if our freedesktop system stack can just handle it for me, across distros. And/or maybe having an option in GNOME Control Center's energy settings to control the lower charging threshold (i.e. how aggressive you want to be in the "battery life expectancy vs always-ready-to-go" tradeoff).
I'm hoping this is the right place to file this request, because I have no idea where to ask otherwise, I wouldn't know where to file it in RH Bugzilla for Fedora (and suspect it would die in obscurity there) and I'd prefer a cross-distro standard middleware solution rather than downstream-specific behavior.