Quest 2 bricked after updating it to 2.4v
So I recently found my Quest 2 headset laying around on a case after not touching it for over 1-2 years, and I got in the mood to try VR again. It was working just fine, however, I noticed it wanted to me to update it, and so I updated it. After updating however, it's now bricked, it's booting just fine but the main screen is now flickering between the gray thingy from the cameras and the main menu. The controllers also keep turning on and off and the headset seems to be heating up quite a bit. I tried many things such as: Updating firmware with ADB using the sideload update option Updating the headset again using Meta's website Factory restting All of which had no success, so I really appreciate any help with this.
We need to talk about the Meta Quest Software.
Hello, my name is Mateus Camargo, I'm a developer from Brazil, and I recently got a Meta Quest 3S. While the hardware itself is impressive, the software experience has some severe flaws. I’d like to highlight three major issues that aren't just bothering me, but a significant portion of the community as well. 1. System Performance and Fluidity The Horizon OS feels noticeably unoptimized. Simple tasks lack fluidity, and occasional stutters break the immersion entirely. Paradoxically, each system update seems to degrade performance instead of improving it. The OS needs a deep optimization pass to become lighter, more responsive, and efficient. 2. Lack of Environment Variety (The Horizon Home) The Horizon Home experience has become incredibly monotonous. We used to have access to a wider variety of environments. While the new default environment (Valley) looks beautiful, the current lack of options feels like a step backward. Stripping away diversity ruins the personal connection users have with their virtual space. 3. Missing Basic Productivity Tools It is frustrating that a powerful standalone headset lacks fundamental tools like a native Calculator, Stopwatch, or Notepad. While competing devices include these by default, Quest users are forced to rely on unofficial workarounds or heavy browser tabs just to take a quick note. Implementing basic, lightweight native productivity apps should be a priority. I hope the software team takes this feedback into consideration. The hardware is great, but the software needs to match its potential.
Viewing Quest Achievements
We're coming up on a year and we still don't have an official way to view and sort the Quest Achievements that we put forth effort unlocking in our massive VR libraries. Developers continue to include them in games as they know it yields extended play sessions and even users revisiting their games to experience every ounce of the hard work they put into their projects. Currently we can only view them in a recently unlocked list in the Meta Horizon Mobile App, and external websites created by Quest users (which are the most useful way at the moment). People didn't even realize Achievements existed because it was hidden in the Scoreboards App, and users hoped for integration into the Profile itself, similar to Steam, Xbox, and PS. Instead, we were left with a misunderstanding of how important Achievements are to the Quest ecosystem. At the very least, could we please get a way to filter by game/in-progress/completed in the Horizon Mobile App? We would love to see them in-headset eventually, but even a small step forward would revitalize our play sessions. 🙏
Quest ideas that will make games run better
LPDDR5 (Low Power Double Data Rate 5) memory, introduced around 2019, represented a significant advancement in mobile DRAM technology. It supports data rates up to 6.4 Gbps, delivering improved bandwidth and energy efficiency compared to prior generations such as LPDDR4X. This standard incorporates features like dynamic voltage scaling and enhanced data handling mechanisms, which contribute to better performance in power-constrained environments while maintaining thermal stability. LPDDR5 has been widely adopted in mid-to-high-end mobile devices, providing a solid foundation for multitasking, graphics-intensive applications, and early AI workloads.b707f5 LPDDR5X, released as an evolutionary enhancement in 2021, builds directly upon the LPDDR5 architecture with notable improvements in speed, efficiency, and signal integrity. It achieves maximum data rates of up to 8.533 Gbps (or higher in optimized implementations), representing approximately a 33% increase over standard LPDDR5. This translates to substantially higher memory bandwidth—often exceeding 68 GB/s per package—while offering up to 20-25% better power efficiency at elevated performance levels. Key technical refinements include advanced I/O interfaces, reduced latency characteristics under load, and compatibility with existing memory controllers, allowing seamless integration into flagship platforms.3500492b9264 Relevance to Meta Quest Devices and Performance Potential In the context of Meta Quest 3 and Quest 3S devices, which utilize the Snapdragon XR2 Gen 2 platform paired with LPDDR5X memory (typically 8 GB configuration), the hardware is engineered for demanding mixed-reality workloads. Micron and other partners have qualified LPDDR5X solutions specifically for this chipset, optimizing for high-bandwidth VR rendering, asset streaming, and multitasking. However, current firmware and dynamic power management often constrain observed frequencies (commonly reported around 1800–2100 MHz base clock in monitoring tools, equating to effective rates well below the standard's full potential). Unlocking higher sustained memory speeds—approaching the upper limits of LPDDR5X capabilities—could yield meaningful gains in frame timing consistency, reduced asset loading delays, and overall smoothness in graphically intensive titles.daacff Implementing configurable memory frequency scaling or higher performance tiers would require developer mode access, which is already standard practice among Quest users seeking performance enhancements via ADB commands, custom optimizers, and side-loaded tools. Such an update could be delivered through a targeted firmware release, allowing advanced users to enable elevated memory controller states when thermal and power conditions permit (as demonstrated by stable operation at ≤36°C with sustained high CPU clocks). For broader compatibility, a lighter variant of these optimizations could extend to Quest 2 devices, which employ earlier LPDDR4X memory, providing modest bandwidth improvements without full LPDDR5X-level changes. Potential Benefits and Considerations Elevated LPDDR5X utilization would directly benefit VR gaming and applications by alleviating memory bandwidth bottlenecks, enabling higher resolution textures, more complex shaders, and improved simultaneous processing of passthrough and rendered content. This aligns with the hardware's inherent capabilities under favorable conditions, such as plugged-in "infinite battery" setups. A developer-exposed option for memory performance tuning would empower the community while maintaining Meta's control over safety parameters, ultimately enhancing user experience across the Quest ecosystem.
The new quest ui is terrible
so the new ui just came out for meta quest and its the most annoying overly complicated ui i have ever had the displeasure of dealing with anyone know any way to reverse it or suggest they change it back or at least give us the option to choose berween the old and new one its extremly annoying i know along of people feel the same way i have to slide thru like 9 tabs to locate an app i used to be able to see on one easy to slide screen and trying to open the call im on is like a 25 step process vs just clicking on one button on my quick menu please reverse this or give us the option to choose between the 2 or customize itCannot Make Purchases. "Request cannot be completed until further actions"
Basically when i wanted to make a purchase, I couldn't, and this message kept popping up saying "Request Cannot be Completed until Further Actions." Probably because I entered my pin incorrectly like once or twice. But Now i can't buy games on my account. Is there any issue to resolve this?
