78.1028 Neverending Update Loop
What’s up with 78.1028? I can’t get my MQ3S to update. It tries to download, oddly wants to restart to apply update at the 90% mark, restarts, and then does that again, and again, and again, and again, and again…and now it’s like 1000-degrees of heat…and trying again, and again. What’s up Meta? Relying on interns and AI pair programmers again?
Join Meta's AR/VR User Research Community and help us build the future!
Join our AR/VR User Research Community and collaborate with our user experience (UX) research teams regularly. Your insights and feedback will play a crucial role in shaping the future of augmented and virtual reality products and experiences! Eligibility: This opportunity is currently open to residents of the United States and the United Kingdom. As a member, you may be invited to participate in various user research activities, such as short polls, surveys, in-depth interviews, and focus groups, covering a wide range of current and upcoming products, services, and features. Participation Benefits: Influence the development of upcoming Meta products Gain insights into the latest AR and VR initiatives, including new features and Beta products Access exclusive content curated by our UX Research Team, showcasing how your feedback impacts product development You may receive swag or e-gift cards as a token of appreciation for your participation Interested? Fill out this quick survey to sign up and start making an impact today!
Quest 3 Controller Bricked by OTA Firmware Update - No Recovery Options, Only $50 “Fix”
On June 6th, 2025, my Quest 3's right controller abruptly stopped working after briefly reporting a low (but likely incorrect) battery level. It was working perfectly a few days prior. After trying the standard troubleshooting steps, I’ve concluded that the controller was likely bricked by a failed firmware update, and there’s no available way for me to recover it except to pay $50 for a refurbished replacement. Here's what happened: libosutils Failed to get real path of file '/data/vendor/misc/sensors/latestfwversion/f43058c4acd3faab', err: No such file or directory 18:48:39.573 SensorService Failed to read from file /data/vendor/misc/sensors/latestfwversion/f43058c4acd3faab 18:48:39.573 libosutils Failed to get real path of file '/data/vendor/misc/sensors/batteryinfo/f43058c4acd3faab', err: No such file or directory 18:48:39.573 SensorService Failed to read from file /data/vendor/misc/sensors/batteryinfo/f43058c4acd3faab These errors show that the controller is failing to report its firmware version and battery status, and never fully initializes. It can pair, but: Doesn’t vibrate during pairing (haptics subsystem never loads) Doesn’t send telemetry (battery, firmware, etc.) Can’t complete firmware update via OTA What likely happened: Quest v76.1027 began rolling out on June 2, 2025. I used the headset on June 4, which likely triggered a silent controller firmware OTA. The controller may have shut down during the update due to battery instability. This resulted in a corrupted firmware image, leaving the controller stuck in a partial boot state. After factory resetting the headset, the controller worked briefly until the headset likely tried to push the firmware update again. Now the controller pairs but never becomes usable again. My support experience: I contacted Meta support and was immediately offered the out-of-warranty program. $50 to send in the controller and get a refurb. No one reviewed the logs I provided. Every email was answered by a new agent, and every escalation request was ignored or redirected back to the same scripted reply. I did not cause this issue. Meta pushed an update that bricked my device, and now I’m being asked to pay for their mistake. What I'm Asking: All I want is for Meta to repair or replace the controller they broke, without charging me $50 for it. If I had access to the reflashing tools, I could fix this myself in minutes but those tools are not provided externally. If anyone from Meta is listening: please escalate this to someone who understands firmware. This is a known class of failure and it shouldn’t be offloaded onto customers who had no control over the OTA update process.
PTC v74 Release Thread
Hey Everyone, The Public Test Channel (PTC) for Quest v74 started to roll out today for Meta Quest 2, Meta Quest Pro, Meta Quest 3 and Meta Quest 3S. If you're seeing an issue or bug after updating to PTC v74: 1) For issues: Go to our Get Help board and search for any existing thread on the issue, if you don't find one, make a new thread. Please add the tag "PTC v74" to the thread and in the title. This way everyone can look for just PTC v74 issues too. 2) For bugs: If you come across a bug, please post each one you spot in its own thread, to keep track of individual issues separately. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. Share your impressions in the comments below and let us know if you see any issues. We know it's tough when you run into a problem on a PTC build and want to thank you all again for testing out PTC and sharing your feedback! This feedback is extremely helpful to our engineering teams. We appreciate your interest and persistence in testing out the core functionality of software as we develop!OpenXR News and Feedback Thread
This thread is to highlight latest developments regarding Oculus and OpenXR! If you're running into any issues with OpenXR and/or have feedback to share, leave it as a comment in this thread! Latest Update 7/23/21: Oculus opens full support for OpenXR, deprecating proprietary APIs! Full Support for OpenXR means that we: Help developers build new applications with OpenXR via our Developer Site Perform QA testing of OpenXR to ensure features are working Address bugs when reported Provide developers API access to new capabilities via OpenXR A year from now (August 31, 2022), Compatibility Support for Oculus Native Mobile and PC APIs will end and they will be Unsupported. Existing applications will continue to function on Oculus devices, but our level of support will change. Read the full details in the following blog: https://developer.oculus.com/blog/oculus-all-in-on-openxr-deprecates-proprietary-apis/ Past Updates 7/23/20: As of v19, we are officially supporting OpenXR 1.0 implementation. Developers can now submit their OpenXR apps to the Oculus Store. For mobile, please use the OpenXR loader that shipped with v19 or higher. You can find the latest PC SDK version here and the latest version of the OpenXR SDK here. Known Issues (will be fixed in future release): Grip pose is misaligned. Action spaces continue to track even when isActive == false, which is conformant but misaligned with other runtimes. This will cause issues if relying on on tracking state vs. isActive for rendering hands. Parent interaction profile bindings are missing for non-natively supported profiles (everything besides the Simple, Touch, and XBox controller profiles). If you have any questions regarding this release, please post them as a reply to this thread!
