Repository navigation
The emulator images move
Android Studio writes a writable image for every emulator that it creates, and
the image grows with each app. That folder is now a row: android.avd.
| Provider | What moves | Variable |
|---|---|---|
android |
The build cache, and the emulator images | ANDROID_AVD_HOME names the image root |
The move warns that a slow disk slows every launch, so pick a fast external
SSD. The build cache row keeps its Gradle lock; the image row refuses while
emulator or qemu-system-* runs. A row now names its own processes, so a
move of one row never waits on the program of another.
Evidence in a test home folder
$ exodrive check
android.build-cache | 6 B | .android/build-cache
android.avd | 8.0 MB | .android/avd
$ exodrive migrate --target=… --tools=android
✅ Migrated Android Build Cache.
✅ Migrated Android Emulator Images.
Migration completed. Reclaimed 8.0 MB on the local disk.
$ ls -l .android
avd -> …/drive/android/avd
build-cache -> …/drive/android/build-cache
$ exodrive verify --all
[ok] android.avd: … (3 files, 8.0 MB)
[ok] android.build-cache: … (1 file, 6 B)
Checked 2 copies. Every copy matches its move.
One process table, two answers:
$ exodrive preflight android.avd --target=…
Preflight failed for android.avd: emulator is running (PID: 99999): stop it before migration
$ exodrive preflight android.build-cache --target=…
Preflight passed for android.build-cache on destination …
exodrive rollback restored both folders, and the ledger was empty again.
What this release does not prove
This Mac has no emulator image folder, so the evidence above comes from a test
home folder with an 8 MB image. An emulator was not started from a linked
folder: the emulator reads its images through the link like any other tool, and
the row refuses the move while one runs.