From be71a8c8b94983319d6f5af50ce80c0bc1315735 Mon Sep 17 00:00:00 2001 From: Bennet Yee Date: Wed, 1 Apr 2026 16:31:54 -0700 Subject: [PATCH 1/2] Update laptop-battery-thresholds.md The firmware has been updated since Nov 2024 to save the threshold values to flash. --- content/laptop-battery-thresholds.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/laptop-battery-thresholds.md b/content/laptop-battery-thresholds.md index cb1ebbc445..f22d2be89c 100644 --- a/content/laptop-battery-thresholds.md +++ b/content/laptop-battery-thresholds.md @@ -74,6 +74,12 @@ The thresholds can be controlled by reading from and writing to these sysfs file ### At boot +The current version of open firmware should persist the threshold values in flash. +If changes to your system's charge thresholds do not persist across reboots, +you should update your firmware. + +If you cannot update your firmware, you can use the instructions below as a workaround. + To work around the limitation in open firmware causing the thresholds to be reset when the system is shut down and unplugged, you can set the thresholds at boot via systemd. To do so, create a file called `/etc/systemd/system/charge-thresholds.service` with the following contents: From d19db76c6a286258da144a0f35f83db3f31dc6cd Mon Sep 17 00:00:00 2001 From: Jacob Kauffmann Date: Thu, 2 Apr 2026 16:52:03 -0600 Subject: [PATCH 2/2] Simplify wording & remove additional mention of limitation --- content/laptop-battery-thresholds.md | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-) diff --git a/content/laptop-battery-thresholds.md b/content/laptop-battery-thresholds.md index f22d2be89c..684fe7e468 100644 --- a/content/laptop-battery-thresholds.md +++ b/content/laptop-battery-thresholds.md @@ -33,8 +33,6 @@ To determine if your laptop has Open Firmware or proprietary firmware, see [this ## Configuring Charging Thresholds (Open Firmware) -**Note:** This feature is not currently finished. Currently, the thresholds are reset when the EC is reset (which happens when the system is shut down and the power is unplugged). Once the feature is complete, the thresholds will be persistent and a GUI will be available to set them. To work around this limitation in the short term, you can [use systemd to set thresholds at boot](#at-boot). - ### Using the terminal You can see the thresholds that are currently set using this command: @@ -74,15 +72,12 @@ The thresholds can be controlled by reading from and writing to these sysfs file ### At boot -The current version of open firmware should persist the threshold values in flash. -If changes to your system's charge thresholds do not persist across reboots, -you should update your firmware. - -If you cannot update your firmware, you can use the instructions below as a workaround. +Open Firmware versions dated 2025-02-04 and later save the charging thresholds automatically. +As a result, this "at boot" workaround is no longer needed. -To work around the limitation in open firmware causing the thresholds to be reset when the system -is shut down and unplugged, you can set the thresholds at boot via systemd. To do so, create a file called -`/etc/systemd/system/charge-thresholds.service` with the following contents: +Earlier versions of firmware lost their configured thresholds when the system was shut down and unplugged. +To work around this limitation in earlier firmware versions, you can set the thresholds at boot via systemd. +To do so, create a file called `/etc/systemd/system/charge-thresholds.service` with the following contents: ``` [Unit]