Battery drain is easier to troubleshoot when every observation and change is recorded. Create one dated investigation log for the device and name the person who owns the final decision. The device user supplies normal-use context; an administrator may own managed settings; a repair provider should own hardware findings. Do not record account passwords, unlock codes, or personal notification contents.
Establish a comparable baseline
Record the device model, operating-system version, battery-health reading if available, charger normally used, network conditions, and the time span being investigated. Note whether the phone was newly set up, restored, or recently updated. Google states that Pixel optimization can take weeks after setup or a factory reset and that temporary extra drain can occur after a software update: https://support.google.com/pixelphone/answer/6090599?hl=en-AU. A post-update day should not be compared casually with a stable week.
Capture charge at the start and end of a normal interval, total screen-on time, time on cellular versus Wi-Fi, signal quality, and unusual activity such as navigation or video. On iPhone, Battery settings can show daily usage compared with previous days and break usage down by app and system activity, including onscreen time, background activity, cellular coverage, and notifications: https://support.apple.com/guide/iphone/understand-iphone-battery-usage-health-iphd453d043a/27/ios/27. Save only the measurements needed to diagnose the issue.
Log decisions before changing settings
For each proposed change, record the setting's current value, the reason for changing it, the person authorized to decide, the expected effect, the test period, and the rollback value. Examples include display brightness, location access, background activity, notification frequency, cellular mode, and per-app battery optimization. Change one meaningful variable at a time when practical. Otherwise, an improvement cannot be attributed to a specific decision.
Google's Pixel guidance directs users to Battery usage to review high background or overall app use and generally recommends keeping apps optimized. It also warns that forcing essential apps or services to stop can make the phone work incorrectly: https://support.google.com/pixelphone/answer/6090599?hl=en-AU. Record the app name and measured usage before restricting, stopping, updating, or uninstalling it. Google also recommends keeping Adaptive Battery and battery optimization enabled for normal Pixel use: https://support.google.com/pixelphone/answer/10011133?hl=en.
Close the investigation with evidence
Repeat the same measurement window after each approved change. Log whether runtime, background activity, temperature, or idle loss improved and whether any required feature stopped working. Mark a change as retained, reversed, or inconclusive. Escalate for hardware evaluation when the operating system reports a service condition, physical damage is present, or controlled software tests do not explain the loss.
The finished log should show the starting condition, the evidence used, who approved each change, the exact setting before and after, the measured outcome, and the final owner. That makes later troubleshooting faster and prevents a collection of undocumented battery-saving changes from silently breaking needed functions.
Sources
- Understand your iPhone battery usage and health — Apple
- Fix battery drain problems on a Pixel phone — Google Pixel Help
- Get started with battery and charging on a Pixel phone — Google Pixel Help