I just got a 3GS and ran it to 0, let it charge for a bit, then turned it back on. Now it's at 17% and running super slow, I can't even open contacts. Unlocking the screen takes 3 min. What the heck is going on?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Ran my new 3GS down to 0, now its super slow?!
- Thread starter patrickdunn
- Start date
- Sort by reaction score
You likely had it running on reserve - try not to run it to 0, I suppose. I would reboot it now that it has some juice in it.
I let it get that low, because I thought you were supposed to "calibrate" the battery. I don't think I will do this again. 
I let it get that low, because I thought you were supposed to "calibrate" the battery. I don't think I will do this again.
Calibration is something to do every month or so not right after getting the phone. Also, you stated you just charged it "up a bit," so I'm not sure why you didn't charge it fully.
I haven't disconnected it from the wall charger yet. It's still charging. I let it charge a bit before turning it on.
You can't, technically, without special procedures. Devices like this actually define 2%-5% as "0%" for the user in order to protect the battery and ensure it'll get back to charging without issue.
That said, you still want to keep the "full cycle" to once every 60 days or so, because you really are hurting the battery every time it dips below 10-20%. Also, try to exercise a little self-control and leave the iPhone off/alone while it charges back up to 100%.
Apple specifically recommends a full cycle every month for iPhones, they have a website for battery information you can refer to if you wish.
And to the OP, this is likely just a coincidental issue. A correctly working battery has zero influence on the speed and performance of other components. And I find it unlikely that your battery is somehow broken in such a specific and perfect way that you would be able to do anything yet have it work slowly. Chances are you've got something else going on. If a restart doesn't fix it, you'll probably have to do a restore.
