Perhaps so, but my dang MacBook does the same thing. I have turned off every single thing that I possibly can that would cause it to wake up, and yet I still randomly find it turning on for no reason pretty much every other day. I’ll walk by my study and find it turning on for short periods, I’ve pulled it out of my bag hot as fire, I’ve had it drain the battery in the middle of the night, etc. Looking at the logs, I’ll often see that it just decided to get into a random loop of dark wakes and sleeps. It’s infuriating.
I think the issue with macbooks is similar, but happens when you have USB-C dock with an external display connected. When you close the lid while connected to the dock, mac does not go to sleep but just switches to using the external display (aka clamshell mode) and when you unplug your computer to put it in your backpack, it just remains active instead of going to sleep.
The solution to this is to install noclamshell via brew or just get in the habit of disconnecting your mac first before closing the lid.
I noticed this because previously it was sleeping completly fine and the problems started only recently which is inline then I started using the dock.
I've seen that happen, but I'm specifically talking about disconnecting my dock (if it's even connected), closing my lid, confirming the fans are off, putting it in a bag, then finding it back on later doing an infinite loop of darkwakes for no reason.
On Apple Silicon Macs, the machine is never going into that deep a sleep to wake up from (it's basically a huge iPhone, remember?) and Wake for network access is not for Wake on LAN but rather if you want it to keep WiFi running to get push notifications etc while in "sleep" (the description under it in Settings even says it's for iMessage and iCloud updates).
Marcan has talked about Apple Silicon sleep states wrt to implementing it in Asahi Linux and IIRC they never put the machine to sleep, they just stop all the processes and hardware like the display and let the CPU idle normally (which it's extremely efficient at)
Yeah. I have an Intel MacBook Pro (nearly 10 years old) and never hit this problem. I can leave it on the shelf for a month and it’ll still have a 70% charge. I just gave up on Windows and brought a new M1 Mac due to this exact issue (the Intel one wasn’t getting OS updates any more).
The speed and reliability with which a Mac sleeps and wakes and how well it maintains battery is insanely good. My Windows laptop was more like a portable desktop, as I always had to plug it in and would walk around with the lid open rather than risk a sleep/wake attempt between meetings.
But according to the video; a 10 year old windows laptop wouldn't have this issue as well. It would probably go to sleep properly as expected almost every time.
Also I have had this issue with Macbook Pro 15 (2019), so it can't be guaranteed every-time for any OS I guess; not sure of the reason though. To me closing the lid should take preference over everything.
I'm temporarily sleeping in the room with my MacBook Pro, and it wakes up (and turns on a glowing peripheral too) half a dozen times during the night, to the point I unplug that peripheral before I go to sleep.
My previous, older Mac wouldn't sleep at all for more than a few seconds unless I unplugged the external monitor.
Yeah, I've turned literally everything off that I can. Not just power nap, all the random wake settings they have: powernap off, proximitywake off, networkoversleep off... all the way down to actually disabling wifi and bt when my lid closes. It's a mess.
What worked for me was disabling the feature of keeping the TCP connections alive. No idea if it's covered by 'networkoversleep', but this is as deep as I've went, considering I've then received a warning that "Find my Mac" will stop working after this toggle.
yep, I did the same. So, last time I dug into it, I found a separate issue where it would darkwake to do things like check in with find my mac, and then an app that had an idle power assertion would prevent the darkwake from fully shutting down again. That's separate from it getting into a weird loop of waking and sleeping though.
