Quest Pro controllers go to sleep too quickly.
Both my partner and I have Quest Pros. We AirLink them to our PCs and play VRChat that way. However, we've both noticed that if we stop moving our hands for only about 10 to 15 seconds the controllers seem to go into a sleep mode which causes our characters in VR's arms to drop straight down to their sides. We can wake the controllers back up by wiggling them a bit but it's quite annoying and jarring to have your arms constantly fall to your sides. It's especially annoying when you're using one controller to scroll through a menu and the other goes to sleep causing the game to enter into one controller mode and then the controller you were using to scroll a menu now moves your character so the menu closes and your character starts moving in some direction. I have looked all over but do not see a way to adjust how frequently the controllers go to sleep when not being moved. I've also tried factory resetting both the headset and the controllers.Solved11KViews8likes25CommentsQuest Pro left controller not work/pairing - V71(controller update)
I didn't use my headset for a while but left it on the charging dock. It looks like they auto -updated the system to the newest version . ( Auto- update check and sleep mode update are checked . ) V71 seems to have completely broken my left controller. It won't pair again , and it's not tracking at all . Actually , the V71 controller update caused the issue . They were paired and connected when the system update was completed . But after the controller update, the left controller started not working , and the controller icon turned into a "not connected " icon when the update was finished .Strangely, It was showing "Left controller is connected" via bubble messages. To try to fix the issue, I tried to reboot my left controller , and it connected for 2 - 3 seconds, during which I saw the dot at menu that tracking was working for a very brief moment before the disconnected icon appeared on the UI panel again. I decided do clean process steps from online guides . 1. Reset controller, ||| button with X => did not work. 2. 35 -second boot - up down - up process => did not work . 3. Factory reset the headset => did not work. 4. Perform a side-load reset => did not work. It seems that a reset is not the issue, so I downloaded the Meta Horizon app to check stats and manage the pairing . When app run, They showed as connected , and both versions and batteries were displayed , proving that they are communicating. To start from scratch, I removed the left controller from the app and tried to pair it again. Now I receive this message: "Your headset was disconnected . Please reconnect your headset to continue editing your headset settings . " This message seems to pop up immediately when they find each other and attempt to pair . With every attempt, they fail to connect . The left controller seems to be fine ; the LED is blinking normally , it can access factory reset mode , and it can enter Bluetooth pairing mode . Someone mentioned that they must be on the same network and bandwidth , so I tried changing the Wi-Fi setting to 2.4 or 5 for my phone and headset , but that did not help at all. So , in conclusion, I've done everything I could , and I don't believe my left controller has an issue or is defective because it was working perfectly a month ago , and I didn't drop it or anything. I am assuming that this seems to be an OS or software issue. Please tell me the fix or what more I can do. I really don't want to buy a new controller. If I had dropped it or damaged it through hardware impact while playing , it would not be a big deal to get a new one, but this seems to be a software issue , not a hardware issue 😞Solved8.5KViews5likes40Comments
Meta Quest Pro WiFi setup fail on university network
We've purchased a bunch of new Meta Quest Pros for our university XR lab. We cannot connect them to the university's WiFi network at all -- cannot get through the initial device setup. In the WiFi settings, the Quest Pro does not seem to retain the CA Certificate selection [Use system certificates] nor the Domain name. It indicates that it has saved the network settings, but fails to connect. When I go back to the settings, all of the other settings appear to be retained: EAP method [PEAP], Phase 2 authentication [MSCHAPV2], Identity [correct], Anonymous identity [blank], Password [(unchanged) -- I can only guess whether it has been retained; I have retyped it many times]. But the CA certificate reverts to [Please select] and after selecting [Use system certificates] the Domain has reverted to [blank] again. These things are bricks if we can't get past this. We have many other WiFi devices running on our network -- notebook computers, phones, ... it is not a problem with WiFi signal strength or stability.Solved27KViews6likes42CommentsQuest 3 & Pro controllers stuck at 0% updating
0% update forever on both PRO controllers that are already sync with a quest 3 headset What I had done.. Pair them again and again the Q3 got them paired all the time Hard reset on controllers Factory reset on Q3 headset (even that involves a huge waste of time) V64 is the version of the software of my Q3 Nothing worked so far in other post I saw that randomly people finally got this controllers working what was not my situation Support on chat after we try it everything ask me to send the pro controllers back what I already did (I already did all that support was asking for but for respect the support guy time I follow all what he asked for "maybe it works this time by a chance"). As I see this issue as very common I want to know what is going on for PRO controllers, Q3 is perfect for me for work as I use them as tool, but for play even vs Q2 the tracking of quest3 is inferior by a lot. If there is no proper solution for this I see no point in order another controllers or even keep the quest 3.Solved17KViews4likes66CommentsKnown Issue - V65 - V67 USB-C Debris/Water Warning
Not a solution - Marking for visibility Known Issue Hello everyone! I have observed that a significant number of users are still encountering the USB-Debris error even after the V64 fix was distributed to everyone. Consequently, I have taken the initiative to inform the team and create this fresh post in order to distinguish between those who faced the issue in the previous post and those who are currently experiencing it on V65-V67. We would greatly appreciate if everyone could please provide the following information: What's the full version number of your headset? (62.0.0.####### or likewise) Quick Settings > System > Software Update What's the full version number of your PC app? (62.0.0.####### or likewise) General > Scroll down to the bottom of the page. Is your PC app on PTC? Are you enrolled in Quest PTC? Any potential workarounds? Which headset is everyone using? Is this only happening with the Quest 3 currently, or is anyone experiencing the same thing on their Quest 2 and Pro I'll do my best to keep you all updated as soon as I find out anymore information! Update 5/26/24 Hey everyone, a little update for you - our awesome engineers are on top of this issue. Don't forget to send in your detailed reports and share any info you have, especially if this problem is new to you. Your input is super valuable! Update 6/6/24 I just wanted to give everyone a quick update that there haven't been any major changes yet. However, I want you all to know that I'm actively monitoring this thread every day and passing on any information that users provide to the engineering team. Update 6/11/24 The engineering team would like me to gather the serial numbers of the headsets of all those affected. Please send me a private message with your serial number. Please do NOT send your serial number in this or any thread publicly. Update 7/3/24 Thanks to all who sent in their Serial numbers. Our engineers are still looking into this matter and are working hard to resolve it in an future software update. Update 7/9/24 We appreciate all those who have provided their serial numbers. If you are still encountering the issue even after updating to V66, please reach out to our support team via private message here for further troubleshooting assistance.118KViews9likes111Comments
