Skip to main content
BobbyVtb
BobbyVtb
Participant
April 14, 2025
Solved

After V76 release, Quest pro's download speed is capped to 200Mbps

  • April 14, 2025
  • 100 replies
  • 17135 views

So after V76 update it seems the download speed is capped around 200Mbps and 6Ghz connection is unstable as well

I've tested on both Wifi 6 router and Wifi 6e routers and both performed simular result

I've also done some LAN connection test from my PC to Quest Pro

On the picture is side by side comparison of Quest Pro V76 and iPhone 15 Pro max connecting to my PC via a Wifi6e router with 1Gbps LAN port under the same internet environment

Meta please fix
Quest Pro Lan Connection speed
IPhone 15 Pro Max Lan Connection speed

      Best answer by TomCgcmfc

      Apparently Update v78.1027 Build508494848.7050.340 Fixes Download Issues.  Looking forward to getting this in the near future.  I believe it's still PTC right now.

      https://www.reddit.com/r/QuestPro/comments/1l8fukd/update_v781027_build5084948487050340_fixes/

       

      100 replies

      Show previous replies
      bowow
      Inspiring
      June 5, 2025

      Just got an update to v78.1027 Build 5084948.6340.340.  Incredibly, the issue is still not fixed.  If the bug makes it out of PTC yet again, it will mark 3 major versions in a row where this terrible experience-ruining bug has not been resolved.  At that point, I think we will be able to officially declare that Meta has abandoned all support for the Quest Pro.

        TheShrekster
        Inspiring
        June 5, 2025

        That's very concerning. Is it still an issue on Quest 2?

        bowow
        Inspiring
        June 5, 2025

        I don't have a Quest 2.  Someone with one in PTC should replicate the local speed test and post pictures here if it's an issue on that headset as well.

        freejack
        Participant
        June 5, 2025

        It's just negligence at this point.  Terrible way to treat your customers who purchased a premium product.

          lrussell887
          New Participant
          June 9, 2025

          I opened my own support ticket with Meta regarding this issue and received this reply a few days ago:

          Thank you for reaching out and sharing your experience. I understand how important smooth wireless performance is for your setup, and I truly appreciate your patience.

          Our team is actively reviewing reports related to Wi-Fi performance changes since Horizon OS v76. While I don’t have an exact timeline for a fix, I want to provide some troubleshooting steps that may help improve stability in the meantime:

          [ General troubleshooting steps]

          ...

          I also want to acknowledge the additional concerns you've mentioned, including audio performance and the IPD adjustment screen behavior. Your feedback is incredibly valuable, and I’ve shared it with our team for further review.

          It looks like it is at least being acknowledged, so hopefully something will come of this soon.

            Lexiibug
            Participant
            June 9, 2025

            Headsets have been effectively crippled by a forced OTA update for three major versions now. Seriously Meta, get off your a**es and fix it. Your consistent bricking of user's devices is approaching class action levels.

              TomCgcmfc
              Honored Contributor
              June 10, 2025

              Earlier today I got another non-ptc v77.1027 update (including firmware) on both my Q3 and QPro.  I now get that pretty multi-colored panel when Link or Air Link starts up, followed very quickly to the usual meta-link grided void. 

              All seems to be working fine but my QPro is still wireless bitrate limited to ~240-280mbps.  No big deal for me since I only use my QPro with a Link cable and it easily gets 750-800mbps dynamic bitrate.  Still, something that meta needs to fix asap imho.  

              No bitrate limiting issues with my Q3 though. 

              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
                TomCgcmfcAnswer
                Honored Contributor
                June 11, 2025

                Apparently Update v78.1027 Build508494848.7050.340 Fixes Download Issues.  Looking forward to getting this in the near future.  I believe it's still PTC right now.

                https://www.reddit.com/r/QuestPro/comments/1l8fukd/update_v781027_build5084948487050340_fixes/

                 

                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
                  bowow
                  Inspiring
                  June 11, 2025

                  I can confirm it is fixed in the latest V78 PTC update from today ( v78.1028 Build 5084948.7050.340 ).  I am very happy Meta finally fixed this Wi-Fi speed issue on the Quest Pro!

                  The random rainbow decoding artifacts at high resolutions that have been there since ~V59 and got noticeably worse with V77 are still there though (presents as a thin diagonal line full of rainbowy pixels, or occasionally rainbowy pixel lines at the top of the screen).  Hopefully that's next on the fix list!

                    TomCgcmfc
                    Honored Contributor
                    June 11, 2025

                    bowow  and lrussell887  Thanks for confirming this mates.  I look forward to getting that version in the future when it comes out of PTC.  I try to avoid all PTC/Beta's and currently this isn't an issue for me since I only use my QPro/rtx4090 with flight/racing sims using the official link cable connected to my z790mb usb3.2 gen2 type-c port at 900mbps max dynamic bitrate (usually reports ~750-800mbps).  Still, good to hear that Meta has found a fix for something that never should have been broken to begin with imho. 

                    bowow  I haven't noticed any artifacts with my QPro for quite a while now (since ~v71-74).  I mainly use it with demanding flight sims like msfs2020 using a Link cable.  Most people I've heard complain about this recently are playing PCVR wireless with Virtual Desktop.  Of course if you post this issue on Reddit you're bound to get a lot of kiddies saying that they have Exactly the same problem, lol!  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
                      bowow
                      Inspiring
                      June 11, 2025

                      Correct, it happens mostly with Virtual Desktop.  You can make the artifacts happen with Steam Link too if you edit the config files to make it render at a high resolution like the resolution I use with Virtual Desktop.  My understanding is these artifacts initially appeared along with the update that boosted the headset's clock rates from well over a year ago.  They've just gotten more noticeable with the new UI update is all.

                        lrussell887
                        New Participant
                        June 11, 2025

                        I can also confirm that the v78.1028 PTC has resolved the issue.

                          ghost605794
                          Participant
                          June 11, 2025

                          I haven't gotten my V78 PTC yet, but I'm glad to hear it's finally resolved.
                          I registered with PTC, but I'm still stuck on V77.

                            dhammans
                            New Participant
                            June 25, 2025

                            I meant to post this a while ago, apologies for not getting this information out there sooner --

                             

                            If you are on v77 or v78.1027 or below and are experiencing this issue a workaround is to statically define the IP address of your headset. The underlying Android OS has a lot of functionality built into it for being a mobile phone -- even though it's a WiFi headset it is still doing a lot of things at the OS level to look for WiFi networks and offload cellular data.

                            If you statically assign an IP to the headset Android is smart enough to know that it won't be able to hop networks and it spends a lot less time (or none) scanning for available SSIDs to connect to.

                            You would need an IP address, 24 bit netmask (presumably), gateway, and DNS for this to work. I suggest 8.8.8.8 and 8.8.4.4 -- I have noticed something about Starlink DNS that the headset didn't like but didn't dig deeply enough to see what it was.

                            If you want to see this in action, bring up an ADB shell on the headset and use the command "dumpsys wifi" which will give you recent logging output from various sources about the WiFi interface. You'll see what I'm talking about.

                            In general if you are doing PCVR I recommend that you run the headset with a static IP address anyway. You will generally see better performance in Airlink, and be a little more impervious to broken Meta updates...

                            Terms & ConditionsAccessibility statement