

Let’s list the devices again to confirm that the device is now connected through WiFi: $ adb devices If, for example, my device’s IP address is 192.168.86.2, we’ll execute the following: $ adb connect 192.168.86.2:4444 Tell adb to run its TCP server: $ adb tcpip 4444įind your device’s private IP address in your network and execute this command: $ adb connect :4444 List the currently connected devices to confirm that our plugged-in device is attached: $ adb devices Now, we have to execute several commands in the command line that we opened in the SDK’s “platform-tools” folder. We’ll only have to do this the first time. Start by plugging in your Android device to your machine. You can add this folder to your path so that it’s easier to run the commands anywhere. We’ll open a command line here to issue commands using adb. You’ll find adb and other platform tools under the “platform-tools” folder. If you can’t find your SDK here, you can find its location from the SDK manager in Android Studio. Usually, the Android SDK is located in the following locations: First, we’ll need to find where it lives. Finding adbĪdb is a tool that comes installed with the Android SDK.

Check the "Use wireless debugging" toggle.Tap on "Wireless debugging", then again in the "Wireless debugging" option (not in the toggle, tap the entire item to enter to the details page.Enable Wireless debugging in your device:.I prefer to use the extension because I don't need to configure nothing and is more visual. Install the ADB Commands for VSCode extension.

You need to have both your computer and your phone connected to the same network. Tested on an Android 13 device and a Windows 10 computer. This post assumes that you have already configured your development environment to run and debug on your Android device over a USB connection. Stop damaging your phone's battery to test your apps, debug without cables (almost).
