02-07-202412:44 PM - last edited on 04-23-202410:21 AM by TheLegend27
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.
Would you please confirm with us if the issue is only when trying to use the cable and if the AirLink works?
Looking forward to hearing from you.
Best regards,"
My response was Airlink works but the error still pops up when charging. The error occurred directly after doing the V62 update. And of course I attached a link to this thread.
Use any cable which keeps Quest 3 charged during use. So, powered cables with PD standard like the Kuject or the Tiergrade. With the stock charger!! Hundreds of cases, weeks gone by, and you haven't been able to replicate???? Are you joking?
Anyone who uses a powered cable which can keep the Quest 3 charged during use has this issue. Hundreds of cases reported here and on reddit, weeks gone by and they can't replicate it?????
Yes, official link cable and official wall charger. The issue has nothing whatsoever to do with the cable. Shut down the headset and plug it in. It charges normally. Turn it on and the 'moisture/debris' warning comes up and it won't charge. As has been mentioned many times already in this thread, this issue is specifically related to the bugs in v62. I've been using Q3 and Q2 before that for 2.5 years and this has never happened until v62.
This blew my mind as well. How on earth are you gonna release a headset that literally cannot draw the power it needs to not die during use. I guess they wanted to avoid having to make a weird cable with a wall brick since a USB port on a PC can't deliver enough current to keep it charged. It's much cleaner to just have one cable and if the consumer assumes it will work without dying then that's on them I guess.
Thanks. If it comes to it I will try that, but potentially bricking our headsets shouldn't even be an option we have to contemplate. I really would love to be a fly on the wall of the office that is responsible for working on this software. Wtf goes on in there that they can't even take 5 mins on a lunchbreak to post a reply to this 2 WEEK old thread that affects every single customer of their flagship hardware product?
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
