Skip to content

t1k:adb-capture

FieldValue
Modulet1k-multimodal
Version2.10.46
Effortlow
ToolsBash, Glob, Grep, Read, Write

Keywords: adb capture, adb input tap, adb screencap, adb screenshot, android device screenshot, android emulator capture, bluestacks, competitor game ui capture, emulator screenshot, ldplayer, waydroid, waydroid android, waydroid capture, waydroid emulator, waydroid screenshot

/t1k:adb-capture
<game or screen to capture> [device serial]

ADB Capture - screenshot an Android game’s UI over adb

Section titled “ADB Capture - screenshot an Android game’s UI over adb”

Drive a game on an emulator or USB phone with adb, saving one PNG per screen for design or competitor research. Read-only exploration: look, never buy, never sign in.

Executed inline by the session that holds the task (Bash only); no sub-agent needed.

  • Never tap a purchase or price button, never spend premium currency, never confirm an in-app purchase.
  • Never log in or type credentials of any kind (store, social, game account).
  • A payment sheet or system dialog appears: press back (input keyevent 4), record it in the notes, move on.
  • Ads: wait for the close button or press back. Never tap through to an install page.
  • Anything irreversible (delete save, reset, gift/claim that costs): skip and note it.
  1. Locate adb. Prefer adb on PATH; else the emulator’s bundled adb.exe (LDPlayer, BlueStacks and Android Studio each ship one — Waydroid does not; the host’s adb connects to its session). Paths and ports: references/emulators-and-commands.md.
  2. Connect. adb devices; when the emulator is absent, adb connect 127.0.0.1:<port>. More than one device: pass -s <serial> on every call.
  3. Check geometry once. adb shell wm size (and wm density); tap coordinates are in these pixels.
  4. Capture. adb exec-out screencap -p > <dir>/NN_<screen>.png. exec-out is binary-safe. Never pipe adb shell screencap -p through a text pipe on Windows: the CRLF translation corrupts the PNG.
  5. Navigate. adb shell input tap X Y, input swipe X1 Y1 X2 Y2 [ms] (scroll, long-press with equal endpoints), input draganddrop, input keyevent 4 (back). Wait 1-2 s after each action before capturing.
  6. Verify each PNG before moving on. Non-empty (size > 10 KB), opens as an image, and its hash differs from the previous capture (sha1sum). Same hash = the tap did nothing or the screen is still loading: retry or note it.
  7. Name and number. NN_<screen>.png with a zero-padded counter in one folder per game and session; keep a notes.md line per capture (screen, how reached, anything skipped).
  8. Analyse through the router vision role, per rules/image-analysis-routing.md (mr-role.cjs call --role vision --file <png> --prompt "<question>"), never by guessing from filenames.
  • Git Bash rewrites /sdcard/... into a Windows path. Use MSYS_NO_PATHCONV=1 adb ... or the //sdcard form.
  • adb pull <device path> <local dir>: give an absolute local directory that exists; a missing one fails silently.
  • adb exec-out ... > file writes through the shell: run it from Git Bash or cmd, not an encoding-converting PowerShell 5 redirect.
  • Testing a game inside the Unity or Cocos editor: use that engine’s own play-mode tools.
  • Sweeping many real phones in CI: use t1k-jenkins-autotest.
  • Automating gameplay or botting an online game: out of scope; this skill only looks.

Command tables, emulator paths and ports: references/emulators-and-commands.md.