Scrcpy: adb server version (32) doesn't match this client (39)

[AndikaTanpaH]

hi, any idea to working with ADB 32 via WIFI?
it's working only via USB, but i trying via WIFI and i got that/

user@user:~$ adb connect 192.168.1.205:5757
connected to 192.168.1.205:5757

user@user:~$ adb devices -l
List of devices attached 
192.168.1.205:5757     device product:Infinix-X552-B1 model:Infinix_X552 device:INFINIX-X552

user@user :~$ scrcpy
INFO: scrcpy 1.12 <https://github.com/Genymobile/scrcpy>
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1

note: I use ubuntu 16.04 32bit, I cant use latest platform-tools its not available for 32bit again on linux

[rom1v]

I cant use latest platform-tools its not available for 32bit again on linux

It seems you can use adb 39, since you just executed it :wink:

You can specify the adb you want:

export ADB=/path/to/your/adb
scrcpy

If you use the snap package, the adb used is a specific snap directory. Use this one to execute your adb connect.

[AndikaTanpaH]

hi @rom1v thanks for your suggestion.

it's working for now, i follow from this issue https://github.com/Genymobile/scrcpy/issues/723#issuecomment-521256246

for now i'm using adb from installed scrcpy snap edition:

scrcpy.adb connect 192.168.1.205:5757

export ADB=/snap/scrcpy/205/usr/lib/android-sdk/platform-tools/adb

scrcpy

server and client run on same version (39)

[axi92]

Ubuntu 18.04
Is there a way to override the ADB to use an external adb?
We use platform-tools to install and update our needed tools.
So we don't want to use the packed adb in snap.

[frederickjh]

@axi92 You should ask your question on the scrcpy snap project page issue queue, as you would be more likely to get an answer there to your question.

[frederickjh]

Thanks @AndikaTanpaH!
This is what I figured out too. I am going to open an issue on sisco311/scrcpy-snap that this should be better documented to use the build in adb, ie. scrcpy.adb if you get an error message similar to the title of this issue.

For anyone else that finds this see the sisco311/scrcpy-snap project page documentation to use the builtin adb tool for more information.

[kamalx]

I am at version 30.x.x of Android sdk platform tools (adb version 41). The method shown above gave me some hope until I tried it and got this:

scrcpy.adb tcpip 5555
adb server version (41) doesn't match this client (39); killing...
ADB server didn't ACK
Full server startup log: /tmp/adb.1000.log
Server had pid: 5829
--- adb starting (pid 5829) ---
adb I 11-16 01:27:12  5829  5829 main.cpp:57] Android Debug Bridge version 1.0.39
adb I 11-16 01:27:12  5829  5829 main.cpp:57] Version 1:8.1.0+r23-5~18.04
adb I 11-16 01:27:12  5829  5829 main.cpp:57] Installed as /snap/scrcpy/254/usr/lib/android-sdk/platform-tools/adb
adb I 11-16 01:27:12  5829  5829 main.cpp:57] 
adb I 11-16 01:27:12  5829  5829 adb_auth_host.cpp:416] adb_auth_init...
adb I 11-16 01:27:12  5829  5829 adb_auth_host.cpp:174] read_key_file '/home/eskimo/snap/scrcpy/254/.android/adbkey'...
adb I 11-16 01:27:12  5829  5829 adb_auth_host.cpp:391] adb_auth_inotify_init...
adb server killed by remote request

* failed to start daemon
error: cannot connect to daemon

whereas, with the newer adb:
platform-tools ❯ adb --version Android Debug Bridge version 1.0.41 Version 30.0.5-6877874 Installed as /home/eskimo/Android/Sdk/platform-tools/adb platform-tools ❯ adb tcpip 5555 error: no devices/emulators found platform-tools ❯ adb connect 192.168.1.100 connected to 192.168.1.100:5555 platform-tools ❯ adb devices List of devices attached 192.168.1.100:5555 device
Eventually, the only thing that worked for me was to follow the guide and build from source. I am on Ubuntu 18.04 and i had to get meson from pypi (pip3 install meson) instead of apt.