iOS 17.2.1 Battery Drain

After update this week to iOS 17.2.1 my iPhone 13, bought on last march, already in warranty, starts to drain the battery very fast. I’m always using the Low Power Mode ON and still draining! Can you help????



[Re-Titled by Moderator]


Posted on Dec 24, 2023 9:22 AM

Reply
122 replies

Dec 27, 2023 6:57 AM in response to tha_stela

My iPhone 13 is running iOS 17.2.1 with no battery drain issues. So are millions of other iPhone 13 users. That means there’s likely a rogue app on your phone that is slurping battery. In the past Facebook has been a big battery drainer if you keep it running in the background.


Have you also tried restarting/rebooting your iPhone 13?


Restart your iPhone - Apple Support


May 14, 2024 11:17 AM in response to iPadbatterydrain

iPadbatterydrain wrote:

Great QUESTION!! HOW ABOUT SOME ANSWERS APPLE???? OTHERWISE WHAT IS
APPLE HELP for????

This is a user-to-user support forum as was explained in the terms of use to which we all agreed when we signed up. Apple's participation here is largely limited to making sure we all follow the rules.


If you want help from Apple, use the Support link at the bottom left of every page of these forums.


Also, if you're still having issues with iOS 17.2.1, I'd suggest it's high time you update to iOS 17.5.

Jan 18, 2024 5:26 PM in response to Mac.newby

Mac.newby wrote:

ok wrong word. They were never started - and then suspended. They are available for dispatch by IOS - right?

Yes. That is a list of apps that have been used; it is only a list. It is not apps. Here is the long answer:


I’m going to try to dig into what the App Switcher is. This is based on my knowledge of operating systems in general and how virtual memory works; it probably is not 100% accurate, but should be close. 

The App Switcher does not contain apps. Essentially it is just a list of apps that have been used. I’ll call them “stubs”. Each stub contains the ID of the app, and the last state the app was in when it last ran. If the app has a code segment in RAM it also contains a pointer to that code segment. But the stub is very small, probably just a few hundred bytes (if that much). When you relaunch an app either from the Home screen or the app switcher the list is consulted, and if the app is in the list either the code segment is activated so it can resume where it left off, or if it is swapped out, it is reloaded so it can resume where it left off.


If the app is not in the list the app is started from scratch; its entry code segment is loaded, and it must run its initialization code, open its resources and then go on to its working code. This takes longer than just activating it from the app switcher, and uses more energy than just activating it from the app switcher, so for this reason killing apps unnecessarily uses more energy than just leaving them in the app switcher list. Probably not a lot more, but some.


But as they are just stubs, none of the apps in the app switcher are “running”. 


When you kill an app in the app switcher the next time it is needed it must be reloaded as I described. But also consider what happens when you kill an app. If you first exit to the Home screen, then kill it, you probably won’t do any damage, because exiting to the Home screen allows the app to save its state in storage and be in an idle state when you kill it.


Some people kill an app by going to the app switcher and killing it while the app is still “running”, rather than exiting to the Home screen first. This can have unpredictable results, because killing an app stops it RIGHT NOW, right in the middle of what it was doing. This can result in lost data. The most egregious example of this was when the “unsend” feature was added to the Mail app. A lot of posts complained that their mail never sent, and it was because they killed the Mail app from the App Switcher without waiting for the message, which was only in RAM, to send. Apple DID fix this, by saving the message to the Outbox as soon as Send was tapped, and before it was sent. The same thing can happen with Messages, if you exit directly from the app switcher, and it is also true for many 3rd party apps.

Jan 19, 2024 7:32 AM in response to Community User

-pachy wrote:

On the contrary, applications located in the application switch have background activity, which leads to greater battery consumption and completely closing some of them can increase battery life.

If you want to turn off background activity for an app, go to Settings>General>Background App Refresh. Turn it off globally or by individual app.

From my observations, I got more screen time when I had as few apps as possible in the app switcher.

But, as we all know, observations are highly subject to confirmation bias.

Jan 17, 2024 8:18 PM in response to tha_stela

I understand it is entirely normal to have quicker battery drain immediately after an update. There are a lot of update processes that continue to go on in the background after the software update. I understand thing improve after that. That's one reason why I hold off updates if I'm going out of town.


https://www.zdnet.com/article/battery-bad-after-installing-ios-17-try-these-7-tips/

Jan 11, 2024 9:39 PM in response to roc289

This happened with my iPhone 14 Pro. I just downloaded the right IPSW/firmware file on https://ipsw.me/ and did a restore using iTunes or Finder (details on https://www.howtogeek.com/694359/how-to-manually-restore-iphone-or-ipad-using-your-mac/)


Apple tried to force me to upgrade back to 17.2.1 to allow me restore via iCloud, but choosing an older iCloud backup solved that problem.

Jan 13, 2024 5:51 PM in response to tha_stela

iPhone SE 3rd gen here. Battery health 96%. Updated the day after release, and suddenly on 1/1/2024 I'm hit with the same. Battery settings show 100% usage at all times, daily battery life has capsized and phone constantly runs hot. In my case, the culprit seems to be Messages, out of nowhere, just chewing through battery in the background. This is the kind of stuff I always read about but have never experienced.



May 14, 2024 12:17 PM in response to OrangeGrapefruit

OrangeGrapefruit wrote:

Second and most importantly, Apple is known the slow down the devices when it’s time to hard push upcoming new ones. Most of the time they use the “security” updates to slow the devices, since these updates are installed more often than not.

No, in fact they are not known for that. At a point in the past, Apple started throttling phones that had dying batteries to prevent those phones from dying unexpectly. They got in trouble for not adequately publicizing that. If that happens to your phone, the solution is to replace the battery. Buying a new phone is not required (unless your phone is really old).


All lithium-ion batteries lose capacity over time. There is nothing Apple can do to change that. And security updates are to counter new security threats.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

iOS 17.2.1 Battery Drain

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.