7.9. Virtual Reality
Android includes APIs and facilities to build “Virtual Reality” (VR) applications including high quality mobile VR experiences. Device implementations MUST properly implement these APIs and behaviors, as detailed in this section.
7.9.1. Virtual Reality Mode
Android includes support for [VR Mode]( https://developer.android.com/reference/android/app/Activity.html#setVrModeEnabled%28boolean, android.content.ComponentName%29), a feature which handles stereoscopic rendering of notifications and disables monocular system UI components while a VR application has user focus.
7.9.2. Virtual Reality High Performance
If device implementations identify the support of high performance VR for longer user periods through the android.hardware.vr.high_performance
feature flag, they:
- [C-1-1] MUST have at least 2 physical cores.
- [C-1-2] MUST declare
android.software.vr.mode feature
. - [C-1-3] MUST support sustained performance mode.
- [C-1-4] MUST support OpenGL ES 3.2.
- [C-1-5] MUST support Vulkan Hardware Level 0 and SHOULD support Vulkan Hardware Level 1.
- [C-1-6] MUST implement
EGL_KHR_mutable_render_buffer
, EGL_ANDROID_front_buffer_auto_refresh
, EGL_ANDROID_get_native_client_buffer
, EGL_KHR_fence_sync
, EGL_KHR_wait_sync
, EGL_IMG_context_priority
, EGL_EXT_protected_content
, and expose the extensions in the list of available EGL extensions. - [C-1-7] The GPU and display MUST be able to synchronize access to the shared front buffer such that alternating-eye rendering of VR content at 60fps with two render contexts will be displayed with no visible tearing artifacts.
- [C-1-8] MUST implement
GL_EXT_multisampled_render_to_texture
, GL_OVR_multiview
, GL_OVR_multiview2
, GL_OVR_multiview_multisampled_render_to_texture
, GL_EXT_protected_textures
, and expose the extensions in the list of available GL extensions. - [C-1-9] MUST implement support for
AHardwareBuffer
flags AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER
and AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA
as described in the NDK. - [C-1-10] MUST implement support for
AHardwareBuffers
with more than one layer. - [C-1-11] MUST support H.264 decoding at least 3840x2160@30fps-40Mbps (equivalent to 4 instances of 1920x1080@30fps-10Mbps or 2 instances of 1920x1080@60fps-20Mbps).
- [C-1-12] MUST support HEVC and VP9, MUST be capable to decode at least 1920x1080@30fps-10Mbps and SHOULD be capable to decode 3840x2160@30fps-20Mbps (equivalent to 4 instances of 1920x1080@30fps-5Mbps).
- [C-1-13] MUST support
HardwarePropertiesManager.getDeviceTemperatures
API and return accurate values for skin temperature. - [C-1-14] MUST have an embedded screen, and its resolution MUST be at least be FullHD(1080p) and STRONGLY RECOMMENDED TO BE be QuadHD (1440p) or higher.
- [C-1-15] The display MUST update at least 60 Hz while in VR Mode.
- [C-1-16] The display latency on Gray-to-Gray, White-to-Black, and Black-to-White switching time MUST be ≤ 3 ms.
- [C-1-17] The display MUST support a low-persistence mode with ≤5 ms persistence, persistence being defined as the amount of time for which a pixel is emitting light.
- [C-1-18] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension section 7.4.3.
- [SR] STRONGLY RECOMMENDED to support
android.hardware.sensor.hifi_sensors
feature and MUST meet the gyroscope, accelerometer, and magnetometer related requirements for android.hardware.hifi_sensors
. - MAY provide an exclusive core to the foreground application and MAY support the
Process.getExclusiveCores
API to return the numbers of the cpu cores that are exclusive to the top foreground application.
If exclusive core is supported, then the core:
- [C-2-1] MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary.