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

I noted yesterday I was still getting it occasionally and thought it was due to what I was connecting to but today I was working over remote desktop most of today doing the same task (so over a period of around 12 hrs). I had to take the headset off maybe 13 or 14 times to do other things and it occurred twice out of the thirteen or so times when putting the headset back on after waking up.  No factors changed.  Did exactly the same thing each time.  Device was never unplugged from the port or even moved or anything.  Sat in same position in same chair, put headset on the same way each time. Using same apps doing the exact same thing. Took the headset off the same way.

It certainly is better than before because I would get it everytime and I would also get it without taking the headset off but it's not fully gone. Seem to be if gets past the waking up part it's totally fine but if the cable is plugged in when it comes out of sleep then there is a still a small chance of the error occurring still.

version 64.0.0.419.370.583580230

Make sure to plug the cable into the Quest first and then plug it into the computer (or charger). I know it sounds like I don't know what I'm talking about, but I swear the order actually matters.

Two days in a row in iracing with no problems. The problem appears to have been resolved.
V 64.00.419.370.583580230
V runtime 64.00.414.368.583580275
V SO SQ3A.220605.009.A1
Connection with Tiergrade power cable.
The day before yesterday I started a 1.30 hour session with 96% and ended with 100% charge.
Yesterday I started a session with 65% and ended with 77%.
Another thing I noticed is that I increased the Encode Bitrate to 600 Mbits and had no problems with the sound. Previously only with 500 there were no noises. This version of the software appears to be successful.

Even on newest beta update if the cable unplugs or loses connection to the computer at the computer end before being disconnected at the headset end this error will pop up.  It’s something with the sensing in the headset of losing the connection with the cable still plugged in.  So any power settings anything that interrupts the usb signal will cause this error to pop up, including unplugging the cable or dust dirt and debris. Your coding or your sensor is not functioning correctly.  Come on meta. This is a pretty easy diagnosis. 

So v64 fixes the issue?  I’ve not had the issue on v63 as long as I use a powered hub.  Perfect 2.3Gbps connection via cable each time.  If I remove the powered hub, it won’t connect at all. 

Just got a new updated v64 ptc update and it seems better so far

old version 64.0.0.419.370.583580230

new version installed just now 64.0.0.464.370.584939338

On the old version I could trigger it easily by unplugging in from the computer end first (I also had another scenario where it would trigger coming out of sleep, not everytime but about 10% of the time)

So far I plugged the cable in and out a bunch of times and no error and flipped the headset on and off a few times and seems to not be triggering.  Will use for longer periods though and feedback but fingers crossed this follow up seems good so far.

Now they just have to fix the **bleep** survey popup on this site. It's like they have an obsession with annoying popups you can't get rid of 😂

The order in which the Meta charging/data cable is connected seems important (several mentiones in this thread and also mentioned in the spec. of the data cable on Amazon).

The correct sequence appears to be :

1 > connect Meta charging port to data cable

2 > connect data cable to Quest 3

3 > connect data cable to PC

My question is, if anyone knows....every time I connect this cable to my Quest 3 do I have to follow the above sequence?

i.e. I don't want to crawl under my desk to connect the charging cable, then back out to connect it to the Quest 3 and then finally back under the desk to connect to the PC every time!

I'm hoping to just unplug the cable from the headset, when I want to move to another room to play in 'stand alone', and then plug the cable back into the headset when it needs charging/playing tethered to the PC.

Technically, this isn't the correct order.

Any advice appreciated.

Here's your options:

1) Buy a height adjustable desk

2) Buy a better PC that has USB-C in the front

3) Move your PC so that it's accessible

4) Plug it in at the headset end but just do it before you turn your computer on.

5) Buy a USB-C extension cable.

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.

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.