Participant

Solved

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

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

S

StarKnight929603Author

Participant

I upgraded to v64 PTC yesterday and tested it for a couple of hours while charging (and battery charge above 90%) without any USB warning, before 64 I usually got that message after 10-30 minutes of usage. So something has changed from v63 to v64. Maybe it's not the ultimate solution (I see some people get it from time to time even with v64) but it's one step forward.

M

MPires

Inspiring

Same here. Tonight I will test it with more time on iracing but I am hopeful that they have resolved the problem.

T

TheJ0rma

Inspiring

Just got the error on v64. For me the message only appears when the quest 3 has hit 100% charge in sleep when connected to a power injecting link cable.

E

er0s3nnin

Participant

I'm also getting on 100% when in sleep, Not using a power injecting cable though but an official meta quest 3 link cable (this one - https://www.meta.com/gb/quest/accessories/link-cable/)

It seems to my simple mind to have something to do with the power output capabilities of the device you are connecting too because it does not occur on my asus laptop, does occur if I use my docking station's port and does occur if I plug directly into macbook too. I suspect my asus laptop has a lower wattage of power it is able to supply the headset when compared to the hub which can do a full 100W. The mac claims 15W max but I have plugged devices into it before that require 25W and they worked so I believe it might have some extra headroom than it claims it terms of output.

I remember reading somewhere the CYPD3177 (the usb controller in the quest) has a protection mechanism that disables the FETs when the VBUS voltage is out of range and then enables the FETs when PD negotiation is complete. This could cause an large spike in inrush current if not handled correctly and maybe/potentially trigger the VBUS overvoltage protection or the VBUS to CC short protections which the firmware then interprets as moisture or debris? Just speculation as I am not professional hardware engineer so could be way off base (the firmware must be getting some kind of signal from the usb controller it's interpreting as a connection issue and there is no direct moisture sensor on the quest)

on version 64.0.0.419.370.583580230

M

MPires

Inspiring

With V64 the problem seems to be solved. I had an hour and a half session with a powered cable and had no problems. I started the session with 96% battery and ended it with 99%. Previously the error appeared after a few minutes.

D

DreadHeadFred

Inspiring

I'm on 36 hours now of pretty heavy use on v64 with no popups! Pretty much running as well as day 1 back in October.

V

vicksonzero

Participant

Don't get my hope so high, i am having a demo session showcasing my VR game to people, and if this issue is to be solved in time, then i can finally use the new usb-4-pd cable to charge my machine between sessions..

magic1968

Up and Coming

just had v64 on the ptc and it still dose not stop the usb water debris warning why cant the boffins fix it lots are now stopping using the quest 3 because of it

S

StarKnight929603Author

Participant

Considering how much time it took to replicate and partially solve the issue probably the cause is harder than we might think. It started with v62 and this could only mean one thing: before that firmware they were not using/considering some signals from the USB port sensors to protect the device from melting (just like what happened with many Quest 2 devices) and now they do (which is a good thing) but... in some circumstances it also detects false warnings. I have some friends that never had that issue even with long cables while charging their devices while others like me had it all the time from v62 to v63 (I hope now with v64 not to see it any more). Hopefully they are addressing it now and maybe in future releases it will be fixed for everybody.

V

vicksonzero

Participant

Good news.

I have used the Quest 3 on v64 for 6.5 hours non-stop, so far no problems have shown up.

My set-up:

USB-4-PD-C-to-C cable
- 2 meters long, non-official non-branded cable, metal core, not fibre-optics
- Cable plugged to the Quest-3 first and then plug to usb-4 port in laptop, if that is relevant.
My PC: Asus ROG Flow x13, nvidia RTX 4050 laptop
Still using Virtual Desktop to do most of the PCVR stuff, just because it works.
I created a Wi-Fi hotspot with my Sony phone. It has 5GHz speed, not 6GHz.
- Both my laptop and the Quest-3 connect to this phone and then i use Virtual Desktop (local network) to do VR.
I have used Unity to write VR app, and to test it via Virtual Desktop. Occasionally i build and sideload the app to my Quest-3, so i guess the bandwidth requirement is not high.
Version: 64.0.0.419.370.583580230
Runtime version: 64.0.0.414.368.583580275
OS Version SQ3A.220605.009.A1

My quest is able to keep charged at 100% while i do my dev work.

Still upset about how slow this bug is being fixed. Credits due, I will give you my gratitude in case i forgot. I will continue using it throughout the Easter holiday so i ll keep you posted if anything changes.

Finger crossed i won't see any problems until the demo days. I am going to play-test my app with lots of people.

A

Adenasyn

New Participant

Try unplugging the cable from the computer with the cable still plugged into the headset and see if it pops up. I had it working till my usb went into power saving. My theory is if the headset is plugged in and loses connection for any reason to the computer this error happens even on v64.

K

Kiwidll

Participant

Guessing there wont be any updates on this from meta, my quest is unfortunately still a dust collector even on v64. I posted multiple comments on youtube videos from the so called "best VR youtubers" and each and every comment got removed. Not gonna say exactly who it is, but just typing "quest news" in youtube you will find all 5 of them that removed my comment, in the same comment i mentioned how the issue still exists and that there is no compensation or fix in sight (in terms of meta announcing something), and how I am displeased that they dont talk about it in their "news" videos.......

H

Halaster

Participant

I expect there will be further updates, once they actually get usable information from people who are saying they still have the problem. I see people say they have v64 with the problems still, but yet to really see a person actually give the full information that Meta Mod has directly requested in the reply post to this thread. Lots of complaints, but not the actual information they asked for.

The stickied thread directly asks the following:

TheLegend27 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.#.#.###.###.#########.

So, instead of posting comments on youtube videos, and others posting in here saying they have v64 and still have the issue. Actually do what the post asks. If you have not already that is. 🙂

K

Kiwidll

Participant

If they asked that 4 weeks ago I would help but going 8 weeks now and just now they are trying to say something, so f not, I will not be doing anything of sorts, because if I do where is my compensation for paying for the product that I can't use, the same product they don't want to take back because bots are answering support messages, why should I do a job of a QA when I am not getting paid for it. Usually I would agree with helping but having people just have the problem for 8 weeks with only 2 messages that both said we are trying our best is not something I can get behind.

Honestly if you trully want to help them then making the issue public is the only way of doing it, they have everything they need to recreate it, and they pushed this device out so it has to work otherwise do a recall.

D

Davilos

Participant

Are you really this dense or do you just play one on TV?

Of course they need QA work done if they’re having problems replicating it. Every single person on this thread seems to have different causes, effects, and times at which it occurs. They need all the data points they can get. You being ignorant and belligerent causes them to have to take longer helping everyone else.

T

TheJ0rma

Inspiring

The error still shows up sometimes when the quest3 has been charging in sleep with link cable connected.

version 64.0.0.419.370.583580230

H

Hchest

Inspiring

Just had a blast iracing, V64 here, no popup in 2 hour session.

Used a normal - non extra powering - USB cable from KIWI

I can only pray that it keeps this way. This is the device i bought, gone disable WIFI, iff the USB connection does not check for updates i should be safe.

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