A feature that drops and returns on a phone or tablet is usually a background battery-optimization or connection-management setting killing it, not failing hardware. For Pixel Adaptive Charging, first check the charging message, alarm schedule and device temperature with a known charger.
What this covers
- Pixel Adaptive Charging with this exact failure state
- Diagnosis across adaptive limit versus heat, alarm/schedule, cable and battery condition
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleNote how long the device was idle or locked before the drop, and whether it correlates with low signal or a Wi-Fi handoff. Expected behavior: schedule slower charging to reduce time held at full charge while meeting the expected unplug time.
Isolate the component boundary
ReversibleCheck the charging message, alarm schedule and device temperature with a known charger. Disable battery optimization for the one app and test with the device kept awake on a single network. Boundary to separate: adaptive limit versus heat, alarm/schedule, cable and battery condition.
Correct only the proven cause
ReversibleLet the schedule complete, cool the phone or disable the feature only for a required full charge. Exempt the app from aggressive battery management, or turn off adaptive Wi-Fi/cellular switching for the test.
Verify and stop safely
ReversibleRun the same use pattern that triggered the drop for at least 30 minutes without it recurring. Stop for swelling, heat, burning odor or repeated power loss.
Evidence ledger
Sources behind this answer
Exact questions