Question about deep sleep

Recently I did not plug AC back in quick enough to avoid my MBP shutting down automatically because the battery was too low. In this case, after plugging back in I was expecting my MBP to wake up from deep sleep, but instead it completely rebooted. I tested and it happened again.
Has there been any change related to deep sleep in recent updates or is there a way I can change a setting so that waking up from deep sleep works properly? Please advise.

Uh oh, I finally got a chance to test out the advice in this thread: 1. using a short power button press to ensure I was not accidentally overriding wake up from deep sleep with powering up from an off state, that was not the issue. 2. Battery recalibration.
I checked for battery health:
Health Information:
Cycle count: 116
Condition: Check battery
That's pretty bad and it seems beyond rescue by battery recalibration. For the MBP, there is this step in the battery recalibration process:
"Continue to keep your computer on until it goes to sleep. Save all your work and close all applications when the battery gets very low, before the computer goes to sleep."
But now my laptop seems to lose power at the point where it should just fall asleep.
Thanks for useful info! I'll bring it to an Apple dealer.

Similar Messages

A question about sleep.

Two months ago I upgraded (perhaps downgraded is a better term, depending on perspective), anyways changed machines from my trusted 1 Ghz Powerbook G4 Ti to a White MacBook Intel 2.1 Ghz Intel Core 2 Duo.
My main question here is does the MacBook put itself to sleep when the battery reaches a certain level? My PowerBook always put itself to sleep when the battery went down to around 20% or so. But recently I have discovered that when I leave and have my MacBook running it turns itself off when the battery reaches 0% even after a smc reset and a reformat and reinstall. At least that's what it says when I plug it in and have to turn it on instead of just waking it from sleep. Is this something that is normal now or should it be going to sleep like the PowerBook did? Yes I know - just plug it in before I leave. If I know I am going to be gone a long time I do - sometimes I plan to be gone only a short time but plans change. Plus I believe everyone who can, should save energy when they can.
I have contacted apple about this problem and several others (now and then the speakers will crackle and unplugging headphones there will be no sound, and keys sticking) and they will be picking up the MB to check it out. Just curious if anyone else has had this/these problems and if you got them fixed.
*Little Rant* And I have to admit I find the intel machine a bit frustrating and I am totally unimpressed with it. (Final Cut Pro 4/5 doesn't work as well as some other costly PPC apps not working or working poorly). Yes I know, why get a MacBook for doing stuff like that - because I don't do a lot of creating anymore - generally just upkeep and small changes. Not enough to justify the cost difference.
Also I thought the increased cpu power would make it fly - but I still get the spinning beach ball a lot. Although processing short videos and animations is quicker (obviously 1 Ghz vs 2.1 Ghz) - but I wonder if the 2.1 intel is actually much faster (I mean more than a minute) than the 1.67 ppc - does anyone know?

Thanks for the input iBod.
Setting the time to go to sleep when idle is not really the problem. I've been using Macs for about 8 years now and I already know about setting the preferences. This year was my first intel MacBook and it isn't as similar as I thought it would be. Sorry if I wasn't more clear in my earlier post.
When I do leave it unattended and running it is because it is processing some stuff for me (be it a video, music, downloading, or whatever) as well as for example a project in iwork and/or photoshop is still open so I can just start where I left off when I return.
The problem I am having is (I am not sure if this is what you mean by "deep sleep") that the computer literally shuts down and I have to push the power button and the MB does a total restart (vs the Powerbook which would just go to sleep so I'd plug it in, press a key and it was exactly where I left off).
This worries me, as I know hard shut downs (which what this seems like to me) aren't good for a computer at all, plus the possible and probable data loss. It seems to be a step away from having things "Just Work" rather than a step forward.
I don't suppose you (or anyone else reading this) knows of any script, terminal setting or preference that I could use to put my MB to sleep when the battery reaches a certain low level?
About final cut 4/5 not working. I didn't mean it that it worked slowly, I meant that it won't even install. When I tried to install it gave some weird video error (can't remember clearly but it was something like 'this machine isn't equipped with agp video card (or something like that) and can't be installed'.
Thanks again for chipping in though.

My (2008) macbook pro, running 10.5.8 runs for about 30 seconds and then goes into deep sleep mode. After significant difficulty awakening, it runs for 30 seconds and....start repeating here. It did this once before about a year ago.

.....and then goes into deep sleep mode. When it (finally) awakens....it runs for about 30 seconds and.....start repeating here.
And yes, I've shut dwn and restarted multiple times, rebooted in terminal mode and run fsck, rebooted and reset the parameter ram, yadda-yadda......
Anybdy got any ideas?

Power or other problems related to unexpected system sleep, shutdown, lights or fans call for an SMC reset. Read all the steps.
Before Resetting the SMC
Try each of the following steps in this order before you reset the SMC. Test the issue after completing each troubleshooting step to determine if the issue still occurs.
Press Command + Option + Escape to force quit any application that is not responding.
Put your Mac to sleep by choosing the Apple () menu from the upper-left menu bar and then choosing Sleep. Wake the computer after it has gone to sleep.
Restart your Mac by choosing the Apple () menu from the upper-left menu bar and then choosing Restart.
Shut down your Mac by choosing the Apple () menu from the upper-left menu bar and then choosing Shut Down.
Resetting the SMC on Mac portables with a battery you can remove
Shut down the computer.
Disconnect the MagSafe power adapter from the computer, if it's connected.
Remove the battery (to remove the battery - click here: MacBook or MacBook Pro).
Press and hold the power button for 5 seconds.
Release the power button.
Reconnect the battery and MagSafe power adapter.
Press the power button to turn on the computer.
Still having problems? Replace steps 6 and 7 with the following:
Reconnect just the MagSafe power adapter.
Press the power button to turn on the computer,
Then reconnect the battery.
Resetting the SMC on portables with a battery you should not remove on your own
Shut down the computer.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if it's not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time. The power adapter indicator light may cycle off / on once.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.

Should I care about BT not available? Or... Is Deep Sleep safe??

As many others here from what I've seen, BT in not available from time to time. I would rather put my MB to sleep rather than shut it down completely. I've downloaded the Deep Sleep Widget and I'm thinking of using this every time BT becomes unavailable. It seems that BT is not available more and more these days.
I don't use BT for anything and I'm wondering if it's safe to use Deep Sleep to put MB to bed each night.
Is it OK to use DS on my MB when BT is MIA?
Thanks

So what does this mean? Does this mean that if I am
going to spawn a thread which updates a Swing
component, that any code which modifies that component
(say setText, or setLocation, etc...), I should wrap
those commands inside Runnable and pass them to
SwingUtilities.invokeAndWait()???If the code that is updating the Swing component is not actually in the Swing thread, then you do have to do that. The Swing thread, by the way, is the one that calls your ActionListeners and other component listeners like them. So you can update Swing components directly from Swing listeners, but otherwise you have to do the invokeAndWait business.
Do I only have to do this if I think there may be
multiple threads accessing the Swing object at the
same thing? I assume so...Yes. And remember that the Swing thread is one of those multiple threads; refer back to the previous comment.
An example I'm dealing with is updating a
JProgressBar. I create multiple threads at startup to
get initial values. These commands take time and it is
much faster to start them all at once rather than run
them sequentially. However, each job then increments
the JProgressBar when it completes. I figured this is
as good example as any of violating this "Thead Safe"
issue, since you have multiple threads trying to
update a single Swing component.Yes, that's a good example.

Carrying around MBP in sleep or deep sleep

I can't seem to find a recent post about this issue, or one that answers my specific question, so here goes.
Numerous posts suggest that it has always been fine to carry a MB or MBP around in sleep mode (in a bag, to and from work for example). But the guy at the Mac store here in Taipei (not sure if he has the "genius" status or not) says that this my damage the hd, as it still spins very slowly during sleep. My first quesiton is, who's right on this point?
Second, other posts suggest that deep sleep is better than regular sleep if you don't mind waiting a bit longer to wake up, in that it saves the current state to hd memory instead of RAM. My second question is, does this make it any safer for carrying the computer around without shutting down?
Incidently, I found that the original Deep Sleep widget (Deep Sleep, last update Feb. 2009) doesn't seem to work with Snow Leopard, it just keeps asking me for my admin password, even after I enter it. I did find a new one that does, however, from Axonic Labs (Axonic Labs - DeepSleep Widget - Hibernate your Mac). Let me know if you have tried a different one, and which you prefer.
Thanks!

Hi; I don't use Hibernation myself; left Sleep as is. Also; from System Preferences > Hardware > Energy Saver > Power Adapter, be sure that the box is checked by "Put the hard disk to sleep when possible." If you want to see what Hibernation mode is, and give it a try:
sleep state (DeepSleep widget can automate this):
from Rob Griffiths, Mac911: Check the current sleep state with Terminal, in Applications > Utilities. After you launch Terminal, the first step is to determine which sleep mode your Mac is currently using (in case you wish to go back to it). You can both view and change the sleep mode using the Unix program pmset. To see your current settings, type (or copy and paste)
pmset -g | grep hibernatemode
You should see something like this:
$ pmset -g | grep hibernatemode
hibernatemode 3
Great, so your machine is using mode 3, whatever that might be. Well, thanks to the documentation for the handy Deep Sleep Dashboard widget, which puts your machine immediately into hibernation mode (so you don’t have to yank all the power sources to invoke it), we can tell exactly which mode is which:
* 1 - Hibernation mode, with RAM contents written to disk, system totally shut down while “sleeping,” and slower wake up, due to reading the contents of RAM off the hard drive.
* 3 - The default mode on machines introduced since about fall 2005. RAM is powered on while sleeping, but RAM contents are also written to disk before sleeping. In the event of total power loss, the system enters hibernation mode automatically.
Once you see which mode you’re presently using, make a note of it. To Change the sleep mode setting you use pmset again: to set to the hibernate sleep mode (which is mode 1 from the above list), enter this command:
sudo pmset -a hibernatemode 1
Press Return, and you’ll be asked for your password. Provide it, and your sleep mode has been changed. If you ever wish to go back to your previous setting, just repeat the above command, but replace 1 with 3.
And yes, this means you can also set your machine to always go directly into hibernation mode by running the above command with 1 at the end. I find it much simpler, though, to use the Deep Sleep widget — and the widget also returns the hibernatemode setting to its prior value, which means that you can use the widget for hibernation, and still enter normal sleep mode the next time you simply close the lid. Note that restarting is not required for these changes to take effect.
Wrap up: Personally, I find the new sleep mode (3) a blessing, and I’ve left my machine in that mode. If you prefer the old (1) hibernate behavior, however, now you know exactly how to go there. Yes, it requires a trip into Terminal land, but it’s really not that hard to do. from Rob Griffiths
Also, RT76, carrying the MBP in a bag:
have you a hard shell custom pack?
Should the lid open accidentally while in transport, you will have a hot MBP with battery run down, when you need the MBP and take it out of the bag.
I use this: Lidwake
go to Utilities > Terminal
type in (or, copy and paste)
sudo pmset lidwake 0
then Press Return
it will ask for your password. type it in, Press Return.
Now, when your computer is sleeping with the lid closed, as you open the lid nothing happens until you press any key ...
Where's the "anykey?" Homer Simpson
To put it back, run this: sudo pmset lidwake 1
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.

5th Generation 80GB iPOD - Questions about functionality

All - I have a new 80GB video iPOD. The question I have is if I leave it just sit on my desk overnight and not plugged into my PC or power, I come in the next morning and go to use it and it seems as though it is shutdown. I press the button to turn it on, an Apple appears and it boots up. After that it appears to be fine, I am just curious if this is normal or not? Thanks in advance!

The iPod Nano and the Fifth Generation iPods have a feature called hibernation. Quote: "This allows the iPod to go into a power conservation mode after 14 hours of inactivity but resume operation in the same state as when it was last used. When the iPod wakes from hibernation, you will see the Apple logo displayed for a moment before the menu appears": iPod: About Sleep, Deep Sleep, Hibernation, and Sleep Timer

Basic questions about macbook pro + external monitor

Hi,
I have some very basic questions about using a Macbook Pro + external display. I don't actually have them but need to know how things works.
So, here they are:
1) Can I use the external display as the main display?
2) Will the external display run with its resolution or with that of the mbook pro?
3) Somewhere I read that you cannot keep the macbook pro open and get the full resolution of the external display. Is that true ?
4) Is it dangerous to keep the mbook closed while using the external display?
5) Does the usage of the external display impact on mbook performance?
I know...a lot of questions , but would be nice if someone could help me.
Thanks.

