Forum Discussion
MeessenPhilips
9 years agoExplorer
Disable the default GearVR hardware input (Unity)
Since Mobile SDK 1.0.4 is incorporated into Unity the reserved input functionality for the GearVR is automatically handled by the VRApi. So a back-button long press now automatically opens the Oculus universal menu.
We have a case where we use the GearVR in a stand-alone setup where clients can use it without supervision. A problem which often arises is that they use the back button and accidentally close our app.
To solve this we would like to incorporate a mode where the back, home and volume buttons are disabled.
Ideally this should be solved in software. I have already tried several things, including extending the default Unity Activity and intercepting the input on a low level, but this only disables the volume buttons.
I know Unity 5.3 versions (and some 5.4) use an older VRApi where the input is not automatically handled, but Oculus states on their website that support is already deprecated and we do not want to keep using an old version indefinitely.
I know the reserved input is a requirement by Oculus, we do want to keep this as default, but want to add an in-app menu option to disable the back, home and volume button for stand-alone demonstrations.
I hope someone knows a solution.
We have a case where we use the GearVR in a stand-alone setup where clients can use it without supervision. A problem which often arises is that they use the back button and accidentally close our app.
To solve this we would like to incorporate a mode where the back, home and volume buttons are disabled.
Ideally this should be solved in software. I have already tried several things, including extending the default Unity Activity and intercepting the input on a low level, but this only disables the volume buttons.
I know Unity 5.3 versions (and some 5.4) use an older VRApi where the input is not automatically handled, but Oculus states on their website that support is already deprecated and we do not want to keep using an old version indefinitely.
I know the reserved input is a requirement by Oculus, we do want to keep this as default, but want to add an in-app menu option to disable the back, home and volume button for stand-alone demonstrations.
I hope someone knows a solution.
3 Replies
Replies have been turned off for this discussion
- MeessenPhilipsExplorer
Hello,
imperativity said:
Hi,
At this time, disabling VRDriver's handling of the volume and home buttons is not yet possible in Mobile SDK 1.0.4 and there are no plans to allow for inhibiting long-press handling.We have a case where we use the GearVR in a stand-alone setup where clients can use it without supervision.Might I suggest programming some visual warning/display into your application warning the user against manipulating the buttons in this fashion?
Thank you for your reply. While a visual warning is an option we ideally prefer to have a "fool proof" solution, where the stand-alone system cannot easily fail. Guess I will have to keep looking.
- ruud3DVStart PartnerHi, is there a solution for this? I'm also looking into disabling the back button for use of the GearVR on exhibitions, to prevent users going to Oculus Home and/or changing user settings. A visual warning won't be enough I'm afraid.
- SrayaHonored GuestHi, I'm also looking for a solution. I'm using unity, and I need to disable long press back-button.
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 8 months ago
- 4 months ago
- 8 months ago
- 9 months ago