Understand permissions for XR

Just like apps on mobile devices and other form factors, some capabilities offered by XR apps require your app to declare permissions in your app's AndroidManifest file. In the case of dangerous permissions, your app may need to request runtime permissions. Read Permissions on Android and permission best practices for more in-depth information.

The following permissions can be used by XR apps. All of the permissions in this section are considered dangerous permissions, so you must declare them in your app manifest and request them at runtime.

android.permission.EYE_TRACKING_COARSE

Representing the user's eye pose, status, and orientation, such as for use with avatars. Use this permission when low-precision eye tracking data is needed.

android.permission.EYE_TRACKING_FINE

Eye gaze for selection, input, and interactions.

android.permission.FACE_TRACKING

Tracking and rendering facial expressions.

android.permission.HAND_TRACKING

Tracking hand joint poses and angular and linear velocities; Using a mesh representation of the user's hands.

android.permission.SCENE_UNDERSTANDING_COARSE

Light estimation; projecting passthrough onto mesh surfaces; performing raycasts against trackables in the environment; plane tracking; object tracking; persistent anchors.

android.permission.SCENE_UNDERSTANDING_FINE

Depth texture.