Participant

Solved

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

1055 replies
309446 views

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.

TheLegend271265668Answer

Honored Contributor

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

Show previous replies

A

Anonymous

As already mentioned here, I don't use a link cable, I only charge while playing.

A charger/cable with which the Quest discharges while playing works without an error message.
If i use a charger/cable with which the charge level is maintained (original Quest charger+cable), the error message appears.

And now my solution:

It's true that I don't use a link cable, but I still play PCVR with a cable like this:

https://communityforums.atmeta.com/t5/Talk-VR/Virtual-Desktop-with-cable-connection/td-p/1163316

Now I have replaced the Meta charger and the cable with this one:

https://www.amazon.de/dp/B0B7B97J6K + https://www.amazon.de/dp/B07PLSDPYN

...and have been playing since then without any error messages and the Quest keeps its charge level!

In addition, the connection is absolutely stable and the visuals are also better.

M

Massacher

Inspiring

I have a ugreen cable too that I use while playing and its plugged into a power bank. I get it even with a different cable. But the message is random. Can happen in a few seconds, minutes or hours.

A

Anonymous

Do you have also a Ugreen charger?

....can you try this, because i mean, it's the charger that makes the difference.

(UGREEN Nexode 30W)

I got it 2 days ago and since then no more errors.

J

javiermares

Up and Coming

Just returned my Quest 3. Even if they fix it, they've shown a disrespect to users that I dislike, by carelessly introducing a bug that disables PCVR for many users, a bug which was already present in PTC to a production update and not fixing it for more than a month.
During this time, I've learned about the Bigscreen Beyond. I encourage you guys to consider this option as they seem like a more engineering focused outfit.

As customers, we get the behaviour that we tolerate. Vote with your euros and dollars.
For reference, this is a picture of me after I returned my Quest 3
this is me after i refunded my quest 3

H

Halaster

Participant

As nice as a bigscreen beyond might be, that is not even remotely in the same ballpark range or market that the Quest 3 is in. The headset alone will run nearly $1100 after tax and that is without audio or controllers. Just adding their audio straps adds another $140 on top of the base price. Picking up two controllers on top of that and for a setup matching/beating the Quest 3 and you are already nearing $1400-$1500. Not even including the required PC since it is also PC only. This is a completely different type of product being sold to a completely different market, for a price that is nearly triple the cost. Once you have reached that price, you can essentially look at and buy any VR option on the market. It is really not an option for most Quest owners. On top of all of the things above that I mentioned, it does not even have passthrough, which is one of the coolest features of the Quest 3.

F

Fazz

Honored Contributor

Apparently this is a problem on some mobile phones too. Just a YouTube search brings up a whole list about this problem.

https://www.youtube.com/results?search_query=liquid+debris+usb+port

M

Massacher

Inspiring

The thing is there is no liquid or debris in the port. The message that pops up is a bug. It needs to be disabled. Or give us the option to disable it ffs. Approaching two months now and still no fix.

A

Anonymous

This does not mean that there is no bug, there definitely is one, possibly the solution is in the settings of the sensor, it would also be good if this would only take effect at 99%.

As a suggestion.

K

Kiwidll

Participant

Guys we have a new update 120HZ , our headsets can now use 120Hz in our headsets, cant wait to try it out, you know next month maybe...

https://overclock3d.net/news/software/meta-gives-their-quest-3-vr-headset-a-major-link-upgrade-for-pc-users/

S

Smyven

Up and Coming

It’s good that they have acknowledged the issue but the fact that a company can let an issue go on for over a month that essentially prevents a lot of people using there 400+ new bits of tech with their PC’s is quite deplorable and also the article states that this issue applies to those with 4070 cards and below is not quite true as I have the issue with a 4080. Any company worth there weight would have addressed this within a few days, even an acknowledgement on this thread by meta would have shown some sort of compassion towards the issue but there’s never been nothing. Think it’s fair to say people subscribing to this thread really don’t care about 120hz over air link or playing VR in bed, they’d rather be playing PCVR without the 💩

K

Kiwidll

Participant

Dude it was sacrasm, you know a new feature is out promoting 120hz pcvr capability, knowing that a lot of pcvr people cant even use their headsets on the pc because of the error happening.
So chill was just a sarcasm because seeing that and knowing that I cant use my headset really makes me HaPpY.......

