Unable to connect to device

[hou-xx]

Unable to connect to device 'erver version (32) doesn't match this client (36); killing...'. Make sure that your computer and your device are connected to the same WiFi network.

[pedrovgs]

Hi @tianqing2117 this crash seems to be related to the java version being used. Could you please tell me what's the java version you are using for running your IntelliJ/Android Studion installation. I also need to know the version of the plugin being used and if there are any steps to reproduce the bug. Thanks!

[cutiko]

Greetings

Same problem here, Im using JAVA 8 (jdk1.8.0_101) since the new Nougat release require it. Plugin version is 2.3

Steps:

1. Connect device via USB
2. Press the icon in Android Studio
3. Error is display Unable to connect to device 'erver version (32) doesn't match this client (36); killing...'. Make sure that your computer and your device are connected to the same WiFi network.

Change to JAVA 7 (jdk1.7.0_80) to try it, same steps before, similar message:

Android WiFi ADB: Unable to connect to device 'SM_N7505L'. Make sure that your computer and your device are connected to the same WiFi network.

Hope to help.

Android WiFi ADB: Unable to connect to device 'D2533'. Make sure that your computer and your device are connected to the same WiFi network.

[UPDATE]

So I was reading

Here https://github.com/pedrovgs/AndroidWiFiADB/issues/36 and here https://github.com/pedrovgs/AndroidWiFiADB/issues/29

Switch to Sony Xperia device instead, kind of same, using JAVA8 got this message Android WiFi ADB: Unable to connect to device 'D2533'. Make sure that your computer and your device are connected to the same WiFi network.

Also relevant information, I came to this plugin because despite I was able to do everything by command, after disconnecting the device it didnt work neither. I got into the terminal successfully connect to the device but then when the device was disconnected from USB the device was no longer linked to ADB (adb devices list was empty, neither working on Android Studio).

[pedrovgs]

Hi @tianqing2117 @cutiko, the log message you provide could be related to the JDK used to build the 2.3 version. I've just released a new version Version 2.4 using the JDK 1.6 instead of the JDK 1.8. Could you update your plugin installation and try again? You can download the artifact manually if needed from this link.

[pedrovgs]

The notification showing this message erver version (32) doesn't match this client (36); killing... inside the device name and a regular notification showing the text Android WiFi ADB: Unable to connect to device 'D2533'. Make sure that your computer and your device are connected to the same WiFi network are not the same. The first one could be related to the JDK used for building the artifact and the second one could be related to the device & OS version supporting or not the debug over wifi feature.

[cutiko]

@pedrovgs not working, complete logs below, comments added for clarification, using JAVA8 (same mentioned above).

//Using Sony Xperia
12:13:48 PM Adb connection Error:EOF
12:13:48 PM Connection attempts: 1
12:13:48 PM Android WiFi ADB: Unable to connect to device 'D2533'. Make sure that your computer and your device are connected to the same WiFi network.
12:13:49 PM Connection attempts: 2
12:13:50 PM Connection attempts: 3
12:13:53 PM Adb connection Error:EOF
12:13:53 PM Connection attempts: 1
12:14:04 PM Adb connection Error:EOF
12:14:04 PM Connection attempts: 1
12:14:06 PM Adb connection Error:EOF
12:14:06 PM Connection attempts: 1
12:14:07 PM Connection attempts: 2
12:14:08 PM Connection attempts: 3
12:14:11 PM Android WiFi ADB: Unable to connect to device 'erver version (32) doesn't match this client (36); killing...'. Make sure that your computer and your device are connected to the same WiFi network.
12:14:30 PM Adb connection Error:EOF
12:14:30 PM Connection attempts: 1
12:14:31 PM Connection attempts: 2
12:14:32 PM Connection attempts: 3
12:14:45 PM Adb connection Error:EOF
12:14:45 PM Connection attempts: 1
12:14:46 PM Connection attempts: 2
12:14:47 PM Connection attempts: 3
//Disconnect, Xperia, but forgot to connect the other device.
12:14:50 PM Android WiFi ADB: There are no devices connected. Review your USB connection and try again.
//Change to Samgung Galaxy note 3 neo, previously known as 'SM_N7505L', and run the app using USB to check
12:14:57 PM Executing tasks: [:app:assembleDebug]
12:15:04 PM Gradle build finished in 6s 895ms
//App using USB runned successfully, try to connect. I saw this message glad it is connected
12:15:20 PM Android WiFi ADB: Device 'SM_N7505L' connected.
12:15:20 PM Adb connection Error:EOF
12:15:20 PM Connection attempts: 1
12:15:21 PM Connection attempts: 2
12:15:22 PM Connection attempts: 3
12:15:25 PM Adb connection Error:EOF
12:15:25 PM Connection attempts: 1
12:16:05 PM Adb connection Error:EOF
12:16:05 PM Connection attempts: 1
12:16:06 PM Connection attempts: 2
12:16:07 PM Connection attempts: 3
//Open the right dashboard, device is listed, press connect button, then this messages is displayed
12:16:14 PM Android WiFi ADB: Unable to connect to device 'SM_N7505L'. Make sure that your computer and your device are connected to the same WiFi network.

