Skip to main content
Participant
February 7, 2024
Solved

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

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.
TheLegend271265668
Honored Contributor
March 8, 2024

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

1055 replies

New Participant
April 10, 2024

v62 i saw this error twice, v63 every hour or so, v64 every 20-30 seconds.... oh so good to play racing sims :s

tryed everything on this forum, nothing has made any difference

Participant
April 10, 2024

Had v64 official release pushed to my Quest 3 today.  I’m still using the powered USB port to tether the headset to my gaming PC.  No issues, 2.5Gbps solid connection.  I still think there’s a power issue with the Quest 3 - as in it’s drawing too much power for a non-powered USB port to handle.  I brought this to Meta’s attention again.  No reply.  Meta Support is useless. 

New Participant
April 11, 2024

there's nothing special in meta cable, name on cable doesnt change physics.... i have https://www.club-3d.com/en/quick-view/2507/ cable, capable of 60w (q3 is 18w), i now think the problem is my mobo that gives out 0.3A 5V (why, i don't know yet, should be 0.5-0.9)

q3 software expects more while charging and gives out error messages

Participant
April 12, 2024

Problem is back again.  Thought the latest v64 update had done it because had a stable few days but it's all back again this morning. 2 debris warnings and battery just draining in no time for no reason.  Even when nothing is running and super super slow charging from any all my chargers including 45W, 100W and 145W ones I have.

This is the most disappointed I have ever been with a product.

Participant
April 12, 2024

Still happening......  🤦🏻:male_sign:

I use a 3rd Party 3.2 Cable. (20Gbps, 100W, 5A, 5 meters long)

 

TheLegend271265668
Honored Contributor
April 12, 2024

Hey everyone! Checking back in after the V64 public release to see if the issue is still affecting anyone. It seems like some of you are still running into the warning on the latest release, so I'd love to bring these reports to the team.

  • Can you share your current V64 build?
    • You can check in Quick Settings > Settings > Software Update under the Current Version Details section. The formatting should be 64.#.#.###.###.#########. Please post the full version number.
    • Is this a PTC build, or a public release?
  • Are you using the official Link cable, or are you using a third-party cable?
    • If it's a third-party cable, which one is it?
      • What's the PD rating of the cable?
Technology, at a certain level of sophistication, is indistinguishable from magic. - some wise guy or something probably
Rolldabeatz
Up and Coming
April 12, 2024

Hello Team!

  • Can you share your current V64 build? - V. 64.0.0.484.370.585752815 (Runtime V. 64.0.0.484.370.585752889)
    • Is this a PTC build, or a public release? - It is a PTC build.
  • Are you using the official Link cable, or are you using a third-party cable? - Third-party cable
    • If it's a third-party cable, which one is it? - Manhattan USB 3.2 Gen 2 Type-C Active Device 5m Cable
      • What's the PD rating of the cable? -  Supports USB Power Delivery (PD) and Quick Charge™ (QC) up to 60 W, current up 3A, voltage up to 20V
      • And as side note the Quest 2 runs nicely with the same cable.
Participant
April 13, 2024

TheLegend27 Once again will continue to post information into the void that is this this thread.  Still happening on the latest V. 64.0.0.484.370.585752815

I also have tried on every firmware version released since v62 and up.  They have all had slightly different results (some worse than others) but the problem never goes away.  Just occurs more or less often depending on whatever was tweaked in the firmware, but give it time it will occur again.

I have 13 different brand cables, all high very high spec-ed and expensive. I also have 12 different chargers (I am an engineer/developer) and all of them do the same.  The one I use most of the time is the official quest 3 link cable.

I have also tried the jsaux, iniu and kuject power cables and all of them have the same behaviour.  I have also used 3 different powered usb hubs too including kensington sd5700t which is considered one of the best on the market. (of course also tried without hubs).

I also have access to 12 different laptops and desktop machines of varying specs and they all have the same results.

