Yes. This is actually a known issue, provided you have an external monitor attached; lots of people complaining about it. The Mac actually wakes up instantly if you lift the screen, but it usually takes 5-10 seconds before it will wake up the external monitor.

Worse, for some of us when it does finally wake up the monitor, sometimes it wakes it up with all the wrong colors, and rebooting is the only reliable fix. (and before anyone asks, yes, I tried a different HDMI cable)

For me it's maybe 5-10 seconds for it to wake my Thunderbolt monitor (LG 4K) from "cold".

It's much faster if the monitor has been used recently, though, so I always figured it was the monitor that was causing the delay by going into some deep sleep state?

It seems a little faster, but not dramatically so for me, when I'm hot switching between different inputs on the monitor. Definitely I think some of it is just the monitor not being really fast about switching, but I use the same monitor with a brand new 16 inch MBP and it's much faster at triggering the monitor to wake up.

Same monitor. The workaround is to put the monitor on a power strip you can trigger when you walk up to it. Hard power off/on of this monitor and it instantly displays for me now.

Found the same

I don't know why I got downvoted on that, it's strange advice but it really works

Do you have issues with the sound on your LG monitor? I have an LG too and the sound being transmitted by the M1 is very bad.

The sound quality is indeed pretty bad on the LG 4K. Noticeably worse than the MacBook Air's built in speakers.

It's just "cheap speakers" bad, though, not anything that would suggest an issue with the sound output from the M1. I've used the LG with a few different Macs, and sound quality is the same from any of them.

I think they are still working through some external monitor driver issues. The colors on my LG 4k were initially way off until I did an advanced calibration. Occasionally waking up from sleep it will revert, but opening the Display preference and swapping between the calibrations fixes it. My connection is through usbc.

I don't have any performance issues waking up though.