I have done it about 4 times during the lapse of time after I got the email notification about the 2.4 version.

[pedrovgs]

@cutiko could you double check that you've installed the version 2.4? You can uninstall and install the plugin again to be sure that the version used is the last one I've just released.

If the last one it's not working then try with this commands from any terminal:

Connect the device to your laptop using a USB cable and then execute:

adb tcpip 5555
adb connect <YOUR_DEVICE_IP>:5555

Send me the result please.

[cutiko]

The first time I did it, I made myself sure to verify the 2.4 version while installing the plugin (install from disk). But took the time, redownload it and reinstall it, why not? I'll be glad if I can help.

First, I have to notice an incredibly unusual behaviour from adb after installing the plugin (after uninstalling it, the odd behaviour stopped). For some reason ADB is constantly trying to connect, you will see in the logs below.

4:25:25 PM Adb connection Error:EOF
4:25:25 PM Connection attempts: 1
4:25:26 PM Connection attempts: 2
4:25:27 PM Connection attempts: 3
4:25:54 PM Android WiFi ADB: Unable to connect to device 'SM_N7505L'. Make sure that your computer and your device are connected to the same WiFi network.
4:25:55 PM Adb connection Error:EOF
4:25:55 PM Connection attempts: 1
4:25:56 PM Connection attempts: 2
4:25:57 PM Adb connection Error:EOF
4:25:57 PM Connection attempts: 1
4:25:58 PM Connection attempts: 2
4:25:59 PM Connection attempts: 3
4:26:00 PM Adb connection Error:EOF
4:26:00 PM Connection attempts: 1
4:26:01 PM Connection attempts: 2
4:26:02 PM Connection attempts: 3
4:26:03 PM Connection attempts: 4
4:26:04 PM Connection attempts: 5
4:26:05 PM Adb connection Error:EOF
4:26:05 PM Connection attempts: 1
4:26:06 PM Connection attempts: 2
4:26:07 PM Connection attempts: 3
4:26:09 PM Adb connection Error:EOF
4:26:09 PM Connection attempts: 1
4:26:10 PM Connection attempts: 2
4:26:11 PM Adb connection Error:EOF
4:26:11 PM Sending jdwp tracking request failed!
4:26:11 PM Connection attempts: 1
4:26:13 PM Adb connection Error:EOF
4:26:13 PM Connection attempts: 1
4:26:15 PM Adb connection Error:EOF
4:26:15 PM Connection attempts: 1
4:26:16 PM Android WiFi ADB: There are no devices connected. Review your USB connection and try again.
4:26:18 PM Adb connection Error:EOF
4:26:18 PM Connection attempts: 1
4:26:19 PM Connection attempts: 2
4:26:20 PM Connection attempts: 3
4:26:21 PM Connection attempts: 4
4:26:22 PM Connection attempts: 5
4:26:23 PM Connection attempts: 6
4:26:24 PM Connection attempts: 7
4:26:25 PM Connection attempts: 8
4:26:26 PM Adb connection Error:EOF
4:26:26 PM Connection attempts: 1
4:26:27 PM Connection attempts: 2
4:26:28 PM Connection attempts: 3
4:26:32 PM Adb connection Error:EOF
4:26:32 PM Connection attempts: 1
4:26:33 PM Connection attempts: 2
4:26:34 PM Connection attempts: 3
4:26:35 PM Connection attempts: 4
4:26:36 PM Connection attempts: 5
4:26:37 PM Adb connection Error:EOF
4:26:37 PM Connection attempts: 1
4:26:38 PM Connection attempts: 2
4:26:39 PM Connection attempts: 3
4:26:40 PM Connection attempts: 4
4:26:41 PM Connection attempts: 5
4:26:42 PM Adb connection Error:EOF
4:26:42 PM Connection attempts: 1
4:26:43 PM Connection attempts: 2
4:26:44 PM Adb connection Error:EOF
4:26:44 PM Connection attempts: 1
4:26:46 PM Adb connection Error:EOF
4:26:46 PM Connection attempts: 1
4:26:47 PM Android WiFi ADB: There are no devices connected. Review your USB connection and try again.
4:26:47 PM Connection attempts: 2
4:26:49 PM Adb connection Error:EOF
4:26:49 PM Connection attempts: 1
4:26:50 PM Connection attempts: 2
4:26:51 PM Connection attempts: 3
4:26:55 PM Adb connection Error:EOF
4:26:55 PM Connection attempts: 1
4:26:56 PM Connection attempts: 2
4:26:57 PM Adb connection Error:EOF
4:26:57 PM Connection attempts: 1
4:26:58 PM Connection attempts: 2
4:26:59 PM Connection attempts: 3
4:27:00 PM Connection attempts: 4
4:27:01 PM Connection attempts: 5
4:27:02 PM Adb connection Error:EOF
4:27:02 PM Connection attempts: 1
4:27:03 PM Connection attempts: 2
4:27:04 PM Connection attempts: 3
4:27:05 PM Connection attempts: 4
4:27:06 PM Connection attempts: 5
4:27:07 PM Connection attempts: 6
4:27:08 PM Connection attempts: 7
4:27:09 PM Connection attempts: 8
4:27:10 PM Adb connection Error:EOF
4:27:10 PM Connection attempts: 1
4:27:11 PM Connection attempts: 2
4:27:12 PM Connection attempts: 3
4:27:14 PM Adb connection Error:EOF
4:27:14 PM Connection attempts: 1
4:27:15 PM Connection attempts: 2
4:27:16 PM Adb connection Error:EOF
4:27:16 PM Connection attempts: 1
4:27:17 PM Connection attempts: 2
4:27:18 PM Connection attempts: 3
4:27:19 PM Connection attempts: 4
4:27:20 PM Connection attempts: 5
4:27:21 PM Adb connection Error:EOF
4:27:21 PM Connection attempts: 1
4:27:22 PM Connection attempts: 2
4:27:23 PM Connection attempts: 3
4:27:24 PM Connection attempts: 4
4:27:25 PM Connection attempts: 5
4:27:26 PM Adb connection Error:EOF
4:27:26 PM Connection attempts: 1
4:27:27 PM Connection attempts: 2
4:27:28 PM Connection attempts: 3
4:27:29 PM Connection attempts: 4
4:27:30 PM Connection attempts: 5
4:27:31 PM Adb connection Error:EOF
4:27:31 PM Connection attempts: 1
4:27:32 PM Connection attempts: 2
4:27:33 PM Connection attempts: 3
4:27:34 PM Connection attempts: 4
4:27:35 PM Connection attempts: 5
4:27:36 PM Adb connection Error:EOF
4:27:36 PM Connection attempts: 1
4:27:37 PM Connection attempts: 2
4:27:38 PM Connection attempts: 3
4:27:39 PM Connection attempts: 4
4:27:40 PM Connection attempts: 5
4:27:41 PM Adb connection Error:EOF
4:27:41 PM Connection attempts: 1
4:27:42 PM Connection attempts: 2
4:27:43 PM Connection attempts: 3
4:27:44 PM Connection attempts: 4
4:27:45 PM Connection attempts: 5
4:27:47 PM Adb connection Error:EOF
4:27:47 PM Connection attempts: 1
4:27:48 PM Connection attempts: 2
4:27:49 PM Connection attempts: 3
4:27:50 PM Connection attempts: 4
4:27:51 PM Connection attempts: 5
4:27:52 PM Adb connection Error:EOF
4:27:52 PM Connection attempts: 1
4:27:53 PM Connection attempts: 2
4:27:54 PM Connection attempts: 3
4:27:55 PM Connection attempts: 4
4:27:56 PM Connection attempts: 5
4:27:57 PM Adb connection Error:EOF
4:27:57 PM Connection attempts: 1
4:27:58 PM Connection attempts: 2
4:27:59 PM Connection attempts: 3
4:28:00 PM Connection attempts: 4
4:28:01 PM Connection attempts: 5
4:28:02 PM Adb connection Error:EOF
4:28:02 PM Connection attempts: 1
4:28:03 PM Connection attempts: 2
4:28:04 PM Connection attempts: 3
4:28:05 PM Connection attempts: 4
4:28:06 PM Connection attempts: 5
4:28:07 PM Adb connection Error:EOF
4:28:07 PM Connection attempts: 1
4:28:08 PM Connection attempts: 2
4:28:09 PM Connection attempts: 3
4:28:10 PM Connection attempts: 4
4:28:11 PM Connection attempts: 5
4:28:12 PM Adb connection Error:EOF
4:28:12 PM Connection attempts: 1
4:28:13 PM Connection attempts: 2
4:28:14 PM Connection attempts: 3
4:28:15 PM Connection attempts: 4
4:28:16 PM Connection attempts: 5
4:28:17 PM Adb connection Error:EOF
4:28:17 PM Connection attempts: 1
4:28:18 PM Connection attempts: 2
4:28:19 PM Connection attempts: 3
4:28:20 PM Connection attempts: 4
4:28:21 PM Connection attempts: 5
4:28:22 PM Adb connection Error:EOF
4:28:22 PM Connection attempts: 1
4:28:23 PM Connection attempts: 2
4:28:24 PM Connection attempts: 3
4:28:25 PM Connection attempts: 4
4:28:26 PM Connection attempts: 5
4:28:28 PM Adb connection Error:EOF
4:28:28 PM Connection attempts: 1
4:28:29 PM Connection attempts: 2
4:28:30 PM Connection attempts: 3
4:28:31 PM Connection attempts: 4
4:28:32 PM Connection attempts: 5
4:28:33 PM Adb connection Error:EOF
4:28:33 PM Connection attempts: 1
4:28:34 PM Connection attempts: 2
4:28:35 PM Connection attempts: 3
4:28:36 PM Connection attempts: 4
4:28:37 PM Connection attempts: 5
4:28:38 PM Adb connection Error:EOF
4:28:38 PM Connection attempts: 1
4:28:39 PM Connection attempts: 2
4:28:40 PM Connection attempts: 3
4:28:41 PM Connection attempts: 4
4:28:42 PM Connection attempts: 5
4:28:43 PM Adb connection Error:EOF
4:28:43 PM Connection attempts: 1