Hi - I am presently using an external display.
To answer your questions in sequence:
1. Yes you can use the external display as your main display. The way to enable that mode is to put your MacBook Pro to sleep, attach the external display. Wake up your MBPro with the lid closed and you will see the external display as you main display. You can alternatively set the external to "Mirror" your notebook by using preferences/display.
2. The external display will run at its resolution although you can adjust and calibrate it using Preferences/Display.
3. Not true. You get max resolution on both displays. Of course you may have to tweak as mentioned above.
4. Not at all. I use this mode all the time. Just make sure you initially set up as mentioned above and your LCD on the MBPro will stay off.
5. I have not seen any performance degradation whatsoever.
Hope this helps.

IMac G5 - Deep sleep - Will not wake up + Fans rev-up.

iMac G5 ( not under any recall programs and no bloated capacitors )
will not come out of deep sleep and the fans start to rev up after 1 min and
stay revved up on hi.
Tried all possible solutions:
Via keyboard : Reset pram + Open firmware
Reset SMU via power cord and the internal smu button.
Sleep light firmware is installed
Reinstalled 10.4.0 and went to 10.4.7
Tried to scare him with a glass of water, still nothing.
With iStat all temps a cool.
External fan on the PSU to keep it cooler.
Forced the iMac to have the fans on hi by booting in single user mode.
Rebooted. Fans still on hi. logged on then let it go to sleep on its own.
Monitor set at 1 min and HD at 5.
Monitor went to sleep but not the HD.
Forced deep sleep and it worked.
But Same symptoms on wakeup.
Removed the cover:
From a cold power up to video display all 3 led's light up.
http://docs.info.apple.com/article.html?artnum=301283
Deep sleep:
Leds 1 and 2 stay on, led 3 shuts off, normal .
Wake from sleep:
Led 1 and 2 are still on.
Led 3 lights up for a fraction of a second and does not come back on.
Checks the disk drive then spins down ( when a disk is present )
Checks the HD then spins down.
1 min later the fans start revving on hi.
Force reboot is required.
Symptoms started after 10.4.8 update. ( Yes I know about unsanity docks )
Coincidence? Maybe, maybe not. I wait until that fat lady sings.
Please keep this post to the specific symptoms and to PPC G5 imacs.
Has any one ( iMacs G5) with these symptoms been cured?.
How can you uninstall the sleep light firmware patch to reinstall it?
I know that it stops the fans from revving.
Any known Open firmware manual?
PM B&W G4 1Ghz Sonnet :: And still strong Mac OS X (10.3.9) If it aint broke, tweak it. If it breaks then fix it and tweak it again.

