Skip to main content
Ghost1506081
Ghost1506081
New Participant
May 24, 2025
Question

New Navigator UI Not Showing For Main User, But Shows For Secondary User

As the title says, the new navigator ui on v77 only works for my other user on my quest and not my main. I've already restarted the headset many times, yet it still doesn't show. If anyone can help, I would really appreciate it!

      12 replies

      quantum0300
      quantum0300
      Up and Coming
      May 24, 2025

      well, I am very eager to update to the new UI, perhaps switching users can achieve it?

      pollitoninja
      New Participant
      May 31, 2025

      I have the same issue. My main profile still has the older version of the UI. But I logged in with other profile and the navigator just pop up. I've tried everything, reboot, power off and on, force power off. The update tool from meta, I don't want to factory reset the headset just to see if it works. 

      quantum0300
      quantum0300
      Up and Coming
      May 31, 2025

      **bleep** it, I tried a brand new sub account that doesn't have a navigator, but has many features that the main account doesn't have (such as custom shortcut menus, automatic updates when shutting down). A brand new account without developer mode and PTC actually has more features, which is absurd and incomprehensible. Regarding the issue between you and the poster, I think it's because the navigator randomly pushes based on accounts, and your main account did not receive the push, while your sub accounts received the push instead. So the navigator is actually installed in the glasses, but only the selected account has permission to use it.

      markinsutton
      markinsutton
      New Participant
      June 5, 2025

      Interesting to know how many of you are outside the US? could this be another example of companies rolling out features to America first before giving it to the rest of us?

       

      Choleni
      Choleni
      Honored Contributor
      June 14, 2025

      BruceArthurWayne It's not a thing of location. 

      Not everyone in the US - or in any other country - has the navigator right now... currently most people don't have it. So, setting your location to a US server won't help.
      I already mentioned the rollout details in the other thread.

      Re: Why Is the New Navigator UI STILL Not Availabl... - Meta Community Forums - 1328127  

      Cloudy21264
      Inspiring
      June 22, 2025

      Same here. I also live in USA, so I'm not sure whats happening.

      MisutaaAsriel
      MisutaaAsriel
      Participant
      July 2, 2025

      Can I ask if you have developer mode?

      I was looking around the OS and I noticed Navigator is a separate package. Launching it manually doesn't work, but I'm wondering if there's a way to enforce it using ADB and a computer. Either through a property (via setprop) or by changing the default home application.

      If it's user based, you could dump the user property store and the default home application to see if it differs between the accounts, maybe?

      Signed, Azi ~
      quantum0300
      quantum0300
      Up and Coming
      July 3, 2025

      no way. That apk is just the most basic program and does not include the resources required by the navigator. Launching it will only result in errors. Perhaps you can achieve this by overwriting the data directory of other navigators onto yours? After I obtained the navigator, its memory usage was 30mb, while when it was unavailable, it was only 6mb.

      MisutaaAsriel
      MisutaaAsriel
      Participant
      July 24, 2025

      That doesn't mean anything. If Navigator creates files on initialization, or downloads assets when working normally, it would increase in on-device size.

      My main curiosity is if the reported home/launcher app is different with Navigator enabled accounts/headsets, or if VRShell is acting as an intermediary launcher between home environments and the rest of the system.

      If it's the former, in theory one could use ADB to change the launcher to match the expected parameters for Navigator.

      Alternatively, if there's a flag set in the OS to signal a change to navigator, knowing that flag and if it's R/W (like the debug flags) would be useful.

      Launching it in a 2D context from another app when it is unintended to launch in that way of course isn't going to work.

      Signed, Azi ~
      BruceArthurWayne
      BruceArthurWayne
      Up and Coming
      July 2, 2025

      I received Navigator on Saturday morning—not on my Quest 2, but on one of my other headsets. It doesn’t seem to be available on all devices yet. From what I can tell, Meta is rolling it out slowly and in stages, enabling it from their side. That means availability will vary by account and device.

       

      Honestly, Meta really needs to rethink how they handle these feature rollouts. It’s confusing, inconsistent, and frustrating for users. They also need to start listening to customer feedback—if people are complaining, it means something isn’t working. A great business isn’t built on praise alone—constructive criticism is how you actually improve.

      pollitoninja
      New Participant
      July 4, 2025

      It's weird, I factory reset my quest and logged in with my friends account and got the navigator, so I added myself as other user to share the headset and also had the navigator. Used for a few days and factory reset again to log in with my personal account and now I don't have the navigator again. Still on v78 but don't have nor navigator or the other funcionality of the new versions. 

      NomadsAnIsland
      Honored Contributor
      July 4, 2025

      You should be thankful if Navigator has not yet infested your headset. It's a diasaster.

      Terms & ConditionsAccessibility statement