When my MacBook Pro i7 runs out of battery, it powers off.

About four or five days, I restarted the SMC (two times) and PRAM (listening the inicial sound three times), each after a start in "normal" mode. After that, the system stores the information as is supposed when the battery runs out.

I went yesterday to the Genius Bar anyway. The technician said that what is described in this thread is not normal. Diagnostic tests performed (not included in installation Disk 2, but others) and and all were passed. He told me to continue looking at the computer.

A greeting.

I am having the same issue and I have lost a lot of work because of it. I am not liking my i7 Macbook Pro because of this problem which is CLEARLY not an isolated incident with a single user.

Same here. I took my 1 week old laptop to an apple specialist in Berlin about this same problem. 1 guy said it's expected behaviour to which i replied, that's rubbish, none of my last 4 macbooks/powerbook did that and my wife's new one doesn't either. then they did a battery check which came up good. they told me to re-install the OS completely because I had migrated from an older intel core 2 duo laptop. i haven't had time but i will......and getting through to applecare in Germany to organise a refund is an hilarious ordeal. usually it takes between 10 and 20 minutes to even speak to someone, never mind get put through to aftersales.

sorry, here's my updated signature. this all happened this week by the way.

This has begun happening to me as well, Macbook Pro 15" i7 '10

they're basically woefully poorly made these days and applecare (berlin) is an hilarious joke. i was told to expect this behaviour. the last 5 mac laptops i have had (and my wife's current one) do not have this fault. when i run out of battery power and i immediately plug the power supply back in, i have to wait up to 2 or 3 minutes while the computer starts up but usually with the long oval bar on the gray screen.....not even the usual start up. really great hardware.....
also i get the noisy clicks under and to the left and right of the trackpad. next one's a Sony.......back to windows

Hi,

I agree with moccasynth. It is a behavior that rarely happens in other MacBook or MacBook Pro models, and even in Notebook PCs. Recently I have detected the noisy clicks at the bottom of laptop ( http://discussions.apple.com/message.jspa?messageID=12641998#12641998). I think that both situations should not happen.

My question has to do with if anyone knows some mechanism to ask directly to Apple for some massive solution in this respect, as a Repair Program, for example.

I dont get it, is this an isolated incident or does every 2010 core i5/7 MBP suffer from this exact issue? So far I have not come across anyone who owns a core i5/7 MBP that skips sleep mode completely and goes directly into hibernation when the batteries are drained! So, unless someone who has a core i5/i7 MBP that goes to sleep instead of hibernation when the batteries are drained, I am going to consider this strange behavior as a feature that for some strange reason is not documented by Apple. I guess they just have other priorities these days!

For what it's worth I'm also experiencing the same problem. Battery hits 0%, computer goes to sleep, saving the contents of RAM to the hard drive, then powers off after a minute or so. The screen turns grey when booting back up, as if it's going to restore the previous session, but then quickly turns black and the computer starts up from scratch.

I tried resetting the NVRAM, PRAM, and SMC to no effect. An archive and install of Snow Leopard also failed to fix the problem for me. Anyone have any other ideas? Could this be a hardware problem, or is it something in the software?

Is there anyone with one of these new Macbook Pros whose computer actually restores the previous session when booting back up after their battery ran out, or is this a widespread problem?

Hi,

I had the problem constantly at the beginning, when I received the computer, but stopped after restarting several times the SMC and some calibrations of battery. Today happened again, but, I suppose, for the same calibration of the battery.

From Apple service of assistance somebody once told me that might have to do with the latter, the battery calibration or the system of recognition of the state of charge (recognize more charge of that actually exists, although Mac OS X shows 0 percent of charge). It would be something eminently of hardware, but not something specific to some MacBooks Pro, because after changing some components in some computers, apparently, the problem has persisted.

Let us hope any response from Apple.

fat chance, they won't acknowledge a problem after this long. last mac i buy. the macbooks (at this rate) are going to fall victim to to what's happening to the iphone vs android. now where's a googlebook pro when you want one?

Hey guys.
Macbook pro 13" mid-2010 here.
Experiencing the same shutdown instead of sleep problem.

Same problem here. Computer saves memory to disk and shuts down immediately when battery is drained to 0% - every time.

I have a mid-year 2010 MacBook Pro Core 2 Duo running OS 10.6.5

I do not know if it have something to do, but for some time, regardless of the involvement of battery level charge detection, some people argued that the system sometimes did not enter to Sleep, SafeSleep or Hibernation mode when remote storage software or services didn't not allow it (like MobileMe or DropBox).
In my case, since I got the MacBook Pro configured MobileMe. The situation is that some reconfiguration of the service, added the following files in the folder LaunchAgents in /Library:

/Users/(User)/Library/LaunchAgents/com.apple.MobileMeSyncClientAgent.plist
/Users/(User)/Library/LaunchAgents/com.apple.ReportCrash.Self.plist
/Users/(User)/Library/LaunchAgents/com.apple.SafariBookmarksSyncer.plist (It, probably related to instances that are synchronized)
/Users/(User)/Library/LaunchAgents/com.microsoft.LaunchAgent.SyncServicesAgent.p list (For Office 2011)

The system stores information when the battery runs out and returned correctly when it turn on to its previous state. I associated it to the repeated reset the SMC, but the last time the process don't returned well I had cleaned that folder. I returned to join the files and the last time made the process correctly (I have not done too many tests, because I expected a relatively complete charge and discharge of the battery to do so).

I don't know if it have relation of if it is a production of random. I share it anyway.

Finnaly, it doesn't solve the problem.