If your Mac happily goes to sleep but won't wake up--Hold down the power switch to force-reboot your machine and get it running again.
Don't worry-your Mac isn't narcoleptic. Its Open Firmware system or NVRAM (nonvolatile RAM) is likely corrupt, and your Mac can't remember how to wake up.
Restart your Mac and immediately hold down the Command-Option-O-F key combo until you see a somewhat intimidating command-line display that ends with the Open Fimware prompt. Type the following line:
reset-nvram
press the return key on your keyboard
set-defaults
press return
reset-all
press return
Your Mac will reboot. Once it's running, put it back to sleep to test. If the problem recurs your Energy Saver preferences may be the culprit. Delete the com.apple.PowerManagement.plist file (go to Finder/Hard drive/Library/Preferences/SystemConfiguration)--don't worry, your Mac will regenerate a new one--and then restart to see if that rights the wrong.
Still didn't work? Might be time to call AppleCare or see an Apple Genius or a technician.
Cheers!
DALE

Macbook Pro Retina Mountain lion freezes after deep sleep

Hello All,
I am having a strange problem with my MacBook Pro Retina, Mid 2012 (Mountain Lion 10.8.3). Since about January time It keeps crashing after I put it into a deep sleep. After closing the lid - waiting for 1 hour or so - then reopening the lid, i get presented with the normal Apple login screen (breifly) and then it crashes and i get a grey screen saying my mac has had an issue and it needs to restart.
When i log back on i get an error message that I can send onto Apple and then my Mac carries on as normal. Very weird.
I have searched these forums, been into the Apple store, spoken to Apple done hardware diagnostics, reinstalled the OS (worked breifly then stopped working again) - so i assume its one of the programs or bits of hardware that i use (which i have tried to isolate/remove)- but i am still strugling to solve these issues.
It would be great if someone could give me some advice around:
1. Where I can find these log files/error messages, etc.
2. Understanding what it is causing this issue.
Thanks in advance.

