{"id":114495,"date":"2025-05-19T14:00:08","date_gmt":"2025-05-19T14:00:08","guid":{"rendered":"https:\/\/www.europesays.com\/uk\/114495\/"},"modified":"2025-05-19T14:00:08","modified_gmt":"2025-05-19T14:00:08","slug":"meta-cto-addresses-quest-3-battery-setting-issue-following-bungled-horizon-os-update","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/uk\/114495\/","title":{"rendered":"Meta CTO Addresses Quest 3 Battery Setting Issue Following Bungled Horizon OS Update"},"content":{"rendered":"

Meta\u2019s latest Horizon OS update for Quest (v76) introduced a new Battery Saver setting as default, which has led users to experience frame rate issues in apps and games. Now, Meta CTO Andrew \u2018Boz\u2019 Bosworth says the company is rolling out a fix and \u201ctaking a serious look\u201d at how OS updates are communicated in the future.<\/p>\n

In a recent Instagram AMA<\/a>, Bosworth addressed recent user complaints about a quietly included system default, which\u00a0automatically toggles\u00a0a more aggressive version of Quest 3\u2019s Battery Saver mode.<\/p>\n

Previously, Battery Saver limited Quest\u2019s refresh rate to 72Hz, applied fixed gaze rendering, and reduced brightness to 50%\u2014something which could be toggled on in the settings to extend battery life.<\/p>\n

The latest v76 release of Horizon OS however includes a new version of Battery Saver as default, putting the headset\u2019s refresh rate to 90Hz, but critically capping many games at a nauseating 45FPS.<\/p>\n

If users were unaware they could turn off Battery Saver, they would have no idea why the headset all of a sudden decided to act up, possibly even leading to blame falling on individual developers for poor optimization.<\/p>\n

\n

PSA<\/strong>: To disable Battery Saver on Quest 3, navigate to the \u201cPower\u201d settings within the \u201cDevice\u201d menu in the settings app. Then, toggle off the \u201cPower Saving Mode\u201d option.<\/p>\n<\/blockquote>\n

Notably, many Quest apps don\u2019t use Application Spacewarp (AppSW), which some older titles implemented to smooth out low framerate stutter by generating synthetic frames between real frames, effectively doubling the perceived frame rate.<\/p>\n

Bosworth says Meta is \u201crolling the fix out for that.\u201d He further notes that while the usual staggering of Horizon OS updates \u201chelps us identify regressions sooner,\u201d the company could \u201cdo better on documentation\u201d when it comes to patch notes. As it stands today, iterative Horizon OS patch notes are fairly paltry, often times only including a few line items without much explanation.<\/p>\n

Here\u2019s the full transcript of Bosworth\u2019s comment below:<\/p>\n

\n

Yeah, good discussion and feedback from developers this last week on the stability and changes that we\u2019re making in our rollouts, making sure that those are higher quality than they have been.<\/p>\n

I think it\u2019s great feedback. We\u2019re taking it seriously for the battery saver issue. We\u2019re rolling the fix out for that.<\/p>\n

And more generally, I don\u2019t think it\u2019s the case that we\u2019re rolling things out too quickly. I do think it\u2019s just the case that we\u2019ve got to have a stronger set of processes in place for quality control before things go out the door, which we\u2019re doing.<\/p>\n

We\u2019re taking a serious look at this. We\u2019re spending time on it. So we appreciate the feedback as always from developers. We take it seriously. That\u2019s our responsibility. These are our mistakes. And we\u2019re going to fix them.<\/p>\n

And we understand that this is not casual. This is people\u2019s livelihoods and time spent on the line that matters a ton in the experience that consumers have of people\u2019s software.<\/p>\n

So yeah, taking that seriously. We\u2019re doing the work. I think staggering things helps because staggering things actually helps us identify regressions sooner. But I agree we could do better on documentation too.<\/p>\n<\/blockquote>\n