run-meshtastic-android

Launch it with the Gradle task :desktopApp:hotRunAsync through the gradle-queue wrapper, using the JetBrains 25 JDK and a sanitized environment. Once the pid file exists, driver.py connects to the hotMcpServer and supports reload to recompile and hot-swap edits into the running app.

Use driver_emulator.py with the connect command, which force-stops the app, relaunches MainActivity with the skip_onboarding extra and a /connections deeplink, accepts the trust dialog, and verifies the connected state. It also supports uiautomator dumps, text-based taps, swipes, and screencaps over adb.

Yes, a replay-sim simulated radio serves a Meshtastic TCP endpoint that the desktop app reaches at 127.0.0.1 and an emulator at 10.0.2.2. Each app needs its own sim port because only one client can hold a connection to a simulated node.

The screenshot captures the window's on-screen region, so the app window must be frontmost before capturing. Run the driver's raise command, which uses System Events AXRaise on the window named Meshtastic Desktop, before taking the screenshot.

The hotMcpServer attaches to the running app asynchronously, so an immediate status call can report connected:false while the app is fine. The driver auto-waits by polling status; persistent false usually means a stray app instance from another checkout holds the pid file.

Deeplink launch requires the plain :desktopApp:run task because hotRunAsync does not accept --args, so you lose hot reload. The blocking run task also holds a gradle-queue slot for the app's entire lifetime, and the deeplink can race last-device auto-reconnect.