Forum Discussion

madebyrsh's avatar
madebyrsh
Explorer
8 months ago

v74 update issue (volume control , pass through mode , boot sound)

Since i update v74 on my MQ3

i have so many problems 

i wonder is there anyone who has same issue

1. Cant use volume control on quick setting menu

i can change volume with MQ3 physical volume control button

but it wont show floating UI which i can see how much i turn on volume up and down Which shows with bar type UI

and also on the quick setting menu, there is slide volume control Ui but even i slide it 

it never changes volume slide when i even push physical volume button on MQ3 

 

2. cant change sometimes pass through <-> immersed mode even i click change mode button on dock and quick setting 

i tried click to change each mode only environment sound shows it react but im stucking in one mode 

 

3. Not working sometime night mode

same like number 2 issue

even i click on quick setting menu

No reaction night mode feature 

 

And i asked to meta and they said i have to do factory reset but i wanna know is there anyone who had same issue and is it really got better after factory reset?

but i heard if u do factory reset

there is more problem sometimes

as like sync controller issue or mobile horizon app sync issue

 

 

EDIT) i tried Factory reset

and after this my MQ3 OS version is v74

and it doesnt have problem that i have

volume control on quick setting menu slide UI is working when i push volume button on device

and i can see v74.1020 new update

i updated this build

and it happens same problem!

i think its bug or error of v74.1020

and i got email from Meta help center

they told me i should do delete cash of system app and safe mode to check it happens same

and turn off any experimental feature

but it still happen same problem..

#v74 #bug

 

