Is there an ETA of when the 3.08 bios will be released?
6 Likes
I think if the estimate time of arrival for the patch from Insyde is still not clear, Framework can release the current BIOS 3.08 officially without the Insyde’s patch, and can release the BIOS 3.09 including the Insyde patch in near future. Because users above already reported BIOS 3.08 improves the battery performance and it also looks stable. If Framework releases it now, I think more users can start to verify the battery life. This is good for all the Framework Laptop users who currently have challenges for the battery life.
Another concern for the new BIOS 3.08 + Insyde patch is, if there is another critical issue coming from the Insyde patch itself, like 3.06, the benefit of the improved battery life in 3.08 is gone.
5 Likes
I’d agree with this too. If the current version of 3.08 resolves the issue with high battery drain while in sleep mode, releasing it might help quite a few user’s issues in that regard. Then when Insyde releases their patch for CVE, then a 3.09 could be released.
1 Like
3.08 resolves drain during off/hibernate, not sleep.
1 Like
That’s right, what I actually meant. I’ve been seeing the high drain while off.
I took the risk and Alpha’d the 3.08 Bios, got a scare at first when I booted into Windows 11, the voltage stayed max and even the fan ran at full speed to try and cool the cores that stayed in the 90’s hitting 100 on occasion, Not sure why it didn’t throttle!
So I immediately shut it down… but when I booted into Windows 11 again (after the case cooled down), everything was back to normal and running fine, only maxed the voltage when hard workload was put on it but managed to throttle itself every time it got into 90s.
I use the laptop as my daily driver so I can really say if it’s using battery or not when off… always seems where I left it when I pull it out of my bag and turn it back so yeah.
Testing Fine so far on Windows 10 Pro (21H2) 19044.1682 and Windows 11 Pro (21H2) 22000.652.
Edit* I also have Windows 11 Pro (22H2 Beta) 22610.1 running in a VM and it works fine but that isn’t the same as running it on the hardware itself 
I turned off my laptop (after charging it to 96%) and put it in my bag about 4.5 hours ago, I just pulled it out and turned it on and it’s still at 96%… I know that isn’t that long but it’s a good sign yes?
14 Likes
Hmm, sad that they still haven’t finished 21 days later. Hopefully you all manage to find some firmware engineers soon! 
I noticed you were looking for them.
If waiting on patches from Insyde is the only thing holding up release of 3.08 (no showstopping bugs), then I agree with releasing it now and putting out 3.09 whenever Insyde turns the code outside!
Or is the deleting boot entries problem still persisting in 3.08?
This is their address: 16F., No.120, Sec.2, Jianguo N. Rd., Zhongshan District. Taipei, Taiwan, R. O. C.
Feel free to send them my best wishes as well.
*Joke
1 Like
Still no news on this from Framework, nor Insyde?
4 Likes
Yeah, how about throwing us a bone, guys! I mean, months after a beta version leaks not even a word about when we might expect this? Or if things aren’t going well how about just an explanation about what’s going on?
3 Likes
Yes…
Wait, no. News = good, good = sated, sate = not want more. At least for reasonable people that is!
2 Likes
This is quite something… The CVEs were released publicly more than 3 months ago…and still no fixes. If this were Lenovo, Dell, or HP… certain environment would have failed these devices security audit.
(i.e. Conceptually, there’s this subjective time period where you’re still ‘ok’ with know CVE exposure…but the more time passes, the more likely that you’re exposed)
2 Likes
This is a good point. If the reason the BIOS release is delayed is because they need to usher in a patch for a security vulnerability, it would seem like there should be more of a sense of urgency to getting the update finalized.
The fact that the rest of the code is sitting around more or less finished but we’re waiting on an “urgent” security patch that is for some reason taking months…well, I just feel like I must be missing something… 
1 Like
From bad RAM module , to a bad motherboard and now what is essentially a new version of the DIY laptop I bought batch 2 all using Windows 10.
I have gone from 3.02 originally to the replacement motherboard which is 3.0. I have held off on all the BIOS updates as I saw the various problems with all the incremental updates in the hope that some day a 3.08 would go legal. As everyone here as said, 3 months and counting.
It has been an interesting experiment, buying this Framework laptop.
I have to agree with the sentiments here, new features/fixes are great to have but security vulnerabilities are a far higher priority and 3 months is too long.
This needs to be addressed.
3 Likes
Just upgrade to 3.07 lol, it’s basically completely stable.
1 Like
Yup, definetly. Although I can’t bring myself to blame Framework considering Insyde is the one making it take so long.
2 Likes