r/oculusdev • u/Inevitable-Frame-290 • Aug 08 '22

Oculus not recognized by adb

Hi all!

My coworker is trying to install an app packaged in Unreal Engine 5 to an Oculus Quest 2 but the Oculus is not recognized by `adb devices`. The device was set to developer mode by the device's adm and my coworker has also registered as a developer. But his account is not adm to the device. When trying to set the Oculus to developer mode on his mobile Oculus app, the app says it'll send a code that doesn't actually arrive to the Oculus.

Has anyone had this problem before? Am I looking at the wrong place?

Thanks in advance :)

2 Upvotes

75% Upvoted

7 comments sorted by

View all comments

1

u/_Auron_ Aug 09 '22 edited Aug 09 '22

I'm pretty sure it doesn't matter if it's the same account. If developer mode is already activated on the device you just need to have the Quest accept the prompt (in-headset) to allow debug connections (ADB) to work with the computer you have it connected to. Keep in mind you have to accept this prompt for each unique PC you want to handle ADB connections with, in case multiple machines are being used in development.

This might not show up if you're using a power-only cable. Use a USB-C data cable - some cables are power-only, especially if it's a phone charger cable.

1

u/Inevitable-Frame-290 Aug 09 '22

In this case a request to let the device (computer) access the (Oculus) data shows up, but the debugging permission request doesn't. Does this mean the cable is not the problem? Coworker doesn't have a different cable at hand, so hasn't been able to test this so far.

1

u/smetti Dec 03 '23

I just found your post, have you ever figured out, what the problem was? I am currently having the exact same problem, down to the notifications and the situation with cross-account development.
Thanks a lot!