860 B
## Android Emulator / Device Policy
- For all Android emulator testing, UI validation, screenshots, integration testing, and interactive app launches, ALWAYS use the AVD named avdslim.
- Treat avdslim as the canonical MotorSignal Android test emulator.
- Do not create, select, launch, or switch to another Android Virtual Device unless the user explicitly instructs you to do so.
- Before running emulator-dependent tests, verify that avdslim is running and available through adb devices.
- If avdslim is not running, start avdslim rather than choosing another emulator.
- When multiple Android devices/emulators are connected, explicitly target avdslim for Flutter/ADB commands instead of relying on automatic device selection.
- Physical devices should only be used when the user explicitly requests physical-device testing.