basti564/Oculess

Ability to auto disable prox sensor on startup

Opened this issue · 8 comments

Bluscream commented

I have once had to replace my usb-c port on my quest, and accidentally broke the ribbon cable of the proximity sensor while doing so, ever since that i need my prox sensor to be disabled on startup otherwise the screen stays blank (yeah, even when manually turning the screen on. idk why but it is like it is).

I used Automagic to do this before;

  <flow type="flow">
    <name>quest disable proximity sensor</name>
    <group>Quest VR</group>
    <enabled>true</enabled>
    <lastExecutionStartTime>1681516572533</lastExecutionStartTime>
    <lastExecutionEndTime>1681516572537</lastExecutionEndTime>
    <executionPolicy>SKIP</executionPolicy>
    <emergencyStopCount>999</emergencyStopCount>
    <triggercontainer id="t1" x="70.0" y="52.5">
      <trigger>Automagic Startup</trigger>
      <trigger>App Task Started: com.oculus.vrshell,com.oculus.vrshell.home,com.bos.vrLauncher</trigger>
      <trigger>Display State: On</trigger>
    </triggercontainer>
    <actioncontainer id="t2" x="69.999985" y="262.5">Send Broadcast: com.oculus.vrpowermanager.prox_close </actioncontainer>
    <connection from="t1" to="t2" type="NORMAL" sourcePosition="SOUTH" targetPosition="NORTH" />
  </flow>
  <action type="send_broadcast">
    <useDefaultName>true</useDefaultName>
    <name>Send Broadcast: com.oculus.vrpowermanager.prox_close </name>
    <intentAction>com.oculus.vrpowermanager.prox_close</intentAction>
    <categoryListEnabled>false</categoryListEnabled>
    <categoryList>android.intent.category.DEFAULT</categoryList>
    <dataEnabled>false</dataEnabled>
    <data></data>
    <dataTypeEnabled>false</dataTypeEnabled>
    <dataType>text/plain</dataType>
    <explicitComponent>false</explicitComponent>
    <packageName></packageName>
    <className></className>
    <flagList>FLAG_ACTIVITY_NEW_TASK</flagList>
    <extras></extras>
    <waitForResult>false</waitForResult>
    <accessResultExtras></accessResultExtras>
  </action>

but Automagic does not work anymore since Android 12 and these fucking stupid permission restrictions. Can you make it part of either oculess or vrLauncher or perhaps a new app like idk vrTweaks or smth.

basti564 commented

I think this could be something to add to Oculess. I'll see if I can make it work

  • ❤️5
mittorn commented

I am using keymapper in v38 and self-made app that receives volume change broadcast in v50

SevastianGit commented

I am using keymapper in v38 and self-made app that receives volume change broadcast in v50

Maybe you could share the app you made :>

mittorn commented
mittorn commented
SevastianGit commented

Uploaded working directory here: http://mittorn.fwgs.ru/volumelistener.7z I cannot test and rewrite it to more useful way now as meta seems to locked facebook account because of untrusted IP, but it is inaccessible from russia, developer mode on quest stopped work after facebook services wasted all space on internal storage, so i only able to run keybound ALVR and cannot install software on reenable devmode :(

You cannot use devmode because you're in Russia? Hm, well maybe you could put a VPN onto your router, or if that doesn't work on Android you can install a VPN (I recommend Windscribe, although you'll probably have to get the apk from apkmirror and you might also have issues registering and have to use their "Emergency VPN connecrion", in case you're unable to register, I can make an account for you) and then go to hotspot settings, toggle "Allow clients to use VPNs", make a hotspot and connect your Quest to the hotspot (and then I suppose use another device with a VPN to go through the dev activation process, I believe this should work)

mittorn commented
SevastianGit commented

Facebook requested passport verification on account with fake data, so it seems, i need to make new one. And developer account needs to be confirmed with bank card, but our cards are blocked worldwide now, so i decided to switch to pico 4 or neo 3, at least it allows enabling developer mode without such confirmation. It is possible to restore account, but it is too complex, so but i not sure i want continue using meta devices now, as it may fail any time, it may disable adb remotely any time, android may bootloop any time forcing me to reset, login and update firmware to some broken version (keymappers does not work on v50+ and causes bootloop on v51+)

Aw man, does seem like Meta's devices are sucky:/ (I'm on Quest 1 myself here hah, I'm just curiously looking around here), have no experience with pico 4 or neo 3, hope they're good for you)