# Bypassing ADB: How I Built a 60Hz Android UI Daemon in Kotlin and a Zero-Token A* MCP Router in Rust

> Source: <https://ainexusdaily.vercel.app/article/2026-11-22-bypassing-adb-how-i-built-a-60hz-android-ui-daemon-in-kotlin-and-a-zero-token-a->
> Published: 2026-11-22 13:51:47+00:00

**Recommendation:** Cache known UI flows in a local A* graph and stream AccessibilityNodeInfo over TCP instead of dumping XML or sending screenshots each step to cut per-tap latency and token spend.
More in the playbook "Designing agent systems": <https://wpnews.pro/playbooks/agent-architecture>

# Bypassing ADB: How I Built a 60Hz Android UI Daemon in Kotlin and a Zero-Token A* MCP Router in Rust

How DroidPath streams Android AccessibilityNodeInfo over raw TCP at 60Hz and caches UI flows in a local A* graph so AI agents navigate real devices in under a second. f you have ever wired an LLM agent (Cursor, Claude Code, Gemini CLI, or a local model) to a physical Android device, you run into the

same three bottlenecks almost immediately: ADB latency. Standard tools like adb shell uiautomator dump, Appium, or Maestro spawn processes and serialize XML on every step. Waiting 2–4 seconds per tap turns a 5-screen flow into a 20-second crawl. Vision-agent token burn.

Sending screenshots to a multimodal model on every single tap costs $0.05–$0.10 per run and adds seconds of inference lag. In CI regression suites, that bill scales fast. Espresso maintenance cost. Espresso runs fast and costs $0 in compute, but the moment a layout changes or a viewId gets refactored, an engineer burns hours fixing flaky locators.

I built DroidPath — an open-source headless Kotlin daemon and cross-platform Rust MCP server — to give AI agents sub-second access to physical Android devices without root, while driving token costs on known routes down to zero. Android lets you execute compiled DEX code directly in the system environment under the shell user via app_process — no root, no unlocked bootloader, no custom ROM. DroidPath splits the workload into two layers: [ AI Agent (Cursor / Claude / Gemini CLI / Local LLM) ] │ │ MCP (stdio / local HTTP+SSE) ▼ [ DroidPath Desktop & MCP Server (Rust + Tauri v2) ] ├── ScreenLayoutHasher (FNV-1a hashing + PII redaction) ├── SpatialGraphEngine (Local DAG + A* pathfinding) ├── MacroExecutionEngine (Execution + self-healing) └── HazardousActionClassifier (Human-in-the-Loop gate) │ │ Raw TCP 60Hz (127.0.0.1 via adb forward) ▼ [ Android Headless Daemon (Kotlin, app_process) ] └── AccessibilityNodeInfo -> Shadow DOM -> TCP :27189

## Key Takeaways

- •Standard tools like adb shell uiautomator dump, Appium, or Maestro spawn processes and serialize XML on every step.
- •This story was reported by **Dev.to** , covering developments in the**dev** space.
- •AI advancements continue to reshape industries — read the full article on Dev.to for complete coverage.

📖 Continue reading the full article:

[Read Full Article on Dev.to →](https://dev.to/v0val0x/bypassing-adb-how-i-built-a-60hz-android-ui-daemon-in-kotlin-and-a-zero-token-a-mcp-router-in-rust-8h6)
