Participant

Solved

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

1055 replies
309386 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

S

Sanastro

Participant

I'm having the same issue. It started immediately after I installed v62 today. When I used the headset earlier today with v60 there were no issues.

I tried multiple different USB cables

E

Elpapodelapelicula

Participant

I have been using my new MetaQuest3 for days with the same cable always connected while in use. I was on 60 and today updated to 62 and I got the debris / water error and hear 3 chrips and the display goes to blank passthrough. I think it may be related to one of the controllers not updating properly and the error always comes up now making my new device practically unusable once I updated to v62.

magic1968

Up and Coming

tell me about it V62 no good till they fix it i add a email off meta this is what it said

It appears that you are having an issue with your device showing Liquid or Debris Headset Warning Message. I completely know where your point of view is getting at, as you really want to use and access most features and content of your device. Allow me to assist you with this.

“Liquid or debris has been detected in the charging port. Please unplug all cables from the headset and turn it off. Wait until liquid dries or debris is gone before restarting your headset. If this message returns, repeat the process.”

For me to get to know the issue much better, would you mind performing the steps below? Once you've done so, let me know what the result will be so that I can provide you with further options on this matter.

Here's how to properly clean your headset:

Required Equipment:

A disposable Soft Bristle Toothbrush.
The toothbrush must be New and Dry to avoid recontamination of the USB port.
Paper towel, Napkin or a dry cleaning cloth

Warning:

Do not use a prepasted toothbrush!
Do not use any liquid or solvent such as isopropyl, bleach..
Wear gloves, safety glasses or a face shield.
Discard the toothbrush after cleaning

Instructions:

Power off the device. Remove all accessories.
In a circular motion, brush and clean inside the USB-C port using the soft bristle toothbrush.
Make sure the toothbrush bristles are getting deep inside the connector and moving around the inner tongue.
Do not overpress down on the toothbrush.
In a scooping motion, use the toothbrush to help the liquid come out of the USB-C port.
Use a paper towel or a dry cloth to absorb and clean the liquid and debris around the port.
Let the device dry at room temperature in a well ventilated area for at least 1 hour (varies).
Do not connect a USB cable to the device until the port is completely dry.
Do not attempt to charge and do not use the device until the USB-C port is completely dry.

Alternatively, use a Compressed Air can to blow inside the USB-C port with 3 bursts. (Safety glasses and PPE must be worn per manufacturing recommendation

and i told there as been no water or anything else near my head set its the V62 what PART OF THAT DONT THEY GET own up to it meta your V62 UPDATE is not working wright you are causing people to loose trust in your updates some are even going to get ride of the head sets and go on to the rivals .i just want you to fix the software PROBBLEM its an isuse like every body says v60 never had probs this dose get your boffins fixing the issuse

A

Anonymous

I am encountering the same issue. That's the last time I ever update this **bleep**ing thing.

C

CBDFARM

Participant

Same issue here in my quest 3. Getting a warning about water or debris being in the USB C port. Never had water near spill on it and port is clear of debris. It still charges, so this is 100 percent a false positive, but kicks me out of pcvr when it does this. Very annoying. Hope someone from the meta team sees this and gets on it and fixes this update.

S

StarKnight929603Author

Participant

This issue has been reported some weeks ago and still Meta had said nothing about it.

C

CBDFARM

Participant

That's sad they haven't done anything about it. Literally had this happen to me today and it's annoying as heck.

TheLegend271265668

Honored Contributor

Hey everyone! It looks like a lot of you are starting to run into this warning when plugging in a cable to the USB-C port on the headset. I appreciate each of you for voicing out your experience running in to this, and I just wanted to get a bit more information before I run it by our internal team to see if I can't get a pair of eyes on it.

Can you confirm which headset version your Quest 3 is currently running? You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 60.#.#.###.###.######### or 62.#.#.###.###.#########.
Are you enrolled in the V62 PTC?
- If so, are you still on the PTC's V62, or the live V62 update?
Which cable are you using when the warning pops up? Where is it plugged in?
- Official charging cable, Official Link cable, Third-party charging/link cable
- Plugged into a Desktop, Laptop, Wall outlet, USB Hub, Power bank, Elite Strap with Battery, etc.
Any workarounds that have caused this warning to not pop up when plugging in a cable?
Can anyone post a screenshot of the error message when it pops up?

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

S

StarKnight929603Author

Participant

The issue appeared on my Quest 3 and also on my wife's one after enrolling PTC and v62. Currently both our visors are running on version 62.0.0.247.343.563460087 (Italian language) and we are still enrolled in PTC because we don't want to reset our devices to go back on live.
Our devices are always plugged with an high-quality USB 3.1 3 meters long cable and the original charger but we have this issue even using the original link cable. The only workaround is keeping it unplugged while using it.

TheLegend271265668

Honored Contributor

Hey everyone! Much appreciated sending all of that over. I'll go ahead and bring these reports to the team to let them have a look into it. As far as rolling back your version to a previous one, that would only be possible if you were still on the PTC update. In that case, you would still be able to factory reset the device after unenrolling to go back to the most recent live update.

Hope to have an update for you all soon!

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

A

Anonymous

They'll have to fix it post haste because I'm returning mine tomorrow. Thank GOD this happened in my first week of ownership. No way will I buy Meta ANYTHING ever again.

magic1968

Up and Coming

i keep geting in headset quest 3 after update v 62 message in screen saying water resedue in usb port on quest what do i do i cant understand it geting any water or damp in it

B

blackbear666

New Participant

Same issue here, right after the update every 10-20 minutes

magic1968

Up and Coming

yes just got quest 3 on and its done it with in 1 min

TheLegend271265668

Honored Contributor

Thanks for your patience everyone! I've just gotten with the team, and engineering has just flagged and begun looking into the issue to try to find a solution. I don't have a guaranteed timeline of when a fix might release, but just know the team is working hard to find something I can bring back to you all. Feel free to keep posting any workarounds—along with the info requested in my other reply, as it can only help the team expedite the process. I hope to have an update for everyone soon!

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

S

spens2403

New Participant

Got same problem today twice. No water or debris in port

pantainn

Participant

I had this with my Quest Pro today, next to the disappearance of the ambient sounds of home environments.

In my case, this only happened with the offical link cable(!) in the front USB-C port. The one on the back: no message (yet). Other cables: OK. I did leave the PTC as I'm done with the experimental stuff now.

I also did the factory reset after backup. While the headset was on zyberVR powerbank, I got several disconnection sounds. No water nor debris.

offtopic but the home environment sounds came back after factory reset, to swiftly disappear again, I don't know what's the cause, no apps were installed at the time.

A

Anonymous

Spoke with help and support, provided all serial number infor and carefully explained the situation. Got an email back 4 hours later that just said "resolved". This is the approach they're taking on fixing this. Get anything other than meta

A

Anonymous

*serial number info*

L

Lemonhead401

Participant

I am experiencing the same issue as everyone else with the new update to v62 and submitted a report to support. I am within my return window on the device from the store and will gladly take it back before that expires if there isnt a fix. wish i had checked for issues before updating.

magic1968

Up and Coming

its a software isuse they say not a hard ware other wise not one quest 3 would be any good its only after the v 62 update they say even if you sent it back got it replaced the v 62 would still be doing it untill they send a update fix

D

DoubleD1798

New Participant

Same issue here, everytime i connect my cable to any power source, pc or just charging i get the warning and it disables data on the cable, cant adb or cable link at all. charging only for me..

magic1968

Up and Coming

meta need to sort it out quick they need to test it out for ages before letting it out to the public its not good

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