Android 11 introduced a redesigned wireless ADB system that does not require a USB cable for initial pairing and does not require root access. Once paired, your phone and computer remember each other and you can connect any time they are on the same network with a single command.
Before Android 11, wireless ADB required a USB cable for the initial setup step (adb tcpip 5555), which disabled the USB ADB interface until you rebooted. It also had no authentication beyond the existing ADB RSA key, so anyone on the same network who knew the device's IP address could potentially attempt a connection.
Android 11's implementation uses a two-step model. First, you pair the computer to the phone using a one-time pairing code or QR code. During pairing, the phone and computer exchange and store mutual authentication credentials using the mDNS-based ADB pairing protocol (MDNS service type _adb-tls-pairing._tcp). After pairing, the computer's ADB key is stored in the phone's trusted key store, and the phone advertises its ADB TLS connection service (_adb-tls-connect._tcp) on the local network. Subsequent connections use TLS mutual authentication — no pairing code is needed again as long as the ADB key on the computer has not changed.
This design is more secure than the pre-Android 11 method and requires no USB cable at any stage. Both phone and computer just need to be on the same Wi-Fi network.
On the Android device:
Note that Wireless Debugging is tied to the current Wi-Fi network. If you switch networks or disconnect from Wi-Fi, the wireless ADB connection drops. The phone must rejoin the same network and have Wireless Debugging enabled (it persists across reboots on most Android builds, but some OEM skins turn it off after reboot).
This method requires Android Studio's Device Manager or the command-line adb pair command with the IP and port from the QR code. The QR code itself encodes a JSON payload with the network address and pairing code — scanning it with a camera app will not pair the device; it must be scanned by ADB tooling.
Using the command line:
192.168.1.15:37205 and a six-character alphanumeric code like A3K7PQ.adb pair 192.168.1.15:37205ADB prompts: Enter pairing code:. Type the six-character code shown on the phone screen and press Enter.
Successfully paired to 192.168.1.15:37205 [guid=adb-XXXXXXXX-XXXXXX]Pairing is now complete. The port used for pairing is different from the port used for the ongoing connection.
After pairing, look at the main Wireless Debugging screen on the phone. It shows the IP address and connection port (different from the pairing port), for example 192.168.1.15:42133. Run:
adb connect 192.168.1.15:42133Output:
connected to 192.168.1.15:42133Then verify with:
adb devicesThe device should appear as 192.168.1.15:42133 device. You can now run all the same ADB commands you would run over USB. Note that wireless ADB is somewhat slower than USB for large file transfers, but for shell commands, log capture, and APK installs the difference is negligible.
The connection port shown on the phone changes each time you toggle Wireless Debugging off and on, or when the phone reboots. This means you need to look up the current port on the phone before running adb connect. There are two approaches to reduce this friction:
Android Studio automatic discovery: Android Studio 4.2 and later includes an mDNS listener that automatically discovers paired devices on the network and connects without you manually entering the IP and port. Open the device dropdown in Android Studio and paired wireless devices appear automatically.
Scripted reconnect: If you use ADB from the command line regularly, a short script can automate the lookup. On the phone, the connection port is visible in the Wireless Debugging settings screen. Some automation tools can read it via adb shell settings get global adb_wifi_port — though this shell command itself requires an active connection, which makes it only useful for reconnecting after a temporary drop, not for initial connection after a reboot.
For most workflows, glancing at the phone's Wireless Debugging screen once per session to get the current port is the simplest approach.
If you prefer not to use the QR code flow, tap Pair device with pairing code on the phone. The phone shows a six-digit numeric code and an IP:port pair. Run the same adb pair command with that port and enter the numeric code when prompted. The process is identical to the QR code method; the only difference is that the code is purely numeric and displayed as plain text rather than encoded in a QR image.
"failed to connect to 192.168.1.15:42133: Connection refused": Wireless Debugging was disabled on the phone (possibly by a reboot). Re-enable it in Developer Options and get the new port.
"failed to authenticate to 192.168.1.15:42133": The ADB keys on the computer and phone are out of sync, possibly because you ran adb keygen or the phone's trusted keys were cleared. Re-pair using adb pair with a fresh pairing code from the phone.
Phone and computer on same network but pairing keeps failing: Some home routers use AP isolation (also called client isolation), which prevents devices connected to the same Wi-Fi from communicating directly with each other. Check your router settings and disable AP isolation for the network both devices are on. Corporate or university Wi-Fi networks frequently enforce isolation, making wireless ADB impractical on those networks.
ADB wireless is slow for file transfers: This is expected. For copying large files, use adb push over USB. Wireless ADB is best suited for shell interaction, logcat, and lightweight tasks.