I’m primarily a Mac user but I haven’t had the same issue with other Windows laptops and the Dell has standby issues in Linux too so it’s just bad. And loud. And hot.
I’m primarily a Mac user but I haven’t had the same issue with other Windows laptops and the Dell has standby issues in Linux too so it’s just bad. And loud. And hot.
They just axed S3 sleep in the latest Tigerlake chips (which the 9310 use, and I assume Framework is using or will use in the future). You can't even workaround this by running Linux.
This more or less means that there isn't actually an alternative to modern standby other than hibernation at the hardware level any more (unless AMD continue to support it which there's a good chance of happening).
I feel like, at least with Dell, it’s a perfect storm of bad Windows power management policies/support, bad Windows drivers (from Dell or Microsoft or both), and generally bad hardware power management at a firmware level within Linux too.
I’ve certainly had some suspend/power management issues with other Windows laptops, but nothing like this Dell. I’m about to return the Dell (taking it back today in fact) and I had it closed on a desk, plugged in, but closed, and the fans started to go insane. I opened it up and my laptop had exited suspend mode and was in some weird Dell system setting scan that I hadn’t initiated and that wasn’t scheduled to run. This literally happened between when I made my first comment and now (I’m using a different device to comment).
Meanwhile, my Framework laptop might not be as good as my MacBook Pro, but when I close it, I don’t need to worry about it turning on in my bag or have it sitting on my desk.
So I blame Dell, Microsoft, and Dell again for bad power management, poor firmware, poor drivers, and lackluster OS support. Linux could probably get some blame too, but again, I tend to think it’s bad drivers and firmware more than anything.
https://docs.microsoft.com/en-us/windows-hardware/design/dev...
Didn't notice it in the first couple years of ownership, not sure if it was because my usage patterns changed or some not-so-helpful update that made it worse, but it's really absurd that I can't predict what will happen when I close the laptop.
I did something to disable network activity from interrupting standby, which reduced the issues a bit but not consistently.
Intel have just removed S3 sleep from the latest Tigerlake chip so there isn't an alternative.
Granted, this laptop is more than a couple years old at this point, so it is possible it is completely unaffected.
Apparently it isn't, which may explain why almost every quarter Apple reports year-over-year gains in laptop sales.
If I were the boss at Microsoft, this would become a top priority. Immediately.
Is it a new company?
Definitely considering it when my current X1 carbon will trespass into laptops Valhalla.
As far as I can tell it is living up to its hype.