The solution is to dump the 100€ mini-display port DVI-D adapter that apple sells and buy a mini-Display to Display-Port cable for 6€. No crashes, no annoying interruption of the display (which I had several times the day for 2 or 3 seconds). There are very short interruptions now, but it is much better than with the apple adapter. The apple adapter needs a USB port, which is not necessary with the simple cable.
As for the monitor: Burn In, otherwise great. The burn in can be erased via monitor menu but should not be there in the first place.
Hope this helps.

Deep sleep/wake black flash problem of normal?

When my imac is coming out of a deep sleep such as an hour or more. When the screen wakes and the password screen comes on, it flashes off or black for a quick second then back to password screen. It does not do this during use or a quick sleep just coming out of a long sleep.
How do I fix this? Is this a major problem worth taking the imac to an apple specialist? Is it a hard drive failure.
Is this normal please help. Imac is a late 2012 27 inch model with fusion drive.

Hey there. I am having the same issue with the same computer. Sometimes my screen will stay black longer or flash multiple times as well. I have lugged it to an Apple store twice with video proof of the events happening and after multiple extensive testing the techs say they cannot find out what is causing it or reproduce the effect. For me, it does it when waking from sleep after at least 2 hours. I told them this but apparently it didn't do it in store. After much head scratching and frustration they told me they are going to replace the logic board and ram. No idea if it will work but I'd definitely contact Apple about your situation. If anything changes I'll try to post back here about it.

