Quest 2 Browser Crash- Seeking Your Feedback
We're aware of an issue affecting some of you where the Quest 2 browser opens for a couple of seconds and then unexpectedly closes. If you’re currently experiencing this issue on a Quest 2 headset, please help us out by sharing your bug report. Some customers also are experiencing issues with broken apps on Quest 2 where reinstalling them rectifies the issue. Please let us know when this happens to you by submitting a bug report. To send the bug report, please DM and I'll provide a link to a Google Drive or provide my email. Questions Is the browser still crashing? Yes/No Are you available to help us investigate the issue further? Yes/No Do you have access to a Mac or Linux PC? Yes/No Are you familiar with adb and/or AndroidStudio? Yes/No If 'Yes', please run the following commands to help us pull the libchrome.so file: For Linux/Mac: adb pull $(adb shell pm dump com.oculus.browser | egrep -o "/data/app/.*/lib")/arm64/libchrome.so ~/Downloads/ For Windows: Two steps: Run the following adb shell pm dump com.oculus.browser | egrep -o "/data/app/.*/lib" Copy (ctrl-c) the output. It will look like /data/app/~~pSsE2yO2R1iJ26tnsq7f_w==/com.oculus.browser-bVK_Gl2PmYqqgBUdsfebug==/lib Example: adb pull ctrl-v adb pull /data/app/~~pSsE2yO2R1iJ26tnsq7f_w==/com.oculus.browser-bVK_Gl2PmYqqgBUdsfebug==/lib/arm64/libchrome.so Thank you for your help! Meta
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!Meta Quest build v67 release notes
These features and enhancements are becoming available starting this week of July 8, 2024 and are pushed to Meta Quest 3, Meta Quest Pro and Meta Quest 2 headsets. Please note that you can find the most up to date release notes on our release notes article and you can check out our v67 blog as well for more details. New window layout We’re adding the ability to move windows around when you have multiple apps open in your headset. You can reposition windows anywhere. You can also watch content on a large screen by selecting the theater view on any window’s control bar. You can find this feature under Experimental in Settings. Creator content in Horizon Feed We’re introducing new creator videos to Horizon Feed. You can connect with creators through reactions and sharing and jump into games and experiences directly from content in your Feed. If you are an active creator on other social networks and are interested in participating as a publisher, please let us know in the Meta Quest Community Discord. This feature is rolling out gradually Swipe Typing We’ve added the ability to use swipe typing to enter text when using your headset. Cut down on typing by sliding your finger or cursor from letter to letter to spell words. You can turn this feature on by going to Settings, then System, then Keyboard and selecting the toggle next to Swipe Typing. Eye tracking improvements (Quest Pro only) We’ve made further improvements to eye tracking on Quest Pro. For the most accurate eye tracking, you can always recalibrate by going to Movement tracking in Settings, then Eye tracking and selecting Calibrate next to Calibrate eye tracking. Do Not Disturb improvements We’ve made a number of improvements to the Do Not Disturb setting. You can now select different durations for Do Not Disturb. You can turn this feature on from Quick settings. If you have Do Not Disturb turned on, you can also control this feature from Notifications. Wi-Fi QR code scanner (Quest 3 only) You can now scan a Wi-Fi QR code to connect to a valid Wi-Fi network with your Quest 3 headset. To scan a QR code, go to Wi-Fi in Settings and tap Scan QR Code. Immersive media continuity You can now open Quest TV or use File Viewer to watch immersive videos without quitting your current immersive app.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!PTC v72 Release Thread
Hey Everyone, The Public Test Channel (PTC) for Quest v72 is starting to roll out soon 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 v72: 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 v72" to the thread and in the title. This way everyone can look for just PTC v72 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. Share your impressions in the comments below and let us know if you see any issues. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. 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!PTC v63 Release Thread
Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v62 and the solutions for some have shipped, while others are on the way! The Public Test Channel (PTC) for Quest v63 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. If you're seeing an issue or bug after updating to PTC v63 jump on over to our Get Help board and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v63" to the thread and in the title. This way everyone can look for just PTC v63 issues too. It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. 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!PTC v67 Release Thread
Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v66 and the solutions for some have shipped, while others are on the way! The Public Test Channel (PTC) for Quest v67 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. If you're seeing an issue or bug after updating to PTC v67 jump on over to our Get Help board and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v67" to the thread and in the title. This way everyone can look for just PTC v67 issues too. It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. 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!PTC v68 Release Thread
Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v67 and the solutions for some have shipped, while others are on the way! The Public Test Channel (PTC) for Quest v68 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. If you're seeing an issue or bug after updating to PTC v68: 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 v68" to the thread and in the title. This way everyone can look for just PTC v68 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. Share your impressions in the comments below and let us know if you see any issues. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. 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!PTC v66 Release Thread
Thanks everyone for all your feedback on our previous builds, several bugs were identified in PTC v65 and the solutions for some have shipped, while others are on the way! The Public Test Channel (PTC) for Quest v66 is starting to roll out soon for Meta Quest 2, Meta Quest Pro, and Meta Quest 3. If you're seeing an issue or bug after updating to PTC v66 jump on over to our Get Help board and search for any existing thread, if you don't find one, make a new thread. Please add the tag "PTC v66" to the thread and in the title. This way everyone can look for just PTC v66 issues too. It's best if you can post each bug you spot in its own thread, to keep track of individual issues separately. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong. 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!
