Skip to main content
Participant
February 7, 2024
Solved

(Resolved) Known Issue - V62/63 USB-C Debris/Water Warning

v62 has a big problem with USB port sensor (found the very same issue on my Q3 and the one of my wife)... when used with an extension cable (even if it is a quality cable) from time to time star showing the debris-water warning message. Of course there is no debris or water, just a nasty software false alarm.

This topic has been closed for replies.
TheLegend271265668
Honored Contributor
March 8, 2024

Not a solution - Marking for visibility

Known Issue

Status: Fix rolling out in V64 - Public Release

Hey everyone! Back with another update. I got word from the team that we should start seeing improvements in the upcoming updates, however, they want to stray from promising any specific timeline for the fix just yet. I know everyone is still prepped for jumping back into their pop-up free VR experience, but this is the extent of information available to me at the moment. Hopefully I can find out and share more with you all soon! Thanks for remaining patient while the team works towards improvements!

 

Update (3/27/2024):

Hey everyone! After waiting patiently from the team for any updates I was able to share with you all, I just got confirmation that we should see a fix in the upcoming V64 build. I've tried to get word about a potential release for V64 & V64's PTC, but I haven't heard anything about it just yet. Be sure to keep an eye on the Announcements board, as that's the place we'll be posting about the PTC and Official releases.

If you continue to experience the error on a V64 build, please let me know! I'd also appreciate if you included your V64 software version number.

  • You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 64.#.#.###.###.#########.

Update (4/5/2024):

Hey again! I'm glad to see that a lot of you are no longer having issues after the rollout of PTC's 64.0.0.419.370.583580230. After bringing more reports to our team, I was notified that the official fix hasn't shipped just yet, but it's a really good sign that improvements are being shown in the PTC builds! The official fix should be rolling out in the public release of the V64 build.

Thank you again for your patience, and please be on the lookout on our Blog or the Announcements board for when the public build is officially announced. Of course, I'll be notifying you all here as well once I find out more information!

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably

1055 replies

Participant
March 8, 2024

Is there really no response or fix for this, every youtuber denies that it exists, most people on reddit are saying that it isn't an issue, I cant return my headset (they cant replicate the issue so the headset is in good condition), I cant get any sort of a refund because it has been a few months now. And worst of all, meta isn't talking about it or saying that they are working on a fix, or anything similar.
Honestly they fell really hard in my eyes now.........

Up and Coming
March 8, 2024

I think they (Meta) have confirmed that they have replicated the problem?

ergo....it isn't in 'good condtition'

 

New Participant
March 8, 2024

Same problem here! Hope it can be fixed soon!!!!!!!!!!

TheLegend271265668
Honored Contributor
March 8, 2024

Not a solution - Marking for visibility

Known Issue

Status: Fix rolling out in V64 - Public Release

Hey everyone! Back with another update. I got word from the team that we should start seeing improvements in the upcoming updates, however, they want to stray from promising any specific timeline for the fix just yet. I know everyone is still prepped for jumping back into their pop-up free VR experience, but this is the extent of information available to me at the moment. Hopefully I can find out and share more with you all soon! Thanks for remaining patient while the team works towards improvements!

 

Update (3/27/2024):

Hey everyone! After waiting patiently from the team for any updates I was able to share with you all, I just got confirmation that we should see a fix in the upcoming V64 build. I've tried to get word about a potential release for V64 & V64's PTC, but I haven't heard anything about it just yet. Be sure to keep an eye on the Announcements board, as that's the place we'll be posting about the PTC and Official releases.

If you continue to experience the error on a V64 build, please let me know! I'd also appreciate if you included your V64 software version number.

  • You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 64.#.#.###.###.#########.

Update (4/5/2024):

Hey again! I'm glad to see that a lot of you are no longer having issues after the rollout of PTC's 64.0.0.419.370.583580230. After bringing more reports to our team, I was notified that the official fix hasn't shipped just yet, but it's a really good sign that improvements are being shown in the PTC builds! The official fix should be rolling out in the public release of the V64 build.

Thank you again for your patience, and please be on the lookout on our Blog or the Announcements board for when the public build is officially announced. Of course, I'll be notifying you all here as well once I find out more information!

Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably
Participant
March 8, 2024

That makes no sense. Either they replicated it and fixed it or they didn’t. There is no in between. If they replicated it they should know if they fixed it. Wtf?

Up and Coming
March 8, 2024

Agreed. It's been a month. Resolve it now - you had the solution in v60. You can take months to be clever and roll out your vague "improvements". You will respect your paying customers. cc Ryanality TheLegend27 

Honored Contributor
March 8, 2024

A similar situation happened with Quest Pro controllers. Where a pop-up message would say the controllers were overheating when they weren't. A year on and the problem still isn't fixed for some people it seems (link below). Does anyone know if the water debris issue is widespread? It seems to be happening to a fair few people, but is it happening on all Quest 3 headsets? And if it isn't happening on all Quest 3 headsets has anyone done a factory reset to test if it fixes the issue? Also, is this only happening when connected to PC-VR via cable, or is it happening when playing stand alone and using a battery power bank?

