Debug Android apps over WiFi without USB cables. Android offers two methods: native wireless debugging (Android 11+, recommended) and legacy TCP/IP mode for older devices.
Prerequisites
- ADB installed (part of Android SDK Platform Tools), version 1.0.41 or higher (
adb version) - Developer Options enabled, USB debugging on
- Computer and device on the same WiFi network
- Android 11+ for native wireless debugging, or Android 10 and below for legacy TCP/IP mode
Method 1: Android 11+ native wireless debugging
Android 11 introduced built-in wireless debugging with secure pairing and automatic reconnection. Use this on modern devices.
Enable wireless debugging
- Settings, System, Developer options.
- Scroll to Wireless debugging, toggle it ON.
- Accept the permission prompt if shown. Keep this screen open while pairing – it shows connection status.
Pairing: QR code (easiest)
On the device: tap Pair device with QR code.
In Android Studio: Device Manager, Physical tab, “Pair using WiFi”, “Pair using QR code”. Studio shows a QR code; scan it with the device. Connection establishes automatically – no IP addresses or pairing codes.
Pairing: manual IP and pairing code
On the device: tap Pair device with pairing code. Note the IP address (e.g. 192.168.1.100), port (e.g. 37043), and 6-digit pairing code (e.g. 582914).
On the computer:
adb pair 192.168.1.100:37043
Enter the pairing code when prompted:
Enter pairing code: 582914
Expected output:
Successfully paired to 192.168.1.100:37043 [guid=adb-1A2B3C4D5E6F-ABCDEF]
Connect after pairing
The pairing port is used once; connecting uses a different port. On the device, go back to the main Wireless debugging screen and look for the IP address and port under the device name (e.g. 192.168.1.100:41053).
adb connect 192.168.1.100:41053
connected to 192.168.1.100:41053
Verify:
adb devices
List of devices attached
192.168.1.100:41053 device
Method 2: Legacy TCP/IP mode (Android 10 and below)
Older devices need one initial USB connection to enable network listening.
Step 1: Connect via USB. Connect the cable, enable USB debugging, accept the authorization prompt. Verify with adb devices.
Step 2: Switch to TCP/IP mode:
adb tcpip 5555
Step 3: Find the device IP. Settings, About phone, Status – or Network and internet, WiFi, tap the connected network.
Step 4: Disconnect the USB cable.
Step 5: Connect over WiFi:
adb connect 192.168.1.100:5555
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| “Connection refused” | Wrong port or device not listening | Check the connection port on the device, ensure wireless debugging is ON |
| “Unable to connect” | Different WiFi networks | Verify both on the same network, check firewall |
| “Device offline” after connecting | Stale connection or network change | adb disconnect, then adb connect again |
| Pairing code doesn’t work | Code expired (60 second timeout) | Generate a new pairing code on the device |
| Connection drops frequently | Weak WiFi or power saving | Move closer to the router, disable battery optimization |
Security notes
Wireless debugging exposes ADB on the network. Keep it locked down:
- Use Android 11+ native wireless debugging – it includes pairing authentication.
- Disable wireless debugging when the session ends.
- Only use it on trusted networks, never public WiFi.
- Legacy TCP/IP mode has no authentication after the initial USB connection, so it is the least secure option.
Method comparison
| Feature | Android 11+ QR code | Android 11+ manual | Legacy TCP/IP |
|---|---|---|---|
| Setup complexity | Easiest | Easy | Moderate |
| Initial USB required | No | No | Yes |
| Authentication | QR code | 6-digit code | None after USB |
| Persists after reboot | Yes (if enabled) | Yes (if enabled) | No |
| Security | High | High | Low |
| Android version | 11+ | 11+ | 10 and below |
References: Android Debug Bridge (adb) and Wireless Debugging – Android Developers (developer.android.com)
Part of the series: The Complete ADB Guide — also in this series: What is ADB? · Install ADB · Essential Commands · Troubleshooting
Was this useful?
Thanks for the feedback.
2 comments