Participant

Solved

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

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

docaranzat

Participant

Wow! It seems the nightmare is coming to an end. I just woke up and read your messages. Thanks for the heads up. I will have breakfast and then proceed with the update and testing.

I still feel like a lab rat. 😉

A

Anonymous

Yes, it really looks like it has been fixed with V64PTC.
I took a cable where the message kept coming up......now it's quiet.

docaranzat

Participant

No breakfast, but 45 minutes, one race, and all quiet. I’ll leave the headset connected and wait for an hour. The last two times I did that, there was a lovely message waiting for me.

S

Samcan2016

New Participant

Received a new update today, still on version 63. I haven't encountered the error that used to occasionally pop up, so I can't provide any insights on that. However, one notable change I observed is that the battery percentage now increases while playing if the device is connected to a power bank. Previously, it would remain at the same level. Interestingly, I'm using the same power bank as before, so it seems something has indeed changed.

#Update 2: Correction - My previous observation was inaccurate. Further testing reveals that the battery level initially increased ( it increased from 30 percent to 42 percent while using ) , but it now appears to be behaving as it did before. Need more testing

docaranzat

Participant

I order to get v64 you must enable PTC.

That must be done in the mobile app.

Flexigem

Participant

Is 64 being pushed on PTC or already on the regular channel?

I

IlMark89

Participant

Only ptc for now. But works

E

er0s3nnin

Participant

Where did you get v64 from? I only have v63 ptc available for my device (on both the app and on the device). I'm on the public test channel because I upgraded to v63 early because of the issues. How are you getting it?

B

Bayspoon

New Participant

I just wanted to mention my experience since I've been dealing with this for over a month now also. PCVR is not usable and that's the main way that I use my HMD. This has been happening since they forced the v62 to everyone.

I have a replacement cable on the way just to troubleshoot and make sure that's not the issue but it absolutely seems like it's software related. Something to do the USB drivers, voltage, and settings of the Quest itself (or the Quest app on PC).

My charging link cable for PCVR, that I've been using with Q3 the entire time since launch (Oct 2023) without any issues at all, stopped working properly whenever the v62 went out. PCVR is entirely unusable.

The Link app will run for about 30seconds-to-10minutes before just freezing entirely into a glitched black screen with jagged edges and becoming unresponsive. I have to press the Meta button and quit the "Quest Link" app manually at that point.

The quest won't recognize that it's still plugged in. The PC Meta app says "general device problem" and is flagged as an error under the "Devices" section on the app. Usually after that everything is glitched and it never really gets back to normal unless I restart everything and unplug and replug it all. Which there's no point in doing because the Link will just crash 20 seconds after getting it working again anyhow.

B

Bayspoon

New Participant

I forgot to mention that I've updated my HMD(quest 3) and PCVR app (Meta) to v64 and the problem persists for me. Zero fix for my issue. I was not getting the "Something detected in the USB port" issue very often before so that wasn't my main problem.

My issue was the actual Link not being stable anymore and crashing constantly. It still does this in v64.

docaranzat

Participant

After two hours and 15 minutes, the beloved message appeared again, it was during the Qualy session so I decided to race anyway. During the race, the message didn’t appear, however, I will have to continue testing throughout the day.

H

harrryckh

New Participant

test

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