Forum Discussion
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.
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
- +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 - [Solved] enable developer mode in your oculus app
- 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... - 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? - Yes, they made a firmeware update, and there for you need to enable it again.
- Hm... notifications would have been nice though.
- 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.
- Maybe it would be a great feature to get some sort of notification if headset and app are not in sync::relieved:
- @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 - 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.1I don't understand why it doesn't find the ADB drivers.What am I missing here?In quest:System update: 3774800165000000Version 9.0.0.168.450.174044450Runtime 9.0.0.170.450.174321109OS version user-377480.16500.0It was working "yesterday"What a nightmare.As I can't upload an image when submitting a ticket, I am doing a post here @ninjaGG
