stuck at boot loop after update v79 quest 2
Was unlucky to update quest 2 to v79 (standard), it messed up usb connectivity on all my cables took me a while to read about update being at fault and not cables or usb-c port, thought beta might allready have a fix for it, activated beta updates via phone, updated to v79.130 something i believe and got stuck at boot menu or "usb update mod" no options work aside from "device info" and "power off", upon choosing any other option screen goes dark for a sec then meta logo without animation and im back to bootload menu (usb update mod) have a strong suspicion that update bricked itAutomatic audio balance setting is present on child's profile but not on primary profile
Another bit of Quest UI weirdness. I just discovered today that my daughter's parentally controlled (secondary) profile on my Quest 3 has a setting under "Camera" to "Automatically adjust microphone and game balance". If I toggle this setting to "off", it will show the separate microphone and app audio sliders. Sorry, no screenshot, I couldn't figure out how to send it from my child's account to my main profile, phone or PC. Strangely however, on my primary profile on the same headset, the toggle to "Automatically adjust microphone and game balance" is completely absent and I only have the separate microphone and app audio sliders (screenshot below). It seems really strange that two different profiles on the same headset don't have the same settings available. I'm on v79.1031 build 5115411.17040.520 (12 Sep 2025). Is this a bug, or by design?
Quest 3 stuck and unable to complete boot
My Quest 3 was working fine until a couple of days ago and I use it almost daily. On trying to turn it on yesterday I am now stuck in with the following: I see a stack Meta Horizon OS logo for a couple of seconds I see the chip icon with arrow and a green progress bar which completes I see an animated spinning Meta Horizon OS logo for maybe 30-60 seconds The screens go black, they are still powered on but not showing anything. It never gets any further than that. I have tried the following, none of them changes anything: Doing a hard reboot Doing a factory reset Doing a sideload of the most recent v79 update via USB, this downloads and installs fine giving no errors but the issue is still there afterwards. I see one other thread in this forum recently which sounds like the same issue but there was no responses on that one https://communityforums.atmeta.com/discussions/OtherTroubleshooting/most-recent-update-bricked-my-quest-3/1343071 At this point I can't think of anything else to try other than to go through a warranty process, but I'd welcome anything else to try first.Meta Q3 and 2nd user Portal to Admin's Home environment
I use Quest 3 2 users When the headset is started not by the administrator in his home environment sees through the "windows" the admin's home environment, restart or shutdown does not help Sometimes the "portal" zone becomes static - and 2nd user can pull out the windows from this block
Pro controllers refuse to update after V79 update on headset
I've run loops with the support team with no help so thought I would come to the forums I have a quest 2 and I have the meta pro controllers after the recent software update they've refused to update I've tried resetting them unpairing and repairing charging them and when nothing worked I contacted meta support which the guy told to me factory reset and guess what it didn't work so now I'm stuck with a factory reset headset that I can't start the set up on because I don't got working controllers because they still say they need to update I don't know how to fix it I don't got a computer that I can use and I don't have another headset that I can pair the controllers to is there anyway to fix this? since Meta support did not help at all
Software Update Tool Not Working for Quest 2
Are you experiencing issues upgrading your Quest 2 headset to v79 with the software update tool? I have taken an hour or so to troubleshoot, and the software tool is not displaying a list of headsets in the browser when connecting with a USB. The software update page notes that Quest 2 is also included in v79, however I am wondering if they have just given up on Quest 2 updates altogether. My warranty has long expired, and I really do not want to purchase another headset at this time. Thanks!v79 Dialog-Related Crashes in Android Settings
Since the v79 update, various dialogs in the Android Settings app are no longer accessible and crash the Android Settings app when opened. This includes, but is not limited to, the following: WiFi & Internet -> Private DNS Accessibility -> [ANY SERVICE] -> Turn On System -> Developer -> Wireless Debugging -> Pair with Pairing Code The following error is visible in LOGCAT: FATAL EXCEPTION: main Process: com.android.settings, PID: 2626 java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity. at androidx.appcompat.app.AppCompatDelegateImpl.createSubDecor(AppCompatDelegateImpl.java:926) at androidx.appcompat.app.AppCompatDelegateImpl.ensureSubDecor(AppCompatDelegateImpl.java:889) at androidx.appcompat.app.AppCompatDelegateImpl.setContentView(AppCompatDelegateImpl.java:772) at androidx.appcompat.app.AppCompatDialog.setContentView(AppCompatDialog.java:99) at androidx.appcompat.app.AlertController.installContent(AlertController.java:232) at androidx.appcompat.app.AlertDialog.onCreate(AlertDialog.java:278) at android.app.Dialog.dispatchOnCreate(Dialog.java:436) at android.app.Dialog.show(Dialog.java:325) at androidx.fragment.app.DialogFragment.onStart(DialogFragment.java:973) at androidx.fragment.app.Fragment.performStart(Fragment.java:3173) at androidx.fragment.app.FragmentStateManager.start(FragmentStateManager.java:625) at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:290) at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:1938) at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:1841) at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1778) at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:564) at android.os.Handler.handleCallback(Handler.java:958) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:218) at android.os.Looper.loop(Looper.java:310) at android.app.ActivityThread.main(ActivityThread.java:8250) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978) This is a regression from v78 and prior versions, where these dialogs all worked as expected.