Also, I maybe catch something else, while the device was connected, normal run was available in the device but wasn't connected for the plugin. You can see the screenshots below.

After this I follow your instructions and try to do it using the command line. You will notice that the device list is asked three times, that is because I unplugged the device so I want to check the device was still there, it wasn't. This is what lead me to your plugin.

MacBook-Pro-de-Erick:sdk cutiko$ cd platform-tools/
MacBook-Pro-de-Erick:platform-tools cutiko$ /.adb tcpip 5555
-bash: /.adb: No such file or directory
MacBook-Pro-de-Erick:platform-tools cutiko$ ./adb tcpip 5555
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
restarting in TCP mode port: 5555
MacBook-Pro-de-Erick:platform-tools cutiko$ ./adb connect 192.168.0.19:5555
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
connected to 192.168.0.19:5555
MacBook-Pro-de-Erick:platform-tools cutiko$ ./adb devices
List of devices attached
192.168.0.19:5555   device
32048d2e55ba1173    device

MacBook-Pro-de-Erick:platform-tools cutiko$ ./adb devices
List of devices attached
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *

MacBook-Pro-de-Erick:platform-tools cutiko$ ./adb devices
List of devices attached

MacBook-Pro-de-Erick:platform-tools cutiko$ 

[pedrovgs]

I don't understand why the plugin does not work. It's working for all the environments I have tried: Android Studio / Intelli J, different JDK installations, different devices, different Android OS, windows and OS X. This is the first time I see the plugin is not working and the user is able to connect the device using the command line. I know that some devices don't support this debug over WiFi feature, but this is not the case. As you may know, the plugin executes the same commands you are executing :S and that should work as expected.

I don't know what's going on with your device and your laptop configuration. The only chance we have to fix this big in your case (when the feature is supported but the plugin does not connect the device) is to manually debug the app and check what's going on. If you could debug it that'd be great, maybe the IP obtained from the device is not correct or there is something wrong when executing adb commands.

Thank you so much @cutiko!

[cutiko]

Thank you, and if I get any sort of clue or news I'll let you know

[realdadfish]

I had the same problem with the most recent version 2.4 - the issue for me was that I had an active emulator in the background and that apparently confused the plugin, even though I did not connect to this thing, but the device.

After I turned the emulator down, the plugin was able to make a connection.

[PoojaB26]

I can also vouch for the above solution. Having an active emulator in the background causes this problem.

[eduardoyurencb]

I was the same problem, with the versión 2.4 i have to close the emulator for can run the plugin