DeoVR busted again with new update
I for the longest time thought that DeoVR was to blame, but since the firmware update a few days ago, I realize it's been the Quest firmware updates hysterically tinkering with head tracking the whole time. I'm on Quest 3, but i had the same issue on Quest 2 - suddenly and without warning, the 6ofD head tracking and dome scaling just becomes "wrong" out of nowhere. E.G., tracking your head forwards or backwards will zoom appropriately, but every other dimension will translate WAY too much as a result, making the video you're watching hypersensitive to tiny little micro motions you don't even realize you're making with your head, rendering almost anything with video or passthrough completely useless. Previous firmware it was calibrated better, it almost seems like it goes normal>bad>normal>bad, with each update. You're basically having to choose between things looking wrong in one way, or looking wrong in a different way. From update to update, It's never consistently wrong, and it's not the app. I keep several versions of the app on hand to jump between whenever this happens, even though it usually doesn't fix anything. It makes more sense now that I know it's not DeoVR, because sometimes I'd be on the same exact version and turn the headset on and just feel like everything suddenly looked horrible where it didn't just hours prior. The color grading gets weird, the passthrough feed and the video clash colors forcing me to turn up night mode so everything is an analogous orange, but which totally defeats the purpose of having color passthrough at all. I guess my question is, why are we messing with the head tracking and color grading at all, when clearly we know that we know what looks good and what doesn't since every alternating update gets it right? It's almost like I'm being pranked, or like I'm being manipulated into engaging here on the forums, or being baited into getting upset and doing unwitting advertising by complaining online, or something. Why is the meta for our updates snip snapping between the normal product I paid for and an insane clown world version with no explanation? This most recent update the tracking is so bad I get motion sickness just IN THE MENU without even opening an app or game at all. How much the passthrough feed moves relative to the very slightly translating HUD menu I'm trying to read makes me feel like I need to immediately rip the headset off and find a bowl to puke in, and I've almost never gotten motion sickness in my entire life. Anyway, really hope we can fix it, thanks for your time.
META Firmware information not available
I can't get the to tell me which firmware version I have. I have both the RayBans and Oakleys. The META AI says to check the app to see the firmware version, but it's not there. Then it tells me it cannot say what the firmware is. I keep asking and one response "It's not important what the firmware is, just use your glasses." Yes, literally. Then I ask again, and it says it cannot tell me and to check the app. So I ask again and it says v11, and I ask how can I upgrade to v21 and it says click update. But update says the glasses are up to date. Basically, this doesn't work. There are a LOT of claims by META about these glasses and they have only been basic cameras and speakers for me. NOTHING ELSE. I paid $500 twice to wear cameras on my head. Amazing.
Software version 83v from 12.11.25???
Hello, I registered as a PTC some time ago. I didn't like it, so I left again. Of course, I kept the PTC 83v firmware because you can't remove it until the next official version comes out. Today was using the VR and noticed that there's now a stable version 83v. However, my software shows that it was created on "12.11.25". That version wasn't released then, but this December. How am I supposed to understand that?
Quest 3 battery drainage when not in use.
If quest 3 staff read this please read it properly and not give me an automated reply I work in IT I don't want automated or generic support I'm not an idiot. I’ve been dealing with a persistent and widespread issue affecting the Meta Quest 3 headset and controllers related to severe battery drain, both during use and while powered off. For several months, I’ve noticed that even when the headset is fully charged and then turned off properly, the battery depletes at an unusually high rate. After leaving the headset unused for approximately one month, the charge drops from 100% to around 5%. This is extremely frustrating, especially since my previous Quest 2 headset could hold a full charge for months without any noticeable drain, and its controllers maintained more than 60% charge even after extended periods of inactivity. I have thoroughly reviewed all available settings to disable features that might keep the headset active in the background or prevent it from entering sleep mode. I’ve also turned off auto-updates and background services, yet the issue persists. Despite these precautions, the headset still performs auto-updates and consumes power unnecessarily when it should remain idle. To rule out individual hardware faults, I tested two separate Quest 3 headsets in my household both exhibit the same problem. Additionally, several friends and family members who own the Quest 3 report identical behaviour, confirming this is not an isolated defect but a broader design or firmware issue. I’ve kept the firmware updated in hopes that Meta would address the problem, but there has been no improvement. Each update seems to introduce additional complications while failing to resolve the ongoing battery drain I hate the fact the headset will auto update when I have that turned off. At this point, it’s clear that the Quest 3 suffers from a serious power management flaw that needs urgent attention from Meta’s engineering and software teams. The level of battery depletion while the device is off is unacceptable for a headset and significantly undermines its usability. It feels like the setting is a lie when you turn off the device its like turning off is a fake sleep mode where you device is in fact still on and updating even if you disable.Controller Light Blinking Help
EDIT: before you read this, the problem has been fixed. (look below) Ok so my left oculus quest 2 touch controller is blinking on and off (spelling SOS in morse code). It appears to be paired in the app, but the headset says otherwise. Its been like this for about an hour. I've searched this problem up online, and apparently its some sort of failed firmware update. There are lots of fixes online but none of them work for me. I have tried: - unpairing then repairing the controllers from the app. (x3) - taking out the battery then re-inserting it. - restarting the headset (x2) - entering Bluetooth pairing mode on the controllers - shutting down the headset and then turning it back on. none of these "fixes" worked for me, and every time I tried one the controllers got more buggy: - left controller (bad one) buzzing every half second - right controller becoming unpaired - default cursor (when no controller is paired) staying in one spot If oculus somehow finds this message, please add some sort of firmware reset that will delete, then reinstall the latest version. Help is appreciated, and if the controllers fix themself (for some reason) ill edit this post. until then, HELP o _ o EDIT: ok so after maybe an hour, the lights started to blink very rapidly. after five minutes the controller reconnected, and after maybe 15 more minutes the blinking stopped. I think that during that time the controller was either updating or reverting to a stable state. Anyways, if you have this situation, just wait about an hour and a half. EDIT: view this post for the continuation of this story (it gets worse) https://forums.oculusvr.com/t5/Support/Controller-not-working/td-p/946474
Quest 2 bricked by firmware update
Hi all, Unfortunately like many others I have a Quest 2 that has been bricked by a firmware update. Meta support have said it's out of warranty and have offered me a refurbished replacement Quest 2 for = £180 (242 USD) which comes with only a 90 day warranty. I understand it's now out of warranty but it's not like this was caused by a fault of our own doing. It has been very well looked after. This Quest 2 was in storage for quite some time since last being used. The symptoms match exactly what others have stated under this issue. I have confirmed it's charging all ok via a USB C power meter. It no longer powers on or shows any lights. When connected to a PC, it is recognised in Device Manager as qusb_bulk_cid:0412, which indicates the device is in Qualcomm's low-level emergency recovery mode, but Meta have not released the software required to recover it pubically. Some news articles on the issue suggest that Meta were replacing or fixing devices out of warranty but it seems that this is no longer the case? https://communityforums.atmeta.com/discussions/OtherTroubleshooting/meta-quest-2-completely-bricked-after-initial-software-update/1275188 https://www.roadtovr.com/meta-free-quest-3s-replacement-bricked/ https://mixed-news.com/en/cause-of-bricked-quest-headsets/ I think the suggested price for a refurbished replacement of a now discontinued headset is way too expensive, especially with only a 90 day warranty. It's not sold any longer. The stated retail price of 299 USD was correct when it was on sale before, when new and before the 3S was released. What's to say this issue won't happen again in a future update or for the Quest 3 or 3S? I understand it's older now, but it's in perfect condition and the only issue is with the software, caused by a Meta update - now it's a useless paperweight and not even from my own doing. It sure puts you off buying a new headset. What are your thoughts?Quest 1 Headset Stuck in Setup Loop. Serial Number Not Recognized.
Hello everyone! I've encountered a very strange and frustrating issue with my Meta Quest 1 headset and I'm hoping someone in the community has faced something similar and can help. My headset is stuck in a setup loop after I performed a factory reset. The screen constantly shows a message to "Continue setup in the Meta Quest mobile app," and I can't proceed past it. I have already tried all the standard solutions I could find: Factory Reset: I performed this both through the phone app and the Fastboot menu, but nothing changed. App Data Clearing: I cleared all the data for the Meta Quest app on my phone and tried to connect again. Manual Firmware Update: I successfully sideloaded both the latest and an older firmware version onto the headset. The headset updated, but the problem remains. ADB Commands: After the firmware update, I tried to run a command to complete the setup, but it failed because the headset was not detected by ADB. Here's what puzzles me the most: Serial Number Not Recognized: When I enter my headset's serial number on the Meta website for verification, I get a message that the device could not be found. My account page also shows no registered devices. ADB Issue: Before the factory reset, my headset connected to my PC without issues and showed the "Allow USB debugging" window. Now, it doesn't. It seems that the problem isn't with the headset or the firmware itself, but with its connection to Meta's databases. I have exhausted all the solutions I know. Also, the headset hasn't been launched for a year Has anyone else encountered a similar issue where the device's serial number is not recognized by the system? Are there any other options besides contacting official support? Thanks for any help!
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.
