quest 3 keeps turning off and on by itself repeatedly, but when back on, no controllers/hands work.
Quest 3 manufactured in December 2023 keeps turning off and on during use, usually after using a data cable either from my pc or from my piano's usb output (for midi which incidentally I can't get to transmit). Each time it comes back on, I'm presented with the pin screen, but I'm only able to move the pointer with my headset, not with my controllers or hand tracking. If I move my head more than 30 degrees I can no longer move the points, and if I press a button on the controller I can no longer move the controller, but repeatedly pressing the button on the controlller after I cant move the pointer, still causes the onscreen pointer dot to flash in response. A few seconds later it will turn off and then repeat the above process. Powering off the device and restarting it seems to allow it to work for a little while before it does it again. I'm not doing anything intensive in it, just meta workroom, and the first time it happened was in PianoVision. Battery is full charged. I've only had the unit 2 days. It's not overheating, because the first time it happened I'd only just turned it on. Strange thing is, since installing the meta remote desktop onto the PC, I experienced a similar issue with my PC when trying to take it out of sleep mode this morning. I think this might be coincidental though, because I wasn't using airlink when it first happened in PianoVision. Could the repeatedly going in and out of standby and the failure to receive midi be caused by a faulty usb-c socket on the quest 3?Interface of getting Controller joystick travel range
Hello, I’m fairly new to the Meta Spatial SDK, and while reviewing the Controller Input documentation, I couldn’t find any interface that allows retrieving the joystick’s travel range. What I came across were examples treating joystick directions as “Buttons” (like ButtonThumbRL). However, what I’m trying to do is map the joystick’s travel to an attribute like “velocity.” Is there any way to access this information? If I’ve missed something, my apologies, thank you!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.
右のコントローラーが接続されないです
なぜか右のコントローラーが反応・接続されません。 ネットに書いてある方法はできる限りすべて試しました。 ・コントローラーを振る・右と左のメニューボタンを同時に押す・一度ペアリングを解除して再接続・電池を抜いて入れ直す。 これらはすべて試しましたが、うまくいきませんでした。ペアリング解除後に再接続しようとした際、指示に従ってボタンを押しても、コントローラーのランプ（点滅）がつきません。 VRは1か月ぶりくらいに使いました。電池は最近交換しており、80％程度は残っているはずです。ただ、1回だけ机にぶつけたことがあり、それが原因かもしれません（右か左かは不明）。 対処方法をご存知の方がいれば教えてください。
Can't disable Xbox controller from interacting with my headset
When a controller is connected to my PC while using (wired) Oculus Link and I am viewing my monitors from within the headset, there will be a dot on the screen that follows my head movements. If I press 'A' on my Xbox Elite 2 Controller, it will act as if I left-clicked where that dot is, 'B' brings up the In-Headset keyboard context menu, left-trigger moves my in headset window, and right-trigger seems to snap my cursor back to the dot. The thing is, I don't want my controller interacting with my headset at all. I want to use my headset, with my computer viewing my monitors in headset and play a game with my controller without those inputs that were meant for the game, also interact with the headset. Another example is that if I'm playing something like Elite Dangerous, which is (very!) VR capable, but needs more input capability like the mouse and keyboard or bunches and bunches of mapped buttons on a controller. To be honest, the controller is easier for games like Elite Dangerous for most tasks but I can't have my 'A' button interfacing with the headset. Not related to Elite, but I also don't need my left-trigger to suddenly start launching in-headset window that I'm currently looking at all over the place. If I need input within my headset, I will grab my headset-controllers that I've set safely just off to the side, or if I can't find them, I can take off my headset to look for them. What's more, if I'm going to interface with my computer's monitors, I'll either be close enough to the computer to use the mouse and keyboard or I'll put back on and use the headset's controllers. I'm honestly not sure how this wasn't a user scenario when designing it. I've seen other posts from years ago and there hasn't been any change in this behavior to accommodate this scenario. I understand that this doesn't fit all persons because maybe the computer is far away from the Oculus and the only input you have in your hands is the controller but, in my situation, I need the ability to disable that. Is it possible to do this?
Can I connect my Quest 3 controllers to my Quest 2?
I have Quest Pro Controllers that I have been using on my Quest 2 (Great!!) I purchased a Quest 3 and will be moving the Quest Pro Controllers to it. I would like/prefer to pair my Quest 3 Controllers to my Quest 2 Headset. Currently this is not an option to select in the App. Are there any plans to allow Quest 3 Controllers to work on a Quest 2 (similar to how the Pro Controllers work on Q2)? What would be the reason to not allow/support it? Thank You! MrTasselhof YouTube (MrTasselhof) Twitch (MrTasselhof)
