adb tcpip vs Wireless Debugging: Which One to Use
Compare adb tcpip 5555 with Android 11+ Wireless debugging: setup, security, what survives a reboot, Android versions, and when to pick each for ADB over Wi-Fi.
Android offers two ways to run ADB over Wi-Fi. adb tcpip is the original: you plug in a cable once, switch the phone's ADB daemon to listen on port 5555 and connect to it. Wireless debugging arrived in Android 11: you pair with a 6-digit code and never need a cable. Use adb tcpip for older phones or quick sessions and Wireless debugging for Android 11+ and safer, cable-free work.
How each one works
adb tcpip
With the phone connected by USB, adb tcpip 5555 restarts adbd in TCP mode. After you unplug, adb connect <ip>:5555 opens a plain TCP connection and the usual RSA key prompt ("Allow USB debugging?") authorizes your computer. The full walkthrough is in ADB over Wi-Fi.
Wireless debugging
You enable Wireless debugging in Developer options and pair your computer once with adb pair <ip>:<pairing-port> and a 6-digit code. Pairing exchanges keys through an authenticated handshake. After that, adb connect <ip>:<port> opens a connection protected by TLS. The connect port is random and the phone announces it on the network (mDNS), which is how tools can find it. Step by step: Connect Android with Wireless debugging from the browser.
Side by side
| adb tcpip | Wireless debugging | |
|---|---|---|
| Minimum Android | Any version with USB debugging | Android 11 (API 30) |
| Needs a cable | Yes, once per session (to run adb tcpip) | No |
| First-time setup | adb tcpip 5555, then adb connect | Enable, pair with a code, then connect |
| Port | Fixed, 5555 | Random, changes often |
| Encryption | None: traffic is plain TCP | TLS |
| Authentication | RSA key prompt on the phone | Paired keys, approved through the pairing code |
| Survives a reboot | No, it resets and needs a cable again | The pairing stays; the setting often switches off and must be re-enabled |
| Discovery | You must know the IP | Phone announces itself on the network (mDNS) |
| Cleanup | adb usb or reboot | Turn the setting off; remove computers under Paired devices |
| In ADBKit | Works with either agent edition | Needs the Go agent (the Node edition cannot pair) |
Security
Both modes expose a service on your local network, so use them only on networks you trust.
- adb tcpip leaves port 5555 open for anyone on the network to try. The RSA prompt stops a stranger from connecting, but the traffic itself is not encrypted, and the open port stays until you run
adb usbor reboot. - Wireless debugging only accepts computers that completed pairing, encrypts the connection, and the setting is easy to turn off again. It is the safer default whenever your phone supports it.
Neither belongs on public Wi-Fi.
Reliability
adb tcpip is predictable: the port never changes, so scripts and saved addresses keep working until a reboot. Wireless debugging is more convenient but fiddlier: the connect port changes when you toggle it or the phone reconnects, Android turns it off when you leave the Wi-Fi network, and a phone on a different subnet or behind client isolation will not be found. ADBKit's agent rediscovers the new port for you.
Which should you use?
- Android 11 or newer, no cable nearby: Wireless debugging.
- Android 10 or older:
adb tcpip, since Wireless debugging does not exist. - A scripted, repeatable setup on a trusted network:
adb tcpip, for the fixed port. - Anything security-sensitive or long-lived: Wireless debugging.
- Quick one-off with a cable in hand: either;
adb tcpipis two commands.
Both need the ADBKit agent running on your computer before a browser tab can use them. Choose an install method in the ADBKit agent reference. For a cable-first connection check how to enable USB debugging.