How to Debug an Android Phone Over Wi-Fi Using ADB and Wireless Debugging

Updated: September 2026

You do not always need a USB cable to debug an Android phone.

Android 11 and newer support Wireless Debugging, allowing Android Studio, Flutter and ADB to communicate with a physical phone over Wi-Fi.

This is especially useful when:

• Your USB port is unreliable
• Windows driver installation is causing problems
• You frequently test apps on a real phone
• You want to move around while debugging

The important part is understanding that wireless debugging still uses ADB. Wi-Fi only replaces the physical USB connection.

Quick Requirement Check

Phone: Android 11 or newer

Computer: Recent Android SDK Platform-Tools

Network: Phone and computer should be on the same Wi-Fi network

Android: Developer Options and Wireless Debugging enabled

What Is ADB Wireless Debugging?

ADB stands for Android Debug Bridge.

It is a command-line tool used by Android development tools to communicate with a device.

ADB can be used to:

• Install applications
• Run apps from development tools
• Read logs
• Open an Android shell
• Copy files
• Debug applications

Traditionally, ADB connects through USB.

Wireless Debugging allows the same type of ADB communication over a local Wi-Fi network.

Wireless Debugging vs USB Debugging

Feature	USB Debugging	Wireless Debugging
Connection	USB cable	Wi-Fi
Windows USB driver	May be required	Usually not required
ADB support	Yes	Yes
Android Studio	Supported	Supported
Flutter	Supported	Supported after ADB connection
Mobility	Limited by cable	More flexible

Step 1: Enable Developer Options

Wireless Debugging is located inside Android Developer Options.

On most Android phones:

Settings → About phone → Build number

Tap Build number seven times.

Enter your device PIN if Android asks for it.

You should then see a message indicating that Developer Options have been enabled.

The exact menu location can vary by manufacturer.

Step 2: Open Developer Options

On many Android phones:

Settings → System → Developer options

Samsung, Xiaomi, OnePlus and other manufacturers may place the menu somewhere slightly different.

Search Settings for:

Developer options

if you cannot find it manually.

Step 3: Enable Wireless Debugging

Inside Developer Options, find:

Wireless debugging

Turn it on.

Android may ask whether you want to allow wireless debugging on the current Wi-Fi network.

Only approve networks that you trust.

Step 4: Make Sure Both Devices Use the Same Network

Your computer and Android phone normally need to be connected to the same local Wi-Fi network.

For example:

Phone → Home Wi-Fi
PC → Same Home Wi-Fi

Wireless debugging may fail on:

• Guest networks
• Corporate Wi-Fi
• Networks that isolate connected devices
• Networks that block local discovery

Method 1: Pair Using Android Studio

Android Studio provides a graphical Wi-Fi pairing workflow.

Open Android Studio and choose:

Pair Devices Using Wi-Fi

Depending on the Android Studio version, this option may appear in Device Manager or the device-selection menu.

Pair Using QR Code

In Android Studio:

1. Open the Wi-Fi pairing window.
2. Select QR-code pairing.
3. On the phone, open Wireless Debugging.
4. Select the option to pair using a QR code.
5. Scan the code displayed by Android Studio.

After pairing, the phone should appear as an available development device.

Method 2: Pair Using an ADB Pairing Code

You can also pair directly from the command line.

On the Android phone:

Developer options → Wireless debugging → Pair device with pairing code

Android will display:

• An IP address
• A pairing port
• A six-digit pairing code

On the computer, open a terminal in your Android SDK Platform-Tools directory.

Run:

adb pair IP_ADDRESS:PAIRING_PORT

Example:

adb pair 192.168.1.25:37021

ADB will ask for the pairing code.

Enter the code shown on the phone.

If pairing succeeds, ADB should confirm that the device has been paired.

Pairing and Connecting Are Different

This is one of the most common sources of confusion.

Pairing establishes trust between the computer and phone.

Connecting creates the active ADB session.

Depending on the device and ADB version, the connection may happen automatically after pairing.

If it does not, check the Wireless Debugging screen for the current connection IP address and port.

Then run:

adb connect IP_ADDRESS:PORT

Verify the Wireless ADB Connection

Run:

adb devices

A working wireless device should appear in the list.

Example:

List of devices attached
192.168.1.25:41135    device

If no device appears, continue with the troubleshooting section below.

Use the Phone With Flutter

Once ADB sees the wireless device, Flutter should normally detect it as well.

Run:

flutter devices

Then launch the application using:

flutter run

If more than one device is connected, choose the correct device ID.

