自 2025 年 3 月 27 日起,我们建议您使用 android-latest-release
而非 aosp-main
构建 AOSP 并为其做出贡献。如需了解详情,请参阅 AOSP 的变更。
用于头部追踪延迟测试的 CTS 验证程序
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Android 15 及更高版本包含用于检查空间音频头部追踪延迟合规性的 CTS 验证程序测试。
要求
在运行 CTS 验证程序以检查头部追踪延迟之前,请确保您有以下设备:
设置测试装置
本部分总结了测试装置的设置步骤。如需详细了解各个步骤,请参阅 Google 空间音频装置硬件 3.0 用户指南。
- 按照录音设置部分中的说明,使用 Linux 计算机和 DUT 设置测试装置。
- 与您的 Google TAM 联系,以便将最新版本的头部追踪延迟测试装置自动化软件下载到您的 Linux 计算机。
- 按照 PC 软件环境设置部分中的说明设置软件。
- 确保在 DUT 上安装了兼容版本的 CTS 验证程序应用。
- 确保 DUT 和头戴式耳机已连接,并且空间音频功能已启用。
- 确保已启用头戴式耳机的入耳检测功能,如入耳式耳机近程传感器部分中所述。
运行头部追踪延迟测试
按照常规说明中的说明访问 CTS 验证程序头部追踪延迟测试。
若要运行 CTS 验证程序头部追踪延迟测试,请按以下步骤操作:
按照 Google 空间音频装置硬件 3.0 用户指南中自动 HTL 测量部分中的说明运行自动化脚本。
测试完成后,Linux 计算机会将测试结果发送到 DUT 上的 CTS 验证程序应用。
报告测试结果:
- 如果测试屏幕显示 Pass,则表示通过测试。
- 如果测试屏幕显示 Fail,则表示测试失败。
- 如果测试界面显示重新测试,请重新运行测试。如果测试界面在多次测试中始终显示重新测试,请根据用户指南检查您的测试设置。
如需诊断测试代码结果,您可以使用头部追踪延迟测试装置的自动化软件。如需了解详情,请参阅访问沉浸式音频代码。
文档
访问沉浸式音频代码
如需在头部追踪延迟测试中使用头部追踪延迟测试装置所需的自动化软件,请填写并提交沉浸式音频代码访问权限申请表。提交表单后,请等待 5 分钟,以便我们向您授予对 HPS-Spatial-Audio 代码库的访问权限。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-05-08。
[null,null,["最后更新时间 (UTC):2025-05-08。"],[],[],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."]]