this post was submitted on 15 Dec 2023
54 points (95.0% liked)
Technology
59287 readers
4174 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
S1 sleep was as fast to resume as S0 standby.
Instead I get 30+ seconds to wake from sleep, 1% battery drain per minute, and the random chance that it just overheats in my bag and crashes. At least on my Surface Pro and Intel U series laptops it's tolerable, but I'd much rather S1 standby for 30 minutes, S3 standby for 4 hours, before finally hibernating. Instead I currently get buggy S0 for 15 minutes, and hopefully it makes it to complete hibernation after that.
Oof, felt that, my thinkpad overheated in my backpack while i was dualbooting, it was that hot so my backpack almost combusted
Yeah windows standby sucks. On platforms where the equivalent of s0 doesn't suck, it's awesome.
Bingo. MacBook’s are always ready to wake with little battery loss. Windows just … can’t do that ever. If phones can be expected to behave this way, computers have zero excuses they can’t.
Man, this is why my work laptop does that. It is an all around POS so I chalked this problem up to that. I didn't know that MS deliberately broke sleep. With this knowledge I've learned how to go back to regular sleep.