Inspiring

Solved

Quest 3 - Liquid & Debris Error

17 replies
43321 views

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.

This topic has been closed for replies.

TheAntiSocializerAnswer

Honored Contributor

Hey everyone! Just jumping in here to report that I'll be locking this thread since we have another one right here that we've flagged internally.

If you're having this error pop up after updating to live version 62, please don't hesitate to post your experience in that thread and we'll be glad to have our team do some further reviewing!

Thanks!

Sometimes it's okay to be a little Bing Chilling

M

Maus7

New Participant

Just used my Quest 3 first time. After 2 hours got the same Fluid in Headset warning. Curious if it will happen again.

E

Emwarz

New Participant

I just had this after no actual water damage. It now says it every time I turn the headset on! Any updates on your end?

E

Ezez333Author

Inspiring

I returned my headset, got another Quest 3, but I haven't yet opened it, been too busy before weekend.

Anyway, I doubt it has anything to do with liquid, guy in the shop I bought my Quest 3 from was guessing it could be some sort of faulty sensor - who knows.

A

AdrellaDev

New Participant

I'm getting the same issue on my Quest Pro. It's been in a case and no possible water damage. Wondering if there's a software issue.

L

Lemwar

New Participant

done nothing different and the message has disappeared. For now. I’ll update if it comes back. I contacted meta and they were willing to replace so don’t worry if this happens to you.

TheAntiSocializer

Honored Contributor

[NOT A SOLUTION] - Just marking this as the solution for visibility

Hey everyone! I noticed this thread getting a bit of traction, so I wanted to get this flagged with the right team.

To get this into the right hands, could everyone still running into this please answer the following:

Could you provide a photo of the error message?
Does it happen when using standalone, connected to PCVR, or both?
What's the full version number of your headset? (57.0.0.####### or likewise)
- Quick Settings > System > Software Update
Is your headset on PTC?
Any potential workarounds?

As soon as I get this, I can get this looked into more in-depth!

Sometimes it's okay to be a little Bing Chilling

G

Graphic

Participant

Heads up everyone, this AntiSocializer is going around to several unresolved posts marking them as resolved. Their whole job is seemingly to fraudulently mark big issues that Meta wants to keep quiet at resolved even though they are not resolved at all.

Re: Quest 3 app sharing not working

Re: Anyone else seeing terrible lens glare like glasses without anti-reflective coating?

Re: Cant view synced videos on Meta Quest app

Just a few here. There were several more but they wait until the noise dies down, then they edit the [NOT A SOLUTION] part out but do not change the resolved status.

TheAntiSocializer

Honored Contributor

Hey Graphic! As Choleni had explained, I do usually drop a disclaimer at the beginning of the comment for everyone to know it's not a solution to the issue. The reason for marking it as the 'solution' however, is that we want everyone who comes across the specific threads to be able to find our posts quickly so that we can make sure we're gathering the information that our engineers require to ultimately resolve the situation faster.

As for stickies, we love the idea but unfortunately we're unable to do so within the forums so our only solution/workaround for that is to mark them as 'solved' if we want everyone to be able to see it if/when we merge older and newer threads into them.

Thank you for your understanding, please feel free to reply with any concerns you might have!

Sometimes it's okay to be a little Bing Chilling

E

Ezez333Author

Inspiring

Well that is a strange way to operate I must say - not going to speculate why - but no one is going to read a small print inside a thread ("NOT A SOLUTION").

If the issue is not solved or explained, there is no reason to mark anything "solved" - SMH.

Choleni

Honored Contributor

Just marking this as the solution for visibility

That's the reason.

People with the same problem find this thread easier and can post the information TheAntiSocializer asked for here.

That might help to solve the problem faster.

G

Graphic

Participant

That's what forum moderator tools like stickies are for. Marking an unresolved issue as resolved is obviously not the right way to gain visibility. Not only that, their posts follow the same cookie cutter procedure every time. Mark resolved & collect some random hardware info to fool people into thinking they are doing something about it, then later on come back and edit the post to inform people to contact support about it.

Go and look at their replies if you don't believe me. This whole forum is just a garbage can Meta send angry customers to so they can yell as loud as they want without potential future customers becoming the wise to their anti consumer tactics

TheAntiSocializer

Honored Contributor

Hey everyone! If you're still running into this issue, I would highly suggest reaching out to MetaStoreHelp through PMs. They'll be able to get a closer look into everything and provide some other things to potentially give a shot.

Sometimes it's okay to be a little Bing Chilling

nalex66

Honored Contributor

I had this issue pop up last week. It was preceded by an unusual power event on my PC. On Thursday evening, I was plugging in my Link cable to copy some recorded video from the headset, and I got a Windows warning about a power surge on the USB port, which said that the connected device was trying to pull more power than the port could supply, and that the USB port (on the PC) had been disabled. I tried a different cable in a different port, and transferred my files without issue.

The next day, when I went to use my headset (in stand-alone mode with a battery strap), I immediately got the pop-up warning in the headset about water or debris in the USB port. This is a Quest 3, latest non-PTC version (59… not sure of the full version number or whether I’ve had an update since). I powered down, examined the port as well as my Link cable and battery strap cable, didn’t see anything out of the ordinary, blew some air into the port for good measure. Powered back up, no message, no issue using either cable, and no recurrence since.

I assume the cause was some debris in the slot causing a short across the power connectors.

DK2, CV1, Go, Quest, Quest 2, Quest 3. Try my game: Cyclops Island Demo

C

Cornflakes0101

New Participant

I had the same issue but appear to have fixed it. My steps were:

1. I cleaned the ports using compressed air. This appeared to make no difference.

2. The cable for the Quest 3 was loosely rolled. I unrolled the cable and the issue went away. I am not convinced that this solved the problem but I no longer have the issue.

TheAntiSocializerAnswer

Honored Contributor

Hey everyone! Just jumping in here to report that I'll be locking this thread since we have another one right here that we've flagged internally.

If you're having this error pop up after updating to live version 62, please don't hesitate to post your experience in that thread and we'll be glad to have our team do some further reviewing!

Thanks!

Sometimes it's okay to be a little Bing Chilling

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO