Participant

Solved

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

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

K

kipliq

New Participant

I just started getting this issue. Very annoying.

Randossanchez95

Participant

Hey all. I've been following this thread for the last couple of weeks as I instantly received this same error once my quest 3 updated to V62. I was using the YRXVW 16 ft link cable with a 65W USB C fast charger. Got both from Amazon and until V62 it mostly worked great. Kept the headset fully charged while I was using it. I mostly use my headset to play iRacing and my iRating to took a serious hit due to having to quit numerous races each time I received the error. It was extremely frustrating. After about a week of on and off troubleshooting I decided to just plug in the official Meta link cable to the USB C port on my pc and I haven't received the error once since then. I did a lot of racing this past weekend to try and get my iRating back up and the headset worked flawlessly. The only downside is it obviously slowly discharges while using it now. However, I have noticed that since the V62 update, it doesn't discharge as fast as it used to and when it is off it charges a helluva lot faster than it did before. It seems to average about a 6-8% discharge per hour, which obviously isn't going to allow anyone to race in any of the 12+ hour endurance races that iRacing has but I've been able to race for up to 6 hours straight without any issue whatsoever. The error really seems to be related to using an external charger of some sort as even using the headset wirelessly with Virtual Desktop and having it plugged into the power brick still gave me the error.

Just figured I'd throw this out there and hope that it helps someone that may not have thought to try the official link cable. If you happen to have one kicking around like I did. It works perfectly for me. YMMV. Good luck and I definitely feel everyone's frustration with this.

C

Coluan

Up and Coming

I don't have the official link cable. Pffft not going to pay that ripoff price.

I do have a 2m USB-C cable that I use which is plugged into a power bank.

I did discover something last night though. My cable is USB 2.0. Not 3.0. According to the Oculus desktop app. I don't think that matters as I only use it to supply power from the power bank. The only other thing I use it for is to transfer files on and off the headset. Which I don't do often as I only play PCVR games.

C

Coluan

Up and Coming

Specifications of the power banks (I have 2)

General

Material ABS
Brand J.Burrows
Manufacturer's Warranty 8 year
Barcode 9341694600833
Descriptive Colour Black
Product Dimensions (mm) 174W x 82D x 27H mm
Product Weight (kg) 0.48 kg
Supported Charging Configurations 20V DC
USB Cable Included Yes

Manufacturer

Country of Manufacture China
Part Number PT820ABK

Ports

Number of USB Charge Ports 3
Charge Ports USB-A, USB-C

Power

Battery Charge Amp Hours (mAh) 25000
Battery Technology Lithium-ion
Max Electric Current (amps) 5A
Power & Charging Interface USB-C
Recharge Time 4 hours
Voltage Provided 20 V

D

DreadHeadFred

Inspiring

Okay, I decided to finally reply to this but I've been dealing with this popup since upgrading to v62. It was very frequent and started immediately after upgrading (never seen it before). I joined the PTC and received v63. It's less frequent but it's still very frequent.

I keep reading about ya'll talking about cables and length and battery packs and straightening the cable and whatnot, but here's my deal.

I'm using the same two cables that I've been using. One is in the power bank and it's the cable that came with the headset. The other is a 5ft USB-A to USB-C cable that is plugged into my PC. I get this popup on both cables.

But here's the dang thing that I haven't seen anyone say yet. I get the popup with no cable plugged in almost everytime I boot the heaset from 'off'. Anyone else?

C

Coluan

Up and Coming

No if I don't have any cable plugged in it doesn't pop up the error.

TheLegend271265668

Honored Contributor

Hey everyone! It looks like things have gotten a little hectic since my last reply. I know we're all anticipating getting back to our regularly scheduled, uninterrupted, wired PCVR experience. Fellow racers, I'm looking at you, and I know a lot of your seasons are starting soon. I'm trying my best to push this one as far as it'll go for a fix before that happens.

Speaking of updates, I've gotten one from the team within the hour to bring to everyone. It looks like this one was pushed into a higher priority to be worked on by engineering. Better news, the team has successfully replicated the issue, and has begun working towards the fix! They let me know they're poking to find an ETA on a fix, but as of this moment, I'm not to certain when that might be. I appreciate everyone for sticking this one out, providing useful data, and being patient with me and the team. I know wired PCVR is important to everyone, and it's important to me too. That's why I'm working in the background to make sure I'm doing what I can for this one.

Hopefully I'll have more to speak on soon! Subscribe to the thread if you haven't already, so you can stay tuned for any updates I push out in the future. Thanks again everyone.

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

C

Coluan

Up and Coming

The debris error hasn't happened for about an hour now. But I haven't done much. Just installing SideQuest and some apps. I have it plugged in to my PC for the most part. I don't know if that has anything to do with it. I'll try with battery pack tomorrow. I have done a factory reset. I disabled updates in settings (its still on v62 so it didn't reset it). But I want to completely disable them. I saw a post on reddit that you can do it with an adb command. But its not working or I mistyped it. Not sure if there are supposed to be spaces as its split over two lines.

C

Coluan

Up and Coming

The command is

I'm not familiar with adb commands so I don't know what I've typed wrong. Can anyone please advise?

V

vicksonzero

Participant

That's what i d like to hear, however late it is. Bug reproduction is the mother of all bug fixes (or something like that).

Do note that i am still mad about v62 not showing any sign of halting. You guys are poised to push a clearly defective software to the mass users. This is unbelievable to any responsible engineers.

But yea... at least i can start dreaming about not losing charge while playing / working... Good start.

docaranzat

Participant

Hello everyone,

Quick update: I’ve been using the Beta version of the Meta Link app and noticed no pop-up interruptions during my sessions. I played for around three hours without any issues.

I did a little test by turning off the Beta in the Meta Link app, which reverted it to a previous version, and immediately, the pop-ups came back. Switching back to the Beta version stopped them again, allowing me to enjoy three hours of gameplay in Assetto Corsa with the F1 2023 Mod without any disturbances.

Here’s what I got:

In Meta Quest 3:

Version: 62.00.273.343.570372087

Runtime version: 62.00269.341.570372063

OSversion: SQ3A.220605.009.A1

Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361)

Let’s see what happens tomorrow

J

javiermares

Up and Coming

I’m on the beta too, and I still get it. Unless you downloaded an update today, when did you get your latest update on the beta?

docaranzat

Participant

Unfortunately, there is no mention of the release date for the beta version that I installed. I hadn't played since Wednesday, and yesterday, when I started the Meta Link app, it installed the update. I have not been able to find the release date of the version.

R

RUBBERDOG

New Participant

I’m struggling to understand why this is so hard to fix…or at the least, generate an interim hotfix

S

SamStrider

Participant

Has anyone tried to drop resolution and frame rates to see if the reduced power drain works as a workaround or is that not technically possible?

M

Massacher

Inspiring

No I haven't tried that. But the image would be blurry and look like **bleep**. Why would anyone want to do that?

The power you'd save doing that is negligible.

P

playnjoy

Participant

I am in the same boat for over a week, my motherboard has 45w capable usb c port which i connect to using meta fibre optic cable and i get this message everytime i connect my headset, and only way is to click ok on that message and restart my headset and it connects well with no problems with link and fine all session but when i get off and unplug and replug its same issue again, very frustrating, i beleive its a sensor issue most likely.

Show more replies

Update (3/27/2024):

Update (4/5/2024):

General

Manufacturer

Ports

Power

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO