Meta Quest v55 Release Notes

Hi, I would really appreciate if I could use my headset with Airlink/Virtual Desktop without experiencing lag spikes every other time I turn my head. Any chance you could stop dragging your feet with this rollout??

Before anyone tells me to just join PTC, I'm not messing with that stuff again. I *just* opted out of the PTC several days ago because I was informed that it wouldn't require a factory reset since the official firmware has caught up. That turned out to be BS, and for whatever reason none of my settings or appdata saved to the cloud so I lost *everything*.

Is there a rollback on this update cause looks like not so many people haven't got update yet. 

Gosh, you lot are impatient. It took a month until I got the last release from when it was announced. You should all consider yourselves lucky that this company releases so often. Some would do a release once a quarter. On the other hand, I feel the pain of the developers having such a short release cycle. I remember working for a company with a 3-month release cycle. It was relentless. Imagine, 12 weeks... 2-4 weeks design time, 4 weeks in-house testing... 4 weeks development time! No time to fix bugs! Unless there are two or three teams with overlapping development cycles it's no wonder there are so many bugs in each release. Don't blame the coders... this is a business issue. I'd be much happier having a longer release cycle with fewer bugs than short release cycles and giving the business a bad rep with new bugs in existing features every release. Sort yourselves out, Meta... it's better to have a good reputation for good stable software than ploughing in new features at the risk of a bad reputation for bug-ridden releases.

so turning off PTC and hitting update in my headset forced a factory reset with no warning and rolled me back to v54 with no option to update. guess I'm going back on PTC again and never disabling it 

Hey everyone, I've checked back in with the team. There's a release planned this week for PTC which will include a new build of v55. Assuming everything goes as planned, you should see it on Wednesday if you're on PTC. If you do get that build, please let us know how it goes! There are a couple fixes in that build, though I don't believe it includes the fix for the Link artifacts issue that some people have noted. That's still being worked on.

I'm honestly very confused by the firmware builds. So you can have major versions like v54, v55, etc but there are individual builds that aren't listed anywhere except in your headset/mobile app settings? Or am I missing a page that actually lists the exact build numbers? I feel like in trying to keep things simple by reducing the info we're shown it actually becomes more confusing but I digress.

In any case, I was previously on the PTC v55 release but only got a few small UI updates and not the rest of the features listed. I disabled PTC assuming I'd be able to get a more stable public release that would get me the new features and instead got reset to v54 with no option to update to the public release. Now after going through the factory reset and then reenabling PTC I'm back on v55 but this time I did get the new features (had to enable direct touch and restart to get browser multitouch while this feature never worked before). My headset says I'm on 55.0.0.111.713.486310262, runtime version 55.0.0.111.713.486310276. Does that sound right? Is this the same version that some people have received on the normal public channel or am I still slightly behind? And I suppose with this new build coming wednesday I'll then be ahead of the stable release again and I should just stay on PTC indefinitely? 

just to clarify and help those who are rightly going to the asylum.
the fact that the release of v55 was announced on June 21st DOES NOT MEAN THAT IT WILL BE COMING TO YOUR DEVICES NOW.
Indeed, at best you will probably receive it towards mid-July, at worst towards the end of the month.
this is always the case with Meta for the wave rollout policy.
Having said that, it is obvious that you are maddened by v54 so if you want v55 right now the only way to get it is to be part of the ptc. then it is advisable to exit the ptc at the beginning of August when it will be much more probable that the ptc version that we will have on the devices will correspond to the stable one and this will not cause the restoration of the factory settings and the rollback.

I have opted into the PTC and restarted my headset/left it plugged in with the Link cable on my table and still no update to V55. Since the "stable" update is taking so long to get to my headset I have opted into the PTC, only to still be unable to download it... 

I too have issues with remote desktop having spikes but wasn't sure if it was unique to my setup 

Have we had any developers release updates to take advantage of the higher clocks? I know walkabout mini golf was increasing resolution but I've not seen anything happen yet?

Hello Ryan,

I'm super new to this community and reason for me being here is i can't use my meta pro headset since the update. I will explain, and just to let you know i am fully capable to pretty much do anything necessary to fix the problem. I'm am sorry for busting up in here like this but I am without any other options it seems. When the battery runs low one of my eyes will still project the game I'm playing and then it completely died, upon charging the device and restarting the headset the controllers no longer would respond or pair. I had the blue and white lights during the pairing and everything still the headset didn't pair. So, I factory reset it and i realized there are two menu's from which you can factory reset one you have to enter a button combination to access, which appeared to me as a default android recovery menu. I don't know if maybe this was the problem from the beginning that i reset it with the wrong menu? But either way I get the same result and setup process, which I cannot pass because at first my device couldn't be found by entering the pairing code. Now I have been able to get the device to be found but it is saying, Can't Pair Yet you can continue pairing after your headset updates. Begin updating your device, then put it on its charging dock. It will play a sound when it's ready to pair.

Now all of this mind you i have to do with no controllers because they will not pair in the beginning of the setup.

and my headset is saying that it is in pairing mode and has the code on screen saying its done updating and ready to go.

Please help I cant use it at all. I've found firmware versions for the quest1 and 2 but i wasn't sure they were the same and even so they weren't a high enough update to even use because i was on the latest. i am totally capable of running adb commands and updating it manually as i assume this would be my best option... please if there is anything you can do to help I would be greatly appreciative and would help you guys anyway i could.

Sincerely,

Donovan P Darroh Jr.

Networking and Security Degree From ITT-Tech with 20 years experience with all things Tech.