More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Android Device Lab: Real-Phone Test Rig

    1

    Turn a physical Android phone into a repeatable test rig from a headless machine: wireless ADB, screenshots, APK install/launch/log automation, and a smoke-test recipe.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Android Device Lab: Real-Phone Test Rig

    Android Device Lab: Real-Phone Test Rig

    Example session with this skill installed

    Smoke-test a new debug build of a camera app, com.example.keelcam, versionCode 3, on a Galaxy S25. The APK is keelcam-v1.2.apk. The phone is on home Wi-Fi and my machine is a cloud VM.

    • Read your context and instructions
    • Compiled the android device lab

    SMOKE TEST — keelcam v1.2 (versionCode 3) on Galaxy S25: PASS.

    Connect: the first attempt from the cloud VM timed out twice — home Wi-Fi is not routable from here, exactly the case the skill plans for. Both ends moved to the same Tailscale tailnet; the phone showed Wireless debugging at 100.64.1.20:41237. adb pair with the 6-digit code, adb connect, and adb devices -l lists the phone as device.

    Loop: adb install -r keelcam-v1.2.apk printed Success. Launched the main activity, waited 5 seconds, screenshot taken — the camera viewfinder renders with the mode dropdown visible. dumpsys confirms versionCode 3. App-scoped logcat pulled: zero FATAL, zero AndroidRuntime, zero ANR. One warning about a missing tele camera — expected on this device, noted, not a failure.

    Report recorded: APK byte count 2,066,467, screenshot path, log path, verdict PASS. The app was left installed at the user's request so he can play with it; the report notes that deviation from the usual uninstall step.

    Second run after a phone reboot: the port had changed to 100.64.1.20:39881 — the most common "the lab broke" report, and it is always the port. Re-checked Wireless debugging, reconnected, re-ran the identical loop: PASS again. Same procedure, same result — that is what a repeatable rig is for.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Emulators lie about performance, sensors, and OEM quirks. This skill turns a physical Android phone into a repeatable test rig in about ten minutes: connect once, then install, launch, screenshot, and pull logs without touching the device.

    It covers the one-time phone setup (Developer options, wireless debugging, pairing code), connecting from the machine (including the Tailscale fallback when a cloud VM can't reach home Wi-Fi), seeing the screen without a display (screenshots as the workhorse, headless scrcpy recording for motion bugs), and the APK test loop as a contract: install must print Success, the screenshot must show the app, and the log must contain no FATAL or AndroidRuntime lines.

    The smoke-test recipe runs identically for every build — install, launch, wait, screenshot, pull app-scoped logcat, record the report, uninstall to leave the device clean. A build report template records pass/fail, screenshot path, log path, and the APK's exact byte count. A troubleshooting section and a connection decision table cover the common failures: stale daemons, unauthorized devices, signature mismatches, changed ports after reboot, and black screenshots from a sleeping screen. The value is in the repetition: the fifth green run means something because the procedure never changed.

    • The phone's IP and port change after reboots — the port must be re-checked in Wireless debugging each time.
    • A cloud VM usually cannot reach a phone on home Wi-Fi; both ends need the same Tailscale tailnet in that case.
    • Screenshots answer "did it render"; subtle animation bugs still need a screen recording.
    • The lab borrows the user's daily driver — it does not replace a dedicated device farm for scale testing.
    • Two phones on one machine require passing -s <serial> on every command.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    Terminal / Shell
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Emulators lie about performance, sensors, and OEM quirks. A build that passes on an emulator and fails on a real phone has told you nothing useful — the phone is the ground truth for what the user will experience.

    Don't retry a dead route more than twice. Put both ends on the same Tailscale tailnet and connect to the tailnet IP instead. The skill walks through exactly that fallback.

    The test proves the build installs, launches, and shows its first screen cleanly. Intermittent crashes are a different investigation: run the loop, then use the logcat capture to catch the crash when it happens.

    New in Mobile Development