make a fix for running in an emulator, plus doc changes

BUILDING.md

@@ -1329,6 +1329,7 @@ npm run build:android:prod           # Production build (builds for production e
 # Auto-run builds
 npm run build:android:test:run       # Test build with auto-run (builds then runs on emulator)
 npm run build:android:prod:run       # Production build with auto-run (builds then runs on emulator)
+# Auto-run targets the one connected device; with none or several it prompts, or exits 9 without a terminal
 
 # Debug and release builds
 npm run build:android:debug          # Debug build (builds debug APK)
@@ -1454,20 +1455,15 @@ npx cap open android
 
 #### Android Build from the console
 
-```bash
-cd android
-./gradlew clean
-./gradlew build -Dlint.baselines.continue=true
-cd -
-```
+* Note that this currently fails: `./gradlew build -Dlint.baselines.continue=true`
 
-... or, to create the `aab` file, `bundle` instead of `build` (but not signed and not usable in Play Store):
+To create the `aab` file, `bundle` instead of `build` (but not signed and not usable in Play Store):
 
 ```bash
 ./gradlew bundleDebug -Dlint.baselines.continue=true
 ```
 
-... or, to create a signed `aab` release:
+So, to create a signed `aab` release:
 
 - Setup by adding the app/gradle.properties.secrets file (see properties at top
   of app/build.gradle) and the app/time-safari-upload-key-pkcs12.jks file
@@ -1843,7 +1839,7 @@ npm run build:android:assets
 - Configure signing keys
 - Check device/emulator setup
 
-## Additional Resources
+## Additional Documentation
 
 - [Electron Build Patterns](doc/electron-build-patterns.md)
 - [iOS Build Scripts](doc/ios-build-scripts.md)