I'm not sure if the scope of this fork could cover something like this, but as stated by many users of scrcpy there are some of us which our use case requires a wired solution for an android to android connection
The reasons, which are not limited to the following, include:
- wired stability / wireless radio interference
- hardware obsolescence (much faster usb 2.0/3.X port than onboard Wi-Fi chip)
- embedded android device in systems where an SoC or device upgrade/replacement is not possible
Internally when a TCP connection is established the internal scrcpy command that is run is something like this:
scrcpy.exe --tcpip=192.168.100.1:5555
And when a USB connection is made is just plain scrcpy.exe (-d if there are multiple ADB usb devices)
It seems that the original mingzhixian project, already calls a function to check for an ADB usb connection, so maybe it's feasible to implement this option, but correct me if i'm wrong.
I'm not sure if the scope of this fork could cover something like this, but as stated by many users of
scrcpythere are some of us which our use case requires a wired solution for an android to android connectionThe reasons, which are not limited to the following, include:
Internally when a TCP connection is established the internal
scrcpycommand that is run is something like this:scrcpy.exe --tcpip=192.168.100.1:5555And when a USB connection is made is just plain
scrcpy.exe(-dif there are multiple ADB usb devices)It seems that the original mingzhixian project, already calls a function to check for an ADB usb connection, so maybe it's feasible to implement this option, but correct me if i'm wrong.