Reserved User Interactions (Deprecated)
Updated: Sep 29, 2022
Mobile SDK Deprecation
As of August 31, 2022, Mobile SDK and the VrApi library are no longer supported. Future updates will be delivered through OpenXR extensions and our OpenXR Mobile SDK, not through any new updates to Meta Mobile or PC APIs. - New apps must use OpenXR unless a waiver is granted.
- New apps will not have access to Meta Native Mobile APIs, but existing apps can continue using them.
- No assistance will be provided for creating new apps with Meta Native APIs. You will find recommendations for migrating existing apps to OpenXR in the developer guides.
- Only critical security, privacy, or safety issues in Meta Native APIs will be addressed.
- Any testing of Meta Native Mobile will be restricted to automated QA tests, only to ensure core features remain functional.
This section describes input actions that are reserved for system-level functionality. This includes use of the Volume and Home physical buttons on the Meta Quest Touch controllers.
Reserved User Interactions
The Home button and Volume button behaviors must conform to specific requirements.
Volume adjustment on the Meta Quest devices is handled automatically. The volume control dialog display is also handled automatically by the VrApi as of Mobile SDK 1.0.3. Do not implement your own volume display handling, or users will see two juxtaposed displays.
You may override automatic volume display handling if necessary by setting VRAPI_FRAME_FLAG_INHIBIT_VOLUME_LAYER as an ovrFrameParm flag.
Volume buttons are not exposed through VrApi interfaces.
A Home button press always opens a dialog to return the user to Home menu. As of Mobile SDK 1.0.4, this behavior is handled automatically by the VrApi.
The Home button is not exposed through the VrApi interfaces, and no Android events will be passed to the app for the Home button.
