OmaDroid 0.3.4 — VPN pairing guidance and ADB startup

Android can display a Tailscale/VPN address in Wireless debugging, which OmaDroid does not accept. This release explains how to pair using the Wi-Fi address and reconnect after enabling the VPN again.

• Added Tailscale/VPN guidance to the pairing page, Help, README, and shared-range address errors.
• Clarified that nearby phone information comes from live network discovery and that each computer needs its own authorization.
• Clarified how Connect resumes a deliberate Disconnect without new pairing; connection failures now include recovery steps for network changes.
• Fixed local ADB daemon startup on a fresh desktop, removing the need for a manual start command or separate startup service.

The phone endpoint allowlist is unchanged. This release does not add remote mirroring over Tailscale, change VPN settings, or pair unknown phones automatically.

Validation: all 93 Python tests pass, including a real isolated ADB startup test, plus QML lint and Omarchy manifest validation. Installed on two Omarchy desktops; verified cold startup on the newly configured desktop and inspected the pairing page in dark and light themes. Broader handset/VPN compatibility remains subject to physical testing.

Update an existing git-managed installation with omarchy plugin update onelegdave.omadroid --yes, then omarchy restart shell. For a local installation, extract the attached archive, run /usr/bin/python3 -E -s install.py from its directory, then omarchy restart shell. The installer preserves settings and saved phone authorization. Verify the archive with sha256sum -c omadroid-v0.3.4.sha256.

Created and maintained by OneLegDave. Commit: 704e8305964e9b6a390c4cd7d20fe10ac71db9ae.