Participant

Solved

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

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

Myrothas

Participant

Yeah same issue here. Been fine on v60, broke at v62.
Was scared it might be hardware issue, thankfully not.
Still annoying.

magic1968

Up and Coming

still geting it now after i used boot on screen power and vollume so no good

A

Anonymous

Same here, also BoboVR not longer working without this issue after Update to V62. ☹️

M

MPires

Inspiring

I did a 3 hour session with an unpower cable (Kiwi) without any problems. Tomorrow I will try the power cable (Tiergrade) again to see what happens. As the Vs62 works normally with an unpower cable I think the error has something to do with external power management.

F

Futureboundgold

Participant

Picked up a brand new meta quest yesterday just updated today, and now cant I connect with my oculus link cable to my pc, which worked yesterday.

S

StarKnight929603Author

Participant

The issue is still present on v63 (I'm on PTC), boot from service menu already tried, and this confirm that Meta is simply ignoring it... or... maybe it is something that Meta wanted (cable certification or something like that) ? 🤔

J

javiermares

Up and Coming

meta, wtf? Do I need to return it?
regarding the cable hypothesis, if they want us to use the official cable maybe they wanna make one that can keep the headset charged during use????

TheLegend271265668

Honored Contributor

Hey everyone! I really appreciate everyone's patience and continued experience reports. I know dealing with the warning bug has been pretty irksome for everyone, and I'm eager to have good news to share with you all as soon as something tangible comes into my hands. I don't mean to withhold any communication or keep anyone in the dark. I'm still keeping a heavy eye on this thread—ready to update everyone as soon as I hear any updates from the team. I encourage you all to keep voicing your experiences and feedback to continue helping the engineering team's efforts.

I hope to have something to bring back to you all soon, and I'll be sure to check in regularly—even if I don't have anything at the moment, just so you don't feel like I've forgotten about you all. Thanks again for your patience everyone!

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

magic1968

Up and Coming

hope you find a update fix soon as every body is going mad

T

Topher420247

Inspiring

I had it happen again today I'm on v62 I unplugged quest restarted and still had no charge from the cable. Got up and unplugged the power from the powered link cable I am using and heard it make the disconnect sound. Plugged it back in and it's charging and instantly picked up by the pc app device page that I had open. So far I've been able to boot back up around it but it's still random and that sucks to be flying an hour long or more dcs campaign mission only for your headset to kill you not your lack of piloting ability

magic1968

Up and Coming

i went on my app on my phone put in the setting PTC and got the v63 update not had any issuse been playing with out any water debris warning for hours

M

MPires

Inspiring

Where you can put he setting PTC in the phone? thanks.

Skippy111taz

Participant

Glad to see I'm not the only one with the issue. It's clearly a software issue. It happened immediately after the update for me. I have tried different cables and charging blocks with no results. Hopefully they get this corrected.

C

Chronometria

New Participant

Updated to 62 and got this exact same issue today. Seems every update comes with some bizarre new problem. Last one made the finger sensors bad and now I get this random water sensor alarm.

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