Hey,
my battery always charges up to 100% and my bios setting with 80% charging limit is ignored. Someone else have this issues?
Regards
Canât help, but you should provide the BIOS version youâre running 
Update to the latest version: Framework Laptop 13 Ryzen 7040 BIOS 3.09 Release
Disable the battery extender in the bios.
Power off laptop (not suspend).
Wait 2 mins. And power on.
This resets the EC.
If you wish to use the battery limit of 80%, you donât need the battery extender function as that is for protecting a 100% charged battery.
Its the new Ryzen 9 HX 370
Sorry there is only the release bios for the Ryzen AI yet
Sorry maybe thats got lost, I donât talk about battery extender, I talk about charging limit
Currently thatâs my configuration
I had it setup exactly like that for my old 7040 Mainboard and thwt configuration never charged more then 80%
And battery extender can mess with the charge limit (or at least id did on the 7x40u).
2 Likes
Ok, that is good that you have âBattery Extenderâ disabled.
The EC code has some bugs in it, that under some situations, it escapes its 80% limit.
When that happens, you can discharge it back to below 80% and it probably will not hit the edge case again for a while.
In any case, going through the EC reset I described should help.
I have written my own bug fixes to the EC code, but it only works on FW13 AMD 7840U, 7640U and FW16 AMD 7840HS. So, they wonât work on your AI 370.
Itâs a known issue as described here : F13 AMD AI 300 - Battery charge limit ignored on subsequent boots ¡ Issue #67 ¡ FrameworkComputer/SoftwareFirmwareIssueTracker ¡ GitHub
framework released a laptop with a buggy bios. We have to wait for them to merge the fix from 7040.
The only bios available for AI 300 now is the 0.3.3 which is can not be suitable for production systems.
Okay I did the following, restart into bios, set charging limit to 100, powered down for 10 minutes, now I booted the machine, set charging limit to 80, now I booted up the os and will wait for the battery to drain under 80
My pre-built 370 exhibits consistent behavior: Battery limit set to 80%. When shutdown and charger cable is plugged in, it will exceed 80%. When running W11 and the charger cable is plugged in, it will maintain 80% charge, running or sleeping (lid shut).I havenât tried hibernate.
Looks like a bug in the firmware with my 7840u Board I never had this issuesâŚ
Thanks for catching the LVFS record, a touch concerned by itâŚ
Iâm facing the exact same issue on my HX 370.
Setting charge limit using @DHowettâs ectool at system boot is my current workaround:
sudo ectool chargecontrol normal 80 80
1 Like
I am also on the new Framework Laptop 13 (AMD Ryzen AI 300 Series)/FRANMGCP09, BIOS 03.04 06/10/2025 and Omarchy Arch Linux version 6.16.3-arch1-1.
So, it used to work very well and the battery limit was respected (even with Extender enabled). Yet, since some time, I realized it does not work anymore and it charges to 100%.
I followed the steps to reset EC and after waiting 2 mins it seems to pick it up initially, i.e. after 2 mins before tuning the laptop on I plug in the adapter and I see the LED changing color from orange to white - which used to be the case when the battery reached the limit set in BIOS. But then, when I turn the laptop on, soon after typing the password to decrypt the SSD, the LED changes to orange again and then it stays like this, until I reset the EC again by powering off, disconnecting the adapter and waiting 2mins. But then the process repeats. So I am wondering if this is still problem of BIOS or there is something with my (Omarchy) Arch LinuxâŚ
Omarchy uses power-profiles-daemon, and i do not see anything strange there⌠At least I did not see any conflicts beforeâŚ
dmsg only gives me this when searching for battery:
``bash
⯠sudo dmesg -T | grep âbatteryâ
[Thu Aug 28 04:11:54 2025] ACPI: battery: Slot [BAT1] (battery present)
[Thu Aug 28 04:12:18 2025] ACPI: battery: new hook: cros-charge-control.6.auto
```
Thanks for any feedbackâŚ
I found the problem.
With recent kernel cros_charge_control seem to be functioning (which means btw that it should be possible to use tlp to control the battery). But even if you do not, the BIOS settings on new FW13 with AI 9 HX 370 to limit charge level will not be respected because they will be conflicting with cros_charge_control. I found it by tracking down the boot logs. At some point I saw this:
journalctl -b -13 | grep battery
Aug 23 02:41:09 f13-ep-0 kernel: ACPI: battery: Slot [BAT1] (battery present)
Aug 23 02:41:09 f13-ep-0 kernel: ACPI: battery: new hook: cros-charge-control.6.auto
And then the threshold files finally appear:
lsmod | grep cros
leds_cros_ec 12288 0
gpio_cros_ec 12288 0
led_class_multicolor 16384 1 leds_cros_ec
cros_kbd_led_backlight 12288 0
cros_ec_sysfs 16384 0
cros_charge_control 16384 0
cros_ec_debugfs 20480 0
cros_ec_chardev 16384 0
cros_ec_hwmon 12288 0
cros_ec_dev 20480 0
cros_ec_lpcs 28672 0
cros_ec 20480 1 cros_ec_lpcs
cros_ec_proto 61440 11 leds_cros_ec,cros_ec_lpcs,cros_kbd_led_backlight,cros_ec,gpio_cros_ec,cros_ec_dev,cros_ec_debugfs,cros_ec_hwmon,cros_ec_sysfs,cros_ec_chardev,cros_charge_control
~
⯠cat /sys/class/power_supply/BAT1/uevent | grep CHARGE
POWER_SUPPLY_CHARGE_FULL_DESIGN=3915000
POWER_SUPPLY_CHARGE_FULL=4014000
POWER_SUPPLY_CHARGE_NOW=2778000
POWER_SUPPLY_CHARGE_CONTROL_START_THRESHOLD=0
POWER_SUPPLY_CHARGE_CONTROL_END_THRESHOLD=100
POWER_SUPPLY_CHARGE_BEHAVIOUR=auto
To get the BIOS working correctly you need to blacklist:
$ cat /etc/modprobe.d/blacklist-cros.conf
blacklist cros_charge_control
$ sudo mkinitcpio -P
This will remove the conflict and let the BIOS control the charging.