Quest 3 stuck in Battery Saver Mode
So I toggled the battery saver mode 3 days ago and ofc it lowered resolution. I wanted to test the feature. So I toggled it on, saw the change, and then toggled it off. When I turned it off, the resolution stayed the same, the fovetated size stayed the same. Everything was the same as if I was still on battery saver mode (with full charge on the headset).
I ignored this issue until today as I cannot deal with it anymore. I restarted the device, resolution is still low, text is pixelated, FOV is terrible, everything warped. The headset thinks I'm in battery saver mode still. Tried toggling it on and off and there is literally no change when turning it on, and of course no change when going back to off.
Please help.
I'm on v60
**NOT A SOLUTION** MARKING FOR VISIBILITY**
Hey everyone! Engineers are currently looking into this and in the meantime, will need you to get connected with support using this link here. They will need to provide a few steps and possibly collect logs. As well as getting this escalated to our internal specialist through email. Our support will have the tools to get a better look into this for you! As well as submitting a bug report!
In addition, please get connected with our support through a PM by clicking their name MetaStoreHelp and making sure you're signed in.
[Also not a solution] - Simply for visibility
Hey everyone, just jumping in here to fill in for AliceinVRworld. Looks like our internal team is still currently looking into things and wants to suggest a few steps to try:
- Try to update your headset to PTC v69 or the latest version of V68
- Factory reset the headset (make sure cloud backup is on)
If you are still running into issues after, please continue to submit bug reports and provide us with the following:
- What's the full version number of your headset? (64.0.0.####### or likewise)
- Quick Settings > System > Software Update
- Troubleshooting already attempted (please feel free to list them out)
As soon as I have this info, I can bring it over to the team.
Thanks again!
Glad/not glad to hear that you tried other headset and you saw that there are no differences at all between the two.
The thing I'm honestly thinking is this: they way his "issue/situation" got stigmatized is for me kinda wrong. It's not related at all with the battery saver button and probably not eventually with low power mode that get stuck somehow.
Ok weird that toggling the battery saver is not visibly lowering the graphic, but as I always stated, that is a description and you should check the code behind it to be sure about the effect of activating that function, so that can't be taken for granted.
Guys we also have to take in consideration that the headset received so many updates now and it's not strange to admit that the headset after one year can look and work differently compared to whenever it cames out... different interfaces, functions, different energy consumption and way of working and not everything is written in the New Version change logs of course.
I would personally explain this situation like this... the Quest 3 changed, they actually changed it and it's not a "bug".
I did many tests at this point and I can say that only certain dynamic objects (mosty texts and flat surfaces) are affected by the saw effect... increasing the resolution from Sidequest is solving the issue, also using QGO is solving this bad graphic.
Changing the framerate from Sidequest is also working, no one is really "stucked" at 72hz since the change can be done manually. Even if before we could change natively the setting of Refresh rate from Quest settings and now it's staying at 72hz standard... did u notice that the option disappeared from the settings? They just removed it, you are not stucked at 72Hz, that's just how it works now, if you force the headset to work with higher value, it will... it's not stucked.
Another huge difference that I'm now noticing and I don't think with previous updates was like this, is that now is visible how the Quest 3 is "reserving" GPU and CPU power when running an app. In other words when you are running a demanding app or the system is just using some of his capability on something, when you try to open or trigger some other app or certain dynamic objects, they will be runned at an embarrassing resolution, very pixeled, it happens also with guardian lines, but it's only temporary since the system is focusing graphic power in something else.
And that's all guys. I really think you should accept the fact that things are constantly changing, more functionality means more power needs, and this also mean that the entire working logic of the device has to be revised and things CAN'T remain the same in a system like this. I agree that might looks like a downgrade for some reason but you should be positive regarding next updates and just accepting your little headset and setting it up the way you prefer, because thanks to Sidequest and QGO you can totally fix even that small things you are complaining about so it's really up to you.
To the one that are still saying "it should be perfect with stock settings" I would say man, it is what it is at the moment... In a way yes, I agree with seeing that the Quest 3 is running in a sort of power saving mode, just lowering the resolution when it could definitely works 10000 times better than it looks, but for me is not the case of calling this a bug or an unresolved issue...I really think is the actual choice of the developers and we should see it as it is.
Peace out ❤️
