Files
pipelines/docs/notes/android-device-pool.md
T
alan 4ab65692d6 Schedule Android UI review through the android-devices pool
The Android UI reviewer declares the android-devices pool instead of one
hard-coded Pixel, so a second UI run can use the idle foldable emulator instead
of waiting behind the single phone. Updates the Android map's device rules to
match the pool (replacing the old single-phone / no-emulator rule) and records
the pool, its members and the delivery-only personal Fold in a note. Safety
rules are unchanged; configuration and the pipeline version are separate steps.
2026-10-19 00:40:10 +01:00

1.8 KiB

Android device pool — 2026-10-19

The Android UI reviewer used to request one hard-coded device ({"exclusive":"phone-47241FDAS00DLK"}), so a second UI run had to wait behind the single Pixel even when another device was idle. Android UI stages now request the android-devices pool instead; the runner grants one free member and passes it to the stage as resource_target, and the stage takes its adb -s target from resource_target.metadata.adb_serial. A stage still never chooses a device.

Pool members

member adb serial metadata
phone-47241FDAS00DLK 47241FDAS00DLK kind=phone, model=Pixel_9_Pro_XL
emulator-Pipelines_Fold_A emulator-5554 kind=emulator, avd=Pipelines_Fold_A

The emulator is a single managed foldable AVD (Pipelines_Fold_A, unfolded built-in display 2076x2152, cover display 1080x2424), started by the operator. It is the only emulator in scope: ad-hoc emulators are still not started per task.

The operator's Pixel 10 Pro Fold (58281FDCG000JF) is delivery-only and is deliberately not a pool member — never a test target.

Rule reconciliation

android/AGENTS.md previously said "never start or use an emulator" and pinned the Pixel as the only device. That rule is replaced by the pool above so the map, the runner resource declaration and the live device set agree; the safety rules (UI-reviewer-only device work, lease-scoped fixtures, settings/build restoration, fail-closed cleanup) are unchanged.

Scope

This note, the map update and the pool declaration are configuration and documentation only. No device probing, health check or autostart is added: the emulator must already be running and the pool declaration is a static list, so an offline member is simply not grantable until it is running again.