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

[Star.Knight]

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.

[tomhorn123]

One of the saddest things I've learned throughout this whole debacle......the indifference towards we 'minions' of mega powerful companies notwithstanding....is the corruption evident of YouTubers, influencers et al

Several who I have previously watched and listened to are clearly 'in the pocket' of these companies.

I have posted regarding this issue on their YouTube videos, they have all without exception been deleted almost immediately.

Who do we trust? Who is not lying to us or hiding the truth??

I'll never take anything, without a generous pinch of salt, from these people ever again.

[Skippy111taz]

I couldn't agree with you more. I had the same issue. I tried to comment on every YouTube video I've seen about the Quest3 and it's "new' features. And 99% of my comments got deleted. My comments weren't even violent or vulgar. It just goes to show that the internet is fake unless you go to the deep web.

[EdLuva72]

I’m still receiving the USB-C charging port disabled message when turning on my Quest 3 sometime after the v62 update.  I don't have a cable plugged in when this happens.  The v64 update did not fix the issue.  There is no debris or liquid in the port.   The same link cable works flawlessly with my son’s Quest 2.  

Also, my original Quest 3 charging brick is no longer working.  This seemed to go bad around the same time as the v62 update.  The cable still works, so I need a replacement charger.  I’ve only used the original charger until it stopped working.  I now have to use my phone charger to charge the Quest 3.  The factory reset has been done and does not fix any of my issues.

Public Release

3rd party INIU DI-401 16FT Link Cable for Meta Oculus Quest 2/3/Pro - 

18W Fast Charging While Playing

[EdLuva72]

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

[Massacher]

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?

[Halaster]

---

@Massacher wrote:

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?

---

Yes, while there are a few people in here still seeing the issue the number that this version fixed it for is far higher. Read the past few pages of comments, especially when the version first came out, and you will see a lot of people confirming that the version fixed it for them. Once they confirmed it is fixed they mostly stopped commenting in the thread, only leaving the folks who still have the problem. 

The charging is both fixed and better, as well as the battery usage in the most recent version for those of us that the fix worked for.

[shakeel100]

Today i got v64 for quest 3,but unfortunately debris and liquid issue still not resolved even got worse.I tried every  nook and corner and factory reset,all in vain.Whenever i power off the headset and then turn on,the first message  i see is:USB is disabled due to debris n liquid.Meta taking no care of us.

Now is the time to put my quest3 under the wheel of

[Massacher]

@Severem 

"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?"

But who is going to do that? Even if all of us in this thread did that they'd find someway to prevent too much bad press coming out. And what about the Youtubers losing their paycheck? I doubt they'd sabotage themselves.

v62 does have this problem. I just experienced it tonight. I don't know how the firmware reverted back to that. I had it on v63 the last time I used it about 6 weeks ago.

[Massacher]

@Severem 

"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"

As it should. I want to see them squirm.

[DreadHeadFred]

I'm past 2 weeks with v64 PTC, and now I think official v64 (not sure how to tell but PTC is off). I haven't had a single debris message since.