v.79 PTC Release Thread

if i turn my quest pro of i "sometimes" get a black screen and the hmd does NOT turn off, the quest pro is just stuck in the black screen ....

i have experienced this behavior since serveral version, i cannot say when it started but i can say it is still there in v79....

you cannot write a bug report for that in the hmd because the bug report system in the hmd isn't managable when you get a black screen :D

cuando van a dar respuesta tengo desde el 25 del otro mes con este problemas y no veo solución, mis meta no se puede usar

Todays update: v79.1030 build 5115411.9220.520

still same issue with usb 3.2 gen 1 & 2 but and its a big but if I use Usb 3.1 gen one it'll work via single cable usb c to c or using the y configured cable for charging and usb connectivity to the PC... Only if I first just connect the Y cable to the quest and PC then and the charger cable, and I get MTP without developer mode plus my usual USB activitys work as they should.

hope that makes sense. Feels as thought this VR by meta is a one man show with maybe 1 employee.

"educated guess that the USB issue is related to charging protocols"

These headsets are based on an older version of Android correct ?? Yet somehow the developers keep screwing up USB, WIfi etc etc, what I don't understand is why are they fiddling with these with Android ? The User interface is basically a skin over the top like any Android based phone! Yes I understand that that interface interacts with the core software but isn't this what developer API's are for ??? it's pretty much plug and play with Android now days so why are they messing it up so bad ? Maybe instead of pay millions in signing bonus to AI programmers from Chat GPT, start pinching a few programmers from the likes of ONE PLUS and SAMSUNG, could you image the fall out if Samsung released an update that stopped your USB port working ?

Lets be honest here the real issue with Meta and it's hardware division is it doesn't care about it's products as they have no real competition in the VR market at this price point (sorry Pico you never really took off) so it's a simple case of like it or lump it.!

This firmware is seriously becoming a joke. Every single update breaks something new. You fix one issue, and two more show up. It’s like the firmware team is throwing darts blindfolded hoping something sticks.

Here’s the brutal truth: Meta needs to stop trying to be so “different” with their own flavor of Android for VR. Stop reinventing the wheel. Just stick with the **bleep** proven Android VR framework that works. Instead, they slap on this clunky, closed-off UI that makes basic functionality a nightmare. The more they try to lock it down, the worse it gets—USB issues, MTP not working right, busted power behavior, broken file transfer modes, random laggy menus, glitchy voice commands, and now I can’t even shut my headset down without it freezing or rebooting itself.

It’s like Meta is actively sabotaging their own product by prioritizing secrecy and control over stability and user experience. Why even base this on Android if you're just going to butcher it?

Honestly, the hardware is solid, I’ll give them that. But the firmware is dragging the whole thing down—and the reputation of the headset with it. Every update feels like it was coded by interns or middle schoolers on a time crunch. Who signed off on this? Does Meta even use their own headsets for more than 5 minutes in testing?

Navigation is clunky, UX is regressing, and basic features that worked months ago are now inconsistent or totally broken. And don’t even get me started on the way bug reports are ignored or buried.

Meta, if you’re reading this:
👎 Stop pushing half-baked firmware
👎 Stop closing everything off
👎 Stop pretending this is fine
👍 Go back to basics. Build on Android like it was meant to be used.
👍 Open up some of the system again so devs and power users can help fix what you won’t.

Hello kylespringer!

We would love to support you with your Meta Quest needs!

What seems to be the issue?

Remember you can also send us a PM!
Click on our name to access our profile page. 
Once there, select 'Send a message' to privately message us. 
Please note that you must be signed in to the community before sending a private message.

Thank you!

MetaQuestSupport

puedes arregla mi problemas y lo de todos... como arreglamos este bug que tuuuuuuuuu has hecho.

haga su trabajo que para eso se le paga

Does anyone know how I can download version 79.1030 to my glasses? I'm stuck on version 79.1029 and they've kicked me out of the PTC program (I can no longer activate it on my cell phone, which is the determining factor). Things couldn't be worse.

Please, Meta, I have always been happy to be part of the development program to collaborate with the community in improving the quality of the Quest 3, but what I ask is that you DO NOT RELEASE such a poor and untested firmware, or at least with bugs as important as the Link Cable. It is normal that being a Beta version it will not come out perfect, I have been a programmer too, but at least it should be presented with bugs that are acceptable to the community and not with this atrocity that you have done.

As soon as you release a stable update, I'll stay put and never return to the PTC program. I've lost all trust in you, sorry.

theirs a bug that still exists where the quest 3 says its water damage or debris inside during pcvr and it kicks you out of pcvr and it dose it like every 20 to 50 minutes this bug needs to be addressed in the next update!

im going to continue to post this on every single update thread cause this needs to be addressed and meta is just blatantly ignoring a 2 year old issue because its a pcvr link cable thing i guess they just don't care im still gonna keep spam posting this regardless!

Hello 00levi00 !

We understand that you are having issues with a false detection of water or debris in the USB-C port, even when the port is dry and clean. This is definitely not the VR experience we want you to have. We do have some troubleshooting steps for you, please follow the below steps:

         1. Restart the Headset: Power off the headset completely (press and hold the power button for 10 seconds, then power it back on), then retry the connection. 

         2. Check for Updates: Ensure your headset has the latest software update. 

         3. Try a Different Cable: If possible, test with a different USB-C cable, preferably one that is not an extension cable. 

         4.  Clean the Port (Gently): If you suspect actual debris, gently clean the USB-C port with a microfiber cloth or compressed air. 

If it doesn't solve your issues, please submit a bug report with us. Therefore, our engineers will be able to look into this issue. If you have more concerns or queries, please contact us through a private message, Please select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.