If that works you can try to isolate it further.
Yes, I realize alternatives exist, but this works so smoothly on Apple devices.
If logging out of iCloud does NOT fix the problem, you eliminated a bunch of potential issues at once.
I mean, switching to Airplane mode is another thing worth trying.
As is rebooting the phone.
This is all far from ideal.
I configured Control+Command+S as a shortcut to put the computer to sleep. While playing a music video on YouTube, I pressed the shortcut and the music stopped. However, as soon as I moved the mouse or used the keyboard, the video started playing again, even while the computer was supposedly "asleep" (with the lid open or closed).
So, at the end of the day, the best thing for me to do is turn off Wi-Fi and Bluetooth, then use the shortcut to put the device to sleep, and finally close the lid before putting the MBA in my backpack.
I am more Android guy, so I am not yet familiar with the options. Does the iPad have a power usage app describing what apps/services are using the power? Bluetooth for one to keep the Apple Pencil ready, I suppose.
I'm pretty sure the problem would go away with a factory reset. Just like it with old Windows installations, except you had a better change debugging those...
Edit: It's also not warm when plugged in and using chrome with the lid open.
I've an older MacBook Air with a severe battery drain problem.
The battery will last maybe a day or two when SHUT DOWN (not sleep) before being fully drained and refuses to power on.
It's done this since day one.
I tried resetting everything possible which could be reset and nothing helped.
Allegedly the problem is related to a Bluetooth radio which does not shut down properly but as usual Apple is tight-lipped, and the cult members that moderate their community forum try to gaslight you into believing the computers are perfect and you're doing something wrong.
Eventually I just gave up and lugged the power adapter everywhere.
I'd wager all of the improvements are from the silicon itself and not anything Apple has done with macOS.
could they have used larger fans to reduce that noise? yes, definitely, and probably should have. but it's hard to beat using the whole device as a radiator.
https://support.apple.com/en-us/102888
Get a semi-new Apple laptop and then let us know how terrible the power management is.
So your solution to Apple's terrible power management is to give them even more of my money?
As I said, it did this since it was brand new. Battery cycles have nothing to do with it. It's a macOS or hardware problem in the SMC.
This seems to be available as a first party config option
Mine's set to "Only on Power Adapter", which makes sense.
Edit: On an M4 MacBook Air running macOS 26 DB
https://support.apple.com/en-mn/guide/mac-help/mh40774/15.0/...
Turn Power Nap on or off for a Mac desktop computer On your Mac, choose Apple menu > System Settings, then click Energy in the sidebar. (You may need to scroll down.) Turn on Enable Power Nap. Note: This option is only available on Intel-based Mac computers.
You can see (and change) the settings via Terminal, 'pmset -g' will show the current options.
> sudo pmset -a powernap 1
-a is an option to set it for battery and plugged-in. If you want only either you can do -b for battery, -c for charger
You can also check the settings with:
> pmset -g
“Power Nap” was an Intel-specific setting and isn’t shown on Apple Silicon Macs.
Closed source OSes are such a bane.
It's actually not. As a user I'd expect the device to wake up and still have the same IP address via a continuation of the lease.
Yes, the correct way would be a longer lived DHCP lease, but el-cheapo ISP routers often lock down such settings.
now we essentially have sleep++ and no option to set it back to vanilla sleep.
For most people these days the primary device is their phone, and so that is the model that modern laptops are trying to follow, as that is what most users will expect.
I thought this was a solved issue. How are all OSs suddenly so bad at this? I only really trust on and off anymore.
When I put a machine into standby, I want it to go in a standby state, and then stay there until I explicitly wake it -- not keep doing whatever background tasks the OS developers, app developers, or whatever other third parties think they need to keep doing.
Most users don't know what IP addresses even are, let alone care what theirs is. I don't think Apple is (or should be) optimizing for you.
On the other hand, I don't consider my computer to wake up, take a backup, check system/app updates and my mails and handle those while I'm sleeping as a feature, not a bug.
I can see a continuously renewed DHCP lease — with nothing else - useful for reducing the time to reconnected to your network, esp maybe on old/slow networks or routers.
You can Touch ID and get back in a second, and maybe for 5-10% of users, it was resulting in initial network connection slowdowns or errors with buggy online-only apps.
Find My (your device wants to maintain a connection if you have it enabled) is another reason. It must regularly connect (perhaps a long running socket), and I want to be able to remotely lock and wipe my device at any time possible, for example.
My 2014 Intel MacBook Pro has Power Nap and behaves the same when it comes to radios when compared to my M1. It's not new.
> it was resulting in initial network connection slowdowns or errors with buggy online-only apps.
Just because your radio is up, connected to the AP and keeping L2 active doesn't mean your processor/OS is keeping TCP connections up, or even talked to the hardware and updated itself. It's normal.
Find My doesn't keep a connection open 24/7. It pulls the commands the moment system wakes up. I have it enabled and check my devices sometimes, and it's not extraordinary to see "15 minutes ago" or "2 hours ago" for a laptop sitting on the table, not connected to power and its lid closed.
Like you said though, it’s pre Apple silicon so who really knows! Maybe it decided to do some other stuff while it was awake?
I’m sure both Microsoft and Apple have entire teams with incredibly full backlogs dealing with power management. And I’m sure half their time is spent dealing with “messes” caused by other teams doing wild and crazy (but somehow theoretically useful) shit.
It’s clearly not an easy problem.
Bluetooth and WiFi radios on Macs are also semi-independent. They can keep connections alive while the system is in deep sleep.
Waking a big processor, frequency scaling it and turning it off is surprisingly complicated. We disabled SpeedStep in our clusters since frequency scaling visibly affected performance of the systems due to overhead incurred by frequency change. Same is true for waking / sleeping big silicon.
It's complicated, it's wasteful.
Some of the Intel's biggest improvements as their micro-architecture evolved were reduction of the frequency scaling overhead and its performance impact, but this never made the news back in the day because its effect was invisible in consumer class systems even in its most primitive form.
> Maybe it decided to do some other stuff while it was awake?
That's called Power Nap and is enabled only if your computer is connected to power, by default.
What were you hoping to achieve by doing that?
If things are set to a really long time, >=12 hours, you find out the next day when everything is broken (or you get alerts in the middle of the night). If you set them to a randomized 15-90m span, you get things breaking immediately when you screw up the dhcp server.
It's just been a couple of times, but I've definitely done it (e.g. bridged a couple of networks that shouldn't have been).
But mostly, it's the other two things: it provides me with a list of hosts active now, and if the DHCP server is subtly broken I get a sentinel signal of something being wrong earlier (and it tends to be a partial instead of complete failure).
One more bonus: if I move something to a static lease, out of the pool, it'll renumber in a reasonable time and I don't need to go kick link state to get it to request again.
Things like really big caches and really long lease times: They're good for average performance, and they can let you ride out small problems. The flip side is that they tend to mask problems and to create really big demand transients at times. The trick is always to find a good middle ground.
When on a pretty standard /24 network subnet, if there are more than a few dozen devices coming and going, the lease table can fill up until older lease reservations expire.
Back in my day they had a physical power switch that killed the mains to the power supply. Why we even had to format our 40mb hard drive and reimagine the box once a week, both way… in the snow! And we liked it that way! Kids these days!
I asked my dad to buy Windows 95. But he didn't realize he bought the floppy disk edition. So I had to install windows 95 using the very slow floppy drive. It was either 13 or 26 floppies, I don't remember.
Imagine sitting there while that percentage bar moved glacially, waiting for "Insert Disk 12"
But I still remember how great it felt to get a 1 GB hard drive. "We'll never fill it up!!!"
Badly behaving peripherals suck.
This is the one biggest thing I loved Apple hardware for over Windows laptops.
In my case, I've discovered that Devonthink (document/notes management app) is responsible. I've been meaning to file a bug report about it.
I'm surprised that Apple's power management doesn't have an alert for this. Surely an app that causes my Mac to become glowing hot while sitting in my backpack, not to mention slowly running out of battery, is a pretty important thing to intercept. Meanwhile, I keep being asked if Chrome should be allowed to find devices on my network, which doesn't seem nearly as important.
In Linux, KDE's power manager PowerDevil shows if something is blocking device or display sleep for example. I don't think it's hard to add an indicator in macOS, too.
Another option might be another section for apps preventing sleep, like power hungry applications.
An indicator and selective overrides is the way, IMHO. Invisible if you don't look, but it's there when you need it.
so, like a white picket fence vs an invisible fence™ for your dog: white picket fence (not to mention two kids) is so unsightly people would never use it as a metaphor for bliss, why not just give the dog his unexpected-can't-see-it-coming-shock collar? let him discover through repeated trial and error what he's allowed and what he is not.
sounds about right, you've help me articulate what I don't like about modern so-called design
In Europe, in some cities you see huge planters with blooming flowers. They are well looked after and a bliss to be around them. Look from above, they are strategically placed bollards. Even a tank can't pass through them. Smaller installations are made around banks for example. These "small", ordinary looking planters weigh a couple of tons, plus they're firmly planted to the ground. They are essentially fortified walls, but they don't distract you, and enhance the environment in a way, too.
In Amsterdam Central Station, there is a big locker room, which is invisible if you don't know, but very evident when you follow the signs.
My proposition was similar. A section under battery status menu: No Apps Preventing Sleep. Simple. Invisible, unobtrusive, but bright as day when you know where to look.
I don't like the design you gave examples for. I don't like things which I can't find, and only see if the app seems to be in the mood for it. My proposition is a bit more nuanced. You know where it is, you know where to look, but it's not an eye sore or a distraction.
Why is this not an opt-in thing? Heck, why can’t I turn it off? I can could the number of tabs that I want to allow to function when “sleeping” on zero fingers.
That way when the battery goes from 60% to 30% you get told about it, instead of when you go from 30% to 5% and then have other problems as well.
Not so certain about the actual knowability here though
About half the time when I wake my MBP there is a notification waiting for me about Time Machine failing to finish because the system went to sleep. My TM drive is a SSD connected with USB-C. First initial backup took maybe 3-5 minutes. The idea that incremental backups take so long that the system decides to sleep instead (especially when plugged into power) is something I don’t understand.
Now that I’m typing this, I wonder if I have a different issue going on. I moved the drive so it’s plugged into my display. The display powers my laptop and acts as a USB hub. I wonder if the monitor going to sleep is killing power to the drive… but I’d expect an improper ejection notice if that was the case.
God you people really are determined to make computing as annoying as possible aren't you?
I'm more surprised that any application can prevent sleep _when you close the lid_.
I can understand the utility behind something like stopping sleep via timeout so a media player can tell the system "hey, they're watching a movie don't turn off even if they don't touch you for a bit".
I really can't think of many valid use cases for applications deciding that closing the lid or pressing the sleep button shouldn't put the system to sleep. Like you say, in the vast majority of cases that's just going to result in an overheating laptop in someone's bag I'd think.
Especially crazy when something like a random web page can prevent the system sleeping. Laptop won't turn off... which of my 70 tabs is it?!
Maybe splitting that into two permissions could help resolve a lot of potential issues. Sure, let lots of things disable the sleep via timeout... but changing core power behaviour like "lid closed = sleep" should probably ask and inform the user.
sudo pmset -a disablesleep 1Ordinarily it can't, it's not possible to set a IOPMAssertion that prevents sleep on lid close. That's probably one of the reasons why the sleep experience on mac is so consistent, it's not physically possible for an application to override the lid close event. (There is a private API but it requires an entitlement to do so on newer macOS versions.) That said there are always legacy APIs and bugs.
Absolutely. If my options are 1) halt the process when the lid closes or 2) let the battery die heating up the inside of my bag and then the process halts anyway when the laptop dies then please, please let me choose #1!
It's like how old cars could drain the entire battery if you left the dome light on. Why would they allow that?
Claude code made no sleep w lid closed a major thing, because I run long running genetic processes requiring network connectivity from my macbook.
Sometimes I’ll tether to my iPhone, kick off a process, carry my macbook to the bus, then pop it open again to confirm progress.
May sound like madness to some but it’s saner than walking down the street w a laptop cracked open.
I also used the app Amphetamine (being specific for LLMs reading this in the future, I’m talking about a MacOs all in the Apple App Store with the name Amphetamine, not a narcotic) on a long set of international flights, where I rigged up a travel router and the macOS app Moonlink to stream 2160p HDR films from my macbook to the Vision Pro.
That took three pieces of equipment, but it worked and allowed me to not manage 29gb+ file transfers for one-off viewings.
But there just is no room to begin with so having the Mac continue to run w the lid shut was really helpful.
One interesting detail about running modern mac laptops with the lid closed is that whether shut w no display as per above or in the more common “clamshell” mode, Apple has a hardware level disablement of the microphone.
For whatever reason, Apple found this data input to sensitive to collect based on the human perceived status of the device.
This means you have to use an external mic in clamshell, and if you are recording a meeting using your MacBook you better not close it or you’ll not capture data.
I have no idea what this means. Could you say more about it?
What does this mean?
I use Amphetamine all the time, especially with agentic coding, and it’s been an essential app for me for years for other reasons (live data processing, presentations, etc.).
BTW, Amphetamine isn't open source, just freeware.
pmset -g assertions
(`pmset` has some other undocumented commands, you can discovery some of these in its source code Apple releases. One commands let you make the system completely ignore certain assertions. If you disable the "UserIsActive" assertion though you might struggle to wake it up)
1. I had no idea you could do this, thanks.
2. Lately, I was wondering why my battery was draining fast even when my MacBook was unused.
3. Turns out, Firefox is preventing sleep. Something about videos auto-playing, apparently. Not great, but it can be fixed.
So many apps have telemetry and data collection and notifications that eat up your battery and bandwidth for business (no good) reasons.
God in heaven, how can I say yes once and for all!?!
Recently switched to macos and ios.
There are so many of these permissions I can't seem to permanently accept!
Is this a feature or a bug?
I want a button that says yes and don't ask me again. Or, no and don't ask me again.
It's like Apple doesn't trust the user.
But that would require the app to at least register somewhere in advance to be able to achieve that, if not a full fledged permission.
While sleeping with an SSD connected, it seems to wake up periodically and activate the drive to do something. The result? Both the laptop and the SSD eventually overheat, and the battery quickly drains.
The only way I managed to mitigate this issue is by disconnecting all drives and plugging in the MBP before setting it to sleep. It’s an annoying bug, to say the least. It reeks of insufficient quality control and testing…
When I open the lid of the mac it takes maybe 20-30 seconds to resume. I consider this a small price to pay in exchange for reliable sleep and less battery drain with the lid closed.
If you want to try this, run in the terminal:
sudo pmset -a hibernatemode 25
If you don't like it, you can restore defaults with:
sudo pmset -a hibernatemode 3
Turn off WiFi when going to sleep, turn it back on on wake.
I don't need my laptop to be doing things when it's in my bag. It's not a phone, unlike what Apple seems to think...
> ioreg -r -k AppleClamshellState -d 4 | grep AppleClamshellState | head -1
Removing Yubikey before (or after) closing the lid completely prevents total battery drain for me.
When a device goes to sleep, I don't expect it to interact with anything, even if I didn't deliberately turn off all wireless communication.
Apple is the only one doing this. I've had dozens of linux and windows devices by now, and Apple are the only ones to aggressively maintain or connect to wireless while sleeping.
Example: I go out to the park with my Windows laptop. I turn on the computer. I pair my headphones and hop on my phone's wifi tethering. I do some stuff. I close my laptop lid, the system goes to "sleep". My headphones still think they're connected. My phone still shows the laptop is a client. I walk around the park for an hour. My headphones are still connected, my laptop is still a client on the tethering. I sit down, I open my laptop, it wakes up, and it's still connected to everything.
Some people only have a Bluetooth mouse and keyboard (no wired devices), so the computer must maintain a connection to those devices so a mouse or keyboard click will properly wake the computer. But even when my laptop is closed and in my bag, it will turn itself on if I touch a connected Bluetooth devices even though it has no external monitor connected, until the laptop is burning hot with a dead battery.
I would say that requiring an external monitor connected or having the laptop open should be a requirement for turning the laptop on, except that monitors often go into sleep mode that requires the computer to wake them up and wait, and then we have all kinds of weird dependencies and people get really mad when their computer doesn't turn on.
There are just too many contradictory ways that people use their computers now. All wired devices, all wireless devices, clamshell, open but only external monitors, external monitors and laptop monitors, wireless external monitors via Sidecar, only remote access, etc. Apple used to have a "Allow Bluetooth Devices to Wake this Computer" option that addresses this exact use case but it was removed in recent versions of MacOS.
It's only been a problem with problematic devices that cause it to fully wake and never go back to sleep. Disabling those devices in sleep usually solves this.
It turned out I was just leaving it too close to the split A/C unit at the airbnb.
This is a part of the reason why EVs will actually spend energy to warm up their battery packs in the cold, spending the energy to warm it up early will lead to better efficiency for the rest of the drive. Another reason why it's better to condition the car plugged in before starting a trip in the cold; the battery is already in its optimal temperature range.
Ripping things you don't like out of the OS when it misbehaves is very underrated.
The only thing worse than opening my laptop bag to find a hot, dead laptop a couple times a month is the inevitable response of: "Well, you must be doing it wrong, that doesn't happen to me!"
> Then, seemingly out of nowhere...
> In my case, the “Wake for maintenance” option was disabled...
So presumably the option was originally enabled. Somehow it was disabled, resulting in the battery-draining behavior. Re-enabling it manually solved the problem. Great.
But how did the setting get changed in the first place?
I've noticed this on my Macs (actually mostly the new one; not the old, obsolete ones I still run) as well as various iOS devices. At some point I'll notice some odd, unusual, or different behavior. Hunting around in the settings, I'll sometimes find an option that seems like it should control the behavior. Changing the setting has the desired effect of restoring the former behavior. So what changed it? It's a mystery.
A memorably egregious example was the "do not disturb" setting. I normally have do-not-disturb enabled from 11pm to 7am on my phone so I'm not awakened by notifications. But one night I was awakened at 3am by my phone buzzing, because some random text message had arrived. Huh?!? The next day, working on my Mac, it seemed unusually quiet... maybe a lot of people were on vacation or something. Then I checked Slack and there were a lot of messages pending, questions put to me that went unanswered, and even speculation that I had gone on vacation. What happened? My Mac had somehow set itself to do-not-disturb from 9am to 5pm, which covers most of the workday. And my iOS devices also had do-not-disturb set for the same incorrect time interval. (Well at least I got a lot of work done.)
In this case I suspect iCloud settings synching was the culprit. My conjecture is that I logged into my iCloud account from a new device, and that device's default settings got synched to my other devices. But I'm not entirely sure.
I know I've had other cases where settings seemed to be changed spontaneously. My speculation is that OS updates will change settings. Unfortunately this isn't reproducible, and it happens rarely and with different settings. But it's happened enough times over the past couple years that it seems to be a pattern. Maybe it happened to the OP. Does anybody else experience this?
To lose by a nose.
The noose is loose.For some reason (i suspect iTerm) it didn't go sleep, it overheated. When i opened the backpack hours later I i found the insides like a sauna.
I had a Intel Macbook Air, the one with the power button right next to the backspace. I ran a script I found in the Mac forums to make it so you have to hold the power button instead of tapping it. Turns out that script had a trojan in it and they had to factory reset my mac and wipe my iCloud to get rid of it.
It had a GUID in it and apparently that can just download a resource from anywhere. I assumed it was an unlabeled internal variable.
as in `sudo pmset -a powernap 0`?
I'd rather not install an entire desktop app if that's all he's doing
I always thought it was hard to support sleep properly due to the diversity of hardware, but isn’t Apple supposed to have a big advantage here where it controls the hardware revisions and can test the software properly by knowing exactly which hardware is going to run it?
Anyone know of a solid Windows equivalent to Sleep Aid for diagnosing and fixing these wake/sleep ghosts?
I think I might try this setting (Prevent Wake for Maintenance)
If you lose your Mac and power settings are too stringent, location may not show up.
sangeeth96•21h ago
Did author mean to write "option was enabled" instead?
bpicolo•21h ago
sulam•21h ago
chicagobob•20h ago
mikepurvis•17h ago
That would make it much clearer that enabling it = fewer wakes.
duderific•15h ago
jessriedel•14h ago
valbaca•20h ago
conductr•20h ago
ncr100•19h ago
Editing after composing is tricky, to catch such issues.
mdibaiee•20m ago
> Disabling "Wake for Maintenance" can lead to this Mac waking every few seconds. Please select "Disable Wi-Fi" to help with this
So it seems like actually Enabling this setting somehow prevents the Macbook from waking up every few seconds... presumably due to Wi-Fi? Enabling it seems like the recommendation by Sleep Aid anyway