# Framework Laptop 13 Ryzen 7040 BIOS 3.08 Release BETA - Held **URL:** \ **Category:** Framework Laptop 13\ **Tags:** bios-announcement, amd-7040\ **Created:** [March 31, 2025, 2:14pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858 "2025-03-31T14:14:01Z")\ **Posts on this page:** 11\ **Page:** 8
**Author:** ![Xal](https://avatars.discourse-cdn.com/v4/letter/x/b5a626/32.png) [@Xal](https://community.frame.work/u/Xal)\ **Post date:** [April 23, 2025, 4:58pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/155 "2025-04-23T16:58:32Z")
Well I dont use the battery features much. but I have to add that the fan sensors are reporting wrong info. (Using aurora, they report they are going full blast all the time even when no noise). Installed the update due to the security fixes. ---
**Author:** ![Will\_Nilges](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/will_nilges/32/23820_2.png) [@Will\_Nilges](https://community.frame.work/u/Will_Nilges)\ **Post date:** [April 28, 2025, 12:53pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/156 "2025-04-28T12:53:51Z")
I talked to support about the flipping issues the other week, and they recommended I install 3.08 (once it is fully released) to fix it. From the original post, they have updated the charge limit logic to prevent micro cycles. > As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on. Is that what you are describing? (It would be really nice if they’d open source the 3.08 EC firmware so we could see what they were doing) Also, anyone following this thread using 3.08, can you confirm that this is now the behavior on charger under load? ---
**Author:** ![Will\_Nilges](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/will_nilges/32/23820_2.png) [@Will\_Nilges](https://community.frame.work/u/Will_Nilges)\ **Post date:** [April 30, 2025, 12:16pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/157 "2025-04-30T12:16:14Z")
@Quin_Chou It’s been about a month since this BIOS was released. When can we expect an update on next steps? ---
**Author:** ![0xc0ffee](https://avatars.discourse-cdn.com/v4/letter/0/c77e96/32.png) [@0xc0ffee](https://community.frame.work/u/0xc0ffee)\ **Post date:** [April 30, 2025, 2:05pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/158 "2025-04-30T14:05:46Z")
Come December we might actually get a proper stable BIOS update… I will also add that fwupdmgr continues to want to upgrade to the now pulled 3.07 BIOS, including after `fwupdmgr refresh --force`. Unless this is an issue due to some weird cache behaviour, can FW please pull the broken update from LVFS so that people don’t accidentally upgrade to a BIOS version that has been officially withdrawn? Edit: Yes, one can permanently mark the update as “to be ignored” with `fwupdmgr block-firmware ` where `` comes from the “Checksum” property in the summary of the update ( `fwupdmgr get-updates`). But that’s not the point, if it has been marked as “held” it should also have been pulled from LVFS. ---
**Author:** ![Richard\_Lee1](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@Richard\_Lee1](https://community.frame.work/u/Richard_Lee1)\ **Post date:** [April 30, 2025, 3:30pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/159 "2025-04-30T15:30:13Z")
> [@0xc0ffee](#): > > Come December we might actually get a proper stable BIOS update… December of what year, though? ---
**Author:** ![0xc0ffee](https://avatars.discourse-cdn.com/v4/letter/0/c77e96/32.png) [@0xc0ffee](https://community.frame.work/u/0xc0ffee)\ **Post date:** [April 30, 2025, 6:29pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/160 "2025-04-30T18:29:35Z")
> [@Richard\_Lee1](#): > > December of what year, though? Whichever comes out of the random number generator 😐 ---
**Author:** ![Will\_Nilges](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/will_nilges/32/23820_2.png) [@Will\_Nilges](https://community.frame.work/u/Will_Nilges)\ **Post date:** [May 1, 2025, 2:19pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/161 "2025-05-01T14:19:50Z")
I reached out to Framework support through the ticket I have open about the battery flipping. > Currently we are not able to provide further details of the exact ETA of the proper stable BIOS update. When I asked if it would be weeks or months: > As much as we want to provide how many weeks, months it will take to release the BIOS update however, we still don’t have any update yet. > Please be advised that we are always trying our best to deploy the latest BIOS updates as soon as possible for our customers who are experiencing issues with the current BIOS. And to the employees that (I really, really hope) are watching this thread, yes, I know that there’s no way support has access to these details, but I have a broken $1400 laptop and two courses of action for trying to get it fixed. 1. Support (see above for how that went) 2. Community forums (well, you read this thread 🙃 ) By the way, it’s May now. ---
**Author:** ![DrFosterGloucester](https://avatars.discourse-cdn.com/v4/letter/d/f17d59/32.png) [@DrFosterGloucester](https://community.frame.work/u/DrFosterGloucester)\ **Post date:** [May 1, 2025, 4:32pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/162 "2025-05-01T16:32:25Z")
As much as I want to love this company, and I have a laptop and am invested, you really can’t be selling laptops at $1000+ and then giving out multiple broken BIOS updates and going, so far, up to 5 months without a fix. We can do better. Surely. ---
**Author:** ![Rei](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rei/32/13593_2.png) [@Rei](https://community.frame.work/u/Rei)\ **Post date:** [May 2, 2025, 10:30am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/163 "2025-05-02T10:30:23Z")
> [@Framework Laptop 13 Ryzen 7040 BIOS 3.09 Release](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release-beta/68601/): > > NOTE: Once you update to 3.09, you cannot downgrade to 3.05 or the version earlier than 3.05. Highlights Please note this #1~#6 are copied from 3.07. Delta is 3.05-\>3.09. Fixes for battery extender functionality introduced in 3.06. Modified the charge limit functionality to allow a 5% float range on the battery. Fixed 5 security vulnerabilities. Fixed ALS sensor communication failures. Fixed IRQ1 wake issues on Linux. Fixed diagnostic compatibility issue with 2.8K displays. Fixed the battery… it arrives 🙂 ---
**Author:** ![TheTRUEAsian](https://avatars.discourse-cdn.com/v4/letter/t/da6949/32.png) [@TheTRUEAsian](https://community.frame.work/u/TheTRUEAsian)\ **Post date:** [May 2, 2025, 2:48pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/164 "2025-05-02T14:48:36Z")
This post is being locked as the 3.09 BETA is now available. [Framework Laptop 13 Ryzen 7040 BIOS 3.09 Release BETA](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-09-release-beta/68601) ---
**Author:** ![TheTRUEAsian](https://avatars.discourse-cdn.com/v4/letter/t/da6949/32.png) [@TheTRUEAsian](https://community.frame.work/u/TheTRUEAsian)\ **Post date:** [May 2, 2025, 2:48pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858/165 "2025-05-02T14:48:39Z")
[Previous page](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-08-release-beta-held/66858.md?page=7)