Mixed Reality Link using USB-C?
I've been using the Mixed Reality Link (Windows laptop) + Windows app (Quest 3) sucessfully at home, both devices connected over WiFi with great success. Today I am travelling by train and wanted to do the same thing. On the train, there is no WiFi, so I brought my USB-C cable, and tried to connect that way, but it does not work. I can see my laptop listed in the Windows app on the Quest 3, but I can not connect, and I can't create a new connection using the QR code either. Is it not supposed to work over cable? [The cable is fine; for an example, I can use the Meta Horizon Link app on Windows to connect that way. Win11 25H2 latest update 26200.7705, Quest 3 V85.1034]146Views0likes2CommentsUSB 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.Solved93KViews9likes49CommentsQuest 3 USB connection to windows 11 prof (development)
what worked for me on windows 11 Prof.: Set energy-mode on MQ3 to 4 hours bevore going to sleep plugged the MQ3 into my PC (USB-C Highend cable) doing the kill-server and devices ("adb kill-server", "adb start-server") in command line (cmd) then go into your mobile-phone to the meta app where you have the Q3 linked already and then disabled "Developer Mode" and enabled it again Now then the popped up appeared in MQ3 Menu. Hope this helps someone.598Views0likes2CommentsKnown Issue - V65 - V67 USB-C Debris/Water Warning
Not a solution - Marking for visibility Known Issue Hello everyone! I have observed that a significant number of users are still encountering the USB-Debris error even after the V64 fix was distributed to everyone. Consequently, I have taken the initiative to inform the team and create this fresh post in order to distinguish between those who faced the issue in the previous post and those who are currently experiencing it on V65-V67. We would greatly appreciate if everyone could please provide the following information: What's the full version number of your headset? (62.0.0.####### or likewise) Quick Settings > System > Software Update What's the full version number of your PC app? (62.0.0.####### or likewise) General > Scroll down to the bottom of the page. Is your PC app on PTC? Are you enrolled in Quest PTC? Any potential workarounds? Which headset is everyone using? Is this only happening with the Quest 3 currently, or is anyone experiencing the same thing on their Quest 2 and Pro I'll do my best to keep you all updated as soon as I find out anymore information! Update 5/26/24 Hey everyone, a little update for you - our awesome engineers are on top of this issue. Don't forget to send in your detailed reports and share any info you have, especially if this problem is new to you. Your input is super valuable! Update 6/6/24 I just wanted to give everyone a quick update that there haven't been any major changes yet. However, I want you all to know that I'm actively monitoring this thread every day and passing on any information that users provide to the engineering team. Update 6/11/24 The engineering team would like me to gather the serial numbers of the headsets of all those affected. Please send me a private message with your serial number. Please do NOT send your serial number in this or any thread publicly. Update 7/3/24 Thanks to all who sent in their Serial numbers. Our engineers are still looking into this matter and are working hard to resolve it in an future software update. Update 7/9/24 We appreciate all those who have provided their serial numbers. If you are still encountering the issue even after updating to V66, please reach out to our support team via private message here for further troubleshooting assistance.118KViews9likes111CommentsA suggestion to utilize magnetic-based cable instead of usb-c connection for oculus to PC connection
So, I have used the Quest, Quest 2 and Quest Pro, and while the products had been mostly satisfactory, one of the most mind bugling issues I had was the relative unease of use of the USB-C connection mechanisms. While using the Oculus, many times I had to inadeptly move my position in a way to pull the cable, and in doing that I feel a sympathetic discomfort for my Oculus and the cable especially when it is forcibly pulled out with side friction, and as every time this occurs it decreases the life expectancy of the link-cable, the quest usb-c port and eventually the whole product use-cycle length. My quest began failing this way after a year or two, and it became very difficult for me to stably connect the usb-c cable so that pc tethering became unusable. So why not implement a magnetic-attached cable attachment solution, so that every time the cable is pulled beyond thresholds it simply disconnects and fall off without inducing any sharp feeling of cable pulling and goldfinger-frictioning? I mean, for the design to be reliable it takes a little work, but the cable that is implemented on my LG DualScreen's second screen phone case is just reliable enough for me to think of it as a good prototyping start point. In addition to these pros, the magnetic-attachment mechanism is also less susceptible to debris and/or liquid damages as recently occurred to my oculus pro....844Views1like0CommentsQuest Pro - Developer mode issue
Looking for help in getting the Quest Pro into developer mode. I have allowed the developer mode on the MQDH mobile app and within the headset however when I plug the USB-C cable into any computer it makes the noise as if something has connected but never pops up with the allow device and hence does not appear within explorer. Has anyone seen the same issue and got a solution to this?664Views0likes0CommentsUsing external USB-C camera
Hello, I'm trying to use an external USB-C camera connected to the Oculus Quest HMD. I'm trying to access to this camera in Unity. When connected, I'm using Android native API to ask for USB permission. But unfortunately the permission dialog does not appear, I can see the 3 dots screen instead of my app until I disconnect the camera in order to get back in my app. Is there some specific configuration to do in order to ask USB camera permission? And is it possible to switch my app in non VR mode just to check if the permission dialog appear in this mode? Thanks for your help.7.6KViews0likes6Comments