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
- same here, I had to turn on dev mode again on mobile app, so unknown folders shows up now on headset, but ADB drivers can't start so headset isn't recognized when I plug it in.
- Similar here - Quest shows up in explorer with all files etc, but Unity can't recognise it as a device to build to.
- I'm having the same problem. I had to set the Quest back to developer mode, and after that I get an ADB Intefrace error when checking it in the Windows Device Manager - it says there are no compatible drivers for the device.I've tried re-downloading and re-installing the Oculus ADB driver but that hasn't helped.Like OlivierJT above, I'm running Windows 8.1 and my headset lists all the same versions...System update: 3774800165000000Version 9.0.0.168.450.174044450Runtime 9.0.0.170.450.174321109OS version user-377480.16500.0
similar problem:
After updating the firmware 0.9 on windows 7, the quest stopped
connecting to the computer. I see In device manager shows Interface ADB
and Interface XRSP
9.0.0.168.450.174044450
9.0.0.170.450.174321109
377480.16500.0
NinjaGG said:
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.
ok, but could the fixed version firmware be updated soon?- This might be a problem with older versions of Windows not recognizing the new firmware. After failing to get my main Windows 8.1 PC to recognize the Quest in developer mode, I tried a Windows 10 Surface. This did work after I updated it to the latest version of Windows, and I can now sideload apps from it.I hope there's a proper fix coming - my Win 10 Surface isn't powerful enough to run Unity, and having to copy files from one PC to another greatly slows down development.
- Same as rfvcx reports, after the firmware update, on Windows 7 the drivers stopped working and can't be successfully reinstalled.
Neither in Developer Mode nor in normal mode the drivers can be installed. Quest as external drive not working either in normal mode.
9.0.0.168.450.174044450 - Did you get it working yet on Windows 7 ? I don't believe it says anywhere you need windows 10 to develop, in which case, they owe us a fix. I put a ticket in last week and haven't heard back yet.
- @Ocubrick no luck for now on Win7. There's an open bug report here: https://developer.oculus.com/bugs/bug/758685794572325/
- Введите свой комментарий
mariuxtheone said:
Same as rfvcx reports, after the firmware update, on Windows 7 the drivers stopped working and can't be successfully reinstalled.
Neither in Developer Mode nor in normal mode the drivers can be installed. Quest as external drive not working either in normal mode.
9.0.0.168.450.174044450
I solved the problem with ADB drivers, now everything works fine on Windows 7
