ByteScope

dumpsys thermalservice

read-only

Whether the phone is throttling, and every thermal zone the hardware layer reports, in degrees Celsius.

Command
adb shell dumpsys thermalservice
Commands
System services (dumpsys)
Risk
read-only

Syntax

dumpsys thermalservice

Examples

Reading the output

Sample 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

FieldMeaning
Thermal Status0 NONE, 1 LIGHT, 2 MODERATE, 3 SEVERE, 4 CRITICAL, 5 EMERGENCY, 6 SHUTDOWN.
IsStatusOverrideTrue means the status was injected for testing and is not measured.
mValue (Temperature)Degrees Celsius as a float. `NaN` is the documented "no reading" sentinel.
mNameThe vendor's own zone label. Match it against your device's datasheet; it is not standardised.
mStatusThat zone's own throttling severity, same 0-6 scale.
mValue (CoolingDevice)A driver-defined state — a cpufreq step, a fan index, a duty cycle. It carries no unit.

Version and vendor notes

We have a UI for this

Android Sensor Tester runs this command over USB and parses what comes back — a Chromium browser, no SDK, nothing uploaded.

Open Android Sensor Tester

Related commands

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

CommandWhat it does
dumpsys batteryThe battery service's live state: level, status, health, voltage and temperature.
topA one-shot process table: CPU share, memory, state and command line.
dumpsys meminfoWhich processes are using the most memory, measured as proportional set size.

More System services (dumpsys) commands

CommandWhat it does
dumpsys diskstatsFree space per partition, a disk write latency check, and a cached per-app breakdown of what is using storage.
dumpsys sensorserviceEvery sensor the phone has, with its vendor, type, rates and batching — plus a buffer of recent readings.
dumpsys packageEverything the package manager knows about one app: version, paths, flags, install source and per-user state.
dumpsys activity activitiesWhich app is in the foreground, and the task and stack structure behind it.
dumpsys dropboxThe platform's ring buffer of crashes, ANRs and tombstones — how you read ANR traces without root.

Checked against AOSP, toybox and kernel sources while writing the parsers behind our Web ADB tools. Where a behaviour genuinely varies by Android version or manufacturer, this page says so instead of giving a number that would be wrong on half the phones out there.

Frequently asked questions

How do I run an adb shell command?

Switch on developer options and USB debugging on the phone, plug it in, then run `adb shell <command>` from a machine with platform-tools installed — or run `adb shell` on its own to get an interactive prompt and type the command without the prefix. If the command produces binary output, such as a screenshot, use `adb exec-out` instead of `adb shell`: the plain shell service attaches a terminal, which rewrites newline bytes and corrupts the data.

Do adb shell commands need root?

Not the ones on this reference. They run as the `shell` user, which can manage packages for its own Android user, read most `dumpsys` services, write the settings provider, inject input and read shared storage. Root is only needed for things this reference deliberately avoids — reading another app's private data (except through `run-as` on a debuggable build), writing system partitions, or reading `/data/anr` directly.

Why does the output look different on my phone?

Either the Android version or the manufacturer. Some flags and fields arrived in a specific release, and those are noted per command. The rest is OEM patching, which hits `dumpsys` hardest: a dump is debug output whose text is whatever the service author last printed, and manufacturers change it and backport their changes. Read fields by name rather than by position, and treat an unfamiliar shape as a difference rather than as a failure.

Can I run this from a browser instead of a terminal?

For many commands, yes — the Web ADB tools on this site talk to a phone over WebUSB from a Chromium-based desktop browser, with no SDK installed and nothing uploaded. Each page links to the tool that runs its command, when one exists. Two limits are worth knowing: only one program can hold the ADB interface at a time, so a desktop `adb server` has to be stopped first, and `adb forward` and `adb reverse` cannot work in a browser at all.

Would rather click than type? The Web ADB Toolkit runs commands like this from a browser over USB. Or browse every command.