Battery problem after update to IOS 9.3.1

I have the same problem - so frustrating

Started 100% - used for an hour and a half - on run

Died as I walked back into the house

Plug in then straight back to 73%

There is something wrong here and it needs fixing

I have also same problem but not found solid solution and I sold it. Now I will buy new phone with latest version.

<Link Edited by Host>

I have been using iphones for over the years since they just named the phone iPhone, then 3Gs and so on and now I am holding iphone 6. Apple have my apple id and they can track how many Apple devices I have been using. I am a loyal kind o customer. But, one thing that I noticed from the past 2 years now, prior to iphone releases, Apple always release newer iOS version and suddenly the battery of the existing iphones drain much quicker. It feels so suspicious that my feeling Apple is driving people to buy their newer phone due to the older ones gets unreliable. Is it really battery problem or software tricky problem... Apple, is it true?

There is a discussion that may related to my issue is this article at: https://discussions.apple.com/thread/7516885?start=135&tstart=0

and unfortunately I found no answer from Apple. Contacting such big corporate like Apple is not an easy matter, unfortunately get this message into viral on social media sometime helps to get Apple's attention. Hope Apple catch this message and listen to the customer complaints.

I recently had this issue after updating to iOS10 and thought that was the cause of my battery draining from 100% to less than 10% (or dead) overnight with little use. It took a few days until I realized that it probably wasn't the update. My ESPN app started downloading ALL podcasts to my phone during the night time and that was draining my battery. I suggest going to settings-->battery and check Battery Usage. Make sure to tap the little clock icon next to "last 7 days" to see what is using your battery so much in the background. That's how I found my issue (ESPN app 8.8 hours in the background).

You should consider plugging the phone in overnight. If you don't, any data usage will be cellular, because WiFi is disabled when the phone is asleep and not connected to power. In addition, if you enable automatic backups, the phone will automatically back up over WiFi every night. As a bonus the phone will have a full charge every morning.

I'm having the same issue

As you could not possibly have updated to 9.3.1 at this time you do not have the same problem. You would get a more helpful response if you posted your own problem in a new message.

My error. Thank you for the helpful suggestion

this is absolutely an OS problem, mine dies at 39%

According to this thread it was an OS problem for 9.3.1. Are you saying you have a problem with 9.3.1, which is way out of date?

Hi Lawrence... my bad, I did not see it was thread for 9.3.1, either way a friend of min and myself are having this exact issue with 10.1.1 which I believe is the latest update. I'm trying to see if someone else is experiencing this same issue and if there is any fix to this yet.

There's a hint as to the issue in that. Every time there has been an update over the past 9 years a few people report a change in battery performance. It happened with 2.0, 2.1, etc all the way up to the current version. So every version of iOS must have been defective over the past 9 years, or there needs to be another explanation. It should be clear it isn't the version, because over 200 million people updated to it, and there aren't 200 million posts about it. or even .001% of 200 million.

Sometimes when you update iOS, apps that are not well designed "break" and get confused by the update. They try to complete data operations that were in progress during the update that were interrupted. To fix the problem you need to identify the corrupt app and try resetting it. You can get a good hint from Settings/Battery.

Hi

There is an iPhone 6s Program for Unexpected Shutdown Issues.

The program covers iPhone 6s devices within a limited serial number range that were manufactured between September and October 2015.

Apple advises that, if you have experienced the issue, you should visit an Apple Retail Store or an Apple Authorised Service Provider to have your iPhone examined and the serial number checked to confirm your eligibility for a battery replacement, free of charge.

More information and instructions:

https://www.apple.com/support/iphone6s-unexpectedshutdown/

I too have had these problems, except mine seemed to originate with 9.3.3 or perhaps 9.3.5. I've documented them in a different thread: Daemon recentsd using > 90% CPU and battery draining on iPhone 5s despite remedial efforts

However, my problem does not seem to involve identityservices which appears to be operating normally. Instead, recentsd races at 90+% of CPU, seems to consume as much memory as is available, crashes, and restarts, doing the same thing every 10 or 20 seconds, leaving behind a slew of Jetsam crash reports.

Having found part of this thread, I followed one lead to turn off "Calls From iPhone" in FaceTime Preferences on each of my Macs, with temporary symptomatic relief. But the recentsd crashes have started again, the phone is heating up, and battery drain continues.

I have avoided robnbill's and the Genius Bar's recommendations to follow the nuclear option. I too tried "reset all settings" to no avail. Updates of iOS have had no effect. But it looks like DFU is the only remaining choice.

I finally exercised the Nuclear Option, DFU restore to New Phone per @robnbill's suggestion. So far only a few hours experience, and quite a bit of energy was used during the Restore and subsequent reconfiguration of settings. Also, I have not yet reloaded all my apps, and I've only configured one email service.

But at least the recentsd crash cycle is gone.

I had asked in my other thread what recentsd does. In OS X it tracks recent iCloud activity. I suppose it does the same in iOS.

This is a sample of the trace after unsuccessful application of all the remedial actions. Notice the 98.1% CPU, the huge (and growing) real memory burden (156+MiB). Also notice the crash reporter just initialized, and the cycles of free physical memory dropping to near-zero, then after recentsd crashes, it is restored. About every 20 seconds in this instrumentation run. The flags in the timeline report low-memory warnings associated with each crash. Notice also the high PID! The result of respawning this daemon plus ReportCrash 10,000 times since the last power cycle.

Now compare a sample of the trace after DFU restore.

Now recentsd is well behaved. Typically running at zero CPU load. When using the cloud (e.g. using iMessage or photos or anything else monitored in the cloud), it perks up, perhaps running with as much as a few percent of the CPU, but usually only sitting in the background. Notice the PID, the original PID; it hasn't been respawned because of crashes. And total CPU load is what it might be expected to be, 5% (over instrumentation's current 10%) when the phone is quiet, jumping only when waking up the phone. The two flags here are when waking up messages and sending a message with a photo.

So far so good. But I'm sad that DFU restore "to new" cleaned out my message history, any personalized spelling dictionary (when sending that message, my iPhone didn't know a trade name that I've used over and over again and which it had learned -- that's something that should be in the cloud!!).

Also, I have not yet reinstalled many of the heaviest lifters among my apps. No NYTimes, no WSJ, no Google maps, no IMDB. And I have not yet connected to Google mail, which has tens of thousands of messages.

I had thought it possible recentsd was somehow hanging up on my huge message cache -- I retain 1 year, possibly 20 MB -- or my huge email cache. The last thing I did was to kill about half of my Google mail messages, moving them into a local folder in Thunderbird on my Mac, and deleting them from the IMAP server. That had no noticeable effect. So, hence the nuclear option.

I will report back how it holds upon reloading other apps and accounts.