Participant

Solved

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

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

Sanastro

Participant

Now after some intensive testing I can confidently say that I was able to solve my issue by using another cable.

I'm certain, that my other cable is not broken.

The "old" cable worked before the v62 update and I even had another one of these (same brand same model) that was completely new and when I unpacked it and tried it, it also had the same error.

The problematic cable was an

USB-C to USB-C 5m cable, USB 3.2 Gen1, 5 Gbps, 3A

Now I bought an

USB-C to USB-C fiber optics link cable 5m, USB 3.2 Gen2, 10Gbps, 3A from CableCreation (the upgraded version)

I'm using a x670e hero motherboard which supports up to 60W on the USB-C slot (it has an additional PCI-E connector for supplying enough power to the USB slots)

Again, my other cables are certainly not broken and I'm sure that the main cause for the error is the v62 update.

However, with the new cable I don't get the warning anymore. I can 100% confirm it, because everytime I use the old cable it takes about 1 min until it shows up when I plug it in. I can swap cables and reproduce it, but with the new cable the message doesn't show up anymore. (I tested it for three days, long play sessions, different charging levels and it always worked. I waited before posting here, because I wanted to be really sure.)

So long story short, apparently there are cables out there, that let you play and charge at the same time without the debris warning, but it's still unacceptable that some cables are working with v60 and suddenly stop working when an update arrives.

M

Magiccarpets

Participant

I have the same motherboard as you. Which slot do you plug it into?

S

Sanastro

Participant

The front USB-C port supports up to 60w.

But you also have to connect the optional PCI-E connector to your motherboard for the extra power

Skippy111taz

Participant

Here is my latest response to support. It's safe to say I give up with "Them"

"You might as well just cancel this support case.

I have to say Meta support has been a complete joke handling this. I have clearly stated what the issue is and that multiple people are experiencing this issue. I have also tried to direct you people to the Meta forum about the issue. Every response I get back is from another "person" that seems to think my issue is with a link cable. My issue is with charging the headset while using it. And it happened after doing the stupid v62 update. Like many other users are reporting daily.

Other users are saying support is like dealing with AI and scripted solutions. But really an AI would at least take the time to read the forum that I have directed you guys to multiple times. So I give up with support and hope Meta gets enough complaints and returns to make their stocks drop to the point that they decide to fix this ridiculous update.

YOUR $500 HEADSETS ARE BECOMING USELESS WITH THIS UPDATE!!!"

J

javiermares

Up and Coming

TheLegend27 please give us a link to v60 so we can download it from an official source instead of from some third party hacker's website

A

Arkangel1981

New Participant

For god's sake, give us the option to unravel that **bleep** MESSAGE, since we pay an arm and a leg for a device we can't use

V

vicksonzero

Participant

Lolz facebook has blocked firmware downgrade since 1~2 years ago. I have just tried the method that the Mysticle has shared, but my downgrade is always cut off at 47% progress.

I am pretty sure that the upgrade process has a version check and will give up if it is an old firmware.

Another path blocked for PCVR for me.

J

javiermares

Up and Coming

Thank you for reporting on this and saving many of us hours of time. TheLegend27 how long will our Quest 3’s be paperweights? Do you want to call us on the phone so we can help you replicate? It’s very easy, look at the descriptions in the hundreds of cases here. My season starts next week. Preparation has already been affected.

A

andhog

New Participant

I'm more than willing to share data/logs if that can help solving this issue, just tell me what you need and where I can find it. I just jumped on the iRacing train and this problem is about to ruin it completely. Yes, I could go back to using my monitor but there was a reason I bought a new computer and a Quest 3. Getting a bit desperate.

V

vicksonzero

Participant

I have given up waiting and found a way that sort of works for me. I used an old usb-2 cable to charge from a powerbank, and connected to my laptop through my phone's wifi hotspot. My Sony Xperia 5v says it can support 5Ghz wifi, so i can sort of play single player games like HL:Alyx. I tuned down the resolution so it is playable apart from frequent lag spikes.

I still aint happy that my usb-4 cables aren't accepted by the version 63. Devs can you ask us more questions? I booted into my android recovery mode and saw some more version info (perhaps it's my hardware version? eureka something). is that helpful in helping you reproduce the error? Just say something.

F

FusedWrath

New Participant

Still getting the error with my Anker battery attached. First time I tried since updating to v62 and getting the error. My OS appears to be the same as others previously posting so there doesn't appear to be a recent hot fix:

System Version: 49829370055000510

Version: 62.0.0.260.343.566123828

Runtime Version: 62.0.0.257.341.566161015

OS Version: SQ3A.220605.009.A1

Here's hoping it's fixed soon...

M

MPires

Inspiring

Every night I check to see if any solution has been given to the problem. I confirm that the problem persists. If my Tiergrade cable is connected to power, the error always appears. If used only as a USB 3.0 cable, the problem does not appear but the Q3 also does not charge the battery.

S

SteveJaye84

Participant

Same here. I check this thread every night and morning hoping for any news from the developers. It's been weeks. Our devices worked fine on v60(besides other issues like wifi 6 speeds), Please take this issue seriously.

B

bigtabs

New Participant

Why isn't there an option to roll back the firmware if you're going to break our devices like this? It would solve everything for us while you work on a fix.

J

javiermares

Up and Coming

TheLegend27 I know "move fast and break things" was a Facebook motto. How about "don't break my users' hardware and move fast to fix it when I do"? Not so catchy?

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