Oculus Go not showing up in adb :(

Ok, please just tell me what I'm doing wrong.

I enabled developer mode in the oculus app, approved it on device, I installed the android skd and the oculus go adb drivers, but when I try to build and run in unity it says "No Android devices connected". When i do "adb devices", it gives me an empty list. If I connect my developer-enabled Android phone (same usb-port, same cable) it shows up in "adb devices" just fine.

What am I missing?

 

That should be all that is required and was all that was required for me. You could try adding an organisation to your oculus account or installing the go drivers again from their directions but that wasn't required for me.

 

Similar issues.

1. The Go one time asked if i wanted to enable USB debugging (I really really do) but my controller crapped out then, so couldn't say yes. I have never gotten that dialogue box back, despite a clean reset of Go. Any way to force that back?

2. I am usually work on mac, but am using a windows machine for this Go project, and cannot get adb to run. Installed the .inf file, but cannot run adb command ('adb' not recognized as an internal or external command...). Stupid question, but what "terminal" would I be running adb in? I am using "command prompt" in windows

 

@ormolvig Yes, the Windows command prompt is a terminal. Please see this https://forum.unity.com/threads/how-to-capturing-device-logs-on-android.528680/

 

Can't say I know what happens if you don't accept but have you tried switching developer mode off then back on again. Maybe that will get the popup back. I'd hope you don't need to reset the go.

Assuming you installed adb correctly, you either need to add the directory where adb is to your path or navigate to that folder before trying to invoke the command.

 

It's my understanding that you need to enable Developer Mode in the Oculus app on the device.

 

To get the popup for USB debugging he would have already turned on developer mode. Otherwise you get a popup for transferring files instead. Also enabling developer mode is on the companion app on your smartphone, it isn't on the device itself.

 

Hi!
I have the same problems. Installed everything, enabled Developer mode etc.. - nothing. Empty device list. Then I turned off and on the Go several times and tried "adb devices" every time - and suddenly.. it appeared in the device list !! I opened unity 2018.1 and in the build window, the GO appeared in the device list (Good feature of 2018.1 BTW). I was so surprised, that I just put some objects in a quick test scene and tried a build. And it worked! I used build and run - and the test scene ran on my GO! But after closing it once, I have no idea, how to start it again on the GO. I cant find the app in any list in Oculus home... And unfortunately, the Go was invisible again for the "adb devices" after some time. But it worked ONE time, before falling asleep again. Felt like in the movie "Awakenings" ;-)

I read in other forums, that you should deinstall the go drivers and install the Samsung drivers instead. But didn't work for me...

 

While I've not had any of those problems, I'm also not using the cable that came with the Go. Years ago I had a similar issue with an asus tablet and after a lot of trial and error, I learned the hard way that not all cables are the same. Since then I've always used one of my million micro usb cables that seems to be rock solid.

Might be the issue, might not be, but it's worth a shot. Since adb is much more lightweight than Unity, I got in the habit of always checking adb devices right when I plug it in. I also usually switch it to wifi via adb tcpip 5555 when it appears that way I don't need to leave it plugged in.

I hope you track down your issue.

 

Oculus also just released brand new drivers (version 2.0) today that supposedly fixes intermittent adb issues. You might want to give that a shot too.

https://developer.oculus.com/downloads/package/oculus-go-adb-drivers/

 

well seems to kinda be working. downloaded the new drivers, ran adb devices, which identified go as unauthorized. next time i put on go, pop up screen to allow usb debugging returned. so that was good.

it still takes a few rounds of powering off and replugging usb cable, but when that works for adb, I then can build and run to go with no issues. So massive improvement. thanks all

 

OK this is ridiculous. I ONLY bought a Go so I could hook it up to Unity and write an app for it. The hurdles to simply getting the Go even RECOGNISED on a PC is RIDICULOUS.

I should be able to plug it in, press the button and DO SOMETHING USEFUL. What the hell is going on with these people. Make it work!

Arrrrhhhghghghghgghghg.

Any ideas?

 

Update ADB to version 1.0.39 (or greater). Afterwards, try "adb devices" in an elevated command line to see if it helps with your Oculus Go not appearing.

 

Dude! Worked first time! THANKS!

For anyone else: https://developer.android.com/studio/releases/platform-tools. Unzip and use the ADB in here!

 

Worked like a charm, the first time. I was trying for like 3 days without luck with the new Oculus adb 2 drivers and such but nothing worked. Thanks mate!

 

Might be a stupid question as I am so flustered beyond belief trying to get this issue resolved, but how do I install the ADB from provided link?

 

What worked for me is copying the files adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot.exe into the C:/adb folder

 

Strangely it was this ...
I "thought" I had developer mode on when in fact it was off.

There is actually no easy way to tell this. It's a white dot on a blue background either way.

If abd devices does not work one way, try the other.

Worked for me anyway

 

This solved it for me as well. For some reason when I simply run adb devices it does not show up, but when I run this version it shows up. I had updated everything, the USB driver, the SDK, but not the debug bridge platform tools. Thanks a ton

 

What worked for me is copying the files adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot.exe into the C:/adb folder.
Also you can follow below video -

IF THE DEVICE DOESNT SHOW UP IN THE ADB COMMAND LINE : -Download the new september 2018 release of the platform tools here: -https://developer.android.com/studio/... -extract the new platform folder, -copy the 4 adb related files from the new folder (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot.exe move and overwrite the 4 adb files in the C:/adb folder with the new files It solved the issue for me on a computer!

 

This worked for me as well. Thanks so much!!

 

me too!!!! Cost me like 20 sec while I was at it for 2 hours... thanks a million!!!!!

 

In my case, an Oculus update reset my "Developer Mode". So FIRST check that in your companion app. If it got turned OFF, turn it back ON and you'll be good to go. If that isn't the problem, try the solutions above.

 

For past day have been trying various things like Factory Reset, Reinstalling Drivers, Different Cables not resolve. This worked like a charm the very first time. Thanks.

 

Thank you! Toggling developer mode back on for me worked.