DEVICE-CENTRIC DOCUMENTATION

The site has a new content architecture. We've added the ability to select your development device to show device-specific content. Please read our blog post Oculus Developer Center Update: Device-centric Documentation Architecture for more information.

Oculus Quest Development

All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.

Gear VR Development Guide - Legacy

Important

Gear VR is no longer supported starting with Mobile SDK 1.27.0 and integrations version 1.42. Please review this document for supported Gear VR development configurations.

This page describes the end of life and ongoing maintenance for Gear VR. This page will also review the development specifics for Gear VR. Unless otherwise noted on this page, development for Gear VR is similar to Oculus Go development.

Gear VR Runtime Updates

All Gear VR devices will stay on the V9 runtime. No updates are planned, but newer devices (Samsung Galaxy S8 and newer) may receive critical patches.

Gear VR Development

Developers who need to update an existing application, should use the following version and/or development environments.

To update your Gear VR application, use the Oculus Mobile SDK v1.26.0

General Development

The following section describes the specifics of Gear VR development.

OSIG

During development, your application must be signed with an Oculus-issued Oculus Signature File, or osig. This signature comes in the form of a file that you include in your application in order to access protected low-level VR functionality on your mobile device. Each signature file is tied to a specific device, so you will need to generate osig files for each device that you use for development. When your application is submitted and approved, Oculus will modify the APK so that it can be used on all devices.

Please see our osig self-service portal for more information and instructions on how to request an osig for development: https://dashboard.oculus.com/tools/osig-generator/

Each signature file is associated with a specific mobile device, so you will need an osig file for each device that you use for development.

Please see our osig self-service portal for more information and instructions on how to request an osig for development: https://dashboard.oculus.com/tools/osig-generator/

Once you have downloaded an osig, be sure to keep a copy in a convenient location for reuse. You will only need one osig per device for any number of applications.

<project>/Assets/Plugins/Android/assets/

If that directory does not exist, create it and copy the osig file to it. Note that the folder names are caps sensitive and must be exactly as stated above.

If you attempt to run an Oculus mobile APK that has not been correctly signed with an osig, you will get the error message “thread priority security exception make sure the apk is signed”.

We recommend removing your osig before building a final APK for submission to the Oculus Store. When your application is approved, Oculus will modify the APK so that it can be used on all devices. See Building Mobile Apps for Submission to the Oculus Store for more information.

adb with Gear VR

Some Samsung phones may require a special USB driver to connect and use ADB. If required, Samsung Android drivers can be found on their developer site at https://developer.samsung.com/mobile/android-usb-driver.html.

Launching a development Gear VR app

When building an app following Android Studio Basics -

If you are developing for Gear VR and your phone is set to Developer Mode, your application can launch without being inserted into your Gear VR headset. Otherwise, when the process completes you will be prompted to insert your mobile device into the headset to launch the application.

Gear VR SD Card Support

All Gear VR applications submitted to the Oculus Store must support installation to SD Card.

SD Card installation support is enabled with the manifest setting android:installLocation="auto" as described in Android Manifest Settings.

To test application performance after installing to an SD Card:

  1. Verify that AndroidManifest.xml is set to android:installLocation=”auto”.
  2. Build an APK of your application.
  3. Sign your application.
  4. Sideload your app as described in “Using adb to Install Applications” in our adb guide. Be sure to install the application to internal storage,
  5. Go to the Android Application Manager and move the application to an SD Card. For more details, see our Developer Blog post Gear VR SD Card Support.
  6. Launch your application and verify that it works properly.

Users who install mobile applications from the Oculus Store who wish to store them on their SD Card must manually move them following the steps described by our Developer Blog post Gear VR SD Card Support.

Gear VR Development Requirements

All Gear VR apps are required to meet the VRCs described in the Mobile Virtual Reality Check (VRC) Guidelines.

Publishing Gear VR Apps

Follow the steps in the Uploading Android Apps section to publish your updated Gear VR app.