Skip to content

phone-setup.md

Latest commit

 

History

History
33 lines (23 loc) · 2.17 KB

phone-setup.md

File metadata and controls

33 lines (23 loc) · 2.17 KB
Raw

Phone setup

  1. Back up anything important before enabling USB debugging.

  2. On the phone, open Settings → About phone and tap Build number repeatedly until Developer Options are enabled.

  3. Open Developer Options and enable USB debugging.

  4. Connect the phone with a data-capable USB cable.

  5. Unlock the phone and accept the Android RSA debugging prompt. Verify the displayed computer fingerprint before accepting.

  6. On the workstation, run:

    adb devices -l

  7. Confirm the device state is device, not unauthorized, offline, or no permissions.

From the repository, npm run check:environment -- --require-scrcpy performs the read-only host tool check required by the default visible-mirror workflow.

If the state is unauthorized, accept the prompt on the phone. If it is offline, reconnect the cable and let the user decide whether to restart ADB. If it is no permissions, fix the Linux udev/group configuration deliberately; this server does not modify udev rules or use elevated privileges.

The server will not unlock the phone, enter a PIN/password, dismiss user-consent prompts, or operate a locked device. Normal MCP control permits valid non-sensitive packages by default; use ANDROID_AGENT_MCP_ALLOWED_PACKAGES to narrow the session when desired. Selecting the device makes one best-effort attempt to start the visible scrcpy mirror unless auto-start is disabled; a mirror failure does not block ADB tools.

Physical test prerequisites

Set explicit inputs before running opt-in physical tests:

export ANDROID_AGENT_MCP_PHYSICAL=1
export ANDROID_AGENT_MCP_TEST_PACKAGE=com.example.androiddevicetest
export ANDROID_AGENT_MCP_TEST_SELECTOR='{"text":"7"}'
npm run test:physical

The harness does not invent a package, selector, or phone and does not modify personal applications. It skips unless the explicit package and repeatable harmless selector are supplied, exactly one authorized device is connected, and the test app is prepared for this workflow. It drives the phone through the same MCP stdio protocol used by an agent. These variables affect only npm run test:physical; normal MCP control uses the configured package policy.