At this point I'm expecting to be able to run;
7. Run scrcpy: scrcpy -s 192.168.1.185:5555
However, both devices are disconnected when pulling the usb cable out.
As an alternate permutation: If I leave the usb connected and run step #7, scrcpy loads and then if I pull the usb - it disconnects.
Upon further testing and after unplugging the USB, I can still use: adb connect DEVICE_IP:5555 and connect to the device. Can also ping the device also and get a response.
It appears to just disappear from the list of devices within ADB (causing SCRCPY to fail to launch as there's no device present in ADB).
I think it has something to do with MAC USB enumeration killing ADB, not the device disconnect itself killing the ADB.
Is anyone chasing a similar issue and resolved by chance?
[disconnect USB] $ adb connect 192.168.1.185:5555 connected to 192.168.1.185:5555 $ ping 192.168.1.185 PING 192.168.1.185 (192.168.1.185): 56 data bytes 64 bytes from 192.168.1.185: icmp_seq=0 ttl=64 time=757.020 ms 64 bytes from 192.168.1.185: icmp_seq=1 ttl=64 time=210.854 ms 64 bytes from 192.168.1.185: icmp_seq=2 ttl=64 time=768.758 ms $ scrcpy adb: error: failed to get feature set: no devices/emulators found 2018-07-03 16:40:33.600 scrcpy[37756:4675145] ERROR: "adb push" returned with value 1 $ adb devices -l List of devices attached [reconnect USB] $ adb devices -l List of devices attached 1KWPH813818187 device usb:336592896X product:vr_pacific model:Pacific device:pacific transport_id:5 192.168.1.185:5555 device product:vr_pacific model:Pacific device:pacific transport_id:6