cancel
Showing results for 
Search instead for 
Did you mean: 

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

Star.Knight
Protege

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.

1,055 REPLIES 1,055

What graphics card are you using? 

What motherboard do you have?

Nvidia 4090 RTX, motherboard is z690 asus. i have usb 3.2 gen 2v2, usb 3.2 gen 2, usb 3.2 gen 1, and usb 2.0. using 2.0 is not a solution, the bitrate is too low.
Why does it matter what hardware I have? This was working fine in v60.

Same setup as you except I’m on a x670 ASUS. 

Because I use it for work, not for playing games. I work as a 3D artist so the program I'm in is often maxing out a 24 core i9 and a 3090 on heavy operations. No stutter. No lag. No latency issues. No charging issues. And PCVR.
So yes, link has been 'awful' for me for over 2 years. Unreliable. Inconsistent. so bad in fact that the devs of the 3D program I'm using are in constant direct contact with the devs of the Oculus software about the issues involved. So no, you haven't established that link isn't awful. 

But yes, different people have different set ups and streaming isn't ideal for everyone, but I've had zero issues since I started streaming last October, compared to the 50/50 unreliability of link in my previous 2 years of using it. You've obviously had a very bad experience with streaming. I haven't. I had a very bad experience with link. You haven't. 
 

javiermares
Adventurer

Always eloquent and engaging Mysticle has given us voice, please spread far and wide in social media and tag other VR influencers. Tag Zuckerberg too (he uses threads, facebook, instagram ofc). Thank you! https://youtu.be/TYM4UCelD4I?t=266

 

Sanastro
Explorer

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.

 

 

 

 

 

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

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

The back two ports at the top left support usb 4. I use that one. I never connected my front usb c port. 

Skippy111taz
Protege

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!!!"
Still need help?

Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.

If you need an agent to help with your Meta device, please contact our store support team here.

Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.

Check out some popular posts here:

Getting Help from the Meta Quest Community

Tips and Tricks: Charging your Meta Quest Headset

Tips and Tricks: Help with Pairing your Meta Quest

Trouble With Facebook/Instagram Accounts?