Participant

Solved

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

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

F

frankdill2024

Participant

if you're NOT charging the headset(just cable headset to the PC) while on using in PCVR do you guys still get the message?

B

Bizzi123

New Participant

i used the kuject cable with power supply. If i'm charging and the battery level is under 80% i don’t get the error message, if i'm not charging and just doing data transfer i don't get the error whatever the percentage of charge the headset is

F

frankdill2024

Participant

I have the same cable( kuject cable ) I haven't tried charging it while under 80%. I originally bought the one that was 18 Watts (white one) that one gave me lot errors. but it actually charged headset while I was playing. I don't know if this would work for people try not charging the headset while on PCVR hopefully they push an update.

F

frankdill2024

Participant

yes sorry people less power wattage when charging over 18 watts is in no go for now.

F

frankdill2024

Participant

was is the headset over 80% battery when you got that annoying message

M

mdibarbo

New Participant

Found this thread because since Sunday when I got the latest firmware update on my Quest 3 I instantly got this warning message. I am quite shocked how long this is already out and Meta is not able to fix it.

T

triangle999

Participant

I've been getting this and frequent disconnects on a Q3 that i have had for three weeks plus no VRusb connection warnings. Makes the link connection super unreliable and i kicked mid-game frequently, The Q3 keeps making the 'now charging' sound and my PC won't go to sleep anymore as the Q3 seems to be re-establishing a connection to the PC (requires we to have the Q3 powered off). I also now have a port reset failed error in my device manager under the USB section but that doesn't seem to make any difference. From what I can tell, the USB port is a bit loose and the cable does not get a good enough fit (at least that's my theory and it may be a software issues relating to the USB port's tolerance for connectivity).

Anyway, I have now put one of those small, right angle usb c female to male adapters in the USB port on the Q3 and plugged the link cable into that - the fit is much, much tighter. Will see how that goes longer term but so far so good. Can get the adapters in pairs from Amazon for about $AUD13 (UGREEN and a few other brands). Hopefully, this is a firmware issue that can be addressed as I now constantly live in doubt when using the headset.

T

triangle999

Participant

Also, try disabling your onboard graphics (Intel or whatever). Your Q3 will only work in Link mode if the Oculus Device (which expands out to Oculus XRSP Interface) is present in your Device Manager. I've been testing this, too, and disabling my onboard graphics seems to be keeping things working through power offs, restarts, computer restarts and power offs, Worth a shot if you haven't tried already. This was a known fix about three or so years ago for some issues with the early Quest models.

R

Reonu

Participant

EDIT: I replied to the wrong post.

R

Reonu

Participant

For whatever it's worth, I decided to replace my Tiergrade Link cable (USB-A for the PC with USB-C power injection) with a straight USB C to USB C fiber optic Link cable from VRcover. This completely eliminated the issue when connected to my MSI Tomahawk x570 motherboard. With this setup, the battery does NOT go up, it goes down very slowly.

They still need to address this issue since they broke behaviour with cables that used to work perfectly, but hopefully this info helps somebody!

D

DreadHeadFred

Inspiring

Hey all, something weird happened today. I've been getting this stupid popup thing ever since v62.. like 2 minutes after the update. It's been more frequent for me than it seems most of you. Then I got v63 and it was less frequent but still very much present. I got the message with a charger, with connection to PC, with different cables, with the bobo battery, and even without any cable connected.

Well, today something strange happened while I was developing in unreal engine. I made a mistake in one of my blueprints and created a loop. When I pushed the apk to the headset and started the application, it froze. I couldn't get even the internal menu gesture to be recognized. So after a minute or two, I rebooted the headset. Ever since, I have not had one popup. I just played 2 hours with the bobo battery connected and not a single popup. I now have the headset charging and NO POPUP! Normally I would see the popup at least a few times by now.

I'm not sure if I got some kind of minor update in the meantime or I "broke-fixed" it. Only time will tell but has anyone else had their issue fixed today?

ETA: My headset is charging way faster now too.

T

triangle999

Participant

Strangely enough, i was prompted to re-pair my Air Link this morning and the headset has behaved a sit did when i first bought it - pop ups with tips etc along with new pop-ups for quick access to Link and other features that i have not seen before. I wonder if some update got stealth pushed out?

T

triangle999

Participant

Plus i'm now getting controller battery % showing in the Oculus app and that has never worked before for me, which I found really frustrating.

V

VanceHanson

Participant

Even though you're sure there isn't any debris or water messing with your device, it wouldn't hurt to give the USB-C port a good clean. A dry, soft brush or some compressed air can work wonders, clearing out any dust particles that you might not see but could still be causing trouble for the sensor. And about the cables, I know you mentioned using quality ones, but it's still possible that the issue might be with how certain cables are interacting with your device's sensor. Trying out a few different ones could shed some light on whether the problem is with the cable itself. Sometimes, what seems like a minor change can make a big difference.

V

vicksonzero

Participant

Wow i have been shelving my quest 3 and is it still not resolved after another week? Meta is surely very busy looking for people to buy their products.

Oh i forgot to mention bug fixing. That's proly out of their concerns.

D

Davilos

Participant

70+ pages of people dealing with this issue and still nothing beyond some vague, hollow promises of a fix? This is ridiculous. If this continues for much longer I'll be buying a Vive XR Elite and ditching Meta for good.

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