HT2412 iMac "deep sleep" problem

Hi, I have a iMac 27" Late 2012 and it keeps going in "deep sleep" when I leave it unattended during the day. When I come back, I have to wait for my mac to load the saved state which is quite long. I had many macs in my life and it's the first time I encounter the problem. I've seen that sleep mode before when my MacBook would be out of battery, but never on a desktop... My energy saver settings are set to never sleep (computer) and 15 minutes (display). My setting in Privacy/Advanced/Log out after XX min of inactivity is also off. I checked my hibernation mode in the terminal and it is set to 0. Out of ideas. Anyone ?
Thank you !

I have the same problem on my black MacBook. My problem is intermittent. Sometimes restart works; sometimes I'll select restart, but after the logout it never really shuts down. Black screen, glowing status indicator, completely unresponsive. I've also left it overnight with no change. The only "fix" is to do a hard shut down with the power button, whereupon I'm presented with the annoying "computer wasn't shut down properly" message on startup. No kidding! But no matter how many times I report it, no response.
I've tried resetting the power manager, I've tried zapping the pram. I've tried reinstalling the system -- I just nuked and paved this weekend, with no change. So either it's a hardware problem, or something fundamentally wrong with the OS. But since I don't hear a lot of people complaining about this one, that makes me think it's specific to my (and your) computer...
I called Apple about it while still under warranty, but got no helpful suggestions. The nearest apple store is 7 hours away, so I can't just pop in and show off my problem

Question about size of ints in Xcode

Hello. I have a a few quick questions about declaring and defining variables and about their size and so forth. The book I'm reading at the moment, "Learn C on the Mac", says the following in reference to the difference between declaring and defining a variable:
A variable declaration is any statement that specifies a variables name and type. The line *int myInt;* certainly does that. A variable definition is a declaration that causes memory to be allocated for the variable. Since the previous statement does cause memory to be allocated for myInt, it does qualify as a definition.
I always thought a definition of a variable was a statement that assigned a value to a variable. If a basic declaration like "int myInt;" does allocate memory for the variable and therefore is a definition, can anyone give me an example of a declaration that does not allocate memory for the variable and therefore is not a definition?
The book goes on, a page or so late, to say this:
Since myInt was declared to be of type int, and since Xcode is currently set to use 4-byte ints, 4 bytes of memory were reserved for myInt. Since we haven't placed a value in those 4 bytes yet, they could contain any value at all. Some compilers place a value of 0 in a newly allocated variable, but others do not. The key is not to depend on a variable being preset to some specific value. If you want a variable to contain a specific value, assign the value to the variable yourself.
First, I know that an int can be different sizes (either 4 bytes or 8 bytes, I think), but what does this depend on? I thought it depended on the compiler, but the above quote makes it sound like it depends on the IDE, Xcode. Which is it?
Second, it said that Xcode is currently set to use 4-byte ints. Does this mean that there is a setting that the user can change to make ints a different size (like 8 bytes), or does it mean that the creators of Xcode currently have it set to use 4-byte ints?
Third, for the part about some compilers giving a newly allocated variable a value of 0, does this apply to Xcode or any of its compilers? I assume not, but I wanted to check.
Thanks for all the help, and have a great weekend!

