自 2025 年 3 月 27 日起,我們建議您使用 android-latest-release
而非 aosp-main
建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
頭部追蹤延遲測試的 CTS 驗證器
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Android 15 以上版本包含 CTS 驗證工具測試,可檢查空間音訊頭部追蹤延遲符合性。
需求條件
執行 CTS Verifier 以測試頭部追蹤延遲時間前,請確認您擁有下列設備:
設定測試裝置
本節將概要說明測試架的設定步驟。如需各步驟的詳細操作說明,請參閱 Google 空間音訊 Rig HW3.0 使用者指南。
- 請按照「音訊錄製設定」一節的說明,使用 Linux 電腦和 DUT 設定測試裝置。
- 請與 Google TAM 聯絡,將最新版的頭部追蹤延遲測試裝置自動化軟體下載到 Linux 電腦。
- 按照「PC SW 環境設定」一節中的操作說明設定軟體。
- 確認 DUT 已安裝相容版本的 CTS Verifier 應用程式。
- 確認 DUT 和耳機已連線,且空間音訊功能已啟用。
- 請確認耳機已啟用入耳偵測功能,如「耳機鄰近感應器」一節所述。
執行頭部追蹤延遲測試
按照「一般操作說明」中的指示,存取 CTS 驗證工具的頭部追蹤延遲測試。
如要執行 CTS 驗證工具的頭部追蹤延遲測試,請按照下列步驟操作:
按照 Google 空間音訊攝影棚 HW3.0 使用手冊的「自動 HTL 測量」一節說明,執行自動化指令碼。
測試完成後,Linux 電腦會將測試結果傳送至 DUT 上的 CTS Verifier 應用程式。
回報測試結果:
- 如果測試畫面顯示「Pass」,請將測試結果回報為「通過」。
- 如果測試畫面顯示「Fail」,請將測試結果回報為失敗。
- 如果測試畫面顯示「Retest」,請再次執行測試。如果在多個測試中,測試畫面持續顯示「Retest」,請根據使用者指南檢查測試設定。
如要診斷測試程式碼結果,您可以使用自動化軟體進行頭部追蹤延遲時間測試。詳情請參閱「存取沉浸式音訊代碼」。
說明文件
取得沉浸式音訊程式碼
如要存取頭戴式追蹤延遲測試裝置中頭戴式追蹤延遲測試所需的自動化軟體,請填寫並提交沉浸式音訊程式碼存取權表單。提交表單後,請等候五分鐘,系統會在這個時間內授予您 HPS-Spatial-Audio 程式碼集的存取權。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-07-27 (世界標準時間)。"],[],[],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."]]