Android 9 相容性定義

一、簡介

本文檔列舉了裝置與 Android 9 相容必須滿足的要求。

「MUST」、「MUST NOT」、「REQUIRED」、「SHALL」、「SHALL NOT」、「SHOULD」、「SHOULD NOT」、「RECOMMENDED」、「MAY」和「OPTIONAL」的使用符合 IETF 標準RFC2119中定義的標準。

在本文檔中,「設備實現者」或「實現者」是指開發運行Android 9 的硬體/軟體解決方案的個人或組織。「設備實現者」或「實現者」是指如此開發的硬體/軟體解決方案。

要被視為與 Android 9 相容,裝置實作必須滿足此相容性定義中提出的要求,包括透過引用合併的任何文件。

如果第 10 節中所述的此定義或軟體測試是沉默的、不明確的或不完整的,則設備實現者有責任確保與現有實現的兼容性。

因此, Android 開源專案既是 Android 的參考實現,也是首選實現。強烈建議設備實現者最大程度地基於 Android 開源專案提供的「上游」原始程式碼來實現其實現。雖然假設某些組件可以替換為替代實現,但強烈建議不要遵循這種做法,因為通過軟體測試將變得更加困難。實作者有責任確保與標準 Android 實作完全行為相容,包括相容性測試套件。最後,請注意,本文檔明確禁止某些組件替換和修改。

本文檔中連結的許多資源直接或間接源自 Android SDK,並且在功能上與該 SDK 文件中的資訊相同。在任何情況下,如果本相容性定義或相容性測試套件與 SDK 文件不一致,則 SDK 文件被視為具有權威性。本文檔中連結資源中提供的任何技術細節均被視為本相容性定義的一部分。

1.1 文檔結構

1.1.1.設備類型的要求

第 2 部分包含適用於特定設備類型的所有要求。第 2 節的每個小節專用於特定的設備類型。

第 2 節之後的部分列出了所有普遍適用於任何 Android 裝置實現的其他要求。這些要求在本文檔中被稱為「核心要求」。

1.1.2.需求ID

需求 ID 是為 MUST 需求分配的。

  • 僅針對必須要求分配 ID。
  • 強烈建議的要求標記為 [SR],但未分配 ID。
  • ID 包括:設備類型 ID - 條件 ID - 要求 ID(例如 C-0-1)。

每個ID的定義如下:

  • 設備類型 ID(更多資訊請參閱2. 設備類型
    • C:核心(適用於任何 Android 裝置實現的要求)
    • H:Android手持設備
    • T:Android 電視設備
    • 答:Android 汽車實施
    • Tab:Android平板電腦實現
  • 條件ID
    • 當要求是無條件時,該ID設定為0。
    • 當要求是有條件的時,為第一個條件分配1,並且在相同部分和相同設備類型內數字加1。
  • 需求ID
    • ID從1開始,在相同的部分和相同的條件下加1。

1.1.3.第 2 部分中的要求 ID

第 2 部分中的要求 ID 以對應的部分 ID 開頭,後面跟著上述要求 ID。

  • 第 2 部分中的 ID 包括:部分 ID/設備類型 ID - 條件 ID - 要求 ID(例如 7.4.3/A-0-1)。

2. 設備類型

雖然 Android 開源專案提供了可用於各種裝置類型和外形規格的軟體堆疊,但也有少數裝置類型擁有相對完善的應用程式分發生態系統。

本節介紹這些設備類型以及適用於每種設備類型的附加要求和建議。

所有不適合任何所描述的裝置類型的 Android 裝置實作仍然必須滿足本相容性定義其他部分中的所有要求。

2.1 設備配置

有關不同設備類型的硬體配置的主要差異,請參閱本節中隨後的特定於設備的要求。

2.2.手持設備要求

Android 手持裝置是指通常手持使用的 Android 裝置實現,例如 MP3 播放器、手機或平板電腦。

如果 Android 裝置實現滿足以下所有條件,則將其歸類為手持裝置:

  • 擁有提供行動性的電源,例如電池。
  • 螢幕物理對角線尺寸在 2.5 至 8 吋範圍內。

本節其餘部分的附加要求特定於 Android 手持裝置實作。

注意:不適用於 Android 平板電腦裝置的要求標示 *。

2.2.1.硬體

手持設備實現:

  • [ 7.1 .1.1/H-0-1] 螢幕的實體對角線尺寸必須至少為 2.5 吋。
  • [ 7.1 .1.3/H-SR] 強烈建議提供使用者更改顯示尺寸的能力。(螢幕密度)

如果手持裝置實作聲稱透過Configuration.isScreenHdr()支援高動態範圍顯示,則它們:

  • [ 7.1 .4.5/H-1-1] 必須通告對EGL_EXT_gl_colorspace_bt2020_pqEGL_EXT_surface_SMPTE2086_metadataEGL_EXT_surface_CTA861_3_metadataVK_EXT_swapchain_colorspaceVK_EXT_hdr_metadata

手持設備實現:

  • [ 7.1 .5/H-0-1] 必須包括對由上游 Android 開源程式碼實現的遺留應用程式相容模式的支援。也就是說,設備實作不得更改啟動相容模式的觸發器或閾值,且不得更改相容模式本身的行為。
  • [ 7.2 .1/H-0-1] 必須包含對第三方輸入法編輯器 (IME) 應用程式的支援。
  • [ 7.2 .3/H-0-1] 必須提供主頁、最近存取和返回功能。
  • [ 7.2 .3/H-0-2] 必須將後退功能 ( KEYCODE_BACK ) 的正常按下事件和長按事件傳送至前台應用程式。這些事件不得由系統使用,並且可以由 Android 裝置外部觸發(例如連接到 Android 裝置的外部硬體鍵盤)。
  • [ 7.2 .4/H-0-1] 必須支援觸控螢幕輸入。
  • [ 7.2 .4/H-SR] 強烈建議啟動使用者選擇的輔助應用程序,即實現 VoiceInteractionService 的應用程序,或在長按KEYCODE_MEDIA_PLAY_PAUSEKEYCODE_HEADSETHOOK時處理ACTION_ASSIST的活動(如果前台活動沒有)處理那些長按事件。
  • [ 7.3 .1 /H-SR] 強烈建議包含 3 軸加速度計。

如果手持設備實現包括 3 軸加速計,則:

  • [ 7.3 .1/H-1-1] 必須能夠以至少 100 Hz 的頻率報告事件。

如果手持設備實作包括陀螺儀,它們:

  • [ 7.3 .4/H-1-1] 必須能夠以至少 100 Hz 的頻率報告事件。

可進行語音通話並在getPhoneType中指示除PHONE_TYPE_NONE以外的任何值的手持裝置實現:

  • [ 7.3 .8 /H] 應包括接近感測器。

手持設備實現:

  • [ 7.3 .12/H-SR] 建議支援 6 個自由度的位姿感測器。
  • [ 7.4 .3/H] 應包括對藍牙和藍牙 LE 的支援。

如果手持設備實施包括按流量計費的連接,則:

  • [ 7.4 .7/H-1-1] 必須提供資料保護模式。

手持設備實現:

  • [ 7.6 .1/H-0-1] 必須有至少 4 GB 的非揮發性儲存可用於應用程式私有資料(也稱為「/data」分割區)。
  • [ 7.6 .1/H-0-2] 當核心和使用者空間可用記憶體少於 1GB 時,必須為ActivityManager.isLowRamDevice()傳回「true」。

如果手持裝置實作聲明僅支援 32 位元 ABI:

  • [ 7.6 .1/H-1-1] 如果預設顯示器使用高達 qHD 的幀緩衝區解析度(例如 FWVGA),則核心和使用者空間可用的記憶體必須至少為 416MB。

  • [ 7.6 .1/H-2-1] 如果預設顯示器使用高達 HD+ 的幀緩衝區解析度(例如 HD、WSVGA),則核心和使用者空間可用的記憶體必須至少為 592MB。

  • [ 7.6 .1/H-3-1] 如果預設顯示器使用高達 FHD 的幀緩衝區解析度(例如 WSXGA+),則核心和使用者空間可用的記憶體必須至少為 896MB。

  • [ 7.6 .1/H-4-1] 如果預設顯示器使用高達 QHD 的幀緩衝區解析度(例如 QWXGA),則核心和使用者空間可用的記憶體必須至少為 1344MB。

如果手持設備實作聲明支援任何 64 位元 ABI(有或沒有任何 32 位元 ABI):

  • [ 7.6 .1/H-5-1] 如果預設顯示器使用高達 qHD 的幀緩衝區解析度(例如 FWVGA),則核心和使用者空間可用的記憶體必須至少為 816MB。

  • [ 7.6 .1/H-6-1] 如果預設顯示器使用高達 HD+ 的幀緩衝區解析度(例如 HD、WSVGA),則核心和使用者空間可用的記憶體必須至少為 944MB。

  • [ 7.6 .1/H-7-1] 如果預設顯示器使用高達 FHD 的幀緩衝區解析度(例如 WSXGA+),則核心和使用者空間可用的記憶體必須至少為 1280MB。

  • [ 7.6 .1/H-8-1] 如果預設顯示器使用高達 QHD 的幀緩衝區解析度(例如 QWXGA),則核心和使用者空間可用的記憶體必須至少為 1824MB。

請注意,上面的「核心和用戶空間可用的記憶體」是指除了已經專用於硬體組件(例如無線電、視訊等)的任何記憶體之外提供的記憶體空間,這些硬體元件在裝置實作上不受核心控制。

如果手持裝置實作包含小於或等於 1GB 可供核心和使用者空間使用的內存,則:

  • [ 7.6 .1/H-9-1] 必須聲明功能標誌android.hardware.ram.low
  • [ 7.6 .1/H-9-2] 必須具有至少 1.1 GB 的非揮發性儲存空間來儲存應用程式私有資料(也稱為「/data」分區)。

如果手持裝置實作包括可供核心和使用者空間使用的超過 1GB 的內存,則:

  • [ 7.6 .1/H-10-1] 必須有至少 4GB 的非揮發性儲存可用於應用程式私有資料(也稱為「/data」分割區)。
  • 應聲明功能標誌android.hardware.ram.normal

手持設備實現:

  • [ 7.6 .2/H-0-1] 不得提供小於 1 GiB 的應用程式共用儲存。
  • [ 7.7 .1/H] 應包括一個支援週邊模式的 USB 連接埠。

如果手持設備實作包括支援週邊模式的 USB 端口,則:

  • [ 7.7 .1/H-1-1] 必須實作 Android 開放附件 (AOA) API。

手持設備實現:

  • [ 7.8 .1/H-0-1] 必須包括麥克風。
  • [ 7.8 .2/H-0-1] 必須有音訊輸出並聲明android.hardware.audio.output

如果手持裝置實現能夠滿足支援 VR 模式的所有效能要求並包括對其的支持,那麼它們:

  • [ 7.9 .1/H-1-1] 必須聲明android.hardware.vr.high_performance功能標誌。
  • [ 7.9 .1/H-1-2] 必須包含一個實作android.service.vr.VrListenerService應用程序,VR 應用程式可以透過android.app.Activity#setVrModeEnabled啟用該服務。

2.2.2.多媒體

手持設備實作必須支援以下音訊編碼:

  • [ 5.1 .1/H-0-1] AMR-NB
  • [ 5.1 .1/H-0-2] AMR-WB
  • [ 5.1 .1/H-0-3] MPEG-4 AAC 設定檔 (AAC LC)
  • [ 5.1 .1/H-0-4] MPEG-4 HE AAC 設定檔 (AAC+)
  • [ 5.1 .1/H-0-5] AAC ELD(增強型低延遲 AAC)

手持設備實作必須支援以下音訊解碼:

  • [ 5.1 .2/H-0-1] AMR-NB
  • [ 5.1 .2/H-0-2] AMR-WB

手持設備實作必須支援以下視訊編碼並使其可供第三方應用程式使用:

  • [ 5.2 /H-0-1] H.264 AVC
  • [ 5.2 /H-0-2] VP8

手持設備實作必須支援以下視訊解碼:

  • [ 5.3 /H-0-1] H.264 AVC
  • [ 5.3 /H-0-2] H.265 HEVC
  • [ 5.3 /H-0-3] MPEG-4 SP
  • [ 5.3 /H-0-4] VP8
  • [ 5.3 /H-0-5] VP9

2.2.3.軟體

手持設備實現:

  • [ 3.2.3.1 /H-0-1] 必須有一個應用程式來處理 SDK 文件中所述的ACTION_GET_CONTENTACTION_OPEN_DOCUMENTACTION_OPEN_DOCUMENT_TREEACTION_CREATE_DOCUMENT意圖,並提供使用者使用DocumentsProvider API REE和ACTION_CREATE_DOCUMENT意圖,並提供使用者使用DocumentsProvider API
  • [ 3.4 .1/H-0-1] 必須提供android.webkit.Webview API 的完整實作。
  • [ 3.4 .2/H-0-1] 必須包含用於一般使用者 Web 瀏覽的獨立瀏覽器應用程式。
  • [ 3.8 .1/H-SR] 強烈建議實現一個支援應用程式內固定快捷方式、小部件和小部件功能的預設啟動器。
  • [ 3.8 .1/H-SR] 強烈建議實作一個預設啟動器,該啟動器可以透過ShortcutManager API 快速存取第三方應用程式提供的其他捷徑。
  • [ 3.8 .1/H-SR] 強烈建議包含一個顯示應用程式圖示徽章的預設啟動器應用程式。
  • [ 3.8 .2/H-SR] 強烈建議支援第三方應用程式小工具。
  • [ 3.8 .3/H-0-1] 必須允許第三方應用程式透過NotificationNotificationManager API 類別向使用者通知值得注意的事件。
  • [ 3.8 .3/H-0-2] 必須支援豐富的通知。
  • [ 3.8 .3/H-0-3] 必須支援平視通知。
  • [ 3.8 .3/H-0-4] 必須包含通知欄,使用戶能夠透過使用者功能(例如操作按鈕或所實現的控制面板)直接控制(例如回覆、暫停、關閉、封鎖)通知在 AOSP 中。
  • [ 3.8 .3/H-0-5] 必須在通知欄中顯示透過RemoteInput.Builder setChoices()提供的選項。
  • [ 3.8 .3/H-SR] 強烈建議在通知欄中顯示透過RemoteInput.Builder setChoices()提供的第一個選擇,而無需額外的使用者互動。
  • [ 3.8 .3/H-SR] 強烈建議當使用者展開通知欄中的所有通知時,在通知欄中顯示透過RemoteInput.Builder setChoices()提供的所有選項。
  • [ 3.8 .4/H-SR] 強烈建議在設備上實現助手來處理協助操作

如果手持設備實現支援輔助操作,則它們:

  • [ 3.8 .4/H-SR] 強烈建議使用長按HOME鍵作為啟動輔助應用程式的指定交互,如第 7.2.3 節所述。必須啟動使用者選擇的輔助應用程序,即實現VoiceInteractionService的應用程序,或處理ACTION_ASSIST意圖的活動。

如果 Android 手持裝置實現支援鎖定螢幕,則:

  • [ 3.8 .10/H-1-1] 必須顯示鎖定畫面通知,包括媒體通知範本。

如果手持裝置實現支援安全鎖定螢幕,則它們:

  • [ 3.9 /H-1-1] 必須實施 Android SDK 文件中定義的全部裝置管理策略。
  • [ 3.9 /H-1-2] 必須透過android.software.managed_users功能標誌聲明對託管配置文件的支持,除非設備配置為將自身報告為低 RAM 設備或分配內部 (不可移動)存儲作為共享存儲。

手持設備實現:

  • [ 3.10 /H-0-1] 必須支援第三方無障礙服務。
  • [ 3.10 /H-SR] 強烈建議在裝置上預先載入與 Switch Access 和 TalkBack(針對預先安裝的文字轉語音引擎支援的語言)功能相當或超過對講開放中提供的輔助功能服務的輔助服務來源項目
  • [ 3.11 /H-0-1] 必須支援安裝第三方 TTS 引擎。
  • [ 3.11 /H-SR] 強烈建議包含支援裝置上可用語言的 TTS 引擎。
  • [ 3.13 /H-SR] 強烈建議包含快速設定 UI 元件。

如果 Android 手持裝置實現聲明FEATURE_BLUETOOTHFEATURE_WIFI支持,則:

  • [ 3.16 /H-1-1] 必須支援配套設備配對功能。

2.2.4.性能和功率

  • [ 8.1 /H-0-1]一致的幀延遲。不一致的幀延遲或渲染幀延遲的發生頻率不得超過每秒 5 幀,且應低於每秒 1 幀。
  • [ 8.1 /H-0-2]使用者介面延遲。裝置實作必須透過在 36 秒內捲動 Android 相容性測試套件 (CTS) 定義的 10K 清單條目清單來確保低延遲使用者體驗。
  • [ 8.1 /H-0-3]任務切換。當多個應用程式已啟動時,啟動後重新啟動已執行的應用程式所用時間必須少於 1 秒。

手持設備實現:

  • [ 8.2 /H-0-1] 必須確保至少 5 MB/s 的順序寫入效能。
  • [ 8.2 /H-0-2] 必須確保至少 0.5 MB/s 的隨機寫入效能。
  • [ 8.2 /H-0-3] 必須確保至少 15 MB/s 的順序讀取效能。
  • [ 8.2 /H-0-4] 必須確保至少 3.5 MB/s 的隨機讀取效能。

如果手持設備實作包括改進 AOSP 中包含的設備電源管理的功能或擴展 AOSP 中包含的功能,則它們:

  • [ 8.3 /H-1-1] 必須提供使用者啟用和停用節電功能的功能。
  • [ 8.3 /H-1-2] 必須讓使用者顯示所有免於應用程式待機和 Doze 節能模式的應用程式。

手持設備實現:

  • [ 8.4 /H-0-1] 必須提供每個組件的電源配置文件,該配置文件定義每個硬體組件的電流消耗值以及組件隨著時間的推移造成的近似電池消耗,如Android 開源專案網站中所述。
  • [ 8.4 /H-0-2] 必須以毫安培小時 (mAh) 為單位報告所有功耗值。
  • [ 8.4 /H-0-3] 必須報告每個行程 UID 的 CPU 功耗。 Android開源專案透過uid_cputime核心模組實作來滿足要求。
  • [ 8.4 /H-0-4] 必須透過adb shell dumpsys batterystats shell 指令向應用程式開發人員提供此電量使用量。
  • [ 8.4 /H] 如果無法將硬體組件的電源使用歸因於應用程序,則應歸因於硬體組件本身。

如果手持裝置實作包括螢幕或視訊輸出,則它們:

2.2.5。安全模型

手持設備實現:

  • [ 9.1 /H-0-1] 必須允許第三方應用程式透過android.permission.PACKAGE_USAGE_STATS權限存取使用情況統計信息,並提供用戶可訪問的機制來授予或撤銷對此類應用程式的存取權限以響應android.settings.ACTION_USAGE_ACCESS_SETTINGS意圖。

當手持裝置實現支援安全鎖定螢幕時,它們:

  • [ 9.11 /H-1-1] 必須允許使用者選擇最短的睡眠逾時,即從解鎖狀態到鎖定狀態的轉換時間,為 15 秒或更短。
  • [ 9.11 /H-1-2] 必須提供使用者隱藏通知並停用除9.11.1 安全鎖定畫面中所述的主要驗證之外的所有形式的驗證的功能。 AOSP 滿足鎖定模式的要求。

2.3.電視需求

An Android Television device refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a “lean back” or “10-foot user介面").

如果 Android 裝置實現滿足以下所有條件,則將其歸類為電視:

  • 提供了一種機制來遠端控制可能距離使用者十英尺遠的顯示器上呈現的使用者介面。
  • 擁有對角線長度大於 24 吋的嵌入式螢幕顯示器,或包含視訊輸出端口,例如 VGA、HDMI、DisplayPort 或用於顯示的無線連接埠。

本節其餘部分的附加要求特定於 Android Television 裝置實作。

2.3.1.硬體

電視設備實現:

  • [ 7.2 .2/T-0-1] 必須支援方向鍵
  • [ 7.2 .3/T-0-1] 必須提供主頁和返回功能。
  • [ 7.2 .3/T-0-2] 必須將 Back 函數 ( KEYCODE_BACK ) 的正常按下事件和長按事件傳送到前台應用程式。
  • [ 7.2 .6.1/T-0-1] 必須包含對遊戲控制器的支援並聲明android.hardware.gamepad功能標誌。
  • [ 7.2 .7/T] 應提供一個遙控器,使用者可透過此遙控器存取非觸控導航核心導航鍵輸入。

如果電視設備實作包含陀螺儀,則它們:

  • [ 7.3 .4/T-1-1] 必須能夠以至少 100 Hz 的頻率報告事件。

電視設備實現:

  • [ 7.4 .3/T-0-1] 必須支援藍牙和藍牙 LE。
  • [ 7.6 .1/T-0-1] 必須有至少 4 GB 的非揮發性儲存可用於應用程式私有資料(也稱為「/data」分割區)。

如果電視設備實現包括支援主機模式的 USB 端口,則它們:

  • [ 7.5 .3/T-1-1] 必須支援透過此 USB 連接埠連接但不一定始終連接的外部攝影機。

如果電視設備實現是 32 位元:

  • [ 7.6 .1/T-1-1] 如果使用以下任何密度,則核心和使用者空間可用的記憶體必須至少為 896MB:

    • 小/普通螢幕上 400dpi 或更高
    • 大螢幕上 xhdpi 或更高
    • 超大螢幕上的 tvdpi 或更高

如果電視設備實現是 64 位元:

  • [ 7.6 .1/T-2-1] 如果使用以下任何密度,則核心和使用者空間可用的記憶體必須至少為 1280MB:

    • 小/普通螢幕上 400dpi 或更高
    • 大螢幕上 xhdpi 或更高
    • 超大螢幕上的 tvdpi 或更高

請注意,上面的「核心和用戶空間可用的記憶體」是指除了已經專用於硬體組件(例如無線電、視訊等)的任何記憶體之外提供的記憶體空間,這些硬體元件在裝置實作上不受核心控制。

電視設備實現:

  • [ 7.8 .1/T] 應包括麥克風。
  • [ 7.8 .2/T-0-1] 必須有音訊輸出並聲明android.hardware.audio.output

2.3.2.多媒體

電視設備實作必須支援以下音訊編碼格式:

  • [ 5.1 /T-0-1] MPEG-4 AAC 設定檔 (AAC LC)
  • [ 5.1 /T-0-2] MPEG-4 HE AAC 設定檔 (AAC+)
  • [ 5.1 /T-0-3] AAC ELD(增強型低延遲 AAC)

電視設備實作必須支援以下視訊編碼格式:

  • [ 5.2 /T-0-1] H.264
  • [ 5.2 /T-0-2] VP8

電視設備實現:

  • [ 5.2 .2/T-SR] 強烈建議支援每秒 30 幀的 720p 和 1080p 解析度影片的 H.264 編碼。

電視設備實作必須支援以下視訊解碼格式:

強烈建議電視設備實現支援以下視訊解碼格式:

電視設備實現必須支援 H.264 解碼,如第 5.3.4 節所述,標準視訊幀速率和解析度高達並包括:

  • [ 5.3.4 .4/T-1-1] 高清 1080p,每秒 60 幀,附 Basline Profile
  • [ 5.3.4 .4/T-1-2] 高清 1080p,每秒 60 幀,附 Main Profile
  • [ 5.3.4 .4/T-1-3] 高清 1080p,每秒 60 幀,High Profile Level 4.2

具有 H.265 硬體解碼器的電視設備實現必須支援 H.265 解碼,如第 5.3.5 節中詳述,標準視訊幀速率和解析度高達並包括:

  • [ 5.3.5 .4/T-1-1] 高清 1080p,每秒 60 幀,Main Profile Level 4.1

如果具有 H.265 硬體解碼器的電視設備實現支援 H.265 解碼和 UHD 解碼配置文件,則:

  • [ 5.3.5 .5/T-2-1] 必須支援具有 Main10 Level 5 Main Tier 設定檔的每秒 60 幀的 UHD 解碼設定檔。

電視設備實現必須支援 VP8 解碼,如第 5.3.6 節所述,標準視訊幀速率和解析度高達並包括:

  • [ 5.3.6 .4/T-1-1] 每秒 60 幀的高清 1080p 解碼配置文件

具有 VP9 硬體解碼器的電視設備實作必須支援 VP9 解碼,如第 5.3.7 節所述,標準視訊幀速率和解析度高達並包括:

  • [ 5.3.7 .4/T-1-1] 高清 1080p,每秒 60 幀,設定檔 0(8 位元色深)

如果具有 VP9 硬體解碼器的電視設備實現支援 VP9 解碼和 UHD 解碼配置文件,則:

  • [ 5.3.7 .5/T-2-1] 必須支援每秒 60 幀的 UHD 解碼配置文件,設定檔 0(8 位元色深)。
  • [ 5.3.7 .5/T-2-1] 強烈建議支援每秒 60 幀的 UHD 解碼配置文件,設定檔 2(10 位元色深)。

電視設備實現:

  • [ 5.5 .3/T-0-1] 必須支援系統主音量及支援輸出上的數位音訊輸出音量衰減,壓縮音訊直通輸出除外(裝置上未進行音訊解碼)。
  • [ 5.8 /T-0-1] 必須設定 HDMI 輸出模式以選擇所有有線顯示器 50Hz 或 60Hz 更新率可支援的最大解析度。
  • [ 5.8 /T-SR] 強烈建議為所有有線顯示器提供使用者可設定的 HDMI 更新率選擇器。
  • [ 5.8 /T-SR] 強烈建議支援安全流的同步解碼。至少,強烈建議同時解碼兩個串流。
  • [ 5.8 ] 應將 HDMI 輸出模式更新率設定為 50Hz 或 60Hz,具體取決於裝置銷售區域的所有有線顯示器的視訊更新率。

如果電視設備實現支援 UHD 解碼並支援外部顯示器,則:

  • [ 5.8 /T-1-1] 必須支援 HDCP 2.2。

如果電視設備實現不支援 UHD 解碼但支援外部顯示器,則:

  • [ 5.8 /T-2-1] 必須支援 HDCP 1.4

2.3.3.軟體

電視設備實現:

  • [ 3 /T-0-1] 必須聲明功能android.software.leanbackandroid.hardware.type.television
  • [ 3.4 .1/T-0-1] 必須提供android.webkit.Webview API 的完整實作。

如果 Android Television 裝置實作支援鎖定螢幕,則:

  • [ 3.8 .10/T-1-1] 必須顯示鎖定畫面通知,包括媒體通知範本。

電視設備實現:

如果電視設備實現報告功能android.hardware.audio.output ,則:

  • [ 3.11 /T-SR] 強烈建議包含支援裝置上可用語言的 TTS 引擎。
  • [ 3.11 /T-1-1] 必須支援安裝第三方 TTS 引擎。

電視設備實現:

  • [ 3.12 /T-0-1] 必須支援電視輸入框架。

2.3.4.性能和功率

  • [ 8.1 /T-0-1]一致的幀延遲。不一致的幀延遲或渲染幀延遲的發生頻率不得超過每秒 5 幀,且應低於每秒 1 幀。
  • [ 8.2 /T-0-1] 必須確保至少 5MB/s 的順序寫入效能。
  • [ 8.2 /T-0-2] 必須確保至少 0.5MB/s 的隨機寫入效能。
  • [ 8.2 /T-0-3] 必須確保至少 15MB/s 的順序讀取效能。
  • [ 8.2 /T-0-4] 必須確保至少 3.5MB/s 的隨機讀取效能。

如果電視設備實現包括 AOSP 中包含的改進設備電源管理的功能或擴展 AOSP 中包含的功能,則它們:

  • [ 8.3 /T-1-1] 必須提供使用者啟用和停用節電功能的功能。
  • [ 8.3 /T-1-2] 必須讓使用者顯示所有免於應用程式待機和 Doze 節能模式的應用程式。

電視設備實現:

  • [ 8.4 /T-0-1] 必須提供每個組件的電源配置文件,該配置文件定義每個硬體組件的電流消耗值以及組件隨著時間的推移造成的近似電池消耗,如Android 開源專案網站中所述。
  • [ 8.4 /T-0-2] 必須以毫安培小時 (mAh) 為單位報告所有功耗值。
  • [ 8.4 /T-0-3] 必須報告每個行程 UID 的 CPU 功耗。 Android開源專案透過uid_cputime核心模組實作來滿足要求。
  • [ 8.4 /T] 如果無法將硬體組件的電源使用歸因於應用程序,則應歸因於硬體組件本身。
  • [ 8.4 /T-0-4] 必須透過adb shell dumpsys batterystats shell 指令向應用程式開發人員提供此電量使用量。

2.4.手錶要求

Android Watch 裝置是指設計用於配戴在身體上(可能戴在手腕上)的 Android 裝置實現。

如果 Android 裝置實作符合以下所有條件,則被歸類為 Watch:

  • 螢幕的物理對角線長度在 1.1 到 2.5 吋之間。
  • 提供可佩戴在身上的機構。

本節其餘部分的附加要求特定於 Android Watch 裝置實作。

2.4.1.硬體

觀看設備實現:

  • [ 7.1 .1.1/W-0-1] 螢幕的實體對角線尺寸必須在 1.1 到 2.5 吋之間。

  • [ 7.2 .3/W-0-1] 必須具有可供使用者使用的 Home 功能和 Back 功能,除非處於UI_MODE_TYPE_WATCH狀態。

  • [ 7.2 .4/W-0-1] 必須支援觸控螢幕輸入。

  • [ 7.3 .1 /W-SR] 強烈建議包含 3 軸加速度計。

  • [ 7.4 .3/W-0-1] 必須支援藍牙。

  • [ 7.6 .1/W-0-1] 必須有至少 1 GB 的非揮發性儲存可用於應用程式私有資料(也稱為「/data」分割區)。

  • [ 7.6 .1/W-0-2] 必須至少有 416 MB 記憶體可供核心和使用者空間使用。

  • [ 7.8 .1/W-0-1] 必須包括麥克風。

  • [ 7.8 .2/W] 可以但不應該有音訊輸出。

2.4.2.多媒體

無額外要求。

2.4.3.軟體

觀看設備實現:

  • [ 3 /W-0-1] 必須宣告功能android.hardware.type.watch
  • [ 3 /W-0-2] 必須支援 uiMode = UI_MODE_TYPE_WATCH

觀看設備實現:

  • [ 3.8 .4/W-SR] 強烈建議在設備上實現助手來處理協助操作

觀看聲明android.hardware.audio.output功能標誌的裝置實作:

如果 Watch 裝置實作報告了 android.hardware.audio.output 功能,則:

  • [ 3.11 /W-SR] 強烈建議包含支援裝置上可用語言的 TTS 引擎。

  • [ 3.11 /W-0-1] 必須支援安裝第三方 TTS 引擎。

2.4.4.性能和功率

如果 Watch 設備實現包含 AOSP 中包含的改進設備電源管理的功能或擴展 AOSP 中包含的功能,則它們:

  • [ 8.3 /W-SR] 強烈建議為使用者提供顯示所有免於應用程式待機和打瞌睡省電模式的應用程式的功能。
  • [ 8.3 /W-SR] 強烈建議為使用者提供啟用和停用節電功能的功能。

觀看設備實現:

  • [ 8.4 /W-0-1] 必須提供每個組件的電源配置文件,該配置文件定義每個硬體組件的電流消耗值以及組件隨著時間的推移造成的近似電池消耗,如Android 開源專案網站中所述。
  • [ 8.4 /W-0-2] 必須以毫安培小時 (mAh) 為單位報告所有功耗值。
  • [ 8.4 /W-0-3] 必須報告每個行程 UID 的 CPU 功耗。 Android開源專案透過uid_cputime核心模組實作來滿足要求。
  • [ 8.4 /W-0-4] 必須透過adb shell dumpsys batterystats shell 指令向應用程式開發人員提供此電量使用量。
  • [ 8.4 /W] 如果無法將硬體組件的功耗歸因於應用程序,則應歸因於硬體組件本身。

2.5.汽車要求

Android Automotive 實作是指運行 Android 作為部分或全部系統和/或資訊娛樂功能的作業系統的車輛主機。

如果 Android 裝置實作聲明了android.hardware.type.automotive功能或滿足以下所有條件,則它們被歸類為汽車。

  • 作為汽車的一部分嵌入或可插入汽車。
  • 使用駕駛座排中的畫面作為主顯示幕。

本節其餘部分的附加要求是特定於 Android Automotive 裝置實作。

2.5.1.硬體

汽車設備實現:

  • [ 7.1 .1.1/A-0-1] 螢幕的實體對角線尺寸必須至少為 6 吋。
  • [ 7.1 .1.1/A-0-2] 螢幕尺寸佈局必須至少為 750 dp x 480 dp。

  • [ 7.2 .3/A-0-1] 必須提供主頁功能,並且可以提供返回和最近使用的功能。

  • [ 7.2 .3/A-0-2] 必須將 Back 函數 ( KEYCODE_BACK ) 的正常按下事件和長按事件傳送到前台應用程式。

  • [ 7.3 .1 /A-SR] 強烈建議包含 3 軸加速度計。

如果汽車設備實現包括 3 軸加速度計,則:

如果汽車設備的實作包括陀螺儀,則它們:

  • [ 7.3 .4 /A-1-1]必須能夠報告至少100 Hz的頻率。

汽車設備實現:

  • [ 7.3 .11/A-0-1]必須將目前齒輪作為SENSOR_TYPE_GEAR提供。

汽車設備實現:

  • [ 7.3 .11.2/a-0-1]必須支援定義為SENSOR_TYPE_NIGHT白天/夜間模式。
  • [ 7.3 .11.2/a-0-2] SENSOR_TYPE_NIGHT標誌的值必須與儀表板白天/夜間模式一致,並且應基於環境光感測器輸入。
  • 潛在的環境光感測器可能與光度計相同。

  • [ 7.3 .11.4/a-0-1]必須提供由SENSOR_TYPE_CAR_SPEED定義的車輛速度。

  • [ 7.3 .11.5/a-0-1]必須提供SENSOR_TYPE_PARKING_BRAKE定義的駐車煞車狀態。

  • [ 7.4 .3/a-0-1]必須支援藍牙,並應支援藍牙LE。

  • [ 7.4 .3/a-0-2] Android汽車實作必須支援以下藍牙設定檔:
    • 透過免持個人資料(HFP)打電話。
    • 透過音訊分發設定檔 (A2DP) 進行媒體播放。
    • 透過遠端控製設定檔 (AVRCP) 進行媒體播放控制。
    • 使用電話簿存取設定檔(PBAP)聯繫共用。
  • 強烈建議[ 7.4 .3/a-SR]支援訊息存取設定檔(MAP)。

  • [ 7.4 .5/a]應包括基於蜂窩網路的數據連接的支援。

  • [ 7.4 .5/a]可以使用系統API NetworkCapabilities#NET_CAPABILITY_OEM_PAID常數,此網路適用於系統應用程式。

  • [ 7.6 .1/a-0-1]必須至少有4 GB的非揮發性儲存空間可用於應用程式私人資料(又稱「/資料」分割區)。

汽車設備實現:

  • [ 7.6 .1/a]應格式化資料分割區,以提供改進的快閃記憶體儲存的效能和壽命,例如使用f2fs檔案系統。

如果汽車設備實現透過內部不可拆卸存儲提供共享的外部存儲,則它們:

  • 強烈建議[ 7.6 .1/a-sr]在外部記憶體上執行的操作,例如使用SDCardFS ,以減少I/O開銷。

如果汽車設備實現為32位:

  • [ 7.6 .1/a-1-1]如果使用以下密度,則核心和使用者空間可用的記憶體必須至少為512MB:

    • 在小/普通螢幕上280DPI或較低
    • LDPI或在超大螢幕上較低
    • 大螢幕上的MDPI或較低
  • [ 7.6 .1/a-1-2]如果使用以下任何密度,則核心和使用者空間的記憶體必須至少為608MB:

    • XHDPI或更高的小/正常螢幕
    • 大螢幕上的HDPI或更高
    • MDPI或更高的大螢幕
  • [ 7.6 .1/a-1-3]如果使用以下任何密度,則核心和使用者空間的記憶體必須至少為896MB:

    • 小/普通螢幕上的400DPI或更高
    • xhdpi或更高的大螢幕
    • TVDPI或更高的大螢幕
  • [ 7.6 .1/a-1-4]如果使用以下任何密度,則可用於核心和使用者空間的記憶體必須至少為1344MB:

    • 小/普通螢幕上的560DPI或更高
    • 大螢幕上的400DPI或更高
    • xhdpi或更高的大螢幕

如果汽車設備實現為64位:

  • [ 7.6 .1/a-2-1]如果使用以下密度,則核心和使用者空間可用的記憶體必須至少為816MB:

    • 在小/普通螢幕上280DPI或較低
    • LDPI或在超大螢幕上較低
    • 大螢幕上的MDPI或較低
  • [ 7.6 .1/a-2-2]如果使用以下密度,則核心和使用者空間可用的記憶體必須至少為944MB:

    • XHDPI或更高的小/正常螢幕
    • 大螢幕上的HDPI或更高
    • MDPI或更高的大螢幕
  • [ 7.6 .1/a-2-3]如果使用以下任何密度,則可以使用核心和使用者空間的記憶體至少為1280MB:

    • 小/普通螢幕上的400DPI或更高
    • xhdpi或更高的大螢幕
    • TVDPI或更高的大螢幕
  • [ 7.6 .1/a-2-4]如果使用以下任何密度,則核心和使用者空間的記憶體必須至少為1824MB:

    • 小/普通螢幕上的560DPI或更高
    • 大螢幕上的400DPI或更高
    • xhdpi或更高的大螢幕

請注意,上面的「可用的記憶體和用戶空間的記憶體」是指除了已經專用於硬體元件(例如無線電,視訊等)的任何記憶體之外提供的記憶體空間,而這些記憶體不在核心對裝置實現的控制下。

汽車設備實現:

  • [ 7.7 .1/a]應包括支援外圍模式的USB連接埠。

汽車設備實現:

  • [ 7.8 .1/A-0-1]必須包括麥克風。

汽車設備實現:

  • [ 7.8 .2/a-0-1]必須具有音訊輸出並聲明android.hardware.audio.output

2.5.2.多媒體

汽車設備實作必須支援以下音訊編碼:

  • [ 5.1 /a-0-1] MPEG-4 AAC設定檔(AAC LC)
  • [ 5.1 /a-0-2] MPEG-4 HE AAC概況(AAC+)
  • [ 5.1 /A-0-3] AAC ELD(增強的低延遲AAC)

汽車設備實作必須支援以下視訊編碼:

  • [ 5.2 /a-0-1] H.264 AVC
  • [ 5.2 /a-0-2] VP8

汽車設備實作必須支援以下視訊解碼:

  • [ 5.3 /a-0-1] H.264 AVC
  • [ 5.3 /A-0-2] MPEG-4 SP
  • [ 5.3 /a-0-3] VP8
  • [ 5.3 /a-0-4] VP9

強烈建議使用汽車設備實作來支援以下視訊解碼:

  • [ 5.3 /A-SR] H.265 HEVC

2.5.3.軟體

汽車設備實現:

  • [ 3 /A-0-1]必須宣告功能android.hardware.type.automotive

  • [ 3 /a-0-2]必須支援uimode = UI_MODE_TYPE_CAR

  • [ 3 /a-0-3] 必須支援android.car.*名稱空間。

  • [ 3.4 .1/a-0-1]必須提供android.webkit.Webview API的完整實作。

  • [ 3.8 .3/a-0-1]必須顯示使用通知的通知。當第三方應用程式要求時, Notification.CarExtender API。

  • 強烈建議[ 3.8 .4/a-SR]在設備上實施助手來處理輔助操作

  • 強烈建議使用[ ​​3.13 /A-SR]包括快速設定UI元件。

如果汽車設備的實現包括一個按鈕按鈕,則它們:

  • [ 3.8 .4/a-1-1]必須使用推動對話按鈕作為指定互動的簡短按下來啟動使用者選擇的輔助應用程序,換句話說,實現VoiceInteractionService的應用程式。

汽車設備實現:

  • [ 3.14 /A-0-1]必須包含一個UI框架,以使用第3.14節所述的媒體API支援第三方應用程式。

2.5.4.性能和功率

如果汽車設備實現包括改善AOSP中包含或擴展AOSP中包含的功能的設備電源管理的功能,則它們:

  • [ 8.3 /A-1-1]必須提供使用者負擔能力,以啟用和停用電池節省功能。
  • [ 8.3 /a-1-2]必須提供使用者負擔,以顯示所有免於應用程式備用和撥打加電功率模式的應用程式。

汽車設備實現:

  • [ 8.2 /a-0-1]必須根據每個進程的UID報告讀取和寫入非揮發性儲存的位元組數量,以便透過System Api android.car.storagemonitoring.CarStorageMonitoringManager向開發人員使用統計資料。 Android開源專案透過uid_sys_stats核心模組符合要求。
  • [ 8.4 /A-0-1]必須提供每個組件功率配置文件,該輪廓定義每個硬體組件的當前消耗值以及由組件隨時間推移所致的電池耗盡,如Android開源專案網站所記錄的那樣。
  • [ 8.4 /A-0-2]必須以毫安培小時(MAH)報告所有功耗值。
  • [ 8.4 /A-0-3]必須根據每個製程的UID報告CPU功耗。 Android開源專案透過uid_cputime核心模組實現滿足了需求。
  • [ 8.4 /a]如果無法將硬體組件用法歸因於應用程序,則應歸因於硬體組件本身。
  • [ 8.4 /a-0-4]必須透過adb shell dumpsys batterystats shell命令將此電源提供給應用程式開發人員。

2.5.5。安全模型

如果汽車設備實現支援多個用戶,則他們:

  • [ 9.5 /A-1-1]必須包含一個允許車輛系統提供的功能的來賓帳戶,而無需使用者登入。

如果汽車設備實現支援安全的鎖定螢幕,則它們:

汽車設備實現:

  • [ 9.14 /a-0-1]必須來自Android Framework車輛子系統(例如,允許清單允許的訊息類型和訊息來源)的網務訊息。
  • [ 9.14 /a-0-2]必須監視拒絕來自Android框架或第三方應用程式的服務攻擊。這種防禦惡意軟體會淹沒車輛網路的流量,這可能會導致車輛子系統故障。

2.6。平板電腦要求

Android平板電腦設備是指符合以下所有標準的Android裝置實作:

  • 通常是透過握住雙手來使用。
  • 沒有翻蓋或可轉換配置。
  • 設備使用的任何實體鍵盤實作都必須透過標準連接進行連接。
  • 具有提供移動性的電源,例如電池。
  • 實體對角線螢幕尺寸在7到18英吋的範圍內。

平板設備實現與手持設備實現相似。該部分中的例外和 *在本節中指定為參考。

2.4.1.硬體

螢幕尺寸

  • [ 7.1 .1.1/tab-0-1]必須在7到18英吋的範圍內具有一個螢幕。

最小記憶體和儲存(第7.6.1節)

在手持要求中列出的小/普通螢幕列出的螢幕密度不適用於平板電腦。

USB外圍模式(第7.7.1節)

如果平板電腦設備實現包括支援外圍模式的USB端口,則它們:

  • [ 7.7.1 /tab]可以實作Android Open Accessory(AOA)API。

虛擬實境模式(第7.9.1節)

虛擬實境高效能(第7.9.2節)

虛擬實境要求不適用於平板電腦。

3、軟體

3.1.託管 API 相容性

託管的 Dalvik 字節碼執行環境是 Android 應用程式的主要工具。 Android 應用程式介面 (API) 是向在託管執行時間環境中運行的應用程式公開的一組 Android 平台介面。

設備實現:

  • [C-0-1]必須提供完整的實現,包括所有由Android SDK所示的已記錄的API或在上游Android原始碼中使用「 @Systemapi」標記的任何API所示的任何已記錄的API。

  • [C-0-2]必須支援/保留以TESTAPI註釋(@TestApi)標記的所有類,方法和相關元素。

  • [C-0-3]不得省略任何託管的API,更改API介面或簽名,偏離已記錄的行為,或包括NO-OPS,除非此相容性定義明確允許。

  • [C-0-4]即使省略了Android包含API的某些硬體功能,也必須以合理的方式保持API並以合理的方式行事。有關此場景的具體要求,請參閱第 7 節

  • [C-0-5]必須限制使用隱藏API的第三方應用程式使用的使用,該應用程式以@hidden註釋裝飾為Android名稱空間中的API,但不用@SystemAPI@TestApi ,如SDK文件中所述並在相同的限制列表中使用每一個隱藏的API運送,與AOSP中適當的API級分支prebuilts/runtime/appcompat/ path中提供的同一限制列表中。但是他們:

    • 可以,如果缺乏隱藏的API或在裝置實作上有所不同,請將隱藏的API移至否定清單中,或從所有限制清單中省略它。
    • 可以,如果AOSP中尚未存在隱藏的API,請將隱藏的API新增到任何限制清單中。
    • 可以實現動態更新機制,該機制將隱藏的API從限制列表中移至限制性較小的列表中,除了允許列表。

3.1.1.安卓擴充

Android 支援擴充託管 API,同時保持相同的 API 等級版本。

  • [C-0-1] Android設備的實現必須預緊額的AOSP實現,共享庫ExtShared和Services ExtServices具有高於或等於每個API級別允許的最小版本。例如,執行 API 等級 24 的 Android 7.0 裝置實作必須至少包含版本 1。

3.1.2.安卓庫

由於Apache HTTP客戶端貶值,設備實作:

  • [C-0-1]不得將org.apache.http.legacy庫放置在bootclasspath中。
  • [C-0-2]只有在應用程式滿足以下條件之一時,才必須將org.apache.http.legacy庫新增至應用程式類別路徑:
    • 目標API等級28或更低。
    • 在其清單中聲明,它需要透過設定<uses-library> to org.apache.http.legacyandroid:name屬性來需要函式庫。

AOSP實施符合這些要求。

3.2.軟 API 相容性

除了第 3.1 節中的託管 API 之外,Android 還包括一個重要的僅運行時「軟」API,其形式為意圖、權限和 Android 應用程式的類似方面,這些方面無法在應用程式編譯時強制執行。

3.2.1.權限

  • [C-0-1]設備實施者必須支援並執行許可參考頁所記錄的所有權限常數。請注意,第 9 節列出了與 Android 安全模型相關的其他要求。

3.2.2.建構參數

Android API 在android.os.Build 類別中包含許多常數,用於描述目前裝置。

  • [C-0-1]為了在設備實現之間提供一致的,有意義的值,下表包括這些值必須符合的這些值的格式的其他限制。
範圍細節
版本.發布目前執行的 Android 系統的版本,採用人類可讀的格式。該欄位必須具有9中定義的字串值之一。
版本.SDK目前執行的 Android 系統的版本,採用第三方應用程式程式碼可存取的格式。對於Android 9,此欄位必須具有整數值9_int。
版本.SDK_INT目前執行的 Android 系統的版本,採用第三方應用程式程式碼可存取的格式。對於Android 9,此欄位必須具有整數值9_int。
版本.增量裝置實現者選擇的值,以人類可讀的格式指定目前正在執行的 Android 系統的特定版本。該值不得重複用於提供給最終用戶的不同建置。此欄位的典型用途是指示使用哪個版本號或原始碼控制變更標識符來產生版本。該欄位的具體格式沒有要求,但不能為 null 或空字串 ("")。
木板設備實現者選擇的值,以人類可讀的格式標識設備使用的特定內部硬體。此欄位的一個可能用途是指示為設備供電的板的特定版本。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9_-]+$」。
品牌反映最終用戶所知的與設備相關的品牌名稱的值。必須採用人類可讀的格式,並且應該代表設備的製造商或設備銷售的公司品牌。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9_-]+$」。
支援_ABIS本機程式碼的指令集名稱(CPU 類型 + ABI 約定)。請參閱第 3.3 節。本機 API 相容性
SUPPORTED_32_BIT_ABIS本機程式碼的指令集名稱(CPU 類型 + ABI 約定)。請參閱第 3.3 節。本機 API 相容性
SUPPORTED_64_BIT_ABIS本機程式碼的第二指令集(CPU 類型 + ABI 約定)的名稱。請參閱第 3.3 節。本機 API 相容性
CPU_ABI本機程式碼的指令集名稱(CPU 類型 + ABI 約定)。請參閱第 3.3 節。本機 API 相容性
CPU_ABI2本機程式碼的第二指令集(CPU 類型 + ABI 約定)的名稱。請參閱第 3.3 節。本機 API 相容性
裝置設備實現者選擇的值,包含標識硬體功能配置和設備工業設計的開發名稱或代號。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9_-]+$」。該設備名稱在產品的生命週期內不得更改。
指紋唯一標識此建置的字串。它應該是合理的人類可讀的。它必須遵循以下模板:

