M1 MacBook Air external display keeps waking up

Question

Level 1

28 points

M1 MacBook Air external display keeps waking up

I have an M1 MacBook Air connected by USB-C to an LG 27UK850-W 4K monitor. The screen has been waking up frequently when the MacBook is asleep. It never exhibited this behavior with my previous computer, a 2018 15" MacBook Pro. Both computers are running macOS 11.0.1.

Basically what will happen is I will put the computer to sleep, and then every ten minutes or so the screen will "wake" but not fully "turn on." So the backlight will come on, but the screen will remain black, and then it will turn itself back off after a minute.

Doesn't seem like something that would be harmful, but it's definitely a bit annoying. If I remember to switch the monitor to a different input, it stops waking by itself and continues to charge the MacBook over USB-C, so that's been my workaround. Just curious whether anyone else was experiencing something similar?

MacBook Air 13″, macOS 11.0

Posted on Nov 24, 2020 8:12 AM

Reply

Answer 1

Feb 17, 2021 12:41 PM in response to uttam33

Bad news. The issue of macOS 11.3 beta 2 is more serious, and all the previous methods fail. Apple doesn't care about this issue. It's estimated that it can only use HDMI to solve this issue.

Reply

Answer 2

Feb 18, 2021 2:35 AM in response to uttam33

I recommend caldigit SOHO dock.

Reply

Answer 3

cafarom

Level 1

14 points

Jan 16, 2021 4:29 PM in response to Jeremy K.

Same problem with my Mac mini M1 with an LG 27UK850 over USB-C. Happened when I had an Intel MacBook Air attached to the same monitor over USB-C as well.

I have not been able to find a fix. It's extremely annoying because it lights up my whole room in the middle of the night.

Reply

Answer 4

Jeremy K. Author

Level 1

28 points

Jan 21, 2021 2:18 PM in response to sp4rkbr

On mine, turning off the monitor hasn't been enough, as the MacBook will keep waking it up. I suppose there might be a more low-power off state if I dig into the monitor settings, but I haven't looked and my guess is that such a state wouldn't charge the MacBook, defeating the purpose of leaving it plugged in.

The one workaround I've found is setting the monitor to a different input (HDMI instead of USB-C). This will continue to charge the MacBook and has prevented it from waking itself up. But the monitor's controls are so fiddly, and I kept forgetting that I had done it and wondering why the computer wouldn't wake up, so I just stopped doing that and will just unplug the monitor when I'm done for the day instead.

Reply

Answer 5

Jeremy K. Author

Level 1

28 points

Jan 23, 2021 2:07 PM in response to chrisia777

2021-01-23 11:18:23 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to NUB.SPMISw3IRQ nub-spmi.0x02 rtc/SleepService Using BATT (Charge:100%) 4 secs    
2021-01-23 11:34:04 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to NUB.SPMISw3IRQ nub-spmi.0x02 rtc/SleepService Using BATT (Charge:100%) 4 secs    
2021-01-23 11:40:23 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:100%) 6 secs    
2021-01-23 11:48:36 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:100%) 6 secs    
2021-01-23 12:56:36 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:91%) 6 secs    
2021-01-23 12:56:59 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:91%) 7 secs    
2021-01-23 12:58:11 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:91%) 14 secs   
2021-01-23 14:51:00 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 7 secs    
2021-01-23 14:51:23 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 7 secs    
2021-01-23 14:52:09 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 7 secs    
2021-01-23 14:52:41 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 7 secs    
2021-01-23 14:53:07 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 6 secs    
2021-01-23 14:53:24 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 6 secs    
2021-01-23 14:54:06 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 6 secs    
2021-01-23 14:54:36 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 7 secs    
2021-01-23 14:54:57 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using BATT (Charge:62%) 9 secs    
2021-01-23 16:57:15 -0500 Sleep               	Entering DarkWake state due to 'Clamshell Sleep':TCPKeepAlive=active Using AC (Charge:36%) 30 secs   
2021-01-23 16:57:45 -0500 Wake                	DarkWake to FullWake from Deep Idle [CDNVA] : due to UserActivity Assertion Using AC (Charge:36%) 65 secs   
2021-01-23 16:58:52 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to ATC0.USBWakeup/ Using AC (Charge:37%) 45 secs   
2021-01-23 17:00:44 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using AC (Charge:37%) 46 secs   
2021-01-23 17:01:35 -0500 DarkWake            	DarkWake from Deep Idle [CDNP] : due to SMC.OutboxNotEmpty smc.70070000 wifibt wlan/ Using AC (Charge:39%) 45 secs   
2021-01-23 17:05:11 -0500 Sleep               	Entering DarkWake state due to 'Clamshell Sleep':TCPKeepAlive=active Using AC (Charge:45%)

