Live data from Hacker News

MacBook Pro Insomnia

manuel.bernhardt.io

191–200 of 238 posts

Re: MacBook Pro Insomnia

#191

Earlier quoted context omitted.

Computer connected to a dock with monitor is a common use case for a close lid for me.

Why not crack the lid a little? No way I'm letting the display of my very expensive laptop contact the chassis while it's in operation.

It’s Apple and I trust that they have thought of this, and designed to support this.

Re: MacBook Pro Insomnia

#192
post #185

Another trick is to open Activity Monitor, switch to the Energy tab, and sort by the "Preventing sleep" column. Some apps prevent macOS from sleeping. 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 h…

I wish ios had insights (and controls) like this. So many apps have telemetry and data collection and notifications that eat up your battery and bandwidth for business (no good) reasons.

Can't you effectively check that through the background activity time in the battery usage overview?

Re: MacBook Pro Insomnia

#193
post #18

Earlier quoted context omitted.

This is a macOS bug; it doesn’t need an IP address while it’s asleep. Waking up to renew a DHCP lease is crazy. Closed source OSes are such a bane.

Macs doesn't need to wake completely to renew their DHCP leases. Bluetooth and Wi-Fi radios can act independently and on their own for this low level operations. 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.

That is pre-Apple Silicon, before together integration of software and wakeups.

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.

Re: MacBook Pro Insomnia

#194
post #193

Earlier quoted context omitted.

Macs doesn't need to wake completely to renew their DHCP leases. Bluetooth and Wi-Fi radios can act independently and on their own for this low level operations. 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.

That is pre-Apple Silicon, before together integration of software and wakeups. 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. F…

> That is pre-Apple Silicon, before together integration of software and wakeups.

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.

Re: MacBook Pro Insomnia

#196
i had the same issue and my i9 macbook pro was heating within seconds of turning on. some where i found that not using chrome could save a lot of battery.

Re: MacBook Pro Insomnia

#197
Unrelated, but this reminds me of a persistent headache on Windows. My screensaver refuses to kick in, no matter what. After tumbling down a rabbit hole longer than I’d care to admit, it’s clear I’m not alone… tons of apps and processes hijack idle detection, leaving my OLED panels stuck on static displays overnight (hello, burn-in risk).

Anyone know of a solid Windows equivalent to Sleep Aid for diagnosing and fixing these wake/sleep ghosts?

Re: MacBook Pro Insomnia

#198
I'm one of those apparently super rare weirdos who just shut down any computer over night. Takes me just a tiny wee bit longer the next day to get started, but given all the issues my work colleagues have with battery life and whatnot (something I've never had troubles with on several machines going 5+ years), I just stick to it - and stories like OPs are definitely reaffirming :)

Re: MacBook Pro Insomnia

#199
I have SentinelOne as part of my install. Since that got upgraded, my Mac started eating its battery during sleep. Possibly due to SentinelOne's network scanner, as that takes up 100% cpu for awhile when just returning from sleep. So my mac awakes 3 times an hour to connect to iCloud and then adding SentinelOne overhead...

I think I might try this setting (Prevent Wake for Maintenance)

Re: MacBook Pro Insomnia

#200
post #75
post #60

Earlier quoted context omitted.

that's called "off".

i suppose we have come to expect 4 states: - off: no power, no activity - hibernate: no power, no activity session state saved to non-volatile storage - sleep: Minimal power, RAM remains powered with the session state, can be resumed quickly - on now we essentially have sleep++ and no option to set it back to vanilla sleep.

Those are the states I expect, indeed, but lately I find them increasingly unreliable. I've had Windows unable to sleep, Linux crashing after hibernating, MacOS issues are addressed aplenty here.

I thought this was a solved issue. How are all OSs suddenly so bad at this? I only really trust on and off anymore.

Post reply on HN