This is what I was expecting from Framework Team: give to the community some explanations about what is going on on their side, and eventually have some explanations about the actions that are happening under the hood.
THANK YOU @Quin_Chou for reporting back !
Please keep going on like this
The EC code to manage all the power on/off, psu plug/unplug and suspend/resume processes and the interaction when they are mixed together is actually quite complex.
This has been an issue prior to this BIOS for 140w chargers I have tried. Though I think I have read a few comments that indicated that there we some 140w chargers that didn’t make fw EC behave weirdly.
Another thing I just noticed. I launched minecraft (uses the dgpu) while on battery and my normally operating system dropped down to the 500MHz issue. echoing “on” to the above fixes it again, and then i can echo back to “auto” and it remains fine.
So this is triggered without any external power connection just by launching a game that turns on the dgpu.
Just another data point on this issue that may hopefully help resolve it.
Here is another strange state it will get in with this 3.06 bios. Seems a little more rare though. It will charge up to 99%, never get to 100%, and then eventually stop charging completely. It will then run on battery until dead. No amount of sleeping/waking/plugging/unplugging the charger will get it out of this state. My battery is reported by the OS to be at 57% lifetime health as well, which seems ridiculous as it was high 90’s before this bios update.
Power down completely and it still will not charge. (second video)
Once it runs completely down and will no longer power on, it will start working normally again and start charging. I had brought it into the bios and was just sitting there when it forced off likely due to the battery reaching 0%. Then it started charging again.
You can see in the first video that it refuses to charge and, in fact, causes the laptop to actually WAKE up when the charger is disconnected/connected. None of this should ever happen. The green is amps and blue is watts on that usb power display which you see remain at 0 because it will not charge.
What is the current go / no go for this BIOS update? Should We let it bake a little bit more?
I’ve been having USB issues on Windows 24H2 that are reminiscent of an x570 bug from back in the day that was fixed via new AGESA firmware update. Considering updating, but not sure how widespread this 540MHz issue is. I have the 64GB dGPU version use a Pluggable TBT4-UDZ dock.
Framework 16 beta BIOS 3.06 is required (BETA) → BIOS
Here’s a link to the actual app: Framework Control
Need to install a lightweight Rust service to be able to use it. Link provided in the APP
All code belongs to me and is open. If paranoid, you can build the service from source (steps in the repo)
Windows, 64GB ram, dGPU, and 180W charger. Most of the time it’s on a 96W dock (Pluggable TBT4-UDZ) . I’ll sometimes play games when I’m at a friend’s house
That is a really cool way to implement the control app. A positive I can think of is its gonna be super easy to update and such but the internet requirement is kinda iffy.
Let me know if you run into any trouble running it. The beta BIOS is a hard requirement but the cli will be installed by the service automatically if not present.
As it stands currently. To be able to complete the package, we really need some sort of TDP control, maybe even a temp limit. I have no idea how difficult that is to land but will do my best…
Should probably clarify since reading it back it sound like it needs an online connection to work.
The iffy part is since its a online site, if the user does not have a internet connection, they can’t change their settings. I’m not sure if Firefox or chrome on desktop has site caching but that would have probably solved the problem.
You make a valid point. I’ll try to bump the priority on the offline support. Need to think about an update strategy as well.
Currently, the tool is just for me to control my own fans and configure them. If it starts getting more traction, I’ll update as I go, paying attention to the community feedback.