05-07-2018 02:25 PM
05-08-2018 03:24 AM
05-10-2018 11:46 AM
05-15-2018 12:55 PM
I can confirm that the Oculus GO ADB drivers 2.0 allow me to successfully connected to the Oculus GO and thus I can push my Unity builds to the device. However once I restart my computer it no longer connects to the Oculus GO. When attempting to debug this I found that once I ran ADB devices in command prompt I get this:
daemon not running; starting now at tcp:5037
daemon started successfully
Once this has occurred the Oculus GO is instantly connected again. Note that this only occurs with the Oculus GO, all other devices connect as expected.
I know very little about this but I would guess that daemon tools should be running without me needing to start it?
Any insight would be much appreciated.
05-16-2018 03:38 AM
05-16-2018 09:38 AM
05-16-2018 09:49 AM
11-15-2018 03:32 PM