PTC v53 Release Megathread

Its all over reddit.  v53 is a buggy mess.  Please encourage the dev team to push for a v51 general release.  

The issue here is so many of us on the PTC got into it with the idea that we could roll back to a stable version as stated in the TOS.  While its understandable that this was an issue with the Android update between v50 and v51, this one time Meta made a mistake by releasing v53 on the PTC BEFORE providing a stable roll back build.  That was absolutly an error and someone failed to take that into consideration. 

Remember , those of us on the PTC program are your more indepth testers and more advanced users than your typical EU.  Thus we provide Meta with a service in the form of telemetry and feed back.  This has soured my taste for the PTC program.  

AGAIN v50 to v51 is understandable, there was no excuse not to wait until v51 official was out before pushing v53 PTC.  Heck, I didnt even know i was still in the PTC program when this updated and ruined my expereince and that's not good 😕

I recently tried to manually downgrade to v51 and that didn't work either. nothing crashed, my Quest 2 works as before and with the exact same problems, just, no downgrades. I expected that since it was an android 12/android12 rollback it would work, but the firmware flash reached 20%, the device rebooted and stayed on v53. This really puzzles me because at this point I have reason to fear that maybe I won't get the rollback to v51 even when it's officially released and even though I'm out of the ptc. please can you get information from the development  team about when v51 will be officially released and if it will actually be installed on devices that came out of ptc and come from v53? 

now the omelette is done so being clear and sincere would only help to mitigate the situation a little.

Well, as you may guess, unparinig and re-pairing the controllers didn't help.

I was desperate to try factory reset, but just occasionally I found what was causing the problems with my controllers (and probably why it's as rare). And the reason is... Wi-Fi router!

Usually I don't use Wi-Fi and turn it on just for the Quest Pro when using it standalone and then turn it off when I'm done. And today I forgot to turn it on when put my headset. I noticed that the controllers were working correctly. I turned the Wi-Fi in my router - and the problem came back - regular frequent controller disappearing. I googled a bit and found out that Quest Pro uses Wi-Fi to track 6DoF controllers. If you turn the wi-fi off in the headset itself - you'll get only 3DoF from the controllers. So, it seems that my particular Wi-Fi settings somehow interfere the headset-controllers connection with this bloody update.

My router is TP-Link Archer C20 and I usually use 5GHz network for Quest Pro. I turned it off and tried the 2.4GHz network - the headset gave me a notification that "DFS channel detected" and redirected me to a weblink stating that touch pro controllers may not work correctly with Quest 2 with a DFS netrowk (come on, I'm not using touch pro controllers with a Quest 2, I'm using it with the Quest Pro which should work like a Swiss watch!). But using the 2.4GHz network seems solving the problem or at least mitigating it. I had only a single controller lost in 30 minutes - compared to a couple of reconnections in a minute it's a win.

I hope that Ryanality will give this info to the dev team and I'm open to provide any specific details of my Wi-Fi settings. I'm also looking forward to advice from them what setting I should change to be able to use the 5GHz network again.

This is definitely the issue with v53 update and it seems it's connected to the issues people have with Wi-Fi 6 networks. I guess I'm done with these public tests, it's better to use a stable firmware instead of being a free QA tester. But by quiting the PTC I guess I won't be able to get rid of this buggy v53 soon...

And I agree with the other guys - the level of the support provided for PTC participants is disappointing. I had no response to the bug I reported to support, and I found no assistance from Meta representatives here as well. I'm not even sure that the info we share here gets to the dev team. So, when I get a stable firmware, I see no point in participating the PTC further.

Yeah, there are problems, but that's what a public beta is all about. Only use the PTC if you know what you are getting yourself into.

All this getting upset over no immediate tech support for these issues is ridiculous considering we are the ones letting them know about these  issues. They have to now look at this feedback and start fixing the issues. It's not like they already knew what we were all going to experience ahead of time, if they knew that, there would be no need for a public beta.

Lying down mode also will not turn off for me unless the headset is restarted.

Hi Ryanality 

Any chance laying down mode will come to quest 1 even though it won't get v53?

As it's an acessibilty option it wouldn't require more performance. 

As I only use my quest 1 for movie watching now the laying down would be very useful.

I have a Meta Quest Pro and its Quest Pro controllers, and with v53 I am continuing to face the issue where after some period of time (possibly related to when the headset sleeps), the controllers will cease to connect with the headset. In the mobile app, they appear as connected, and I can see their battery levels and even unpair/repair them. But in the headset, both controllers will appear as "Not Connected". If I turn off WiFi within the headset, then the controllers suddenly reappear, but they have question marks next to their status icons in the Quick Settings menu, and they also only have 3DoF tracking, and as soon as I reenable WiFi they disappear again. The only way I can resolve this is to do a full factory reset, which only works temporarily until they stop working again (in previous updates, they stopped working after a single restart, but today I was able to restart my headset several times before they stopped working). I have seen that others have experienced this issue, but seeing that v51 is now starting to roll out, I am wondering if any progress has been made to identify the root cause of this issue and whether any fixes are available. Otherwise, I effectively no longer want to use the Quest Pro because I know I'll have to do a factory reset and redownload the applications I want every time I want to use it. 

My problem with 53 and my Pro is that my Wi-Fi connection tanks after being connected for a while. Starts out strong when I disconnect then reconnect, sometimes showing 1200, but after a while it will go down to under 200, at which point streaming content is horrible.

Also my touch controllers, keep overheating usually when I've set them down beside me on the couch. They give the overheating warning, then actually shut down after a while.

Another interesting thing is with 51 or maybe 50, my left touch pro started showing white instead of green when fully charged. Now with v53, it's back to green like it's supposed to be when fully charged.

Ryanality

Bugs

1. When starting the headset up the music that plays when creating guardian continued to play while in home enviroment (multiple Times)

2. Internet disconnecting when headset is put down while downloading/installling large games 

3. Controllers not always connecting as quick as they should this has happened a few times

4. Shutdown menu needs to be made smaller it is ridiculously oversized

Expected Feature

I expected with a full system change to see some big requested changes and think most users would agree that we need some way to remove uninstalled apps from the app library screen and a way to organise our content into sections like a third party launcher would do the app library should really have similar features to a standard android system with the ability to create seperate pages for different types of content. (or the ability to create new tabs and move icons to that tab for categorization) the current app library is missing so much in the way of features

(Sure this has been mentioned multiple times in the past and ignored by the devs as a feature requested by the end user)

After PTC v53, I need restart headset to use Link/Air Link frequently.