33 Replies

  • Nohnez's avatar
    Nohnez
    Honored Guest
    8 months ago

    mate!!! I thought I was the only one with this problem!!! I don't just have one of your problems but exactly all the ones you listed.

     

    but the volume slider also works in the youtube app.

    • madebyrsh's avatar
      madebyrsh
      Explorer
      8 months ago

      Wow so we are not the only one who has same problem im from south korea and i checked other korean VR communities they also has same problem so i think it wasnt only me who has problem it all people in the world using Meta quest they have  same problem lol  and yes i also can change volume on youtube app thats why its not problem of device or other third party apps problem its ONLY meta horizon OS problem! 

       

      so i got some emails from meta quest help center and they said they need to check of this issue and to deliver technical team

      so only thing i can do is waiting their next emails

      and i think its just problem of their new OS update v74.1020 becuz when i did factory reset and OS is v74 and with v74 i dont have any problem

       

      i cant believe Meta such as big company has problem with their OS update everytime

      and also cant understand still they dont support other languages to change physical keyboard to use lol

      anyway i will update if i have new email

      • TomCgcmfc's avatar
        TomCgcmfc
        MVP
        8 months ago

        madebyrsh  Always an mystery as to why some always have update problems and some, like myself, don't.  With my Q3 I have the latest non-ptc v74 Build 5070966.19510.510 (not sure what you refer to as v74.1020 ?) and this is working very well with everything; standalone VR/MR and PCVR with Link and Air Link (with latest non-beta meta link pc app 74.0.0.675.347),

        I don't quite understand when your said; ' when i did factory reset and OS is v74 and with v74 i dont have any problem '.  Does this mean doing a factory reset fixed things?  Anyway, if you're still having issues I suggest that if you are enrolled in the Meta PTC program that you opt out of this (using your smartphone app) and do another factory reset.  May or may not help if you were already on PTC so you may need to wait for the next update (v75?) in order to sort this out.

        Otherwise, I think all you can do is continue to work with meta support on all this.  I guess there's always a chance that your issues are hardware related and you may need a replacement.  Sorry, as a user, I can't be of more help so I'll sign off this thread now.  Good luck mate and cheers.

  • user.764669's avatar
    user.764669
    Expert Protege
    8 months ago

    I encountered the first problem you mentioned, but I didn't encounter the others.

  • shuaibird's avatar
    shuaibird
    Explorer
    8 months ago

    Nohnez 

    I did a quick test, and issues #2 and #3 don’t occur on my device.

     

    By the way, what do you mean by the volume slider also works in the YouTube app? Are you referring to the built-in volume slider within the YouTube app or the one in the quick settings menu? In my case, the former works, the floating volume adjustment UI appears as well; but the latter does not.

    • Nohnez's avatar
      Nohnez
      Honored Guest
      8 months ago

      so i meant in the quick settings volume slider does not work but in the youtube app. 

       

      the foating volume slider is sometimes visible and sometimes not I haven't found a derivable regularity yet

       

      EDIT:
      What I also noticed is that the translations in some menu items are not complete, as many parts in the quick settings remain in English despite selecting "German."

      • shuaibird's avatar
        shuaibird
        Explorer
        8 months ago

        It’s interesting that while we both experience similar volume control issues, they aren’t exactly the same.

  • shuaibird's avatar
    shuaibird
    Explorer
    8 months ago

    Alright, everyone, just a quick update.

    I finally decided to do a factory reset, and that solved my issue. However, I’m not part of the Public Test Channel, so I didn’t have the v74.1020 version mentioned earlier in the thread - I assume that’s an early test version (feel free to correct me if I was wrong).

    As someone completely new to this device and ecosystem, I never expected to run into such an issue.

    Anyway, I wish my experience may help you get out of such a trouble.

    [UPDATE]

    I checked the version installed on my device, and the version and build number remain the same as before. However, I noticed a difference in the date:

    •Before the factory reset, it showed “Installed on March 18th.”

    •After the reset, it now shows “Created on March 13th.”

     

    One possibility I’m considering is that the update I downloaded might have been different in some way, even though I have no solid evidence to confirm this.

    [RE-UPDATE]

    I believe I now have evidence confirming that the two versions are indeed not the same.

     

    The UI of the Quick Settings looks different. Previously, the microphone and night mode buttons were displayed on the same line as the volume and brightness controls. However, after the factory reset, they are now positioned at the bottom section of the panel.

  • Choleni's avatar
    Choleni
    MVP
    8 months ago

    shuaibird

    most likely nobody is on a PTC version right now. When the build version gets rolled out, PTC user also receive the build version. And to my knowledge, the next beta version isn't rolled out, so all are on the official version.

    After you got a version - for example V74 - this version also will receive updates, which explains the different versin numbers.

     

     

     

     

  • shuaibird's avatar
    shuaibird
    Explorer
    8 months ago

    Choleni 
    Thx for your clarification. For my case, PTC is totally irrelevant. However, I'm 90% sure I installed a minor different version after factory reset - check my RE-UPDATE section in my previous comment for the details, unless the different UI layout is also a bug 😂.

    • Choleni's avatar
      Choleni
      MVP
      8 months ago

      .....unless the different UI layout is also a bug

      who knows😂....v74 seems a bit buggy.

      It's great that you could fix your issue by doing a factory reset👍

      Other users - with different problems - had no luck with that.

      • shuaibird's avatar
        shuaibird
        Explorer
        8 months ago

        Yep. I've seen some minor UI issues already, not critical to me though.

  • Nohnez's avatar
    Nohnez
    Honored Guest
    8 months ago

    Quick update on my case: I didn’t get any real new response from Meta support regarding the issue. So, I went ahead and did a factory reset. After that, all UI and volume issues disappeared, and it’s now running v74 (same build number as BEFORE  "...19510.510" the reset). Interestingly, the install date now shows "Installed on March 13, 2025". no idea why, but at least it works.

    Still, three hours of my life wasted on an update that apparently never went through quality control. Unbelievable. By the way, I’m not in the PTC channel, so this is an official build. I hope you guys can get the issue fixed as well.

    EDIT:
    What took a bit longer this time was the installation of QGO and the ADB drivers. Also, the permission for USB debugging was a bit buggy.

    madebyrsh 
    By the way, in the buggy update, the toggles for night mode and microphone mute were also in different places. The microphone button was directly in the volume slider, and the night mode button was also inside the brightness slider. now its at the button of the qicksettings menu.

  • RickDragon's avatar
    RickDragon
    Honored Guest
    8 months ago

    I bought my Meta Quest 3 a month ago. and I'm having the same problem with the volume slider. I thought it was just me. Sorry for my bad English, I'm from Brazil.

    compilation version: 5070966.19510.510 - March 12, 2025

  • shuaibird's avatar
    shuaibird
    Explorer
    8 months ago

    Bummer Alert:

    Just a quick reminder, if you’ve resolved the issue by performing a factory reset and rolling back the OS version, make sure to disable automatic OS updates—it’s enabled by default. Otherwise, the system may update itself again within a few hours, and you’ll likely encounter the same issue - In my case, it took just 1 hour before the system auto-updated again—I ended up having to reset it all over.


    BTW, I believe this is a bug was introduced by the Meta team tweaking the Quick Settings UI. For some reason, it hasn’t been publicly acknowledged or announced anywhere.

    • madebyrsh's avatar
      madebyrsh
      Explorer
      8 months ago

      shuaibird 

      yes thats why i can say its not problem of v74 (you can see my screenshot)

      becuz when i factory reset its  v74 not v74.1020(you can also see my screenshot)

      on  v74 i dont have problem but when it automatically update becuz of turn on automatic update it change to v74.1020 and then have a same issue again

       

      so i  turn off automatic update

      but i want Meta have to knows their problem of new OS thats why i asked their customer help support

      and i finally got email from them

      and they said  when i send to show every video and screenshot that i took and

      they told me it will be investigated from higher technic team but what i got answer is v72.1020 has no problem

      and  just they will send referbish new MQ3 if i send my MQ3

      so i told him thats not make sense

      because its not my device problem

      so many MQ3 user have same issue

      and then they told me oh actually it didnt delivered to their high level tech team

      so we should investigate that issue again

       

      its kind of waste my whole time

      to share with them

      if they didnt send this isssue to developers of Os team how they can know it has problem in all over world MQ3 user

      and keep saying send my MQ and they will give referbish MQ3

      thats not make sense
      And i send email reply again

      I hope they should investigate of this is issue for next update

      and they changed person who gonna charge with my issue and new guy said

      Send my MQ and we will give new referbish MQ 

      annoyed

      • shuaibird's avatar
        shuaibird
        Explorer
        8 months ago

        madebyrsh 

        It seems like this might be an incident that even the Meta product team hasn’t fully figured out yet. My MQ3 is set to EN-US, but I’m not seeing the v74.1020 version like you are—though I’m not sure if the language setting is actually related. The only visible difference I’ve noticed between the “two versions” is in the UI of the Quick Settings menu, which you could see the same.

        My guess is that the issue could be tied to something more complex within the delivery infrastructure—possibly involving caching or the CDN mechanism.

        That said, as long as the issue gets resolved for now, just relax and enjoy the ride!

        By the way, I used to use AVP. It’s definitely a more mature platform with fewer issues compared to the MQ3. But since it’s a more closed system, I found it less exciting to explore and got bored fairly quickly. In my opinion, that’s the charm and energy of an open system like MQ3—always evolving and full of surprises, including both good and bad.

  • Nohnez's avatar
    Nohnez
    Honored Guest
    8 months ago

    shuaibird  & madebyrsh 

    As I already said, I see it exactly the same way: wasted lifetime. Especially after the last update caused countless Quest 3 models worldwide to run into an error that prevented them from even booting. Many people in Meta's target audience are unable to fix such issues, and I don't see it as the user's responsibility to have to acquire this knowledge or spend hours searching and reading through random forums to find a solution.

    We're talking about devices with a new price ranging from $300 to $600. Many users have saved up for a long time to afford them.

    It's like a car dealer saying: "Oh, you crashed on the highway after we updated your ABS system? No problem, just send us back the wreck, and you'll get a new car."

    Also, as already mentioned, not everyone is aware that the default settings could cause the Quest to automatically download the same update again - unless the user manually disables this option.

    I wish everyone still struggling with this issue the best of luck in resolving it soon.