I have tried to be patient on this thread and keep posting information but it really feels like a complete waste of my time. I have spent hundreds of pounds on cables, hubs and connectors and many many hours methodically trying every combination I can.  I think I can categorically say it is not the cables, not the computers, not the chargers, not the "setup".  IT IS THE DEVICES OR THE FIRMWARE.  Constantly asking people to post specs and making them question their sanity/cables/setup is disingenuous and outright poor and dismissive behaviour on meta's part.

This isn't even the only issue with the device.  The graphical artifacts that can get really bad sometimes (white snow and rainbow streaks), the elite battery disconnects, controller disconnects and not reconnecting until reboot and sometime weird controller tracking where it looks like you have some kind of parkinsons with your hand moving up and down constantly and many more.  These are all in separate threads on the forums and all of them are basically being ignored or getting the occasional message every few weeks of feigned sympathy but no action or resolution. All the while pointless new "features"  being rolled out that no one really asked for or wanted.

Personally I think there is a quality problem and you are shipping defective units and trying to shift blame to consumers for it whilst their warranties all run out and just treating it as collateral damage because there is not enough defective units and people complaining for it to have caused enough stink in press yet for anyone at meta to bat an eyelid.

I for one was evaluating this devices for the use with remote working and meetings across regions for the employees through out my company but I will certainly be looking forward to evaluating the vision pro soon and probably recommending that for rollout as this device is just not really even able to do the basics it claims to be capable of.

New Participant
April 13, 2024

Wow, so i just got the "cheap" link cable just to find out, that it is harder to set up then wifi...just got it running ONE TIME. The other times i just get the message that water is found on the cable or the software keeps searching forever for my computer. Way too much money for stuff that just dont work.

 

Edit: Just made sure...yes im on v64.

Inspiring
April 13, 2024
4 days in a row without any problems in iracing, in sessions lasting close to 2 hours and with initial power conditions ranging from 70 to 100%.
 
Vs: 64.0.0.484.370.585752815
Vs: Runtime 64.0.0.480.368.585752889
Vs: SO SQ3A.220605.009.A1
 
Using Tiergrade power cable.
 
The problem seems to be resolved in my case.
magic1968
Up and Coming
April 13, 2024

i have the ptc on and the last update on the v64 last week i dont get any usb water debris now and i can us the cable on the pc with out a prob and the airlink so am all good now 

Inspiring
April 16, 2024

Can anyone else confirm that v64 fixed the debris error? I was just using my HMD again today and I got the debris error twice within 30 seconds. I haven't updated and I'm hesitant to because what if it makes it worse?

Inspiring
April 13, 2024

Well its been a long while. I haven't used my HMD for I think a month and a half or so. I turned it on today to try out another game in VR. First thing I did is checked the version number. Somehow its reverted to v62 lol! That's before the debris error occurred. I am never letting it update.

Participant
April 13, 2024

You know, if this information were to be released to bigger media franchises, like Youtube or electronic reviewers, announcing the bugs that Meta has been trying to quietly overt by promising fixes that are never happening, this might cause a bigger stir and force Meta to actually fix a problem, rather than face the chance of losing potential buyers due to bad reviews.  I thought they were working on this problem... as in Devs were looking into it, apparently not.  v62 never had this problem... so why now?

Participant
April 14, 2024

Who would we release the info to exactly?

Participant
April 14, 2024

Well, on Youtube I suppose Mysticle might be able to shed more light to the public, though I am sure that the public who owns a Meta already knows about it, but the world at large probably should as well, get more attention from outside to make Meta realize this is a bigger issue and that their sales for these products could be at jeopardy.  I did once see a news article about it, though I found another one here:

https://community.oneplus.com/thread/1285338

As a company, they don't want their errors being made public because that means people won't buy their stuff, which makes them hurt financially.  Just a thought

Participant
April 15, 2024

I forgot to mention my link cable also stopped working with the Quest 3.  It used to work every time before the v62 update.