[Feature Request] Camera and Depth raw data access through USB ADB connection
I know there have been plenty of other posts requesting access to the camera feeds from the Quest devices, and I understand the privacy and potential PR issues that might arise from giving apps access to the raw feeds from the cameras. I know Passthrough Over Link exists, but it's not the original data. What I don't understand, however, is why the raw data isn't accessible through a wired ADB connection... Wouldn't it be possible to enable access to the raw data of each camera and the depth sensor through a wired ADB connection, without exposing it to apps running on the device? Akin to what is done for screen capture as described in https://creator.oculus.com/create-build/capturing-video-from-a-quest-headset/ I'm interested in using the data for my university research, but the lack of access to it is rather disappointing.
Error in mobile app when try to set developer mode
I cannot set developer mode after doing a factory reset on my Quest 2. I'm having the black screen issues, so I did a factory reset to try to solve it. But it doesn't help and now I'm trying to get developer mode to disable proximity sensor, but when I switch the developer mode button in mobile app I'm getting the error shown in the picture. The message in red says: we're having trouble completing your request. Try again... I haven't had problems to set developer mode before. But now it seems impossible. I tried all common troubleshooting... Remove phone number / CC in developer account, I created a new developer account, changed the Oculus account, tried in another phone, etc. Nothing helped. Because black screen I cannot even enter the Oculus home. Tried all known troubleshooting to solve Oculus black screen issue, nothing helped too.
No Developer Mode on Quest or Rift
Been trying for 7 days now- numerous emails back and forth with tech support 1 Quest 2 2 Rifts Iphone About ready to give up. Was going to teach VR with Unity and Oculus, but only thing students have learned so far is that if you want to be a developer then probably best to buy a different headset. Other companies simply enable developer mode - not tied into Facebook.
Can't find more settings to access developer mode on Oculus app (quest 2)
I'm signed up successfully as a developer on Oculus. My headset is synced to my phone app perfectly, it says it's connected. I want to go into developer mode through the app, and every tutorial I find on how to achieve this says I have to access settings to do so. However, there are only two settings options I can find -- Account Settings, and Privacy Settings. Neither of these contains what I'm looking for. Supposedly there is a "more settings" option somewhere, but it doesn't seem to exist. Why won't it allow me to go into Developer Mode on the app?Cannot disable Guardian anymore
Some serious issues here on a couple of Quest units (one with v34, the other with v35) Once I turn Guardian off in the Developer menu (BTW, congrats for messing the UI up in v35...) I can still see the boundaries and as soon as I walk outside passthrough kicks in... a couple of other units (v33) work perfectly, but the updated ones are buggy. Is it just me? I tried to disable and re-enable developer mode in the app, cleared the location history... it just gets stuck. Sometimes I cannot even enable Guardian anymore, the button turns blue, but cannot define a new area, but still I cannot disable the existing one... Since I'm testing a free roaming app (10x10 meters with no active boundaries) I NEED this badly. It's an hit and miss situation: upon reboot sometimes it works just once and then gets stuck again, sometimes it boots like that no matter what. It might help to know that I'm using AirLink and I need to set the floor from there... maybe AirLink is messing with the Quest OS? Seems a pretty serious bug to me anyway. EDIT: Under further investigations, it turns out that you MUST reboot the Quest in order to activate/deactivate Guardian boundaries control... not useful at all if you need to activate/deactivate multiple times per session for testing purposes!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.
