USB 3.0 issues with Quest 2
I see lots of similar posts about things surrounding this issue but they usually get brushed off, I am hoping that making this post and outlining what I have done so far it may finally prompt a fix. Essentially the issue is that when connecting with a USB 2.0 connection, the link is completely stable, it reliably connects for several hours and even if the headset is removed and left to "sleep", it reawakens and is still successfully connected (team events in iRacing if you're asking). When using USB 3.0 however, the exact opposite is true, generally speaking in the best case scenario, when keeping the headset awake the whole time, I can sometimes get an hour before a disconnect, however, nearly every time it goes to sleep, it disconnects and sometimes the connection will be lost within minutes of launching with no explanation. For a bit of history, over the course of trying to find a solution to this issue I have: Used a USB A-C 3.0 cable, 2x USB C-C 3.0 cables (including Oculus' own), a USB A-C 2.0 cable, a USB C-C 2.0 cable, replaced my PC's motherboard with a Asus Prime Z-390A, so I would like to think this firmly rules out the frequently posed "solutions" such as better quality cables or using different ports. I have also tried resetting experimental features as I read that sometimes causes issues but this didn't have an effect, nor has making sure that video drivers and my motherboards firmware are up to date, disabled legacy USB support in my bios settings or ensuring there is no power saving settings activated on USB ports. The most frustrating part of all is that recently I did a factory reset of the headset 'cause I couldn't think of any other fix and seemingly this finally gave me a stable USB 3.0 connection using the official cable, which not only lasted until I disconnected it (several hours), but also through cycles of sleeping and waking the headset. I then didn't play for a week and Oculus app version 38.0.0.51.727 (38.0.0.51.727) / headset version 38.0.0.63.727.351486028 installed themselves and now I'm back to the same problem of 3.0 not working and 2.0 being absolutely fine, the factory reset and experimental features reset has not had an effect this time. To be clear, there have been no hardware changes at this time so given it did work as intended previously, it has nothing to do with cable quality or any mechanical issue. Any other insight of fixes that I have not yet tried would be appreciated, although mostly an indication that this is being sincerely looked into as a known issue not just brushed off as an outlier. Please let me know if you need any additional information and I'll post when I can.Solved92KViews9likes49CommentsUSB stick with OTG Adapter on Oculus Quest 2
Hi Guys, I've recently bought an Oculus Quest 2 64 GB and currently trying to watch videos on my USB Stick via Big Screen and Pigasus VR Media Player on the headset. I've got an USB-C to USB 3.0 OTG adapter which I use to connect the USB stick to the headset. I've already formatted the filetype on my USB Stick to FAT32 as I'm aware that's the only USB filetype currently supported by Oculus Quest. When I connect the USB stick to the headset via the adapter, the headset recognizes that I've connected something as I hear a sound but then I'm unable to find the USB stick on any of the apps. I've tried following instructions on the Oculus support page which states that I should find 'Connect media' on Oculus Gallery but the app is no longer available on Quest 2. Are USB sticks supported on the Quest 2 or not? If yes, what are the instructions for accessing USB storage on the Quest 2? Any guidance on this would be greatly appreciated as one of the reasons I got the headset was to watch 3D movies on the go as I thought the Quest headsets supported media playback via USB. Any help would be greatly appreciated. ThanksSolved76KViews3likes19CommentsQuest must be restarted while plugged in to be detected by Win10 PC on Developer mode
We are using the latest Oculus adb drivers, but the Quest in developer mode won't be detected by the PC once plugged in or started up whilst it is plugged in. The Quest seems to need to be plugged in while on, then restarted while still plugged in to be detected. Is this expected and desired behaviour? It creates a few extra minutes of hassle every day when setting the device up for building and testing on from a development PC.2KViews1like7CommentsOculus Quest + Intel RealSense D435i + Unity
Hello everybody, I'm designing a VR performance, in which the user would interact with a real-time point cloud of the space around them. I am using an Intel RealSense D435i depth camera (all the processing is done in the device) and an Oculus Quest, and I'm developing in Unity. My question is: Is it technically possible for the Quest to communicate with the RealSense camera, through the USB-C port ? If not, is it a hardware limitation (for example, the Quest can't even power the RealSense) or is it a driver / android library / unity sdk limitation ? So far, my test pointcloud-viewer project builds without errors and when I connect the Realsense to the Quest I get the familiar sound of the Quest recognizing that something connected to it, but the actual app does not show any pointcloud at all, and the depth camera is clearly inactive (no flashing laser, no IR illumination in the room when viewed in Passthrough mode). This is new ground, so any help would be greatly appreciated!5.8KViews1like9CommentsEnabling USB Audio Output on Quest and Quest 2
The Oculus Go was able to easily output audio via USB. The Quest, despite also running android, doesn't allow it. Any ideas on how to enable it? File managers seem to have proprietary drivers for accessing storage devices. Is it possible to extract the necessary files/drivers from another version of Android and sideload it into the Quest?834Views0likes0Comments