• fuckwit_mcbumcrumble@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    7
    ·
    11 months ago

    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.

    • doczombie@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      Yeah windows standby sucks. On platforms where the equivalent of s0 doesn’t suck, it’s awesome.

      • QuarterSwede@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        11 months ago

        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.

    • bruhduh@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      Oof, felt that, my thinkpad overheated in my backpack while i was dualbooting, it was that hot so my backpack almost combusted

    • Kethal@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      11 months ago

      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.