Option to Disable the "Liquid or Debris Detected" Error
This notification ruins the gaming experience for many people. It turns the screen off and shows the "Liquid or debris detected, charging port disabled" notification. I'm in a simracing game and have to switch to the controller and close that popup to continue the game, which I already crashed thanks to the stupid notification. I don't care if the charging is disabled or not, please don't turn my screen off in the middle of a game.79Views0likes2CommentsKnown 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.117KViews9likes111CommentsQuest 3 - Liquid & Debris Error
Got the Quest 3 ten days ago. I've gotten warnings about USB-port containing some debris or liquid, when unplugging or plugging the USB-cable to Quest 3. This has also happened when I power up the headset with its power button. It is a popup window with this warning message. I have no idea if this is software or hardware issue. I got this message first time when I booted the headset for the very first time and plugged the USB-cable to headset. There is obviously no liquid damage or visible debris in the USB port, the device charges OK, I've charged the headset maybe 2 to 3 times, and today I again got a warning when I pressed the power button and the headset booted.Solved42KViews19likes17CommentsPotential Fixes and Workarounds for "Liquid or Debris in charging port" warning
Hi everyone, After struggling with the issue of the "liquid or debris found" error message when using the link cable for development and pushing builds, I thought I'd share a couple of workarounds that seem to work some of the time until Meta issues a fix for this. 1) Try a different port on your computer, maybe a different type of port. I had the error pop up nearly 100% of the time I plugged in my cable when I was using a USB type C 3.2 port on my computer. When I switched to using a USB 3.2 type A port with an adapter, I am experiencing the issue much less. I am yet to use this for an extended period of time but I'll provide an update on how frequently the error pops up later. 2) Use ADB over Wifi. If you can get your headset connected at least once, it may be worth the time to get the Meta Quest Developer Hub and try using ADB over Wifi. I believe you have to connect the headset over cable once before you can use this feature but it may save you some time down the line. Of course, this won't work with features like Unreal's VR Preview but you will still be able to package projects and push the APK over wifi as long as you are fine with waiting for the time it takes to package every time.897Views5likes1Comment