MacBook Pro Retina slow to wake when open lid

yourdream

macrumors regular
Original poster
Aug 16, 2008
148
0
When I open my lid, the screen does not come on instantly like it should. Instead, the screen comes on 5-6 seconds later. And at times there is a white screen before showing the desktop. I did a reset on SMC, NVRAM, and PRAM, but that didn't seem to help. And I've repaired the disk permissions and disk. Sometimes, when I open the lid, I hear a sound like a mount sound when the desktop shows. I have installed all updates from the App Store. And sometimes the screen just comes on instantly when I have the lid halfway open. But most of the time, when I open the lid, the screen shows up much later. Are these issues caused by a hardware problem? I am still in the 14 day return period.
 
Last edited:

questioner76

macrumors member
Apr 27, 2011
70
9
I just bought my retina last week and I have the exact same problem. My cMBP turned on instantly when you lifted the lid.
 

lordjonny

macrumors regular
Sep 18, 2006
211
1
When I open my lid, the screen does not come on instantly like it should. Instead, the screen comes on 5-6 seconds later. And at times there is a white screen before showing the desktop. I did a reset on SMC, NVRAM, and PRAM, but that didn't seem to help. And I've repaired the disk permissions and disk. Sometimes, when I open the lid, I hear a sound like a mount sound when the desktop shows. I have installed all updates from the App Store. And sometimes the screen just comes on instantly when I have the lid halfway open. But most of the time, when I open the lid, the screen shows up much later. Are these issues caused by a hardware problem? I am still in the 14 day return period.
What, if any, third party extensions do you have installed?
 

yourdream

macrumors regular
Original poster
Aug 16, 2008
148
0
What, if any, third party extensions do you have installed?
I don't have any third party extensions installed. I made a new user account and the problem is still there. Maybe I need to do a clean install on Mountain Lion? If so, how do I do it? Mountain Lion was already installed on my computer when I first got it.
 

M5RahuL

macrumors 68030
Aug 1, 2009
2,704
1,034
Colorado
Press and Hold the OPTION Key right after pressing the power button [ boot up ] This will take you in to Recovery.

It should guide you from there...Make sure you have internet [ wifi ] available! There are no install discs provided for OS-reinstalls anymore. It's all done from Apple's servers.

This should help too : http://support.apple.com/kb/HT4718
 

lordjonny

macrumors regular
Sep 18, 2006
211
1
I don't have any third party extensions installed. I made a new user account and the problem is still there. Maybe I need to do a clean install on Mountain Lion? If so, how do I do it? Mountain Lion was already installed on my computer when I first got it.

Have you checked console for errors at wake?
 

yourdream

macrumors regular
Original poster
Aug 16, 2008
148
0
Have you checked console for errors at wake?
I just did.

All messages:

2012-10-01 6:36:01.422 PM mdworker[792]: Unable to talk to lsboxd
2012-10-01 6:36:01.426 PM mdworker[793]: Unable to talk to lsboxd
2012-10-01 6:36:01.485 PM sandboxd[794]: ([792]) mdworker(792) deny mach-lookup com.apple.ls.boxd
2012-10-01 6:36:01.000 PM kernel[0]: Sandbox: sandboxd(794) deny mach-lookup com.apple.coresymbolicationd
2012-10-01 6:36:01.490 PM sandboxd[794]: ([793]) mdworker(793) deny mach-lookup com.apple.ls.boxd
2012-10-01 6:36:29.119 PM WindowServer[74]: Created shield window 0x2ed for display 0x04280380
2012-10-01 6:36:29.119 PM WindowServer[74]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
2012-10-01 6:36:29.000 PM kernel[0]: Sound assertion in AppleMikeyI2C at line 267
2012-10-01 6:36:29.000 PM kernel[0]: Sound assertion in AppleMikeyI2C_TS3A8235 at line 249
2012-10-01 6:36:29.000 PM kernel[0]: Sound assertion in AppleMikeyI2C_TS3A8235 at line 335
2012-10-01 6:36:29.000 PM kernel[0]: Sound assertion in AppleMikeyDevice at line 842
2012-10-01 6:36:29.000 PM kernel[0]: Sound assertion in AppleMikeyDevice at line 818
2012-10-01 6:36:29.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep
2012-10-01 6:36:29.140 PM WindowServer[74]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
2012-10-01 6:36:31.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
2012-10-01 6:36:31.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
2012-10-01 6:36:36.000 PM kernel[0]: Wake reason: EC.LidOpen (User)
2012-10-01 6:36:36.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
2012-10-01 6:36:36.000 PM kernel[0]: Previous Sleep Cause: 5
2012-10-01 6:36:36.000 PM kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0
2012-10-01 6:36:36.000 PM kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
2012-10-01 6:36:36.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed
2012-10-01 6:36:36.000 PM kernel[0]: en0: 802.11d country code set to 'X0'.
2012-10-01 6:36:36.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
2012-10-01 6:36:36.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
2012-10-01 6:36:36.000 PM kernel[0]: IOThunderboltSwitch(0x0)::listenerCallbackStatic - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
2012-10-01 6:36:36.000 PM kernel[0]: TBT W (2): 0x0100 [x]
2012-10-01 6:36:36.576 PM hidd[56]: MultitouchHID: device bootloaded
2012-10-01 6:36:36.000 PM kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
2012-10-01 6:36:37.096 PM configd[17]: network changed: v4(en0-:142.151.145.200) DNS- Proxy- SMB
2012-10-01 6:36:37.111 PM configd[17]: setting hostname to "*****-MacBook-Pro.local"
2012-10-01 6:36:37.309 PM WindowServer[74]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
2012-10-01 6:36:37.000 PM kernel[0]: en0: 802.11d country code set to 'CA'.
2012-10-01 6:36:37.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
2012-10-01 6:36:37.000 PM kernel[0]: MacAuthEvent en0 Auth result for: 00:0c:e6:08:32:00 Auth timed out
2012-10-01 6:36:37.000 PM kernel[0]: MacAuthEvent en0 Auth result for: 00:0c:e6:08:32:40 MAC AUTH succeeded
2012-10-01 6:36:37.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
2012-10-01 6:36:37.000 PM kernel[0]: AirPort: Link Up on en0
2012-10-01 6:36:37.000 PM kernel[0]: en0: BSSID changed to 00:0c:e6:08:32:40
2012-10-01 6:36:37.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed
2012-10-01 6:36:38.000 PM kernel[0]: AirPort: RSN handshake complete on en0
2012-10-01 6:36:38.640 PM airportd[797]: _doAutoJoin: Already associated to “utmres”. Bailing on auto-join.
2012-10-01 6:36:38.653 PM airportd[797]: _doAutoJoin: Already associated to “utmres”. Bailing on auto-join.
2012-10-01 6:36:39.245 PM configd[17]: network changed: v4(en0+:142.151.145.200) DNS+ Proxy+ SMB
2012-10-01 6:36:39.254 PM UserEventAgent[11]: Captive: en0: Not probing '****' (protected network)
2012-10-01 6:36:39.257 PM configd[17]: network changed: v4(en0!:142.151.145.200) DNS Proxy SMB
2012-10-01 6:36:39.259 PM configd[17]: setting hostname to "guest-**.ca"




Diagnostics and Usage Messages:

2012-10-01 6:36:20.479 PM Apple80211 framework[132]:
com.apple.message.domain: com.apple.wifi.timeout.scan
com.apple.message.signature: Success
com.apple.message.result: pass
com.apple.message.value: 3235.000000
com.apple.message.summarize: YES

2012-10-01 6:36:23.706 PM Apple80211 framework[132]:
com.apple.message.domain: com.apple.wifi.timeout.scan
com.apple.message.signature: Success
com.apple.message.result: pass
com.apple.message.value: 3208.000000
com.apple.message.summarize: YES

2012-10-01 6:36:28.891 PM loginwindow[52]: loginwindow SleepWakeCallback WILL sleep
com.apple.message.domain: com.apple.loginwindow.logs
com.apple.message.signature: will sleep event received
com.apple.message.uuid: 61BD6412-445F-4383-846C-E2A4549D633B
com.apple.message.result: noop

2012-10-01 6:36:28.915 PM powerd[18]: Clamshell Sleep Sleep: Using AC (Charge:100%)
com.apple.message.domain: com.apple.powermanagement.Sleep
com.apple.message.signature: Success
com.apple.message.value: 25
com.apple.message.result: Success
com.apple.message.uuid: 61BD6412-445F-4383-846C-E2A4549D633B
com.apple.powermanagement: pmlog