$(品牌)/$(產品)/
$(設備):$(版本.發佈)/$(ID)/$(版本.增量):$(類型)/$(標籤)

例如:

acme/我的產品/
mydevice:9/lmyxx/3359:使用者debug/test-keys

指紋不得包含空白字元。如果上述模板中包含的其他字段具有空白字符,則必須在構建指紋中將它們替換為另一個字符,例如下劃線(“_”)字符。此欄位的值必須可編碼為 7 位元 ASCII。

硬體硬體的名稱(來自核心命令列或/proc)。它應該是合理的人類可讀的。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9_-]+$」。
主持人一個字串,以人類可讀的格式唯一標識建構建構的主機。該欄位的具體格式沒有要求,但不能為 null 或空字串 ("")。
ID設備實現者選擇的標識符,用於引用特定版本,採用人類可讀的格式。該欄位可以與 android.os.Build.VERSION.INCRMENTAL 相同,但應該是一個對於最終用戶區分軟體版本足夠有意義的值。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9._-]+$」。
製造商產品原始設備製造商 (OEM) 的商品名稱。該欄位的具體格式沒有要求,但不能為 null 或空字串 ("")。該領域在產品的生命週期內不得改變。
模型設備實現者選擇的值,包含最終使用者已知的設備名稱。此名稱應與設備行銷和銷售給最終用戶時使用的名稱相同。該欄位的具體格式沒有要求,但不能為 null 或空字串 ("")。該領域在產品的生命週期內不得改變。
產品設備實施者選擇的值,包含特定產品 (SKU) 的開發名稱或程式碼名稱,該產品在同一品牌中必須是唯一的。必須是人類可讀的,但不一定供最終用戶查看。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9_-]+$」。該產品名稱在產品的生命週期內不得更改。
串口必須返回“未知”。
標籤由設備實現者選擇的以逗號分隔的標籤列表,可進一步區分建置。此欄位必須具有與三種典型 Android 平台簽章配置相對應的值之一:release-keys、dev-keys、test-keys。
時間表示建構發生時間的時間戳記的值。
類型由設備實現者選擇的值,指定建置的運行時配置。此欄位必須具有與三種典型 Android 運行時配置相對應的值之一:user、userdebug 或 eng。
使用者產生建置的使用者(或自動使用者)的名稱或使用者 ID。該欄位的具體格式沒有要求,但不能為 null 或空字串 ("")。
安全補丁指示建置的安全性修補程式等級的值。它必須表明該構建不會以任何方式受到指定 Android 公共安全公告中描述的任何問題的影響。它必須採用 [YYYY-MM-DD] 格式,與Android 公共安全公告Android 安全通報中記錄的定義字串相符,例如「2015-11-01」。
基本作業系統表示建置的 FINGERPRINT 參數的值,除 Android 公共安全公告中提供的補丁外,該值與此建置相同。它必須報告正確的值,如果這樣的建置不存在,則報告空字串(“”)。
引導程式裝置實現者選擇的值,以人為可讀取的格式識別裝置中使用的特定內部引導程式版本。此欄位的值必須可編碼為 7 位元 ASCII 並符合正規表示式「^[a-zA-Z0-9._-]+$」。
getradioversion()必須(或返回)設備實現者選擇的值,該值以人為可讀取的格式識別設備中使用的特定內部無線電/數據機版本。如果裝置沒有任何內部收音機/數據機,則必須傳回null。此欄位的值必須編碼為7位元ASCII,並符合正規表示式「^[A-ZA-Z0-9 ._-,]+$。
geterial()必須(或返回)硬體序號,必須在具有相同型號和製造商的設備之間可用且獨特。此欄位的值必須編碼為7位元ASCII,並符合正規表示式「^[A-ZA-Z0-9 ._-,]+$。

3.2.3.意圖相容性

3.2.3.1.核心應用意圖

Android 意圖允許應用程式元件向其他 Android 元件請求功能。 Android 上游項目包括被視為核心 Android 應用程式的應用程式列表,這些應用程式實現了多種意圖模式來執行常見操作。

  • [C-0-1]裝置實作必須預先載入一個或多個具有意圖處理程序的應用程式或服務元件,對於由下列核心Android應用程式定義的所有公開意圖過濾模式:AOSP:

    • 英式鐘
    • 瀏覽器
    • 日曆
    • 聯絡方式
    • 畫廊
    • 全球搜尋
    • 啟動器
    • 音樂
    • 設定
3.2.3.2.意圖解析
  • [C-0-1]由於Android是一個可擴展的平台,設備實作必須允許第3.2.3.1節中引用的每個意圖模式(設定除外)被第三方應用程式覆蓋。預設情況下,上游Android開源實作允許這樣做。

  • [C-0-2] DVICE實施者不得將特殊特權附加到系統應用程式對這些意圖模式的使用,或防止第三方應用程式與這些模式的結合並控制這些模式。該禁止具體包括但不限於停用「選擇器」使用者介面,該介面允許使用者在全部處理相同意圖模式的多個應用程式之間進行選擇。

  • [C-0-3]設備實作必須為使用者提供使用者介面,以修改意圖的預設活動。

  • 但是,當預設活動為資料 URI 提供更具體的屬性時,裝置實作可以為特定 URI 模式(例如 http://play.google.com)提供預設活動。例如,指定資料 URI「http://www.android.com」的意圖過濾器模式比瀏覽器的「http://」核心意圖模式更具體。

Android 還包含一種機制,供第三方應用程式為某些類型的 Web URI 意圖聲明權威的預設應用程式連結行為。當在應用程式的意圖過濾器模式中定義此類權威聲明時,設備實作:

  • [C-0-4]必須嘗試透過執行在上游Android開源專案中實現的數位資產連結規格中定義的驗證步驟來驗證任何意圖過濾器。
  • [C-0-5]必須嘗試在安裝應用程式期間驗證意圖過濾器,並將所有成功驗證的URI意圖過濾器設定為其URIS的預設應用程式處理程序。
  • 如果成功驗證但其他候選 URI 過濾器驗證失敗,則可以將特定 URI 意圖過濾器設定為其 URI 的預設應用程式處理程序。如果裝置實作這樣做,它必須在設定選單中為使用者提供適當的每 URI 模式覆蓋。
  • 必須在設定中為使用者提供每個應用程式的應用程式連結控件,如下所示:
    • [C-0-6]使用者必須能夠整體上覆蓋應用程式的預設應用程式連結行為:始終打開,始終詢問或永遠不會打開,必須適用於所有候選URI意圖均等過濾器。
    • [C-0-7]使用者必須能夠查看候選URI意圖過濾器的清單。
    • 設備實作可以為使用者提供基於每個意圖過濾器覆蓋已成功驗證的特定候選 URI 意圖過濾器的能力。
    • [C-0-8]裝置實作必須為使用者提供檢視和覆蓋特定候選URI意圖過濾器的能力,如果裝置實作使某些候選URI意圖過濾器成功驗證,而其他人則可能會失敗。
3.2.3.3.意圖命名空間
  • [C-0-1]裝置實作不得包含任何使用Android中的動作,類別或其他金鑰字串的新意圖或廣播意圖模式來尊重任何新意圖或廣播的模式。或com.android。命名空間。
  • [C-0-2]裝置實現者不得包含任何使用動作,類別或其他金鑰字串的新意圖或廣播意圖模式來尊重任何新意圖或廣播意圖模式,否則不得包含任何Android元件。
  • [C-0-3]設備實現者不得更改或擴展第3.2.3.1節中列出的核心應用程式所使用的任何意圖模式。
  • 設備實作可以包括使用與其自己的組織明確相關的命名空間的意圖模式。該禁止類似於3.6 節中針對 Java 語言類別指定的禁止。
3.2.3.4.廣播意圖

第三方應用程式依靠平台廣播某些意圖,以通知它們硬體或軟體環境的變化。

設備實現:

  • [C-0-1]必須依照SDK文件中所述的適當系統事件來廣播公眾廣播意圖。請注意,此要求與第3.5節沒有衝突,因為SDK文件中也描述了背景應用程式的限制。
3.2.3.5.預設應用程式設定

Android 包含的設定可讓用戶輕鬆選擇預設應用程序,例如主螢幕或簡訊。

在有意義的情況下,設備實作必須提供類似的設定選單,並與 SDK 文件中所述的意圖過濾器模式和 API 方法相容,如下所示。

如果裝置實作報表android.software.home_screen ,則它們:

如果裝置實作報表android.hardware.telephony ,它們:

  • [C-2-1]必須提供一個設定選單,該選單將呼叫android.provider.Telephony.ACTION_CHANGE_DEFAULT意圖顯示一個對話框以更改預設的SMS應用程式。

  • [C-2-2]必須尊重android.telecom.action.CHANGE_DEFAULT_DIALER意圖顯示對話框,以允許使用者更改預設電話應用程式。

    • 必須使用用戶選擇的預設電話應用程式的UI進行傳入和傳出電話,除了緊急呼叫,它將使用預先設定的電話應用程式。
  • [C-2-3]必須尊重Android.telecom.action.change_phone_accounts的意圖,目的是提供使用者負擔來配置與PhoneAccounts相關的ConnectionServices ,以及預設的PhoneAccount,電信服務供應商將使用電信服務供應商來接聽即將發生的呼叫。 AOSP實作透過在「呼叫」設定選單中包含一個「呼叫帳戶選項」選單來滿足此要求。

如果裝置實作報表android.hardware.nfc.hce ,則它們:

如果裝置實作支援VoiceInteractionService ,並且使用該API一次安裝了多個應用程序,則它們:

3.2.4.輔助顯示的活動

如果設備實作允許在輔助顯示器上啟動正常的Android活動,則它們:

  • [C-1-1]必須設定android.software.activities_on_secondary_displays功能標誌。
  • [C-1-2]必須保證與主顯示器上執行的活動相似的API相容性。
  • [C-1-3]必須將新活動與啟動其啟動的活動相同的顯示,而新活動是在不透過ActivityOptions.setLaunchDisplayId() API指定目標顯示的情況下啟動的。
  • [C-1-4]當有Display.FLAG_PRIVATE標誌的顯示時,必須銷毀所有活動。
  • [C-1-5]如果調整顯示本身,則必須相應地調整VirtualDisplay上的所有活動。
  • 當文字輸入欄位專注於輔助顯示時,可以在主顯示器上顯示IME(輸入方法編輯器,一個使用戶輸入文字的使用者控制項)。
  • 應在支援觸控或鍵輸入時獨立於主顯示器上的輸入重點。
  • 應具有與該顯示相對應的android.content.res.Configuration ,以便顯示,正確操作並保持相容性,如果在輔助顯示上啟動了活動。

如果裝置實作允許在輔助顯示上啟動正常的Android活動,並且主要和次要顯示具有不同的Android.util.displaymetrics

  • [C-2-1]不可避免的活動(在AndroidManifest.xml中具有resizeableActivity=false )和針對API等級23或更低的應用程式在輔助顯示時不得允許。

如果裝置實作允許在輔助顯示器上啟動正常的Android活動,並且輔助顯示具有android.view.display.flag_private標誌:

  • [C-3-1]只有該顯示器上已經存在的顯示,系統和活動的擁有者才能啟動。每個人都可以啟動到具有android.view.display.flag_public標誌的顯示。

3.3.本機 API 相容性

本機程式碼相容性具有挑戰性。因此,設備實現者是:

  • [SR]強烈建議使用下游Android開源專案中列出的程式庫的實作。

3.3.1.應用程式二進位接口

託管 Dalvik 字節碼可以呼叫應用程式.apk檔案中提供的本機程式碼,作為針對適當設備硬體架構編譯的 ELF .so檔。由於本機程式碼高度依賴底層處理器技術,Android 在 Android NDK 中定義了許多應用程式二進位介面 (ABI)。

設備實現:

  • [C-0-1]必須與一個或多個定義的ABI相容,並與Android NDK實現相容性。
  • [C-0-2]必須使用標準Java本機介面(JNI)語意來包含在託管環境中執行的程式碼的支持,以呼叫本機程式碼。
  • [C-0-3]必須與來源相容(IE標頭相容)和二進位相容(對於ABI),並在下面的清單中使用每個必需的程式庫。
  • [C-0-5] MUST accurately report the native Application Binary Interface (ABI) supported by the device, via the android.os.Build.SUPPORTED_ABIS , android.os.Build.SUPPORTED_32_BIT_ABIS android.os.Build.SUPPORTED_64_BIT_ABIS ,每個逗號分開的ABIS列表從最多到最不受歡迎的列表。
  • [C-0-6]必須透過上述參數報告以下ABIS清單的子集,且不得在清單中報告任何ABI。

    • armeabi
    • armeabi-v7a
    • arm64-v8a
    • x86
    • x86-64
    • [C-0-7]必須製作以下所有函式庫(提供本機API),可用於應用程式包含本機程式碼的應用程式:

    • libaaudio.so(Aaudio本地音訊支援)

    • libandroid.so(原生 Android 活動支援)
    • libc(C 庫)
    • libcamera2ndk.so
    • libdl(動態連結器)
    • libEGL.so(原生 OpenGL 表面管理)
    • libGLESv1_CM.so (OpenGL ES 1.x)
    • libGLESv2.so(OpenGL ES 2.0)
    • libGLESv3.so (OpenGL ES 3.x)
    • libicui18n.so
    • 庫克庫克
    • libjnigraphics.so
    • liblog(Android 日誌記錄)
    • libmediandk.so(原生媒體 API 支援)
    • libm(數學庫)
    • libneuralnetworks.so(神經網路API)
    • libOpenMAXAL.so(OpenMAX AL 1.0.1 支援)
    • libOpenSLES.so(OpenSL ES 1.0.1 音訊支援)
    • libRS.so
    • libstdc++(對 C++ 的最低支援)
    • libvulkan.so(Vulkan)
    • libz(Zlib 壓縮)
    • JNI介面
  • [C-0-8]不得為上面列出的本機庫新增或刪除公共功能。

  • [C-0-9]必須列出其他直接暴露於/vendor/etc/public.libraries.txt中的第三方應用程式的非AOSP程式庫。
  • [C-0-10]不得將任何其他本機庫曝光,並在AOSP中以系統庫的形式實施並提供,並將其保留為24或更高的第三方應用程式。
  • [C-0-11]必須透過libGLESv3.so函式庫匯出所有OpenGL ES 3.1和Android擴充包函數符號。請注意,儘管必須存在所有符號,但第7.1.4.1節更詳細地描述了何時預期每個相應功能的完整實現的要求。
  • [C-0-12]必須為核心VULKAN 1.0功能符號的導出功能符號以及VK_KHR_surfaceVK_KHR_android_surfaceVK_KHR_swapchain ,VK_KHR_SWAPCHAIN, VK_KHR_maintenance1VK_KHR_get_physical_device_properties2 libvulkan.so請注意,儘管必須存在所有符號,但第7.1.4.2節更詳細地描述了何時預期每個相應功能的完整實現的要求。
  • 應使用上游 Android 開源專案中提供的源代碼和頭文件進行構建

請注意,未來的Android版本可能會引入其他ABIS的支援。

3.3.2. 32 位元 ARM 本機程式碼相容性

如果設備實施報告了armeabi Abi的支持,則它們:

  • [C-3-1]還必須支援armeabi-v7a並報告其支持,因為armeabi僅用於向後與較舊應用的兼容。

如果設備實現報告了armeabi-v7a ABI的支持,則用於使用此ABI的應用程序,則它們:

  • [C-2-1]必須在/proc/cpuinfo中包含以下行,並且即使其他ABI讀取了同一設備上的值,也不應更改同一設備上的值。

    • Features: ,然後是該裝置支援的任何選用ARMV7 CPU功能的清單。
    • CPU architecture:接著是描述設備最高支撐的ARM架構的整數(例如,對於ARMV8設備,「 8」)。
  • [C-2-2]即使在AMV8體系架構上實作ABI,無論是透過本機CPU支援或透過軟體模擬實現ABI,也必須隨時保持下列操作可用:

    • SWP和SWPB說明。
    • 設定指令。
    • CP15ISB,CP15DSB和CP15DMB屏障操作。
  • [C-2-3]必須包含高階SIMD (又稱霓虹燈)擴充的支援。

3.4.網路相容性

3.4.1.網頁視圖相容性

如果裝置實作提供了android.webkit.Webview API的完整實現,則它們:

  • [C-1-1]必須報告android.software.webview
  • [C-1-2]必須使用Android 9分支的上游Android開源專案的Chromium Project構建,以實現android.webkit.WebView API。
  • [C-1-3] WebView報告的用戶代理字串必須以這種格式:

    Mozilla/5.0(Linux; Android $(版本); [$(型號)] [build/$(build)]; wv)AppleWebkit/537.36(Khtml,例如Gecko)版本/4.0 $(Chromium__ver)Mobile Safari/537.36

    • $(VERSION) 字串的值必須與 android.os.Build.VERSION.RELEASE 的值相同。
    • $(型號)字串可能是空的,但是如果它不是空的,則必須具有與android.os.build.model相同的值。
    • 可能會省略“構建/$(build)”,但是如果存在,則$(build)字串必須與android.os.os.build.id的值相同。
    • $(CHROMIUM_VER) 字串的值必須是上游 Android 開源專案中 Chromium 的版本。
    • 設備實作可以在用戶代理字串中省略 Mobile。
  • WebView 元件應該包含對盡可能多的 HTML5 功能的支持,並且如果它支援該功能,則應該符合HTML5 規範

3.4.2.瀏覽器相容性

如果設備實作包括用於通用Web瀏覽的獨立瀏覽器應用程序,則它們:

  • [C-1-1]必須支援與HTML5相關的每個API:
  • [C-1-2]必須支援HTML5/W3C WebStorage API ,並應支援HTML5/W3C索引DB API 。請注意,隨著 Web 開發標準機構逐漸轉向支援 IndexedDB 而不是 Webstorage,IndexedDB 預計將成為 Android 未來版本中的必要組件。
  • 可以在獨立瀏覽器應用程式中運送自訂使用者代理字串。
  • 應在獨立瀏覽器應用程式上實施對HTML5盡可能多的支援(無論是基於上游WebKit瀏覽器應用程式還是第三方替代)。

但是,如果設備實作不包括獨立瀏覽器應用程序,則它們:

  • [C-2-1]仍必須支持第3.2.3.1節所述的公共意圖模式。

3.5. API 行為相容性

設備實現:

  • [C-0-9]必須確保對所有已安裝的應用程式應用API行為相容性,除非按照第3.5.1節所述的限制。
  • [C-0-10]不得實現僅適用於裝置實作者選擇的應用程式的API行為相容性的允許清單。

每個 API 類型(託管、軟體、本機和 Web)的行為必須與上游Android 開源專案的首選實作一致。一些特定的兼容性領域是:

  • [C-0-1]設備不得改變標準意圖的行為或語意。
  • [C-0-2]裝置不得改變特定類型的系統元件的生命週期或生命週期語意(例如服務,活動,content-provider等)。
  • [C-0-3]設備不能更改標準許可的語意。
  • 設備不得改變背景應用程式上強制執行的限制。更具體地說,對於背景應用程式:
    • [C-0-4]他們必須停止執行該應用程式註冊的回調,以從GnssMeasurementGnssNavigationMessage接收輸出。
    • [C-0-5]他們必須透過LocationManager API類別或WifiManager.startScan()方法對應用程式提供的更新頻率進行評分。
    • [C-0-6]如果該應用程式針對API等級25或更高,則它們不得允許在應用程式清單中為標準Android意圖的隱式廣播註冊廣播接收器,除非廣播意圖需要"signature"或「 ”或"signatureOrSystem" protectionLevel許可或在豁免清單中。
    • [C-0-7]如果該應用程式針對API等級25或更高,則必須停止應用程式的背景服務,就像該應用程式稱為stopSelf()方法一樣,除非將應用程式放置在臨時允許清單上處理使用者可見的任務。
    • [C-0-8]如果該應用程式針對25級或更高的API級別,則必須釋放該應用程式保留的Wakelocks。
  • [C-0-9]設備必須傳回以下安全提供程序,作為來自Security.getProviders()方法的前七個數組值,以給定訂單和給定名稱(如Provider.getName()返回)和類,除非應用程式透過insertProviderAt()removeProvider()修改了清單。設備可能會傳回其他提供者以下指定的提供者清單。
    1. Androidnssp android.security.net.config.NetworkSecurityConfigProvider
    2. androidopenssl com.android.org.conscrypt.OpenSSLProvider
    3. certPathProvider sun.security.provider.CertPathProvider
    4. AndroidKeyStoreBcworkaround android.security.keystore.AndroidKeyStoreBCWorkaroundProvider
    5. BC com.android.org.bouncycastle.jce.provider.BouncyCastleProvider
    6. HarmonyJsse com.android.org.conscrypt.JSSEProvider
    7. AndroidKeystore android.security.keystore.AndroidKeyStoreProvider

上面的列表並不全面。相容性測試套件 (CTS) 測試平台的重要部分(但不是全部)的行為相容性。實作者有責任確保與 Android 開源專案的行為相容性。因此,裝置實現者應該盡可能使用透過 Android 開源專案提供的原始程式碼,而不是重新實作系統的重要部分。

3.5.1.背景限制

如果設備實作實現了AOSP中包含或擴展應用程式限制的應用程式限制,則它們:

  • 強烈建議[C-SR]提供用戶負擔能力,其中用戶可以看到受限制的應用程式清單。
  • [C-1-2]必須提供使用者負擔,以開啟 /關閉每個應用程式的限制。
  • [C-1-3]沒有系統健康行為不良的證據,不得自動應用限制,而是在發現不良系統健康行為(如卡住Wakelocks,長期運行的服務和其他標準)時可能會應用對應用程式的限制。標準可以由設備實施者確定,但必須與應用程式對系統健康的影響有關。與系統健康無關的其他標準,例如該應用程式在市場上缺乏知名度,不得用作標準。
  • [C-1-4]當使用者手動關閉應用程式限制時,不得自動對應用程式應用應用程式限制,並可能建議使用者應用應用程式限制。
  • [C-1-5]必須通知使用者是否將應用程式限制應用於應用程式。
  • [C-1-6]當限制應用程式呼叫此API時, ActivityManager.isBackgroundRestricted()必須傳回true
  • [C-1-7]不得限制使用者明確使用的頂端應用程式。
  • [C-1-8]當使用者明確開始使用曾經受到限制的應用程式時,必須暫停對應用程式的限制。
  • [C-1-9]必須透過UsageStats報告所有應用程式限制事件。如果設備實現擴展了AOSP中實現的應用程式限制,則必須遵循本文檔中所述的實作。

3.6. API命名空間

Android 遵循 Java 程式語言定義的套件和類別命名空間約定。為了確保與第三方應用程式的相容性,裝置實作者不得對這些套件命名空間進行任何禁止的修改(見下文):

  • java.*
  • javax.*
  • sun.*
  • android.*
  • androidx.*
  • com.android.*

也就是說,他們:

  • [C-0-1]不得透過更改任何方法或類別簽署或刪除類別或類別欄位來修改Android平台上公開暴露的API。
  • [C-0-2]不得將任何公開暴露的元素(例如類,接口,字段或方法)或現有類或接口的字段或方法)或測試或系統API添加到上述名稱空間中的API中。 「公開暴露的元素」是任何未用上游Android原始碼中使用的「 @Hide」標記裝飾的構造。

