Participant

Solved

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

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

Rolldabeatz

Up and Coming

Still no fix, tried all recommended ways of the community, plugging order and what not. Both cabled and wireless Quest Link are broken and my Quest 3 is now second month just sitting there, menacingly. I feel like this has to be CODE RED to the Meta staff to get their code together and fix it, or admit that you sold us broken devices that need to be recalled and changed.

D

DreadHeadFred

Inspiring

I'm still checking this thread every day but I'm happy (for myself) to report that I'm now 7 days in with v64 and I have not received a single popup for the charging port issue. Mainly used for PCVR for developing but also used for PCVR and standalone gaming. The headset charges way faster, charges when gaming PCVR, and actually charges when gaming using the bobo battery. It's how the headset should work.

I have had one issue though and it's only happened maybe 3 times. When developing with PCVR, I've mainly been using hand tracking and I take the headset off and put it on many times in a row to test development progress. A few times I have received a different popup saying something to the effect of "tracking has been lost. Use the controller to proceed". Except, neither hands or controller is recognized and I'm forced to restart the headset by holding the power button down. I don't think this has anything to do with the debris message, and it's probably because I'm putting the headset on and off repeatedly.

Anyhow, for those that still have issue, I feel for you. I was getting the popup every 5-10 minutes regardless of a cable plugged in or not.

This issue has, in my opinion, absolutely nothing to do with what type of cable you use, what order you plug which end in, or anything in your control. It is purely software based and Meta knows how to fix it. I'm guessing they tried to fix it in different ways with different versions and I just happened to get the proper fix on mine. Hope you all get yours fixed soon.

N

nixt

Participant

The only way i was able to fix my issue of losing controller tracking every time I took the headset off was a factory reset. After that, I've never had the issue.

C

conradaxx

Participant

Is that related to this issue?

M

MPires

Inspiring

Yesterday I received a new version and the error appeared once when I turned on the Quest 3 when it was fully charged. Afterwards the error did not appear again. The version I received was
64.0.0.464.370.584939916

C

conradaxx

Participant

How do you know when you get a new version?

M

MPires

Inspiring

I confirm that with this new version (64.0.0.464.370.584939916) the problem has returned, disconnections appear frequently. With the previous version (64.0.0.419.370.583580230) I went for 3 consecutive days without any problems. Meta, please resolve this issue.

S

Severem

Participant

I bet once someone Roots the Meta 3, any and all false alarms will be a thing of the past, because apparently, those capable of rooting the Meta are better programmers and can fix this **bleep** issue, that should have been fixed before the v64 patch came out! BTW Meta, if you are reading this... it is within my rights as a consumer, to notify you that any and all information that you collect from me and the device that I paid for its use, to NOT be sold or used to advertise to any other company as a result could lead to a class action lawsuit. Thank you for your time.... and fix this **bleep** problem, respectfully.

S

SirXandel

New Participant

Hello, now is the third v64 PTC update out, but this issue still existing. 😞

K

kakao551055

New Participant

"I believe in Meta."

E

er0s3nnin

Participant

I might have just figured it out. I think the issue is fixed but it's not actually running the full update properly for some people. I've had issues through all the updates v62, v63, v64 (419, 464 and 484). Most recently most (but not all) of the popups being gone but incredibly unstable usb connections and the battery draining immensely fast. So much so that I had to keep putting it back on charge every 45 mins. And even then charging would take FOREVER.

Anyway I had noticed since probably v62 maybe that the shutdown screen (when you hold the button for second) would always have a section asking me to apply updates when shutting down. And even though I would say to do that nothing would happen. It would just shut down. But the message was always there, so much so I thought it was meant to be there (it just always says it)

So earlier I was reading other threads about troubleshooting other issues and someone mentioned about hard shut down with volume down + power. I did that and rebooted back into the device. (the person was claiming the device never really shuts down with normal power off and this is the only way to clear some kind of cache).

Anyway next boot I fiddled with a few settings and then tried the normal shut down but this time when it shut down I got the update dialog box (with the rainbow progress bar). It did that for about two minutes and then shut down. I was intrigued because I was already on the latest (484) and I had checked about 20 mins before and there was no new update available.

When it booted first thing I did was check the version, still the same v64 (484 version) so was baffled about what had just happened. But within a few minutes I noticed something - Charging was working right again. Excited I jumped into virtual desktop etc. and everything was back to stable and running correctly and can use for hours now like I did before this whole mess without any issues.

Also on the power down screen - THE PROMPT TO INSTALL UPDATES ON SHUTDOWN has gone. I'm pretty darn sure there was part of the one of the previous updates that was supposed to run on shutdown which has been failing to run and then not fully applying the whole fix and the device was in a "partially updated" state until I managed to trigger this shutdown update.

Would be good if someone else could try and see if they have anything similar going on. Might explain why for some people it worked and others not.

M

MPires

Inspiring

Yesterday I received another 9 Gb update (still V64) and then I had a 2 hour session without any problems. I started the session with 96% charge and ended it with 100%. It is possible that the previous update was not complete... . I hope the problem is resolved.