Forum Discussion

f0gpie's avatar
f0gpie
Explorer
13 days ago

Starting at Rift 1 it’s silly that Quest in 2025 still lack basic user controls for core functions

    • People have been asking Meta for years to add a simple toggle to disable the proximity sensor directly on the headset. Instead, the only way is through ADB or SideQuest, which makes zero sense for a mainstream device. A native setting should exist by now.
    • Meta also removed the option to disable the “double tap to glance” overlay. It’s now permanently on with no way to turn it off. 

    In fast movement or dance sessions, both problems annoy constantly. Quick head movement or leaning forward trips the proximity sensor, and accidental taps or scratches activate room view. It breaks immersion every time.

    It honestly feels like the product designers don’t actually use the headset actively. Having to open a developer account just to disable Guardian proves it. If there are legal concerns, add warnings. Don’t take away core user control!

    Small note while on on the train of annoying issues about Pro:
    -thanks for fixing the odd rendering issue on Pro headset where a diagonal line was breaking the image on the headset after updating to v80 and up its gone

    • BUT when will your microphones ever be flawless? It's not as bad as the Rift S, but occasional mic dying turning robotic or giving a high pitch scream still appears once every few months or weeks 
      does not happen on my Quest 3, Rift cv1, but we all know the famous Rift s mic going robot mode!

    (all headsets now on newest OS at the time of writing this)

No RepliesBe the first to reply