I think there are a couple issues going on with the colors. For some people it is calibration. But what I experience is almost like a color inversion (but it's not a full inversion, it looks like maybe one or two channels got inverted). Makes it difficult to even find the mouse pointer so I can get to the menu and reboot the machine. Then it comes up fine.

Interesting. I did submit a bug to Apple about my issue. Mainly because I never did a calibration with my 2017 mbp and the monitor looked great. With the M1 MBA I had to do the advanced calibration just to make the same monitor usable. Otherwise the colors were completely washed out. It almost seemed like the setting to auto-dim the laptop monitor was also being oddly applied to the external.

This happens to me too! Exactly as described. I have 16gbac mini conmected to an external monitor with an HDMI cable. A bit irritating but not a huge deal I don't do any color work on it so the occassional color issues are not a problem for me.

I've got an Intel Mini, and it's much faster to wake when I'm using a TB3->HDMI cable than an HDMI->HDMI cable. (Going to a dell 3219Q)

Anecdotal, but I haven’t seen any issues while using DisplayPort rather than HDMI. EDIT: Other than the delay in waking the monitor.

Yeah, I would like to use DP, for sure. A peculiarity of my situation and the devices I need to connect means I can't make that work with just two ports on the laptop. So I use the Apple USB-C PD/HDMI/USB adapter so I can get the ports I need and still charge.

Does this happen with the Mac Mini?

M1 instantly wakes my XDR display and never has a problem.

>and before anyone asks, yes, I tried a different HDMI cable

Have you tried a USB-C/thunderbolt cable/controller tho?

I'm kinda limited in my options, because this MBP only has two USB ports. So I have one port which goes to a USB hub, and the other port goes to an Apple A/V adapter with USB-C power delivery pass-thru, HDMI, and a USB port. If not for my need to have one USB port be switchable, and the rest not, I'd use a USB-C -> DP cable like I use on my 16" MBP.

This may prompt me to upgrade prematurely, if/when the next M1 MBP comes out with more than two ports.

Get a thunderbolt dock and you don’t have to worry about it. The dock also charges my MBA.

Which dock are you using? Caldigit? Those seem popular, but I see there are a number of options at every price point.

I have the OWC TB dock that was just released (and has been backordered). It works great other than the headphone jack has a slight hiss that I don't get plugging directly into the MBA.

CalDigit TS3+ works great for me with monitor hooked up on DisplayPort. No delay on resume. This is the dock Apple sells.

Instant wake for me. However any time I come across a password field in a website the computer freezes for a painfully long 10 seconds or so while it presumably decrypts my password vault.

Sometimes this will happen multiple times per page load if I deselect and reselect the password field.

Oh goodness I thought this was just me after searching online and finding very little, if any, discussion of the bug. The issue I had wasn't on password login prompts, but on account creation prompts (i.e. password+confirm password). I had assumed it was lastpass at first, but the freeze persisted even after removing that -- on a one-day old computer.

Feel free to report it in Feedback Assistant.

I gave up on reporting bugs to Apple a while ago. The experience, repeated several times over, of spending all the time to file a radar, gather all the logs and files that Apple insists on (probably reasonably), then submitting the thing and getting exactly zero feedback for the next year when you are then told to repeat all the same work on a new macos version or the radar will be automatically closed, is demoralizing. Mind you, the issues I reported were fixed/went away a few years after that (so clearly not as a result of the then-long-closed ticket), but the process just feels like a waste of time to interact with the black box of apple.

It helps more than nothing. I would recommend just becoming more casual about it.

My experience maintaining projects is actually not that people don't provide enough info in their bugs (certainly true for random forum rants though), but when they try they try too hard and end up spending a long time writing a bunch of stuff I don't even read, because the log speaks for itself.

In this case you're not necessarily reaching an engineer, it could go to someone who combines reports together, or the fix is because of your report but it doesn't get communicated back properly, but it's still letting someone know it's a problem.

This happens to me too, I’m using 1Password. I have a suspicion the plug-in is involved with this but I’ve not had time to collect evidence yet. Seems to be rare though, I’ve not spotted anybody else with this issue.

I am seeing lots of spinning balls with 1Password on my 2015 Macbook Pro. Even just switching between fields with the keyboard brings up a spinner for two seconds or so. It's a recent thing I think. No other app has any issues.

Is it possibly due to the x86 emulation? I could see something like that being the cause

Apparently the latest version 7.8 runs natively on Apple Silicon.

I see the same thing on native x86 1Password.

I just updated to version 7.8 from version 7.7 and it looks fine so far. I haven't seen any freezes in the five minutes that I have been using it.

This makes me realise how much of a pain it has been to use in the past weeks or so. Now that it is back to normal snappy it is such a pleasure to work with again.

Huh, no problem here. I use lastpass and safari's built in password thing.

Anecdotal but keeper and the built in keychain are instant ish at least not slow enough to notice

I don't use any external password manager, only Keychain and Safari and I see this 10-15 second delay every time when adding new password to Keychain since day 1.

It is my only issue with M1.

Did you somehow accumulate a bajillion passwords?

Crypto optimizations are no joke. My Pinebook Pro takes several seconds longer than my T430 to decrypt my keepassxc database.

Maybe the time is hashing your password. This is designed to take as long as it can while still being reasonable. 1 second on a fast machine isn't unheard of.

Why would it need to decrypt a whole database though, and not just the required password? To avoid leaking the key name?

Yes I think it is an all or nothing deal.

Perhaps it could be a two-level thing then, where you first decrypt e.g. the list of keys and then read the one you want and get a "start/end" offset to read/decrypt just the value for that key from another file. So keys and values are still decrypted, but you don't have to decrypt the whole bundle in one step to get the value.

I have a non-M1 with Big Sir and it takes more than full minute from sleep to usable.

I suspect it’s because I have five monitors and 20 million pixels (actually more as that’s the post-retina resolution).

How does the number of pixels (or even monitors, for that matter), affect that much sleeping time?

Rendering a FPS game at 1080p is 2 million pixels per frame. At 60fps, that's rendering 120 million pixels per second.

What am I missing?

Detecting the monitors, negotiating the correct resolutions, setting scaling factors and window positions after coming out of sleep will take some time. Maybe macOS does monitor setup sequentially? (no idea, just got 1 big external screen that also takes a few seconds to light up - handshake speed seems to vary between monitor brands)

This is almost certainly it - the screens show all sorts of weird graphical artifacts (some clearly a Retina display in "native" resolution) as it starts and loads. I assume it's having to fire up all the GPU memory, etc.

This is anecdotal and I don't have anything to prove it, but I really feel like my old spinning-hard-drive 2010 MacBook Pro woke faster from sleep running Snow Leopard, than the Retina models ever did (or the old ones did after a few software updates).

Of course for general tasks it was slower, but I really remember that thing waking up instantly when I raised the lid, every time.

My nostalgia agrees with you, but I think it’s probably wrong. The wake from sleep was what finally convinced me to get my first Mac. Even now they have the best hibernation and wake from sleep.

Yeah. To me it looks like macOS goes so deep into sleep it disconnects the external display. On wake, the system rediscovers the external and resizes the desktop across both displays. With a bunch of apps/windows open, half your apps simultaneously resizing all their windows can peg all CPU cores for a number of seconds.

(It's still way faster than the same set of apps on an Intel Mac laptop, where it could sometimes take on the order of 30 seconds to get to a usable desktop after a long sleep. On Intel Macs it seemed more obvious that the GPU was the bottleneck)

No, it's perfect, instant wake for me. I have never seen anything like this.

I have buggy apps (like Facebook Messenger) locking up, but I guess that's normal, I just uninstall them.

Which M1 do you have?

16 GB RAM pro 1TB SSD.

I guess the only drawback compared to MB Air is that it's a bit heavier.

Haven’t seen this on my M1 Mac mini; my wake times are faster than my monitors can wake. No performance issues immediately after sleep.

Maybe desktop platforms sleep differently than laptops?

Most likely. Same here with my Mini

I am using the LG Ultrafine 5K (so it’s a TB monitor) and it takes maybe 1.5s to 5s longer than the built in display (which wakes instantly) to turn on.

I do occasionally have an issue where the brightness on the built in display is borked and won’t adjust back to the correct level for anywhere between 30s to a few minutes.

And then I don’t know if it’s my monitor or the M1, but sometimes there will be a messed up run of consecutive pixel columns about 1/10th of the screen wide starting about 30% from the left of the display. The entire screen in that region is shifted a few pixels upwards. Sometimes it’s hard to notice it but once you do it can’t be unseen. Replugging the monitor into the M1 resolves the issue.

It way faster than my old macbook pro. But one thing is the external monitor won't be open upon resuming. I have to plug/unplug the cable to re-active the external monitor. It seems HDMI handshake was failed somehow

I haven't noticed poor wake times, but my laptop does kernel panic and reboot a fair amount. Maybe 4 times in the past week. My hunch is that it's Spotify's fault but I haven't dug into the logs.

A user-land program cannot be at fault for a kernel panic, that is the kernels fault, always.

xnu will panic if it doesn't receive periodic check-ins from userspace. For example if WindowServer hangs, then the kernel may deliberately panic so that the system reboots. See man watchdogd for (a tiny bit) more.

True, but a third-party program shouldn’t really be able to do this, at least not easily.

I have this problem but only if I've been plugged into a monitor, and then unplugged and gone onto battery. Rebooting after unplugging stops it but its annoying.

I've had mine panic and reboot twice, both times happened shortly after disconnecting other Macs that were connected via a Thunderbolt cable (target disk mode).

How does spotify panic the kernel itself?

Definitely no issue with waking my M1 8GB MacBook Air. Takes a fraction of a second, every time. In fact, this is specifically something that Apple were bragging about when they launched the M1 Macs!

Very happy with my Air 16gb on resume - much faster than my 2018 air

Do you have it plugged into a monitor upon wake? How many programs do you have when it is resuming? I noticed this really infrequently.

I tried reinstalling OSX, now it seems fine! ¯\_(ツ)_/¯

Nope, my M1 Air is connected to an external monitor most of the day and I don’t have issues.

It’s inappropriate of you to post an offtopic end user technical support question on this post about CPU microarchitecture performance.

It's inappropriate of you to scold another commenter with a content-less comment.

Why? There isn't really anything interesting in this post, beyond that Apple obviously wanted this feature for whatever reason