Forum Discussion

BruceArthurWayne's avatar
BruceArthurWayne
MHCP Member
1 month ago

Meta AI & Accessibility Features Still Missing in the UK on Quest – Anyone Else?

Hi everyone,

 

I wanted to ask if anyone else in the UK is experiencing delays with Meta AI and accessibility features on Quest devices.

 

These features seem to have been rolling out for quite a while, but they still don’t appear to be fully available in the UK.

 

For example:

 

- Meta AI is still not available

- Accessibility features like dictation (UK version) are missing

- Accessibility tools do not seem widely available

 

I’m also experiencing some issues on Quest OS v72 (2.1 interface):

 

- I previously had Navigator (v87)

- After an update Navigator disappeared

- I still do not have access to the new interface

 

So currently I seem to have:

- No Meta AI

- Missing accessibility features

- Navigator removed

- No access to the new interface

 

Is this still region locked for the UK or part of a slow rollout?

 

Has anyone else in the UK experienced Navigator disappearing after updates?

 

It would be great to hear from other UK Quest users to see if this is a wider issue.

2 Replies

  • steve_40's avatar
    steve_40
    Honored Visionary

    How Meta Rolls Out Quest Updates

    1. Staged, Gradual Rollouts (the default)

    Meta does not release updates to all Quest headsets simultaneously. Instead, they use a phased rollout model:

    • Updates are released to a small percentage of users first.
    • If no major issues appear, the rollout expands to more devices.
    • The full rollout can take days or even weeks.


    This applies to Quest 2, Quest 3, Quest Pro, and older models. This is confirmed directly by Meta's own release FAQ, which explains that updates are intentionally staggered to ensure stability.


    2. Why Meta Uses Staged Rollouts

    Meta’s approach is similar to how large-scale OS updates work on phones and consoles:

    • Catches bugs early before they affect everyone
    • Allows real‑world testing on a subset of devices
    • Manages server load during large updates
    • Prevents mass outages if something goes wrong


    This is why you may see people online reporting new features before they appear on your headset.


    3. Automatic vs. Manual Updates

    Automatic (default): Your Quest checks for updates periodically and installs them when available to your rollout group.

    Manual (newer option): Since 2024, Meta provides a Meta Quest Software Update Tool that lets you manually install the latest system version via USB if you don't want to wait for the staged rollout. This tool uses WebUSB and works on Windows, Mac, Linux, ChromeOS, and Android. This is especially useful if:

    • You're stuck on an older version
    • You want new features immediately
    • Your region is receiving updates later than others


    4. Regional Differences

    Rollouts can vary by:

    • Country
    • Device model
    • Whether you're in a test cohort
    • Regulatory requirements


    This is why some features (like Meta AI or accessibility tools) may appear in the US before the UK, EU, or Australia.


    5. How Long Does a Rollout Usually Take?

    Typical rollout duration:

    • 3–14 days for minor updates
    • 1–3 weeks for major OS releases


    But Meta does not publish exact schedules.


    6. How to Tell If You're in the Rollout Yet

    You can check manually:

    • Settings>General>Software Update


    If it says "You're up to date" but others have a newer version, you're simply not in the current rollout wave yet.


    7. If You Want Updates Immediately

    You can use the Meta Quest Software Update Tool to sideload the latest official update package. This bypasses the waiting period but still installs the official Meta OS.

    Why You Can Have the Latest Build but Still Miss Features

    1. Meta separates OS updates from feature activation

    This is the part most people don't realize:

    • The OS version and the feature availability are not the same thing.
    • Meta often ships the code for new features inside the update, but the features themselves are controlled by server‑side flags.


     That means:

    • Your headset can be fully updated
    • The feature is technically installed
    • But Meta hasn't "switched it on" for your account or region yet


    This is why two people on the exact same build can have different features.


    2. Regional restrictions and staged feature activation

    Some features roll out:

    • Only in the US first
    • Only to certain languages
    • Only to certain age groups or account types
    • Only to a percentage of users at a time


    3. A/B testing and "cohort" experiments

    Meta frequently runs experiments where:

    • Group A gets the feature
    • Group B doesn't
    • Group C gets a slightly different version


    This is extremely common with Meta AI, passthrough improvements, and UI changes. You can be on the newest build and still be in the "not yet" cohort.


    4. Account‑level flags, not device‑level

    Some features are tied to:

    • Your Meta account
    • Your region settings
    • Your age verification
    • Your language
    • Your privacy settings


    So even if you update your device manually, the server may still say: "This account isn't enabled for Feature X yet."


    What this means for you

    • Even with the newest build, you're not guaranteed to get the features Meta advertised.
    • This isn't a bug - it's how Meta intentionally structures their rollout system.
    • It's confusing, and honestly, Meta could communicate this much more clearly.

     

    P.S. If you'd like a more humorous take on the rollouts, you can read my "Grand Chaotic Meta Feature Lottery Theory" here:

    Meta Quest 3 Software Version Post Fix Questions | Meta Community Forums - 1367842