Troubleshoot battery drain by comparing a normal period with the first period that felt abnormal, then record every relevant change in between. The change log should include app installs or updates, operating-system updates, signal conditions, travel, screen time, background activity, accessories, charging behavior, and battery-health warnings. The goal is not to disable everything; it is to find one repeatable difference.
Establish a fair baseline
Charge the device normally, note the start time and percentage, and observe it through a typical block of use. Record screen-on time, location or cellular conditions, major apps used, temperature, and the ending percentage. Repeat the check under similar conditions. A single heavy day is evidence to investigate, not proof of a failing battery.
On iPhone, Settings > Battery provides daily app and system activity. Apple explains that the details can separate on-screen and background time, and can identify low cellular coverage or notifications as contributors to battery use (Apple iPhone battery usage and health). Capture those details in the change log rather than relying on memory. Also record any battery-health message because aging capacity and software activity are different hypotheses.
Match the drain to a recent change
Sort the log by time and mark the last normal interval. Check for an app version change, new permission, background sync, navigation session, photo upload, weak signal, hotspot use, display change, or operating-system update immediately before the first bad interval. If one app dominates, note whether its use was on screen or in the background. If the phone was in a low-signal area, repeat the test on stable Wi-Fi before blaming the app.
For Android app development, Google documents that Battery Historian can correlate system and app behaviors with battery consumption, but it is no longer actively maintained; Google points developers toward system tracing, Macrobenchmark power metrics, or Power Profiler when possible (Android power analysis). That makes tool choice part of the log: record the profiler, build, device, and test scenario so two runs can be compared honestly.
Test one reversible adjustment
Choose one suspected cause. For example, pause a newly enabled background sync, correct a runaway location permission, update a defective app, or repeat the same workflow in strong signal conditions. Do not combine multiple changes in the same test. Record the old setting, the new setting, start and end measurements, and whether the symptom returned. Restore the setting if the test does not help.
Avoid deleting important data or turning off security updates just to improve a battery graph. If the device is unusually hot, swollen, physically damaged, or reports a service condition, stop the experiment and follow the manufacturer's safety or service guidance.
Close with evidence, not a guess
Consider the issue isolated only when the same condition produces the drain and removing that condition improves a comparable run. Keep screenshots or exported profiler evidence, the final setting, and the date for a follow-up check. If multiple apps show normal activity but capacity continues to fall unusually fast across controlled runs, document that result and move the investigation toward battery health, charging hardware, or authorized service rather than repeatedly changing software settings.
Sources
- Understand your iPhone battery usage and health — Apple Support
- Analyze power use with Battery Historian — Google