Battery drain is a symptom, not a single metric. A phone may lose charge because the screen stayed on, a navigation session used GPS, cellular signal was weak, an app ran in the background, or the battery itself has aged. To decide whether a change worked, define the workload, collect the same measurements before and after, and account for conditions that can overwhelm a small improvement.
Define the question before the test
Choose one outcome: overnight idle loss, battery used during a 30-minute video call, active screen-on runtime, or background consumption from a specific app. Record device model, operating-system version, battery health if available, starting charge, network type, signal strength, brightness, temperature, and enabled radios. Do not mix an idle test with a heavy-use day and call the percentage difference a diagnosis.
Use the operating system as a first baseline
Apple's battery usage view compares current activity with the previous seven days and identifies app and system activity, including background use and periods of low signal. Start there before installing another monitoring app. Capture the same time window, top consumers, screen-active time, screen-idle time, and any system suggestions. Treat percentages as attribution within that period, not as laboratory-grade energy measurements.
Run a repeatable before-and-after scenario
Charge to the same level, allow the device to reach a similar temperature, close or retain the same apps, and run the same scripted steps for the same duration. Repeat each condition more than once. Compare median battery percentage lost, active time, temperature change, and the operating system's activity breakdown. Change one variable at a time, such as background refresh for one app, so the result has a plausible cause. Restore the original setting if the test makes no meaningful difference.
Use a profiler when percentages are too coarse
Android Studio's Power Profiler visualizes device power consumption and supports controlled A/B comparisons. Google cautions that device-level measurements include noise from other apps and system activity, so the result is better for comparing controlled scenarios than assigning every unit of power to one line of code. Hardware support also varies. Document the profiler version, device, connection method, start and end markers, and exact test sequence.
Decide what counts as success
Set a practical threshold before looking at the result: for example, the overnight loss should fall below an agreed range across three comparable nights, or a 20-minute navigation test should consume less charge without breaking location updates. Include a guardrail for functionality, because disabling notifications, synchronization, or location can reduce drain by removing the feature you needed. A result is useful only when the workload still succeeds.
Keep the evidence and retest
Save screenshots or exported traces, the test script, and the configuration. Repeat after operating-system, app, or firmware updates. If results remain erratic, isolate the device from optional accessories and accounts, check battery health, and seek manufacturer service guidance rather than treating a single percentage reading as proof of a faulty app or battery.
Sources
- If the battery in your iPhone or iPad drains too quickly — Apple
- Inspect power use with Power Profiler — Google Android Developers