Quest 3 stuck in Battery Saver Mode

jof

Participant

It is related to the passthrough even the web support team say it is

Participant

Regardless, all of this could be resolved easier, if they just made resolution a separate setting we could manually control, independent of battery saver. Then again, with our luck, they'd probably make a resolution dropdown that also wouldn't work either. So who knows.

Participant

This is only happening because META is leaving a vacuum for people to speculate. It would be nice after all this time of having this issue open, they provide some actual FACTS of what is going on, what they've done to investigate it, what the next steps needs to be. Instead this thread drags on and on, with little to no update from META. They really need to be taking control of this situation, and providing some direction.

I

Icyquaga

New Participant

I have been able to fix this issue.

I'm not sure about the passthrough, but when I turned battery saver on, I noticed that the foveated rendering got really bad (which ofc didnt change after I turned it off).

I tried using sidequest to change the refresh rate, texture resolution, and foveated rendering and everything felt instantly better.

One thing to note is that my passthrough wasn't affected by the battery saver mode as some were saying. I mean it sure is grainy, but not as bad as some of the footage I found on youtube.

jaybdg2024

Participant

Thank you. Meta still needs to get their act together and fix this bug the correct way rather than bypassing their issue with a side app. But if it somehow restores better resolution for now I for one appreciate you taking time to post this based on your testing. Thank you for that!

https://www.engadget.com/how-small-claims-court-became-metas-customer-service-hotline-160224479.html

Participant

When you see articles like this, I guess it all starts to make more sense now:

jaybdg2024

Participant

Not surprised based on lack of effort on situations such as this particular one.

jof

Participant

Could someone explain to me why wouldn’t this bug affect passthrough.

The battery saver lowers resolution, why wouldn’t it lower the resolution of the passthrough?

AliceinVRworld

Honored Contributor

Hey everyone! Our team is still currently looking into this. When I get an update I will make sure to let you all know through this thread!

We are all mad here.

AliceinVRworld

Honored Contributor

Hey everyone! Make sure we are staying updated right now that we have a new PTC v67! Still keep submitting those bug reports as well! Thank you all for your patience!

We are all mad here.

F

FrankDelano

Participant

Hi Alice, is there an expectation that v67 will impact this issue?
We haven't received any updates of substance since we all began reporting - is there an internal issue tracking number, what is the priority on resolution, has root cause analysis identified a cause, etc.

What is being done for customers who reported the issue as requested but wasn't engaged by support?

Are headsets still being replaced?

AliceinVRworld

Honored Contributor

I have no information on this but engineer team let me know to have everyone check new updates and submit bug reports as they are still working on this. We all appreciate the patience and know this is not the experience we should be having however, once there is an update I can let you all know.

We are all mad here.

M

mihaialexe12

Participant

I was messing around with the settings today (v66) and decided to turn on power saving mode to see what it changes.. then tried turning it back off, only to have the brightness, resolution, refresh rate and whatever else the option changes not go back to normal.. yes i can turn the brightness back up manually but the rest of the changes are still there. It looks and feels worse. Only after doing this did i get a flashback to the time i've heard and read about this being an issue months ago (before i had the headset, since i only had it for a few days now), and i must say it's absolutely shameful this hasn't been fixed yet and needs to be fixed as soon as possible.. it was supposed to be fixed so long ago.. Meta is trying to hide the people having this problem by making them PM them instead, so if you have this problem, or maybe i made you realise you do.. come forward and make a post and upvote this post as well.. i paid money to upgrade to this headset for a reason, a free undoable downgrade back to quest 2 type quality is not something i'll take lightly.

DasBearski

Honored Contributor

Meta was recommending doing a factory reset to restore non-battery saver behaviour.

Up to you if you'll take the gamble or not.

I know just enough about tech to look like I know what I'm doing.

M

mihaialexe12

Participant

It was made very clear by many posts from other people as well that factory resetting does nothing to fix the issue, and i can also confirm this myself.

Participant

Obviously whatever this toggle setting is doing, is persisting some kind of a setting to storage. How can they not reset this setting back to default as part of doing a factory reset, at least at a minimum, so people can just factory reset to get it back to the way it was? Regardless of whether they know why the toggle setting itself is fixing things or not, it is unacceptable that factory reset isn't actually resetting the headset back to the way it came from the factory.

jaybdg2024

Participant

I totally agree. While factory resetting would be a minor PITA I'd GLADLY do it to get rid of this obnoxious bug. BUT for the record I personally have factory reset this numerous times out of sheer frustration both through the headset as well as the app and nothing changes. I've also mentioned that swapping out a brand new headset for a so called refurbished one should not be the fix-all. I am **bleep** with keeping mine in as pristine a condition as I can. I have no idea what a refurbished unit has gone through. While the consensus would be that it's "as good as new" I can't chance that personally for such an expensive investment. I'd this can't be resolved via software then they should do the right thing and send brand new replacements in exchange for these bugged ones. Then they could do whatever they wanted to with them. Just my 2 cents.