Apps should support 3D audio spatialization. (Recommended)
Additional Details
For more information, see QIYU Device Developer SDK & Document-Audio (opens new window).
Steps to Test
Locate a sound source within the app and rotate your head.
Expected Result
Sound should switch appropriately between speakers.
1.The app must use a refresh at least 72 Hz on QIYU devices.
Additional Details
For more information, see QIYU Device Developer SDK & Document (opens new window).
The SDK Sample provides FPS.cs for calculating FPS.
Expected Result
The application should not experience extended periods of framerate below the requested refresh rate of the display. Exceptions include when there’s a black screen or loading scenes.
2.The app must run for 45 minutes with typical usage without entering thermal throttling Power Save mode.
Steps to Test
adb push freq_temp.sh /sdcard/
adb shell
cd sdcard
chmod 775 freq_temp.sh
nohup sh freq_temp.sh > data.csv &
Expected Result
Device's performance will not be degraded because of thermal issues caused by running application.
3.The app must either display a slow head tracked graphics in the headset within 4 seconds of launch or provide a loading indicator in VR.
Steps to Test
Expected Result
App begins accepting input, responds to head tracking, and displays graphics within 4 seconds of app startup.
1. The app must install and run without crashes, freezes, or extended unresponsive states.
Steps to Test
Expected Result
2. Single player apps must pause when the user removes the headset or opens the Flexible Dock.
Additional Details
In Unity, you should see OnApplicationPause(true) called both when the HMD sleeps after dismount, as well as when the display is turned off from the power button.
This will be matched by a corresponding OnApplicationPause(false) when the headset is remounted, or the power button is hit again to turn on the display.
Things that cause OnApplicationPause(true) to occur:
Steps to Test
Expected Result
Things that cause the occurring of application pause:
3. The app must not leave the user stuck at any point in the experience.
Additional Details
For example, if your app requires a login, you must provide instructions for the user to successfully create an account. These instructions must be discoverable in VR, but account creation could happen in 2D.
Game levels must not have broken logic that prevents progressing to the next level.
Steps to Test
Expected Result
User must be able to experience all content without being unable to progress or requiring unobtainable information.
4.Volume can be adjusted properly by using the headset volume keys，the in-app volume and sound settings.
Steps to Test
Expected Result
Volume can be adjusted.
5.The application must respond to the HMD’s positional tracking as well as orientation.
Steps to Test
Expected Result
Your view should look as if you are moving within the VR world.
6. Only QIYU hardware information should be displayed if the app or store assets involves information about headsets, controllers or related devices.
Steps to Test
Expected Result
App should only reference QIYU HMDs and controllers.
The customized controllers should not be similar to that of other brands.
7.The app must not lose the user’s data. Such as saves/settings/downloads/content. If there is a leaderboard, leaderboard records must be saved.
Steps to Test
Expected Result
All user saves/settings/downloads/content created within the app persist throughout use of the application.
Leaderboard records must be saved properly, and won't be lost under any operation.
8.If your app requires Internet connectivity for its core functionality, notify users without an active Internet connection that one is required.
Additional Details
In Unity, you can use the Application.internetReachability property to test for an active Internet connection.
Other engines may require you to test the connection by attempting to reach a server.
Steps to Test
Expected Result
If app requires a connection to the Internet, an error message is displayed.
9.Network functions such as online gameplay or leaderboard is functional in Chinese network environment. ( For games released in Mainland China, the game servers should be set in Mainland China as well. And the data of Mainland China users can not be connected or exchanged with that of overseas users.)
Steps to Test
Expected Result
Multiplayer is available in online gameplay.
Each matchmaking time should be proper in online multiplayer session. Automatic cancel or specific notes for players should be given when waiting takes time.
Users are able to create/close/join multiplayer rooms.
10.The voice chat is functional.
Steps to Test
Launch the title and enable voice chat functions;
Expected Result
Voice chat is available.
Voice chat can be turned on/off through in-app settings (if supported).
11.Users must not get disconnected from a multiplayer match if they press the Home button or remove their HMD.
Steps to Test
Expected Result
User stays connected for at least 1 minute.
12.The app must continue to download content if the user removes the headset.
Additional Details
When a user removes their headset, the foreground app is paused, which means any downloads running in the app are also paused. In order for downloads to continue when a user removes their HMD, they must be done in the background. To meet this requirement, you can use Android DownloadManager (opens new window), or other similar utilities, to download in the background.
Steps to Test
Expected Result
The download in application should not be shut down.
13.The user must be able to reset their forward orientation.
Steps to Test
Expected Result
Forward orientation is reset.
14.Headlocked menus and UI elements are generally uncomfortable for the user and should be avoided. (Recommended)
Steps to Test
Expected Result
Nothing should be headlocked.
15.The app must use the QIYU provided payment channel to handle all the payment processing for the Apps hosted on the QIYU Platform.
Steps to Test
Launch app and check if there are payment channels.
Expected Result
There should be no payment channels that are not provided by the QIYU platform. ( Including payment portals, payment links, in-app purchases or in-app advertising.)
16.If the app involves additional purchased content, users should be able to pay and unlock the purchased content normally on the QIYU platform.
Testing steps
Launch app and purchase additional content.
Expected results
Users should be able to pay and use the purchased content normally on the QIYU platform.
17.If the app supports MRC, the phone screen should be consistent with in-app during MRC recording.
Testing steps
Expected results
Users can use the MRC function normally and the phone screen is consistent with in-app during MRC recording.
18.The versions of content amount/functionalities/gameplay, etc. offered in the apps should not be lower than the performance of other platforms in general circumstances.
The app must request the minimum number of permissions required to function and must not request permissions that are not supported by the QIYU headset. For the permissions that QIYU supports applying for storage space, location information, microphone.
Additional Details
The review team will be paying especially close attention to the list of permissions that Google considers dangerous, which includes camera, location, microphone, reading and writing external storage, and others.
For more information about permissions, see https://developer.android.com/guide/topics/permissions/overview.html (opens new window).
Steps to Test
$ aapt dump badging and search the output for uses-permission.Expected Result
There must be a rationale behind every permission your app requests in the app manifest.
1.When configuring the submission metadata for your app, it must meet the requirements for either sitting, standing, or roomscale play modes.
Steps to Test
Expected Result
Sitting: no action requires you to stand or reach down to the ground.
Standing: You are able to interact with all gelements while standing, turning around, or reaching within a 2 x 2 (m²) play area.
Roomscale: The app must be completely usable within a 2 x 2 (m²) play area.
2.In the in-site mode, users can run and interact with the app normally within the play zone.In custom mode, users can run and interact with the app normally within the play zone.
Steps to Test
Launch the title, set the minimum play zone and activate it.
Expected Result
When the play zone is activated, users should be given a clear indication after stepping out of the play zone.
Users can run and interact with the app normally within the play zone.
3.If users move out of the play zone, the app could run as normal when returning or resetting the zone.
Steps to Test
Expected Result
The app could still run normally when users move back into the play zone.
The app could still run normally after users set a new play zone.
4. Notice should be given when the play zone is closed.
Steps to Test
Close the play zone and launch the title;
Expected Result
A clear and prominent security indication needs to be provided if the play zone is detected to be closed.
1.In-app menus should be activated with the menu button on the left QIYU controller. (Recommended)
Steps to Test
Expected Result
App should open an in-app menu, if applicable.
2.When picking up objects within the app, use the controller’s grip button rather than the trigger button. (Recommended)
Steps to Test
Expected Result
You use the grip button to pick up objects.
3.In-application hands and controllers should line up with the user’s real-world counterparts in position and orientation as closely as possible.
Steps to Test
While using your app, hold your hands in front of your face and raise your headset slightly so you can compare your real-world hands and your virtual hands. Repeat this process with your hands at different angles and positions in order to observe and correct any disparities.
Expected Result
In-application hands should match your real-world hands.
4. Screen capture (fast screen capture) or screen recording (fast screen recording) is available without blocking the app process.
Steps to Test
Expected Result
Screen capture (fast screen capture) or screen recording (fast screen recording) is available without blocking the app process.
The process will not call up the in-app menu, causing the application screen to be obscured.
