-
All replies
-
Helpful answers
-
Jan 5, 2014 10:09 AM in response to ncon64by Sandylp,Ever since I changed the power settings (pmset in terminal) on 12/21, as described below, I have had no issues. I sleep the computer every night for about 8 hours and several times during the day plugged into a power source most of the time, but sometimes not. Every time I open the lid, it wakes instantly with no hesitation. Sometimes it's attached to my 27 inch Apple monitor and sometimes it isn't. Doesn't seem to make any difference.
Power Settings for AC Power:
AC Power -1*
Currently in use:
standbydelay 86400
standby 0
womp 1
halfdim 1
hibernatefile /var/vm/sleepimage
darkwakes 0
gpuswitch 2
networkoversleep 0
disksleep 0
sleep 1 (sleep prevented by backupd-helper)
autopoweroffdelay 86400
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 15
acwake 0
lidwake 1
Power Settings for Battery Power:
Battery Power -1*
AC Power -1
Currently in use:
standbydelay 86400
standby 0
halfdim 1
hibernatefile /var/vm/sleepimage
darkwakes 0
gpuswitch 2
disksleep 0
sleep 1
autopoweroffdelay 86400
hibernatemode 0
autopoweroff 0
ttyskeepawake 1
displaysleep 10
acwake 0
lidwake 1
I also unchecked the following in Energy Saver in System Preferences:
Under Battery:
Put hard disks to sleep when possible.
Enable Power Nap while on battery power.
Under Power Adapter:
Prevent computer from sleeping automatically when the display is off.
Put hard disks to sleep when possible.
Enable Power Nap while plugged into a power adapter.
I also disabled the sleep image file: To remove the sleep image file: sudo rm -rf /var/vm/sleepimage
I have the 15" rmbp with 1TB SSD drive bought 10/2013, so I don't know if these settings would work for all computers having the issue of not waking after sleep, but it seems to be working for mine...at least for the last 15 days.
-
Jan 5, 2014 10:16 AM in response to aashishpatilby aashishpatil,I wanted to follow up on my experience.
Its been a week now and disabling (unchecking) "Put hard disks to sleep whenever possibile" has helped. Have not had to restart my machine since then.
I don't know what the implications of unchecking that option are though. Also, I don't know what this option means for SSD drives, which is what these MBPs come with. I thought this was more for the platter based drives.
-
Jan 5, 2014 10:19 AM in response to Sandylpby Supreem,Thanks for the info Sandylp, I'm real glad the cover-up fix works an all but I'm still bummed out that the fault is still lingering there, I mean let's face it if you were using your rMBP on stock Power Settings and Terminal settings (as you should be able to do) then you would still have the wake up crashing happening just as you would if you reversed those Power Settings adjustments and Terminal Settings adjustments. I'm itching to take mine into the Genius bar come Feb/March, want to get this (what I think is a hardware problem) resolved properly.
-
Jan 5, 2014 10:20 AM in response to ncon64by ncon64,WELL,WELL,WELL....just done a hardware tes as described other than ticked the box below to do an extened one.
Came up with an error message: Apple hardware detected an error : 4HDD/11/40000000 SATA (0,0)
-
Jan 5, 2014 10:26 AM in response to ncon64by Supreem,Yeah crazy hopefully this is a progressive step forward, get your MBP to the Genius bar lad and let us all know what the deal is!
I can't do an extended diagnostics one on my rMBP, I don't think you can do them on the Haswell models (or maybe it's something to do with the solid state unless yours too is SSD) as I never saw a box to tick for extended.
I'll have another look for an option to an extended now as I've done it twice recently and don't recall any such option.
-
Jan 5, 2014 10:26 AM in response to ncon64by ncon64,if you can all look back to sepreems earlier post and try a full diagnostic hardware test, if you haven't already done so. I need to know what the my error message means? i'm going to carry out another with power plugged in.
-
Jan 5, 2014 10:29 AM in response to Supreemby Sandylp,Thanks for the reply. I appreciate everyone's experiences and realize that what I did may not apply to all. I also found this from an article on the internet:
Whether you choose to keep Hibernatemode (or Safe Sleep) on or not is a matter of personal preference, but if your machine is generally plugged in and you don't run the battery down below 20%, you are never actually taking advantage of the feature. If you want to chew up the drive space and take the time for the sleep image to write anyway, that's up to you. On SSD-equipped machines, the image save time is inconsequential but the loss of storage space is even more acute.
-
Jan 5, 2014 10:35 AM in response to ncon64by Supreem,ncon64 wrote:
WELL,WELL,WELL....just done a hardware tes as described other than ticked the box below to do an extened one.
Came up with an error message: Apple hardware detected an error : 4HDD/11/40000000 SATA (0,0)
No there's definitely not an option to do an extended test on mine, I'll have to get into the Genius bar for that :/
-
Jan 5, 2014 10:35 AM in response to Sandylpby ncon64,WELL LADIES AND GENTS...google my message error and see how many peolpe have the same issue and the crap response they get from Genius bar!!!!!!
-
Jan 5, 2014 10:54 AM in response to ncon64by Sandylp,I ran Apple Diagnostics, since only computers introduced before June 2013 use the Apple Hardware Test, and there were no issues.
Also, found this on the Apple site at this link: http://support.apple.com/kb/TS4356
Mac notebooks: Apple Hardware Test may report "HDD" alert
Symptoms
When you test your Mac notebook using an SSD or Flash storage drive with Apple Hardware Test (AHT) diagnostics, you may encounter the following message if the test is looped multiple times:
- 4HDD/11/40000000:SATA
Resolution
The alert is erroneous and generally takes multiple loops of Apple Hardware Test to induce.
Before starting Apple Hardware Test, looping can be enabled or disabled by pressing the L key on the keyboard. If the message appears and there are also other issues with the computer that appear to be related to the solid state drive (SSD) or Flash storage drive, schedule an appointment at an Apple Retail Store or contact an Apple Service Provider.
-
Jan 5, 2014 1:11 PM in response to Sandylpby ncon64,Thanks for this info Sandy!!..pressed L for looping and done another test and still same message....I'd be a bit dubious of Apple puting out statements...as they do seem to be dragging their heals on certain issues. Maybe they know there is a malor issue with parts of the hardware and they'd rather fob off than actively address these issues They need to send all their customers updates of known issues relating to specific Mac products ( personalise things more ). With the amount of customers complaining about this sleep issue on this and other boards, they should have dedicated staff to look over and bring it to the top managements attention!
-
Jan 5, 2014 5:50 PM in response to ncon64by Sandylp,I agree. Please keep us updated on what you find out.
-
Jan 10, 2014 12:03 PM in response to RevCamlinby pippatron,I thought i would chip in with my experience, I bpught my new 15inch Mac Book Pro on day one october 2013.
I had the not wake from sleep issue from first day. Returned it after 3 weeks for a new retail unit with exactly the same problem, i kept it 7 weeks and eventualy returned it yesterday for a third retail unit after setting up last night it failed to wake from sleep this morning and also this evening when returning from work.
So if anybody thinks that exchanging for a new one will cure your issues i am sorry to say it wont.
The last unit is december 2012 build so i am guessing a completly different batch from the first two.
I have no idea where to go from here, i realy dont think a forth unit will be any different from the first three
so it is a refund which is not realy what i want or live with it and hope Apple fix the issue.
-
Jan 10, 2014 12:18 PM in response to pippatronby Supreem,pippatron wrote:
I thought i would chip in with my experience, I bpught my new 15inch Mac Book Pro on day one october 2013.
I had the not wake from sleep issue from first day. Returned it after 3 weeks for a new retail unit with exactly the same problem, i kept it 7 weeks and eventualy returned it yesterday for a third retail unit after setting up last night it failed to wake from sleep this morning and also this evening when returning from work.
So if anybody thinks that exchanging for a new one will cure your issues i am sorry to say it wont.
The last unit is december 2012 build so i am guessing a completly different batch from the first two.
I have no idea where to go from here, i realy dont think a forth unit will be any different from the first three
so it is a refund which is not realy what i want or live with it and hope Apple fix the issue.
Hey man I'm slightly confused with your post, you bought your laptop on "day one october", does that mean day one of the new Haswell release i.e. 26th of October, or the first day of the month i.e. the 1st of October?
Also you stated that your third replacement unit was built in December 2012?? I don't get it, you have a Late 2013 release laptop that was built 9 months ago??
My brother has a Late 2013 15" rMBP and not had a single sleep/wake crash issue, where as my Late 2013 13" rMBP some nights doesn't go to sleep properly and so is warm to the touch in the morning when trying to wake it up, which it fails at doing hence requires a hard shutdown and restart.
Point being that this problem surely doesn't effect every single Haswell release rMBP, if that was the case then this thread would be at least a hundred times bigger than it is, trust me the Late 2013 13" was released with a trackpad & keyboard freeze-up problem on release which affected every single unit and that thread was 150 pages long within the space of 2 weeks!
-
Jan 10, 2014 12:54 PM in response to Supreemby pippatron,Sorry, Day one new Haswell release date late october 2013. 3rd replacement built dec 2013.
The only issue i have is it does not wake from long sleep withput a hard reboot. It may not effect every late 2013
MBP.
This is my third late 2013 Mac Book Pro all have or had the same problem.