| name | iterating-on-voltius-android |
| description | Use when building, deploying, running, screenshotting, clicking through, or debugging the Voltius Tauri app on a real Android phone — drives the on-device debug APK through the tauri-android MCP (adb + Chrome DevTools Protocol) so changes are seen and interacted with on the device, not just compiled. |
Iterating on Voltius Android
Overview
Build the debug APK, install it on the phone, then look at it and drive it on the device
through the tauri-android MCP (adb + CDP). Same tool names as the desktop tauri-docker
backend, selected by PLATFORM=android. A cross-compile only proves ABI linkage — the Android
sandbox (SELinux, no shell spawn, no raw devices, scoped storage) breaks several host-integration
features at runtime; the only proof a feature works is driving it on the phone and reading the
screenshot. See docs/android-dev.md (runbook) and docs/android-feature-gaps.md (triage queue).
Build (x86_64 WSL2 laptop — build here)
scripts/android-build.sh aarch64
Output: src-tauri/gen/android/app/build/outputs/apk/universal/debug/app-universal-debug.apk
(~310 MB, debug-signed with committed keystore/voltius-debug.keystore → adb install -r upgrades).
On an aarch64 host the NDK runs under QEMU (~1h clean) — avoid; build on the x86_64 box.
Reach the phone + deploy (do this FIRST — MCP is useless if adb can't see the phone)
Phone plugs into Windows; WSL reaches it via a Windows-hosted adb server. Full setup +
the three non-obvious blockers (Hyper-V firewall, adb version match, RSA auth) live in the
android-adb-wsl-setup memory. Quick check before anything else:
