Did you specify the correct location of the cab file? How did you download the cab file? What BIOS are you currently on?
I downloaded it directly via the link you provided above (with Firefox). I did specify the entire path to the cab file on the command line. I am on version 3.08 currently.
Did you try an absolute path? Is the cab file perhaps corrupted? I donāt know what else to tell you.. Perhaps an SELinux issue? checked the logs? Perhaps wait for the official release?
I tried redownloading it twice, and I did try an absolute path. SELinux not enabled on my laptop.
I updated from 3.0.7 to 3.0.9. That is the only difference i can see so far. Furthermore, there appears to be a unusual low success rate reported by LVFS for this version.
Why is this not tagged bios-announcement like 3.08 was???
Most likely a typo as itās tagged with bios instead.
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.
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.
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.
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.
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.
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).
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.
