-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wireless disconnection when removing USB (oculus go) #189
Comments
I can't reproduce (with a Nexus 5, not an Oculus go). If I unplug the device, there is still the device connected over TCP. Your device seems to restart/reconfigure adb when you unplug it. |
I've been doing some more 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. I think it has something to do with MAC USB enumeration killing ADB, not the device itself.
|
I use this for my Oculus Go all the time, never have an issue. However if I connect to my Go via WiFi BEFORE disconnecting the USB, I ALWAYS get disconnected. I have to FIRST disconnect the USB connection, THEN I can connect to it over WiFi with ADB. Think you're just doing it wrong. |
please see #209 this might resolve the issue you are having |
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.
Is there a better method for getting wireless connectivity working?
The text was updated successfully, but these errors were encountered: