(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.

[vicksonzero]

Problem came back again.

Last night i did some more dev work with my usb-4-pd-c-to-c (2meters) cable again. I got some debris warnings and that cut my input to the game until i acknowledge the message.

it didn't actually cut my access to usb though. i checked the dashboard and it was still charging.

what is different this time is perhaps i wasn't that absolutely careful about plugging it correctly, and perhaps the cable got a little bit wriggles every now and then. i would still classify that as perfectly normal use though. that amount of wriggle shouldn't cause any kind of disconnects, as i am well within 1m range and the cable is 2m in length.

Would small wriggle in the usb ports trigger this warning, like some unusual micro-disconnections?

my headset is not with me right now, will edit this post for the current software version info.

[er0s3nnin]

I installed the new updated 2nd version ptc 64 yesterday (v64.0.0.464.370.584939338 version with the "464" instead of the "419")
It seemed to have resolved all my warning issues even with the connection order issues being alluded too in the couple of posts above this one (I can now connect in any order, no popup)

Issue is now the battery drains super fast plugged into usb.  Before it used to drain a bit but I could use for hours and take occasional breaks where it would recharge off usb and it would never really get below 50% MINIMUM and that would be after a mammoth session with no breaks.

Just now I put my headset on, and it had been left charging from usb (or so i thought) for at least an hour because I was taking a break and it pinged up saying running out of battery, looked and it's on 15%.  I was only using it barely for barely an hour or so before that too.

I've just had to plug into a different charger because I don't think it charges at all over usb anymore (official quest link cable) and it most certainly did before this 2nd version of ptc 64.

[Rolldabeatz]

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. 

[DreadHeadFred]

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.

[MPires]

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

[MPires]

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.

[Severem]

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.

[SirXandel]

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

[kakao551055]

"I believe in Meta."

[er0s3nnin]

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.