Use the Phone With Android Studio

After the phone is paired and connected, it should appear in Android Studio's device selector.

Select the device and run the Android project normally.

The app can then be installed and debugged without connecting the phone through USB.

Useful ADB Commands Over Wi-Fi

The same standard ADB commands work after a wireless connection is established.

List Devices

adb devices

Open Android Shell

adb shell

Install an APK

adb install app.apk

View Logs

adb logcat

Restart ADB

adb kill-server
adb start-server

Phone Is Paired but Does Not Appear in adb devices

First confirm that Wireless Debugging is still enabled.

Then:

1. Check that the phone and PC are on the same Wi-Fi network.
2. Run adb devices again.
3. Restart the ADB server.
4. Turn Wireless Debugging off and back on.
5. Pair the devices again if necessary.

ADB Says Connection Refused

If:

adb connect IP:PORT

returns a connection-refused error, check that you are using the current port.

Wireless Debugging ports can change.

Do not assume that the pairing port is also the active connection port.

The Phone's IP Address Changed

Wi-Fi routers can assign a different local IP address after reconnecting.

If a previously working connection stops:

1. Open Wireless Debugging on the phone.
2. Check the current IP address.
3. Reconnect using the current information.

Wireless Device Discovery Does Not Work

Modern ADB uses local network discovery to locate paired wireless devices.

Some networks block this type of discovery.

Common examples include:

• Public Wi-Fi
• Hotel networks
• School networks
• Office networks
• Guest networks with client isolation

Try a normal private network where devices are allowed to communicate locally.

Update Android SDK Platform-Tools

If wireless debugging behaves unpredictably, check that ADB comes from a recent Android SDK Platform-Tools installation.

You can update Platform-Tools using Android Studio's SDK Manager.

Also verify which ADB executable the computer is actually using.

On Windows:

where adb

If several copies appear, an old ADB installation may be running instead of the newer SDK version.

Restart the ADB Server

A quick ADB restart can resolve temporary connection problems.

adb kill-server
adb start-server
adb devices

Then test the wireless connection again.

Forget and Re-Pair the Computer

If pairing credentials become unreliable, remove the existing pairing.

On the phone:

Developer options → Wireless debugging → Paired devices

Select the computer and choose:

Forget

Then pair it again.

Wireless Debugging Security

ADB provides powerful access to a development device.

Do not enable Wireless Debugging permanently on untrusted networks.

Recommended precautions:

• Use trusted private Wi-Fi.
• Do not share pairing codes.
• Forget old paired computers.
• Turn Wireless Debugging off when you no longer need it.
• Do not approve unexpected debugging requests.

Wireless Debugging Diagnostic Table

Problem	Likely Cause	Check First
Pairing option missing	Android version or Developer Options	Android 11+ and Wireless Debugging
Pairing fails	Wrong IP, port or code	Generate a fresh pairing code
Paired but not connected	ADB discovery or connection	adb devices and current connection port
Connection refused	Wrong or expired port	Check Wireless Debugging screen
Device disappears later	Wi-Fi or IP change	Reconnect to the same network
Works at home but not office	Network isolation	Local-network restrictions
Flutter does not see device	ADB not connected	adb devices first

Old ADB Over TCP/IP Method

Older Android versions can also use ADB over Wi-Fi, but the workflow is different.

For Android 10 and older, the common method requires an initial USB connection.

The basic workflow is:

adb tcpip 5555
adb connect PHONE_IP:5555

This older method should not be confused with the modern Android 11+ Wireless Debugging pairing system.

Recommended Wireless Debugging Workflow

Use This Sequence

1. Enable Developer Options.
2. Enable Wireless Debugging.
3. Connect phone and computer to the same trusted Wi-Fi.
4. Pair using QR code or pairing code.
5. Verify with adb devices.
6. Verify with flutter devices if using Flutter.
7. Run the app.
8. Turn Wireless Debugging off when finished if you do not need it permanently.

Final Thoughts

Wireless Debugging is one of the most useful Android development features when USB connections are inconvenient or unreliable.

The key is to understand the sequence:

Developer Options → Wireless Debugging → Pair → Connect → adb devices → development tool.

If the connection fails, troubleshoot ADB and the local network before changing unrelated Android settings.

Related Guides

• How to Enable Developer Options on Android 16
• How to Connect an Android Phone to Flutter for USB and Wireless Debugging
• How to Fix USB Code 43 on Android in Windows 11

Official Sources & Further Reading

• Android Developers — Run Apps on a Hardware Device
• Android Developers — Android Debug Bridge