Hey everyone,
I've been having a really frustrating issue with my iPhone 13 over the past couple of weeks. The battery seems to be draining much faster than usual, even when I'm not using it heavily. I've tried the usual suspects like checking battery usage by app, but nothing is obviously consuming a huge chunk.
Here's what I've tried so far:
- Restarted the phone multiple times.
- Checked Battery Health (it's at 98%).
- Ensured iOS is updated to the latest version.
- Reduced screen brightness and disabled background app refresh for non-essential apps.
- Checked Location Services settings.
It's particularly bad overnight. I'll charge it to 100% before bed, and wake up to find it around 70-80%, even with Airplane Mode on. Has anyone else encountered this, and more importantly, found a solution? Any advice would be greatly appreciated!
Comments (5)
Hi John, I'm experiencing something similar. It started after the last iOS update for me. Have you checked if "Other" usage in Battery settings is unusually high? Sometimes rogue processes can cause this.
I had this issue on my iPhone 12. For me, it turned out to be an app called "Smart Home Control" that was constantly trying to connect to devices in the background, even when I didn't use it. Try uninstalling any newly installed apps one by one and see if that helps.
Thanks for the suggestions, Alice and Robert! I'll definitely check the "Other" usage again, Alice. Robert, that's a good point about new apps. I did install a new smart home app around the time this started, I'll try removing that first.
One more thing to check: Settings > General > iPhone Storage. Sometimes an app can get stuck in an update loop or background process that isn't obvious in the battery usage graph. Also, consider resetting network settings (Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings). It won't delete your data but might fix connectivity-related battery drain.
Update: I uninstalled the smart home app, and overnight the drain was much less! About 5% lost. It seems that was the culprit. Thanks, Robert! I'll keep an eye on it, but this is a huge improvement.
Add a Reply