Participant

Solved

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

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

L

Lemonhead401

Participant

TheLegend27 why have yall not stopped the v62 update yet? I don’t know how much more confirmation yall need to understand you’re screwing your customer base that plays pcvr.

we get stuff breaks and doesn’t implement correctly, but yall don’t have a single failsafe in the event it has issues?

Why can’t we rollback? Why haven’t yall stopped the update? Why haven’t the engineers been able to find the issue in a month?

I know you’re just a mod, but you work for them and should be able to do something. This is absolutely ridiculous.

someone needs to do their freaking job properly.

A

anxiousprogram

New Participant

Here to B!+(h and moan. I have the same error. It is annoying that there is no fix or response from meta on this situation. I can't even get the Meta store support on my quest to work so I can warranty claim this brick that I have. It is pathetic. As a developer I should be allowed to roll back, I cannot continue development on my game due to this issue persisting. I hope this gets fixed soon or this will come at a great financial cost to me and I will have to take some sort of action in order to get this resolved.

A

anxiousprogram

New Participant

I love how this is a featured topic and no one has addressed it 🤣

H

Hchest

Inspiring

Only Youtubers can push this issue!

J

javiermares

Up and Coming

indeed, pls spread the word! mysticle, epic as he is, listened and covered the issue in his penultimate video

V

VaulthuntersSanctuary

New Participant

Hello All,

Recently I updated my Quest 3 to the latest firmware. Following the update I now receive a pop up every 1 to 2 minutes from my quest headset when hooked up to PCVR stating that there is debris or water in my USB-C port causing it to be disabled. I can still play PCVR it just doesn't charge. however, the pop up continues to happen every 1 to 2 minutes causing issues with lag, nausea, and just general annoyance. I have attached the photo of the pop up on this. My headset has 0 debris within the port and has never come into contact with water. Likewise, I have checked the port for my PC and used several variations of cords to see if that was the issue. No avail so far. Has anyone figured out a solution to this problem or dealing with the same thing. I live stream VR gameplay and generally extol the capabilities of the quest but I cannot do that with a pop up every minute stopping gameplay. Thank you for any assistance. Note: I just installed update V64 with the hopes that they fixed the bug, but it is still happening. Thanks again.

V

VaulthuntersSanctuary

New Participant

Another note. I used my Meta Quest 2 tonight and had no issues with the pop up with either the cord or the PC. So this is an issue with the Quest 3 specifically. Just wanted to provide all information. Thank you.

M

Massacher

Inspiring

Ok I'm home now. I plugged in my cable and within seconds of my home screen loading yep you guessed it the beeping and the warning about debris. But no message this time as the screen went black. I have the velcro straps attached to keep the cable more secured.
I once again had to press the power button for about 1.5-2seconds to get back in. For some reason the right controller gets disabled and I have to use the left one to select Power Off. Just before when I did this (literally 2 minutes ago) it updated and had the message please keep your charger connected (yea right and cause it to beep again) and wi-fi connected until the update is complete.

When I turned it back on without the cable plugged in no problem for the few minutes I went into settings to check the version and if anything else had changed. Nothing was changed. So I turned it off and back on again 2 more times and each time I turned it off it told me to keep the cable connected and wifi connected. How can there be several updates that don't do anything?

Here is the info requested:

Can you confirm which headset version your Quest 3 is currently running? You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 60.#.#.###.###.######### or 62.#.#.###.###.#########.
Its on v62.0.0.269.341.570372063 OS Version SQ3A.220605.009.A1
Are you enrolled in the V62 PTC?
No.
Which cable are you using when the warning pops up? Where is it plugged in?
- Official charging cable, Official Link cable, Third-party charging/link cable
- Plugged into a Desktop, Laptop, Wall outlet, USB Hub, Power bank, Elite Strap with Battery, etc.
  I'm using this cable (its a third party cable):
  https://www.ugreen.com/products/right-angle-usb-c-quick-charging-cable?variant=39915662082110
  Plugged into this power bank:
  https://www.officeworks.com.au/shop/officeworks/p/j-burrows-laptop-powerbank-130w-black-jbpbbk130w
Any workarounds that have caused this warning to not pop up when plugging in a cable?
None that I've tried. Other than not having the cable plugged in.
Can anyone post a screenshot of the error message when it pops up?
No not possible for me. The screen goes black and no interface so I can't.

edit:
There was a small update (maybe it was the date updating, its correct now):

J

javiermares

Up and Coming

I did a second attempt at booting up while already plugged in, to see if it would work. It didn’t. I got the error half an hour after starting the PCVR session and it put my f1 car into the wall of turn 1 at Nurburgring. Bye safety rating or bye other people’s races, or bye bye to my season

A

anxiousprogram

New Participant

So I made a threat and magically I get an update not a few hours later and now it is working........😑

M

Massacher

Inspiring

anxious_program wrote:
So I made a threat and magically I get an update not a few hours later and now it is working........😑

What do you mean a threat? Who did you threaten?

magic1968

Up and Coming

not got any update here yet quest 3 been on all morning no update as of yet am still on v63 and it still bad

Skippy111taz

Participant

So I got another reply from the AI Support.

"Thank you for getting back.

My name is Jada from Meta Store Support and I'll be assisting you today on behalf of my colleague.

Upon reviewing your previous interactions, it is my understanding that you're having some trouble with your headset, not to worry, I'll be delighted to assist you wit this matter.

Firstly, thank you for attempting all troubleshooting steps provided. I'm going to recommend we proceed with a Factory Reset of the device. What this will do is reset the device to a "like-new" state, wiping all information and data off the device, however before performing a factory reset, please ensure your Cloud Back Up is enabled. I have provided the steps below:

Put on your headset, then hover over the clock on the left side of the universal menu. When Quick Settings appears, select it to open the Quick Settings panel.
Select Settings.
Select System, then select Backup.
Select the toggle next to Cloud Backup to turn Cloud Backup on or off.

You may refer to the following links regarding this: Inset Link

Once you've setup Cloud Backups, ensure your device is fully charged, then proceed with factory resetting your headset.

To perform a factory reset using your phone:

Open the Meta Quest app on your phone.
Tap Menu then tap Devices.
Tap the headset connected to your phone.
Tap Headset settings, then tap Advanced settings.
Tap Factory reset, then Reset.

To perform a factory reset using your headset:

Turn off your headset.
Hold the power and volume (-) button on your headset down simultaneously until the boot screen loads on your headset.
Use the volume buttons on your headset to highlight Factory Reset and press the power button.
Use the volume buttons on your headset to highlight Yes and press the power button.

However if the issue still persists, the next step would be to start looking into replacement possibilities. Could you please provide me with the following information:

Full name:
Street Address:
City:
State or province:
Postal (Zip) Code:
Country:
Phone number:
Preferred email address to receive labels:
Username and/or email address associated with your Meta/Oculus account:
Serial Number of the device which needs to be replaced (headset):
Box serial number, which is located on the box. If unavailable, headset serial number:

I am eager to have this resolved for you, in order for you to continue to enjoy your VR experience! However, once you have provided the following information, I will be able to assist you further.

Looking forward to your response.

Best regards,

Jada
Meta Store Support"

I did the factory reset and it just reinstalled V62. The error popped up half way through the install. If they would just tell me that they know about the issue and are working on it, I'd be fine with that. But since they want to play these games and not listen to the consumer, I guess I'll be getting them to replace my headset.

M

Massacher

Inspiring

I got a similar message in my email.

Why do they keep sending automated bot responses.

I like how they said if none of that works the next step is to replace it. That won't fix the issue. When you get a replacement it'll update to v62 and you'll be back to square one.

I've never dealt with such an incompetent company before.

J

javiermares

Up and Coming

If you want to get really angry, read their full reply when I asked about a refund (as I said before, we have 3 year warranty in Spain and 2 year warranty in the EU so this is not legal) but also watch how he gaslights about the cause of the problem. It’s about where I downloaded iRacing from!! 😄😄😄or .. all my other games too. TheLegend27 Ryanality if this gaslighting is company policy I’ll make sure not to purchase another Meta product again, this is disrespectful. Take a look at this:

“

Hi Javier,

Thanks for your answer.

Regarding the refund, we could verify if this is possible as long as the glasses were purchased from us and the purchase was made less than 30 days ago. You can access this link for more information.

These crashes may also be occurring depending on where you have downloaded the games. If you purchased them from third-party stores such as Steam VR, some compatibility and/or performance issues may occur, so we could not ensure that these will work correctly. This is because our Meta Quests are designed to work with our PC app and the games in our store.

I suggest that you reinstall the games, restart the glasses, factory reset them, since doing these steps will reset the game data and settings and return to their initial point. This can solve many technical errors in both the glasses and the software of the Quest and the games, such as errors with fake water, debris, the white screen that appears in the game, etc.

In other similar cases with other people, by accessing the Meta Quest public channel, some have had this type of error solved with the new updates that Meta is releasing. I could suggest that you try it but it may not work because there is a limit on registrations or places to access this public channel.

You can try the following too
If any changes caused this to start, undo these changes (refresh rate, manual tracking, experimental setup, etc.)

Sign out and sign back in to the phone app.

If the previous steps did not work for you, please let me know so I can transfer your case to our specialized team and I can investigate the best solution for these problems you have with the Quest v62.

All the best,

Sergio R.”

Z

Zakowski

New Participant

Hey guys I find the solutions to survive this hard time waiting for bugfix if you really want use link connection Is only one option you need a power bank with fast charge output 18watts and connect power bank to the link wire ,simple solutions ,tested for around 12 houres without any issues , 20000mha power bank give you a lot of time without charging ,sorry for my English

M

Magiccarpets

Participant

This doesn't help PCVR users.

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