Honored Contributor

PTC v51 Release Megathread Quest 2 and Quest Pro

83 replies
22977 views

The Public Test Channel (PTC) for Quest v51 is starting to roll out now. Exciting news for Meta Quest Pro users out there, we’re now opening sign-ups for Meta Quest Pro PTC. We’d like to thank everyone for all your feedback over the past versions and are thrilled to open the Quest PTC for even more users. For anyone with a Meta Quest 2 or Meta Quest Pro that would like to join the PTC, check out our directions on the thread here or our support page article on PTC.

Let's use this thread for collecting feedback on v51. Share your impressions and let us know if you see any issues. Please make sure to also send in bug reports along with posting here if you notice anything going wrong.

Thanks to everyone testing out PTC and sharing your feedback! We appreciate your help testing out the core functionality of software as we develop!

ptc

Show previous replies

S

Stugabaranda

Up and Coming

Hi, I have disabled the ptc through the meta mobile app. I was warned by the app that by disabling the ptc I would have a factory reset and a downgrade to the latest official firmware released to the public. All of this is exactly what I want.
since after disabling the ptc I did a factory reset but I still find myself with Android 12L could someone kindly explain to me if there is a wait for the downgrade and which version of firmware, operating system and runtime I will have not doing more part of the ptc?

Meta Quest 2 256GB, GC Nvidia GeForce RTX 3060, Intel 12th Gen Intel i5-12400F, 16Gb RAM, Windows 11 home 22H2. Connected with dedicated router via ethernet cat 6 with pc and to Quest 2 on wifi 5 ch 36

Pandages

Up and Coming

Attempted to file a bug report on this issue already but haven't received contact or confirmation.

PTC v51 has made my Quest Pro functionally unusable: the Touch Pro controllers Will not communicate with the Quest Pro at all, unless I disable WiFi. I can't even see their battery state.

When I disable WiFi, the controllers connect immediately, BUT, the controllers track very far from aligned with my motions, practically unusable.

There is no way to revert from v51 to v50.

I've performed all the troubleshooting steps recommended.

1) reboot headset

2) re-paired controllers

3) factory reset controllers

4) factory reset headset. This TEMPORARILY fixes the issue until the controllers are left idle (say while the controllers are charging or the user is sleeping, I can't be asked to keep them awake 24/7 as that would be absurd.)

5) contact support. Did not receive my call at the scheduled time, received an apology email later. Also attempted to contact via Twitter and Reddit. No replies.

My $1500 headset is functionally a paperweight because I use it exclusively over Link. And controllers support is mandatory for Link. Hand tracking doesn't work.

without having a way to revert to an older version, I have no way to use my extremely expensive unit (for which I paid the original $1500 MSRP on the day it was announced).

edit: sorry I'm exhausted from fighting with this for the past 2 days. I'm pretty emotional as I'm trying to explain the problem and my experience.

S

Stugabaranda

Up and Coming

In theory, disabling PTC Meta should automatically factory reset and downgrade your device to the latest officially released public version (this is clearly written in the pop-up that appears when you disable ptc from meta mobile app ) I am arguing with meta support service because I want rollback as expected. For now they first tried to convince me that v51 is official and not PTC (so no rollback), now they are saying that the official version is v50, while on the Meta site in the release notes article it says that the latest official version is even v49 dated January 19, 2023, not even v50.
First they apologized saying that on the Italian site the release notes article could not be updated, now they are accusing me of probably having a pc with a browser with cache and cookies to clean up which are the reasons why I don't see correctly the web page...
at this point if someone kindly English or US could check the release notes what they say, I would really appreciate it. The fact is that I am still with v51 and Android 12 despite having left the PTC, and it seems that they have no intention of making me go back despite what is written on their own official channels. Unbelievable stuff!

Meta Quest 2 256GB, GC Nvidia GeForce RTX 3060, Intel 12th Gen Intel i5-12400F, 16Gb RAM, Windows 11 home 22H2. Connected with dedicated router via ethernet cat 6 with pc and to Quest 2 on wifi 5 ch 36

RyanalityAuthor

Honored Contributor

Hi Stugabaranda and Pandages, the PTC v51 upgrade can't be rolled back because it upgrades the device from Android 10 to Android 12 and includes several security updates as part of that upgrade. The headset won't accept a lower version to be installed since it's considered a "downgrade", even if it's PTC vs official release.

The PTC team is aware that this is causing some people trouble around the Android 12 upgrade not being compatible with certain apps, but at this time rollback isn't possible for v50 to v51. They'll be looking into this as feedback for the future.

PS. I'll look into the Italian site's release notes.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

StainlessLobster

Participant

Thank you for the update Ryan.
It's great to know that there's someone with continuity and knowledge representing Meta on these forums.

I'm sure part of the frustration you're seeing is coming from people who for the 10th time have been told to replace the batteries in the controllers and do a factory reset (or similarly irrelevant scripted answers) when your work tool isn't working as expected due to an update.

My issue with v51 is that is that it completely bricked the controller reconnection and I haven't been able to use it for the work I'm relying on it for for almost a week.

It would be super helpful to know what issues are being addressed and a rough timeframe of when we can expect a resolution (days, weeks or months?)

RyanalityAuthor

Honored Contributor

Hi! It sounds like you may be running into something similar to what Pandages mentioned a page back, but they're using a Quest Pro with Link.

I'd like to get some more details on what you're seeing to pass this along. Assuming you're on Quest 2, since you're talking about removing batteries, is this also with Link (cabled) or Air Link? What other troubleshooting steps have you tried, such as rebooting the headset or anything else...