設備實施者可以修改API的基本實現,但進行了修改:

  • [C-0-3]不得影響任何公開暴露的API的既定行為和Java語言簽名。
  • [C-0-4]不得向開發人員做廣告或以其他方式接觸。

但是,裝置實作者可以在標準Android名稱空間之外新增自訂API,但自訂API:

  • [C-0-5]不得在另一個組織擁有或指涉另一個組織的命名空間中。例如,裝置實作者不得將 API 新增至com.google.*或類似的命名空間:只有 Google 可以做到。同樣,Google 不得將 API 新增至其他公司的命名空間。
  • [C-0-6]必須在Android共享庫中打包,以便只有明確使用它們的應用程式(透過<susta-library>機制)受到此類API的記憶體使用的增加影響。

如果設備實現者建議改進上述包命名空間之一(例如透過向現有 API 添加有用的新功能,或添加新 API),則實現者應該訪問source.android.com並開始貢獻更改和的過程代碼,根據該網站上的信息。

請注意,上述限制對應於 Java 程式語言中命名 API 的標準約定;本節的目的只是為了加強這些約定,並透過將其納入此相容性定義來使其具有約束力。

3.7.運行時相容性

設備實現:

  • [C-0-1]必須支援完整的Dalvik可執行執行(DEX)格式和Dalvik字節碼規範和語意

  • [C-0-2]必須配置Dalvik Runtimes,以根據上游Android平台分配內存,並按照下表指定。 (有關螢幕尺寸和螢幕密度定義,請參閱第 7.1.1 節。)

  • 應使用Android Runtime(ART),DALVIK可執行格式的參考上游實作以及參考實作的軟體包管理系統。

  • 應在各種執行模式和目標體系結構下執行模糊測試,以確保運行時的穩定性。請參閱Android開源專案網站中的JfuzzDexFuzz

請注意,下面指定的記憶體值被視為最小值,設備實作可以為每個應用程式分配更多記憶體。

螢幕佈局螢幕密度最小應用記憶體
安卓手錶120 dpi(LDPI) 32MB
160 dpi (mdpi)
213 dpi(電視dpi)
240 dpi(高清) 36MB
280dpi (280dpi)
320 dpi(xhdpi) 48MB
360dpi (360dpi)
400dpi (400dpi) 56MB
420 dpi (420dpi) 64MB
480 dpi (xxhdpi) 88MB
560dpi(560dpi) 112MB
640 dpi (xxxhdpi) 154MB
小/正常120 dpi(LDPI) 32MB
160 dpi (mdpi)
213 dpi(電視dpi) 48MB
240 dpi(高清)
280dpi (280dpi)
320 dpi(xhdpi) 80MB
360dpi (360dpi)
400dpi (400dpi) 96MB
420 dpi (420dpi) 112MB
480 dpi (xxhdpi) 128MB
560dpi(560dpi) 192MB
640 dpi (xxxhdpi) 256MB
大的120 dpi(LDPI) 32MB
160 dpi (mdpi) 48MB
213 dpi(電視dpi) 80MB
240 dpi(高清)
280dpi (280dpi) 96MB
320 dpi(xhdpi) 128MB
360dpi (360dpi) 160MB
400dpi (400dpi) 192MB
420 dpi (420dpi) 228MB
480 dpi (xxhdpi) 256MB
560dpi(560dpi) 384MB
640 dpi (xxxhdpi) 512MB
超大120 dpi(LDPI) 48MB
160 dpi (mdpi) 80MB
213 dpi(電視dpi) 96MB
240 dpi(高清)
280dpi (280dpi) 144MB
320 dpi(xhdpi) 192MB
360dpi (360dpi) 240MB
400dpi (400dpi) 288MB
420 dpi (420dpi) 336MB
480 dpi (xxhdpi) 384MB
560dpi(560dpi) 576MB
640 dpi (xxxhdpi) 768MB

3.8.使用者介面相容性

3.8.1.啟動器(主螢幕)

Android 包括啟動器應用程式(主畫面)並支援第三方應用程式來取代裝置啟動器(主畫面)。

如果設備實現允許第三方應用程式替換設備主螢幕,則它們:

  • [C-1-1]必須聲明平台功能android.software.home_screen
  • [C-1-2]當第三方應用程式使用<adaptive-icon>標籤以提供其圖示時,必須返回AdaptiveIconDrawable對象,並且呼叫了檢索圖示的PackageManager方法。

如果裝置實作包括支援快捷方式內應用程式固定的預設啟動器,則它們:

相反,如果裝置實作不支援快捷方式的應用程式內固定,則它們:

If device implementations implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the ShortcutManager API, they:

  • [C-4-1] MUST support all documented shortcut features (eg static and dynamic shortcuts, pinning shortcuts) and fully implement the APIs of the ShortcutManager API class.

If device implementations include a default launcher app that shows badges for the app icons, they:

  • [C-5-1] MUST respect the NotificationChannel.setShowBadge() API method. In other words, show a visual affordance associated with the app icon if the value is set as true , and do not show any app icon badging scheme when all of the app's notification channels have set the value as false .
  • MAY override the app icon badges with their proprietary badging scheme when third-party applications indicate support of the proprietary badging scheme through the use of proprietary APIs, but SHOULD use the resources and values provided through the notification badges APIs described in the SDK , such as the Notification.Builder.setNumber() and the Notification.Builder.setBadgeIconType() API.

3.8.2.小部件

Android supports third-party app widgets by defining a component type and corresponding API and lifecycle that allows applications to expose an “AppWidget” to the end user.

