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

G

GustavoDell

Participant

So guys, i cant stand this **bleep** anymorem we have tons of people screwed by meta here and they do nothing about it. I cant use cable, virtual desktop has bugs, then you try to use air link and it doesnt recognize until you restart everything. We spend money on this and cant even try to enjoy it. We should go show some "love" in all meta pages so they start to feel in their pockets how nice it is when people are screwing you. I already started, join me leaving some comments on meta pages until they fix this **bleep** thing.

docaranzat

Participant

Well. I’m just another user that can’t use this magnificent VR headset. 😉😡😡😡😡

M

Massacher

Inspiring

It did this once shortly after I got it (first week of January). It had a message on the screen that there's debris in the charging port. I took it off. Unplugged the cable and blew on it to get out any dust that may have been in there. I don't know if there was but its been working since then with no issue. I haven't used it for about a week. Then today I decided to have a quick play. I didn't even get to load up SteamVR and it had that same beeping noise. When the beeping stops the screen goes black. If I hold the power button for about 1.5-2 seconds I can see the screen flash for a moment and then I get the reboot screen. I cancel and I can get back in. But I cannot do anything as it keeps doing it within a minute.

I have tried a different cable.

I am using this powerbank and have been using this cable when playing with the powerbank plugged in. I tried the cable that came with this charger tonight. Same issue.

Is my charging port damaged? Or are my USB-C cables damaged?

Here's a photo of it:

I can see what maybe looks like dust on the top of the connection. But I'm not sure what it is. I can't see it with my naked eye. I blew on it to try and clear it but it didn't do anything.

edit:

I forgot to mention that I'm using the BOBOVR M3 Mini Head Strap. I don't think anything was damaged when I changed it over.

M

Matti1337

New Participant

This problem has destroyed so many sim-racing races during past weeks. Why this false error kick you out of PCVR and make you blind for a moment, why it could not be registered into some error log and your headset would be usable. Now this product is totally unusable and META hasn`t done any hotfix to solve the issue. You just get false error-pop up at random point and get kicked out from PCVR. Where is possibility to downgrade the firmware?

J

javiermares

Up and Coming

yeah the start of my year long iRacing f1 season is completely messed up because of this. The error message is idiotic - it completely and violently pulls you out of the simulation, and of course you will destroy your and someone else's race. Incredibly careless, it's insane to me. This company is worth 1.21 trillion dollars so the only conclusion is that they don't really care enough to fix it, or to fix it quickly. (quickly being, not weeks) TheLegend27 just tell us how to roll back to v60 please

M

Massacher

Inspiring

And they just tell you to factory reset it. Like how is that going to fix the issue? There's clearly a bug in the power management somewhere.

M

MPires

Inspiring

I also check every night and yesterday I had the same error again with the aggravating factor that Q3 was at around 70% charge. Previously the error only appeared when Q3 was above 80% load. I really hope that Meta resolves this quickly because for the simracers community this is fundamental.

J

javiermares

Up and Coming

Basti564 help 😄 do you have any ideas on what we can do? AFAIK we can't downgrade to v60 from v62 and v63. Thanks in advance

M

Massacher

Inspiring

I'm on v62. It happened once when I was on v60. So I don't think it matters which firmware you're on.

J

javiermares

Up and Coming

If you look at this thread and the post on read, you will see that the vast majority of the reports say that it started happening with v62. This is the first case that I hear that also had the issue on V60, so perhaps it’s a different problem causing it for you

J

javiermares

Up and Coming

TheLegend27 Amazon says I need to ask you, Meta, for a refund or replacement. The Meta page I was redirected to was as useless as any other support I've received here. We have strict consumer protection laws in EU. I bought this in December. We have 2 year warranty in EU, 3 year warranty in Spain by law. Please advise

S

Sunski

Participant

I've done some further testing and can confirm that i get the water/debris warning when I plug or unplug ANY kind of powered cable while the headset is on (and then need to restart to get rid of it), no matter the headset charge (had it at 30%, 60, 85 and near 100).

This applies to both the original Meta charger and cable as well as third party cables and power solutions (powerbank, Kiwi headstrap with battery).

Interestingly enough, I don't get the warning and usb port disconnect when the power source is already plugged in while the headset is powered down. So, if I power up the headset with the Kiwi strap or charger already plugged in, it works okay.

Hope this helps with troubleshooting, I've already submitted my error log.

M

Massacher

Inspiring

Where do I find the error log and how do I submit it?

K

Kirso

New Participant

why is there not an option to turn this off.

Myrothas

Participant

I think i have found a workaround - at least it works for me 100% of the time.
Plug the cable in, accept the message.
Click the off button on your headset.
Wait 5 to 15 Minutes. ( i didnt figure out how low u can go )
Click the on button on your headset.

After this, it stays charged / is charging and not causing any more annoying popup messages.

Myrothas

Participant

Wondering why noone noticed my workaround.
It works. Noone cares. All are busy crying.

M

Massacher

Inspiring

Can't quote on mobile so Imma use quotation marks.

"I think i have found a workaround - at least it works for me 100% of the time.
Plug the cable in, accept the message.
Click the off button on your headset.
Wait 5 to 15 Minutes. ( i didnt figure out how low u can go )
Click the on button on your headset.

After this, it stays charged / is charging and not causing any more annoying popup messages."

When you say click do you just mean press it or press and hold?

So we have to wait five minutes before we can use it? That is not acceptable. And we shouldn't have to do some ridiculous step to get it to work.

There's a bug in their software. They MUST fix it. Otherwise why would I keep it?

I'm m sick of this bull**bleep** in this day and age you buy a product for hundreds of dollars and it fails after two months. What a joke.

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