After closing the lid and waiting over 10-15 minutes when I open the clamshell the screen is blank. The system is awake and you can hear alerts, and if you randomly hit keys on the keyboard you can hear stuff. Today one of my folders got renamed due to hitting all the keys to get a response.
The work around is to close it and open it again, which is not how it should work. My MacBook Pro M1 works fine and does not require the extra step of open / closing the lid to resume from a sleep.
This was a problem since day one with the Air. We followed all the "fixes" out on the web(SMC/re-install/new user)... A couple days ago it started functioning, but today it quit working again.
% pmset -g log |grep Clamshell
2022-06-24 16:05:16 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:33%) 1070 secs
2022-06-24 16:39:00 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:31%) 958 secs
2022-06-26 11:33:02 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:29%) 391 secs
2022-06-27 09:04:33 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using AC (Charge:58%) 933 secs
2022-06-28 08:57:42 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:96%) 1025 secs
2022-06-28 09:37:24 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:96%) 767 secs
2022-06-28 09:50:25 -0400 Sleep Entering DarkWake state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:96%) 0 secs
% pmset -g
System-wide power settings:
Currently in use:
standby 1
Sleep On Power Button 1
hibernatefile /var/vm/sleepimage
powernap 1
disksleep 10
sleep 1 (sleep prevented by powerd)
hibernatemode 3
ttyskeepawake 1
displaysleep 94
tcpkeepalive 1
lowpowermode 1
The difference today, it is showing DarkWake when we open the clamshell.
What can be done to either disable DarkWake or modify it so when the clamshell is open the screen is on.
Thank you,
Ed
The work around is to close it and open it again, which is not how it should work. My MacBook Pro M1 works fine and does not require the extra step of open / closing the lid to resume from a sleep.
This was a problem since day one with the Air. We followed all the "fixes" out on the web(SMC/re-install/new user)... A couple days ago it started functioning, but today it quit working again.
% pmset -g log |grep Clamshell
2022-06-24 16:05:16 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:33%) 1070 secs
2022-06-24 16:39:00 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:31%) 958 secs
2022-06-26 11:33:02 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:29%) 391 secs
2022-06-27 09:04:33 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using AC (Charge:58%) 933 secs
2022-06-28 08:57:42 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:96%) 1025 secs
2022-06-28 09:37:24 -0400 Sleep Entering Sleep state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:96%) 767 secs
2022-06-28 09:50:25 -0400 Sleep Entering DarkWake state due to 'Clamshell Sleep':TCPKeepAlive=active Using Batt (Charge:96%) 0 secs
% pmset -g
System-wide power settings:
Currently in use:
standby 1
Sleep On Power Button 1
hibernatefile /var/vm/sleepimage
powernap 1
disksleep 10
sleep 1 (sleep prevented by powerd)
hibernatemode 3
ttyskeepawake 1
displaysleep 94
tcpkeepalive 1
lowpowermode 1
The difference today, it is showing DarkWake when we open the clamshell.
What can be done to either disable DarkWake or modify it so when the clamshell is open the screen is on.
Thank you,
Ed
