dumpsys thermalservice

Syntax

dumpsys thermalservice

Examples

• dumpsys thermalservice

  Throttling severity plus every zone's temperature.

• cat /sys/class/thermal/thermal_zone0/temp

  The kernel's own reading, in thousandths of a degree.

Reading the output

IsStatusOverride: false
Thermal Status: 0
Cached temperatures:
  Temperature{mValue=32.5, mType=2, mName=battery, mStatus=0}
HAL Ready: true
Current temperatures from HAL:
  Temperature{mValue=32.5, mType=2, mName=battery, mStatus=0}
Current cooling devices from HAL:
  CoolingDevice{mValue=0, mType=2, mName=thermal-cpufreq-0}

`Thermal Status` is the phone's global throttling severity, 0 to 6. Below it, two sections describe the same zones twice — the live hardware read and the service's cached copy — so merge them by `mName` rather than listing both, or a zone appears twice at slightly different temperatures. `mValue` on a temperature is already degrees Celsius as a float; nothing needs dividing.

Output fields

What access it needs

Reading is the easy half: `dumpInternal` is gated by `DumpUtils.checkDumpPermission`, so `android.permission.DUMP` alone, which the Shell package's manifest declares. No root, no `adb root`, no developer-options switch beyond USB debugging. Writing is gated differently, and more tightly than anything else on this page. `ThermalManagerService.onShellCommand` refuses outright unless the calling uid is `SHELL_UID` or `ROOT_UID` — it does not consult a permission at all — and only then runs its shell command. That path is reached by `cmd thermalservice`, not by `dumpsys`: the service's `dump` hands its arguments to `dumpInternal`, which ignores them completely, so `cmd thermalservice override-status <n>` sets `IsStatusOverride: true` while `dumpsys thermalservice override-status <n>` quietly prints the dump and changes nothing. A phone left overridden reports a throttling severity that no sensor produced, indefinitely, and every tool reading this dump will believe it; `cmd thermalservice reset` is the way back. Read `IsStatusOverride` before you trust `Thermal Status`, in that order, every time — including on a phone you did not touch, because the override outlives the shell session that set it and the person before you may not have cleared it. The Android Sensor Tester only ever sends the read form.

Failure messages, decoded

Version and vendor notes

• Three temperature scales meet here: this dump prints degrees as a float, `dumpsys battery` prints tenths, and `/sys/class/thermal/*/temp` prints thousandths. Applying one scale's conversion to another's number is a factor-of-ten mistake that looks plausible.
• A severity number Android does not define should be shown as unknown, not rounded up to SHUTDOWN.
• Zone names, coverage and even whether the hardware layer answers at all vary by manufacturer.
• `dumpsys thermalservice reset` resets nothing. The service's `dump` passes its arguments to `dumpInternal`, which ignores them and prints the dump again; the override is set with `cmd thermalservice override-status <n>` and cleared with `cmd thermalservice reset` — the opposite of how `dumpsys battery` treats its arguments.
• The `… from HAL:` sections are printed only while `HAL Ready: true`, and the static-thresholds one is newer than the other two: absent at tag android-11.0.0_r1, present from android-12.0.0_r1.

Related commands

Commands that turn up in the same session as dumpsys thermalservice.

More System services (dumpsys) commands