avd.py: Ergonomic improvements to the script
* -v now shows emulator logs for "start" command
* "start" now runs "install" if obviously necessary (config.ini not present)
* "list" command added, which makes it clear what --avd-config options
exist.
Bug: 1276006
Change-Id: Idc37641d9a665f7460e2eabe5348aea1e262d247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3438186
Reviewed-by: Haiyang Pan <hypan@google.com>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/main@{#969283}
diff --git a/docs/android_emulator.md b/docs/android_emulator.md
index 3359ada3..648e529 100644
--- a/docs/android_emulator.md
+++ b/docs/android_emulator.md
@@ -17,6 +17,10 @@
Chromium has a set of prebuilt images stored as CIPD packages. These are used
by various builders to run tests on the emulator. Their configurations are
currently stored in [`//tools/android/avd/proto`](../tools/android/avd/proto/).
+You can run this command to list them:
+```sh
+tools/android/avd/avd.py list
+```
| Configurations | Android Version | AVD Target | Builder |
|:-------------- |:--------------- |:---------- |:------- |
@@ -110,15 +114,6 @@
The test runner will set up and tear down the emulator on each invocation.
To manage emulator lifetime independently, use `tools/android/avd/avd.py`.
-> Note: Before calling `avd.py start`, use `avd.py install` to install the
-> emulator configuration you intend to use. Otherwise the emulator won't start
-> correctly.
->
-> ```
-> $ tools/android/avd/avd.py install \
-> --avd-config tools/android/avd/proto/generic_android28.textpb
-> ```
-
##### Options
* `--avd-config`