There should be a way to disable these horrible pop-up false messages, if indeed they are false. And if they are not false then Meta should make this fix a top priority. Bricking people's headsets with firmware and expecting them to wait months for a fix, that is some cheek if you ask me..

https://communityforums.atmeta.com/t5/Get-Help/Quest-Pro-controllers-giving-overheating-message/td-p/995907/page/9

Up and Coming
March 8, 2024

yes they are false, yes it is widespread (apparently affecting most if not all charging setups (cable and charger) that are cable of keeping or increasing charge), yes we have tried factory resets and they don't work, the error mostly it seems to occur when PCVR is connected but has also been reported with battery power banks.

please Fazz upvote and comment on the reddit post linked below, the only way 1.29 trillion dollar corporations are motivated to do anything is by public pressure by social media posts that garner attention https://www.reddit.com/r/OculusQuest/comments/1ba0s50/the_quest_for_a_fix_water_warning_unfixed_for/

also please share with VR, gaming and hardware influencers. thank you

Participant
March 9, 2024

I can guess the fix use the official Link cable, third party charging cable should not be used with the quest 3 thanks Meta great solution i THINK my next VR headset might be the big screen Beyond 2.

Up and Coming
March 9, 2024

So do you think they’ve gone the Apple route and require official meta cabling, shame if they have. Sure I heard this issue applies to their own expensive cable. Be interested to know more

Participant
March 9, 2024

we are sarcastic bunch in Canada

New Participant
March 9, 2024

I, too, am having this water in the USB-C port error. Didn't happen in January when I first got the unit. Only after it started to apply updates after the initial V60 configuration. 

Honored Contributor
March 9, 2024

I saw someone mention in this thread that this problem seems to happen more between 80% and 100% battery life of the Quest 3. Do you think it might have something to do with what Meta have done to try and get more battery life out of the Quest 3 internal battery? I saw this on Road to VR (link below). Maybe send Road To VR a message about this error message you are now getting and they might do an article about it. After reading this article from Road To VR, it's obvious Meta have done some big changes that has now created this problem.

https://www.roadtovr.com/meta-quest-link-update-120hz-battery/

Up and Coming
March 9, 2024

It happens even on low charging states, I couldnt find a charging state low enough that the error would stop occurring

Inspiring
March 9, 2024

Same. It happens at random no matter what percentage the battery is at.

Up and Coming
March 9, 2024

For myself the water debris warning happens when I first put the headset on and the lenses fog up, It will happen a few times until the lenses warm up a little and stop fogging, after that there’s no issue.

March 9, 2024

I want my money back! Headset worked for 3 days before getting this liquid/debris message, essentially rendering my headset useless for PCVR. This bull**bleep** cost me 800eur meta you mother**bleep**ing scammers

Inspiring
March 10, 2024

At least you can refund it. I'm stuck with a useless piece of junk. I can send it back to get a replacement but what use is that it will update to v62 and I'll be stuck with another piece of useless junk.

They're taking their sweet ass time processing the replacement.

You can go to your account and start a refund request.

New Participant
March 9, 2024

hello.

my quest3 has the same problem (software version 62). Some weeks ago I got a repaired quest3 but after some days it has the same problem. Now, after playing around with different cables and power plugs, i found 2 workaround, which allows me to load and use the quest3.

1: power-off the quest3, completely. Then the usb cable (original) is plugged and the VR starts loading. Then the quest3 can be powered-on. Now I can use it for some time. Typically it runs a long time, mostly the usb becomes deactivated after a standby.

2: even if the usb-c is deactivated, the VR can be loaded with a (normal, not original) cable. I use a cable which has one end usb-b and the other end usb-c. The power plug is with usb-b. The quest3 keeps loading all the time, the deactivated usb-c seems to have no impact. As well, a usb-power bank can be used instead of a power plug.

That are the workarounds I'm using for the moment. I hope to get support from Meta soon.

Inspiring
March 10, 2024

"I use a cable which has one end usb-b and the other end usb-c. The power plug is with usb-b. The quest3 keeps loading all the time, the deactivated usb-c seems to have no impact. As well, a usb-power bank can be used instead of a power plug."

So it only works if you use the official cable first? And you use a USB B? What does that look like?

I'm not going to buy the official cable. No way. I'm not buying anything from them ever again. Not going to buy Quest 4 or anything else they or Facebook or Instagram make. Nothing from Meta or anything related to Meta.

Complete boycott of Zuckerberg and his bull**bleep** products. 

I look forward to Meta, Facebook and Instagram all falling πŸ˜‚πŸ€£πŸ˜‚πŸ€£πŸ€£πŸ€£