Quest 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.
Oculus 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!Enabling 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?