2012-10-01 6:36:28.916 PM powerd[18]: PID 68(apsd) Released ApplePushServiceTask "com.apple.apsd-waitingformessages-push.apple.com" 00:01:08 id:0xc000005d2 Aggregate:0x40
com.apple.message.domain: com.apple.powermanagement.Assertions
Process: 68
Action: Released
AssertionName: ApplePushServiceTask
RetainCount: 0
com.apple.powermanagement: pmlog

2012-10-01 6:36:28.920 PM powerd[18]: Clients requested wake events: [proc=powerd request=BTIntervalWaitToDarkWake inDelta=1800]
com.apple.message.uuid: 61BD6412-445F-4383-846C-E2A4549D633B
com.apple.message.domain: com.apple.powermanagement.WakeRequests
com.apple.powermanagement: pmlog

2012-10-01 6:36:28.920 PM powerd[18]: PM scheduled RTC wake event: MaintenanceImmediate inDelta=1799.99
com.apple.message.uuid: 61BD6412-445F-4383-846C-E2A4549D633B
com.apple.message.domain: com.apple.powermanagement.WakeRequests
com.apple.powermanagement: pmlog

2012-10-01 6:36:36.011 PM loginwindow[52]: loginwindow SleepWakeCallback will power on, Currenttime:10/1/2012 6:36:36.011 PM - Waketime:10/1/2012 6:36:33.240 PM = Deltatime:2.770767033
com.apple.message.domain: com.apple.loginwindow.logs
com.apple.message.signature: will power on event received
com.apple.message.uuid: 61BD6412-445F-4383-846C-E2A4549D633B
com.apple.message.value: 2.770767033
com.apple.message.value2: 0
com.apple.message.result: noop

2012-10-01 6:36:36.062 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: DRIVER_EVENT
com.apple.message.result: pass
com.apple.message.value: 27.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.065 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: DRIVER_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.070 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: DRIVER_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.078 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: DRIVER_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.082 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.084 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: DLIL_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.131 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:36.135 PM configd[17]:
com.apple.message.signature: Success
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.summarize: YES

2012-10-01 6:36:37.102 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 2.000000
com.apple.message.summarize: YES

2012-10-01 6:36:37.112 PM Apple80211 framework[797]:
com.apple.message.domain: com.apple.wifi.timeout.scan
com.apple.message.signature: Success
com.apple.message.result: pass
com.apple.message.value: 946.000000
com.apple.message.summarize: YES

2012-10-01 6:36:37.347 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:37.350 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:37.387 PM powerd[18]: Wake due to EC.LidOpen/Lid Open: Using AC (Charge:100%)
com.apple.message.signature: Success
com.apple.message.uuid: 61BD6412-445F-4383-846C-E2A4549D633B
com.apple.message.domain: com.apple.powermanagement.Wake
com.apple.message.result: Success
com.apple.powermanagement: pmlog

2012-10-01 6:36:37.389 PM configd[17]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: DLIL_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES

2012-10-01 6:36:37.810 PM airportd[797]:
com.apple.message.domain: com.apple.wifi.timeout.assoc
com.apple.message.signature: Success
com.apple.message.result: pass
com.apple.message.value: 380.000000
com.apple.message.summarize: YES

2012-10-01 6:36:38.627 PM Apple80211 framework[797]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: ASSOC_EVENT
com.apple.message.result: pass
com.apple.message.value: 1320.000000
com.apple.message.summarize: YES

2012-10-01 6:36:38.627 PM airportd[797]:
com.apple.message.domain: com.apple.wifi.autojoin.multi
com.apple.message.signature: Success
com.apple.message.signature2: NoRetry
com.apple.message.signature3: 2GHz
com.apple.message.signature4: FullWake
com.apple.message.result: pass
com.apple.message.value: 2.491495
com.apple.message.value2: 0.000000
com.apple.message.value3: 1.000000
com.apple.message.value4: -55.000000
com.apple.message.value5: -92.000000

2012-10-01 6:36:40.300 PM airportd[797]:
com.apple.message.domain: com.apple.wifi.networkReachability
com.apple.message.signature: Success
com.apple.message.signature4: FullWake
com.apple.message.result: pass
com.apple.message.value: 1.447833
com.apple.message.value2: 1.457413
com.apple.message.value3: 2.488974

