nope i’ve tried that also maybe because it is not full release like 3.07 that can also be the reason
Due to an issue with the release of version 3.07 to our knowledge base, we have currently only provided the changelog detailing differences between 3.07 and 3.09. A complete changelog, covering versions 3.05 to 3.09, will be made available once this BIOS version transitions to stable.
1 Like
Yes, the condition can still be triggered. I am currently preparing a detailed explanation and will make it public as soon as it is complete.
The tag is wrong. I correct it.
2 Likes
I have updated from 3.05 via lvfs-testing using Fedora 42.
I reset my bios to defaults before the update. Everything seems to have gone ok.
I am only using battery limit at 80 as I don’t find the battery extender feature enticing for my use case.
Is there a way to check the 5% float value? Because I drained from 80 to 77% as a test then plugged back in and it charged back up to 80%.
I think the float only applies as long as it remains plugged in. If you connect a charger, it will charge to the set charge limit, but then as long as the charger remains connected, it will continue to power the laptop, but it won’t start charging the battery again until it drops 5%. At least, that is my understanding, and how it seems to work on my FW 13.
Thanks for the hint.
I ran a test this morning and it seems to be working as you said.
- Plugged in, 80%
- Stress test via s-tui
- Battery slowly drained over 30 minutes down to 78%
- Stopped stress test
- Battery remained at exact same energy level (even tough upower was reporting it was charging, it was not)
- Unplugged and Plugged USB-C charger, battery charged back up to 80%
here’s a graph of the log of battery capacity in Wh
What’s the wattage of your USB-C charger?
I am using a steamdeck dock which comes with a 45w charger. I once tried the framework charger on the dock and it did not like that at all… not sure why. You’d think it was passthrough power… but I guess they designed it with 45w chargers in mind since the steamdeck probably pulls less than 45w. (I don’t have a steamdeck)
My update to 3.09 went smoothly (from 3.08, the previous beta). I currently have battery charge limit set to 80 and have the battery extender enabled with defaults. Everything seems normal except the floating charge limit doesn’t seem to be working as described. Charging kicks back in for me when charge drops (from 80%) to 79%. Charging stops at 80%, and the cycle continues (flip-flopping b/w 79-80%).
So, the floating range-based charging is not working as described. I wonder if that works only if battery charge limit is set to 100.
5 Likes
Oh no. Don’t tell me Framework released yet another dud. You should open a ticket with support about that.
Does the float behavior work properly if you disable battery extender?
I can confirm having run this experiment for several hours, with battery extender disabled and charge limit at 80%, that the floating range is not working. The battery charge stays at 80% and Settings > Power > Battery Level shows “Charging”.
That said, I’m not even sure if the floating range is supposed to work for the scenario tested (this whole thing has gotten so complicated 
). If someone can confirm the expected outcome of the test performed, that’d be helpful.
I’ll run another test with battery extender enabled over the next few days (so the extender has an opportunity to kick in). I’ll adjust battery extender trigger and reset to 1-day and 90 minutes, respectively, to give the extender a fair shake.
1 Like
Please share your detailed procedure for the floating range test and the corresponding BIOS configurations. We want to review these, given that our team previously ran this test before release under various battery limit and extender settings (enabled/disabled).
1 Like
I wonder, why is the lower boundary fixed to 5%? What if I want to discharge my battery for more than 5%? I’d imagine a floating range of 80% to 70%, but also being able to set it in the BIOS.
Based on your steps, this should be the expected behavior because the AC charger was unplugged and replugged. If you continue running the stress test without this action, you should observe that the device doesn’t charge again until its battery level drops below 75%.
1 Like
Before the 3.09 upgrade, I had charge limit at 80% and battery extender disabled. After the upgrade, I enabled battery extender and left charge limit at 80%. I didn’t run this test long enough for the battery extender to kick in, but it showed the floating range wasn’t working. This issue was described in this comment.
Next, I kept the battery extender enabled and changed charge limit to 100%. Again, I didn’t run this test long enough for the battery extender to kick in, however it too showed the floating range didn’t work as expected.
Finally, I disabled battery extender and set charge limit back to 80%. Here too I didn’t observe the expected floating range behavior. This test was described in detail here.
Please let me know if you have any other questions or would like me to perform further tests.
Even after a few hours at your charge limit, the battery percentage may not drop unless your load exceeds the power supply’s ability to keep up. Natural, self-discharge of the battery could easily take far longer than a few hours to drop even a single percentage. It doesn’t stop charging and put load on the battery, it remains powering the laptop from the charger and the battery will only drop in charge level from the batterie’s internal, self-discharge (which is very slow on Li-Ion batteries), or if the system draw exceeds the charger’s power delivery, and it has to draw from the battery.
I think the fact that it shows “charging” is just because the charger is still connected, and the OS hasn’t commanded the charging to stop, the BIOS setting did. But the fact that the percentage wasn’t increasing is pretty good evidence that it wasn’t actually charging.
I’m not saying there is no problem, but none of the details so far provided lead me to conclude there is definitely an issue.
Someone else confirmed the float was working on their machine by using a 45 watt charger and once the battery was at the charge limit, they applied a heavy, synthetic benchmark load that resulted in the charger not keeping up, so some power had to be drawn from the battery. Once the charge level had dropped three percent, they removed the heavy load, and the battery remained at that percentage. It didn’t charge back up to their set charge limit until they disconnected and re-connected the charger.
If you simply let it sit there with the charger plugged in for a few hours, it’s very possible that the charge level wouldn’t have dropped if the system load never exceeded what the charger could supply.
3 Likes
Fair point. For background, I’ve been using the system to work on a mid-sized Python project in LazyVim, plus the usual things like Firefox with a bunch of tabs, music playing in the background, and btop etc. So, yeah, the load is pretty nominal, plus the system is plugged into an 85W docking station. If the charger is indeed powering the current use of the machine, it would explain the battery charge level staying at a constant 80%. That said, further testing (on my part) is in order.
Since I need my external displays and keyboard rn, I won’t be able to test with a lower-wattage charger just yet, but I’ll try using a lower-wattage charger on Saturday or Sunday and report back what I find.
2 Likes
Thank you for that explanation. I think you’re right, and I think the OS still saying charging might be an artifact of one of the bugs we are chasing separately in this thread: [TRACKING] Battery flipping between charging and discharging / Draws from battery even on AC
That said, support has confirmed to me that it is expected for the OS to say charging even at the top of the batt limit.
So I think so far 3.09 sounds like it’s still good? We need to be certain that batt extender+charge limit+float works.
Given the slew of reported but inconclusive test results on lack of function of the charge management behavior, I’ll contribute my success for a little balance. I’ve been using 3.09 for the last week, and both the charge limit and float range have worked properly and without fail for me so far. My heavy system load on AC power has all been application load, usually software compilation. I have the battery extender off, as it provides no benefit over my set limit.
1 Like