Meta Quest 3 - Unusable for many people after recent update. 6 weeks and 700 comments with still no resolution
Post by: u/piercy08
https://communityforums.atmeta.com/t5/Get-Help/Not-Resolved-Known-Issue-V62-63-USB-C-Debris-Water-Warning/m-p/1148154/highlight/true#M271317Open linkView original on lemmy.lukeog.com
78 replies
76vangel: Oh valve please release an index 2 I’m so fed up with this annoying meta crap.
Strongpillow: Lol valve. Always this cope in posts like this... You don't have to wait for valve to not do something you sound like you not happy about. It's not vital to your health sticking with Meta products... Empty threats for the theatrics or not doing something unless it's super convenient for you doesn't really help the situation.
Philorsum: You madder about his comment than entire headsets not working with no official word on when or if theyll be fixed.
Strongpillow: Lol. Mad? I'm the one that said they don't need to wait. Get out now if it's that problematic. No sense in continuing until it's absolutely convenient waiting for a competitor to materialize. It's not vital to your health. Empty threats mean nothing.
It's also people that default to valve being some kind of savior for doing literally nothing for a decade is baffling to me.
---fatal---: So the fucking latest update causing this. Fantastic.
I wondered what the fuck is going on. Debris couldn't get into my USB port as a power bank is constantly connected.
piercy08: I'm glad you posted , I feel some what vindicated. I felt like a proper Karen posting this 🤣 but least it's helped someone , and hopefully with some publicity Meta will finally fix it
piercy08: I appreciate this isnt the most fun topic, but, realistically theres going to be a lot of people buying headsets and finding it doesnt work. Hopefully can give some visibility so people can think before they purchase.
I imagine with this being the oculus reddit it might get removed, but I can only hope they are fair and allow warranted critism
TrefoilHat: As an aside, this isn’t an official Oculus subreddit so I’m not sure why this would be removed. Making people aware of bad (and good) things about the Quest and helping people deal with them is part of the reason for being here.
If criticism about bugs, Meta, or bad updates wasn’t allowed, some days there would be no discussion at all!
piercy08: Ah I thought it was official , good to know
TailOnFire_Help: Does Reddit have officially anything? It's all volunteer run. I don't think they would want another company making decisions on their platform.
piercy08: I thought some subs had representatives ... No idea how much power they have though
TailOnFire_Help: Yeah companies can have accounts. Actually I may be talking out of my ass, I'm almost certain I've seen at least one company rep account also be a mod.
FuckIPLaw: Whoever grabs a subreddit name first gets it. Sometimes that's the company that the subreddit is about. Sometimes they'll get PR people onto an existing mod team, too.
TailOnFire_Help: Yeah as I was thinking it through I realized you're right.
IBartman: Just curious, does the error pop up with no cable connected ever?
Th3S1l3nc3: This is the greatest thing I could see all day. I was on chat with Meta all night trying to get them to understand that they broke my device and it was almost criminal to keep pushing the OOW program where I buy a refurbished headset for $169 to replace this one.
Again and again and again they pushed me. I kept screen shots. They passed me off when they couldn’t answer anymore. I had one guy directly say to me “No, it was not the update”.
I had no idea this was going on for six weeks. I just turned my headset on after a year. Worked great when I plugged it in to charge and was bricked the next day!!!
I’m beyond livid and there is no where to turn. They told me there was no supervisor. There is no number. And with Meta they can do whatever they want. Big enough they don’t care.
If I was considering a headset, no matter how affordable it is, I would want a Quest if they can just get remotely bricked for no reason!
Th3S1l3nc3: https://preview.redd.it/to4a0zublkpc1.jpeg?width=1170&format=pjpg&auto=webp&s=bf533c12e86d89cacfdeb6d6b8f0d2ac6c03dfaa
Outright lying.
Th3S1l3nc3: https://preview.redd.it/hd5s97f4lkpc1.jpeg?width=1170&format=pjpg&auto=webp&s=9ed97b9b63ebd6e16c97b8bfa3772d47221df370
More pushing the OOW
I get broken link for those reddit links.
Th3S1l3nc3: https://preview.redd.it/upm7s5fwkkpc1.jpeg?width=1169&format=pjpg&auto=webp&s=6ae46da861c61e70d6f141090ce23b3048c63abc
Another where they just ghosted me
Th3S1l3nc3: https://preview.redd.it/7nn1z665kkpc1.png?width=1169&format=png&auto=webp&s=6323566e5f50c95964f5d35b2a3d36afd781e1a6
Trying to upsell me on a NEW device
TheMasterOfLoki: Yep. I've been facing the same issue since I updated to V62 (and still V63). No issues when playing unplugged but when using while charging or plugged in with ANY cable (included cable, extended 6ft cable or just any other USB-C I have at hand) it flags up that warning / error randomly and intermittently, kicking me out of games or video. A mix or resets, different cables, cleaning & updates have not helped at all.
teiji25: Does this affect battery headstrap, too? Either way, I'm glad I stayed on V60 with auto-update off.
senpai69420: It affected my old powerbank but the problem went away when I swapped it
retropyor: Just posting for visibility, but the issue here is that after the latest update, it's giving a false message as there's dust or debris in the USB-C port
SvenViking: P.S. Meta seems to be saying this is something that will be improved in software updates, in the linked forum thread:
> 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!
absorbingtoxicity: I'm getting that "Go to meta.com/device and connect your accounts"
NewShadowR: For me it only happens if I plug in a cable but there's no power running through it, be it an extension cable or the one to my battery pack. Plugging one in with power fixes this.
BlueFeathered1: Thanks for clarifying. I haven't gotten this and wasn't sure what was up.
SvenViking: I’ve been getting that message too at times, but not too frequently fortunately for me. (It does seem to have increased in frequency compared to the first couple of months when I only got it once, though. Hopefully coincidental?)
RedcoatTrooper: I had it today for the first time, as with others my wire has been connected all week so no chance for a foreign contaminant.
It went away thankfully but this is a concern.
LevKusanagi: Thanks for sharing, I posted on here originally about this issue, I spent a month waiting for resolution, I have now returned my quest 3 and will be buying a big screen beyond. I think Meta has been disrespectful to its customers, and I’d rather spend my money elsewhere. I need a reliable device because I do simracing.
AutoModerator: Thank you for your submission to r/oculusquest piercy08! Feel free to check out the following community resources:
Discord Channel: Dive into our fun Discord community! We host events, giveaways, and there's even a dedicated support section if you need help. Don't miss out on the fun. Join us on Discord!
Wiki & FAQs: Seeking answers? Our Wiki and FAQs are packed with valuable information.
Referrals: Please note that we do not allow quest referrals on r/oculusquest. However, if you're looking for device and app referrals or wish to submit your own, you can head over to Meta Dog.
We're thrilled to have you as part of our community. Let's keep r/oculusquest an amazing space for VR enthusiasts!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
deftware: It says "Status: Issue Replicated. Fix In Progress."
BroadswordBlues: Anyone recently experiencing subtle strobing, as if one of the lenses is flickering white? (Not the white flecks many have experienced, including myself)
This new issue was introduced to me just recently after the update but I suppose it could be early signs of unrelated hardware failure.
Styrofoamexpert: Try shorter cable. .moar powa.
colbyshores: I have been having an issue where the homescreen just hangs on bootup on my Quest 2 with the most recent update. I have to fiddle with it on and off to force close in order for it to load.Jesus, they have like 3 devices to support. Who the hell do they have over there doing QA at Reality Labs?!
ThatGuyOnDiscord: They're working on it; all we can do is wait, and bitch when something like this inevitably happens again.
kermityfrog2: Kind of sucks with forced updates nowadays, instead of choosing which update you want or don't want to install.
throwawayPzaFm: At least on v62 it's not forced. Just turn off updates in settings.
wraith8178: I’ve had this issue multiple times with my Quest 3 recently as well.
Germangunman: I had this come up, but my Bobovr was plugged into it without the battery pack on it. Unplugged it and it went away. Got pretty lucky.
VicMan73: Why even such warning should be in the first place? Do we need to know if water or debris is in the USB port? How to measure it? Through the amp delivery? Or changes in the voltage? If you use a less quality USB 3 cable, the warning may show up? I don't do wired VR gaming.
piercy08: Hey yeah, I'm not sure . People say they are getting it with the official cable , so it's debatable if it's a cheap/third party cable thing ...
It could be meta trying to detect third party cables, so people buy their very expensive one .. but that would be the conspiracy theorist in me and there's no proof of that really.
At the moment, all we really know is that it's a bug, both official and non official cables suffer, a lot of people are experiencing it and that it seems to have appeared in recent updates.
Dramatic-Bath9890: Can confirm it’s with official cables. Happened to me once with standard in the box charger and another time with the official oculus link cable. I always use link to wall to charge because it’s faster charging than the standard cable but after link gave me the error I used white in the box one and it still gave the error
wraith8178: I’m the same boat as this person.
Silversmith144: Its probably a result of the quest 2s massive issue of the USB port overheating and actually melting all the plastic around the port.
piercy08: Actually a good shout, that might explain it's sudden appearance and why it's taken so long
Mythril_Zombie: It's an android thing.
elFistoFucko: I am curious as how it is measured/detected, but my galaxy phone and tablet have both let me know when I've (stupidly) inserted a cable I had got wet and not thouroughly dried off before inserting.
I'm guessing there is a simple short protection in the devices that triggers the warning, but the meta issue is with the software behind the warning.
General-Permission-5: Another issue that makes me happy I didn't get one. Have quest 2, same sort of problems. And still no word on san andreas vr, that announcement was a scam. You got zucked if you believe it.
webheadVR: Just as a data point, no issue here.. but definitely seeing this complaint around here.
I am curious though, people having issues, what have you tried? I'm just curious if I should bother trying to troubleshoot this with users I talk to.
firmretention: It happens to me with multiple different cables, whether I'm using them to charge with the stock adapter, with a power bank, or wired Quest Link. Had no issues prior to v62.
piercy08: Unplugging it all and plugging back in again.
Shutting down both headset and pc and trying again.
I've tried doing things in specific orders, like turning headset on then putting cable in. Or cable first then turning on headset. Headset on before starting pc. All that jazz. Unfortunately no luck.
I should add, I have a friend with a q3, uses it for the same as I do, SIM racing. Same update version , he is working fine, never seen the issue
webheadVR: If it's link, have you tried another cable? I'm thinking even a phone charging cable.. 2.0, really anything bog standard just to try.
piercy08: Originally I did try another cable , but it didn't help then I saw the thread and gave up.
I should also say I had no issues with my cable for maybe 2 weeks , and then constant issues. Nothing had changed it just started occurring, I can't remember if I updated at that point or not
webheadVR: I'm wondering if there's some sort of issue in the port or cables people are using triggering this. I have only managed to get the warning once and it was a very old charging cable is why I wonder.
​
I'm not blaming users, I'm just trying to see if I can provide suggestions at least when people have this issue :(
piercy08: Yeah it such a shame because if this didn't happen I'd have no complaints about a good upgrade from my index.
AlvinCopper: I think it was a software issue - a bug, when it shows I just click ok and continue without disconnecting, everything works and it is annoying, happens 7/10 times when it is plugged in, although this won't happen while playing. Or could it detect non official cable? I have doubts.
piercy08: In my case it happens almost every minute or so
As I am sim racing , I don't have the controllers in hand to click ok, just a steering wheel , so I crash the car (as I can't see past the pop up), try again and one or two minutes later it's back again. Can't even complete a single lap .
AlvinCopper: Oh that's quite bad, I mainly use it for flightsim if that happens it would be useless. I suspect it could have something to do with their debris or water detection mechanism on the software side, maybe it is electric current related and the threshold is a bit lower. Maybe they lower that threshold after the recent v62 update. Seeing that there is a difference in the frequency of this issue occurring it could also have something to do with the quality of USB cables as well, but I presume that cable is not the main issue here.
SkipnikxD: Strange, quest restart works 100% of time for me
DullStation1: In my case I use a powered link cable. This pop up mess only happens in PCVR with some games (i.e. City Car Driving (a LOT), Assetto Corsa (sometimes)) but not with others (iRacing never happens, half life helyx never happens). I suspect it has something to do with FPS fluctuations, which trigger a false positive on the cable (or when switching video modes?). I’ve seen reports of people saying it happens when charging against the wall, but this never happened to me yet. Smells 100% like a Software issue on the PCVR driver, for sure. I use Oculus app whenever possible (no OpenVR / OpenXR / No air link / VD)
krectus: Is this just the same post that gets made after every update?
piercy08: Unfortunately not, it's been an ongoing issue for many people for months, it seemed to really ramp up at the start of February
Mythril_Zombie: How many people?
burgertanker: Is this an issue with v63?
piercy08: I believe it started with v62 and didn't get any better with v63. It doesn't seem to be affecting everyone though
burgertanker: I was gonna say, I thankfully haven't had this issue. Guess I'll pause updates until I hear about a fix
Th3S1l3nc3: FYI all, talking with Meta again and they said this is NOT a known issue. They aren’t admitting anything
wordyplayer: But if you click on the OP link, it is in the Meta forum, and a meta employee proclaims in a large bold font: "KNOWN ISSUE"
full text copied below:
"Not a solution - Marking for visibility
Known Issue
Status: Issue Replicated. Fix In Progress.
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!"
Th3S1l3nc3: Yep. Your guess is as good as mine. This experience proved to me that Meta is garbage
wordyplayer: Strange that the phone support and the online support are not on the same page. Perhaps the phone support is outsourced, and they are the very last to get any new information...
Historical-Ride-3169: I’m still at v62. Did most people get v63 already? I keep the auto update on but it was never updated to v63.
piercy08: As far as I'm aware this issue affects v62 and v63 , some people are lucky and dint have the issue though
SpookyFries: I'd be curious to know what the "fix" ends up being. My old Pixel 4a has been doing this for years now. When the battery dies all the way I can charge it. Once it's on for a day or two I get the message again. It's one of the more annoying things I've experienced with android
JoshuaPearce: Take the cart out and blow into it. That should make your NES stop flashing.
Silk02: I haven't had this issue either recently, but did have it start if the year, it eventually worked it self out. I blew in the port left it for a day or 2 after trying a couple restarts. Haven't had the issue can't remember if I factory reset or not but assuming you have done that? As that's always their go to.