Forum Discussion
Can't see USB devices on Quest 2
I'm trying to communicate with a Wireless Dongle plugged in to the USB C port on the Quest 2. I have no problem doing so on the Quest 1.
The Quest 2 does not seem to recognize the device at all.
It does not show up using lsusb from adb.
There is no beep, confirmation sound like Quest 1 when plugging it in. No permissions window pops up.
My manifest is set to use the android.hardware.usb.host feature but UsbManager.getDeviceList() is returning nothing.
Is the USB Host API locked down on Quest 2? How do I enable USB Host? Thanks
The Quest 2 does not seem to recognize the device at all.
It does not show up using lsusb from adb.
There is no beep, confirmation sound like Quest 1 when plugging it in. No permissions window pops up.
My manifest is set to use the android.hardware.usb.host feature but UsbManager.getDeviceList() is returning nothing.
Is the USB Host API locked down on Quest 2? How do I enable USB Host? Thanks
6 Replies
- Same issue here.I contacted technical support regarding this issue. They responded that the problem most likely originates from the update to Android 10 on the Quest 2 (as opposed to Android 7 on the Quest 1).Checking the Quest 2 filesystem at /system/etc/permissions/, there is no file named "android.hardware.usb.host.xml", which seems to be necessary to enable USB host at the system level (cf. this issue: https://stackoverflow.com/questions/16006889/usbmanager-getdevicelist-returns-empty).Since the filesystem is read-only, there seems to be no easy solution at this point.
- So they did update the Android version... I did not know it was that big a jump.
Also interesting about the USB host file... but what if a USB device is connected using an OTG adapter? Maybe that will have the system create the xml file? Hmmm... is a OTG adapter even needed? I think with the Quest 1 they made some changes to how the USB port works on the device at some point, because in the beginning I needed an OTG adapter I think, to get it to work, and later on I didn't.
So maybe try with an without an OTG adapter. I have seen a youtuber that talked about having used an X-BOX USB controller with the Quest 2. But that might of course be part of a limited USB support to try to protect the Quest 2 from being rooted. - I tried several different adapters, unfortunately without success. If I discover something new I will let you know immediately.Interesting that some folks managed to connect the XBox controller via USB. If true, there still may be a way...Best of luck!
- either your cables don't communicate what the usb sends or the oculus dosen't accept it.
- I have a semi similar issue on my Mac, lsusb shows the device, but adb devices doesnt and I have reinstalled them. I also never get the USB Debugging Dialog to pop up.. When I boot into Windows 10 it works but my main development is all done on my mac.. WTF :)
- Not sure if this will help but there is a SideQ app called "Android System Settings Launcher" that allows access to Android Dev mode in the settings like a XDA mobile phone so it has some extra USB related options. Not sure what the effect would be to the rest of the stack tho. Good Luck !
