Forcibly updated to V2.1
Ok so firstly, I don't even want to be here because somehow my Quest 3 is updated to 2.1 even though I have never joined the PTC in my horizons app. So, the issue with V2.1 I'm having currently is that the controllers go to sleep WAY too fast. It used to take longer so when idle your controllers just don't disappear immediately but now after 3 seconds of inactivity it just disappears until you move it again. While this might seem to be a non-issue, it is immersion breaking in some cases, please revert this behavior to the previous version. Additionally, why was I even updated to 2.1? Is there a way for me to not be included, I'm having a very bad experience with it currently.
Browser WebXR controller vibration bug after updating to OS v2.1
Hi, After updating to OS v2.1 and starting my own WebXR (VR) game (using A-Frame) I noticed something annoying: When the right controller should vibrate, the left one does and when the left controller should vibrate, nothing happens. In Wolvic, this issue is not there (just wanted to try another browser to see if it was the browser). I have tried different approaches to solve this issue by debugging and rewriting my JS code to no avail. It worked perfectly fine before the update. The vibration works correctly in the OS itself, so that's not an issue (did unpair controllers and removed/inserted batteries etc.). Could there be a bug in how WebXR works in the latest Quest browser? Would appreciate all the help I cant get, Thanks!
PTC v2.1: Both of my Quest 3 headsets are paperweights
Whatever Meta is trying to rollout has disabled both of my headsets. I just have a grey screen. Multiple attempts to use software update tool \ factory reset are useless and don't help. 'Tech support' is no help. I explained it is highly unlikely that both my headsets crap out within a week of each other for no reason. Other than that Meta staggers their update pushes. Honestly I feel like this is intentional to make it harder to look like it's their issue. If they rollout an update, but not everyone's headset is effected, then obviously not the update. Maybe everyone doesn't know they stagger the updates. This is not the first time. I have had to send back 2 headsets both failed due to their updates. The last one I just got back in October of 2025. It's now March, a few months later, and it's a paperweight with whatever update it has received. On top of that, I was not allowed to buy extended warranty on the replacement. Why? This replacement unit has nothing to do with the unit I just handed you . This one will be broken in 6 months time with the next update. So after the 12 month mark, and manufacturer warranty no longer in place, we are just supposed to buy another headset? How is that not a form of fraud. We bought something; now we can't use it because of something you did; and you won't fix it. .... Update: one headset has come back to life. Through some magic combination of either factory reset or software tool update one came back. Still no luck with the other after fresh factory reset and retry of software update
Quest 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! 🙏
3 problems regarding Navigator, PTC and a need to downgrade without factory resetting.
Hello! This is Broken Computer, a owner of the Quest 3S. Im pretty proud of it, but there are some problems i need for the Software Engineers to check: Problem 1: in the new PTC (V 2.1 ), there are problems with navigating the menu. The bottom mini thing in apps that shows buttons to go into Focus Mode, Minimize or Close it dissapears in some situations. It annoys me to restart it to fix it, only for a few moments later to happen again. Problem 2: Ive ALWAYS loved the new Navigator Mode, it looks very cool. BUT, in V 85, it has been removed for an unknown reason and I need to know it. Even if I upgrade to PTC 2.1, it doesn't appear! Why?! Problem 3: Bug Regarding changing the controller vibration: Ive been thinking, when going the controller vibration to Low, it glitches back to the medium bar, but the controllers won't vibrate. Did the new PTC start to act weird? Problem 4: Some design of the menu in PTC has been DOWNGRADED to a pretty lookin back. In 85, it had good design, but now? Ugh, I hate it! Are there any solutions? Thanks, Broken Computer.
V2.1 PTC - Question about Rollout
So I've been part of the PTC on Quest 3 for some time. I have the option enabled in the mobile Meta app, but for some reason the update doesn't seem to be triggering. I've tried disabling, enabling etc, but I'm stuck at v85.1034. Is the 2.1 rollout gradual in the PTC or should anyone enrolled in the PTC get it now? Sorry if it sounds like a stupid question, but last time a PTC update came out, I got it same day. (Based in the UK)
