feat(droiddeckctl): thermal and wait cool

Nothing in droiddeckctl reported temperature, so a before/after
comparison could start one run hot and the next cold.

`thermal` reads the battery temperature from dumpsys battery, the
thermal status from dumpsys thermalservice, and each CPU policy's
scaling_max_freq against cpuinfo_max_freq (capped when lower), all
readable over plain adb. `wait cool --below <C>` polls it every 10 s
until the battery is under that temperature, or exits 5 at --timeout.
This commit is contained in:
angelrenefm committed 2026-11-04 00:13:31 +01:00
1 parent f3650d3d37
commit 8e480d0e84
3 files changed
+126 -3

No files matched your search

+8 -1
View File
@@ -26,7 +26,7 @@ and reports every run.
Player controls and observations work over authorized ADB on any build: `state`, `start`, `stop`,
`resume`, `wait`, `launch`, `quit`, `focus`, `input`, `ui`, `logs`, `screenshot`, `record`, `pacing`,
`displays`, `wake`, `glasses` (except `glasses raw`), and `access`.
`thermal`, `displays`, `wake`, `glasses` (except `glasses raw`), and `access`.
**Setup > Diagnostics > Debugging tools** is off by default in every build, including debug builds.
It enables `run`, `guest`, `cdp`, all `env` operations, `override`, `prefs`, and `glasses raw`. The
@@ -125,6 +125,8 @@ tools/droiddeckctl screenshot ./screen.png --display 4
tools/droiddeckctl xr-frame ./xr-capture
tools/droiddeckctl record ./clip.mp4 --seconds 8 --display 0
tools/droiddeckctl pacing --seconds 30
tools/droiddeckctl thermal
tools/droiddeckctl wait cool --below 38 --timeout 900
tools/droiddeckctl displays
tools/droiddeckctl wake
@@ -162,6 +164,11 @@ the present-to-present histogram and the share of intervals off the usual cadenc
counter counts frames handed over, not frames shown, so it can read 60 while one frame in four
stays on screen for two refreshes.
`thermal` reports the battery temperature (`dumpsys battery`), the thermal status
(`dumpsys thermalservice`, 0 NONE to 6 SHUTDOWN) and each CPU policy's `scaling_max_freq` against
its `cpuinfo_max_freq`, with `capped` when the first is lower. `wait cool --below <°C>` polls it
every 10 s until the battery is under that temperature, so runs being compared start equally cool.
`input` needs a session that has drawn its first frame. Pad input goes through the session screen's
virtual pad, the same one the on-screen controls drive, so games that ignore touch still respond.
`launch`, `quit` and `cdp` need a Steam session; `focus` and `wait focused` need gamescope (every