I have looked at the forum posts, but haven’t found anything similar yet.
My framework was siting on a small desk on the Table (plain surface, so nothing blocked the Vents any way), connected over USB4 to a 65 Watt docking station. Apparently i forgot to shut it down in the evening, because as i saw the morning afterwards that it’s still on and in suspend mode. When i wanted to reactivate it i noticed that it was very hot, especially the area of the CPU felt like i could burn my fingers.
I know that suspend also draws power and therefore generates heat, but isn’t there any point the fans should start spinning?
I have not seen this issue yet, also if i remember correctly, when i left the Framework in a bag on suspend before the fans turned on after a while. But this happened before the UEFI update.
Welcome to the wonderful world of S0. Basically what you will want to do is either enable S3 support, OR make S0 network disconnected. There are posts on this forum talking about these points.
In essence, S0 is a low power idle state that allow some work to be done. S3 is suspend to RAM with the CPU effectively off and no work happening. S0 does permit a suspend then hibernate scheme based on drained battery percentage. However, you will never see this with the laptop plugged into a power source. S3 will suspend (using less power while doing it, compared to S0) but will suspend right until the battery is dead and the whole system runs out of power.
I just use S0 network disconnected, and if I know I am going to be a while, I just hibernate to keep things cool. YMMV.
Like others have mentioned putting the computer into hibernate instead of sleep will get better results. The whole modern standby is way more complicated than it needs to be.
If I remember right you have to enable Hibernate because it is not available by default in Window 11.
Then changing your power options to choose what to do when:
Press the power button: Hibernate (or choose)
Close the lid: Hibernate
The system boots so quickly from hibernating it is not worth the risk of it waking up (especially in a bag) and potentially cooking itself.
I believe there have been a few reports of the fans not coming on when the computer is in modern standby. I am not certain if that is still an issue the Framework team is still addressing with the embedded controller (EC).
They have a number of other issues they are working on as well. The BIOS team is somewhat small and they are tackling as many things as they can with all the various models in the Framework lineup.
A support ticket could be filed so they have more datapoints to go off of with this issue. Maybe one of the mods has a better idea of how to log the issue if it is not already entered in the Github repository for the BIOS.
Hibernation is the sure way to ensure you don’t have a hot potato when retrieving your FW from a bag, BUT if you switch to S3, you can be resumably assured that the same wont happen while suspended.
SO how do you get rid of pesky S0? Look no further, here is the way:
Open the Registry Editor:
Press the Windows key + R to open the Run dialog box.
Type “regedit” and press Enter.
Navigate to the Power Key:
Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power.
Create the Registry Entry:
Right-click on the “Power” folder and select “New” > “DWORD (32-bit) Value”.
Name the new value “PlatformAoAcOverride” (case-sensitive).
Set the Value: (Observe that it is not already set to 0. If it is you can skip this as it is already done.)
Right-click on the newly created “PlatformAoAcOverride” value and select “Modify”.
Set the “Value data” to 0 and click “OK”.
Restart Your Computer:
Restart your computer for the changes to take effect.
Should you want to revert to S0 for any reason, you would simply delete this DWORD. For anyone reading and using this guide, please note that your registry is very important. Do not treat it like a sandbox you are romping around in. You have been warned.
Long live S3 until S0 can stop being a steaming pile of refuse.
