Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP. For more information, see Changes to AOSP.
CTS Verifier for head tracking latency test
Stay organized with collections
Save and categorize content based on your preferences.
Android 15 and higher includes a CTS Verifier test for
spatial audio head tracking latency compliance.
Requirements
Before running CTS Verifier for head tracking latency, ensure that you have the
following equipment:
Set up the test rig
This section summarizes the setup steps for the test rig. For detailed
instructions on each step, refer to the
Google Spatial Audio Rig HW3.0 User Guide.
- Follow the Audio Recording Setup section
to set up the test rig with the Linux computer and DUT.
- Contact your Google TAM to download the latest version of the head tracking latency
test rig automation software to your Linux computer.
- Set up the software using the instructions in the
PC SW environment setup section.
- Ensure that the a compatible version of the CTS Verifier app is installed on
the DUT.
- Ensure that the DUT and the headphones are connected and that the
spatial audio feature is enabled.
- Ensure that the in-ear
detection by the headphones is enabled as described in the
Earbuds proximity sensor section.
Run the head tracking latency test
Access the CTS Verifier head tracking latency test following the instructions in
General instructions.
To run the CTS Verifier head tracking latency test, follow these steps:
Run the automation scripting according to the instructions in the
Automatic HTL Measurements section of the
Google Spatial Audio Rig HW3.0 User Guide.
When the testing is completed, the Linux computer sends the test results
to the CTS Verifier app on the DUT.
Report test results:
- If the test screen displays Pass, report the test as passed.
- If the test screen displays Fail, report the test as failed.
- If the test screen displays Retest, rerun the test again. If the
test screen consistently displays Retest across multiple tests,
check your test setup according the user guides.
To diagnose test code results, you can use automation software for the head
tracking latency test rig. See Access to immersive audio code
for more information.
Documentation
Access to immersive audio code
To access the automation software required for the head tracking latency test
rig in the head tracking latency test, complete and submit the
Immersive Audio Code Access
form. After submitting the form, allow five minutes for your access to the HPS-Spatial-Audio
codebase to be granted.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-06-12 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-12 UTC."],[],[],null,["# CTS Verifier for head tracking latency test\n\nAndroid 15 and higher includes a CTS Verifier test for\nspatial audio head tracking latency compliance.\n\nRequirements\n------------\n\nBefore running CTS Verifier for head tracking latency, ensure that you have the\nfollowing equipment:\n\n- Android-powered phone (the device under test (DUT)) that has verified Android API compatibility by successfully passing the CTS\n- Accompanied headset with the dynamic spatial audio (with head tracking) enabled\n- A head tracking latency test rig (available through [MM Solutions](https://www.mm-sol.com/android-spatial-audio-htl-test-rig/)).\n- An audio card ([Zoom H6essential](https://zoomcorp.com/en/us/handheld-recorders/handheld-recorders/h6essential/) strongly recommended).\n- Linux computer with three USB 2.0 compatible ports\n\n All connections to the DUT\n and test rig are through these ports. You can use a USB hub if your Linux\n computer does not have enough integrated ports.\n\nSet up the test rig\n-------------------\n\nThis section summarizes the setup steps for the test rig. For detailed\ninstructions on each step, refer to the\n[Google Spatial Audio Rig HW3.0 User Guide](/static/docs/compatibility/cts/Google_SpatialAudio_User_Guide_20240409.pdf).\n\n1. Follow the **Audio Recording Setup** section to set up the test rig with the Linux computer and DUT.\n2. Contact your Google TAM to download the latest version of the head tracking latency test rig automation software to your Linux computer.\n3. Set up the software using the instructions in the **PC SW environment setup** section.\n4. Ensure that the a compatible version of the CTS Verifier app is installed on the DUT.\n5. Ensure that the DUT and the headphones are connected and that the spatial audio feature is enabled.\n6. Ensure that the in-ear detection by the headphones is enabled as described in the **Earbuds proximity sensor** section.\n\nRun the head tracking latency test\n----------------------------------\n\nAccess the CTS Verifier head tracking latency test following the instructions in\n[General instructions](/docs/compatibility/cts/audio-tests#general-instructions).\n\nTo run the CTS Verifier head tracking latency test, follow these steps:\n\n1. Run the automation scripting according to the instructions in the\n **Automatic HTL Measurements** section of the\n [Google Spatial Audio Rig HW3.0 User Guide](/static/docs/compatibility/cts/Google_SpatialAudio_User_Guide_20240409.pdf).\n\n2. When the testing is completed, the Linux computer sends the test results\n to the CTS Verifier app on the DUT.\n\n3. Report test results:\n\n - If the test screen displays **Pass**, report the test as passed.\n - If the test screen displays **Fail**, report the test as failed.\n - If the test screen displays **Retest** , rerun the test again. If the test screen consistently displays **Retest** across multiple tests, check your test setup according the user guides.\n\nTo diagnose test code results, you can use automation software for the head\ntracking latency test rig. See [Access to immersive audio code](#immersive-audio-code-access)\nfor more information.\n\nDocumentation\n-------------\n\n- [Google Spatial Audio Rig HW3.0 User Guide](/static/docs/compatibility/cts/Google_SpatialAudio_User_Guide_20240409.pdf)\n\nAccess to immersive audio code\n------------------------------\n\nTo access the automation software required for the head tracking latency test\nrig in the head tracking latency test, complete and submit the\n[Immersive Audio Code Access](https://docs.google.com/forms/d/e/1FAIpQLScpyzvGkkNOjDsvidKLOduRosrK2tEKC11nCbcD-dm_RgiSzg/viewform)\nform. After submitting the form, allow five minutes for your access to the [HPS-Spatial-Audio](https://partner-code.googlesource.com/HPS-Spatial-Audio)\ncodebase to be granted."]]
