Participant

Solved

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

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

H

Hchest

Inspiring

Testing conditions:

Quest 3 with v62 (2month old device)
Quest 3 never had any issues before V62
Succesfull tests are 1 hour AI races in iRacing using ocolus VR runtime.
When using cable with extra charging input, it is hooked up to original Quest3 charger
I used the same USB 3.1 port on back of PC for all cables and tests

Testing results:

1st test (normal non charging KIWI cable) started 100% battery, finished 65% => No problems
2nd test (cable with extra charging input!) started 55% battery, finished 72% => No problems
3d test (cable with extra charing input!) started 81% battery , finished 86% => In a span of 35 min; i got the Error 4 times! Stopped the test.

Testing conclusions (how i see it):

V62 introduces a bug, when the battery gets charged between 80 and 100% (with cable that has extra charging input otherwise it loses charge), my guess it gets to hot, hot error handled by debree or liqued chargingport error?

Charging batterys in the 80-100 range is known to introduce more stress and heat to batterys.

iRacers: Please try to have the headset almost empty when starting a race, then you can do 2 to 3 stints back to back (2.5 - 3h) or more, before the battery gets to around 80% and problems start to show...

Also let me know iff this helped, my testing was intense, but not conclusive ofc, im a one man show...

To make it clear, this is not a iRacing problem, this is a V62 problem!

G

gabrielbittio

New Participant

here the error appears with the quest3 charging in the socket, without the cable the error also occurred, but mine had less than 10% battery. I haven't been able to test it yet with questlink because I use wireless simulation on the virtual desktop. today without errors (battery between 80% and 100%, wireless)

V

vicksonzero

Participant

I just want to know if there are any persons on version 62 but don't have this problem…

the last guy came and say things, but did not report the version of their machine

S

StarKnight929603Author

Participant

Everybody here have at least v62 or greater.

I have latest v63 PTC release and my wife the latest v62 live release... both having that unacceptable issue since we upgraded to v62 and NEVER had it before so... the conclusion is obvious. Comments of other users here are useful to narrow the possible cause but if Meta doesn't care at all (it's been one month since the issue was reported) they are useless.

S

Sunski

Participant

Adding to the convo:

I've also had the issue with the headset battery at around 30% and NOTHING plugged in.

A friend (who experienced this a few weeks ago, i think she is on the beta program) had some success with never plugging AND unplugging anything from the USB C socket while the quest is powered up (i. e. doing any plugging and unplugging of cables while the headset is powered down).

Not sure whether this will actually help (and it would obviously just be a stopgap solution, no actual fix), but may be worth a try?

And while I really appreciate everyone's testing, suggestions etc. the solution can't really be to use a very specific cable, stretched just so, with the headset is at 78% (and waiting for a full moon) considering things worked just fine with a variety of cables, chargers, power sources and use scenarios prior to the update.

B

BadBoysMFX

New Participant

I have the same problem (v62), but only with my elite strap with battery. i cleaned the cable multiple times. There is no dirt or water in the connector. I noticed that this connector has less pins than my other charging/data cables. I'm not sure if it's related.

A

andhog

New Participant

Same issue started to occur recently for me as well. I use an INIU 5m cable from Amazon with USB-C port for charging and I'm randomly being kicked out from games due to this. Super annoying and makes it impossible to do any kind of online gaming with the headset right now!

shariacoleslaw

Participant

What would be really nice would be getting an update on this. Some sort of confirmation that you all are working on a fix for this even if you don't know when it will be ready.

H

Hchest

Inspiring

The 62 update was the "we care about PCVR" update... Sigh...

Skippy111taz

Participant

So heard back from support......sort of🙄.

"This is an automated response to your support ticket.

We’re checking in here to see if you still need our help on this support ticket.

If your issue or concern is resolved now, that’s great! Just respond to this email and let us know so we can close your ticket.

If your issue or concern isn’t resolved and you still need assistance, please respond to this email as soon as possible and let us know so we can help.

If we don’t hear back from you in the next 5 days, your ticket will automatically close. We look forward to hearing from you soon.

Thank you,
Meta Quest Support"

Seriously 😑. My response was basically no it's no resolved for me and hundreds of other users. And to read their own dam forum. With a link attached to this growing thread.

I'm trying guy's 🤷🏼.

TheLegend271265668

Honored Contributor

Hey everyone! Just coming back in for a quick update. It looks like engineering hasn't been able to replicate the issue so far. Just know this doesn't mean the team stopped working towards a solution. It's very apparent that this is a problem that a lot of you are coming across that is soiling a seamless experience.

artemisprime999 & Hchest, great work. I really appreciate the detailed reports and testing. I passed those along to the team in hopes that it'll help them work towards replicating the issue. If anyone else has been able to consistently replicate the issue, I encourage you to share your testing and results. The more information the team has, the better.

I really appreciate everyone's patience as the team works hard to find a way to replicate the issue. I wish I could do more on my end for everyone. I'm still doing what I can with passing reports and information to and from the team to keep everyone updated on both sides. Thanks again everyone, and I hope to have an update again soon.

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

S

StarKnight929603Author

Participant

The fact that "engineering hasn't been able to replicate the issue" is simply hilarious since from what they can see here everyone has v62 or v63 and is using a Quest 3 device connected to PC or power got it. I personally tested using every USB cable I have in my house and got that message... the same on my wife's Q3. I have not tried yet to make it discharge before plugging it and I'll try but it obviously is not a solution for those wo need to use it for several hours.

J

javiermares

Up and Coming

Anyone who uses a powered cable which can keep the Quest 3 charged during use has this issue. Hundreds of cases reported here and on reddit, weeks gone by and they can't replicate it?????

S

Sunski

Participant

Just to make sure this doesn't get forgotten:

I (and several people I know) have been getting this issue since v62 WITHOUT ever connecting the Quest 3 to a computer. It's popped up for me when connected to my Kiwi battery strap, connected to chargers (Meta original and otherwise, using the original Meta cable and other cables) and even without anything connected to the USB C port, directly after startup, so it's not just a PC connection issue.

I have submitted my error log, but haven' heard back from support.

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