Tron55555 wrote:
I always thought a definition of a variable was a statement that assigned a value to a variable. If a basic declaration like "int myInt;" does allocate memory for the variable and therefore is a definition, can anyone give me an example of a declaration that does not allocate memory for the variable and therefore is not a definition?
I always like to think of a "declaration" to be something that makes no changes to the actual code, but just provides visibility so that compilation and/or linking will succeed. The "definition" allocates space.
You can declare a function to establish it in the namespace for the compiler to find but the linker needs an actual definition somewhere to link against. With a variable, you could also declare a variable as "extern int myvar;". The actual definition "int myvar;" would be somewhere else.
According to that book, both "extern int myvar;" and "int myvar;" are declarations, but only the latter is a definition. That is a valid way to look at it. Both statements 'delcare' something to the compiler, but on the second one 'define's some actual data.
First, I know that an int can be different sizes (either 4 bytes or 8 bytes, I think), but what does this depend on? I thought it depended on the compiler, but the above quote makes it sound like it depends on the IDE, Xcode. Which is it?
An "int" is supposed to be a processor's "native" size and the most efficient data type to use. A compiler may or may not be able to change that, depending on the target and the compiler. If a compiler supports that option and Xcode supports that compiler and that option, then Xcode can control it, via the compiler.
Second, it said that Xcode is currently set to use 4-byte ints. Does this mean that there is a setting that the user can change to make ints a different size (like 8 bytes), or does it mean that the creators of Xcode currently have it set to use 4-byte ints?
I think that "setting" is just not specifying any option to explicitly set the size. You can use "-m32" or "-m64" to control this, but I wouldn't recommend it. Let Xcode handle those low-level details.
Third, for the part about some compilers giving a newly allocated variable a value of 0, does this apply to Xcode or any of its compilers? I assume not, but I wanted to check.
I don't know for sure. Why would you ask? Are you thinking of including 45 lines of macro declarations 3 levels deep to initialize values based on whether or not a particular compiler/target supports automatic initialization? Xcode current supports GCC 3.3, GCC 4.0, GCC 4.2, LLVM GCC, CLang, and Intel's compiler for building PPC, i386, and x86_64 code in both debug and release, with a large number of optimization options. It doesn't matter what compiler you use or what it's behavior is - initialize your variables in C.

Macboor air 13 late 2010 freezes when wake from deep sleep

Hi. I have had this problem for a few months and still havent found a solution. This macbook air freezes and is totally unresponsive for five or six seconds when it wakes from deep sleep. I have tried:
1 Apple hardware test, which came up negative. No hardware problem detected
2 reset the SMC several times. No fix.
3 repaired permissions in disk utility, and also verified and repaired disk. Still no results.
4 restarted many times.
5 tried booting in safe mode, but it made the machine hang.
The only thing I havent tried yet is resetting the PRAM. in the event that that doesnt work, does anyone have any ideas. I only found thre

I think it might just depend on how often your machine does this. My MBA 13 has done what you are describing one or twice, but its a rare event. I'm not too worried about it, but you might want to contact AppleCare and see if they have any more information...
Sly

MacBook always needs to be woken from deep sleep twice

Whenever I wake my MacBook Pro (mid 2012) from "deep sleep"/"hibernation", it wakes up with the gray loading bar and brings me to the login screen as usual, but the keyboard and mouse remain unresponsive. The cursor is blinking in the "Enter Password" field and everything, but it won't recognize any input at all. It remains this way for 2 or 3 minutes, and then it shuts off again. Not just goes back to regular sleep, but back to "deep sleep", so I have to press the power button again, I get the mac chime, and the gray loading bar again, and this time it does this same thing but after about a minute it will suddenly start recognizing mouse and keyboard input.
What's up with this? Is it some driver that's taking a very very long time to load or something? This happens 100% of the time, every single time I wake my MacBook from deep sleep, without fail. Please help, this is extremely inconvenient.

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

IPod gets stuck when it starts play mostly after deep sleep

Hi,
I have a problem with my 60G Video iPod:
Most of the times it gets stuck completely when I start use it after deep sleep (it hasn't been used for night etc.).
The problem is very consistent:
1. I turn it on.
2. Start playing some song.
3. See the 'normal' play screen (song timer is 0:0)
4. Hear spinning and clicks of hard drive and ....
5. It just freezes: doesn't response to any key (including Hold)
Only Reset helps now and when I generally get Folder icon with exclamation point and
it needs at least another reset to be able use it.
I updated iPod to the last version (1.1) - doesn't help.
It passed through Restore - same results: Every second turning on it gets stuck.
Does anybody have/know about similar behavior?
I think I have to ask Yeda for help?
Any ideas?
Thanks
vov

Welcome to Apple Discussions!
Have you tried this, even though the folder isn't always there?
iPod Displays A Folder With An Exclamation Point
btabz

Question about deep sleep

Similar Messages

Maybe you are looking for