Oculess VS vrLauncher

Oculess Github

Never tried it but there is Oculess: https://github.com/basti564/Oculess

you can try using oculess to disable telemetry and maybe even remove fb from the headset if you manage to score a v41 or lower headset and use only oculus link/virtual desktop or alvr or any wireless vr streaming to use it with steamvr

Perhaps the root of this problem. https://github.com/basti564/Oculess/issues/81

link: https://github.com/basti564/Oculess

I could trigger the tutorial with vrLauncher https://github.com/basti564/vrLauncher and after that I had the option. I think the activity I launched was “CO_PRESENCE_NUX”

There are many ways to open the settings app and bypass the ADB shell restrictions if you know how. One simple way is to just sideload VRLauncher found here. https://github.com/basti564/vrLauncher

You can open it using Basti's VR launcher: https://github.com/basti564/vrLauncher/releases

they've kept this menu, but removed some of the most important functions of it. see Oculess and vrLauncher 1.8

Passthrough portal is a feature oculus opened up for devs to experiment with. Reference https://github.com/basti564/vrLauncher/releases

vrLauncher: launch various /hidden/ options of the Oculus Quest (2)

I found an ipd test pattern & config window with vrLoader which confirmed my feeling.

Side load the latest apk from https://github.com/basti564/vrLauncher and use the drop down to launch Passthrough Portal if you want to try it out. Either way, this is clearly something that will be polished up by Oculus and officially released whenever they make a push for Infinite Office and definitely feels like a better solution for getting a keyboard into VR than what you currently get with a seven year old Logitech keyboard.