PTC v77 V76 broke Wifi Downstreamspeed for higher bitrates on Quest Pro, bug carried over to PTC v77

[hatsuratsu]

Wifi Downloadspeed on Quest Pro is still broken, my Quest 3 is nomal (1600mbit/s), as show in my test, all are on same network with 160mhz channelbandwidth (it does not matter if i use a wifi 6e oder wifi 7 wifi-ap/router, i have tested both, wifie 6e router and a wifi 7 router in combination with a Quest Pro in V76 and V77) ...

Already have filled a bug report in V76, nothing has changed and now the bug has carried over to V77...
Aldready contacted support in V76 PTC, they mixed it up with a WIFI 7 problem, but as described, the Wifi 7 problem is a different one.

The V76 and V77 PTC ( see here: https://communityforums.atmeta.com/t5/Announcements/v-77-PTC-Release-Thread/ba-p/1315776 )is full of people that describe the low wifi throughput on Quest Pro but there are also no replys by meta staff , also asked if meta has acknowledged the existence of the bug/behaviour --> now answer yet ...

[TomCgcmfc]

Ya, def needs a QPro fix asap imho. 

Not a big deal for me since I only use my QPro/rtx4090 with the official link cable at 900mbps Dynamic bitrate with flight/racing sims and my Q3/512Gb for everything else; standalone vr/mr and wireless PCVR with Air Link or Virtual Desktop.  I'm currently on non-ptc v76 and I'm not experiencing any Link issues that some users have reported.

[NovaFluffyhusky]

I've been in a constant back and forth with their support desk through both chat and ticket. After giving them all the logs they needed (and them asking for the same ones multiple times) this was the closest thing to an acknowledgement of a wider spread issue:

"It looks like you have been experiencing similar issues with the Meta Quest Pro V76 update, particularly with Air Link and wired Link performance. Allow me to help you.

We understand that you experiencing a repeated errors preventing stable connections, even on a wired LAN setup. Please know, the update appears to enforce a hard cap on bitrate, limiting throughput and affecting streaming quality. Also we have noted that the link-local speed is capped at ~200 Mbps, despite having much higher network capabilities."

Their fix was PTC and giving them the exact same logs I had given earlier. If they had read anything they would seen I have done both.

Mind you provided them with additional info/logs.

Video of a link local test (from both clients including packet and NIC monitoring on local PC side)

Even did their jobs for them and in the logs they keep asking for but never seem to read:

Bitrate and Performance Issues:

Log Path:  /Diagnostics/OculusServiceLogs/Service_2025-05-03_15.58.38.txt

Dynamic bitrate summaries:

 /Diagnostics/OculusServiceLogs/Service_2025-05-03_15.58.38.txt

Hard cap enforced:

Forcing max bitrate to 105000000

Dynamic bitrate configuration confirms:

min_dynamic_bitrate: 10, static_bitrate: 10, max_dynamic_bitrate: 170

Plus in other logs more indicating degraded video streaming or post-process pipeline failures in the headset firmware (likely driver handling) or rendering engine.

I've worked in support facing roles for a little over seven years in big tech and I haven't seen this kind of case management and dodging before. What an awful experience. 

[falsk]

Yeah, I'm not buying another meta product in my life. Quest Pro was the first and last thing I bought from this company lmao. The fact that this issue was reported in V76 PTC and still pushed to live and even exist in V77 PTC is insane. I mean, maybe there's too few people experiencing this issue, am I right? :))People experiencing this issue

[hatsuratsu]

@metaich you don't trust/like openspeedtest (that is sometimes a bit odd) here are results from iperf3 with 8 parallel streams, both on quest pro vs quest 3, same results on same network, same postion to wifi router with 160mhz channelbandwidth, same on PTV V77, Quest Pro Wifi-throughput is crippled but ONLY on QUEST PRO, Quest 3 behaves "normal" ....  (edit: added image where quest 3 als run with -R (reverse option -->Server sending data, same results))

 

 

[ghost.605794]

They are not concerned about products that have already been discontinued.

Quest 3 is also experiencing issues with Quest Links not working, and Meta seems to have rushed the Android 14 update.

I will update to the stable version and will not update my headset any further.

[hatsuratsu]

@ghost.605794 "I will update to the stable version and will not update my headset any further."

meta forces updates after some time, even if you don't want it install these updates. you probably have to intervene via adb ( disable com.oculus.updater via packagemanager  ).

my quest pro is still under warranty for a short period of time, so it is not even 2 years old ... so sad that people have to go this way ...

[bowow]

I am convinced at this point that their support is just AI-generated responses designed to waste the customer's time until they give up and go away.  I have gone full circle with them so many times now I'm just completely irritated.  I explain everything in the clearest, plainest language possible.  They waste my time and tell me to troubleshoot my network multiple times, even though I already pointed out this is affecting multiple people on multiple networks, and a headset on older software works fine on the same network.  I explain everything again.  They ask if I updated to V76 already, even though I extremely plainly stated what version CAUSED the problem (V76...) in the first sentence and multiple times in every response.  So, I explain everything AGAIN.  They say they want to send me a replacement, even though I already explained a replacement cannot possibly resolve an issue that exists in the OS software since the replacement will run the same software.  So I explain this again to them.  Now for the 2nd time they tell me they're looking into it.

Last time they did this, after a week or two they just sent me the same generic troubleshooting steps that don't and can't possibly fix the problem, and started the same tedious and circuitous loop of AI-generated time-wasting messages.  Even after I very clearly explained that there is nothing I can possibly do on my end to fix the problem that Meta introduced in V76 because I am not a Meta developer working on Horizon OS, I don't have access to the source code of Horizon OS, and therefore I cannot fix the problem that exists within the code of Horizon OS.

I have asked them numerous times to escalate this issue to someone that can understand the problem, but to no avail.  Genuinely the least helpful support I have ever experienced from a large company.  And that includes even Comcast.

[Bobby_Vtb]

Oof it’s still happening in V77 PTC?

hopefully they’ll patch it on the full release or else meta’s firmware is a joke on another level