Since the customers have reported sub-optimal battery performance. Not only in standby time (Apple’s iPhone specs comparison chart notes that the 4S offers 200 hours of standby time, while previous models offered 300), but in daily use as well. The UK’s Guardian newspaper reports that some users have been directly contacted by engineers (!) who are trying to suss out the issue.4S was released, several
Today, Erick Schonfeld reports his experience at Tech Crunch. Despite moderate use during an 8-hour work day — about two-and-a-half hours of Internet and email and roughly 30 minutes of calls — his iPhone’s battery had died. If the iPhone saw hands-on activity for about three hours, according to Erick’s anecdotal observation, it spent about 5 hours sitting idle.
As Erick notes, the phone was “…constantly bleeping with notifications and emails. And that may very well be the problem.” Often a “resting” iPhone is in fact doing something, and it’s possible that very frequent notification alerts can contribute to battery drain. Per the Guardian story, problematic contacts may also be to blame (see Chris Breen story below).
While we wait and see if anything official will come from apparently widespread problem, here are a few general tips you can use for preserving battery life on an device. You won’t suddenly run 12-hour days after trying these things out, but every bit helps, right?on this
- Lower screen brightness. A blazing screen equals a blazing battery. Move that slider a bit to the left.
- Reduce alerts you don’t need. Yes, push notifications are wonderful as are their corresponding beeps. Just look at how many you’ve got enabled and whittle it down to the essential.
- Enable quick screen locking. You can typically let the display go to sleep when you aren’t actively using your iPhone.
- Enable Airplane mode when offline. It kills Wi-Fi and data dead. Plus it’s polite to whomever you happen to be talking with.
- Reduce email checking. Do you really need to see a new message every five minutes?
- Make sure you’re not synchronizing massive mail folders you don’t actually need on the go, like Sent, Drafts or Junk.
- Try de-synchronizing your Exchange, iCloud or Google contacts and seeing if that improves matters — you may have a corrupt contact record in there.
Admittedly these tips are common sense stuff and probably won’t address more specific issues others are reporting. For example, the folks at iDownloadBlog suggest that the Time Zone setting could be a problem and describe a way to test your own device (note that they tested the and 3GS, not just the 4S), while Christopher Breen discovered that an errant contact was causing a battery-draining crash loop while trying to sync to iCloud.
If you’ve found any helpful tricks, please share in the comments.
Battery Life Sucks? Try Disabling Location Services
We’ve covered a handful of tips to increase battery life in iOS 5 and even for the new iPhone 4S, but nonetheless the complaints about battery drain are still piling up. The culprit for the 4S is almost always Location Services, and all you need to do is disable a few things:
- Tap on “Settings” and go to “Location Services”
- Selectively disable Location Services for services you don’t use, like Reminders, before proceeding
- Next, tap to “System Services” and switch the following to OFF:
- Compass Calibration
- Diagnostics & Usage
- Setting Time Zone
- Close out of Settings
The Reminders feature combined withis great and obviously helpful, but it seems to constantly query the location of the iPhone, presumably to try and determine where the thing is and if a reminder should be triggered. Turn it off if you’re concerned about battery life.
The other part is ‘System Services’, which the items highlighted in the screenshot below seem to be the biggest offenders hat constantly ping location (with the exception of iAds, which took an unlucky spot). Many reports indicate that disabling just “Setting Time Zones” alone will save considerable battery life.
Is the sometimes dodgy iPhone 4S battery life a result of bug in5? Will it be resolved with an .0.1 update?