I am trying to connect ADB via WIFI on my unarmed android devices. I currently have 3 Android devices, 2 of them running Android 4.0.4 and 1 running Android 2.3.
The IP addresses of my devices are 192.168.2.122, 192.168.2.131, 192.168.2.115.
I have enabled debugging via USB on all devices and am following all the steps listed here.
In the command line I did the following
adb tcpip 5555
Restart in TCP mode port: 5555
adb socket 192.168.2.131
My problem is that on one of my devices (Android 4.0.4), the ADB connects with a message that says
connected to 192.168.2.122:5555
However, when I try to contact others, they say….
Cannot connect to 192.168.2.131:5555
Screenshot of the terminal page :
Picture of the terminal on the connected device :
Image of the terminal on a device that is not connected :
Many posts on Stack Over Flow indicate that I do the same thing from the root of my phone, but the device that connects the ADB is not rotatable either.
The problem with devices that are not connected to the network may be that their ports are not listening.
We are grateful for all the help.
How can I solve this problem?
It works fine with the android 4.0.4. but below that it doesn’t work. The answer to your problem is to update all devices to version 4.0.4.
I had the same problem.
First, I connected an Android4.0.3 based device via USB and set the TCP/IP port to 5555.
$ adb tcpip 5555
I then disconnected the USB connection and connected the device via IP WiFi and it worked.
adb kill server
$ adb connect 192.168.2.5
* Daemon is not running. run it now on port 5037 *
* Daemon is running successfully *
is connected to 192.168.2.5:5555
The steps are correct, a small part is different: The connection step must be performed after removing the cable.
Again, follow the steps below. This also works for devices that are not rooted. I have tested it on several non-functional devices including Moto G, Nexus 1, Videocon, etc.
- Connect the mobile phone via USB and tap the button:
Doping control 5555
- Find the type of mobile IP :
shell adb ip -f inet addr show wlan0
The IP address is displayed on the second line as follows:
192.168.1.233/24 brd 192.168.1.255 wlan0 on a global scale
where 192.168.1.233 is the IP address of your mobile phone.
- Remove the USB cable and enter the type:
After reading this question, I decided to create a user-friendly solution to solve this problem. You can use the open source plugin for IntelliJ that I developed. Here is the code and here is the plugin, ready to use.
The request is quite simple. Here’s a present for you:
Remember that older devices using Android 2.X do not support this Android Debug Bridge feature. For this reason, you cannot connect the device shown in the screenshots.
Solution no. 5:
First connection of the device via USB
and then apply the commands from …. apply.
Solution no. 6:
Activate adb via Wi-Fi on your phone
For example, create a file on the desktop. B. ‘Connect.bat’
and paste this code (you only need to change sdk, port and ip):
cd /dd %sdk%
adb tcpip %port%
adb shell netcfg
adb connect %ip%:%port%
echo connected via WiFi
adb -s %ip%:%port% usb
It is a very quick and easy solution. Have fun!
adb tcpip permanent, adb usb cable, adb over bluetooth, how to use adb through wifi, fastboot over wifi, android wifi adb unable to connect to device, adb authorize device, how to authorize adb on locked phone, adb wifi reborn, wireless debugging android 11, android wifi adb, adb over internet, adb connect connection refused, how to install adb wifi in android studio, wireless adb android 10, wireless adb android 11, adb connection refused, termux adb, scrcpy wireless, adb wireless download, over the air adb, adb wireless connection refused, wireless adb android studio, flutter wireless debug android, adb loses connection to device, enable adb over wifi without usb, adb tcpip 5555 no devices/emulators found, adb over bluetooth no root, connect adb over wifi, how to connect mobile to android studio without usb, adb wireless (no root), adb wifi commands