Reply

Answer 6

Jan 31, 2021 1:37 AM in response to uttam33

Not all monitors can recognize darkwake correctly, and some monitors will be turned on (possibly due to usb hub). But I'm sure m1 macbook will wake up during sleep even if there is no external device. This is also the reason why many people consume too much power after sleep.

Reply

Answer 7

iCoco

Level 1

119 points

Feb 4, 2021 9:21 AM in response to Jeremy K.

Same issue here with a Dell U3421WE connected via USB-C to my new MacBook Air M1. And when returning to my computer this morning, I've had "hundreds" of notification messages telling me to properly disconnect an external hard drive - see screenshot. Totally annoying! I'm asking myself whether I shall return the Dell oder the MacBook ...

Reply

Answer 8

uttam33

Level 1

8 points

Feb 5, 2021 7:58 AM in response to chrisia777

for the time being i am planning to switch to hdmi, until the dp issues are resolved. do you have any suggestions for usb c to hdmi adaptor? currently i am using a usb c to hdmi from moarmouz it has a small indicator light which constantly glows all the time when connected which i dont like.

Reply

Answer 9

Nick2qk

Level 1

4 points

Mar 2, 2021 6:52 PM in response to Zain_A

I'm having this same issue, my LG 27UK850-W monitor cuts on all through the night unless I shutdown my M1 Mac completely. I searched for a LG Calibration Studio download but my model number doesn't show an availability. This is the only monitor that cuts on, my LG 34" WQHD give no issues. Any fix? I want to leave my Mac on sleep so that necessary downloads can take place at night, but am afraid I'm reducing the life of my computer and/or monitor screen.

Reply

Answer 10

Dec 22, 2020 2:47 PM in response to Jeremy K.

Having the same problem with the M1 MBP and the LG 38” (LG38WK95C-W). Also tried upgrading from the USB-C cable supplied with the monitor to the fancy Apple Thunderbolt 3 cable, with no luck.

Reply

Answer 11

Jeremy K. Author

Level 1

28 points

Jan 16, 2021 7:36 PM in response to cafarom

Worked totally fine on a 2018 15” MacBook Pro running Big Sur 11.0.1. Has never worked properly on my M1 MacBook Air running Big Sur 11.0–11.1.

Reply

Answer 12

Jan 29, 2021 8:04 PM in response to uttam33

I'm not sure if macos 11.1 has allows these commands. You can try them first and upgrade to 11.2RC if they are invalid.

Reply

Answer 13

Nov 29, 2020 3:12 PM in response to Jeremy K.

Hey! I’ve got the same problem with my Apple Silicon M1 MacBook Pro.

It really, really annoys me! Especially because I’m sleeping in the same room as I‘m working, and this also happens during nighttime.

Just because I‘m curious, have you ever installed the program TimeMachineEditor?

Reply

Answer 14

Jeremy K. Author

Level 1

28 points

Nov 29, 2020 6:44 PM in response to SupportLaurens

Not on the Air, no. I'm running a few other system utilities though: BetterTouchTool, Bartender, Moom, and Stay.

Coincidentally, I did have TimeMachineEditor installed on the Pro (where I wasn't having any issues), along with the above.

Reply

Answer 15

Dec 16, 2020 1:29 PM in response to Jeremy K.

MacOs 11.1 seems to solve some display issues (Macbook Air M1 + LG 49WL95C-W) but now the big problem is monitor constantly waking up and power off every 2/3 minutes when I put the MacBook on Sleep. So, I have to completely shutdown the Mac every time. Any solutions about this?

Reply

M1 MacBook Air external display keeps waking up

Similar questions