Skip to main content
Up and Coming
October 3, 2019

ADB device list empty

Hey there,
when I came back to work this morning, I found both of my
Quests unable to be listed under adb devices. I tried Mac and Win but
the list won't get populated.
In difference to yesterday I realised
that every time I connect a Quest to a computer the Quest will ask to
confirm: "Allow Access to Data. The connected device will be able to
access files on this headset." This wasn't there before remains come
back every time.

I am unable to side load any builds which is kind of a show stopper.

37 replies

October 3, 2019
+1
I run in the exact same problem, it looks like Oculus did a firmware update or something. I cant see my sideloaded apps and adb devices gives a empty list.




@NinjaGG
October 3, 2019
[Solved] enable developer mode in your oculus app
BBigGAuthor
Up and Coming
October 3, 2019
Dev mode is enabled. I can access the files. Just ADB wont list it.
Same issue with two headsets, different cable on different usb ports on mac and win...



Processor AMD Ryzen 9 3900X 12-Core Processor, 3800 Mhz Installed Physical Memory (RAM) 32.0 GB NVIDIA GeForce RTX 2080 Ti
BBigGAuthor
Up and Coming
October 3, 2019
Okay turns out there was some miss match. Both quests showed that the developer mode is active but when I went to the phone app it was turned off.
Turned it on again, seems to work.
But why would this happen and even with both devices in the same time? Is this caused by an update or something?
Processor AMD Ryzen 9 3900X 12-Core Processor, 3800 Mhz Installed Physical Memory (RAM) 32.0 GB NVIDIA GeForce RTX 2080 Ti
October 3, 2019
Yes, they made a firmeware update, and there for you need to enable it again.
BBigGAuthor
Up and Coming
October 3, 2019
Hm... notifications would have been nice though.
Processor AMD Ryzen 9 3900X 12-Core Processor, 3800 Mhz Installed Physical Memory (RAM) 32.0 GB NVIDIA GeForce RTX 2080 Ti
mousebear
Honored Contributor
October 4, 2019
Sorry for the subpar experience with this! There was a bug that affected some developers where updating to firmware v9.0 disabled the Developer mode within the companion app. This has since been fixed in a more recent firmware update.
If you need immediate help or want additional support/context on an issue you are having with our platform or integrations: 1. Gather any and all logs , screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.) 2. Please submit a ticket here through the "Contact Us" link (include what you've gathered in step 1). 3. Tag me @mouse_bear once you have done so!
BBigGAuthor
Up and Coming
October 4, 2019
Maybe it would be a great feature to get some sort of notification if headset and app are not in sync::relieved:
Processor AMD Ryzen 9 3900X 12-Core Processor, 3800 Mhz Installed Physical Memory (RAM) 32.0 GB NVIDIA GeForce RTX 2080 Ti
October 4, 2019
@NinjaGG No problem, fortunately i was able to solve it quickly! a notification would be great, and also that we can choose when we want to perform the update.

Win10

Up and Coming
October 4, 2019
Not fixed...!
Tried everything on all the post here.
Reboot, reinstall adb driver, togle dev mode on Companion app, reboot, uninstall, replug, restart... etc...
The only way I have something "Quest" is if I turn off dev mode, and then I see "quest" as a drive. BUT no adb devices.
I can't push UE4 builds to Quest. "No device found"

Windows 8.1
I don't understand why it doesn't find the ADB drivers.
What am I missing here?

In quest:
System update: 3774800165000000
Version    9.0.0.168.450.174044450
Runtime  9.0.0.170.450.174321109
OS version user-377480.16500.0

It was working "yesterday"
What a nightmare.

As I can't upload an image when submitting a ticket, I am doing a post here @ninjaGG


Welcome to http://www.SynthesisUniverse.com it's out there, on the Oculus Share : https://share.oculus.com/app/synthesis-universe--maze--intro-experience