ADB: unable to connect to 192.168.1.10و555

Question

I cannot use adb connect to connect via Wi-Fi to my device (nexus 5, android 6), but since I am developing a cordova plugin using usb OTG, I really need to connect via Wi-Fi.

I tried adb kill-server and all the solutions are provided on SO and no one works for me ... Before it worked fine (like Android 5).

Any idea?

Answer 1

I had the same problem with updating Android 6. I noticed that for some reason the device plays "hard to get" when you try to contact it via WIFI.

Try the following steps:

1. Make sure that the Aggressive Wi-Fi to Cellular handover section of the "Network" in the device’s developer settings is disabled.

2. continuously ping -t 192.168.1.10 from the computer to the device, to make sure that it is not in the standby mode of the network ping -t 192.168.1.10 (windows cmd), unlock the device and even try to go to some website, just to wake it from network standby,

3. If ping does not work, turn off / on Android Wifi and go back to step 2.

4. When it answers ping, connect it via USB and:

   ADB USB

   adb tcpip 5555

   ADB Connect 192.168.10.1∗555

5. If it is still not connected, try switching the USB connection mode to MTP / PTP / Camera while the device is connected via USB, and repeat these steps again ...

If the above items do not work, try running ADB as an administrator. For Ubuntu -

 sudo adb start-server 

Answer 2

For me, I tried to connect via Wi-Fi, the accepted answer helped.

I needed to get it out of power saving mode . (API 23)

Answer 3

I have a device disabled that cannot be turned on, and I want to know if it is possible to connect the device via ubs using adb and restart the computer? Thanks PS, I'm French

Answer 4

In my case, I had to close the Wi-Fi ADB debugger application on the device. On another USB device, I had to disconnect and go into developer mode, and then reinstall the development settings. Also restart my computer.

It seems that adb has somehow messed up with global communications, and all debugging messages should be discarded on both sides.

After this, the devices begin to reconnect

Answer 5

An important step in order to make this work is to disconnect the USB cable after running the adb connect xx.xxxx: 5555 command. You are currently connected, but not authorized. Run adb kill-server and retry the connection command. Verify that the adb shell date is running.