glibc 2.43 now ships with an actual en_SE locale. Having this link will
now conflict with the package provided file.
This new, actual en_SE locale mostly works for our LC_TIME purposes.
Unlike en_DK, it uses numerical offsets for timezones (which I'm ok
with) and does not include any separator between the seconds and the
timezone (which I'm less ok with).
So instead of en_DK:
d_t_fmt "%Y-%m-%dT%T %Z"
Now we have actual en_SE:
d_t_fmt "%Y-%m-%dT%T%:z"
I'll live with it. I'm willing to put up with much to get sane ISO8601
YYYY-MM-DD date formatting in my browser.
https://lists.gnu.org/archive/html/info-gnu/2026-01/msg00005.htmlhttps://pig-monkey.com/2024/02/things-i-do-for-time/
When I first bought my Framework, the battery charge limit reset after
every boot, necessitating something like this. With later firmware
versions, it doesn't reset, so there's no need for a service. Just set
your preferred limit once, using whatever method you like, and then
forget about it.
The only thing I use either of these for is setting the charge limit.
Both seem to work identically. I've been using framework-system for a
month or so and haven't noticed any difference.
If you set a charging threshold on the battery, you may bounce between
charging and discharging while still on AC. The profile only needs to
change when AC is disconnected. If the battery is discharging, but AC is
connected, don't switch to a power-saving profile.
I think.
Apparently changes made via ectool only survive power off if the laptop
remains plugged in, so in practice we have to set this on every boot.
https://wiki.archlinux.org/title/Framework_Laptop_13#Battery_control
Setting the lower and upper charge percentage to the same value causes
the controller to idle the battery at that percentage. This seems like
it would be better for the long term health of the battery than giving
the battery a range to constantly dis/charge between. It also feels more
like what I'm used to from all my years of Thinkpads and TLP.
I have also set the max charge on my battery to 90% in the BIOS, as per:
https://guides.frame.work/Guide/Enabling+Battery+Saver+Functionality+in+BIOS/392
I'm not sure if a looping script like this is the best way to accomplish
this. I don't understand why TuneD doesn't provide this functionality
itself, like TLP does.
