It would be great if Oculus Go would provide a Kiosk mode - that is the best case scenario.

But, in the meantime, Surelock or KioWare may work if only there was a way to handle the non-VR admin screens. Meaning, it is currently possible to install the Kiosk software using 'adb install surelock.apk' for instance. When the Oculus Go is rebooted - after adb install of the apk, you are prompted with a VR screen to set the Home Launcher to the default Oculus Go Launcher or Surelock for instance. If you set to Surelock, the Admin screens appear in non-VR form (standard phone form) and are not accessible and are hardly viewable through the VR lenses (as one would expect). Any hope with that approach?

Or, another approach is to set our app as the Device Owner and use the Android startLockTask - from custom code. We have tried this as well. However, the permissions do not seem to allow us to set our app to Device Owner.adb shell dpm set-device-owner <package>/.AdminReceiverIs this approach viable? Perhaps we are missing something regarding permissions?

@frankayarsI agree, the dpm set-device-owner method works on android usually but not on Go. Maybe there's an extra step here on Go to be able to pull it off. Wouldn't it be adb shell dpm set-device-owner (package-name)/.DeviceAdmin ?

@undef_devThat's awesome though don't we still have the issue that Oculus home is still available?

"Note: The device owner can be set only from an unprovisioned device. If Settings.Secure.USER_SETUP_COMPLETE has ever been set, the device is considered provisioned and the device owner cannot be set."

@frankayarsThanks for the explanation, makes more sense to me now. I'm going to continue experimenting with the commands and see what I can find.

@undef_devOn the Go I can't seem to get the command to work. It returns with an argument exception when I try and set-home-activity in the shell. No matter what I try. Could you talk me through your process?

I have tried the Mobilock and Hexnode solutions with the Oculus Go, but they are unmanageable due to they are not correctly displayed, and they don't work with the controller. However, I have been talking with the people of Mobilock, and they told they will buy one Oculus Go to try it, and maybe, adapt their software to VR.