2012-10-01 6:36:47.438 PM powerd[18]: PID 68(apsd) Created ApplePushServiceTask "com.apple.apsd-waitingformessages-push.apple.com" 00:00:08 id:0xc00000603 Aggregate:0x40
com.apple.message.domain: com.apple.powermanagement.Assertions
Process: 68
Action: Created
AssertionName: ApplePushServiceTask
com.apple.powermanagement: pmlog
 

wiznet

macrumors regular
May 30, 2012
165
1
Canada
Turn off "put hard disks to sleep when possible".

That's why it should only happen on battery, because on Power Adapter that option is turned off.
 

yourdream

macrumors regular
Original poster
Aug 16, 2008
148
0
Turn off "put hard disks to sleep when possible".

That's why it should only happen on battery, because on Power Adapter that option is turned off.
Do I turn that option off for Power Adapter? Because I did and the problem is still there.
 

SDAVE

macrumors 68040
Jun 16, 2007
3,381
443
Nowhere
Turn off hibernate (safesleep). You will also save space!

One downside is, if you run out of battery power while it's sleeping, it will "shut off" so you can't resume to where you were.

A good solution for that would be to always make sure your battery have enough juice to stay asleep.

I have a 256GB SSD in my 2011 MBP and it's super fast when I wake it up. And I saved 16GB of space.

http://wingedboar.net/2012/02/20/disable-safesleep-hibernation-mac-os-x/
 

yourdream

macrumors regular
Original poster
Aug 16, 2008
148
0
Turn off hibernate (safesleep). You will also save space!

One downside is, if you run out of battery power while it's sleeping, it will "shut off" so you can't resume to where you were.

A good solution for that would be to always make sure your battery have enough juice to stay asleep.

I have a 256GB SSD in my 2011 MBP and it's super fast when I wake it up. And I saved 16GB of space.

http://wingedboar.net/2012/02/20/disable-safesleep-hibernation-mac-os-x/
I've turned off hibernate mode before and did not work. I tried again, it still did not help.
 

HighEndMac

macrumors regular
Mar 30, 2011
229
1
I have a very similar issue, but with me the screen powers up instantaneously however the cursor is not present and takes up to 20-25 seconds to appear before I can actually take any action. Does anyone know what this could be?
 

leman

macrumors G4
Oct 14, 2008
10,472
4,971
Yep, mine actually boots faster than resume from sleep. Very annoying at times.
 

MRamirez181

macrumors newbie
Sep 20, 2012
7
0
I was having the same problem when I got my Retina about 3 weeks ago. I had the screen resolution at the 1920x1200 and decided to go back to the normal resolution because the images were too tiny. When I woke it from sleep the next time the issue was gone. I have not had one problem since.
 

wiznet

macrumors regular
May 30, 2012
165
1
Canada
this is useless advice for an SSD.
It obviously isn't as it fixed the issue on my Macbook with Retina Display.

The Macbook will go into a deep sleep after a certain period of time, unless it is plugged into a power adapter, or you have said option turned off.
 

S.L.

macrumors regular
Oct 2, 2012
146
25
USA
PowerNap caused this issue for me. Turned off that feature and have not had a problem ever since, even on higher res. settings.
 

thejadedmonkey

macrumors G3
May 28, 2005
8,123
1,001
Pennsylvania
This is normal, sadly. I had a 2006 Macbook Pro that would resume from sleep faster than my macbook air. Basically, the older macs would suspend and keep that data in RAM, which is very fast to read from.

Instant Wake that the new macs come with put the computer into hibernation (to save battery) and write the contents to SSD. Reading from the SSD is slower than RAM, so it takes longer.

This is the new apple: high on marketing lingo, slow on ... the startup.
 

ajcadoo

macrumors 6502
Sep 17, 2011
276
132
San Diego, CA
Keep in mind that the amount of RAM in these Macbooks are huge. When your laptop goes to sleep, all of the RAM is saved onto the SSD. Then, when you wake up, the memory is placed back onto the RAM. Sometimes, with 2-4GBs in memory, it takes a couple seconds for the wakeup to occur!
 

ReanimationN

macrumors 6502a
Sep 7, 2011
724
0
Australia
My MBP was like this from the time that I got it, until the time that I installed Mountain Lion. I'm now leaving my Mac on 10.8.0 until it dies, the instant wake from sleep was one of the reasons I bought a Mac and I now finally have it. I don't want any updates or changes to take it away from me again.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.