Forum Discussion
Using dev mode to disable proxy sensor but dev mode stopped working
I used side quest and MQDH to disable the proxy sensor and now my meta quest app gives me an error when trying to enable dev mode after it disabled its self. I’ve searched through a lot of online stuff but it all requires you to use you headset which I can’t do without dev mode so there’s kind of a loop there and it doesn’t seem fixable unless I get my sensor fixed unless there’s some other way like forcing adb or anything anyone else can think of if it seems like it can’t get fixed I’ll go and get my headset fixed and try to figure something out from there.
5 Replies
Use Sidequest to install 'Settings Shortcut'.
This little app gives you direct access to the Android settings.
If the developer mode is stuffed up:
Disable it, do the usual 7 taps and enable it again - no need to go through the phone app and developer account.
Lightning launcher does give you settings access as well but not sure if it still runs stable on the V60 update as it struggled on the V56 already.
Keep in mind that certain things ARE required by the OS and if disabled it can have unforeseen consequences....I didn’t mean to accept this as the solution but I’m unable to access my headset due to the facial proxy not working like I said in the post and I used side quest to deactivate the sensor but also side quest doesn’t accept anything unless dev mode is active so everything you just said will not be accessible to me
I see your issue now 😞
Sensor turned off and developer mode out of reach.
Just to prevent my further confusion:
You can turn on your headset....
Did you provide authorisation for the laptop/PC for ADB access without confirmation?
If Sidequest worked I have to assume you did.
Trying to get you going here:
Does the headset show up in the Windows Device manager when you connect it?
It should boot up and then show up in there.
IF that is the case you can download the ADB Android stuff and use a command prompt or powershell to get to the headset.
If you find the folder with the ADB stuff in your Sidequest installation you can just open a prompt there.
Of course in the mobile app there is a slider to turn this sensor on and off.
Thing is that upon a restart the sensor should be enabled back by default.
"In the mobile app, go to Menu at the bottom right, then Devices -> Headset Settings -> Power Settings and turn off the Auto Wake-Up slider."
If that does not work and you can't use Sidequest but ADB still works, do it manually:Turn off sensor:
shell am broadcast -a com.oculus.vrpowermanager.prox_closeTurn on sensor:
shell am broadcast -a com.oculus.vrpowermanager.automation_disable
Last but not least and to avoid a factory reset:
Do a proper power cycle of the headset.
Press and hold volume down/power until the little boot menu shows up.
Select to power up/start the device.
Once done wait a few minutes and do the same but select to power down/shut off.
This shall remove and fix anything store in temp places that is not as the default.
As a last resort a factory reset, available through the above menu will fix the sensor issue but you then start from scratch.Forgot the 'official' fix the support wont tell you about:
In the developer you can turn off the proximity sensor, which means it should be possible to enable it back there as well.
Bit of a hassle but still.Tech issues can feel like a never-ending loop sometimes. I had a similar situation with my headset a while back, where I tried everything to fix a glitch, but I was stuck in a cycle of troubleshooting. I ended up finding that using mobile proxies really helped with some connectivity issues I had. They made things a lot smoother and less frustrating! As for your issue, I think forcing ADB might be worth a shot if you haven't tried that yet. But if that doesn't work, getting your sensor fixed sounds like a solid plan. It can be a hassle, but it might just solve everything. I’m new here, so I’m still figuring out all the ins and outs of the forum.
