Orion/2. Areas/Home Personal/knowledge/android-avdmanager-writes-config-android-emulator-misses.md
Avi a66996ac10 Orion vault — clean initial history
Knowledge vault (Orion/PARA) migrated from the pre-Orion 484vault on
2026-10-01. Deliberately orphaned: prior history contained a plaintext
password and stays local-only on branch archive/pre-boilerplate-history.
Secrets and live Hermes state are gitignored.
2026-10-02 08:34:48 -05:00

19 lines
891 B
Markdown

# Emulator can't find AVDs created by avdmanager (path mismatch)
**Date:** 2026-09-13 · **Machine:** Framework Laptop (Arch/Omarchy, pacman Android toolchain)
## Symptom
`avdmanager list avd` shows the AVD, but `emulator -avd <name>` says it doesn't exist / finds none.
## Diagnosis path
1. `avdmanager list avd` vs `ls ~/.android/avd` — mismatch: the toolchain is inconsistent about where AVDs live.
2. Pacman's `avdmanager` writes AVDs + ini files to `~/.config/.android/` while `emulator` reads `~/.android/`.
## Fix
Copy (or symlink) the AVD dir and its `.ini` from `~/.config/.android/avd/` into `~/.android/avd/`, and make sure the ini's `path=` points at the new location. Emulator sees them immediately.
## Environment facts
- gradle 9.7 + kotlin 2.4 via pacman; adb + scrcpy installed.
- Test device: Pixel 8 Pro, adb serial `3A251FDJG0067W`.
Related: [[Omarchy Commands]]