Quest 2 v78.1030 build 5163765.9120.150 105MB
V78.1030 will not install over v78.1027. Settings shows v78.1030 available. Ater downloading and restarting version unchanged from v78.1027 and software up to date. Updating via software update too...
Forum Discussion
Hi NomadsAnIsland! Thank you for bringing this issue to our attention.
We understand that it can be confusing to update your software only to find out that you're still on the older version, even though your device says it's up to date.
It's important to note that our software updates aren't released to all users at the same time. They are rolled out in phases to ensure a smoother transition and allow us to monitor for any issues before wider distribution. This phased rollout helps minimize the impact of potential bugs or problems that might arise with a new update.
With that say, we would still like for you to submit a bug report so that we can better understand the issue and review it with our team.
To submit a bug report, you need to:
- Open the Meta Horizon mobile app on your phone.
- Tap your avatar picture at the bottom, then tap in the top right.
- Scroll down to Support, then tap Report an issue.
- Tap Report a problem, then type an explanation where prompted.
We hope that this was helpful and please be sure to check back on the Forum frequently for any news and updates regarding this issue. If you have any other questions or concerns, please do not hesitate to reach back out to us, we are always more than happy to help our VR family!
“We hope this is helpful” eeerm, how could that possibly be helpful? You haven’t offered any help. If this so-called Meta “Community Manger” reply isn’t an A.I. bot then honestly you should be ashamed of yourself.NomadsAnIsland HAS reported the issue & given all relevant details. All you are doing is, asking them to submit the same information again. How is that helpful, at all? Don’t you work at Meta? Can’t you flag the issue to the relevant support team yourself? News flash - THOUSANDS OF YOUR USERS WILL BE AFFECTED BY THIS EXACT SAME ISSUE. Your update code is bunk. You guys seemingly don’t understand how operating systems work.
MetaStoreHelp this issue has nothing to do with updates that are rolled out gradually.
The headset doesn't tell me an update is available before it is rolled out to me.
NomadsAnIsland 78.1030 and 78.1027 have both build 5163765.9120.150 ??
I can’t speak for Nomad but yes - that build number matches my headset, on v 78.1027. It detected as available, downloaded and “installed” .1030 earlier today, only to restart, then report being on 78.1027 still, with now no update available and the same OS last update date for me of 8th July. Same build number, too. The web link to Meta’s update notes is beyond pointless, just mixed up version numbers & no note(s) even published for .1030. Why do we even need a build number? These guys are jokers, it’s an excellent troll, really.
you should possibly work for Meta support as it was obvious to you that the first couple paragraphs of the support response to Nomad were pointless word salad. The fact that they are so cautious about rolling out feature updates speaks volumes to me… Imagine having so little confidence in what you’re doing that even just using the PTC channel to test isn’t enough, instead you have to drip feed even cosmetic changes to your users over actually many months rather than just testing things properly then issuing an update once it’s ready. Sad.
that build number matches my headset, on v 78.1027. It detected as available, downloaded and “installed” .1030 earlier today, only to restart, then report being on 78.1027 still, with now no update available and the same OS last update date for me of 8th July
Yes, and according to the size (105 MB) this update was exactly the same as the 78.1028 update.