M

MortsFam

Participant

So....I just returned my 3 week old Quest 3 to Amazon after getting this error. Not thinking it would solve the issue, but worth a shot. Got the refund. Got the new Quest in last night. Kiwi battery strap, and my Kiwi charging stand worked perfectly fine all night and all this morning.....until the USB-C charging debris/liquid error struck again. Back to only using the cable that came with the headset (which is the only one that will charge it now). I then also ordered a pcvr cable (Syntech Link Cable) and thankfully that worked perfectly fine for doing Steam Link VR. Very dissappointed that this error still came back though with a brand new headset. At least there's a comfort that its 100% caused by the software update.

TheLegend27what is going on with this? You told us over a week ago we can expect fixes soon, but not a word since then. You all are stringing us along with our $500 headsets that dont even charge properly. Roll the **bleep** update back. How hard can it be?????

P

piercy0812

Participant

TheLegend27 This guys got a point, where are the updates about this issue? Its been going on far too long and empty words that "you are working on it" are not enough.

O

OkaMoja

Participant

11 emails. That is how many so far of back and forth rubbish I have so far endured with Meta support. In 11 emails I have asked for a resolution to the USB error and in 11 responses not 1 mention of a solution just automated rubbish about how unfortunate the situation must be and can I please supply the same information that has been asked several times in previous emails and how since the hardware was purchased more than 30 days ago a replacement is not possible and do I want to pursue other alternatives. 11 times I respond saying no I just want a solution to the USB error brought on by V62 update. Next day the same automated bot rubbish is in my inbox saying the same crap over and over and over. How does anyone solve anything with this company.
What I did find however is that by using Virtual Desktop I get a far better connection then air link could ever possibly dream of and is so good in fact that the link connection can be bypassed with no degradation in link connectivity. I use Quest 3 for iRacing and I have found the wireless connection with Virtual Desktop gives me a better experience then the link cable connection.

M

Massacher

Inspiring

Yea bro they don't care. They have our money. They think replying with bots is going to satisfy us. That we'll forget about it. No! Never! I will never forget about it and neither will anyone else. Almost another month has passed and still no fix for the **bleep**en false debris error. Listen dip**bleep**s. Get a programmer to go into the code and delete the entire debris and water warning code. Its not needed.

Skippy111taz

Participant

So I currently have 10 emails going back and forth with the support bots at Meta. I refuse to let them close this support ticket. Every email I send a link to this thread and explain how hundreds of us are having this issue.

We all need to just open up a support ticket and not let them close it until this is resolved. The one email even made me laugh when they said they are getting a large number of tickets submitted. To what I replied "no kidding" with a link to this thread.

My latest email from them actually sounded like an actual person and seems like they are looking into the issue........ maybe 🤔.

I understand that you are having issues with your headset where you are receiving warning on water and debris. I appreciate your response on this.

Please be informed that I will check on this with our team for further investigation. However, we do require more time in order for us to check on this for you. Once we have an update, we will surely let you know immediately.

K

Kiwidll

Participant

The thing that I and quite sure most of users here would like to know is, what kind of compensation will people here get for not being able to use the headsets for more than 4 weeks now (going into end of 5), there have been no responses on what is being done, no updates on the fix, nothing.....
All most people want is just to get back to playing but you took that away and took the money people paid for the device, quite sure some EU consumer laws would be broken here.
I just want to use my device again, without an error popping up every 2 seconds.
also you did make a recall for all elite straps that you know have the issue, but you don't do it with the quest 3, I understand that it would be expensive, but Consumer Laws exist and there is a bottom line a product has to provide.

docaranzat

Participant

Two weeks without using my Meta Quest3. Today I updated to v63. I raced on iracing for an hour. Went to have dinner and upon returning, “voila,” the damned message was waiting for me. I suppose there are Q3 users who don’t encounter this issue. I mean, they play iracing connected with a cable to the PC and keep their headset charged without any annoying messages, just as I did for the last two years.

At least my Q2 does its job. But, believe me, I enjoyed that hour with the Q3.

In the end, total frustration.

Show more replies

Update (3/27/2024):

Update (4/5/2024):

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO