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

New Participant
March 12, 2024

Got the same error here.

If I use a USB 2.0 cable I don't get the error, but if I connect a 3.2 USB, either to a 3.2 or a Thunderbolt 3 port (I have a Z790 Taichi I get the debris message. It's so annoying

Honored Contributor
March 12, 2024

Imagine just for a second buying a television, phone or tablet. Updating it and then having a problem message like this. You would just end up returning the device if it was still under warranty. That might make Meta think next time before pushing out firmware that causes such annoying problems. 

Participant
March 12, 2024

For anyone wondering this happens to me at least once a day with an brand spanking new headset and a brand new official quest link cable bought from the meta store.  So the fix is not an official cable.  It's not a poor cable or a occasional dodgy headset issue.  It has to be a software bug or a hardware flaw built into the actual design.

Participant
March 12, 2024

This is unacceptable and I am thinking of returning my headset. I dont think ive even had it a month and I am experiencing this issue. I never had this issue with my Valve Index.  I use the headset for sim racing, I cant even do half a lap before a big window comes up and I crash into a wall while blind.  There isnt even a setting to disable or ignore it.

Very disappointed in this. It should be an option to disable this warning, or roll back to a previous version of the software. Terrible. 

Participant
March 12, 2024

sad to hear of your bad experience but in part i am happy there are others suffering the same problem. i've given up on them, even if they fix it now i can't use hardware so carelessly managed, i need reliability. what a wasted opportunity by Meta to earn some goodwill in this nascent industry. Meta, this has been absolute muppetry.

Participant
March 12, 2024

Okay I did a little more testing. The error only pops up if I plug in a cable that is not connected to power, including the official link cable. If I plug it into the headset and unplug the cable from my PC, it will give the debris warning. There is one exception, however. If I plug in the charging cable that came with the headset, even while unplugged, it will not give the error. The Link cable is completely clean, however, and should not give any errors. I should also mention I'm on v63 PTC.

Participant
March 12, 2024

Okay even more testing later, it ONLY happens with my Link Cable. My Quest Pro had that error with the same cable a year or so ago, so maybe I just need a new cable...?

March 12, 2024

I don't use a link cable, but I load the Quest3 while I'm playing. If I use a cable that only charges the Quest3 a little so that it discharges slowly, I don't get an error message.

If I use the original Quest charger + cable, which keeps the Quest3 at the same charge level, I get the error message.

Up and Coming
March 13, 2024

What are we to do?

Look at both the length of this post AND the time period that it's been active!!

I don't want to send my Quest 3 back, getting a replacement won't alleviate the problem and there is no suitable (imho) alternative......and is that the crux of the issue?.....do Meta know they have us trapped?

I'm not responding to any more bot generated replies to this issue I reported. It's ridiculuos and intentionally designed to make one jump through hoops and perform pointless resets and testing....'take a photo of the charging port'.....really? What will that achieve exactly?? Do they think I'm some sort of cretin who can't recognise if a port is obviously damaged??? (maybe I should photoshop little amphibious creatures emerging from it)

So the end result?......they'll flag the problem as being fixed due to my refusal to take part in their time wasting exercise 😞

Nothing will be achieved here unless THOUSANDS of headsets are returned due to this fault......and that aint gonna happen!

 

Participant
March 13, 2024

I'm getting the same issue since updating to v62 on the PTC even after a factory reset. Seems to only happen when I use an extension cable of any kind. I've tried three. Meta needs to allow us to disable this.
Note to OP: Sorry for responding directly to your post, it wouldn't let me reply to the topic in general.

Participant
April 23, 2024

They say this has been resolved...NO IT HASN'T, people are still having issues, including myself.  As long as there are people still having moisture/debris issues, regardless to how few, it is NOT RESOLVED!!  This is just a smoke and mirrors reply to keep people off Meta's back about actually fixing the **bleep** problem, they closed the post and said 1 "Accepted Solution."  This company sucks all the way around.

 

Participant
March 14, 2024

First off, agree!  Having this 'sensor' on the port may have seemed like a good idea to Meta, but let's get serious, It ISN'T.  i do not see any other device on the market, except maybe really stylized smartphones, even have a sensor for this stuff.
Second, If your getting the port wet, what the hell are you doing??  Plus, if you see it's wet, I am sure you won't use your device, and if you pick up your headset, I am sure you might notice that something is off when liquid drops from your system.
Third, If there is debris in your port... I am certain you cannot plug in your USB cord because there is something in there, am I right?!? 
Fourth, It is a waste of computing cycles (and thus battery drain) that could otherwise be used for other resources... like playing games.
In conclusion Meta... Update the firmware to not even give a crap about the sensor, because, honestly, how many people out there have actually had an issue that utilized that safeguard??  Using 3rd party cables has caused the message to appear, and on others it hasn't, so actually, is it a programmer's scam to force people to buy the Official Meta Quest Data Cable for a whopping $80??  A cable that can be made for $5 and sold for $20.

-Nough Said

Participant
March 14, 2024

Just wanted to add my comment in here that the problem is occurring for me as well. Never used to have this message, but updated stuff yesterday and all of a sudden it is popping up constantly making using it with PC a nightmare.

I have tried the official cable as well as 4 different high speed USB 3.2 C cables ranging from 5GB to 20GB data rates.

 

Please fix.

New Participant
March 14, 2024

Message popped up for me as well today, keeps spamming me every 20ish seconds.
The headset charges fine, the connection with PCVR is perfectly good, it just keeps alerting me with this obviously bugged message.