Dear Meta | What happened?
I've been happily using my quest 2 for 2 out of 4 years in total. The first 2 years were great! everything in the program felt neccessary and cared for, bugs were looked after. Reports were reviewed, and updates felt like quality. There were ups and downs but in the end everything was fun. These past 2 years have been nothing but a downward spiral. The UI change is weird, Settings misplaced, Lying about support, buggy server statuses, and of course the complete issue of Meta Quest link. What happened? We've done everything the AI supporter did and still you find a new way for us to hack our rigs just so we can last a second longer than 30 minutes. My suggestion: please just go back to the stable versions of both the headset and link app. Your latest version of both are so "stable" they disconnect "so much less". In sarcasm of course. PLEASE Meta please just stick with the stable versions and MAINTAIN THEM. I love my quest 2. But i can't see myself playing much nowadays due to these bugs. Good luck Meta team.125Views0likes7CommentsControllers go to sleep after a second of inactivity due to the v2.1 update
I recently updated my Quest 3S to the latest stable version, and now my controllers start turning off after just 1–2 seconds of inactivity. I’ve tried restarting the headset and re-pairing the controllers, but nothing seems to help.30Views0likes0CommentsV2.1 PTC - Nothing has changed
Meta makes it seem like V2.1 PTC should be an entire new experience, however after updating I still don't have NAVIGATOR or the SURFACE KEYBOARD feature. Can't hide hands, there's quite literally nothing that changed, like it's the same thing from 6 months ago, like what is the point of even naming this V2.1? Why do some people have the new navigator/surface keyboard feature on v2.1 but I don't, it's the same version... Meta should differentiate the version numbers because I clearly have a completely different firmware from others. It makes no sense.331Views0likes12CommentsQuest 3S stuck on PTC/Beta firmware - cannot leave, ADB broken, device missing from account
Hi everyone, tagging @MetaQuestSupport because I really need help. My Quest 3S is permanently stuck on the Beta (PTC) firmware and I can't get out of it no matter what I try. What I've tried: Toggled PTC OFF in the Meta Horizon app multiple times Factory reset multiple times (boot menu + Meta website) Manual ADB sideload of stable firmware (completes successfully but headset always boots back into beta) ADB commands to disable OTA updates The core issue: The bootloader always boots from the beta partition regardless of what I sideload. It seems like a server-side PTC lock that only Meta can remove from the backend. Additional problem: After multiple factory resets, the Quest 3S no longer appears in my account's device list on the Meta website, even though the headset is still logged into my account. What I need: Manual removal from the PTC program on the backend Re-linking of the device to my account The beta firmware is also causing hand tracking crashes and USB debugging (ADB) to malfunction. Thank you so much, any help is appreciated! 🙏92Views0likes1Comment