Regarding resolution, it really speeds the process up if we can get the issue reproduced by our engineering and QA team, that way they can collect detailed logs and everything, so the more details I can give them about what's happening on your end, the better. Things that can be recreated are in general likely to get a quick fix.

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

StainlessLobster

Participant

Hi Ryan,

It’s a Quest Pro.

I used the “remove batteries” example to highlight the level of support we’re receiving from the regular support channel (when they actually do respond)

I don’t use it with Link or Airlink.

The issue is 100% reproducible and I’m in Seattle so I can drive over with it if you want QA or engineering taking a look at it.

The steps I’ve gone through include:

Full factory reset. Restores connectivity until resuming from sleep again.
Factory reset but suspended before the account linking step (to rule out the effect of any account specific application of setting)
Removed controllers using the Meta Quest companion app and re-pairing them again.
Removing the controllers but then adding them one at a time with a reboot in between (as per Meta’s support instructions)
Rebooting the headset
Factory reset using the bootloader as opposed to the companion app
Disabling hand tracking
Disabling wifi (this partially resores the connection but only while wifi is left turned off
Extending the time before suspend to use the headset at least once more for work (workaround, not fix)

V

viiqiuio

Participant

Hi Ryanality , any progress on my report?

RyanalityAuthor

Honored Contributor

Hi vii.qiuio, the team is looking into it, but they could use some more details if you're still having this trouble. Are there any specific custom environments or 2d apps that you're not able to use that I can have them test out?

Help others find great discussions and answers by adding kudos and marking solutions to your questions.

V

viiqiuio

Participant

Thanks Ryanality
I'm using sidequest and Quest app launcher.

I use sidequestVR to install custom homes in VR successfully, the home are lying in the unknown sources but not on the Settings > Personalization > Virtual Environment list.
1. 'any specific custom environments' as you can see in the picture below, none of them are available.
2. I tried with sidequest PC version over adb, nothing's wrong then. But I don't want to use a PC at all. Why won't v51 allow me to find the homes I installed already? So weird.
Now in Quest App Launcher, I can't launch any other 3D or 2D apps anymore, only flashback to Home screen.

But it all works well before I update to V51. I even run into the 'permission app(not sure about the words) keeps stop running' and then 'my Quest pro restarts automatically' issue.

Please fix these bugs asap, I'm worried that V51 is gonna ruin all my headsets, no matter Quest 2 or Pro.

T

TomCgcmfc

Honored Contributor

I got a 2nd v51 PTC update on both my Quest Pro and Oculus desktop app public beta earlier today. This included controller updates. All seems to be working fine standalone and wireless PCVR with Air Link (at 200mbps dynamic). Also seems to work fine with Link (at 500mbps bitrate). I'm not sure what this 2nd v51 PTC update did but at least it did me no harm, lol!

Fortunately I haven't had any reason to want to opt out of PTC with my QPro, I have kept my Q2 on non-beta, v50, just in case. Sorry to hear about the problems other are having opting out and rolling back (with a factory reset). It looks like the new Android 12 OS has made this difficult to do. I hope you people get a fix soon. Cheers.

i9 13900K water cooled, RTX4090, Z790 MB w/wifi6e, 64Gb 6400 ram, 2x2TB SSD, 1000W PSU, Win 11, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers

LuvinLife

Participant

I'm not sure if it is the V51 or the Q Pro controller update or both. My guardian floor level is changing even between plays of the same game. I have not changed anything else in my setup recently. I have an IR light in the area and can play without any other lights on, so it isn't lighting. Guardian recognition and controller recognition seem impacted as well. In the past I have noticed Quest builds helping or hurting the guardian recognition even when I used the Q2 controllers.

Moriarti4

Up and Coming

Think I might have found a bug..? I was playing a PCVR game via air link on my Quest Pro, I ended the game then quit out of Air Link back to the home environment and my the virtual controllers are missing..? my hands where there gripping nothing and the pointer lines where there and and controls worked but no visible controllers, I did a restart and the controllers where back as they should be..?

LuvinLife

Participant

I noticed that the other day when playing stand alone Q2 game. Started up the headset and there were just hands. Everything worked, so I thought maybe it was intentional to give more of a sense of hands vs controllers. Then restarted today and the controllers are back.

S

Stugabaranda

Up and Coming

ciao vii.qiuio , non sei solo con il problema delle case personalizzate. Se le installo tramite sidequest vr le trovo tra le fonti sconosciute ma non più tra gli ambienti virtuali e l'unico modo per trovarle c'è installandole tramite sidequest pc.
Ciao, Ryanality
Il problema non riguarda una singola o qualche abitazione in particolare ma tutte le abitazioni.
sul server discord casalingo personalizzato, infatti, il problema, sorto con l'avvento della v51, è già noto e come misura tampone si suggerisce di installare con un PC, alla vecchia maniera.

Meta Quest 2 256GB, GC Nvidia GeForce RTX 3060, Intel 12th Gen Intel i5-12400F, 16Gb RAM, Windows 11 home 22H2. Connected with dedicated router via ethernet cat 6 with pc and to Quest 2 on wifi 5 ch 36

Moriarti4

Up and Coming

Where are the release notes for this build...? this would help us to look for bugs in the software as we would have a better idea what has been changed, for example i've heard on the rumour mill that this version is meant to have a fix for the airlink wifi bug for the quest pro that has been present since the pro was released..?!

T

tanubon

Inspiring

They don't show it for PTC. 😞

LuvinLife

Participant

Wolvic VR browser seems to be impacted by this release. I can't get it to fully open, see a design screen of some sort and no way to use it. I used it prior to this release.

I am really hoping the ability to resize the main menu windows and TV section will be fixed. You are able to enlarge the actual TV app videos, but scrolling on such a small screen is a pain point.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO