| |
| ▲ | Krssst 33 minutes ago | parent | next [-] | | This was ~2 years ago, but it didn't work on my side. Closing the lid would put the laptop to sleep then quickly wake it up, fan spinning at full speed even if unplugged. I think I used their diagnosing tool and one cause was some non-microsoft (installed by a driver I think, laptop as almost new) scheduled task, so not fully their fault, but forcing this kind of much weaker/unstable sleep without backup when S3 worked well is a bit crazy to me. (by the way the laptop was a Framework 13 AMD, curious if others experienced the same. Maybe they fixed it now) | | |
| ▲ | rmunn 4 minutes ago | parent [-] | | The Framework 16 had an issue where the closed lid would flex slightly in your backpack, and press keys on the keyboard, waking up the computer. Ten days ago (Nov 14th), Framework released a BIOS update for the 16 that would turn off the keyboard (and numeric pad) when the lid was closed. I installed that update immediately, and for the first time, when I pulled my laptop out of my backpack after leaving the office and going home (or the reverse), it was still suspended. Had nothing to do with Windows drivers (I run Linux), was purely a physical issue. I haven't checked if the Framework 13 got BIOS updates at the same time. But you could check if the keyboard is causing the wakeup (the Framework 13 has the same keyboard as the 16, but its smaller screen means less flexing in a backpack so it might not be suffering the same issue) by opening a Notepad window before putting the computer to sleep and closing the lid. If you find that random characters have been typed into Notepad while it's sleeping, then the issue was the same that the 16 was experiencing: the keyboard needs to be disabled while the lid is closed. If you don't see random typing with the lid closed, then it's a different issue. |
| |
| ▲ | FridayoLeary 2 hours ago | parent | prev [-] | | Still not? It's a feature everyone needs i'm assuming lots of people at microsoft own laptops. Mac probably figured it out around the same time as the declaration of independence was drafted. | | |
| ▲ | hedora 2 hours ago | parent [-] | | That one is arguably Intel’s fault. The last few generations of intel macbooks did the same thing, and I had the same issues under Linux (except they were debuggable there, and clearly Intel’s problem). Apple fixed it by switching to their own processors. MacOS is sliding fast too though. If I leave my MacBook plugged in overnight, it’s toasty in the morning at least half the time. Not sure how many times it died because it was low at night and I forgot to plug it in, and how many were failed sleeps. Power Nap or whatever it’s called is disabled. |
|
|
