Battery limit setting not working anymore

Fedora 44

CPU Ai9 HX 370

I have 2 hard drives and each have their own OS. Primary runs Fedora 44 KDE and secondary runs Windows 11 Pro (only used if no other options).

I have been using Framework_tool to adjust the battery charge limit which has been working flawless. It normally sits at 60% SOC and today I set it to 90% SOC as I had to do some outside work.

Having to use Win 11 and after finishing, I set it back to 60% SOC, but the Laptop kept charging further.

Shut it down and booted into the BIOS and it was showing 60 limit. Overrode it setting it to 60% SOC again..saved and the Laptop is now ignoring the Charge Limit settings.

It now charges to 100% no matter what I do.

Anybody got some ideas ?

This is due to a bug in the EC firmware where the setting in the BIOS mismatches the setting in the EC.
An EC reset will fix the problem.

  1. power off laptop. (Not standby)
  2. remove power adapter.
  3. wait 120 seconds. (The EC stays powered for a while even with the power adapter unplugged. This wait ensures the EC powers off also)
  4. plug power adapter in
  5. power on laptop.
1 Like

In my case the fix was different.

Setting not working: Setting changed to 60% after it was set to 90% via Framework tool.

SOC at that stage was above 83%, so above the SOC 60% setting when hooked back onto the Charger.

Even resetting it in the BIOS directly did not fix this.

Result: Battery kept charging up to 100%.

Fix (in my case): Discharged battery to 49% then connected back onto the charger.

Result: Battery now charging back to 60% only as per setting.

so I tried this, but even though I have it set to 80%, it’s still charging to 100%. Does this reset always fix it, or maybe there’s something else I can try?

Make sure that you discharge the battery below your set 80%. If the battery is above the set SOC then it won’t work anyway. It needs to be lower then your setting.

yeah, I tried that too, but it charged up past the set value

do I maybe have to get it below 80%, then power off for 120 seconds to reset EC, then plug in and power on?

Recent version of Bazzite (KDE) broke that too. Since Bazzite is kind of a downstream fork of Fedora Silverblue/Kinoite, that may be relevant to your case.

An alleged UniversalBlue dev recently told us this:

oh thanks for the info! I much prefer this being a Bazzite thing than yet another firmware bug :joy: I just updated my BIOS to latest, so I wasn’t sure if I was seeing a bios bug or if rebooting just bumped me to the latest Bazzite too. Sounds like it’s mostly a coincidence though. Thanks! o7

1 Like

I’m also on KDE Bazzite and having the same problem for the last few days.