To verify battery drain after an update or major change, compare the device with its own pre-change baseline under similar conditions. Allow temporary update work to finish, record battery level over a defined period, inspect which apps and system activities consumed power, and repeat the test before blaming the update or replacing hardware.
Establish a fair baseline
Write down the device model, operating-system version, battery health or condition, starting charge, screen brightness, network type, signal quality, temperature, and the apps used during the test. Define a repeatable window, such as an overnight idle period or one hour of the same active task. Keep charging, display time, connectivity, and workload as consistent as practical. A single unusually busy day is evidence to investigate, not proof of a persistent regression.
On iPhone, Battery settings can compare current daily usage with the previous seven days and show battery use by app and system activity (Apple's battery-usage guide). Use those views to note screen-on time, background activity, notifications, and periods of low cellular signal. A changed usage pattern can explain the drop even when the update itself is not the cause.
Allow post-update activity to settle
Operating-system updates can continue setup work in the background. Apple advises that update-related tasks may temporarily affect battery life and thermal performance and recommends checking again after a few days (Apple guidance after an update). During that period, keep the device updated, connected to reliable power when convenient, and observe whether drain returns toward the baseline. Do not treat this waiting period as a reason to ignore overheating, swelling, shutdowns, or other safety symptoms; those deserve prompt manufacturer support.
Identify the consumer, not just the percentage
Review app and system battery activity for the test window. Look for an app with unusually high background time, constant location use, repeated notifications, heavy media processing, or poor-signal activity. On Android, system tracing and profilers can correlate device events and app behavior with power consumption. Google's Battery Historian documentation describes system-wide and app-specific consumption patterns, while also warning that Battery Historian is no longer actively maintained and that newer profilers or system tracing should be preferred when available (Android power-analysis guidance).
Test one change at a time
If one app or feature stands out, change only that factor for the next comparable window: update the app, stop an unnecessary background task, improve signal conditions, or temporarily disable a newly enabled feature. Then repeat the same workload and record the result. Avoid changing brightness, network, refresh settings, and several apps at once because an improvement will be impossible to attribute.
Decide from repeated evidence
A credible finding includes at least two comparable test windows, battery-activity evidence, and the exact software versions involved. If drain remains materially worse after temporary update work has settled and no app or workload explains it, preserve screenshots and timestamps and contact the device maker or app developer. If the result normalizes, retain the baseline so the next update can be evaluated against evidence rather than memory.
Sources
- About battery health and performance on iPhone — Apple Support
- Understand your iPhone battery usage and health — Apple
- Analyze power use with Battery Historian — Google Android Developers