domains / families / software-engineering / diagnose-android-overheating
diagnose-android-overheating
authentic
Use when diagnosing Android overheating, idle heat, thermal throttling, charging or radio heat, or abnormal battery drain with read-only ADB evidence and approval gates.
When to use
- Use when an Android phone is hot, warm while idle, thermally throttled, shutting down from heat, or draining its battery unusually fast.
- Use when heat appears during charging, weak cellular signal, 5G use, navigation, camera use, gaming, media playback, tethering, or background activity.
- Use when the user wants to identify an offending app, service, wakelock, sensor, modem condition, or charging condition through ADB.
- Use when a previous Android optimization or debloat attempt may have left settings that changed power or thermal behavior.
- Use for physical phones and tablets. For profiling the energy use of an app under development, use an app-performance skill instead.
When not to use
- ADB cannot prove battery internal resistance, physical damage, charger quality, or exact internal component temperature on every device.
- Thermal sensor values and thresholds are OEM-specific; some devices hide sensors or report status incompletely.
- Battery attribution is historical and model-dependent, not a laboratory power measurement.
- USB-connected observation can alter charging, radio, and thermal behavior.
- Root-only files and vendor services may be unavailable; do not bypass device security to obtain them.
Skill page
Source