PTC v76 Release Thread

hatsuratsu They spend their billions to the following and more:

• wearables like rayban, evolved product line this year
• expanding Quest ecosystem and shop
• vr capable glasses codename Orion
• aritifical intelligence in every aspect
• research in vr/ar/mr/xr fields
• funding vr pioneers

And yes, their vision of the "metaverse", as known by consumers by Horizon Worlds.
The only "income" by that... the shop (heared of 2 billion last year?).

Do you really think they earn only one cent by selling Quests at this affordable price?
I can answer that: No, they pay on top of each device they're selling!

Does that makes it sorry for the bad community service?
No, but it explains where the billions go.

Discussion with IA Grok on the issue.
New Display Port ALT MODE???
Why DisplayPort Alternate Mode might be involved

Increased complexity: • The addition of DisplayPort Alternate Mode introduces a new way for the Quest to communicate with the PC, treating it as a DisplayPort display in addition to its usual role as a VR headset via Quest Link. This dual functionality can complicate the management of USB-C connections, drivers, and communication protocols. • If the software (Horizon OS or the Oculus PC app) is not fully optimized to handle this mode, it can lead to instabilities, such as connection failures, slowdowns, or crashes.

Hardware and software compatibility: • DisplayPort Alternate Mode requires that the PC, USB-C cable, and headset all support this standard. If a single component (e.g., a non-DisplayPort-compatible USB-C port or a misconfigured GPU driver) isn't working properly, it can disrupt Quest Link, even for users who aren't actively using this mode. Nvidia's 5000-series GPUs, mentioned in some reports on X, appear to be particularly affected by compatibility issues with v76, which could be exacerbated by the new mode.
Couldn't LINK's problems stem from this new v76 feature?

According to my research, this mode transforms the (compatible) USB-C cable into DisplayPort?
So there's no longer any H264 or H265 compression between the PC and the Quest?
So the headset receives an uncompressed stream from the PC via this complex mode? The PC, the cable, and the Quest must be compatible, which is the case for the headset with the V76.
If this is indeed misconfigured in the headset software and in the PC's Quest Link program, it can quickly create a lot of problems.

EDIT : I just tried a less powerful USB-A port with a USB-C adapter. Quest Link tells me I'm not using USB 3.0, but strangely, I no longer have any problems. The image quality isn't great, but I can race in Iracing.

Badstar25 No, that's a misunderstanding of your's...
The way discussed with "IA Grok", is from Headset to PC, not the other way round, to realize PCVR.

The DP alternate Mode is for a better streming experience of content of the headset.
Before that, only streaming per internet was possible... HMD > iNet > local PC.
With the addition of the DP alternate Mode... HMD > local PC

Does anyone know if the sideloading issue is related to Android 14? Do we need to change something in how the builds are done, or is this just something caused by Meta breaking sideloading? I've figured out that if the apk was previously uploaded to their distribution channels (using Meta Quest Developer Hub)  and the app is approved and then sideloading through adb using adb directly or sidequest, it seems to work, but it was not the same version that is crashing for me. 

This is not happening just in PTC, it is happening in the last update they did (v76).

Any hints?

EDIT: In my case, I had to build the apk using API Level 32 (Android 12) as a target API.   

Somewhere during the numerous v76.1023 updates in the past few days a stunning new feature was added.

When launching an now instead of the three white dots on black we are treated to an awesome void style animated scene with inspirational music/tones.

Simply amazing! I can't imagine how many devopment and testing hours were put into this instead of fixing bugs.

Quest 2 headset updated to v76.1024. Despite what it says there are no releas notes for this version.

Do not update to v76 or v77

To Meta: It was incredibly irresponsible to greenlight a PTC in this state. I realize it was a big jump to Android version 14, and there's more work to be done, but there are so many core features that are completely non-functional: Quest Pro is completely ****** for a lot of users because of the 200 Mbps bug, Wifi 7 locking up is also completely unacceptable, among many other bugs.

What's worse is that v77 barely fixes any of this. The core bugs mentioned above are not fixed at all. It's been more than a month!

I hate this "move fast break things" mentality; it just leads to people getting frustrated with their headsets, putting them down, and never picking them back up.

Nogib  you should be able to get V76 or 77 using this method.

jesus_vbw sideloading was partially broken in v74 (which was still Android 11) and they eventually fixed it before public release. Might be the case here too.