Wireless ADB Controller manages Android's ADB daemon over TCP, offering session-only or boot-persistent activation, custom ports, and optional authorization-key tools.
Root-Controlled Wireless Debugging
Use a terminal on every supported root manager, or the integrated WebUI on KernelSU and APatch.
Session Control
Starts or stops ADB over TCP immediately and reports the daemon's current wireless status.
Boot Persistence
Stores whether wireless ADB should be enabled after reboot and which listening port should be used.
Authorization Keys
Includes experimental import, backup, restore, and revocation commands for Android's authorized ADB keys.
Command Reference
| Command | Effect |
|---|---|
wadbd on [port] | Enables wireless ADB for the current session; port 5555 is used when no port is supplied. |
wadbd off | Stops wireless ADB listening. |
wadbd status | Reports whether the wireless ADB daemon is active. |
wadbd enable-on-boot [port] | Enables persistent startup on the chosen port, defaulting to 5555. |
wadbd disable-on-boot | Removes the automatic boot behavior. |
Experimental Key Management
When Android does not show an authorization prompt, wadbd --import-key <path> can import an ADB public key. Public keys are typically stored in the desktop user's .android directory. The module can also back up and restore the device's authorized-key database.
These functions are explicitly experimental and are not exposed in the WebUI. Clearing keys revokes existing computers and requires authorization to be established again.