If device implementations support third-party app widgets, they:

  • [C-1-1] MUST declare support for platform feature android.software.app_widgets .
  • [C-1-2] MUST include built-in support for AppWidgets and expose user interface affordances to add, configure, view, and remove AppWidgets directly within the Launcher.
  • [C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See the App Widget DesignGuidelines in the Android SDK documentation for details.
  • MAY support application widgets on the lock screen.

If device implementations support third-party app widgets and in-app pinning of shortcuts, they:

3.8.3.通知

Android includes Notification and NotificationManager APIs that allow third-party app developers to notify users of notable events and attract users' attention using the hardware components (eg sound, vibration and light) and software ificlights and softnity the , 系統) 。

3.8.3.1. Presentation of Notifications

If device implementations allow third-party apps to notify users of notable events , they:

  • [C-1-1] MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware.例如,如果裝置實作包含振動器,則它必須正確實作振動 API。如果設備實作缺少硬件,則對應的 API 必須實作為無操作。此行為在第 7 節中有進一步詳細介紹。
  • [C-1-2] MUST correctly render all resources (icons, animation files, etc.) provided for in the APIs, or in the Status/System Bar icon style guide , although they MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation.
  • [C-1-3] MUST honor and implement properly the behaviors described for the APIs to update, remove and group notifications.
  • [C-1-4] MUST provide the full behavior of the NotificationChannel API documented in the SDK.
  • [C-1-5] MUST provide a user affordance to block and modify a certain third-party app's notification per each channel and app package level.
  • [C-1-6] MUST also provide a user affordance to display deleted notification channels.
  • [C-1-7] MUST correctly render all resources (images, stickers, icons, etc.) provided through Notification.MessagingStyle alongside the notification text without additional user interaction. For example, MUST show all resources including icons provided through android.app.Person in a group conversation that is set through setGroupConversation .
  • [C-SR] Are STRONGLY RECOMMENDED to automatically surface a user affordance to block a certain third-party app's notification per each channel and app package level after the user dismisses that notification multiple times.
  • SHOULD support rich notifications.
  • SHOULD present some higher priority notifications as heads-up notifications.
  • SHOULD have a user affordance to snooze notifications.
  • MAY only manage the visibility and timing of when third-party apps can notify users of notable events to mitigate safety issues such as driver distraction.

If device implementations support rich notifications, they:

  • [C-2-1] MUST use the exact resources as provided through the Notification.Style API class and its subclasses for the presented resource elements.
  • SHOULD present each and every resource element (eg icon, title and summary text) defined in the Notification.Style API class and its subclasses.

If device implementations support heads-up notifications: they:

  • [C-3-1] MUST use the heads-up notification view and resources as described in the Notification.Builder API class when heads-up notifications are presented.
  • [C-3-2] MUST display the actions provided through Notification.Builder.addAction() together with the notification content without additional user interaction as described in the SDK .
3.8.3.2. Notification Listener Service

Android includes the NotificationListenerService APIs that allow apps (once explicitly enabled by the user) to receive a copy of all notifications as they are posted or updated.

If device implementations report the feature flag android.hardware.ram.normal , they:

  • [C-1-1] MUST correctly and promptly update notifications in their entirety to all such installed and user-enabled listener services, including any and all metadata attached to the Notification object.
  • [C-1-2] MUST respect the snoozeNotification() API call, and dismiss the notification and make a callback after the snooze duration that is set in the API call.

If device implementations have a user affordance to snooze notifications, they:

  • [C-2-1] MUST reflect the snoozed notification status properly through the standard APIs such as NotificationListenerService.getSnoozedNotifications() .
  • [C-2-2] MUST make this user affordance available to snooze notifications from each installed third-party app's, unless they are from persistent/foreground services.
3.8.3.3. DND (Do not Disturb)

If device implementations support the DND feature, they:

  • [C-1-1] MUST implement an activity that would respond to the intent ACTION_NOTIFICATION_POLICY_ACCESS_SETTINGS , which for implementations with UI_MODE_TYPE_NORMAL it MUST be an activity where the user can grant or deny the app access to DND policy configurations.
  • [C-1-2] MUST, for when the device implementation has provided a means for the user to grant or deny third-party apps to access the DND policy configuration, display Automatic DND rules created by applications alongside the user-created and pre-defined rules.
  • [C-1-3] MUST honor the suppressedVisualEffects values passed along the NotificationManager.Policy and if an app has set any of the SUPPRESSED_EFFECT_SCREEN_OFF or SUPPRESSED_EFFECT_SCREEN_ON flags, it SHOULD indicate to the user that the visual effects are suppressed in the DND settings menu.

Android 包含的 API 允許開發人員將搜尋合併到他們的應用程式中,並將應用程式的資料公開到全域系統搜尋中。一般來說,此功能由單一系統範圍的使用者介面組成,允許使用者輸入查詢、在使用者鍵入時顯示建議並顯示結果。 Android API 允許開發人員重複使用此介面在自己的應用程式中提供搜索,並允許開發人員向通用全域搜尋使用者介面提供結果。

  • Android 裝置實作應該包括全域搜索,這是一個單一的、共享的、系統範圍的搜尋使用者介面,能夠響應用戶輸入提供即時建議。

If device implementations implement the global search interface, they:

  • [C-1-1] MUST implement the APIs that allow third-party applications to add suggestions to the search box when it is run in global search mode.

If no third-party applications are installed that make use of the global search:

  • The default behavior SHOULD be to display web search engine results and suggestions.

Android 還包含Assist API ,允許應用程式選擇與裝置上的助理共享當前上下文的多少資訊。

If device implementations support the Assist action, they:

  • [C-2-1] MUST indicate clearly to the end user when the context is shared, by either:
    • Each time the assist app accesses the context, displaying a white light around the edges of the screen that meet or exceed the duration and brightness of the Android Open Source Project implementation.
    • For the preinstalled assist app, providing a user affordance less than two navigations away from the default voice input and assistant app settings menu , and only sharing the context when the assist app is explicitly invoked by the user through a hotword or assist navigation key input.
  • [C-2-2] The designated interaction to launch the assist app as described in section 7.2.3 MUST launch the user-selected assist app, in other words the app that implements VoiceInteractionService , or an activity handling the ACTION_ASSIST intent.

3.8.5。 Alerts and Toasts

Applications can use the Toast API to display short non-modal strings to the end user that disappear after a brief period of time, and use the TYPE_APPLICATION_OVERLAY window type API to display alert windows as an overlay over other apps.

If device implementations include a screen or video output, they:

  • [C-1-1] MUST provide a user affordance to block an app from displaying alert windows that use the TYPE_APPLICATION_OVERLAY . The AOSP implementation meets this requirement by having controls in the notification shade.

  • [C-1-2] MUST honor the Toast API and display Toasts from applications to end users in some highly visible manner.

3.8.6。主題

Android 提供「主題」作為應用程式在整個 Activity 或應用程式中應用樣式的機制。

Android includes a “Holo” and "Material" theme family as a set of defined styles for application developers to use if they want to match the Holo theme look and feel as defined by the Android SDK.

If device implementations include a screen or video output, they:

  • [C-1-1] MUST NOT alter any of the Holo theme attributes exposed to applications.
  • [C-1-2] MUST support the “Material” theme family and MUST NOT alter any of the Material theme attributes or their assets exposed to applications.

Android 還包含一個「裝置預設」主題系列,作為一組定義的樣式,供應用程式開發人員在想要匹配裝置實現者定義的裝置主題的外觀和風格時使用。

Android 支援具有半透明系統列的變體主題,允許應用程式開發人員使用其應用程式內容填充狀態列和導覽列後面的區域。為了在此配置中實現一致的開發人員體驗,在不同的裝置實作中保持狀態列圖示樣式非常重要。

If device implementations include a system status bar, they:

  • [C-2-1] MUST use white for system status icons (such as signal strength and battery level) and notifications issued by the system, unless the icon is indicating a problematic status or an app requests a unless the icon is indicating a problematic status or an app requests a unless 保險。
  • [C-2-2] Android device implementations MUST change the color of the system status icons to black (for details, refer to R.style ) when an app requests a light status bar.

3.8.7.動態壁紙

Android 定義了一種元件類型以及相應的 API 和生命週期,允許應用程式向最終用戶公開一個或多個「動態桌布」 。動態壁紙是動畫、圖案或具有有限輸入功能的類似圖像,在其他應用程式後面顯示為壁紙。

如果硬體能夠以合理的幀速率運行所有動態壁紙,且沒有功能限制,並且不會對其他應用程式產生不利影響,則該硬體被認為能夠可靠地運行動態壁紙。如果硬體限制導致壁紙和/或應用程式崩潰、故障、消耗過多的 CPU 或電池電量,或以不可接受的低幀速率運行,則該硬體被視為無法運行動態壁紙。例如,某些動態桌布可能使用 OpenGL 2.0 或 3.x 上下文來渲染其內容。動態桌布將無法在不支援多個 OpenGL 上下文的硬體上可靠地運行,因為使用 OpenGL 上下文的動態桌布可能會與也使用 OpenGL 上下文的其他應用程式發生衝突。

  • 如上所述,能夠可靠地運行動態壁紙的設備實現應該實現動態壁紙。

If device implementations implement live wallpapers, they:

  • [C-1-1] MUST report the platform feature flag android.software.live_wallpaper.

3.8.8.活動切換

上游 Android 原始程式碼包括概覽畫面、系統級使用者介面,用於任務切換以及使用使用者上次離開應用程式時應用程式圖形狀態的縮圖顯示最近造訪的活動和任務。

Device implementations including the recents function navigation key as detailed in section 7.2.3 MAY alter the interface.

If device implementations including the recents function navigation key as detailed in section 7.2.3 alter the interface, they:

  • [C-1-1] MUST support at least up to 7 displayed activities.
  • 應至少一次顯示 4 個活動的標題。
  • [C-1-2] MUST implement the screen pinning behavior and provide the user with a settings menu to toggle the feature.
  • 應顯示最近的突出顯示顏色、圖示、螢幕標題。
  • 應顯示關閉可供性(“x”),但可以延遲顯示,直到使用者與螢幕互動。
  • SHOULD implement a shortcut to switch easily to the previous activity.
  • 當最近使用的功能鍵被點擊兩次時,應該會觸發兩個最近使用的應用程式之間的快速切換操作。
  • 當長按最近使用的功能鍵時,如果支持,應該觸發分割畫面多視窗模式。
  • 可以將關聯的最近內容顯示為一起移動的群組。
  • [SR] Are STRONGLY RECOMMENDED to use the upstream Android user interface (or a similar thumbnail-based interface) for the overview screen.

3.8.9。輸入管理

Android 包括對輸入管理的支援以及對第三方輸入法編輯器的支援。

If device implementations allow users to use third-party input methods on the device, they:

  • [C-1-1] MUST declare the platform feature android.software.input_methods and support IME APIs as defined in the Android SDK documentation.
  • [C-1-2] MUST provide a user-accessible mechanism to add and configure third-party input methods in response to the android.settings.INPUT_METHOD_SETTINGS intent.

If device implementations declare the android.software.autofill feature flag, they:

3.8.10.鎖定螢幕媒體控制

從 Android 5.0 開始,遠端控制用戶端 API 已被棄用,取而代之的是媒體通知模板,該模板允許媒體應用程式與鎖定螢幕上顯示的播放控制項整合。

3.8.11.螢幕保護程式(以前的夢想)

Android 支援互動式螢幕保護程序,以前稱為 Dreams。當連接到電源的裝置空閒或停靠在桌面擴充座時,螢幕保護程式允許使用者與應用程式互動。 Android Watch devices MAY implement screen savers, but other types of device implementations SHOULD include support for screen savers and provide a settings option for users to configure screen savers in response to the android.settings.DREAM_SETTINGS intent.

3.8.12.地點

If device implementations include a hardware sensor (eg GPS) that is capable of providing the location coordinates, they

3.8.13.統一碼和字體

Android includes support for the emoji characters defined in Unicode 10.0 .

If device implementations include a screen or video output, they:

  • [C-1-1] MUST be capable of rendering these emoji characters in color glyph.
  • [C-1-2] MUST include support for:
    • Roboto 2 font with different weights—sans-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, sans-serif-condensed, sans-serif-condensed-light for the languages available on the裝置.
    • Full Unicode 7.0 coverage of Latin, Greek, and Cyrillic, including the Latin Extended A, B, C, and D ranges, and all glyphs in the currency symbols block of Unicode 7.0.
  • SHOULD support the skin tone and diverse family emojis as specified in the Unicode Technical Report #51 .

If device implementations include an IME, they:

  • SHOULD provide an input method to the user for these emoji characters.

3.8.14.多視窗

If device implementations have the capability to display multiple activities at the same time, they:

  • [C-1-1] MUST implement such multi-window mode(s) in accordance with the application behaviors and APIs described in the Android SDK multi-window mode support documentation and meet the following requirements:
  • [C-1-2] Applications can indicate whether they are capable of operating in multi-window mode in the AndroidManifest.xml file, either explicitly via setting the android:resizeableActivity attribute to true or implicitly by having the targetSdkVersion > 24. Apps that explicitly set this attribute to false in their manifest MUST NOT be launched in multi-window mode. Older apps with targetSdkVersion < 24 that did not set this android:resizeableActivity attribute MAY be launched in multi-window mode, but the system MUST provide warning that the app may not work as expected in multi-window mode.
  • [C-1-3] MUST NOT offer split-screen or freeform mode if the screen height < 440 dp and the screen width < 440 dp.
  • 螢幕尺寸xlarge裝置實作應該支援自由格式模式。

If device implementations support multi-window mode(s), and the split screen mode, they:

  • [C-2-1] MUST preload a resizeable launcher as the default.
  • [C-2-2] MUST crop the docked activity of a split-screen multi-window but SHOULD show some content of it, if the Launcher app is the focused window.
  • [C-2-3] MUST honor the declared AndroidManifestLayout_minWidth and AndroidManifestLayout_minHeight values of the third-party launcher application and not override these values in the course of showing some content of the docked activity.

If device implementations support multi-window mode(s) and picture-in-picture multi-window mode, they:

  • [C-3-1] MUST launch activities in picture-in-picture multi-window mode when the app is: * Targeting API level 26 or higher and declares android:supportsPictureInPicture * Targeting API level 25 or lower and declares both android:resizeableActivity and android:supportsPictureInPicture .
  • [C-3-2] MUST expose the actions in their SystemUI as specified by the current PIP activity through the setActions() API.
  • [C-3-3] MUST support aspect ratios greater than or equal to 1:2.39 and less than or equal to 2.39:1, as specified by the PIP activity through the setAspectRatio() API.
  • [C-3-4] MUST use KeyEvent.KEYCODE_WINDOW to control the PIP window; if PIP mode is not implemented, the key MUST be available to the foreground activity.
  • [C-3-5] MUST provide a user affordance to block an app from displaying in PIP mode; the AOSP implementation meets this requirement by having controls in the notification shade.
  • [C-3-6] MUST allocate minimum width and height of 108 dp for the PIP window and minimum width of 240 dp and height of 135 dp for the PIP window when the Configuration.uiMode is configured as UI_MODE_TYPE_TELEVISION .

3.8.15. Display Cutout

Android supports a Display Cutout as described in the SDK document. The DisplayCutout API defines an area on the edge of the display that is not functional for displaying content.

If device implementations include display cutout(s), they:

  • [C-1-1] MUST only have cutout(s) on the short edge(s) of the device. Conversely, if the device's aspect ratio is 1.0(1:1), they MUST NOT have cutout(s).
  • [C-1-2] MUST NOT have more than one cutout per edge.
  • [C-1-3] MUST honor the display cutout flags set by the app through the WindowManager.LayoutParams API as described in the SDK.
  • [C-1-4] MUST report correct values for all cutout metrics defined in the DisplayCutout API.

3.9.設備管理

Android includes features that allow security-aware applications to perform device administration functions at the system level, such as enforcing password policies or performing remote wipe, through the Android Device Administration API .

If device implementations implement the full range of device administration policies defined in the Android SDK documentation, they:

  • [C-1-1] MUST declare android.software.device_admin .
  • [C-1-2] MUST support device owner provisioning as described in section 3.9.1 and section 3.9.1.1 .

3.9.1 準備配置

3.9.1.1 設備所有者配置

If device implementations declare android.software.device_admin , they:

  • [C-1-1] MUST support enrolling a Device Policy Client (DPC) as a Device Owner app as described below:
  • [C-1-2] MUST require some affirmative action during the provisioning process to consent to the app being set as Device Owner. Consent can be via user action or by some programmatic means during provisioning but it MUST NOT be hard coded or prevent the use of other Device Owner apps.

If device implementations declare android.software.device_admin , but also include a proprietary Device Owner management solution and provide a mechanism to promote an application configured in their solution as a "Device Owner equivalent" to the standard "Device Owner" as recognized by the standard Android DevicePolicyManager APIs, they:

  • [C-2-1] MUST have a process in place to verify that the specific app being promoted belongs to a legitimate enterprise device management solution and it has been already configured in the proprietary solution to have the right equist" 。
  • [C-2-2] MUST show the same AOSP Device Owner consent disclosure as the flow initiated by android.app.action.PROVISION_MANAGED_DEVICE prior to enrolling the DPC application as "Device Owner".
  • MAY have user data on the device prior to enrolling the DPC application as "Device Owner".
3.9.1.2 託管設定檔配置

If device implementations declare android.software.managed_users , they:

  • [C-1-1] MUST implement the APIs allowing a Device Policy Controller (DPC) application to become the owner of a new Managed Profile .

  • [C-1-2] The managed profile provisioning process (the flow initiated by android.app.action.PROVISION_MANAGED_PROFILE ) users experience MUST align with the AOSP implementation.

  • [C-1-3] MUST provide the following user affordances within the Settings to indicate to the user when a particular system function has been disabled by the Device Policy Controller (DPC):

    • 一致的圖示或其他使用者可供性(例如上游 AOSP 資訊圖示),用於表示特定設定何時受到設備管理員的限制。
    • 簡短的解釋訊息,由設備管理員透過setShortSupportMessage提供。
    • DPC 應用程式的圖示。

3.9.2 託管設定檔支持

If device implementations declare android.software.managed_users , they:

  • [C-1-1] MUST support managed profiles via the android.app.admin.DevicePolicyManager APIs.
  • [C-1-2] MUST allow one and only one managed profile to be created .
  • [C-1-3] MUST use an icon badge (similar to the AOSP upstream work badge) to represent the managed applications and widgets and other badged UI elements like Recents & Notifications.
  • [C-1-4] MUST display a notification icon (similar to the AOSP upstream work badge) to indicate when user is within a managed profile application.
  • [C-1-5] MUST display a toast indicating that the user is in the managed profile if and when the device wakes up (ACTION_USER_PRESENT) and the foreground application is within the managed profile.
  • [C-1-6] Where a managed profile exists, MUST show a visual affordance in the Intent 'Chooser' to allow the user to forward the intent from the managed profile to the primary user or vice versa, if enable Polid by the Device or vice versa, if enable Polid by the Device or vice versa, if enable Poli控制器。
  • [C-1-7] Where a managed profile exists, MUST expose the following user affordances for both the primary user and the managed profile:
    • 單獨核算主要使用者和託管設定檔的電池、位置、行動資料和儲存使用情況。
    • 獨立管理安裝在主要使用者或託管設定檔中的 VPN 應用程式。
    • 獨立管理安裝在主用戶或託管設定檔中的應用程式。
    • 對主要使用者或託管設定檔中的帳戶進行獨立管理。
  • [C-1-8] MUST ensure the preinstalled dialer, contacts and messaging applications can search for and look up caller information from the managed profile (if one exists) alongside those from the primary profile, if the Device Policy Controller permits it.
  • [C-1-9] MUST ensure that it satisfies all the security requirements applicable for a device with multiple users enabled (see section 9.5 ), even though the managed profile is not counted as another user in addition to the primary user.
  • [C-1-10] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile.
  • 當託管設定檔中的聯絡人顯示在預先安裝的通話記錄、通話中UI、進行中和未接來電通知、聯絡人和訊息應用程式中時,他們應該使用與指示託管設定檔應用程式相同的徽章。

3.9.3 Managed User Support

If device implementations declare android.software.managed_users , they:

  • [C-1-1] MUST provide a user affordance to logout from the current user and switch back to the primary user in multiple-user session when isLogoutEnabled returns true . The user affordance MUST be accessible from the lockscreen without unlocking the device.

3.10.無障礙

Android 提供了一個輔助功能層,可以幫助殘障用戶更輕鬆地導航其裝置。此外,Android 還提供平台 API,使輔助功能服務實現能夠接收使用者和系統事件的回調,並產生備用回饋機制,例如文字轉語音、觸覺回饋和軌跡球/方向鍵導航。

If device implementations support third-party accessibility services, they:

  • [C-1-1] MUST provide an implementation of the Android accessibility framework as described in the accessibility APIs SDK documentation.
  • [C-1-2] MUST generate accessibility events and deliver the appropriate AccessibilityEvent to all registered AccessibilityService implementations as documented in the SDK.
  • [C-1-3] MUST honor the android.settings.ACCESSIBILITY_SETTINGS intent to provide a user-accessible mechanism to enable and disable the third-party accessibility services alongside the preinstalled accessibility services.
  • [C-1-4] MUST add a button in the system's navigation bar allowing the user to control the accessibility service when the enabled accessibility services declare the AccessibilityServiceInfo.FLAG_REQUEST_ACCESSIBILITY_BUTTON . Note that for device implementations with no system navigation bar, this requirement is not applicable, but device implementations SHOULD provide a user affordance to control these accessibility services.

If device implementations include preinstalled accessibility services, they:

  • [C-2-1] MUST implement these preinstalled accessibility services as Direct Boot Aware apps when the data storage is encrypted with File Based Encryption (FBE).
  • SHOULD provide a mechanism in the out-of-box setup flow for users to enable relevant accessibility services, as well as options to adjust the font size, display size and magnification gestures.

3.11.文字轉語音

Android 包含的 API 允許應用程式使用文字轉語音 (TTS) 服務,並允許服務提供者提供 TTS 服務的實作。

If device implementations reporting the feature android.hardware.audio.output, they:

If device implementations support installation of third-party TTS engines, they:

  • [C-2-1] 必須提供使用者可供選擇的 TTS 引擎以在系統層級使用。

3.12.電視輸入框架

Android Television 輸入框架 (TIF)簡化了向 Android Television 裝置交付即時內容的過程。 TIF 提供標準 API 來建立控制 Android Television 裝置的輸入模組。

如果設備實現支援 TIF,則:

  • [C-1-1] MUST declare the platform feature android.software.live_tv .
  • [C-1-2] 必須支援所有 TIF API,以便可以在裝置上安裝和使用使用這些 API 和第三方基於 TIF 的輸入服務的應用程式。

3.13.快速設定

Android provides a Quick Settings UI component that allows quick access to frequently used or urgently needed actions.

If device implementations include a Quick Settings UI component, they:

  • [C-1-1] MUST allow the user to add or remove the tiles provided through the quicksettings APIs from a third-party app.
  • [C-1-2] MUST NOT automatically add a tile from a third-party app directly to the Quick Settings.
  • [C-1-3] MUST display all the user-added tiles from third-party apps alongside the system-provided quick setting tiles.

3.14。媒體介面

If device implementations include the UI framework that supports third-party apps that depend on MediaBrowser and MediaSession , they:

3.15。即時應用程式

Device implementations MUST satisfy the following requirements:

  • [C-0-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel set to "instant" .
  • [C-0-2] Instant Apps MUST NOT interact with installed apps via implicit intents unless one of the following is true:
    • The component's intent pattern filter is exposed and has CATEGORY_BROWSABLE
    • 操作是 ACTION_SEND、ACTION_SENDTO、ACTION_SEND_MULTIPLE 之一
    • The target is explicitly exposed with android:visibleToInstantApps
  • [C-0-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps.
  • [C-0-4] IInstalled Apps MUST NOT see details about Instant Apps on the device unless the Instant App explicitly connects to the installed application.

3.16。 Companion Device Pairing

Android includes support for companion device pairing to more effectively manage association with companion devices and provides the CompanionDeviceManager API for apps to access this feature.

If device implementations support the companion device pairing feature, they:

  • [C-1-1] MUST declare the feature flag FEATURE_COMPANION_DEVICE_SETUP .
  • [C-1-2] MUST ensure the APIs in the android.companion package is fully implemented.
  • [C-1-3] 必須提供使用者選擇/確認配套設備存在且可運作的功能。

3.17。 Heavyweight Apps

If device implementations declare the feature FEATURE_CANT_SAVE_STATE , then they:

  • [C-1-1] MUST have only one installed app that specifies cantSaveState running in the system at a time. If the user leaves such an app without explicitly exiting it (for example by pressing home while leaving an active activity the system, instead of pressing back with no remaining active activities in the system), then device implementations MUST prioritize that app in RAM as they do for other things that are expected to remain running, such as foreground services. While such an app is in the background, the system can still apply power management features to it, such as limiting CPU and network access.
  • [C-1-2] MUST provide a UI affordance to chose the app that won't participate in the normal state save/restore mechanism once the user launches a second app declared with cantSaveState attribute.
  • [C-1-3] MUST NOT apply other changes in policy to apps that specify cantSaveState , such as changing CPU performance or changing scheduling prioritization.

If device implementations don't declare the feature FEATURE_CANT_SAVE_STATE , then they:

  • [C-1-1] MUST ignore the cantSaveState attribute set by apps and MUST NOT change the app behavior based on that attribute.

4. 應用程式封裝相容性

Devices implementations:

  • [C-0-1] MUST be capable of installing and running Android “.apk” files as generated by the “aapt” tool included in the official Android SDK .
  • As the above requirement may be challenging, device implementations are RECOMMENDED to use the AOSP reference implementation's package management system.

設備實現:

  • [C-0-2] MUST support verifying “.apk” files using the APK Signature Scheme v3 , APK Signature Scheme v2 and JAR signing .
  • [C-0-3] MUST NOT extend either the .apk , Android Manifest , Dalvik bytecode , or RenderScript bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices.
  • [C-0-4] MUST NOT allow apps other than the current "installer of record" for the package to silently uninstall the app without any user confirmation, as documented in the SDK for the DELETE_PACKAGE permission.唯一的例外是處理PACKAGE_NEEDS_VERIFICATION意圖的系統套件驗證程式應用程式和處理ACTION_MANAGE_STORAGE意圖的儲存管理器應用程式。

  • [C-0-5] MUST have an activity that handles the android.settings.MANAGE_UNKNOWN_APP_SOURCES intent.

  • [C-0-6] MUST NOT install application packages from unknown sources, unless the app that requests the installation meets all the following requirements:

    • It MUST declare the REQUEST_INSTALL_PACKAGES permission or have the android:targetSdkVersion set at 24 or lower.
    • It MUST have been granted permission by the user to install apps from unknown sources.
  • SHOULD provide a user affordance to grant/revoke the permission to install apps from unknown sources per application, but MAY choose to implement this as a no-op and return RESULT_CANCELED for startActivityForResult() , if the device implementation does not want to allow users to have this choice. However, even in such cases, they SHOULD indicate to the user why there is no such choice presented.

  • [C-0-7] MUST display a warning dialog with the warning string that is provided through the system API PackageManager.setHarmfulAppWarning to the user before launching an activity in an application that has been mark before launching an PackageManager.setHarmfulAppWarning in an application that has been marked 之前有害。

  • SHOULD provide a user affordance to choose to uninstall or launch an application on the warning dialog.

5. 多媒體相容性

設備實現:

  • [C-0-1] MUST support the media formats, encoders, decoders, file types, and container formats defined in section 5.1 for each and every codec declared by MediaCodecList .
  • [C-0-2] MUST declare and report support of the encoders, decoders available to third-party applications via MediaCodecList .
  • [C-0-3] MUST be able to decode and make available to third-party apps all the formats it can encode. This includes all bitstreams that its encoders generate and the profiles reported in its CamcorderProfile .

設備實現:

  • SHOULD aim for minimum codec latency, in others words, they
    • SHOULD NOT consume and store input buffers and return input buffers only once processed.
    • 保留解碼緩衝區的時間不應超過標準(例如 SPS)指定的時間。
    • 保留編碼緩衝區的時間不應超過 GOP 結構所需的時間。

All of the codecs listed in the section below are provided as software implementations in the preferred Android implementation from the Android Open Source Project.

請注意,Google 和開放手機聯盟均未聲明這些編解碼器不受第三方專利的影響。打算在硬體或軟體產品中使用此原始碼的人請注意,此程式碼的實現(包括在開源軟體或共享軟體中)可能需要相關專利持有者的專利許可。

5.1.媒體編解碼器

5.1.1.音訊編碼

See more details in 5.1.3. Audio Codecs Details .

If device implementations declare android.hardware.microphone , they MUST support the following audio encoding:

  • [C-1-1] PCM/WAVE

5.1.2. Audio Decoding

See more details in 5.1.3. Audio Codecs Details .

If device implementations declare support for the android.hardware.audio.output feature, they must support decoding the following audio formats:

  • [C-1-1] MPEG-4 AAC Profile (AAC LC)
  • [C-1-2] MPEG-4 HE AAC Profile (AAC+)
  • [C-1-3] MPEG-4 HE AACv2 Profile (enhanced AAC+)
  • [C-1-4] AAC ELD (enhanced low delay AAC)
  • [C-1-11] xHE-AAC (ISO/IEC 23003-3 Extended HE AAC Profile, which includes the USAC Baseline Profile, and ISO/IEC 23003-4 Dynamic Range Control Profile)
  • [C-1-5] FLAC
  • [C-1-6] MP3
  • [C-1-7] MIDI
  • [C-1-8] Vorbis
  • [C-1-9] PCM/WAVE
  • [C-1-10] Opus

If device implementations support the decoding of AAC input buffers of multichannel streams (ie more than two channels) to PCM through the default AAC audio decoder in the android.media.MediaCodec API, the following MUST be supported:

  • [C-2-1] Decoding MUST be performed without downmixing (eg a 5.0 AAC stream must be decoded to five channels of PCM, a 5.1 AAC stream must be decoded to six channels of PCM).
  • [C-2-2] Dynamic range metadata MUST be as defined in "Dynamic Range Control (DRC)" in ISO/IEC 14496-3, and the android.media.MediaFormat DRC keys to configure the dynamic range-related behaviors of the audio decoder. The AAC DRC keys were introduced in API 21,and are: KEY_AAC_DRC_ATTENUATION_FACTOR , KEY_AAC_DRC_BOOST_FACTOR , KEY_AAC_DRC_HEAVY_COMPRESSION , KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_ENCODED_TARGET_LEVEL .

When decoding USAC audio, MPEG-D (ISO/IEC 23003-4):

  • [C-3-1] Loudness and DRC metadata MUST be interpreted and applied according to MPEG-D DRC Dynamic Range Control Profile Level 1.
  • [C-3-2] The decoder MUST behave according to the configuration set with the following android.media.MediaFormat keys: KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_DRC_EFFECT_TYPE .

MPEG-4 AAC, HE AAC, and HE AACv2 profile decoders:

  • MAY support loudness and dynamic range control using ISO/IEC 23003-4 Dynamic Range Control Profile.

If ISO/IEC 23003-4 is supported and if both ISO/IEC 23003-4 and ISO/IEC 14496-3 metadata are present in a decoded bitstream, then:

  • ISO/IEC 23003-4 metadata SHALL take precedence.

5.1.3. Audio Codecs Details

格式/編解碼器細節支援的文件類型/容器格式
MPEG-4 AAC 設定文件
(AAC LC)
Support for mono/stereo/5.0/5.1 content with standard sampling rates from 8 to 48 kHz.
  • 3GPP (.3gp)
  • MPEG-4(.mp4、.m4a)
  • ADTS raw AAC (.aac, ADIF not supported)
  • MPEG-TS (.ts, not seekable)
MPEG-4 HE AAC 設定檔 (AAC+) Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz.
MPEG-4 HE AACv2
設定檔(增強型 AAC+)
Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz.
AAC ELD(增強型低延遲AAC)支援單聲道/立體聲內容,標準取樣率為 16 至 48 kHz。
美國空軍司令部Support for mono/stereo content with standard sampling rates from 7.35 to 48 kHz. MPEG-4(.mp4、.m4a)
AMR-NB 8 kHz 時取樣率為 4.75 至 12.2 kbps 3GPP (.3gp)
AMR-WB 9 個速率,從 6.60 kbit/s 到 23.85 kbit/s,取樣頻率為 16 kHz
FLAC單聲道/立體聲(無多聲道)。取樣率高達 48 kHz(但在具有 44.1 kHz 輸出的裝置上建議高達 44.1 kHz,因為 48 至 44.1 kHz 下取樣器不包括低通濾波器)。推薦 16 位; 24 位元沒有套用抖動。限 FLAC (.flac)
MP3單聲道/立體聲 8-320Kbps 恆定 (CBR) 或可變位元速率 (VBR) MP3 (.mp3)
MIDI MIDI 類型 0 和 1。DLS 版本 1 和 2。XMF 和 Mobile XMF。支援鈴聲格式 RTTTL/RTX、OTA 和 iMelody
  • 類型 0 和 1(.mid、.xmf、.mxmf)
  • RTTTL/RTX(.rtttl、.rtx)
  • OTA (.ota)
  • iMelody (.imy)
沃爾比斯
  • 奧格 (.ogg)
  • Matroska(.mkv,Android 4.0+)
PCM/波16 位元線性 PCM(速率達到硬體限制)。設備必須支援 8000、11025、16000 和 44100 Hz 頻率下原始 PCM 錄製的取樣率。波形 (.wav)
作品Matroska (.mkv)、Ogg(.ogg)

5.1.4.影像編碼

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support encoding the following image encoding:

  • [C-0-1] JPEG
  • [C-0-2] PNG
  • [C-0-3] WebP

5.1.5。影像解碼

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support decoding the following image encoding:

  • [C-0-1] JPEG
  • [C-0-2] GIF
  • [C-0-3] PNG
  • [C-0-4] BMP
  • [C-0-5] WebP
  • [C-0-6] Raw
  • [C-0-7] HEIF (HEIC)

5.1.6。圖像編解碼器詳細信息

格式/編解碼器細節支援的文件類型/容器格式
JPEG基礎+漸進JPEG (.jpg)
動圖GIF (.gif)
巴布亞紐幾內亞PNG (.png)
骨形態發生蛋白點陣圖 (.bmp)
網路P WebP (.webp)
生的ARW (.arw)、CR2 (.cr2)、DNG (.dng)、NEF (.nef)、NRW (.nrw)、ORF (.orf)、PEF (.pef)、RAF (.raf)、RW2 ( .rw2)、SRW (.srw)
海伊夫Image, Image collection, Image sequence HEIF (.heif), HEIC (.heic)

5.1.7.視訊編解碼器

  • For acceptable quality of web video streaming and video-conference services, device implementations SHOULD use a hardware VP8 codec that meets the requirements .

If device implementations include a video decoder or encoder:

  • [C-1-1] Video codecs MUST support output and input bytebuffer sizes that accommodate the largest feasible compressed and uncompressed frame as dictated by the standard and configuration but also not overallocate.

  • [C-1-2] Video encoders and decoders MUST support YUV420 flexible color format (COLOR_FormatYUV420Flexible).

If device implementations advertise HDR profile support through Display.HdrCapabilities , they:

  • [C-2-1] MUST support HDR static metadata parsing and handling.

If device implementations advertise intra refresh support through FEATURE_IntraRefresh in the MediaCodecInfo.CodecCapabilities class, they:

  • [C-3-1] MUST support the refresh periods in the range of 10 - 60 frames and accurately operate within 20% of configured refresh period.

5.1.8.視訊編解碼器列表

格式/編解碼器細節支援的文件類型/
容器格式
H.263
  • 3GPP (.3gp)
  • MPEG-4 (.mp4)
H.264AVC詳細資訊請參閱第 5.2 節第 5.3
  • 3GPP (.3gp)
  • MPEG-4 (.mp4)
  • MPEG-2 TS(.ts,僅限 AAC 音頻,不可搜索,Android 3.0+)
H.265 HEVC詳細資訊請參閱第 5.3 節MPEG-4 (.mp4)
MPEG-2主要簡介MPEG2-TS
MPEG-4 SP 3GPP (.3gp)
VP8詳細資訊請參閱第 5.2 節第 5.3
VP9詳細資訊請參閱第 5.3 節

5.2.視訊編碼

If device implementations support any video encoder and make it available to third-party apps, they:

  • SHOULD NOT be, over two sliding windows, more than ~15% over the bitrate between intraframe (I-frame) intervals.
  • SHOULD NOT be more than ~100% over the bitrate over a sliding window of 1 second.

If device implementations include an embedded screen display with the diagonal length of at least 2.5 inches or include a video output port or declare the support of a camera via the android.hardware.camera.any feature flag, they:

  • [C-1-1] MUST include the support of at least one of the VP8 or H.264 video encoders, and make it available for third-party applications.
  • SHOULD support both VP8 and H.264 video encoders, and make it available for third-party applications.

If device implementations support any of the H.264, VP8, VP9 or HEVC video encoders and make it available to third-party applications, they:

  • [C-2-1] MUST support dynamically configurable bitrates.
  • 應支援可變幀速率,其中視訊編碼器應根據輸入緩衝區的時間戳確定瞬時幀持續時間,並根據該幀持續時間分配其位元桶。

If device implementations support the MPEG-4 SP video encoder and make it available to third-party apps, they:

  • SHOULD support dynamically configurable bitrates for the supported encoder.

5.2.1. H.263

If device implementations support H.263 encoders and make it available to third-party apps, they:

  • [C-1-1] MUST support Baseline Profile Level 45.
  • SHOULD support dynamically configurable bitrates for the supported encoder.

5.2.2. H-264

If device implementations support H.264 codec, they:

  • [C-1-1] MUST support Baseline Profile Level 3. However, support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL.此外,為了保持與其他 Android 裝置的兼容性,建議編碼器不要將 ASO、FMO 和 RS 用於 Baseline Profile。
  • [C-1-2] MUST support the SD (Standard Definition) video encoding profiles in the following table.
  • 應支援主設定檔等級 4。
  • 應支援 HD(高清晰度)視訊編碼配置文件,如下表所示。

If device implementations report support of H.264 encoding for 720p or 1080p resolution videos through the media APIs, they:

  • [C-2-1] MUST support the encoding profiles in the following table.
標清(低品質)標清(高品質)高清720p高清1080p
視訊解析度320 x 240 像素720 x 480 像素1280 x 720 像素1920 x 1080 像素
視訊幀率20 幀/秒30 幀/秒30 幀/秒30 幀/秒
視訊比特率384Kbps 2Mbps 4Mbps 10Mbps

5.2.3. VP8

If device implementations support VP8 codec, they:

  • [C-1-1] MUST support the SD video encoding profiles.
  • SHOULD support the following HD (High Definition) video encoding profiles.
  • SHOULD support writing Matroska WebM files.
  • SHOULD use a hardware VP8 codec that meets the WebM project RTC hardware coding requirements , to ensure acceptable quality of web video streaming and video-conference services.

If device implementations report support of VP8 encoding for 720p or 1080p resolution videos through the media APIs, they:

  • [C-2-1] MUST support the encoding profiles in the following table.
標清(低品質)標清(高品質)高清720p高清1080p
視訊解析度320 x 180 像素640 x 360 像素1280 x 720 像素1920 x 1080 像素
視訊幀率30 幀/秒30 幀/秒30 幀/秒30 幀/秒
視訊比特率800Kbps 2Mbps 4Mbps 10Mbps

5.2.4. VP9

If device implementations support VP9 codec, they:

  • SHOULD support writing Matroska WebM files.

5.3.視訊解碼

If device implementations support VP8, VP9, H.264, or H.265 codecs, they:

  • [C-1-1] MUST support dynamic video resolution and frame rate switching through the standard Android APIs within the same stream for all VP8, VP9, H.264, and H.265 codecs in real time and up to the maximum resolution supported by each codec on the device.

If device implementations declare support for the Dolby Vision decoder through HDR_TYPE_DOLBY_VISION , they:

  • [C-2-1] MUST provide a Dolby Vision-capable extractor.
  • [C-2-2] MUST properly display Dolby Vision content on the device screen or on a standard video output port (eg, HDMI).
  • [C-2-3] MUST set the track index of backward-compatible base-layer(s) (if present) to be the same as the combined Dolby Vision layer's track index.

5.3.1. MPEG-2

If device implementations support MPEG-2 decoders, they:

  • [C-1-1] MUST support the Main Profile High Level.

5.3.2. H.263

If device implementations support H.263 decoders, they:

  • [C-1-1] MUST support Baseline Profile Level 30 and Level 45.

5.3.3. MPEG-4

If device implementations with MPEG-4 decoders, they:

  • [C-1-1] MUST support Simple Profile Level 3.

5.3.4. H.264

If device implementations support H.264 decoders, they:

  • [C-1-1] MUST support Main Profile Level 3.1 and Baseline Profile.對 ASO(任意切片排序)、FMO(靈活宏塊排序)和 RS(冗餘切片)的支援是可選的。
  • [C-1-2] MUST be capable of decoding videos with the SD (Standard Definition) profiles listed in the following table and encoded with the Baseline Profile and Main Profile Level 3.1 (including 720p30).
  • 應能夠解碼具有 HD(高清晰度)配置文件的視頻,如下表所示。

If the height that is reported by the Display.getSupportedModes() method is equal or greater than the video resolution, device implementations:

  • [C-2-1] MUST support the HD 720p video decoding profiles in the following table.
  • [C-2-2] MUST support the HD 1080p video decoding profiles in the following table.
標清(低品質)標清(高品質)高清720p高清1080p
視訊解析度320 x 240 像素720 x 480 像素1280 x 720 像素1920 x 1080 像素
視訊幀率30 幀/秒30 幀/秒60 幀/秒30 fps (60 fps Television )
視訊比特率800Kbps 2Mbps 8Mbps 20Mbps

5.3.5。 H.265 (HEVC)

If device implementations support H.265 codec, they:

  • [C-1-1] MUST support the Main Profile Level 3 Main tier and the SD video decoding profiles as indicated in the following table.
  • 應支援下表所示的高清解碼設定檔。
  • [C-1-2] MUST support the HD decoding profiles as indicated in the following table if there is a hardware decoder.

If the height that is reported by the Display.getSupportedModes() method is equal to or greater than the video resolution, then:

  • [C-2-1] Device implementations MUST support at least one of H.265 or VP9 decoding of 720, 1080 and UHD profiles.
標清(低品質)標清(高品質)高清720p高清1080p超高畫質
視訊解析度352 x 288 像素720 x 480 像素1280 x 720 像素1920 x 1080 像素3840 x 2160 像素
視訊幀率30 幀/秒30 幀/秒30 幀/秒30/60 fps (60 fps Television with H.265 hardware decoding ) 60 幀/秒
視訊比特率600Kbps 1.6Mbps 4Mbps 5Mbps 20Mbps

5.3.6。 VP8

If device implementations support VP8 codec, they:

  • [C-1-1] MUST support the SD decoding profiles in the following table.
  • SHOULD use a hardware VP8 codec that meets the requirements .
  • 應支援下表中的高清解碼設定檔。

If the height as reported by the Display.getSupportedModes() method is equal or greater than the video resolution, then:

  • [C-2-1] Device implementations MUST support 720p profiles in the following table.
  • [C-2-2] Device implementations MUST support 1080p profiles in the following table.
標清(低品質)標清(高品質)高清720p高清1080p
視訊解析度320 x 180 像素640 x 360 像素1280 x 720 像素1920 x 1080 像素
視訊幀率30 幀/秒30 幀/秒30 fps (60 fps Television ) 30 (60 fps Television )
視訊比特率800Kbps 2Mbps 8Mbps 20Mbps

5.3.7. VP9

If device implementations support VP9 codec, they:

  • [C-1-1] MUST support the SD video decoding profiles as indicated in the following table.
  • 應支援下表所示的高清解碼設定檔。

If device implementations support VP9 codec and a hardware decoder:

  • [C-2-1] MUST support the HD decoding profiles as indicated in the following table.

If the height that is reported by the Display.getSupportedModes() method is equal to or greater than the video resolution, then:

  • [C-3-1] Device implementations MUST support at least one of VP9 or H.265 decoding of the 720, 1080 and UHD profiles.
標清(低品質)標清(高品質)高清720p高清1080p超高畫質
視訊解析度320 x 180 像素640 x 360 像素1280 x 720 像素1920 x 1080 像素3840 x 2160 像素
視訊幀率30 幀/秒30 幀/秒30 幀/秒30 fps (60 fps Television with VP9 hardware decoding ) 60 幀/秒
視訊比特率600Kbps 1.6Mbps 4Mbps 5Mbps 20Mbps

5.4.聲音錄製

While some of the requirements outlined in this section are listed as SHOULD since Android 4.3, the Compatibility Definition for future versions are planned to change these to MUST. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements that are listed as SHOULD, or they will not be able to attain Android compatibility when upgraded to the future version.

5.4.1.原始音訊捕獲

If device implementations declare android.hardware.microphone , they:

  • [C-1-1] MUST allow capture of raw audio content with the following characteristics:

    • 格式:線性 PCM,16 位元
    • Sampling rates : 8000, 11025, 16000, 44100 Hz
    • 頻道:單聲道
  • [C-1-2] MUST capture at above sample rates without up-sampling.

  • [C-1-3] MUST include an appropriate anti-aliasing filter when the sample rates given above are captured with down-sampling.
  • SHOULD allow AM radio and DVD quality capture of raw audio content, which means the following characteristics:

    • 格式:線性 PCM,16 位元
    • Sampling rates : 22050, 48000 Hz
    • 聲道:立體聲

If device implementations allow AM radio and DVD quality capture of raw audio content, they:

  • [C-2-1] MUST capture without up-sampling at any ratio higher than 16000:22050 or 44100:48000.
  • [C-2-2] MUST include an appropriate anti-aliasing filter for any up-sampling or down-sampling.

5.4.2.語音辨識捕獲

If device implementations declare android.hardware.microphone , they:

  • [C-1-1] MUST capture android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source at one of the sampling rates, 44100 and 48000.
  • [C-1-2] MUST, by default, disable any noise reduction audio processing when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.
  • [C-1-3] MUST, by default, disable any automatic gain control when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.
  • SHOULD record the voice recognition audio stream with approximately flat amplitude versus frequency characteristics: specifically, ±3 dB, from 100 Hz to 4000 Hz.
  • SHOULD record the voice recognition audio stream with input sensitivity set such that a 90 dB sound power level (SPL) source at 1000 Hz yields RMS of 2500 for 16-bit samples.
  • SHOULD record the voice recognition audio stream so that the PCM amplitude levels linearly track input SPL changes over at least a 30 dB range from -18 dB to +12 dB re 90 dB SPL at the microphone.
  • SHOULD record the voice recognition audio stream with total harmonic distortion (THD) less than 1% for 1 kHz at 90 dB SPL input level at the microphone.

If device implementations declare android.hardware.microphone and noise suppression (reduction) technologies tuned for speech recognition, they:

  • [C-2-1] MUST allow this audio affect to be controllable with the android.media.audiofx.NoiseSuppressor API.
  • [C-2-2] MUST uniquely identify each noise suppression technology implementation via the AudioEffect.Descriptor.uuid field.

5.4.3.捕獲以重新路由播放

android.media.MediaRecorder.AudioSource類別包含REMOTE_SUBMIX音訊來源。

If device implementations declare both android.hardware.audio.output and android.hardware.microphone , they:

  • [C-1-1] MUST properly implement the REMOTE_SUBMIX audio source so that when an application uses the android.media.AudioRecord API to record from this audio source, it captures a mix of all audio streams except for the following:

    • AudioManager.STREAM_RING
    • AudioManager.STREAM_ALARM
    • AudioManager.STREAM_NOTIFICATION

5.5.音訊播放

Android includes the support to allow apps to playback audio through the audio output peripheral as defined in section 7.8.2.

5.5.1.原始音訊播放

If device implementations declare android.hardware.audio.output , they:

  • [C-1-1] MUST allow playback of raw audio content with the following characteristics:

    • Format : Linear PCM, 16-bit, 8-bit, float
    • Channels : Mono, Stereo, valid multichannel configurations with up to 8 channels
    • Sampling rates (in Hz) :
      • 8000, 11025, 16000, 22050, 32000, 44100, 48000 at the channel configurations listed above
      • 96000 in mono and stereo
  • SHOULD allow playback of raw audio content with the following characteristics:

    • 取樣率:24000、48000

5.5.2.音訊效果

Android 為裝置實作提供了音訊效果 API

If device implementations declare the feature android.hardware.audio.output , they:

  • [C-1-1] MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER implementations controllable through the AudioEffect subclasses Equalizer , LoudnessEnhancer .
  • [C-1-2] MUST support the visualizer API implementation, controllable through the Visualizer class.
  • [C-1-3] MUST support the EFFECT_TYPE_DYNAMICS_PROCESSING implementation controllable through the AudioEffect subclass DynamicsProcessing .
  • SHOULD support the EFFECT_TYPE_BASS_BOOST , EFFECT_TYPE_ENV_REVERB , EFFECT_TYPE_PRESET_REVERB , and EFFECT_TYPE_VIRTUALIZER implementations controllable through the AudioEffect sub-classes BassBoost , EnvironmentalReverb , PresetReverb , and Virtualizer .

5.5.3.音訊輸出音量

Automotive device implementations:

  • SHOULD allow adjusting audio volume separately per each audio stream using the content type or usage as defined by AudioAttributes and car audio usage as publicly defined in android.car.CarAudioManager .

5.6.音訊延遲

音訊延遲是音訊訊號通過系統時的時間延遲。許多類別的應用程式依靠短延遲來實現即時聲音效果。

就本節而言,使用以下定義:

  • 輸出延遲。應用程式寫入 PCM 編碼資料幀與相應的聲音在裝置上的感測器處呈現給環境或訊號通過連接埠離開裝置並可在外部觀察到的時間間隔。
  • 冷輸出延遲。當音訊輸出系統在請求之前處於空閒狀態並斷電時,第一幀的輸出延遲。
  • 連續輸出延遲。設備播放音訊後後續幀的輸出延遲。
  • 輸入延遲。環境在裝置上的感測器處向裝置呈現聲音或訊號透過連接埠進入裝置與應用程式讀取對應的 PCM 編碼資料幀之間的時間間隔。
  • 丟失輸入。輸入訊號的初始部分不可用或不可用。
  • 冷輸入延遲。當音訊輸入系統在請求之前處於空閒狀態並斷電時,遺失的輸入時間和第一幀的輸入延遲總和。
  • 連續輸入延遲。設備擷取音訊時後續幀的輸入延遲。
  • 冷輸出抖動。冷輸出延遲值的單獨測量之間的變異性。
  • 冷輸入抖動。冷輸入延遲值的單獨測量之間的可變性。
  • 連續往返延遲。連續輸入延遲加上連續輸出延遲加上一個緩衝週期的總和。緩衝期允許應用程式有時間處理訊號,並允許應用程式有時間減輕輸入和輸出流之間的相位差。
  • OpenSL ES PCM 緩衝佇列 APIAndroid NDK中與 PCM 相關的OpenSL ES API 集。
  • AAudio native audio API . The set of AAudio APIs within Android NDK .
  • Timestamp . A pair consisting of a relative frame position within a stream and the estimated time when that frame enters or leaves the audio processing pipeline on the associated endpoint. See also AudioTimestamp .

If device implementations declare android.hardware.audio.output they are STRONGLY RECOMMENDED to meet or exceed the following requirements:

  • [C-SR] Cold output latency of 100 milliseconds or less
  • [C-SR] Continuous output latency of 45 milliseconds or less
  • [C-SR] Minimize the cold output jitter
  • [C-SR] The output timestamp returned by AudioTrack.getTimestamp and AAudioStream_getTimestamp is accurate to +/- 1 ms.

If device implementations meet the above requirements, after any initial calibration, when using both the OpenSL ES PCM buffer queue and AAudio native audio APIs, for continuous output latency and cold output latency over at least one supported audio output device, they are:

If device implementations do not meet the requirements for low-latency audio via both the OpenSL ES PCM buffer queue and AAudio native audio APIs, they:

  • [C-1-1] MUST NOT report support for low-latency audio.

If device implementations include android.hardware.microphone , they are STRONGLY RECOMMENDED to meet these input audio requirements:

  • [C-SR] Cold input latency of 100 milliseconds or less.
  • [C-SR] Continuous input latency of 30 milliseconds or less.
  • [C-SR] Continuous round-trip latency of 50 milliseconds or less.
  • [C-SR] Minimize the cold input jitter.
  • [C-SR] Limit the error in input timestamps, as returned by AudioRecord.getTimestamp or AAudioStream_getTimestamp , to +/- 1 ms.

5.7.網路協定

Device implementations MUST support the media network protocols for audio and video playback as specified in the Android SDK documentation.

If device implementations include an audio or a video decoder, they:

  • [C-1-1] MUST support all required codecs and container formats in section 5.1 over HTTP(S).

  • [C-1-2] MUST support the media segment formats shown in the Media Segment Formats table below over HTTP Live Streaming draft protocol, Version 7 .

  • [C-1-3] MUST support the following RTP audio video profile and related codecs in the RTSP table below.對於例外情況,請參閱第 5.1 節的表註腳。

Media Segment Formats

段格式參考)所需的編解碼器支持
MPEG-2 傳輸流ISO 13818視訊編解碼器:
  • H264 AVC
  • MPEG-4 SP
  • MPEG-2
有關 H264 AVC、MPEG2-4 SP、的詳細信息,請參閱第 5.1.3 節
和 MPEG-2。

音訊編解碼器:

  • 亞克力
有關 AAC 及其變體的詳細信息,請參閱第 5.1.1 節
帶有 ADTS 框架和 ID3 標籤的 AAC ISO 13818-7有關 AAC 及其變體的詳細信息,請參閱第 5.1.1 節
網路VTT網路VTT

RTSP(RTP、SDP)

個人資料名稱參考)所需的編解碼器支持
H264 AVC RFC 6184有關 H264 AVC 的詳細信息,請參閱第 5.1.3 節
MP4A-LATM RFC 6416有關 AAC 及其變體的詳細信息,請參閱第 5.1.1 節
H263-1998 RFC 3551
RFC 4629
RFC 2190
有關 H263 的詳細信息,請參閱第 5.1.3 節
H263-2000 RFC 4629有關 H263 的詳細信息,請參閱第 5.1.3 節
抗微生物藥物抗藥性RFC 4867有關 AMR-NB 的詳細信息,請參閱第 5.1.1 節
AMR-WB RFC 4867有關 AMR-WB 的詳細信息,請參閱第 5.1.1 節
MP4V-ES RFC 6416有關 MPEG-4 SP 的詳細信息,請參閱第 5.1.3 節
mpeg4-通用RFC 3640有關 AAC 及其變體的詳細信息,請參閱第 5.1.1 節
MP2T RFC 2250有關詳細信息,請參閱 HTTP Live Streaming 下的MPEG-2 傳輸流

5.8.安全媒體

If device implementations support secure video output and are capable of supporting secure surfaces, they:

  • [C-1-1] MUST declare support for Display.FLAG_SECURE .

If device implementations declare support for Display.FLAG_SECURE and support wireless display protocol, they:

  • [C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast.

If device implementations declare support for Display.FLAG_SECURE and support wired external display, they:

  • [C-3-1] MUST support HDCP 1.2 or higher for all external displays connected via a user-accessible wired port.

5.9.樂器數位介面 (MIDI)

If device implementations report support for feature android.software.midi via the android.content.pm.PackageManager class, they:

  • [C-1-1] MUST support MIDI over all MIDI-capable hardware transports for which they provide generic non-MIDI connectivity, where such transports are:

  • [C-1-2] MUST support the inter-app MIDI software transport (virtual MIDI devices)

5.10.專業音響

If device implementations report support for feature android.hardware.audio.pro via the android.content.pm.PackageManager class, they:

  • [C-1-1] MUST report support for feature android.hardware.audio.low_latency .
  • [C-1-2] MUST have the continuous round-trip audio latency, as defined in section 5.6 Audio Latency , MUST be 20 milliseconds or less and SHOULD be 10 milliseconds or less over at least one supported path.
  • [C-1-3] MUST include a USB port(s) supporting USB host mode and USB peripheral mode.
  • [C-1-4] MUST report support for feature android.software.midi .
  • [C-1-5] MUST meet latencies and USB audio requirements using both the OpenSL ES PCM buffer queue and AAudio native audio APIs.
  • [SR] Are STRONGLY RECOMMENDED to provide a consistent level of CPU performance while audio is active and CPU load is varying. This should be tested using SimpleSynth commit 1bd6391 . The SimpleSynth app needs to be run with below parameters and achieve zero underruns after 10 minutes:
    • Work cycles: 200,000
    • Variable load: ON (this will switch between 100% and 10% of the work cycles value every 2 seconds and is designed to test CPU governor behavior)
    • Stabilized load: OFF
  • SHOULD minimize audio clock inaccuracy and drift relative to standard time.
  • SHOULD minimize audio clock drift relative to the CPU CLOCK_MONOTONIC when both are active.
  • SHOULD minimize audio latency over on-device transducers.
  • SHOULD minimize audio latency over USB digital audio.
  • SHOULD document audio latency measurements over all paths.
  • SHOULD minimize jitter in audio buffer completion callback entry times, as this affects usable percentage of full CPU bandwidth by the callback.
  • SHOULD provide zero audio underruns (output) or overruns (input) under normal use at reported latency.
  • SHOULD provide zero inter-channel latency difference.
  • SHOULD minimize MIDI mean latency over all transports.
  • SHOULD minimize MIDI latency variability under load (jitter) over all transports.
  • SHOULD provide accurate MIDI timestamps over all transports.
  • SHOULD minimize audio signal noise over on-device transducers, including the period immediately after cold start.
  • SHOULD provide zero audio clock difference between the input and output sides of corresponding end-points, when both are active.相應的終點的範例包括在裝置上的麥克風和揚聲器,或音訊插孔輸入和輸出。
  • SHOULD handle audio buffer completion callbacks for the input and output sides of corresponding end-points on the same thread when both are active, and enter the output callback immediately after the return from the input callback.或者,如果在同一線程上處理回調是不可行的,請在輸入輸入回調後不久輸入輸出回調以允許應用程式具有輸入和輸出側的一致時機。
  • SHOULD minimize the phase difference between HAL audio buffering for the input and output sides of corresponding end-points.
  • SHOULD minimize touch latency.
  • SHOULD minimize touch latency variability under load (jitter).
  • SHOULD have a latency from touch input to audio output of less than or equal to 40 ms.

If device implementations meet all of the above requirements, they:

If device implementations include a 4 conductor 3.5mm audio jack, they:

If device implementations omit a 4 conductor 3.5mm audio jack and include a USB port(s) supporting USB host mode, they:

  • [C-3-1] MUST implement the USB audio class.
  • [C-3-2] MUST have a continuous round-trip audio latency of 20 milliseconds or less over the USB host mode port using USB audio class.
  • The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the USB host mode port using USB audio class.

If device implementations include an HDMI port, they:

  • [C-4-1] MUST support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling, in at least one configuration.

5.11.捕獲未處理的

Android includes support for recording of unprocessed audio via the android.media.MediaRecorder.AudioSource.UNPROCESSED audio source.在OpenSL ES中,可以使用記錄預設SL_ANDROID_RECORDING_PRESET_UNPROCESSED來存取它。

If device implementations intent to support unprocessed audio source and make it available to third-party apps, they:

  • [C-1-1] MUST report the support through the android.media.AudioManager property PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED .

  • [C-1-2] MUST exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±10dB from 100 Hz to 7000 Hz for each and every microphone used to record the unprocessed audio source.

  • [C-1-3] MUST exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 5 Hz to 100 Hz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source.

  • [C-1-4] MUST exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 7000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source.

  • [C-1-5] MUST set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 94 dB Sound Pressure Level (SPL) yields a response with RMS of 520 for 16 bit-samples (or -36 dB Full Scale for floating point/double precision samples) for each and every microphone used to record the unprocessed audio source.

  • [C-1-6] MUST have a signal-to-noise ratio (SNR) at 60 dB or higher for each and every microphone used to record the unprocessed audio source. (whereas the SNR is measured as the difference between 94 dB SPL and equivalent SPL of self noise, A-weighted).

  • [C-1-7] MUST have a total harmonic distortion (THD) less than be less than 1% for 1 kHZ at 90 dB SPL input level at each and every microphone used to record the unprocessed audio source.

  • MUST not have any other signal processing (eg Automatic Gain Control, High Pass Filter, or Echo cancellation) in the path other than a level multiplier to bring the level to desired range.換句話說:

  • [C-1-8] If any signal processing is present in the architecture for any reason, it MUST be disabled and effectively introduce zero delay or extra latency to the signal path.
  • [C-1-9] The level multiplier, while allowed to be on the path, MUST NOT introduce delay or latency to the signal path.

所有SPL測量值直接在正在測試的麥克風旁邊進行。對於多個麥克風配置,這些要求適用於每個麥克風。

If device implementations declare android.hardware.microphone but do not support unprocessed audio source, they:

  • [C-2-1] MUST return null for the AudioManager.getProperty(PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED) API method, to properly indicate the lack of support.
  • [SR] are still STRONGLY RECOMMENDED to satisfy as many of the requirements for the signal path for the unprocessed recording source.

6. 開發者工具和選項相容性

6.1.開發者工具

設備實現:

  • [C-0-1] MUST support the Android Developer Tools provided in the Android SDK.
  • Android Debug Bridge(ADB)

    • [C-0-2] MUST support adb as documented in the Android SDK and the shell commands provided in the AOSP, which can be used by app developers, including dumpsys and cmd stats .
    • [C-0-3] MUST NOT alter the format or the contents of device system events (batterystats , diskstats, fingerprint, graphicsstats, netstats, notification, procstats) logged via the dumpsys command.
    • [C-0-10] MUST record, without omission, and make the following events accessible and available to the cmd stats shell command and the StatsManager System API class.
      • ActivityForegroundStateChanged
      • AnomalyDetected
      • AppBreadcrumbReported
      • AppCrashOccurred
      • AppStartOccurred
      • BatteryLevelChanged
      • BatterySaverModeStateChanged
      • BleScanResultReceived
      • BleScanStateChanged
      • ChargingStateChanged
      • DeviceIdleModeStateChanged
      • ForegroundServiceStateChanged
      • GpsScanStateChanged
      • JobStateChanged
      • PluggedStateChanged
      • ScheduledJobStateChanged
      • ScreenStateChanged
      • SyncStateChanged
      • SystemElapsedRealtime
      • UidProcessStateChanged
      • WakelockStateChanged
      • WakeupAlarmOccurred
      • WifiLockStateChanged
      • WifiMulticastLockStateChanged
      • WifiScanStateChanged
    • [C-0-4] MUST have the device-side adb daemon be inactive by default and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge.
    • [C-0-5] MUST support secure adb. Android 包含對安全 adb 的支援。安全性 adb 在已知的經過驗證的主機上啟用 adb。
    • [C-0-6] MUST provide a mechanism allowing adb to be connected from a host machine.例如:

      • Device implementations without a USB port supporting peripheral mode MUST implement adb via local-area network (such as Ethernet or Wi-Fi).
      • MUST provide drivers for Windows 7, 9 and 10, allowing developers to connect to the device using the adb protocol.
  • Dalvik 調試監控服務 (ddms)

    • [C-0-7] 必須支援 Android SDK 中記錄的所有 ddms 功能。由於 ddms 使用 adb,因此預設對 ddms 的支援應該處於非活動狀態,但只要使用者啟動 Android 偵錯橋就必須支持,如上所述。
    • [C-0-8] MUST include the Monkey framework and make it available for applications to use.
  • Systrace
    • [C-0-9] 必須支援 Android SDK 中記錄的 systrace 工具。 Systrace 預設必須處於非活動狀態,且必須有使用者可存取的機制來開啟 Systrace。

If device implementations report the support of Vulkan 1.0 or higher via the android.hardware.vulkan.version feature flags, they:

  • [C-1-1] 必須提供應用程式開發者啟用/停用 GPU 偵錯層的功能。
  • [C-1-2] 啟用 GPU 偵錯層時,必須列舉可偵錯應用程式目錄中的外部工具(即不是平台或應用程式套件的一部分)提供的程式庫中的層,以支援vkEnumerateInstanceLayerProperties()vkCreateInstance () API 方法。

6.2.開發者選項

Android 支援開發人員配置應用程式開發相關的設定。

Device implementations MUST provide a consistent experience for Developer Options, they:

  • [C-0-1] 必須遵循android.settings.APPLICATION_DEVELOPMENT_SETTINGS Intent 以顯示應用程式開發相關的設定。上游 Android 實作預設隱藏「開發人員選項」選單,並允許使用者在「設定」 > 「關於裝置」 > 「內部版本號」選單項目上按七 (7) 次後啟動開發人員選項。
  • [C-0-2] MUST hide Developer Options by default.
  • [C-0-3] MUST provide a clear mechanism that does not give preferential treatment to one third-party app as opposed to another to enable Developer Options. MUST provide a public visible document or website that describes how to enable Developer Options. This document or website MUST be linkable from the Android SDK documents.
  • 當啟用開發者選項並且關注使用者安全時,應持續向使用者發出視覺通知。
  • 可以透過視覺隱藏或停用選單來暫時限制對「開發人員選項」選單的訪問,以防止在關注用戶安全的情況下分散注意力。

7. 硬體相容性

如果設備包含特定硬體元件,且該元件具有供第三方開發人員使用的對應 API:

  • [C-0-1] 裝置實作必須實作 Android SDK 文件中所述的 API。

如果 SDK 中的 API 與指定為可選的硬體元件交互,且裝置實作不擁有該元件:

  • [C-0-2] 仍必須提供元件 API 的完整類別定義(如 SDK 所記錄)。
  • [C-0-3] API 的行為必須以某種合理的方式實作為無操作。
  • [C-0-4] API 方法必須在 SDK 文件允許的情況下傳回 null 值。
  • [C-0-5] API 方法必須傳回 SDK 文件不允許使用 null 值的類別的無操作實作。
  • [C-0-6] API methods MUST NOT throw exceptions not documented by the SDK documentation.
  • [C-0-7] Device implementations MUST consistently report accurate hardware configuration information via the getSystemAvailableFeatures() and hasSystemFeature(String) methods on the android.content.pm.PackageManager class for the same build fingerprint.

應用這些要求的場景的典型範例是電話 API:即使在非電話設備上,這些 API 也必須以合理的無操作方式實作。

7.1.顯示和圖形

Android 包含自動調整應用程式資源和適合裝置的 UI 佈局的功能,以確保第三方應用程式在各種硬體配置上運作良好。設備必須正確實作這些 API 和行為,如本節所述。

本節要求引用的單位定義如下:

  • 物理對角線尺寸。顯示器照明部分的兩個相對角落之間的距離(以英吋為單位)。
  • 每吋點數 (dpi) 。 1 英吋的線性水平或垂直跨度所包含的像素數。在列出 dpi 值的地方,水平和垂直 dpi 都必須落在該範圍內。
  • 長寬比。螢幕較長尺寸與較短尺寸的像素之比。例如,480x854 像素的顯示器將為 854/480 = 1.779,或大致為「16:9」。
  • 與密度無關的像素 (dp) 。歸一化為 160 dpi 螢幕的虛擬像素單位,計算公式為:像素 = dps * (密度/160)。

7.1.1.螢幕配置

7.1.1.1. Screen Size and Shape

The Android UI framework supports a variety of different logical screen layout sizes, and allows applications to query the current configuration's screen layout size via Configuration.screenLayout with the SCREENLAYOUT_SIZE_MASK and Configuration.smallestScreenWidthDp .

設備實現:

  • [C-0-1] MUST report the correct layout size for the Configuration.screenLayout as defined in the Android SDK documentation.具體來說,設備實現必須報告正確的邏輯密度無關像素 (dp) 螢幕尺寸,如下所示:

    • Devices with the Configuration.uiMode set as any value other than UI_MODE_TYPE_WATCH, and reporting a small size for the Configuration.screenLayout , MUST have at least 426 dp x 320 dp.
    • Devices reporting a normal size for the Configuration.screenLayout , MUST have at least 480 dp x 320 dp.
    • Devices reporting a large size for the Configuration.screenLayout , MUST have at least 640 dp x 480 dp.
    • Devices reporting a xlarge size for the Configuration.screenLayout , MUST have at least 960 dp x 720 dp.
  • [C-0-2] MUST correctly honor applications' stated support for screen sizes through the < supports-screens > attribute in the AndroidManifest.xml, as described in the Android SDK documentation.

  • MAY have a display with rounded corners.

If device implementations support UI_MODE_TYPE_NORMAL and include a display with rounded corners, they:

  • [C-1-1] MUST ensure that the radius of the rounded corners is less than or equal to 38 dp.
  • 應包括使用者切換到帶有矩形角的顯示模式的能力。
7.1.1.2.螢幕縱橫比

While there is no restriction to the screen aspect ratio value of the physical screen display, the screen aspect ratio of the logical display that third-party apps are rendered within, as can be derived from the height and width values reported through the view.Display APIs and Configuration API, MUST meet the following requirements:

  • [C-0-1] Device implementations with the Configuration.uiMode set as UI_MODE_TYPE_NORMAL MUST have an aspect ratio value between 1.3333 (4:3) and 1.86 (roughly 16:9), unless the app can be deemed as ready to be stretched longer by meeting one of the following conditions:

    • The app has declared that it supports a larger screen aspect ratio through the android.max_aspect metadata value.
    • 應用程式透過android:resizeableActivity屬性聲明它可以調整大小。
    • The app is targeting API level 24 or higher and does not declare a android:MaxAspectRatio that would restrict the allowed aspect ratio.
  • [C-0-2] Device implementations with the Configuration.uiMode set as UI_MODE_TYPE_WATCH MUST have an aspect ratio value set as 1.0 (1:1).

7.1.1.3。螢幕密度

Android UI 框架定義了一組標準邏輯密度來幫助應用程式開發人員定位應用程式資源。

  • [C-0-1] By default, device implementations MUST report only one of the following logical Android framework densities through the DENSITY_DEVICE_STABLE API and this value MUST NOT change at any time;但是,設備可以根據使用者在初始啟動後設定的顯示配置變更(例如,顯示尺寸)報告不同的任意密度。

    • 120 dpi(LDPI)
    • 160 dpi (mdpi)
    • 213 dpi(電視dpi)
    • 240 dpi(高清)
    • 260 DPI(260DPI)
    • 280dpi (280dpi)
    • 300 DPI(300DPI)
    • 320 dpi(xhdpi)
    • 340 DPI(340DPI)
    • 360dpi (360dpi)
    • 400dpi (400dpi)
    • 420 dpi (420dpi)
    • 480 dpi (xxhdpi)
    • 560dpi(560dpi)
    • 640 dpi (xxxhdpi)
  • 裝置實現應該定義在數值上最接近螢幕物理密度的標準 Android 框架密度,除非該邏輯密度將報告的螢幕尺寸推至支援的最小值以下。如果在數字上最接近物理密度的標準 Android 框架密度導致螢幕尺寸小於支援的最小相容螢幕尺寸(320 dp 寬度),則裝置實現應該報告下一個最低的標準 Android 框架密度。

If there is an affordance to change the display size of the device:

  • [C-1-1] 顯示尺寸縮放後不得超過原始密度的 1.5 倍,也不得產生小於 320dp(相當於資源限定符 sw320dp)的有效最小螢幕尺寸(以先到者為準)。
  • [C-1-2] 顯示尺寸縮放後不得小於原始密度的 0.85 倍。
  • 為了確保良好的可用性和一致的字體大小,建議提供以下本機顯示選項縮放(同時遵守上述指定的限制)
  • 小:0.85倍
  • 預設值:1x(本機顯示比例)
  • 大:1.15x
  • 更大:1.3x
  • 最大1.45倍

7.1.2.顯示指標

If device implementations include a screen or video output, they:

如果裝置實作不包括嵌入式螢幕或視訊輸出,則:

  • [C-2-1] MUST report reasonable values for all display metrics defined in the android.util.DisplayMetrics API for the emulated default view.Display .

7.1.3.螢幕方向

設備實現:

  • [C-0-1] MUST report which screen orientations they support ( android.hardware.screen.portrait and/or android.hardware.screen.landscape ) and MUST report at least one supported orientation. For example, a device with a fixed orientation landscape screen, such as a television or laptop, SHOULD only report android.hardware.screen.landscape .
  • [C-0-2] MUST report the correct value for the device's current orientation, whenever queried via the android.content.res.Configuration.orientation , android.view.Display.getOrientation() , or other APIs.

If device implementations support both screen orientations, they:

  • [C-1-1] 必須支援應用程式動態定向為縱向或橫向螢幕方向。也就是說,設備必須尊重應用程式對特定螢幕方向的請求。
  • [C-1-2] MUST NOT change the reported screen size or density when changing orientation.
  • 可以選擇縱向或橫向作為預設方向。

7.1.4. 2D 和 3D 圖形加速

7.1.4.1 OpenGL ES

設備實現:

  • [C-0-1] MUST correctly identify the supported OpenGL ES versions (1.1, 2.0, 3.0, 3.1, 3.2) through the managed APIs (such as via the GLES10.getString() method) and the native APIs.
  • [C-0-2] 必須支援他們確定要支援的每個 OpenGL ES 版本的所有對應託管 API 和本機 API。

If device implementations include a screen or video output, they:

  • [C-1-1] 必須支援 OpenGL ES 1.1 和 2.0,如Android SDK 文件中所體現和詳細說明。
  • [SR] are STRONGLY RECOMMENDED to support OpenGL ES 3.1.
  • 應支援 OpenGL ES 3.2。

如果裝置實作支援任何 OpenGL ES 版本,則它們:

  • [C-2-1] MUST report via the OpenGL ES managed APIs and native APIs any other OpenGL ES extensions they have implemented, and conversely MUST NOT report extension strings that they do not support.
  • [C-2-2] MUST support the EGL_KHR_image , EGL_KHR_image_base , EGL_ANDROID_image_native_buffer , EGL_ANDROID_get_native_client_buffer , EGL_KHR_wait_sync , EGL_KHR_get_all_proc_addresses , EGL_ANDROID_presentation_time , EGL_KHR_swap_buffers_with_damage and EGL_ANDROID_recordable extensions.
  • [SR] are STRONGLY RECOMMENDED to support EGL_KHR_partial_update.
  • SHOULD accurately report via the getString() method, any texture compression format that they support, which is typically vendor-specific.

如果裝置實作聲明支援 OpenGL ES 3.0、3.1 或 3.2,則:

  • [C-3-1] 除了 libGLESv2.so 函式庫中的 OpenGL ES 2.0 函數符號之外,還必須匯出這些版本的對應函數符號。

如果裝置實作支援 OpenGL ES 3.2,則:

  • [C-4-1] 必須完整支援 OpenGL ES Android 擴充包。

If device implementations support the OpenGL ES Android Extension Pack in its entirety, they:

  • [C-5-1] MUST identify the support through the android.hardware.opengles.aep feature flag.

If device implementations expose support for the EGL_KHR_mutable_render_buffer extension, they:

  • [C-6-1] MUST also support the EGL_ANDROID_front_buffer_auto_refresh extension.
7.1.4.2 Vulkan

Android 支援Vulkan ,這是一種用於高效能 3D 圖形的低開銷、跨平台 API。

If device implementations support OpenGL ES 3.1, they:

  • [SR] Are STRONGLY RECOMMENDED to include support for Vulkan 1.1.

If device implementations include a screen or video output, they:

  • SHOULD include support for Vulkan 1.1.

If device implementations include support for Vulkan 1.0, they:

  • [C-1-1] MUST report the correct integer value with the android.hardware.vulkan.level and android.hardware.vulkan.version feature flags.
  • [C-1-2] MUST enumerate, at least one VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices() .
  • [C-1-3] MUST fully implement the Vulkan 1.0 APIs for each enumerated VkPhysicalDevice .
  • [C-1-4] MUST enumerate layers, contained in native libraries named as libVkLayer*.so in the application package's native library directory, through the Vulkan native APIs vkEnumerateInstanceLayerProperties() and vkEnumerateDeviceLayerProperties() .
  • [C-1-5] MUST NOT enumerate layers provided by libraries outside of the application package, or provide other ways of tracing or intercepting the Vulkan API, unless the application has the android:debuggable attribute set as true .
  • [C-1-6] 必須報告它們透過 Vulkan 本機 API 支援的所有擴充字串,反之不得報告它們不正確支援的擴充字串。
  • [C-1-7] 必須支援 VK_KHR_surface、VK_KHR_android_surface、VK_KHR_swapchain 和 VK_KHR_incremental_present 擴充功能。

如果設備實現不包括對 Vulkan 1.0 的支持,則:

  • [C-2-1] MUST NOT declare any of the Vulkan feature flags (eg android.hardware.vulkan.level , android.hardware.vulkan.version ).
  • [C-2-2] MUST NOT enumerate any VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices() .

If device implementations include support for Vulkan 1.1, they:

  • [C-3-1] MUST expose support for the SYNC_FD external semaphore and handle types.
  • [SR] Are STRONGLY RECOMMENDED to support the VK_ANDROID_external_memory_android_hardware_buffer extension.
7.1.4.3 渲染腳本
  • [C-0-1] Device implementations MUST support Android RenderScript , as detailed in the Android SDK documentation.
7.1.4.4 2D 圖形加速

Android 包含一種機制,供應用程式透過使用清單標記android:hardwareAccelerated或直接 API 呼叫來聲明它們希望在應用程式、活動、視窗或視圖層級啟用 2D 圖形的硬體加速。

設備實現:

  • [C-0-1] MUST enable hardware acceleration by default, and MUST disable hardware acceleration if the developer so requests by setting android:hardwareAccelerated="false” or disabling hardware acceleration directly through the Android View APIs.
  • [C-0-2] 必須表現出與硬體加速的 Android SDK 文件一致的行為。

Android 包含一個 TextureView 對象,可讓開發人員直接將硬體加速的 OpenGL ES 紋理集成為 UI 層次結構中的渲染目標。

設備實現:

  • [C-0-3] MUST support the TextureView API, and MUST exhibit consistent behavior with the upstream Android implementation.
7.1.4.5 廣色域顯示器

If device implementations claim support for wide-gamut displays through Configuration.isScreenWideColorGamut() , they:

  • [C-1-1] 必須具有經過顏色校準的顯示器。
  • [C-1-2] 顯示器的色域必須完全覆蓋 CIE 1931 xyY 空間中的 sRGB 色域。
  • [C-1-3] 顯示器的色域面積必須至少為 CIE 1931 xyY 空間中 DCI-P3 的 90%。
  • [C-1-4] MUST support OpenGL ES 3.1 or 3.2 and report it properly.
  • [C-1-5] MUST advertise support for the EGL_KHR_no_config_context , EGL_EXT_pixel_format_float , EGL_KHR_gl_colorspace , EGL_EXT_gl_colorspace_scrgb , EGL_EXT_gl_colorspace_scrgb_linear , EGL_EXT_gl_colorspace_display_p3 , and EGL_KHR_gl_colorspace_display_p3 extensions.
  • [SR] Are STRONGLY RECOMMENDED to support GL_EXT_sRGB .

相反,如果設備實作不支援廣色域顯示,則:

  • [C-2-1] SHOULD cover 100% or more of sRGB in CIE 1931 xyY space, although the screen color gamut is undefined.

7.1.5。舊版應用程式相容模式

Android 指定了一種“相容模式”,在該模式下,框架以“正常”螢幕尺寸等效(320dp 寬度)模式運行,以便為未針對螢幕尺寸獨立之前的舊版Android 開發的遺留應用程式帶來好處。

7.1.6。螢幕技術

Android 平台包含允許應用程式向顯示器呈現豐富圖形的 API。除非本文檔特別允許,否則裝置必須支援 Android SDK 定義的所有這些 API。

設備實現:

  • [C-0-1] MUST support displays capable of rendering 16-bit color graphics.
  • SHOULD support displays capable of 24-bit color graphics.
  • [C-0-2] MUST support displays capable of rendering animations.
  • [C-0-3] MUST use the display technology that have a pixel aspect ratio (PAR) between 0.9 and 1.15.也就是說,像素長寬比必須接近正方形 (1.0),容差為 10 ~ 15%。

7.1.7.輔助顯示器

Android 支援輔助顯示器以啟用媒體共享功能和開發人員 API 以存取外部顯示器。

如果裝置實現透過有線、無線或嵌入式附加顯示器連接支援外部顯示器,則:

  • [C-1-1] MUST implement the DisplayManager system service and API as described in the Android SDK documentation.

7.2.輸入裝置

設備實現:

7.2.1.鍵盤

如果裝置實作包括對第三方輸入法編輯器 (IME) 應用程式的支持,則它們:

裝置實作:* [C-0-1] 不得包含與android.content.res.Configuration.keyboard中指定的格式之一(QWERTY 或 12 鍵)不符的硬體鍵盤。 * 應包括額外的軟鍵盤實現。 * 可能包括硬體鍵盤。

7.2.2.非觸控式導航

Android includes support for d-pad, trackball, and wheel as mechanisms for non-touch navigation.

設備實現:

如果設備實現缺乏非觸控導航,它們:

  • [C-1-1] MUST provide a reasonable alternative user interface mechanism for the selection and editing of text, compatible with Input Management Engines.上游 Android 開源實作包括適合與缺乏非觸控導航輸入的裝置一起使用的選擇機制。

7.2.3.導航鍵

The Home , Recents , and Back functions typically provided via an interaction with a dedicated physical button or a distinct portion of the touch screen, are essential to the Android navigation paradigm and therefore, device implementations:

  • [C-0-1] MUST provide a user affordance to launch installed applications that have an activity with the <intent-filter> set with ACTION=MAIN and CATEGORY=LAUNCHER or CATEGORY=LEANBACK_LAUNCHER for Television device implementations.主頁功能應該是這種使用者可供性的機制。
  • 應提供「最近使用」和「返回」功能的按鈕。

如果提供了「首頁」、「最近使用」或「返回」功能,則它們:

  • [C-1-1] 當其中任何一個可存取時,必須可以透過單一操作(例如點擊、雙擊或手勢)進行存取。
  • [C-1-2] 必須明確指示哪個單一操作將觸發每個功能。在按鈕上印上可見的圖示、在螢幕的導覽列部分顯示軟體圖示、或在開箱即用的設定體驗期間引導使用者完成引導的分步示範流程都是此類範例。指示。

設備實現:

  • [SR] are STRONGLY RECOMMENDED to not provide the input mechanism for the Menu function as it is deprecated in favor of action bar since Android 4.0.

如果設備實作提供選單功能,則它們:

  • [C-2-1] 只要操作溢出選單彈出視窗不為空且操作列可見,就必須顯示操作溢位按鈕。
  • [C-2-2] 不得透過選擇操作列中的溢出按鈕來修改操作溢出彈出視窗的位置,但可以在透過選擇選單顯示操作溢出彈出視窗時在螢幕上修改的位置呈現操作溢出彈出視窗功能。

If device implementations do not provide the Menu function, for backwards compatibility, they: * [C-3-1] MUST make the Menu function available to applications when targetSdkVersion is less than 10, wareeiton, asoft phys by asoft 10, wareeiton, phy0, wares , 0, wares by asoft physware, asoft 10, wares by asoft physware, 10, wares by physion, wares , 10, wareeiton, asoft 0, wares , 0, wares by asoft physware, 10, wares by asoft physware, 10, wares by asoft physware, 10, wareeiton, phy0, wares , 0, wares 認為 a手勢。 This Menu function should be accessible unless hidden together with other navigation functions.

If device implementations provide the Assist function , they: * [C-4-1] MUST make the Assist function accessible with a single action (eg tap, double-click or gesture) when other navigation keys are accessible. * [SR] STRONGLY RECOMMENDED to use long press on HOME function as this designated interaction.

如果裝置實作使用螢幕的不同部分來顯示導航鍵,則它們:

  • [C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to applications, and MUST NOT obscure or otherwise interfere with the portion of the screen available to applications.
  • [C-5-2] 必須向符合第 7.1.1 節中定義的要求的應用程式提供部分顯示內容。
  • [C-5-3] MUST honor the flags set by the app through the View.setSystemUiVisibility() API method, so that this distinct portion of the screen (aka the navigation bar) is properly hidden away as documented in the SDK.

7.2.4.觸控螢幕輸入

Android 支援各種指針輸入系統,例如觸控螢幕、觸控板和假觸控輸入裝置。基於觸控螢幕的裝置實現與顯示器相關聯,使得使用者有直接操縱螢幕上的項目的印象。由於使用者直接觸摸螢幕,系統不需要任何額外的功能來指示正在操作的物件。

設備實現:

  • SHOULD have a pointer input system of some kind (either mouse-like or touch).
  • SHOULD support fully independently tracked pointers.

If device implementations include a touchscreen (single-touch or better), they:

  • [C-1-1] MUST report TOUCHSCREEN_FINGER for the Configuration.touchscreen API field.
  • [C-1-2] MUST report the android.hardware.touchscreen and android.hardware.faketouch feature flags.

If device implementations include a touchscreen that can track more than a single touch, they:

  • [C-2-1] MUST report the appropriate feature flags android.hardware.touchscreen.multitouch , android.hardware.touchscreen.multitouch.distinct , android.hardware.touchscreen.multitouch.jazzhand corresponding to the type of the specific touchscreen on the裝置.

If device implementations do not include a touchscreen (and rely on a pointer device only) and meet the fake touch requirements in section 7.2.5 , they:

  • [C-3-1] MUST NOT report any feature flag starting with android.hardware.touchscreen and MUST report only android.hardware.faketouch .

7.2.5.假觸摸輸入

Fake touch interface provides a user input system that approximates a subset of touchscreen capabilities.例如,驅動螢幕上遊標的滑鼠或遙控器類似於觸摸,但需要使用者先指向或聚焦,然後按一下。許多輸入裝置(例​​如滑鼠、觸控板、基於陀螺儀的空中滑鼠、陀螺儀指標、操縱桿和多點觸控觸控板)都可以支援假觸控互動。 Android 包含功能常數 android.hardware.faketouch,它對應於高保真非觸控(基於指針)輸入設備,例如可以充分模擬基於觸控的輸入(包括基本手勢支援)的滑鼠或觸控板,以及表示該設備支持觸控螢幕功能的模擬子集。

If device implementations do not include a touchscreen but include another pointer input system which they want to make available, they:

  • SHOULD declare support for the android.hardware.faketouch feature flag.

If device implementations declare support for android.hardware.faketouch , they:

  • [C-1-1] 必須報告指針位置的絕對 X 和 Y 螢幕位置,並在螢幕上顯示可視指針。
  • [C-1-2] MUST report touch event with the action code that specifies the state change that occurs on the pointer going down or up on the screen .
  • [C-1-3] 必須支援指標在螢幕上的物件上向下和向上移動,這樣使用者就可以模擬點擊螢幕上的物件。
  • [C-1-4] 必須支援在一定時間閾值內將指標向下、指標向上、指標向下然後指標向上放在螢幕上物件的相同位置,這允許使用者模擬雙擊螢幕上的物件。
  • [C-1-5] 必須支援將指標放在螢幕上的任意點上,然後將指標移到螢幕上的任何其他任意點,然後將指標向上,以便使用者可以模擬觸控拖曳。
  • [C-1-6] 必須支援指針向下,然後允許使用者快速將物件移動到螢幕上的不同位置,然後在螢幕上向上指針,這樣使用者就可以在螢幕上拋出物件。
  • [C-1-7] MUST report TOUCHSCREEN_NOTOUCH for the Configuration.touchscreen API field.

If device implementations declare support for android.hardware.faketouch.multitouch.distinct , they:

  • [C-2-1] MUST declare support for android.hardware.faketouch .
  • [C-2-2] 必須支援對兩個或多個獨立指標輸入的不同追蹤。

If device implementations declare support for android.hardware.faketouch.multitouch.jazzhand , they:

  • [C-3-1] MUST declare support for android.hardware.faketouch .
  • [C-3-2] 必須完全獨立地支援 5 個(追蹤手指的手)或更多指針輸入的不同追蹤。

7.2.6。遊戲控制器支持

7.2.6.1.按鈕映射

If device implementations declare the android.hardware.gamepad feature flag, they:

  • [C-1-1] MUST have embed a controller or ship with a separate controller in the box, that would provide means to input all the events listed in the below tables.
  • [C-1-2] MUST be capable to map HID events to it's associated Android view.InputEvent constants as listed in the below tables.上游 Android 實作包括滿足此要求的遊戲控制器的實作。
按鈕HID 用法2安卓按鈕
1 0x09 0x0001 KEYCODE_BUTTON_A (96)
1 0x09 0x0002 KEYCODE_BUTTON_B (97)
X 1 0x09 0x0004 KEYCODE_BUTTON_X (99)
Y 1 0x09 0x0005 KEYCODE_BUTTON_Y (100)
方向鍵向上1
方向鍵向下1
0x01 0x0039 3 AXIS_HAT_Y 4
方向鍵左1
方向鍵右1
0x01 0x0039 3 AXIS_HAT_X 4
左肩按鈕1 0x09 0x0007 KEYCODE_BUTTON_L1 (102)
右肩按鈕1 0x09 0x0008 KEYCODE_BUTTON_R1 (103)
左搖桿點選1 0x09 0x000E KEYCODE_BUTTON_THUMBL (106)
右搖桿點選1 0x09 0x000F KEYCODE_BUTTON_THUMBR (107)
首頁1 0x0c 0x0223 KEYCODE_HOME (3)
返回1 0x0c 0x0224 KEYCODE_BACK (4)

1關鍵事件

2 上述 HID 用法必須在遊戲手把 CA (0x01 0x0005) 內聲明。

3 此用法必須具有邏輯最小值 0、邏輯最大值 7、物理最小值 0、物理最大值 315、單位為度和報告大小 4。邏輯值定義為順時針旋轉遠離垂直軸;例如,邏輯值0表示不旋轉且按下向上按鈕,而邏輯值1表示旋轉45度並且按下向上和向左鍵。

4 MotionEvent

模擬控制1 HID 使用安卓按鈕
左扳機0x02 0x00C5 AXIS_LTRIGGER
右邊扳機0x02 0x00C4 AXIS_RTRIGGER
左搖桿0x01 0x0030
0x01 0x0031
軸_X
Y軸
右搖桿0x01 0x0032
0x01 0x0035
軸_Z
軸_RZ

1 個運動事件

7.2.7.遙控

有關設備特定要求,請參閱第 2.3.1 節

7.3.感應器

If device implementations include a particular sensor type that has a corresponding API for third-party developers, the device implementation MUST implement that API as described in the Android SDK documentation and the Android Open Source documentation on sensors .

設備實現:

  • [C-0-1] MUST accurately report the presence or absence of sensors per the android.content.pm.PackageManager class.
  • [C-0-2] MUST return an accurate list of supported sensors via the SensorManager.getSensorList() and similar methods.
  • [C-0-3] MUST behave reasonably for all other sensor APIs (for example, by returning true or false as appropriate when applications attempt to register listeners, not calling sensor listeners when the corresponding sensors are not present; etc.).

如果裝置實作包含特定感測器類型,且該感測器類型具有供第三方開發人員使用的對應 API,則它們:

  • [C-1-1] 必須使用 Android SDK 文件中定義的每種感測器類型的相關國際單位制(公制)值來報告所有感測器測量值
  • [C-1-2] MUST report sensor data with a maximum latency of 100 milliseconds + 2 * sample_time for the case of a sensor streamed with a minimum required latency of 5 ms + 2 * sample_time when the application processor is active.此延遲不包括任何過濾延遲。
  • [C-1-3] 必須在啟動感測器的 400 毫秒 + 2 * 樣本時間內報告第一個感測器樣本。此樣本的準確度為 0 是可以接受的。
  • [SR] SHOULD report the event time in nanoseconds as defined in the Android SDK documentation, representing the time the event happened and synchronized with the SystemClock.elapsedRealtimeNano() clock.強烈建議使用現有的和新的Android設備來滿足這些要求,以便它們能夠升級到將來的平台版本,其中可能會成為所需的組件。同步誤差應低於100毫秒。

  • [C-1-4] 對於 Android SDK 文件指示為連續感測器的任何 API,裝置實作必須連續提供抖動應低於 3% 的週期性資料樣本,其中抖動定義為差異的標準偏差連續事件之間報告的時間戳值的數量。

  • [C-1-5] 必須確保感測器事件流不得阻止裝置 CPU 進入暫停狀態或從暫停狀態喚醒。

  • 當多個感測器被啟動時,功耗不應超過各個感測器報告的功耗總和。

上面的列表並不全面; Android SDK 和 Android 開源文件在感測器上記錄的行為被視為具有權威性。

某些感測器類型是複合的,這意味著它們可以從一個或多個其他感測器提供的數據中導出。 (Examples include the orientation sensor and the linear acceleration sensor.)

設備實現:

  • 當這些感測器類型包含感測器類型中所述的必備實體感測器時,應實現這些感測器類型。

如果設備實現包括複合感測器,則它們:

  • [C-2-1] 必須按照有關複合感測器的 Android 開源文件中的說明實現感測器。

7.3.1.加速度計

  • 設備實現應該包括一個 3 軸加速度計。

If device implementations include a 3-axis accelerometer, they:

  • [C-1-1] 必須能夠以至少 50 Hz 的頻率報告事件。
  • [C-1-2] MUST implement and report TYPE_ACCELEROMETER sensor.
  • [C-1-3] 必須符合 Android API 中詳述的Android 感測器座標系
  • [C-1-4] 必須能夠在任何軸上從自由落體到四倍重力 (4g) 或以上的情況下進行測量。
  • [C-1-5] 解析度必須至少為 12 位元。
  • [C-1-6] 標準差不得大於 0.05 m/s^,其中標準差應根據在至少 3 秒的時間內以最快採樣率收集的樣本按軸計算。
  • [SR] are STRONGLY RECOMMENDED to implement the TYPE_SIGNIFICANT_MOTION composite sensor.
  • [SR] are STRONGLY RECOMMENDED to implement the TYPE_ACCELEROMETER_UNCALIBRATED sensor if online accelerometer calibration is available.
  • SHOULD implement the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors as described in the Android SDK document.
  • 應報告至少 200 Hz 的事件。
  • 分辨率應至少為 16 位元。
  • 如果特性在生命週期內發生變化,則應在使用時進行校準並進行補償,並在設備重新啟動之間保留補償參數。
  • 應進行溫度補償。
  • SHOULD also implement TYPE_ACCELEROMETER_UNCALIBRATED sensor.

If device implementations include a 3-axis accelerometer and any of the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors are implemented:

  • [C-2-1] The sum of their power consumption MUST always be less than 4 mW.
  • 當設備處於動態或靜態條件時,每個功率應低於 2 mW 和 0.5 mW。

If device implementations include a 3-axis accelerometer and a gyroscope sensor, they:

  • [C-3-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
  • SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor.
  • [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.

If device implementations include a 3-axis accelerometer, a gyroscope sensor and a magnetometer sensor, they:

  • [C-4-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

7.3.2.磁力計

  • 設備實現應該包括一個 3 軸磁力計(指南針)。

If device implementations include a 3-axis magnetometer, they:

  • [C-1-1] MUST implement the TYPE_MAGNETIC_FIELD sensor.
  • [C-1-2] MUST be able to report events up to a frequency of at least 10 Hz and SHOULD report events up to at least 50 Hz.
  • [C-1-3] 必須符合 Android API 中詳述的Android 感測器座標系
  • [C-1-4] 必須能夠在飽和之前在每個軸上測量 -900 µT 到 +900 µT 之間的溫度。
  • [C-1-5] 將磁力計放置在遠離動態(電流感應)和靜態(磁感應)磁場的位置,硬鐵偏移值必須小於 700 µT,並且應該低於 200 µT。
  • [C-1-6] MUST have a resolution equal or denser than 0.6 µT.
  • [C-1-7] MUST support online calibration and compensation of the hard iron bias, and preserve the compensation parameters between device reboots.
  • [C-1-8] 必須應用軟鐵補償 - 可以在設備使用期間或生產期間進行校準。
  • [C-1-9] 必須具有一個標準偏差,該標準偏差是根據每個軸在至少 3 秒的時間內以最快採樣率收集的樣本計算得出的,不得大於 1.5 µT; SHOULD have a standard deviation no greater than 0.5 µT.
  • SHOULD implement TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.
  • [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.

If device implementations include a 3-axis magnetometer, an accelerometer sensor and a gyroscope sensor, they:

  • [C-2-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

如果設備實現包括 3 軸磁力計、加速度計,則它們:

  • MAY implement the TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor.

If device implementations include a 3-axis magnetometer, an accelerometer and TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor, they:

  • [C-3-1] MUST consume less than 10 mW.
  • SHOULD consume less than 3 mW when the sensor is registered for batch mode at 10 Hz.

7.3.3.全球定位系統

設備實現:

  • SHOULD include a GPS/GNSS receiver.

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag, they:

  • [C-1-1] MUST support location outputs at a rate of at least 1 Hz when requested via LocationManager#requestLocationUpdate .
  • [C-1-2] 當連接到0.5 Mbps 或更快的資料時,必須能夠在10 秒內(快速首次定位)在開闊的天空條件(強訊號、可忽略的多路徑、HDOP < 2)中確定位置高速網路連線。通常透過使用某種形式的輔助或預測 GPS/GNSS 技術來滿足此要求,以最大限度地減少 GPS/GNSS 鎖定時間(輔助資料包括參考時間、參考位置和衛星星曆/時鐘)。
    • [C-1-6] 進行此類位置計算後,重新啟動位置請求時,設備實現必須在5 秒內(在初始位置計算後一小時內)在開闊的天空中確定其位置,即使後續請求也如此是在沒有資料連接的情況下和/或在電源循環之後進行的。
  • 在決定位置後的開闊天空條件下,靜止或以小於 1 公尺每秒平方的加速度移動時:

    • [C-1-3] MUST be able to determine location within 20 meters, and speed within 0.5 meters per second, at least 95% of the time.
    • [C-1-4] MUST simultaneously track and report via GnssStatus.Callback at least 8 satellites from one constellation.
    • 應能同時追蹤來自多個星座的至少 24 顆衛星(例如 GPS + 格洛納斯、北斗、伽利略中的至少一個)。
    • [C-1-5] MUST report the GNSS technology generation through the test API 'getGnssYearOfHardware'.
    • [SR] Continue to deliver normal GPS/GNSS location outputs during an emergency phone call.
    • [SR] Report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS.
    • [SR] Report AGC, and Frequency of GNSS measurement.
    • [SR] Report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS/GNSS location.
    • [SR] are STRONGLY RECOMMENDED to meet as many as possible from the additional mandatory requirements for devices reporting the year "2016" or "2017" through the Test API LocationManager.getGnssYearOfHardware() .

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag and the LocationManager.getGnssYearOfHardware() Test API reports the year "2016" or newer, they:

  • [C-2-1] MUST report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
  • [C-2-2] MUST report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag and the LocationManager.getGnssYearOfHardware() Test API reports the year "2017" or newer, they:

  • [C-3-1] MUST continue to deliver normal GPS/GNSS location outputs during an emergency phone call.
  • [C-3-2] MUST report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS.
  • [C-3-3] MUST report AGC, and Frequency of GNSS measurement.
  • [C-3-4] MUST report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS/GNSS location.

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag and the LocationManager.getGnssYearOfHardware() Test API reports the year "2018" or newer, they:

  • [C-4-1] MUST continue to deliver normal GPS/GNSS outputs to applications during a Mobile Station Based (MS-Based) Network Initiated emergency session call.
  • [C-4-2] MUST report positions and measurements to the GNSS Location Provider API's.

7.3.4.陀螺儀

設備實現:

  • SHOULD include a gyroscope (angular change sensor).
  • SHOULD NOT include a gyroscope sensor unless a 3-axis accelerometer is also included.

如果設備實作包括陀螺儀,它們:

  • [C-1-1] 必須能夠以至少 50 Hz 的頻率報告事件。
  • [C-1-2] MUST implement the TYPE_GYROSCOPE sensor and SHOULD also implement TYPE_GYROSCOPE_UNCALIBRATED sensor.
  • [C-1-3] MUST be capable of measuring orientation changes up to 1,000 degrees per second.
  • [C-1-4] MUST have a resolution of 12-bits or more and SHOULD have a resolution of 16-bits or more.
  • [C-1-5] MUST be temperature compensated.
  • [C-1-6] 必須在使用時進行校準和補償,並在設備重新啟動之間保留補償參數。
  • [C-1-7] MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, or rad^2 / s). The variance is allowed to vary with the sampling rate, but MUST be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it SHOULD be no greater than 1e-7 rad^2/s^2.
  • [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the SENSOR_TYPE_GYROSCOPE_UNCALIBRATED sensor.
  • [SR] Calibration error is STRONGLY RECOMMENDED to be less than 0.01 rad/s when device is stationary at room temperature.
  • 應報告至少 200 Hz 的事件。

If device implementations include a gyroscope, an accelerometer sensor and a magnetometer sensor, they:

  • [C-2-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

If device implementations include a gyroscope and a accelerometer sensor, they:

  • [C-3-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
  • [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.
  • SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor.

7.3.5。晴雨表

  • 設備實現應該包括氣壓計(環境氣壓感知器)。

如果設備實現包括氣壓計,則它們:

  • [C-1-1] MUST implement and report TYPE_PRESSURE sensor.
  • [C-1-2] MUST be able to deliver events at 5 Hz or greater.
  • [C-1-3] 必須進行溫度補償。
  • [SR] STRONGLY RECOMMENDED to be able to report pressure measurements in the range 300hPa to 1100hPa.
  • 應具有 1hPa 的絕對精度。
  • 在 20hPa 範圍內應具有 0.12hPa 的相對精度(相當於海平面變化約 200m 時約 1m 的精度)。

7.3.6。溫度計

Device implementations: * MAY include an ambient thermometer (temperature sensor). * MAY but SHOULD NOT include a CPU temperature sensor.

If device implementations include an ambient thermometer (temperature sensor), they:

  • [C-1-1] MUST be defined as SENSOR_TYPE_AMBIENT_TEMPERATURE and MUST measure the ambient (room/vehicle cabin) temperature from where the user is interacting with the device in degrees Celsius.
  • [C-1-2] MUST be defined as SENSOR_TYPE_TEMPERATURE .
  • [C-1-3] MUST measure the temperature of the device CPU.
  • [C-1-4] MUST NOT measure any other temperature.

請注意, SENSOR_TYPE_TEMPERATURE感測器類型在 Android 4.0 中已棄用。

7.3.7.光度計

  • 設備實現可以包括光度計(環境光感測器)。

7.3.8.接近感測器

  • 設備實現可以包括接近感測器。

If device implementations include a proximity sensor, they:

  • [C-1-1] MUST measure the proximity of an object in the same direction as the screen.也就是說,接近感測器的方向必須能夠偵測靠近螢幕的物體,因為這種感測器類型的主要目的是偵測使用者正在使用的手機。 If device implementations include a proximity sensor with any other orientation, it MUST NOT be accessible through this API.
  • [C-1-2] 精度必須為 1 位或更高。

7.3.9.高保真感應器

如果設備實現包括本節中定義的一組更高品質的感測器,並將其提供給第三方應用程序,則它們:

  • [C-1-1] MUST identify the capability through the android.hardware.sensor.hifi_sensors feature flag.

If device implementations declare android.hardware.sensor.hifi_sensors , they:

  • [C-2-1] MUST have a TYPE_ACCELEROMETER sensor which:

    • MUST have a measurement range between at least -8g and +8g, SHOULD have a measurement range between at least -16g and +16g.
    • 測量解析度必須至少為 2048 LSB/g。
    • 必須具有12.5 Hz或更低的最小測量頻率。
    • 最大測量頻率必須為 400 Hz 或更高; SHOULD support the SensorDirectChannel RATE_VERY_FAST .
    • MUST have a measurement noise not above 400 μg/√Hz.
    • 必須實現該感測器的非喚醒形式,並具有至少 3000 個感測器事件的緩衝能力。
    • 必須具有批次功耗不得差3兆瓦。
    • [C-SR] Is STRONGLY RECOMMENDED to have 3dB measurement bandwidth of at least 80% of Nyquist frequency, and white noise spectrum within this bandwidth.
    • 在室溫下測試的加速度隨機遊走應小於 30 μg √Hz。
    • 相對於溫度的偏差變化應為 ≤ +/- 1 mg/°C。
    • 應具有最佳擬合線的非線性≤0.5%,靈敏度變化與溫度≤0.03%/c°。
    • SHOULD have cross-axis sensitivity of < 2.5 % and variation of cross-axis sensitivity < 0.2% in device operation temperature range.
  • [C-2-2] MUST have a TYPE_ACCELEROMETER_UNCALIBRATED with the same quality requirements as TYPE_ACCELEROMETER .

  • [C-2-3] MUST have a TYPE_GYROSCOPE sensor which:

    • 測量範圍必須至少在 -1000 到 +1000 dps 之間。
    • 必須具有至少16個LSB/DPS的測量解析度。
    • 必須具有12.5 Hz或更低的最小測量頻率。
    • 最大測量頻率必須為 400 Hz 或更高; SHOULD support the SensorDirectChannel RATE_VERY_FAST .
    • 測量雜訊必須不高於 0.014°/s/√Hz。
    • [C-SR] Is STRONGLY RECOMMENDED to have 3dB measurement bandwidth of at least 80% of Nyquist frequency, and white noise spectrum within this bandwidth.
    • 在室溫下測試的隨機遊走率應小於 0.001 °/s √Hz。
    • 偏差隨溫度的變化應為 ≤ +/- 0.05 °/ s / °C。
    • 靈敏度隨溫度的變化應≤ 0.02%/°C。
    • 最佳擬合線非線性度應≤ 0.2%。
    • 噪音密度應≤0.007°/s/√Hz。
    • SHOULD have calibration error less than 0.002 rad/s in temperature range 10 ~ 40 ℃ when device is stationary.
    • SHOULD have g-sensitivity less than 0.1°/s/g.
    • SHOULD have cross-axis sensitivity of < 4.0 % and cross-axis sensitivity variation < 0.3% in device operation temperature range.
  • [C-2-4] MUST have a TYPE_GYROSCOPE_UNCALIBRATED with the same quality requirements as TYPE_GYROSCOPE .

  • [C-2-5] MUST have a TYPE_GEOMAGNETIC_FIELD sensor which:

    • MUST have a measurement range between at least -900 and +900 μT.
    • MUST have a measurement resolution of at least 5 LSB/uT.
    • MUST have a minimum measurement frequency of 5 Hz or lower.
    • 最大測量頻率必須為 50 Hz 或更高。
    • MUST have a measurement noise not above 0.5 uT.
  • [C-2-6] MUST have a TYPE_MAGNETIC_FIELD_UNCALIBRATED with the same quality requirements as TYPE_GEOMAGNETIC_FIELD and in addition:

    • 必須實現該感測器的非喚醒形式,並具有至少 600 個感測器事件的緩衝能力。
    • [C-SR] Is STRONGLY RECOMMENDED to have white noise spectrum from 1 Hz to at least 10 Hz when the report rate is 50 Hz or higher.
  • [C-2-7] MUST have a TYPE_PRESSURE sensor which:

    • 測量範圍必須至少在 300 至 1100 hPa 之間。
    • MUST have a measurement resolution of at least 80 LSB/hPa.
    • MUST have a minimum measurement frequency of 1 Hz or lower.
    • MUST have a maximum measurement frequency of 10 Hz or higher.
    • MUST have a measurement noise not above 2 Pa/√Hz.
    • 必須實現該感測器的非喚醒形式,並具有至少 300 個感測器事件的緩衝能力。
    • 批次功耗必須不低於 2 mW。
  • [C-2-8] MUST have a TYPE_GAME_ROTATION_VECTOR sensor which:
    • 必須實現該感測器的非喚醒形式,並具有至少 300 個感測器事件的緩衝能力。
    • 批次功耗必須不低於 4 mW。
  • [C-2-9] MUST have a TYPE_SIGNIFICANT_MOTION sensor which:
    • 設備靜態時功耗不得低於 0.5 mW,設備移動時功耗不得低於 1.5 mW。
  • [C-2-10] MUST have a TYPE_STEP_DETECTOR sensor which:
    • 必須實現該感測器的非喚醒形式,並具有至少 100 個感測器事件的緩衝能力。
    • 設備靜態時功耗不得低於 0.5 mW,設備移動時功耗不得低於 1.5 mW。
    • 批次功耗必須不低於 4 mW。
  • [C-2-11] MUST have a TYPE_STEP_COUNTER sensor which:
    • 設備靜態時功耗不得低於 0.5 mW,設備移動時功耗不得低於 1.5 mW。
  • [C-2-12] MUST have a TILT_DETECTOR sensor which:
    • 設備靜態時功耗不得低於 0.5 mW,設備移動時功耗不得低於 1.5 mW。
  • [C-2-13] The event timestamp of the same physical event reported by the Accelerometer, Gyroscope, and Magnetometer MUST be within 2.5 milliseconds of each other. The event timestamp of the same physical event reported by the Accelerometer and Gyroscope SHOULD be within 0.25 milliseconds of each other.
  • [C-2-14] MUST have Gyroscope sensor event timestamps on the same time base as the camera subsystem and within 1 milliseconds of error.
  • [C-2-15] MUST deliver samples to applications within 5 milliseconds from the time when the data is available on any of the above physical sensors to the application.
  • [C-2-16] MUST NOT have a power consumption higher than 0.5 mW when device is static and 2.0 mW when device is moving when any combination of the following sensors are enabled:
    • SENSOR_TYPE_SIGNIFICANT_MOTION
    • SENSOR_TYPE_STEP_DETECTOR
    • SENSOR_TYPE_STEP_COUNTER
    • SENSOR_TILT_DETECTORS
  • [C-2-17] MAY have a TYPE_PROXIMITY sensor, but if present MUST have a minimum buffer capability of 100 sensor events.

Note that all power consumption requirements in this section do not include the power consumption of the Application Processor. It is inclusive of the power drawn by the entire sensor chain—the sensor, any supporting circuitry, any dedicated sensor processing system, etc.

如果設備實現包括直接感測器支持,則它們:

  • [C-3-1] MUST correctly declare support of direct channel types and direct report rates level through the isDirectChannelTypeSupported and getHighestDirectReportRateLevel API.
  • [C-3-2] 對於聲明支援感測器直接通道的所有感測器,必須至少支援兩種感測器直接通道類型之一。
  • SHOULD support event reporting through sensor direct channel for primary sensor (non-wakeup variant) of the following types:
    • TYPE_ACCELEROMETER
    • TYPE_ACCELEROMETER_UNCALIBRATED
    • TYPE_GYROSCOPE
    • TYPE_GYROSCOPE_UNCALIBRATED
    • TYPE_MAGNETIC_FIELD
    • TYPE_MAGNETIC_FIELD_UNCALIBRATED

7.3.10.生物辨識感測器

7.3.10.1.指紋感應器

如果裝置實作包括安全鎖定螢幕,則:

  • SHOULD include a fingerprint sensor.

If device implementations include a fingerprint sensor and make the sensor available to third-party apps, they:

  • [C-1-1] MUST declare support for the android.hardware.fingerprint feature.
  • [C-1-2] MUST fully implement the corresponding API as described in the Android SDK documentation.
  • [C-1-3] MUST have a false acceptance rate not higher than 0.002%.
  • [SR] Are STRONGLY RECOMMENDED to have a spoof and imposter acceptance rate not higher than 7%.
  • [C-1-4] MUST disclose that this mode may be less secure than a strong PIN, pattern, or password and clearly enumerate the risks of enabling it, if the spoof and imposter acceptance rates are higher than 7%.
  • [C-1-5] MUST rate limit attempts for at least 30 seconds after five false trials for fingerprint verification.
  • [C-1-6] MUST have a hardware-backed keystore implementation, and perform the fingerprint matching in a Trusted Execution Environment (TEE) or on a chip with a secure channel to the TEE.
  • [C-1-7] MUST have all identifiable fingerprint data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the TEE, or a chip with a secure channel to the TEE as documented in the implementation guidelines on the Android Open Source Project site.
  • [C-1-8] MUST prevent adding a fingerprint without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so.
  • [C-1-9] MUST NOT enable 3rd-party applications to distinguish between individual fingerprints.
  • [C-1-10] MUST honor the DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT flag.
  • [C-1-11] MUST, when upgraded from a version earlier than Android 6.0, have the fingerprint data securely migrated to meet the above requirements or removed.
  • [C-1-12] MUST completely remove all identifiable fingerprint data for a user when the user's account is removed (including via a factory reset).
  • [C-1-13] MUST not allow unencrypted access to identifiable fingerprint data or any data derived from it (such as embeddings) to the Application Processor.
  • [SR] Are STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device.
  • [SR] Are STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the fingerprint sensor is touched until the screen is unlocked, for one enrolled finger.
  • SHOULD use the Android Fingerprint icon provided in the Android Open Source Project.
7.3.10.2. Other Biometric Sensors

If device implementations include one or more non-fingerprint-based-biometric sensors and make them available to third-party apps they:

  • [C-1-1] MUST have a false acceptance rate not higher than 0.002%.
  • [C-SR] Are STRONGLY RECOMMENDED to have a spoof and imposter acceptance rate not higher than 7%.
  • [C-1-2] MUST disclose that this mode may be less secure than a strong PIN, pattern, or password and clearly enumerate the risks of enabling it, if the spoof and imposter acceptance rates are higher than 7%.
  • [C-1-3] MUST rate limit attempts for at least 30 seconds after five false trials for biometric verification - where a false trial is one with an adequate capture quality (ACQUIRED_GOOD) that does not match an enrolled biometric
  • [C-1-4] MUST have a hardware-backed keystore implementation, and perform the biometric matching in a TEE or on a chip with a secure channel to the TEE.
  • [C-1-5] MUST have all identifiable data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the TEE, or a chip with a secure channel to the TEE as documented in the implementation guidelines on the Android Open Source Project site.
  • [C-1-6] MUST prevent adding new biometrics without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so.
  • [C-1-7] MUST NOT enable third-party applications to distinguish between biometric enrollments.
  • [C-1-8] MUST honor the individual flag for that biometric (ie: DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT , DevicePolicymanager.KEYGUARD_DISABLE_FACE , or DevicePolicymanager.KEYGUARD_DISABLE_IRIS ).
  • [C-1-9] MUST completely remove all identifiable biometric data for a user when the user's account is removed (including via a factory reset).
  • [C-1-10] MUST not allow unencrypted access to identifiable biometric data or any data derived from it (such as embeddings) to the Application Processor outside the context of the TEE.
  • [C-SR] Are STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device.
  • [C-SR] Are STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the biometric is detected, until the screen is unlocked, for each enrolled biometric.

7.3.11. Android 汽車專用感光元件

Automotive-specific sensors are defined in the android.car.CarSensorManager API .

7.3.11.1.目前檔位

See Section 2.5.1 for device-specific requirements.

7.3.11.2。日夜模式

See Section 2.5.1 for device-specific requirements.

7.3.11.3。駕駛狀態

This requirement is deprecated.

7.3.11.4。輪速

See Section 2.5.1 for device-specific requirements.

7.3.11.5.駐車制動

See Section 2.5.1 for device-specific requirements.

7.3.12.姿勢感測器

設備實現:

  • 可支援 6 個自由度的姿態感測器。

如果設備實現支援具有 6 個自由度的姿態感測器,則它們:

  • [C-1-1] MUST implement and report TYPE_POSE_6DOF sensor.
  • [C-1-2] MUST be more accurate than the rotation vector alone.

7.4.數據連接

7.4.1.電話

Android API 和本文檔中使用的「電話」特別指與透過 GSM 或 CDMA 網路撥打語音電話和發送 SMS 訊息相關的硬體。雖然這些語音通話可能會也可能不會進行資料包交換,但出於 Android 的目的,它們被視為獨立於可能使用相同網路實現的任何資料連線。換句話說,Android「電話」功能和 API 特指語音通話和簡訊。 For instance, device implementations that cannot place calls or send/receive SMS messages are not considered a telephony device, regardless of whether they use a cellular network for data connectivity.

  • Android 可以在不包含電話硬體的裝置上使用。也就是說,Android 相容於手機以外的裝置。

If device implementations include GSM or CDMA telephony, they:

  • [C-1-1] MUST declare the android.hardware.telephony feature flag and other sub-feature flags according to the technology.
  • [C-1-2] 必須為該技術的 API 提供全面支援。

如果設備實作不包括電話硬件,則:

  • [C-2-1] MUST implement the full APIs as no-ops.
7.4.1.1.號碼屏蔽相容性

If device implementations report the android.hardware.telephony feature , they:

  • [C-1-1] MUST include number blocking support
  • [C-1-2] MUST fully implement BlockedNumberContract and the corresponding API as described in the SDK documentation.
  • [C-1-3] MUST block all calls and messages from a phone number in 'BlockedNumberProvider' without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation.
  • [C-1-4] MUST NOT write to the platform call log provider for a blocked call.
  • [C-1-5] MUST NOT write to the Telephony provider for a blocked message.
  • [C-1-6] MUST implement a blocked numbers management UI, which is opened with the intent returned by TelecomManager.createManageBlockedNumbersIntent() method.
  • [C-1-7] MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected.
  • SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0.
7.4.1.2. Telecom API

If device implementations report android.hardware.telephony , they:

  • [C-1-1] MUST support the ConnectionService APIs described in the SDK .
  • [C-1-2] MUST display a new incoming call and provide user affordance to accept or reject the incoming call when the user is on an ongoing call that is made by a third-party app that does not support the hold feature specified via CAPABILITY_SUPPORT_HOLD .
  • [C-SR] Are STRONGLY RECOMMENDED to notify the user that answering an incoming call will drop an ongoing call.

    The AOSP implementation meets these requirements by a heads-up notification which indicates to the user that answering an incoming call will cause the other call to be dropped.

  • [C-SR] Are STRONGLY RECOMMENDED to preload the default dialer app that shows a call log entry and the name of a third-party app in its call log when the third-party app sets the EXTRA_LOG_SELF_MANAGED_CALLS extras key on its PhoneAccount to true .

  • [C-SR] Are STRONGLY RECOMMENDED to handle the audio headset's KEYCODE_MEDIA_PLAY_PAUSE and KEYCODE_HEADSETHOOK events for the android.telecom APIs as below:

7.4.2. IEEE 802.11(無線網路)

設備實現:

  • SHOULD include support for one or more forms of 802.11.

If device implementations include support for 802.11 and expose the functionality to a third-party application, they:

  • [C-1-1] MUST implement the corresponding Android API.
  • [C-1-2] MUST report the hardware feature flag android.hardware.wifi .
  • [C-1-3] MUST implement the multicast API as described in the SDK documentation.
  • [C-1-4] MUST support multicast DNS (mDNS) and MUST NOT filter mDNS packets (224.0.0.251) at any time of operation including:
    • Even when the screen is not in an active state.
    • For Android Television device implementations, even when in standby power states.
  • [C-1-5] MUST NOT treat the WifiManager.enableNetwork() API method call as a sufficient indication to switch the currently active Network that is used by default for application traffic and is returned by ConnectivityManager API methods such as getActiveNetwork and registerDefaultNetworkCallback . In other words, they MAY only disable the Internet access provided by any other network provider (eg mobile data) if they successfully validate that the Wi-Fi network is providing Internet access.
  • [C-SR] Are STRONGLY RECOMMENDED, when the ConnectivityManager.reportNetworkConnectivity() API method is called, to re-evaluate the Internet access on the Network and, once the evaluation determines that the current Network no longer provides Internet access, switch to any other available network (eg mobile data) that provides Internet access.
  • [C-SR] Are STRONGLY RECOMMENDED to randomize the source MAC address and sequence number of probe request frames, once at the beginning of each scan, while STA is disconnected.
    • Each group of probe request frames comprising one scan should use one consistent MAC address (SHOULD NOT randomize MAC address halfway through a scan).
    • Probe request sequence number should iterate as normal (sequentially) between the probe requests in a scan.
    • Probe request sequence number should randomize between the last probe request of a scan and the first probe request of the next scan.
  • [C-SR] Are STRONGLY RECOMMENDED, while STA is disconnected, to allow only the following elements in probe request frames:
    • SSID Parameter Set (0)
    • DS Parameter Set (3)

If device implementations support Wi-Fi and use Wi-Fi for location scanning, they:

7.4.2.1.無線直連

設備實現:

  • SHOULD include support for Wi-Fi Direct (Wi-Fi peer-to-peer).

If device implementations include support for Wi-Fi Direct, they:

  • [C-1-1] MUST implement the corresponding Android API as described in the SDK documentation.
  • [C-1-2] MUST report the hardware feature android.hardware.wifi.direct .
  • [C-1-3] MUST support regular Wi-Fi operation.
  • [C-1-4] MUST support Wi-Fi and Wi-Fi Direct operations concurrently.

設備實現:

If device implementations include support for TDLS and TDLS is enabled by the WiFiManager API, they:

  • [C-1-1] MUST declare support for TDLS through WifiManager.isTdlsSupported .
  • 僅當可能且有益時才應使用 TDLS。
  • 當 TDLS 的效能可能比透過 Wi-Fi 存取點差時,應該採用一些啟發式方法,而不是使用 TDLS。
7.4.2.3.無線網路感知

設備實現:

If device implementations include support for Wi-Fi Aware and expose the functionality to third-party apps, then they:

  • [C-1-1] MUST implement the WifiAwareManager APIs as described in the SDK documentation .
  • [C-1-2] MUST declare the android.hardware.wifi.aware feature flag.
  • [C-1-3] MUST support Wi-Fi and Wi-Fi Aware operations concurrently.
  • [C-1-4] MUST randomize the Wi-Fi Aware management interface address at intervals no longer than 30 minutes and whenever Wi-Fi Aware is enabled.

If device implementations include support for Wi-Fi Aware and Wi-Fi Location as described in Section 7.4.2.5 and exposes these functionalities to third-party apps, then they:

7.4.2.4. Wi-Fi 通行點

設備實現:

If device implementations include support for Wi-Fi Passpoint, they:

  • [C-1-1] MUST implement the Passpoint related WifiManager APIs as described in the SDK documentation .
  • [C-1-2] MUST support IEEE 802.11u standard, specifically related to Network Discovery and Selection, such as Generic Advertisement Service (GAS) and Access Network Query Protocol (ANQP).

Conversely if device implementations do not include support for Wi-Fi Passpoint:

  • [C-2-1] The implementation of the Passpoint related WifiManager APIs MUST throw an UnsupportedOperationException .
7.4.2.5. Wi-Fi Location (Wi-Fi Round Trip Time - RTT)

設備實現:

If device implementations include support for Wi-Fi Location and expose the functionality to third-party apps, then they:

  • [C-1-1] MUST implement the WifiRttManager APIs as described in the SDK documentation .
  • [C-1-2] MUST declare the android.hardware.wifi.rtt feature flag.
  • [C-1-3] MUST randomize the source MAC address for each RTT burst which is executed while the Wi-Fi interface on which the RTT is being executed is not associated to an Access Point.

7.4.3.藍牙

If device implementations support Bluetooth Audio profile, they:

  • SHOULD support Advanced Audio Codecs and Bluetooth Audio Codecs (eg LDAC).

If device implementations support HFP, A2DP and AVRCP, they:

  • SHOULD support at least 5 total connected devices.

If device implementations declare android.hardware.vr.high_performance feature, they:

  • [C-1-1] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension.

Android includes support for Bluetooth and Bluetooth Low Energy .

If device implementations include support for Bluetooth and Bluetooth Low Energy, they:

  • [C-2-1] MUST declare the relevant platform features ( android.hardware.bluetooth and android.hardware.bluetooth_le respectively) and implement the platform APIs.
  • SHOULD implement relevant Bluetooth profiles such as A2DP, AVRCP, OBEX, HFP, etc. as appropriate for the device.

If device implementations include support for Bluetooth Low Energy, they:

  • [C-3-1] MUST declare the hardware feature android.hardware.bluetooth_le .
  • [C-3-2] MUST enable the GATT (generic attribute profile) based Bluetooth APIs as described in the SDK documentation and android.bluetooth .
  • [C-3-3] MUST report the correct value for BluetoothAdapter.isOffloadedFilteringSupported() to indicate whether the filtering logic for the ScanFilter API classes is implemented.
  • [C-3-4] MUST report the correct value for BluetoothAdapter.isMultipleAdvertisementSupported() to indicate whether Low Energy Advertising is supported.
  • SHOULD support offloading of the filtering logic to the bluetooth chipset when implementing the ScanFilter API .
  • SHOULD support offloading of the batched scanning to the bluetooth chipset.
  • SHOULD support multi advertisement with at least 4 slots.

  • [SR] STRONGLY RECOMMENDED to implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy.

If device implementations support Bluetooth LE and use Bluetooth LE for location scanning, they:

  • [C-4-1] MUST provide a user affordance to enable/disable the value read through the System API BluetoothAdapter.isBleScanAlwaysAvailable() .

7.4.4.近場通訊

設備實現:

  • SHOULD include a transceiver and related hardware for Near-Field Communications (NFC).
  • [C-0-1] MUST implement android.nfc.NdefMessage and android.nfc.NdefRecord APIs even if they do not include support for NFC or declare the android.hardware.nfc feature as the classes represent a declare the android.hardware.nfc feature as the classes represent a protocol-presmatent as the classs represent a protocol. 。

If device implementations include NFC hardware and plan to make it available to third-party apps, they:

  • [C-1-1] MUST report the android.hardware.nfc feature from the android.content.pm.PackageManager.hasSystemFeature() method .
  • MUST be capable of reading and writing NDEF messages via the following NFC standards as below:
  • [C-1-2] MUST be capable of acting as an NFC Forum reader/writer (as defined by the NFC Forum technical specification NFCForum-TS-DigitalProtocol-1.0) via the following NFC standards:
    • NFCA (ISO14443-3A)
    • NFCB (ISO14443-3B)
    • NfcF (JIS X 6319-4)
    • ISODep (ISO 14443-4)
    • NFC Forum Tag Types 1, 2, 3, 4, 5 (defined by the NFC Forum)
  • [SR] STRONGLY RECOMMENDED to be capable of reading and writing NDEF messages as well as raw data via the following NFC standards. Note that while the NFC standards are stated as STRONGLY RECOMMENDED, the Compatibility Definition for a future version is planned to change these to MUST.這些標準在此版本中是可選的,但在未來版本中將是必需的。我們強烈鼓勵運行此版本 Android 的現有設備和新設備立即滿足這些要求,以便它們能夠升級到未來的平台版本。

  • [C-1-3] MUST be capable of transmitting and receiving data via the following peer-to-peer standards and protocols:

    • ISO 18092
    • LLCP 1.2 (defined by the NFC Forum)
    • SDP 1.0(由 NFC 論壇定義)
    • NDEF Push Protocol
    • SNEP 1.0(由 NFC 論壇定義)
  • [C-1-4] MUST include support for Android Beam and SHOULD enable Android Beam by default.
  • [C-1-5] MUST be able to send and receive using Android Beam, when Android Beam is enabled or another proprietary NFC P2p mode is turned on.
  • [C-1-6] MUST implement the SNEP default server.預設 SNEP 伺服器收到的有效 NDEF 訊息必須使用android.nfc.ACTION_NDEF_DISCOVERED意圖分派到應用程式。在設定中停用 Android Beam 不得停用傳入 NDEF 訊息的調度。
  • [C-1-7] MUST honor the android.settings.NFCSHARING_SETTINGS intent to show NFC sharing settings .
  • [C-1-8] MUST implement the NPP server. NPP 伺服器接收的訊息必須以與 SNEP 預設伺服器相同的方式進行處理。
  • [C-1-9] MUST implement a SNEP client and attempt to send outbound P2P NDEF to the default SNEP server when Android Beam is enabled.如果未找到預設 SNEP 伺服器,則用戶端必須嘗試傳送到 NPP 伺服器。
  • [C-1-10] MUST allow foreground activities to set the outbound P2P NDEF message using android.nfc.NfcAdapter.setNdefPushMessage , and android.nfc.NfcAdapter.setNdefPushMessageCallback , and android.nfc.NfcAdapter.enableForegroundNdefPush .
  • 在發送出站 P2P NDEF 訊息之前,應使用手勢或螢幕確認,例如「觸摸到光束」。
  • [C-1-11] MUST support NFC Connection handover to Bluetooth when the device supports Bluetooth Object Push Profile.
  • [C-1-12] MUST support connection handover to Bluetooth when using android.nfc.NfcAdapter.setBeamPushUris , by implementing the “ Connection Handover version 1.2 ” and “ Bluetooth Secure Simple Pairing Using NFC version 1.0 ” specs from the NFC Forum.此類實作必須實作服務名稱為「urn:nfc:sn:handover」的切換 LLCP 服務,用於透過 NFC 交換切換請求/選擇記錄,並且必須使用藍牙物件推送設定檔進行實際的藍牙資料傳輸。由於遺留原因(為了與 Android 4.1 裝置保持相容),實現仍應接受 SNEP GET 請求,以透過 NFC 交換切換請求/選擇記錄。然而,實作本身不應該發送 SNEP GET 請求來執行連線切換。
  • [C-1-13] MUST poll for all supported technologies while in NFC discovery mode.
  • 當裝置喚醒且螢幕處於作用中且鎖定螢幕解鎖時,應處於 NFC 發現模式。
  • SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm NFC Barcode products.

Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications cited above.

Android 支援 NFC 主機卡模擬 (HCE) 模式。

If device implementations include an NFC controller chipset capable of HCE (for NfcA and/or NfcB) and support Application ID (AID) routing, they:

  • [C-2-1] MUST report the android.hardware.nfc.hce feature constant.
  • [C-2-2] MUST support NFC HCE APIs as defined in the Android SDK.

If device implementations include an NFC controller chipset capable of HCE for NfcF, and implement the feature for third-party applications, they:

  • [C-3-1] MUST report the android.hardware.nfc.hcef feature constant.
  • [C-3-2] MUST implement the NfcF Card Emulation APIs as defined in the Android SDK.

If device implementations include general NFC support as described in this section and support MIFARE technologies (MIFARE Classic, MIFARE Ultralight, NDEF on MIFARE Classic) in the reader/writer role, they:

  • [C-4-1] MUST implement the corresponding Android APIs as documented by the Android SDK.
  • [C-4-2] MUST report the feature com.nxp.mifare from the android.content.pm.PackageManager.hasSystemFeature () method. Note that this is not a standard Android feature and as such does not appear as a constant in the android.content.pm.PackageManager class.

7.4.5。最低網路能力

設備實現:

  • [C-0-1] MUST include support for one or more forms of data networking. Specifically, device implementations MUST include support for at least one data standard capable of 200 Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet and Bluetooth PAN.
  • SHOULD also include support for at least one common wireless data standard, such as 802.11 (Wi-Fi), when a physical networking standard (such as Ethernet) is the primary data connection.
  • MAY implement more than one form of data connectivity.
  • [C-0-2] MUST include an IPv6 networking stack and support IPv6 communication using the managed APIs, such as java.net.Socket and java.net.URLConnection , as well as the native APIs, such as AF_INET6 sockets.
  • [C-0-3] MUST enable IPv6 by default.
  • MUST ensure that IPv6 communication is as reliable as IPv4, for example:
    • [C-0-4] MUST maintain IPv6 connectivity in doze mode.
    • [C-0-5] Rate-limiting MUST NOT cause the device to lose IPv6 connectivity on any IPv6-compliant network that uses RA lifetimes of at least 180 seconds.
  • [C-0-6] MUST provide third-party applications with direct IPv6 connectivity to the network when connected to an IPv6 network, without any form of address or port translation happening locally on the device. Both managed APIs such as Socket#getLocalAddress or Socket#getLocalPort ) and NDK APIs such as getsockname() or IPV6_PKTINFO MUST return the IP address and port that is actually used to send and receive packets on the network.

The required level of IPv6 support depends on the network type, as shown in the following requirements.

If device implementations support Wi-Fi, they:

  • [C-1-1] MUST support dual-stack and IPv6-only operation on Wi-Fi.

If device implementations support Ethernet, they:

  • [C-2-1] MUST support dual-stack operation on Ethernet.

If device implementations support Cellular data, they:

  • SHOULD support IPv6 operation (IPv6-only and possibly dual-stack) on cellular.

If device implementations support more than one network type (eg, Wi-Fi and cellular data), they:

  • [C-3-1] MUST simultaneously meet the above requirements on each network when the device is simultaneously connected to more than one network type.

7.4.6。同步設定

設備實現:

7.4.7。資料保護程式

如果設備實現包括按流量計費的連接,則它們是:

  • [SR] STRONGLY RECOMMENDED to provide the data saver mode.

如果設備實作提供資料保護模式,則它們:

If device implementations do not provide the data saver mode, they:

  • [C-2-1] MUST return the value RESTRICT_BACKGROUND_STATUS_DISABLED for ConnectivityManager.getRestrictBackgroundStatus()
  • [C-2-2] MUST NOT broadcast ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED .
  • [C-2-3] MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.

7.4.8。安全元件

If device implementations support Open Mobile API capable secure elements and make them available to 3rd-party apps, they:

7.5。相機

If device implementations include at least one camera, they:

  • [C-1-1] MUST declare the android.hardware.camera.any feature flag.
  • [C-1-2] 當相機出於基本預覽和靜態目的而開啟時,應用程式必須能夠同時分配 3 個 RGBA_8888 位元圖,其大小等於裝置上最高解析度相機感測器產生的影像的大小擷取。

7.5.1.後置攝像頭

後置相機是位於裝置與顯示器相對的一側的攝影機;也就是說,它像傳統相機一樣對設備遠端的場景進行成像。

設備實現:

  • SHOULD include a rear-facing camera.

If device implementations include at least one rear-facing camera, they:

  • [C-1-1] MUST report the feature flag android.hardware.camera and android.hardware.camera.any .
  • [C-1-2] 解析度必須至少為 200 萬像素。
  • 應該在相機驅動程式中實現硬體自動對焦或軟體自動對焦(對應用程式軟體透明)。
  • 可能具有定焦或 EDOF(擴展景深)硬體。
  • 可能包括閃光燈。

If the camera includes a flash:

  • [C-2-1] the flash lamp MUST NOT be lit while an android.hardware.Camera.PreviewCallback instance has been registered on a Camera preview surface, unless the application has explicitly enabled the FLASH_MODE_AUTO FLASH_MODE_ON on the Camera.Parameters物件。請注意,此約束不適用於裝置的內建系統攝影機應用程序,而僅適用於使用Camera.PreviewCallback的第三方應用程式。

7.5.2.前置鏡頭

前置相機是與顯示器位於裝置同一側的相機;也就是說,通常用於對使用者進行成像的相機,例如用於視訊會議和類似應用。

設備實現:

  • 可能包括前置鏡頭。

如果設備實現至少包含一個前置鏡頭,則:

  • [C-1-1] MUST report the feature flag android.hardware.camera.any and android.hardware.camera.front .
  • [C-1-2] MUST have a resolution of at least VGA (640x480 pixels).
  • [C-1-3] MUST NOT use a front-facing camera as the default for the Camera API and MUST NOT configure the API to treat a front-facing camera as the default rear-facing camera, even if it is the only camera在設備上。
  • [C-1-4] The camera preview MUST be mirrored horizo​​​​ntally relative to the orientation specified by the application when the current application has explicitly requested that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation() 。 Conversely, the preview MUST be mirrored along the device's default horizontal axis when the current application does not explicitly request that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation() method.
  • [C-1-5] MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage.
  • [C-1-6] 必須以與相機預覽影像串流相同的方式鏡像後視圖顯示的影像。
  • 可以包括後置相機可用的功能(例如自動對焦、閃光燈等),如第 7.5.1 節所述。

如果設備實作能夠由使用者旋轉(例如透過加速計自動旋轉或透過使用者輸入手動旋轉):

  • [C-2-1] 相機預覽必須相對於裝置的當前方向水平鏡像。

7.5.3.外接攝影機

設備實現:

  • MAY include support for an external camera that is not necessarily always connected.

如果設備實現包括對外部攝影機的支持,則:

  • [C-1-1] MUST declare the platform feature flag android.hardware.camera.external and android.hardware camera.any .
  • [C-1-2] MUST support USB Video Class (UVC 1.0 or higher) if the external camera connects through the USB host port.
  • [C-1-3] MUST pass camera CTS tests with a physical external camera device connected.相機 CTS 測試的詳細資訊可在source.android.com上找到。
  • SHOULD support video compressions such as MJPEG to enable transfer of high-quality unencoded streams (ie raw or independently compressed picture streams).
  • 可以支援多個攝影機。
  • MAY support camera-based video encoding.

如果支援基於攝影機的視訊編碼:

  • [C-2-1] A simultaneous unencoded / MJPEG stream (QVGA or greater resolution) MUST be accessible to the device implementation.

7.5.4.相機 API 行為

Android 包含兩個用於存取相機的API 包,較新的android.hardware.camera2 API 向應用程式公開較低級別的相機控制,包括高效的零複製突發/串流媒體流以及曝光、增益、白平衡增益的每幀控制、色彩轉換、去雜訊、銳化等。

The older API package, android.hardware.Camera , is marked as deprecated in Android 5.0 but as it should still be available for apps to use. Android device implementations MUST ensure the continued support of the API as described in this section and in the Android SDK.

All features that are common between the deprecated android.hardware.Camera class and the newer android.hardware.camera2 package MUST have equivalent performance and quality in both APIs. For example, with equivalent settings, autofocus speed and accuracy must be identical, and the quality of captured images must be the same. Features that depend on the different semantics of the two APIs are not required to have matching speed or quality, but SHOULD match as closely as possible.

Device implementations MUST implement the following behaviors for the camera-related APIs, for all available cameras.設備實現:

  • [C-0-1] MUST use android.hardware.PixelFormat.YCbCr_420_SP for preview data provided to application callbacks when an application has never called android.hardware.Camera.Parameters.setPreviewFormat(int) .
  • [C-0-2] MUST further be in the NV21 encoding format when an application registers an android.hardware.Camera.PreviewCallback instance and the system calls the onPreviewFrame() method and the preview format is YCbCr_420_SP, the data in the byte[] passed into onPreviewFrame() .也就是說,NV21 必須是預設值。
  • [C-0-3] MUST support the YV12 format (as denoted by the android.graphics.ImageFormat.YV12 constant) for camera previews for both front- and rear-facing cameras for android.hardware.Camera . (硬體視訊編碼器和相機可能使用任何本機像素格式,但是設定實作必須支援轉換為YV12。)
  • [C-0-4] MUST support the android.hardware.ImageFormat.YUV_420_888 and android.hardware.ImageFormat.JPEG formats as outputs through the android.media.ImageReader API for android.hardware.camera2 devices that advertise REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE capability in android.request.availableCapabilities .
  • [C-0-5] 仍必須實作 Android SDK 文件中包含的完整相機 API ,無論裝置是否包含硬體自動對焦或其他功能。例如,缺乏自動對焦的攝影機仍然必須呼叫任何已註冊的android.hardware.Camera.AutoFocusCallback實例(即使這與非Autofocus相機無關,請注意)請注意,這確實適用於前面的相機;例如,即使大多數前置鏡頭不支援自動對焦,API 回呼仍然必須按照描述進行「偽造」。
  • [C-0-6] MUST recognize and honor each parameter name defined as a constant on the android.hardware.Camera.Parameters class. Conversely, device implementations MUST NOT honor or recognize string constants passed to the android.hardware.Camera.setParameters() method other than those documented as constants on the android.hardware.Camera.Parameters .也就是說,如果硬體允許,則必須支援所有標準攝影機參數,並且必須不支援自訂相機參數類型。 For instance, device implementations that support image capture using high dynamic range (HDR) imaging techniques MUST support camera parameter Camera.SCENE_MODE_HDR .
  • [C-0-7] MUST report the proper level of support with the android.info.supportedHardwareLevel property as described in the Android SDK and report the appropriate framework feature flags .
  • [C-0-8] MUST also declare its individual camera capabilities of android.hardware.camera2 via the android.request.availableCapabilities property and declare the appropriate feature flags ;如果任何連接的相機設備支援該功能,則必須定義該功能標誌。
  • [C-0-9] MUST broadcast the Camera.ACTION_NEW_PICTURE intent whenever a new picture is taken by the camera and the entry of the picture has been added to the media store.
  • [C-0-10] MUST broadcast the Camera.ACTION_NEW_VIDEO intent whenever a new video is recorded by the camera and the entry of the picture has been added to the media store.
  • [C-SR] Are STRONGLY RECOMMENDED to support a logical camera device that lists capability CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA , for devices with multiple cameras facing the same direction, consisting of each physical camera facing that direction, as long as the physical camera type is supported by the framework and CameraCharacteristics.INFO_SUPPORTED_HARDWARE_LEVEL for the physical cameras is either LIMITED , FULL , or LEVEL_3 .

7.5.5。相機方向

如果設備實現具有前置或後置攝像頭,則此類攝像頭:

  • [C-1-1] 方向必須使相機的長邊尺寸與螢幕的長邊尺寸對齊。也就是說,當設備處於橫向方向時,相機必須以橫向方向捕捉影像。無論設備的自然方向如何,這都適用;也就是說,它適用於橫向主設備以及縱向主設備。

7.6。記憶體和儲存

7.6.1.最小內存和存儲

設備實現:

  • [C-0-1] 必須包含應用程式可以用來下載資料檔案的下載管理器,並且它們必須能夠將大小至少為 100MB 的單一檔案下載到預設「快取」位置。

7.6.2.應用程式共享儲存

設備實現:

  • [C-0-1] MUST offer storage to be shared by applications, also often referred as “shared external storage”, "application shared storage" or by the Linux path "/sdcard" it is mounted on.
  • [C-0-2] 必須配置預設安裝的共享存儲,即“開箱即用”,無論存儲是在內部存儲組件還是可移動存儲介質(例如安全數位卡插槽)上實現)。
  • [C-0-3] MUST mount the application shared storage directly on the Linux path sdcard or include a Linux symbolic link from sdcard to the actual mount point.
  • [C-0-4] MUST enforce the android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage as documented in the SDK.共享儲存否則必須透過獲得該許可的任何應用程式可寫入。

設備實作可以使用以下任一方式滿足上述要求:

  • 使用者可存取的可移動存儲,例如安全數位 (SD) 卡插槽。
  • Android 開源專案 (AOSP) 中實現的內部(不可移動)儲存的一部分。

If device implementations use removable storage to satisfy the above requirements, they:

  • [C-1-1] 必須實作 Toast 或彈出式使用者介面,以便在插槽中沒有插入儲存媒體時警告使用者。
  • [C-1-2] 必須包含 FAT 格式的儲存媒體(例如 SD 卡),或在包裝盒和購買時提供的其他資料上標明該儲存媒體必須單獨購買。

如果設備實現使用一部分不可移動儲存來滿足上述要求,則:

  • SHOULD use the AOSP implementation of the internal application shared storage.
  • 可與應用程式私有資料共用儲存空間。

If device implementations include multiple shared storage paths (such as both an SD card slot and shared internal storage), they:

  • [C-2-1] MUST allow only preinstalled and privileged Android applications with the WRITE_EXTERNAL_STORAGE permission to write to the secondary external storage, except when writing to their package-specific directories or within the URI returned by firing the ACTION_OPEN_DOCUMENT_TREE intent.

如果裝置實現具有支援 USB 週邊模式的 USB 端口,則:

  • [C-3-1] 必須提供一種從主機存取應用程式共用儲存上的資料的機制。
  • SHOULD expose content from both storage paths transparently through Android's media scanner service and android.provider.MediaStore .
  • MAY use USB mass storage, but SHOULD use Media Transfer Protocol to satisfy this requirement.

如果裝置實現具有 USB 週邊模式的 USB 連接埠並支援媒體傳輸協議,則它們:

  • 應與參考 Android MTP 主機、 Android 檔案傳輸相容。
  • 應報告 USB 裝置類別 0x00。
  • 應報告 USB 介面名稱“MTP”。

7.6.3.可採用的存儲

如果設備不像電視那樣本質上是移動的,則設備實現是:

  • [SR] STRONGLY RECOMMENDED to implement the adoptable storage in a long-term stable location, since accidentally disconnecting them can cause data loss/corruption.

如果可移動儲存裝置連接埠處於長期穩定的位置,例如在電池盒或其他保護蓋內,則裝置實現為:

7.7. USB

If device implementations have a USB port, they:

  • 應支援 USB 週邊模式並且應支援 USB 主機模式。

7.7.1. USB週邊模式

If device implementations include a USB port supporting peripheral mode:

  • [C-1-1] 此連接埠必須可連接至具有標準 A 型或 C 型 USB 連接埠的 USB 主機。
  • [C-1-2] MUST report the correct value of iSerialNumber in USB standard device descriptor through android.os.Build.SERIAL .
  • [C-1-3] 必須根據 Type-C 電阻器標準檢測 1.5A 和 3.0A 充電器,如果它們支援 Type-C USB,則必須偵測廣告中的變更。
  • [SR] The port SHOULD use micro-B, micro-AB or Type-C USB form factor.強烈建議現有和新的 Android 裝置滿足這些要求,以便它們能夠升級到未來的平台版本。
  • [SR] The port SHOULD be located on the bottom of the device (according to natural orientation) or enable software screen rotation for all apps (including home screen), so that the display ws correctly when the home screen the so that the display ws correctly wsen the orm. 。強烈建議現有和新的 Android 裝置滿足這些要求,以便它們能夠升級到未來的平台版本。
  • [SR] SHOULD implement support to draw 1.5 A current during HS chirp and traffic as specified in the USB Battery Charging specification, revision 1.2 .強烈建議現有和新的 Android 裝置滿足這些要求,以便它們能夠升級到未來的平台版本。
  • [SR] STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods.雖然這被稱為“強烈建議”,但在未來的 Android 版本中,我們可能會要求所有 C 型設備支援與標準 C 型充電器的完全互通性。
  • [SR] STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping when they support Type-C USB and USB host mode.
  • 應支援高壓充電的電力傳輸並支援交替模式(例如顯示輸出)。
  • 應實作 Android 開放附件 (AOA) API 和規範,如 Android SDK 文件所述。

如果裝置實作包含 USB 連接埠並實作 AOA 規範,則:

  • [C-2-1] MUST declare support for the hardware feature android.hardware.usb.accessory .
  • [C-2-2] The USB mass storage class MUST include the string "android" at the end of the interface description iInterface string of the USB mass storage
  • 不應實作 Android 開放附件協定 2.0 文件中記錄的AOAv2 音訊。 AOAv2 audio is deprecated as of Android version 8.0 (API level 26).

7.7.2. USB主機模式

如果設備實作包括支援主機模式的 USB 端口,則:

  • [C-1-1] MUST implement the Android USB host API as documented in the Android SDK and MUST declare support for the hardware feature android.hardware.usb.host .
  • [C-1-2] 必須實現對連接標準 USB 週邊裝置的支持,換句話說,它們必須:
    • 擁有裝置上的 C 型連接埠或隨附將裝置上的專有連接埠適配為標準 USB C 型連接埠(USB C 型裝置)的連接線。
    • 擁有裝置上的 A 型連接埠或隨附將裝置上的專有連接埠適配為標準 USB A 型連接埠的連接線。
    • 具有設備上的微型 AB 端口,該端口應附帶適用於標準 A 型端口的電纜。
  • [C-1-3] 不得隨附從 USB A 型或 micro-AB 連接埠轉換為 C 型連接埠(插座)的轉接器。
  • [SR] STRONGLY RECOMMENDED to implement the USB audio class as documented in the Android SDK documentation.
  • 應支援在主機模式下為連接的 USB 週邊設備充電;依照USB Type-C 電纜和連接器規範修訂版 1.2的終止參數部分中的規定,針對USB Type-C 連接器宣傳至少1.5A 的源電流,或使用USB Type-C 電纜和連接器規範修訂版1.2中規定的充電下游連接埠 (CDP) 輸出電流範圍Micro-AB 連接器的電池充電規範,修訂版 1.2
  • SHOULD implement and support USB Type-C standards.

If device implementations include a USB port supporting host mode and the USB audio class, they:

  • [C-2-1] 必須支援USB HID 類別
  • [C-2-2] MUST support the detection and mapping of the following HID data fields specified in the USB HID Usage Tables and the Voice Command Usage Request to the KeyEvent constants as below:
    • Usage Page (0xC) Usage ID (0x0CD): KEYCODE_MEDIA_PLAY_PAUSE
    • Usage Page (0xC) Usage ID (0x0E9): KEYCODE_VOLUME_UP
    • Usage Page (0xC) Usage ID (0x0EA): KEYCODE_VOLUME_DOWN
    • Usage Page (0xC) Usage ID (0x0CF): KEYCODE_VOICE_ASSIST

If device implementations include a USB port supporting host mode and the Storage Access Framework (SAF), they:

  • [C-3-1] MUST recognize any remotely connected MTP (Media Transfer Protocol) devices and make their contents accessible through the ACTION_GET_CONTENT , ACTION_OPEN_DOCUMENT , and ACTION_CREATE_DOCUMENT intents. 。

如果裝置實作包括支援主機模式和 USB Type-C 的 USB 端口,則:

  • [C-4-1] 必須實作 USB Type-C 規格(第 4.5.1.3.3 節)定義的雙重角色連接埠功能。
  • [SR] STRONGLY RECOMMENDED to support DisplayPort, SHOULD support USB SuperSpeed Data Rates, and are STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping.
  • [SR] STRONGLY RECOMMENDED to NOT support Audio Adapter Accessory Mode as described in the Appendix A of the USB Type-C Cable and Connector Specification Revision 1.2 .
  • 應實現最適合設備外形尺寸的 Try.* 模型。例如,手持裝置應該實作 Try.SNK 模型。

7.8。聲音的

7.8.1.麥克風

如果裝置實作包含麥克風,則:

  • [C-1-1] MUST report the android.hardware.microphone feature constant.
  • [C-1-2] 必須符合第 5.4 節的錄音要求。
  • [C-1-3] 必須符合第 5.6 節中的音訊延遲要求。
  • [SR] Are STRONGLY RECOMMENDED to support near-ultrasound recording as described in section 7.8.3 .

如果裝置實作省略了麥克風,則:

  • [C-2-1] MUST NOT report the android.hardware.microphone feature constant.
  • [C-2-2] 根據第 7 節,必須至少將音訊錄製 API 實作為無操作。

7.8.2.音訊輸出

如果裝置實現包括揚聲器或用於音訊輸出外設的音訊/多媒體輸出端口,例如 4 導體 3.5mm 音訊插孔或使用USB 音訊類別的 USB主機模式端口,則:

  • [C-1-1] MUST report the android.hardware.audio.output feature constant.
  • [C-1-2] MUST meet the audio playback requirements in section 5.5 .
  • [C-1-3] 必須符合第 5.6 節中的音訊延遲要求。
  • [SR] STRONGLY RECOMMENDED to support near-ultrasound playback as described in section 7.8.3 .

If device implementations do not include a speaker or audio output port, they:

  • [C-2-1] MUST NOT report the android.hardware.audio.output feature.
  • [C-2-2] 必須至少將音訊輸出相關 API 實作為無操作。

就本節而言,「輸出埠」是指實體接口,例如 3.5 公釐音訊插孔、HDMI 或具有 USB 音訊類別的 USB 主機模式連接埠。對透過基於無線電的協定(例如藍牙、WiFi 或蜂窩網路)的音訊輸出的支援不屬於包含「輸出連接埠」的資格。

7.8.2.1.類比音訊連接埠

為了與整個 Android 生態系統中使用 3.5 毫米音訊插頭的耳機和其他音訊配件相容,如果裝置實現包含一個或多個類比音訊端口,則:

  • [C-SR] Are STRONGLY RECOMMENDED to include at least one of the audio port(s) to be a 4 conductor 3.5mm audio jack.

If device implementations have a 4 conductor 3.5mm audio jack, they:

  • [C-1-1] 必須支援透過立體聲耳機和帶麥克風的立體聲耳機播放音訊。
  • [C-1-2] 必須支援具有 CTIA 引腳排列順序的 TRRS 音訊插頭。
  • [C-1-3] 必須支援針對音訊插頭上的麥克風和接地導體之間的以下 3 個等效阻抗範圍進行偵測並對應到鍵碼:
    • 70歐姆或以下KEYCODE_HEADSETHOOK
    • 210-290 ohm : KEYCODE_VOLUME_UP
    • 360-680 ohm : KEYCODE_VOLUME_DOWN
  • [C-1-4] MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after all contacts on plug are touching their relevant segments on the jack.
  • [C-1-5] 必須能夠在 32 歐姆揚聲器阻抗上驅動至少 150mV ± 10% 的輸出電壓。
  • [C-1-6] 麥克風偏壓必須在 1.8V ~ 2.9V 之間。
  • [C-1-7] 必須偵測並對應到鍵碼,以獲得音訊插頭上的麥克風和接地導體之間的以下等效阻抗範圍:
    • 110-180 ohm: KEYCODE_VOICE_ASSIST
  • [C-SR] Are STRONGLY RECOMMENDED to support audio plugs with the OMTP pin-out order.
  • [C-SR] Are STRONGLY RECOMMEND to support audio recording from stereo headsets with a microphone.

If device implementations have a 4 conductor 3.5mm audio jack and support a microphone, and broadcast the android.intent.action.HEADSET_PLUG with the extra value microphone set as 1, they:

  • [C-2-1] 必須支援偵測插入的音訊配件上的麥克風。

7.8.3。近超音波

近超音波音訊的頻段為 18.5 kHz 至 20 kHz。

設備實現:

If PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND is "true", the following requirements MUST be met by the VOICE_RECOGNITION and UNPROCESSED audio sources:

  • [C-1-1] 麥克風在 18.5 kHz 至 20 kHz 頻段的平均功率響應不得比 2 kHz 頻段的響應低 15 dB 以上。
  • [C-1-2] 對於 -26 dBFS 的 19 kHz 音調,麥克風在 18.5 kHz 至 20 kHz 範圍內的未加權信噪比必須不低於 50 dB。

If PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND is "true":

  • [C-2-1] 揚聲器在 18.5 kHz - 20 kHz 範圍內的平均響應必須比 2 kHz 範圍內的響應低不少於 40 dB。

7.9。虛擬實境

Android 包含用於建立「虛擬實境」(VR) 應用程式(包括高品質行動 VR 體驗)的 API 和工具。設備實作必須正確實作這些 API 和行為,如本節所述。

7.9.1.虛擬實境模式

Android includes support for VR Mode , a feature which handles stereoscopic rendering of notifications and disables monocular system UI components while a VR application has user focus.

7.9.2. Virtual Reality Mode - High Performance

如果裝置實作支援 VR 模式,則:

  • [C-1-1] 必須至少有 2 個物理核心。
  • [C-1-2] MUST declare the android.hardware.vr.high_performance feature.
  • [C-1-3] 必須支援持續性能模式。
  • [C-1-4] 必須支援 OpenGL ES 3.2。
  • [C-1-5] MUST support android.hardware.vulkan.level 0.
  • SHOULD support android.hardware.vulkan.level 1 or higher.
  • [C-1-6] MUST implement EGL_KHR_mutable_render_buffer , EGL_ANDROID_front_buffer_auto_refresh , EGL_ANDROID_get_native_client_buffer , EGL_KHR_fence_sync , EGL_KHR_wait_sync , EGL_IMG_context_priority , EGL_EXT_protected_content , EGL_EXT_image_gl_colorspace , and expose the extensions in the list of available EGL extensions.
  • [C-1-8] MUST implement GL_EXT_multisampled_render_to_texture2 , GL_OVR_multiview , GL_OVR_multiview2 , GL_OVR_multiview_multisampled_render_to_texture , GL_EXT_protected_textures , and expose the extensions in the list of available GL extensions.
  • [C-SR] Are STRONGLY RECOMMENDED to implement GL_EXT_external_buffer , GL_EXT_EGL_image_array , and expose the extensions in the list of available GL extensions.
  • [C-SR] Are STRONGLY RECOMMENDED to support Vulkan 1.1.
  • [C-SR] Are STRONGLY RECOMMENDED to implement VK_ANDROID_external_memory_android_hardware_buffer , VK_GOOGLE_display_timing , VK_KHR_shared_presentable_image , and expose it in the list of available Vulkan extensions.
  • [C-SR] Are STRONGLY RECOMMENDED to expose at least one Vulkan queue family where flags contain both VK_QUEUE_GRAPHICS_BIT and VK_QUEUE_COMPUTE_BIT , and queueCount is at least 2.
  • [C-1-7] GPU 和顯示器必須能夠同步對共享前端緩衝區的訪問,以便在兩個渲染上下文中以60fps 的速度進行VR 內容的交替眼渲染,並且不會出現明顯的撕裂偽像。
  • [C-1-9] MUST implement support for AHardwareBuffer flags AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER , AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA and AHARDWAREBUFFER_USAGE_PROTECTED_CONTENT as described in the NDK.
  • [C-1-10] MUST implement support for AHardwareBuffer s with any combination of the usage flags AHARDWAREBUFFER_USAGE_GPU_COLOR_OUTPUT , AHARDWAREBUFFER_USAGE_GPU_SAMPLED_IMAGE , AHARDWAREBUFFER_USAGE_PROTECTED_CONTENT for at least the following formats: AHARDWAREBUFFER_FORMAT_R5G6B5_UNORM , AHARDWAREBUFFER_FORMAT_R8G8B8A8_UNORM , AHARDWAREBUFFER_FORMAT_R10G10B10A2_UNORM , AHARDWAREBUFFER_FORMAT_R16G16B16A16_FLOAT .
  • [C-SR] Are STRONGLY RECOMMENDED to support the allocation of AHardwareBuffer s with more than one layer and flags and formats specified in C-1-10.
  • [C-1-11] 必須支援至少3840 x 2160 (30fps) 的H.264 解碼,壓縮至平均40Mbps(相當於4 個1920 x1080(30 fps-10 Mbps)實例或2 個1920 x 1080(60 fps )實例fps-20 Mbps)。
  • [C-1-12] 必須支援HEVC 和VP9,必須能夠以30 fps 的速度至少解碼1920 x 1080(壓縮至平均10 Mbps),並且應該能夠以30 fps-20 Mbps 的速度解碼3840 x 2160(相當於至 4 個 1920 x 1080(30 fps-5 Mbps)實例)。
  • [C-1-13] MUST support HardwarePropertiesManager.getDeviceTemperatures API and return accurate values for skin temperature.
  • [C-1-14] 必須具有嵌入式螢幕,且其解析度必須至少為 1920 x 1080。
  • [C-SR] Are STRONGLY RECOMMENDED to have a display resolution of at least 2560 x 1440.
  • [C-1-15] 在 VR 模式下,顯示器的更新頻率必須至少為 60 Hz。
  • [C-1-17] 顯示器必須支援餘輝時間≤ 5 毫秒的低餘輝模式,餘輝定義為像素發光的時間量。
  • [C-1-18] 必須支援藍牙 4.2 和藍牙 LE 資料長度擴展第 7.4.3 節
  • [C-1-19] MUST support and properly report Direct Channel Type for all of the following default sensor types:
    • TYPE_ACCELEROMETER
    • TYPE_ACCELEROMETER_UNCALIBRATED
    • TYPE_GYROSCOPE
    • TYPE_GYROSCOPE_UNCALIBRATED
    • TYPE_MAGNETIC_FIELD
    • TYPE_MAGNETIC_FIELD_UNCALIBRATED
  • [C-SR] Are STRONGLY RECOMMENDED to support the TYPE_HARDWARE_BUFFER direct channel type for all Direct Channel Types listed above.
  • [C-1-21] MUST meet the gyroscope, accelerometer, and magnetometer related requirements for android.hardware.hifi_sensors , as specified in section 7.3.9 .
  • [C-SR] Are STRONGLY RECOMMENDED to support the android.hardware.sensor.hifi_sensors feature.
  • [C-1-22] 端對端運動到光子的延遲必須不超過 28 毫秒。
  • [C-SR] Are STRONGLY RECOMMENDED to have end-to-end motion to photon latency not higher than 20 milliseconds.
  • [C-1-23] 第一幀比率(從黑色過渡到白色後第一幀的像素亮度與穩定狀態下的白色像素的亮度之間的比率)必須至少為 85%。
  • [C-SR] Are STRONGLY RECOMMENDED to have first-frame ratio of at least 90%.
  • MAY provide an exclusive core to the foreground application and MAY support the Process.getExclusiveCores API to return the numbers of the cpu cores that are exclusive to the top foreground application.

If exclusive core is supported, then the core:

  • [C-2-1] 不得允許任何其他用戶空間進程在其上運行(應用程式使用的裝置驅動程式除外),但可以允許某些核心進程在必要時運行。

8. 性能和功率

Some minimum performance and power criteria are critical to the user experience and impact the baseline assumptions developers would have when developing an app.

8.1.使用者體驗一致性

如果存在某些最低要求以確保應用程式和遊戲的幀速率和回應時間一致,則可以向最終用戶提供流暢的使用者介面。 Device implementations, depending on the device type, MAY have measurable requirements for the user interface latency and task switching as described in section 2 .

8.2.文件 I/O 存取效能

Providing a common baseline for a consistent file access performance on the application private data storage ( /data partition) allows app developers to set a proper expectation that would help their software design.根據設備類型,設備實作可能對以下讀寫作業有第 2 節中所述的某些要求:

  • 順序寫入效能。透過使用 10MB 寫入緩衝區寫入 256MB 檔案來測量。
  • Random write performance . Measured by writing a 256MB file using 4KB write buffer.
  • Sequential read performance . Measured by reading a 256MB file using 10MB write buffer.
  • 隨機讀取效能。透過使用 4KB 寫入緩衝區讀取 256MB 檔案來測量。

8.3.省電模式

If device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

  • [C-1-1] MUST NOT deviate from the AOSP implementation for the triggering, maintenance, wakeup algorithms and the use of global system settings of App Standby and Doze power-saving modes.
  • [C-1-2] MUST NOT deviate from the AOSP implementation for the use of global settings to manage the throttling of jobs, alarm and network for apps in each bucket for App standby.
  • [C-1-3] MUST NOT deviate from the AOSP implementation for the number of the App Standby Buckets used for App Standby.
  • [C-1-4] 必須實現應用待機儲存桶和打瞌睡,如電源管理所述。
  • [C-1-5] MUST return true for PowerManager.isPowerSaveMode() when the device is on power save mode.
  • [C-SR] Are STRONGLY RECOMMENDED to provide user affordance to enable and disable the battery saver feature.
  • [C-SR] Are STRONGLY RECOMMENDED to provide user affordance to display all Apps that are exempted from App Standby and Doze power-saving modes.

除了省電模式之外,Android 裝置實作還可以實現進階配置和電源介面 (ACPI) 定義的任意或全部 4 種睡眠電源狀態。

如果設備實現實現 ACPI 定義的 S4 電源狀態,則:

  • [C-1-1] MUST enter this state only after the user has taken an explicit action to put the device in an inactive state (eg by closing a lid that is physically part of the device or turning closing a lid that is physically part of the device or turning closing a lid that is physically part of the device or turning r.在使用者重新啟動裝置之前(例如,透過打開蓋子或重新打開車輛或電視)。

如果設備實現實現 ACPI 定義的 S3 電源狀態,則:

  • [C-2-1] 必須滿足上述 C-1-1,或者,僅當第三方應用程式不需要係統資源(例如螢幕、CPU)時才必須進入 S3 狀態。

    相反,當第三方應用程式需要係統資源時,必須退出 S3 狀態,如本 SDK 中所述。

    For example, while the third party applications request to keep the screen on through FLAG_KEEP_SCREEN_ON or keep CPU running through PARTIAL_WAKE_LOCK , the device MUST NOT enter S3 state unless, as described in C-1-1, the user has taken explicit action to put the device in an inactive state. Conversely, at a time when a task that third party apps implement through JobScheduler is triggered or Firebase Cloud Messaging is delivered to third party apps, the device MUST exit the S3 state unless the user has put the device in an inactive state. These are not comprehensive examples and AOSP implements extensive wake-up signals that trigger a wakeup from this state.

8.4.用電核算

更準確的功耗統計和報告為應用程式開發人員提供了優化應用程式功耗模式的激勵和工具。

設備實現:

  • [SR] STRONGLY RECOMMENDED to provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
  • [SR] STRONGLY RECOMMENDED to report all power consumption values in milliampere hours (mAh).
  • [SR] STRONGLY RECOMMENDED to report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
  • [SR] STRONGLY RECOMMENDED to make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
  • SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

8.5。一致的性能

Performance can fluctuate dramatically for high-performance long-running apps, either because of the other apps running in the background or the CPU throttling due to temperature limits. Android includes programmatic interfaces so that when the device is capable, the top foreground application can request that the system optimize the allocation of the resources to address such fluctuations.

設備實現:

If device implementations report support of Sustained Performance Mode, they:

  • [C-1-1] MUST provide the top foreground application a consistent level of performance for at least 30 minutes, when the app requests it.
  • [C-1-2] MUST honor the Window.setSustainedPerformanceMode() API and other related APIs.

If device implementations include two or more CPU cores, they:

  • SHOULD provide at least one exclusive core that can be reserved by the top foreground application.

If device implementations support reserving one exclusive core for the top foreground application, they:

  • [C-2-1] MUST report through the Process.getExclusiveCores() API method the ID numbers of the exclusive cores that can be reserved by the top foreground application.
  • [C-2-2] MUST not allow any user space processes except the device drivers used by the application to run on the exclusive cores, but MAY allow some kernel processes to run as necessary.

If device implementations do not support an exclusive core, they:

9. 安全模型相容性

設備實現:

  • [C-0-1] MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs in the Android developer documentation.

  • [C-0-2] MUST support installation of self-signed applications without requiring any additional permissions/certificates from any third parties/authorities.具體而言,相容設備必須支援以下小節中所述的安全機制。

9.1.權限

設備實現:

  • [C-0-1] MUST support the Android permissions model as defined in the Android developer documentation. Specifically, they MUST enforce each permission defined as described in the SDK documentation;無法省略,更改或忽略權限。

  • MAY add additional permissions, provided the new permission ID strings are not in the android.\* namespace.

  • [C-0-2] Permissions with a protectionLevel of PROTECTION_FLAG_PRIVILEGED MUST only be granted to apps preinstalled in the privileged path(s) of the system image and within the subset of the explicitly allowlisted permissions for each app. The AOSP implementation meets this requirement by reading and honoring the allowlisted permissions for each app from the files in the etc/permissions/ path and using the system/priv-app path as the privileged path.

Permissions with a protection level of dangerous are runtime permissions. Applications with targetSdkVersion > 22 request them at runtime.

設備實現:

  • [C-0-3] MUST show a dedicated interface for the user to decide whether to grant the requested runtime permissions and also provide an interface for the user to manage runtime permissions.
  • [C-0-4] MUST have one and only one implementation of both user interfaces.
  • [C-0-5] MUST NOT grant any runtime permissions to preinstalled apps unless:
    • The user's consent can be obtained before the application uses it.
    • The runtime permissions are associated with an intent pattern for which the preinstalled application is set as the default handler.
  • [C-0-6] MUST grant the android.permission.RECOVER_KEYSTORE permission only to system apps that register a properly secured Recovery Agent. A properly secured Recovery Agent is defined as an on-device software agent that synchronizes with an off-device remote storage, that is equipped with secure hardware with protection equivalent or stronger than what is described in Google Cloud Key Vault Service to prevent brute-force attacks on the lockscreen knowledge factor.

If device implementations include a preinstalled app or wish to allow third-party apps to access the usage statistics, they:

  • [SR] are STRONGLY RECOMMENDED provide user-accessible mechanism to grant or revoke access to the usage stats in response to the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent for apps that declare the android.permission.PACKAGE_USAGE_STATS permission.

If device implementations intend to disallow any apps, including preinstalled apps, from accessing the usage statistics, they:

  • [C-1-1] MUST still have an activity that handles the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent pattern but MUST implement it as a no-op, that is to have an equivalent behavior as when the user is declined for access.

9.2. UID 和進程隔離

設備實現:

  • [C-0-1] MUST support the Android application sandbox model, in which each application runs as a unique Unixstyle UID and in a separate process.
  • [C-0-2] MUST support running multiple applications as the same Linux user ID, provided that the applications are properly signed and constructed, as defined in the Security and Permissions reference .

9.3.檔案系統權限

設備實現:

9.4.備用執行環境

Device implementations MUST keep consistency of the Android security and permission model, even if they include runtime environments that execute applications using some other software or technology than the Dalvik Executable Format or native code.換句話說:

  • [C-0-1] Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in section 9 .

  • [C-0-2] Alternate runtimes MUST NOT be granted access to resources protected by permissions not requested in the runtime's AndroidManifest.xml file via the < uses-permission > mechanism.

  • [C-0-3] Alternate runtimes MUST NOT permit applications to make use of features protected by Android permissions restricted to system applications.

  • [C-0-4] Alternate runtimes MUST abide by the Android sandbox model and installed applications using an alternate runtime MUST NOT reuse the sandbox of any other app installed on the device, exception the sandbox of any other app installed on the device, exceptity 。

  • [C-0-5] Alternate runtimes MUST NOT launch with, grant, or be granted access to the sandboxes corresponding to other Android applications.

  • [C-0-6] Alternate runtimes MUST NOT be launched with, be granted, or grant to other applications any privileges of the superuser (root), or of any other user ID.

  • [C-0-7] When the .apk files of alternate runtimes are included in the system image of device implementations, it MUST be signed with a key distinct from the key used to sign other applications included with the device implementations.

  • [C-0-8] When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application.

  • [C-0-9] When an application needs to make use of a device resource for which there is a corresponding Android permission (such as Camera, GPS, etc.), the alternate runtime MUST inform the user that the application will be able to access that resource.

  • [C-0-10] When the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime.

  • Alternate runtimes SHOULD install apps via the PackageManager into separate Android sandboxes (Linux user IDs, etc.).

  • 替代運行時可能會使用替代運行時提供所有應用程式共享的單一Android沙箱。

9.5。多用戶支援

Android includes support for multiple users and provides support for full user isolation.

  • Device implementations MAY but SHOULD NOT enable multi-user if they use removable media for primary external storage.

If device implementations include multiple users, they:

  • [C-1-1] MUST meet the following requirements related to multi-user support .
  • [C-1-2] MUST, for each user, implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs.
  • [C-1-3] MUST have separate and isolated shared application storage (aka /sdcard ) directories for each user instance.
  • [C-1-4] MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to the files owned by any other user, even if the data of both users are stored on the or文件系統。
  • [C-1-5] MUST encrypt the contents of the SD card when multiuser is enabled using a key stored only on non-removable media accessible only to the system if device implementations use removable media for the external storage APIs.由於這將使主機PC無法閱讀媒體,因此將需要裝置實作來切換到MTP或類似系統,以便為主機PC提供存取目前使用者資料的存取。

If device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

  • [C-2-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device.借助限制的配置文件,設備所有者可以快速設置單獨的環境供其他用戶工作,並且能夠管理在這些環境中可用的應用程式中進行細粒度限制的能力。

If device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

  • [C-3-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

9.6.高級簡訊警告

Android includes support for warning users of any outgoing premium SMS message .高級SMS訊息是發送到使用運營商註冊的服務的短信,該服務可能會向用戶收取費用。

If device implementations declare support for android.hardware.telephony , they:

  • [C-1-1] MUST warn users before sending a SMS message to numbers identified by regular expressions defined in /data/misc/sms/codes.xml file in the device.上游Android開源專案提供了滿足此要求的實作。

9.7.安全特性

Device implementations MUST ensure compliance with security features in both the kernel and platform as described below.

The Android Sandbox includes features that use the Security-Enhanced Linux (SELinux) mandatory access control (MAC) system, seccomp sandboxing, and other security features in the Linux kernel.設備實現:

  • [C-0-1] MUST maintain compatibility with existing applications, even when SELinux or any other security features are implemented below the Android framework.
  • [C-0-2] MUST NOT have a visible user interface when a security violation is detected and successfully blocked by the security feature implemented below the Android fr時開發。
  • [C-0-3] MUST NOT make SELinux or any other security features implemented below the Android framework configurable to the user or app developer.
  • [C-0-4] MUST NOT allow an application that can affect another application through an API (such as a Device Administration API) to configure a policy that breaks compatibility.
  • [C-0-5] MUST split the media framework into multiple processes so that it is possible to more narrowly grant access for each process as described in the Android Open Source Project site.
  • [C-0-6] MUST implement a kernel application sandboxing mechanism which allows filtering of system calls using a configurable policy from multithreaded programs. The upstream Android Open Source Project meets this requirement through enabling the seccomp-BPF with threadgroup synchronization (TSYNC) as described in the Kernel Configuration section of source.android.com .

Kernel integrity and self-protection features are integral to Android security.設備實現:

  • [C-0-7] MUST implement kernel stack buffer overflow protections (eg CONFIG_CC_STACKPROTECTOR_STRONG ).
  • [C-0-8] MUST implement strict kernel memory protections where executable code is read-only, read-only data is non-executable and non-writable, and writable data is non-executable (eg CONFIG_DEBUG_RODATA or CONFIG_STRICT_KERNEL_RWX ).
  • [C-0-9] MUST implement static and dynamic object size bounds checking of copies between user-space and kernel-space (eg CONFIG_HARDENED_USERCOPY ) on devices originally shipping with API level 28 or higher.
  • [C-0-10] MUST NOT execute user-space memory when executing in the kernel mode (eg hardware PXN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ) on devices originally shipping with API level 28 or higher.
  • [C-0-11] MUST NOT read or write user-space memory in the kernel outside of normal usercopy access APIs (eg hardware PAN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ) on devices originally shipping with API level 28 or higher.
  • [C-0-12] MUST implement kernel page table isolation on all devices originally shipping with API level 28 or higher (eg CONFIG_PAGE_TABLE_ISOLATION or `CONFIG_UNMAP_KERNEL_AT_EL0).
  • [SR] STRONGLY RECOMMENDED to keep kernel data which is written only during initialization marked read-only after initialization (eg __ro_after_init ).
  • [SR] STRONGLY RECOMMENDED to randomize the layout of the kernel code and memory, and to avoid exposures that would compromise the randomization (eg CONFIG_RANDOMIZE_BASE with bootloader entropy via the /chosen/kaslr-seed Device Tree node or EFI_RNG_PROTOCOL ).

If device implementations use a Linux kernel, they:

  • [C-1-1] MUST implement SELinux.
  • [C-1-2] MUST set SELinux to global enforcing mode.
  • [C-1-3] MUST configure all domains in enforcing mode.不允許允許模式域,包括特定於設備/供應商的域。
  • [C-1-4] MUST NOT modify, omit, or replace the neverallow rules present within the system/sepolicy folder provided in the upstream Android Open Source Project (AOSP) and the policy MUST compile with all neverallow rules present, for both AOSP SELinux domains as well as device/vendor specific domains.
  • [C-1-5] MUST run third-party applications targeting API level 28 or higher in per-application SELinux sandboxes with per-app SELinux restrictions on each application's private data directory.
  • SHOULD retain the default SELinux policy provided in the system/sepolicy folder of the upstream Android Open Source Project and only further add to this policy for their own device-specific configuration.

If device implementations use kernel other than Linux, they:

  • [C-2-1] MUST use a mandatory access control system that is equivalent to SELinux.

Android contains multiple defense-in-depth features that are integral to device security.

設備實現:

  • [C-SR] Are STRONGLY RECOMMENDED not to disable Control-Flow Integrity (CFI) or Integer Overflow Sanitization (IntSan) on components that have it enabled.
  • [C-SR] Are STRONGLY RECOMMENDED to enable both CFI and IntSan for any additional security-sensitive userspace components as explained in CFI and IntSan .

9.8.隱私

9.8.1.使用歷史

Android stores the history of the user's choices and manages such history by UsageStatsManager .

設備實現:

  • [C-0-1] MUST keep a reasonable retention period of such user history.
  • [SR] Are STRONGLY RECOMMENDED to keep the 14 days retention period as configured by default in the AOSP implementation.

Android stores the system events using the StatsLog identifiers, and manages such history via the StatsManager and the IncidentManager System API.

設備實現:

  • [C-0-2] MUST only include the fields marked with DEST_AUTOMATIC in the incident report created by the System API class IncidentManager .
  • [C-0-3] MUST not use the system event identifiers to log any other event than what is described in the StatsLog SDK documents. If additional system events are logged, they MAY use a different atom identifier in the range between 100,000 and 200,000.

9.8.2.記錄

設備實現:

  • [C-0-1] MUST NOT preload or distribute software components out-of-box that send the user's private information (eg keystrokes, text displayed on the screen) off the device without the user's consent or clear ongoing notifications.

If device implementations include functionality in the system that captures the contents displayed on the screen and/or records the audio stream played on the device, they:

  • [C-1-1] MUST have an ongoing notification to the user whenever this functionality is enabled and actively capturing/recording.

If device implementations include a component enabled out-of-box, capable of recording ambient audio to infer useful information about user's context, they:

  • [C-2-1] MUST NOT store in persistent on-device storage or transmit off the device the recorded raw audio or any format that can be converted back into the original audio or a near facsimile, except with explicit user consent.

9.8.3。連接性

如果裝置實現具有支援 USB 週邊模式的 USB 端口,則:

  • [C-1-1] MUST present a user interface asking for the user's consent before allowing access to the contents of the shared storage over the USB port.

9.8.4。網路流量

設備實現:

  • [C-0-1] MUST preinstall the same root certificates for the system-trusted Certificate Authority (CA) store as provided in the upstream Android Open Source Project.
  • [C-0-2] MUST ship with an empty user root CA store.
  • [C-0-3] MUST display a warning to the user indicating the network traffic may be monitored, when a user root CA is added.

If device traffic is routed through a VPN, device implementations:

  • [C-1-1] MUST display a warning to the user indicating either:
    • That network traffic may be monitored.
    • That network traffic is being routed through the specific VPN application providing the VPN.

If device implementations have a mechanism, enabled out-of-box by default, that routes network data traffic through a proxy server or VPN gateway (for example, preloading a VPN service with android.permission.CONTROL_VPN granted), they:

  • [C-2-1] MUST ask for the user's consent before enabling that mechanism, unless that VPN is enabled by the Device Policy Controller via the DevicePolicyManager.setAlwaysOnVpnPackage() , in which case the user does not need to provide a separate consent, but MUST only be notified.

If device implementations implement a user affordance to toggle on the "always-on VPN" function of a 3rd-party VPN app, they:

  • [C-3-1] MUST disable this user affordance for apps that do not support always-on VPN service in the AndroidManifest.xml file via setting the SERVICE_META_DATA_SUPPORTS_ALWAYS_ON attribute to false .

9.9.資料儲存加密

If Advanced Encryption Standard (AES) crypto performance, measured with the most performant AES technology available on the device (eg the ARM Cryptography Extensions), is above 50 MiB/sec, device implementations:

  • [C-1-1] MUST support data storage encryption of the application private data ( /data partition), as well as the application shared storage partition ( /sdcard partition) if it is a permanent, non-removable part of the device, except for device implementations that are typically shared (eg Television).
  • [C-1-2] MUST enable the data storage encryption by default at the time the user has completed the out-of-box setup experience, except for device implementations that are typically shared (eg Television).

If the AES crypto performance is at or below 50 MiB/sec, device implementations MAY use Adiantum-XChaCha12-AES instead of the form of AES listed in any of the following: AES-256-XTS in Section 9.9.2 [C-1-5]; AES-256 in CBS-CTS mode in Section 9.9.2 [C-1-6]; AES in Section 9.9.3 [C-1-1]; AES in Section 9.9.3 [C-1-3].

If device implementations are already launched on an earlier Android version and cannot meet the requirement through a system software update, they MAY be exempted from the above requirements.

設備實現:

9.9.1.直接啟動

設備實現:

  • [C-0-1] MUST implement the Direct Boot mode APIs even if they do not support Storage Encryption.

  • [C-0-2] The ACTION_LOCKED_BOOT_COMPLETED and ACTION_USER_UNLOCKED Intents MUST still be broadcast to signal Direct Boot aware applications that Device Encrypted (DE) and Credential Encrypted (CE) storage locations are available for user.

9.9.2.基於文件的加密

If device implementations support FBE, they:

  • [C-1-1] MUST boot up without challenging the user for credentials and allow Direct Boot aware apps to access to the Device Encrypted (DE) storage after the ACTION_LOCKED_BOOT_COMPLETED message is broadcasted.
  • [C-1-2] MUST only allow access to Credential Encrypted (CE) storage after the user has unlocked the device by supplying their credentials (eg. passcode, pin, pattern or fingerprint) and the ACTION_USER_UNLOCKED message is broadcasted.
  • [C-1-3] MUST NOT offer any method to unlock the CE protected storage without either the user-supplied credentials or a registered escrow key.
  • [C-1-4] MUST support Verified Boot and ensure that DE keys are cryptographically bound to the device's hardware root of trust.
  • [C-1-5] MUST support encrypting file contents using AES-256-XTS. AES-256-XTS refers to the Advanced Encryption Standard with a 256-bit key length, operated in XTS mode. The full length of the XTS key is 512 bits.
  • [C-1-6] MUST support encrypting file names using AES-256 in CBC-CTS mode.

  • The keys protecting CE and DE storage areas:

  • [C-1-7] MUST be cryptographically bound to a hardware-backed Keystore.

  • [C-1-8] CE keys MUST be bound to a user's lock screen credentials.
  • [C-1-9] CE keys MUST be bound to a default passcode when the user has not specified lock screen credentials.
  • [C-1-10] MUST be unique and distinct, in other words no user's CE or DE key matches any other user's CE or DE keys.

  • [C-1-11] MUST use the mandatorily supported ciphers, key lengths and modes by default.

  • [C-SR] Are STRONGLY RECOMMENDED to encrypt file system metadata, such as file sizes, ownership, modes, and Extended attributes (xattrs), with a key cryptographically bound to the device's hardware root of trust.

  • SHOULD make preinstalled essential apps (eg Alarm, Phone, Messenger) Direct Boot aware.

  • MAY support alternative ciphers, key lengths and modes for file content and file name encryption.

The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel ext4 encryption feature.

9.9.3。全碟加密

If device implementations support full disk encryption (FDE), they:

  • [C-1-1] MUST use AES in a mode designed for storage (for example, XTS or CBC-ESSIV), and with a cipher key length of 128 bits or greater.
  • [C-1-2] MUST use a default passcode to wrap the encryption key and MUST NOT write the encryption key to storage at any time without being encrypted.
  • [C-1-3] MUST AES encrypt the encryption key by default unless the user explicitly opts out, except when it is in active use, with the lock screen credentials stretched using a slow stretching algorithm (eg PBKDF2 or scrypt).
  • [C-1-4] The above default password stretching algorithm MUST be cryptographically bound to that keystore when the user has not specified a lock screen credentials or has disabled use of the passcode for encryption and the device provides a hardware-backed keystore.
  • [C-1-5] MUST NOT send encryption key off the device (even when wrapped with the user passcode and/or hardware bound key).

The upstream Android Open Source project provides a preferred implementation of this feature, based on the Linux kernel feature dm-crypt.

9.10。設備完整性

The following requirements ensures there is transparency to the status of the device integrity.設備實現:

  • [C-0-1] MUST correctly report through the System API method PersistentDataBlockManager.getFlashLockState() whether their bootloader state permits flashing of the system image. The FLASH_LOCK_UNKNOWN state is reserved for device implementations upgrading from an earlier version of Android where this new system API method did not exist.

  • [C-0-2] MUST support Verified Boot for device integrity.

If device implementations are already launched without supporting Verified Boot on an earlier version of Android and can not add support for this feature with a system software update, they MAY be exempted from the requirement.

Verified Boot is a feature that guarantees the integrity of the device software. If device implementations support the feature, they:

  • [C-1-1] MUST declare the platform feature flag android.software.verified_boot .
  • [C-1-2] MUST perform verification on every boot sequence.
  • [C-1-3] MUST start verification from an immutable hardware key that is the root of trust and go all the way up to the system partition.
  • [C-1-4] MUST implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage.
  • [C-1-5] MUST use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048).
  • [C-1-6] MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used.
  • [C-1-7] MUST NOT allow verified partitions on the device to be modified unless the user has explicitly unlocked the bootloader.
  • [C-SR] If there are multiple discrete chips in the device (eg radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting.
  • [C-1-8] MUST use tamper-evident storage: for storing whether the bootloader is unlocked. Tamper-evident storage means that the boot loader can detect if the storage has been tampered with from inside Android.
  • [C-1-9] MUST prompt the user, while using the device, and require physical confirmation before allowing a transition from boot loader locked mode to boot loader unlocked mode.
  • [C-1-10] MUST implement rollback protection for partitions used by Android (eg boot, system partitions) and use tamper-evident storage for storing the metadata used for determining the minimum allowable OS version.
  • [C-SR] Are STRONGLY RECOMMENDED to verify all privileged app APK files with a chain of trust rooted in /system , which is protected by Verified Boot.
  • [C-SR] Are STRONGLY RECOMMENDED to verify any executable artifacts loaded by a privileged app from outside its APK file (such as dynamically loaded code or compiled code) before executing them or STRONGLY RECOMMENDED not to execute them at all.
  • SHOULD implement rollback protection for any component with persistent firmware (eg modem, camera) and SHOULD use tamper-evident storage for storing the metadata used for determining the minimum allowable version.

If device implementations are already launched without supporting C-1-8 through C-1-10 on an earlier version of Android and can not add support for these requirements with a system software update, they MAY be exempted from the requirements.

The upstream Android Open Source Project provides a preferred implementation of this feature in the external/avb/ repository, which can be integrated into the boot loader used for loading Android.

設備實現:

If device implementations support the Android Protected Confirmation API they:

  • [C-3-1] MUST report true for the ConfirmationPrompt.isSupported() API.
  • [C-3-2] MUST ensure that secure hardware takes full control of display in such a way that Android OS cannot block it without detection by the secure hardware.
  • [C-3-3] MUST ensure that secure hardware takes full control of the touch screen.

9.11。金鑰和憑證

The Android Keystore System allows app developers to store cryptographic keys in a container and use them in cryptographic operations through the KeyChain API or the Keystore API .設備實現:

  • [C-0-1] MUST allow at least 8,192 keys to be imported or generated.
  • [C-0-2] The lock screen authentication MUST rate-limit attempts and MUST have an exponential backoff algorithm. Beyond 150 failed attempts, the delay MUST be at least 24 hours per attempt.
  • SHOULD not limit the number of keys that can be generated

When the device implementation supports a secure lock screen, it:

  • [C-1-1] MUST back up the keystore implementation with an isolated execution environment.
  • [C-1-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
  • [C-1-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
  • [C-1-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.
  • [C-1-5] MUST allow the user to choose the Sleep timeout for transition from the unlocked to the locked state, with a minimum allowable timeout up to 15 seconds.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the android.hardware.fingerprint feature which requires a keystore backed by an isolated execution environment.

9.11.1。安全鎖定螢幕

The AOSP implementation follows a tiered authentication model where a knowledge-factory based primary authentication can be backed by either a secondary strong biometric, or by weaker tertiary modalities.

設備實現:

  • [C-SR] Are STRONGLY RECOMMENDED to set only one of the following as the primary authentication method:
    • A numerical PIN
    • An alphanumerical password
    • A swipe pattern on a grid of exactly 3x3 dots

Note that the above authentication methods are referred as the recommended primary authentication methods in this document.

If device implementations add or modify the recommended primary authentication methods and use a new authentication method as a secure way to lock the screen, the new authentication method:

If device implementations add or modify the authentication methods to unlock the lock screen if based on a known secret and use a new authentication method to be treated as a secure way to lock the screen:

  • [C-3-1] The entropy of the shortest allowed length of inputs MUST be greater than 10 bits.
  • [C-3-2] The maximum entropy of all possible inputs MUST be greater than 18 bits.
  • [C-3-3] The new authentication method MUST NOT replace any of the recommended primary authentication methods (ie PIN, pattern, password) implemented and provided in AOSP.
  • [C-3-4] The new authentication method MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_SOMETHING .

If device implementations add or modify the recommended primary authentication methods to unlock the lock screen and use a new authentication method that is based on biometrics to be treated as a secure way to lock the screen, the new method:

  • [C-4-1] MUST meet all requirements described in section 7.3.10.2 .
  • [C-4-2] MUST have a fall-back mechanism to use one of the recommended primary authentication methods which is based on a known secret.
  • [C-4-3] MUST be disabled and only allow the recommended primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the keguard feature policy by calling the method DevicePolicyManager.setKeyguardDisabledFeatures() , with any of the associated biometric flags (ie KEYGUARD_DISABLE_BIOMETRICS , KEYGUARD_DISABLE_FINGERPRINT , KEYGUARD_DISABLE_FACE , or KEYGUARD_DISABLE_IRIS ).
  • [C-4-4] MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) at least once every 72 hours or less.
  • [C-4-5] MUST have a false acceptance rate that is equal or stronger than what is required for a fingerprint sensor as described in section section 7.3.10 , or otherwise MUST be disabled and only allow the recommended primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_BIOMETRIC_WEAK .
  • [C-SR] Are STRONGLY RECOMMENDED to have spoof and imposter acceptance rates that are equal to or stronger than what is required for a fingerprint sensor as described in section 7.3.10 .
  • [C-4-6] MUST have a secure processing pipeline such that an operating system or kernel compromise cannot allow data to be directly injected to falsely authenticate as the user.
  • [C-4-7] MUST be paired with an explicit confirm action (eg: a button press) to allow access to keystore keys if the application sets true for KeyGenParameterSpec.Built.setUserAuthenticationRequired() and the biometric is passive (eg face or iris where no explicit signal of intent exists).
  • [C-SR] The confirm action for passive biometrics is STRONGLY RECOMMENDED to be secured such that an operating system or kernel compromise cannot spoof it.為 example, this means that the confirm action based on a physical button is routed through an input-only general-purpose input/output (GPIO) pin of a secure element (SE) that cannot be driven than n drice 6按。

If the biometric authentication methods do not meet the spoof and imposter acceptance rates as described in section 7.3.10 :

  • [C-5-1] The methods MUST be disabled if the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_BIOMETRIC_WEAK .
  • [C-5-2] The user MUST be challenged for the recommended primary authentication (eg: PIN, pattern, password) after any 4-hour idle timeout period. The idle timeout period is reset after any successful confirmation of the device credentials.
  • [C-5-3] The methods MUST NOT be treated as a secure lock screen, and MUST meet the requirements that start with C-8 in this section below.

If device implementations add or modify the authentication methods to unlock the lock screen and a new authentication method is based on a physical token or the location:

  • [C-6-1] They MUST have a fall-back mechanism to use one of the recommended primary authentication methods which is based on a known secret and meet the requirements to be treated as a secure lock screen.
  • [C-6-2] The new method MUST be disabled and only allow one of the recommended primary authentication methods to unlock the screen when the Device Policy Controller (DPC) application has set the policy with either the DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_TRUST_AGENTS) method or the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_UNSPECIFIED .
  • [C-6-3] The user MUST be challenged for one of the recommended primary authentication methods (egPIN, pattern, password) at least once every 72 hours or less.
  • [C-6-4] The new method MUST NOT be treated as a secure lock screen and MUST follow the constraints listed in C-8 below.

If device implementations have a secure lock screen and include one or more trust agent, which implements the TrustAgentService System API, they:

  • [C-7-1] MUST have clear indication in the settings menu and on the lock screen when device lock is deferred or can be unlocked by trust agent(s). For example, AOSP meets this requirement by showing a text description for the "Automatically lock setting" and "Power button instantly locks" in the settings menu and a distinguishable icon on the lock screen.
  • [C-7-2] MUST respect and fully implement all trust agent APIs in the DevicePolicyManager class, such as the KEYGUARD_DISABLE_TRUST_AGENTS constant.
  • [C-7-3] MUST NOT fully implement the TrustAgentService.addEscrowToken() function on a device that is used as a primary personal device (eg handheld) but MAY fully implement the function on device implementations that are typically shared (eg Android Television or Automotive device).
  • [C-7-4] MUST encrypt all stored tokens added by TrustAgentService.addEscrowToken() .
  • [C-7-5] MUST NOT store the encryption key on the same device where the key is used. For example, it is allowed for a key stored on a phone to unlock a user account on a TV.
  • [C-7-6] MUST inform the user about the security implications before enabling the escrow token to decrypt the data storage.
  • [C-7-7] MUST have a fall-back mechanism to use one of the recommended primary authentication methods.
  • [C-7-8] The user MUST be challenged for one of the recommended primary authentication (eg: PIN, pattern, password) methods at least once every 72 hours or less.
  • [C-7-9] The user MUST be challenged for one of the recommended primary authentication (eg: PIN, pattern, password) methods after any 4-hour idle timeout period. The idle timeout period is reset after any successful confirmation of the device credentials.
  • [C-7-10] MUST NOT be treated as a secure lock screen and MUST follow the constraints listed in C-8 below.

If device implementations add or modify the authentication methods to unlock the lock screen that is not a secure lock screen as described above, and use a new authentication method to unlock the keyguard:

9.11.2.保險櫃

The Android Keystore System allows app developers to store cryptographic keys in a dedicated secure processor as well as the isolated execution environment described above.

設備實現:

  • [C-SR] Are STRONGLY RECOMMENDED to support StrongBox.

If device implementations support StrongBox, they:

  • [C-1-1] MUST declare FEATURE_STRONGBOX_KEYSTORE .

  • [C-1-2] MUST provide dedicated secure hardware that is used to back keystore and secure user authentication.

  • [C-1-3] MUST have a discrete CPU that shares no cache, DRAM, coprocessors or other core resources with the application processor (AP).

  • [C-1-4] MUST ensure that any peripherals shared with the AP cannot alter StrongBox processing in any way, or obtain any information from the StrongBox. The AP MAY disable or block access to StrongBox.

  • [C-1-5] MUST have an internal clock with reasonable accuracy (+-10%) that is immune to manipulation by the AP.

  • [C-1-6] MUST have a true random number generator that produces uniformly-distributed and unpredictable output.

  • [C-1-7] MUST have tamper resistance, including resistance against physical penetration, and glitching.

  • [C-1-8] MUST have side-channel resistance, including resistance against leaking information via power, timing, electromagnetic radiation, and thermal radiation side channels.

  • [C-1-9] MUST have secure storage which ensures confidentiality, integrity, authenticity, consistency, and freshness of the contents. The storage MUST NOT be able to be read or altered, except as permitted by the StrongBox APIs.

  • To validate compliance with [C-1-3] through [C-1-9], device implementations:

    • [C-1-10] MUST include the hardware that is certified against the Secure IC Protection Profile BSI-CC-PP-0084-2014 or evaluated by a nationally accredited testing laboratory incorporating High attack potential vulnerability assessment according to the Common Criteria Application of Attack Potential to Smartcards .
    • [C-1-11] MUST include the firmware that is evaluated by a nationally accredited testing laboratory incorporating High attack potential vulnerability assessment according to the Common Criteria Application of Attack Potential to Smartcards .
    • [C-SR] Are STRONGLY RECOMMENDED to include the hardware that is evaluated using a Security Target, Evaluation Assurance Level (EAL) 5, augmented by AVA_VAN.5. EAL 5 certification will likely become a requirement in a future release.
  • [C-SR] are STRONGLY RECOMMENDED to provide insider attack resistance (IAR), which means that an insider with access to firmware signing keys cannot produce firmware that causes the StrongBox to leak sadabled, procise 片面tive用戶資料。 The recommended way to implement IAR is to allow firmware updates only when the primary user password is provided via the IAuthSecret HAL.

9.12.資料刪除

All device implementations:

  • [C-0-1] MUST provide users a mechanism to perform a "Factory Data Reset".
  • [C-0-2] MUST delete all user-generated data. That is, all data except for the following:
    • The system image
    • Any operating system files required by the system image
  • [C-0-3] MUST delete the data in such a way that will satisfy relevant industry standards such as NIST SP800-88.
  • [C-0-4] MUST trigger the above "Factory Data Reset" process when the DevicePolicyManager.wipeData() API is called by the primary user's Device Policy Controller app.
  • MAY provide a fast data wipe option that conducts only a logical data erase.

9.13。安全啟動模式

Android provides Safe Boot Mode, which allows users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as "Safe Boot Mode", provides the user the capability to uninstall potentially harmful third-party apps.

Device implementations are:

  • [SR] STRONGLY RECOMMENDED to implement Safe Boot Mode.

If device implementations implement Safe Boot Mode, they:

  • [C-1-1] MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except when the third-party app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag as true.

  • [C-1-2] MUST provide the user the capability to uninstall any third-party apps within Safe Mode.

  • SHOULD provide the user an option to enter Safe Boot Mode from the boot menu using a workflow that is different from that of a normal boot.

9.14。汽車車輛系統隔離

Android Automotive devices are expected to exchange data with critical vehicle subsystems by using the vehicle HAL to send and receive messages over vehicle networks such as CAN bus.

The data exchange can be secured by implementing security features below the Android framework layers to prevent malicious or unintentional interaction with these subsystems.

9.15。訂閱計劃

"Subscription plans" refer to the billing relationship plan details provided by a mobile carrier through SubscriptionManager.setSubscriptionPlans() .

All device implementations:

  • [C-0-1] MUST return subscription plans only to the mobile carrier app that has originally provided them.
  • [C-0-2] MUST NOT remotely back up or upload subscription plans.
  • [C-0-3] MUST only allow overrides, such as SubscriptionManager.setSubscriptionOverrideCongested() , from the mobile carrier app currently providing valid subscription plans.

10.軟體相容性測試

設備實作必須通過本節中所述的所有測試。但是,請注意,沒有軟體測試軟體包是完全全面的。 For this reason, device implementers are STRONGLY RECOMMENDED to make the minimum number of changes as possible to the reference and preferred implementation of Android available from the Android Open Source Project.這將最大程度地降低引入錯誤的風險,從而創建不相容,需要返工和潛在的設備更新。

10.1.相容性測試套件

設備實現:

  • [C-0-1] MUST pass the Android Compatibility Test Suite (CTS) available from the Android Open Source Project, using the final shipping software on the device.

  • [C-0-2] MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code.

CTS設計為在實際設備上運作。像任何軟體一樣,CTS本身可能包含錯誤。 The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 9.

設備實現:

  • [C-0-3] MUST pass the latest CTS version available at the time the device software is completed.

  • SHOULD use the reference implementation in the Android Open Source tree as much as possible.

10.2. CTS驗證器

CTS驗證儀包含在相容性測試套件中,旨在由人類操作員運行,以測試無法通過自動化系統測試的功能,例如相機和感測器的正確功能。

設備實現:

  • [C-0-1] MUST correctly execute all applicable cases in the CTS verifier.

CTS驗證儀對許多硬體進行了測試,包括一些可選的硬體。

設備實現:

  • [C-0-2] MUST pass all tests for hardware that they possess;例如,如果裝置具有加速度計,則必須在CTS驗證器中正確執行加速度計測試案例。

可以跳過或省略此相容性定義文件所指出的功能的測試案例。

  • [C-0-2] Every device and every build MUST correctly run the CTS Verifier, as noted above.但是,由於許多建置非常相似,因此不會期望裝置實作者明確地在僅以微不足道的方式上建置的CTS驗證器。具體而言,與僅通過包含的語言環境,品牌等的集合透過CTS驗證者的實現不同的實現設備實現可能會省略CTS驗證器測試。

11. 可更新的軟體

  • [C-0-1] Device implementations MUST include a mechanism to replace the entirety of the system software.該機制不必執行「即時」升級,也就是說,可能需要重新啟動設備。只要可以替換設備上預先安裝的整個軟體,就可以使用任何方法。例如,以下任何方法都可以滿足此要求:

    • “Over-the-air (OTA)” downloads with offline update via reboot.
    • “Tethered” updates over USB from a host PC.
    • “Offline” updates via a reboot and update from a file on removable storage.
  • [C-0-2] The update mechanism used MUST support updates without wiping user data.也就是說,更新機制必須保留應用程式私人資料和應用程式共享資料。請注意,上游Android軟體包括滿足此要求的更新機制。

If the device implementations includes support for an unmetered data connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile, then, they:

  • [C-1-1] MUST support OTA downloads with offline update via reboot.

For device implementations that are launching with Android 6.0 and later, the update mechanism SHOULD support verifying that the system image is binary identical to expected result following an OTA.自Android 5.1以來新增的上游Android開源專案中基於區塊的OTA實作滿足了這項要求。

Also, device implementations SHOULD support A/B system updates . The AOSP implements this feature using the boot control HAL.

If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, then:

  • [C-2-1] The device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.

Android includes features that allow the Device Owner app (if present) to control the installation of system updates. If the system update subsystem for devices report android.software.device_admin then, they:

12. 文件變更日誌

For a summary of changes to the Compatibility Definition in this release:

For a summary of changes to individuals sections:

  1. 介紹
  2. 設備類型
  3. 軟體
  4. Application Packaging
  5. 多媒體
  6. Developer Tools and Options
  7. 硬體相容性
  8. 性能和功率
  9. 安全模型
  10. Software Compatibility Testing
  11. Updatable Software
  12. 文件變更日誌
  13. 聯絡我們

12.1。變更日誌查看提示

Changes are marked as follows:

  • CDD
    Substantive changes to the compatibility requirements.

  • 文件
    Cosmetic or build related changes.

For best viewing, append the pretty=full and no-merges URL parameters to your changelog URLs.

13. 聯絡我們

您可以加入Android 相容性論壇並要求澄清或提出您認為該文件未涵蓋的任何問題。