最後更新：2013 年 11 月 27 日
版權所有 © 2013，谷歌公司。保留所有權利。
3.2.軟 API 兼容性
3.3.原生 API 兼容性
3.5. API 行為兼容性
3.6. API 命名空間
7.4.2. IEEE 802.11（無線網絡）
本文檔列舉了設備與 Android 4.4 兼容必須滿足的要求。
“必須”、“不得”、“要求”、“應”、“不應”、“應該”、“不應”、“推薦”、“可能”和“可選”的使用符合 IETF 標準在 RFC2119 [資源，1 ] 中定義。
本文檔中使用的“設備實施者”或“實施者”是指開發運行 Android 4.4 的硬件/軟件解決方案的個人或組織。 “設備實現”或“實現”是這樣開發的硬件/軟件解決方案。
要被視為與 Android 4.4 兼容，設備實現必須滿足本兼容性定義中提出的要求，包括通過引用併入的任何文檔。
如果此定義或第 10 節中描述的軟件測試是沉默的、模棱兩可的或不完整的，則設備實現者有責任確保與現有實現的兼容性。
出於這個原因，Android 開源項目 [ Resources, 3 ] 既是 Android 的參考實現，也是首選實現。強烈建議設備實施者盡可能將其實施基於 Android 開源項目提供的“上游”源代碼。雖然假設某些組件可以替換為替代實現，但強烈建議不要這樣做，因為通過軟件測試將變得更加困難。實施者有責任確保與標準 Android 實施的行為完全兼容，包括和超越兼容性測試套件。最後，請注意，本文檔明確禁止某些組件替換和修改。
- IETF RFC2119 要求級別： http ://www.ietf.org/rfc/rfc2119.txt
- Android 兼容性計劃概述：http: //source.android.com/compatibility/index.html
- Android 開源項目：http: //source.android.com/
- API 定義和文檔：http: //developer.android.com/reference/packages.html
- Android 權限參考：http: //developer.android.com/reference/android/Manifest.permission.html
- android.os.Build 參考：http: //developer.android.com/reference/android/os/Build.html
- Android 4.4 允許的版本字符串：http: //source.android.com/compatibility/4.4/versions.html
- 渲染腳本：http: //developer.android.com/guide/topics/graphics/renderscript.html
- 硬件加速：http: //developer.android.com/guide/topics/graphics/hardware-accel.html
- android.webkit.WebView 類：http: //developer.android.com/reference/android/webkit/WebView.html
- HTML5：http: //www.whatwg.org/specs/web-apps/current-work/multipage/
- HTML5 離線功能： http ://dev.w3.org/html5/spec/Overview.html#offline
- HTML5 視頻標籤： http ://dev.w3.org/html5/spec/Overview.html#video
- HTML5/W3C 地理定位 API： http ://www.w3.org/TR/geolocation-API/
- HTML5/W3C 網絡存儲 API： http ://www.w3.org/TR/webstorage/
- HTML5/W3C IndexedDB API： http ://www.w3.org/TR/IndexedDB/
- Dalvik 虛擬機規範：可在 Android 源代碼中找到，位於 dalvik/docs
- AppWidgets：http: //developer.android.com/guide/practices/ui_guidelines/widget_design.html
- 通知：http: //developer.android.com/guide/topics/ui/notifiers/notifications.html
- 應用資源： http ://code.google.com/android/reference/available-resources.html
- 狀態欄圖標樣式指南：http: //developer.android.com/guide/practices/ui_guidelines/icon_design_status_bar.html
- 搜索管理器：http: //developer.android.com/reference/android/app/SearchManager.html
- 祝酒詞：http: //developer.android.com/reference/android/widget/Toast.html
- 主題：http: //developer.android.com/guide/topics/ui/themes.html
- R.style 類：http: //developer.android.com/reference/android/R.style.html
- 動態壁紙：http: //developer.android.com/resources/articles/live-wallpapers.html
- Android 設備管理：http: //developer.android.com/guide/topics/admin/device-admin.html
- DevicePolicyManager 參考：http: //developer.android.com/reference/android/app/admin/DevicePolicyManager.html
- Android 無障礙服務 API：http: //developer.android.com/reference/android/accessibilityservice/package-summary.html
- Android 無障礙 API：http: //developer.android.com/reference/android/view/accessibility/package-summary.html
- 眼睛免費項目： http ://code.google.com/p/eyes-free
- 文字轉語音 API：http: //developer.android.com/reference/android/speech/tts/package-summary.html
- 參考工具文檔（用於 adb、aapt、ddms、systrace）：http: //developer.android.com/guide/developing/tools/index.html
- Android apk 文件說明：http: //developer.android.com/guide/topics/fundamentals.html
- 清單文件：http: //developer.android.com/guide/topics/manifest/manifest-intro.html
- 猴子測試工具：http: //developer.android.com/guide/developing/tools/monkey.html
- Android android.content.pm.PackageManager 類和硬件特性列表：http: //developer.android.com/reference/android/content/pm/PackageManager.html
- 支持多屏：http: //developer.android.com/guide/practices/screens_support.html
- android.util.DisplayMetrics：http: //developer.android.com/reference/android/util/DisplayMetrics.html
- android.content.res.Configuration：http: //developer.android.com/reference/android/content/res/Configuration.html
- android.hardware.SensorEvent：http: //developer.android.com/reference/android/hardware/SensorEvent.html
- 藍牙 API：http: //developer.android.com/reference/android/bluetooth/package-summary.html
- NDEF 推送協議：http: //source.android.com/compatibility/ndef-push-protocol.pdf
- MIFARE MF1S503X： http ://www.nxp.com/documents/data_sheet/MF1S503x.pdf
- MIFARE MF1S703X： http ://www.nxp.com/documents/data_sheet/MF1S703x.pdf
- MIFARE MF0ICU1： http ://www.nxp.com/documents/data_sheet/MF0ICU1.pdf
- MIFARE MF0ICU2： http ://www.nxp.com/documents/short_data_sheet/MF0ICU2_SDS.pdf
- MIFARE AN130511： http ://www.nxp.com/documents/application_note/AN130511.pdf
- MIFARE AN130411： http ://www.nxp.com/documents/application_note/AN130411.pdf
- 相機方向 API：http: //developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)
- 相機：http: //developer.android.com/reference/android/hardware/Camera.html
- Android 打開附件：http: //developer.android.com/guide/topics/usb/accessory.html
- USB 主機 API：http: //developer.android.com/guide/topics/usb/host.html
- Android 安全和權限參考：http: //developer.android.com/guide/topics/security/permissions.html
- 適用於 Android 的應用程序： http ://code.google.com/p/apps-for-android
- 安卓下載管理器：http: //developer.android.com/reference/android/app/DownloadManager.html
- 安卓文件傳輸： http ://www.android.com/filetransfer
- Android 媒體格式：http: //developer.android.com/guide/appendix/media-formats.html
- HTTP 直播流協議草案： http ://tools.ietf.org/html/draft-pantos-http-live-streaming-03
- NFC 連接切換： http ://www.nfc-forum.org/specs/spec_list/#conn_handover
- 使用 NFC 的藍牙安全簡單配對： http ://www.nfc-forum.org/resources/AppDocs/NFCForum_AD_BTSSP_1_0.pdf
- Wi-Fi 組播 API：http: //developer.android.com/reference/android/net/wifi/WifiManager.MulticastLock.html
- 動作輔助：http: //developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST
- USB 充電規範： http ://www.usb.org/developers/devclass_docs/USB_Battery_Charging_1.2.pdf
- Android Beam：http: //developer.android.com/guide/topics/nfc/nfc.html
- Android USB 音頻：http: //developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO
- Android NFC 共享設置：http: //developer.android.com/reference/android/provider/Settings.html#ACTION_NFCSHARING_SETTINGS
- Wi-Fi 直連（Wi-Fi P2P）：http: //developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html
- 鎖定和主屏幕小部件：http: //developer.android.com/reference/android/appwidget/AppWidgetProviderInfo.html
- 用戶管理器參考：http: //developer.android.com/reference/android/os/UserManager.html
- 外部存儲參考：http: //source.android.com/devices/tech/storage
- 外部存儲 API：http: //developer.android.com/reference/android/os/Environment.html
- 短信短代碼： http ://en.wikipedia.org/wiki/Short_code
- 媒體遠程控制客戶端：http: //developer.android.com/reference/android/media/RemoteControlClient.html
- 顯示管理器：http: //developer.android.com/reference/android/hardware/display/DisplayManager.html
- 夢想：http: //developer.android.com/reference/android/service/dreams/DreamService.html
- Android 應用程序開發相關設置：http: //developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS
- 相機：http: //developer.android.com/reference/android/hardware/Camera.Parameters.html
- EGL 擴展-EGL_ANDROID_RECORDABLE： http ://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_recordable.txt
- 運動事件 API：http: //developer.android.com/reference/android/view/MotionEvent.html
- 觸摸輸入配置：http: //source.android.com/devices/tech/input/touch-devices.html
- Unicode 6.1.0： http ://www.unicode.org/versions/Unicode6.1.0/
- WebView 兼容性：http: //www.chromium.org/
- Android 設備所有者應用程序：http: //developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp(java.lang.String)
- WifiManager API：http: //developer.android.com/reference/android/net/wifi/WifiManager.html
- RTC 硬件編碼要求： http ://www.webmproject.org/hardware/rtc-coding-requirements/
- Settings.Secure LOCATION_MODE：http: //developer.android.com/reference/android/provider/Settings.Secure.html#LOCATION_MODE
- 內容解析器：http: //developer.android.com/reference/android/content/ContentResolver.html
- SettingInjectorService：http: //developer.android.com/reference/android/location/SettingInjectorService.html
- 基於主機的卡模擬：http: //developer.android.com/guide/topics/connectivity/nfc/hce.html
- 電話服務提供商：http: //developer.android.com/reference/android/provider/Telephony.html
其中許多資源直接或間接從 Android SDK 派生，並且在功能上與該 SDK 文檔中的信息相同。在此兼容性定義或兼容性測試套件與 SDK 文檔不一致的任何情況下，SDK 文檔被視為權威。上述參考文獻中提供的任何技術細節都被視為包含在本兼容性定義中。
3.1。託管 API 兼容性
託管（基於 Dalvik）的執行環境是 Android 應用程序的主要工具。 Android 應用程序編程接口 (API) 是向在託管 VM 環境中運行的應用程序公開的一組 Android 平台接口。設備實現必須提供 Android SDK [資源，4 ] 公開的任何文檔化 API 的完整實現，包括所有文檔化行為。
設備實現不得省略任何託管 API、更改 API 接口或簽名、偏離記錄的行為或包含無操作，除非此兼容性定義特別允許。
此兼容性定義允許設備實現忽略 Android 包含 API 的某些類型的硬件。在這種情況下，API 必須仍然存在並以合理的方式運行。有關此場景的具體要求，請參見第 7 節。
3.2.軟 API 兼容性
除了第 3.1 節中的託管 API 之外，Android 還包括一個重要的僅運行時“軟”API，其形式為諸如 Intent、權限和 Android 應用程序的類似方面等無法在應用程序編譯時強制執行的方面。
設備實現者必須支持並強制執行權限參考頁 [資源，5 ] 中記錄的所有權限常量。請注意，第 9 節列出了與 Android 安全模型相關的其他要求。
Android API 在
android.os.Build類 [ Resources, 6 ] 上包含許多常量，用於描述當前設備。為了在設備實現中提供一致、有意義的值，下表包含了對設備實現必須遵守的這些值的格式的額外限制。
|版本.發布||當前執行的 Android 系統的版本，採用人類可讀的格式。該字段必須具有 [ Resources, 7 ] 中定義的字符串值之一。|
|版本.SDK||當前執行的 Android 系統的版本，採用第三方應用程序代碼可訪問的格式。對於 Android 4.4，此字段必須具有整數值 19。|
|VERSION.SDK_INT||當前執行的 Android 系統的版本，採用第三方應用程序代碼可訪問的格式。對於 Android 4.4，此字段必須具有整數值 19。|
|版本.增量||設備實現者選擇的值，以人類可讀的格式指定當前執行的 Android 系統的特定構建。此值不得重新用於最終用戶可用的不同構建。此字段的典型用途是指示使用哪個構建號或源代碼控制更改標識符來生成構建。該字段的具體格式沒有要求，但不能為空或空字符串（“”）。|
|木板||設備實現者選擇的一個值，用於標識設備使用的特定內部硬件，採用人類可讀的格式。該字段的一個可能用途是指示為設備供電的電路板的特定版本。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|牌||反映與最終用戶所知的設備關聯的品牌名稱的值。必須採用人類可讀的格式，並且應該代表設備的製造商或銷售該設備的公司品牌。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|CPU_ABI||本機代碼的指令集名稱（CPU 類型 + ABI 約定）。請參閱第 3.3 節：本機 API 兼容性。|
|CPU_ABI2||本機代碼的第二個指令集（CPU 類型 + ABI 約定）的名稱。請參閱第 3.3 節：本機 API 兼容性。|
|設備||由設備實現者選擇的一個值，包含標識硬件功能配置和設備工業設計的開發名稱或代號。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
指紋不得包含空格字符。如果上面模板中包含的其他字段包含空格字符，則必須在構建指紋中將它們替換為另一個字符，例如下劃線（“_”）字符。該字段的值必須可編碼為 7 位 ASCII。
|硬件||硬件的名稱（來自內核命令行或 /proc）。它應該是合理的人類可讀的。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|ID||設備實現者選擇的標識符，用於引用特定版本，採用人類可讀的格式。此字段可以與 android.os.Build.VERSION.INCREMENTAL 相同，但應該是一個足以讓最終用戶區分軟件構建的值。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|製造商||產品的原始設備製造商 (OEM) 的商品名稱。該字段的具體格式沒有要求，但不能為空或空字符串（“”）。|
|產品||設備實施者選擇的一個值，其中包含特定產品 (SKU) 的開發名稱或代碼名稱，在同一品牌中應該是唯一的。必須是人類可讀的，但不一定供最終用戶查看。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|串行||硬件序列號，必須可用。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|標籤||由設備實現者選擇的以逗號分隔的標籤列表，用於進一步區分構建。例如，“未簽名，調試”。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
|類型||設備實現者選擇的值，指定構建的運行時配置。該字段應該具有對應於三個典型 Android 運行時配置的值之一：“user”、“userdebug”或“eng”。此字段的值必須可編碼為 7 位 ASCII 並匹配正則表達式|
設備實現必須遵循 Android 的鬆散耦合 Intent 系統，如下節所述。 “尊敬”是指設備實現者必須提供一個 Android 活動或服務，該活動或服務指定一個匹配的 Intent 過濾器，並綁定到每個指定的 Intent 模式並實現正確的行為。
但是，任何此類替代版本都必須遵循上游項目提供的相同 Intent 模式。例如，如果設備包含替代音樂播放器，它仍必須遵循第三方應用程序發布的 Intent 模式來挑選歌曲。
以下應用程序被視為核心 Android 系統應用程序：
核心 Android 系統應用程序包括各種被視為“公共”的 Activity 或 Service 組件。也就是說，屬性“android:exported”可能不存在，或者可能具有值“true”。
對於在核心 Android 系統應用之一中定義的每個 Activity 或 Service，如果沒有通過值為“false”的 android:exported 屬性標記為非公共，設備實現必須包含實現相同 Intent 過濾器的相同類型的組件模式作為核心的Android系統應用程序。
換句話說，設備實現可能會取代核心的 Android 系統應用程序；但是，如果支持，設備實現必須支持每個被替換的核心 Android 系統應用程序定義的所有 Intent 模式。
由於 Android 是一個可擴展的平台，設備實現必須允許第 220.127.116.11 節中引用的每個 Intent 模式被第三方應用程序覆蓋。上游 Android 開源實現默認允許這樣做；設備實現者不得將特殊權限附加到系統應用程序對這些 Intent 模式的使用，或阻止第三方應用程序綁定並控制這些模式。該禁止具體包括但不限於禁用“選擇器”用戶界面，該界面允許用戶在所有處理相同意圖模式的多個應用程序之間進行選擇。
但是，如果默認活動為數據 URI 提供更具體的過濾器，則設備實現可以為特定 URI 模式（例如 http://play.google.com）提供默認活動。例如，指定數據 URI“http://www.android.com”的意圖過濾器比“http://”的瀏覽器過濾器更具體。設備實現必須為用戶提供一個用戶界面來修改意圖的默認活動。
設備實現不得包含任何使用 android.* 或 com.android.* 命名空間中的 ACTION、CATEGORY 或其他鍵字符串來支持任何新 Intent 或 Broadcast Intent 模式的 Android 組件。設備實施者不得在屬於另一個組織的包空間中包含任何使用 ACTION、CATEGORY 或其他鍵字符串來尊重任何新 Intent 或 Broadcast Intent 模式的 Android 組件。設備實現者不得更改或擴展第 18.104.22.168 節中列出的核心應用程序使用的任何 Intent 模式。設備實現可能包括使用名稱空間的 Intent 模式，這些名稱空間與它們自己的組織相關聯。
這種禁止類似於第 3.6 節中為 Java 語言類指定的禁止。
第三方應用程序依靠平台廣播某些 Intent 來通知他們硬件或軟件環境的變化。 Android 兼容設備必須廣播公共廣播 Intent 以響應適當的系統事件。廣播意圖在 SDK 文檔中進行了描述。
Android 4.4 添加了允許用戶選擇其默認 Home 和 SMS 應用程序的設置。設備實現必須為每個提供類似的用戶設置菜單，與 SDK 文檔 [資源，91 ] 中描述的 Intent 過濾器模式和 API 方法兼容。
3.3.原生 API 兼容性
在 Dalvik 中運行的託管代碼可以調用應用程序 .apk 文件中提供的本機代碼，作為為適當的設備硬件架構編譯的 ELF .so 文件。由於本機代碼高度依賴於底層處理器技術，Android 在文件
docs/CPU-ARCH-ABIS.html中的 Android NDK 中定義了許多應用程序二進制接口 (ABI)。如果設備實現與一個或多個定義的 ABI 兼容，它應該實現與 Android NDK 的兼容性，如下所示。
如果設備實現包括對 Android ABI 的支持，它：
- 必須包括對在託管環境中運行的代碼的支持，以調用本機代碼，使用標準 Java 本機接口 (JNI) 語義
- 必須與以下列表中的每個所需庫兼容源代碼（即標頭兼容）和二進制兼容（對於 ABI）
docs/CPU-ARCH-ABIS.html中報告最新版本的 Android NDK 中記錄的 ABI
android.os.Build.CPU_ABI僅報告下列 ABI 之一
- 應該使用上游 Android 開源項目中可用的源代碼和頭文件構建
以下本機代碼 API 必須可用於包含本機代碼的應用程序：
- libc（C 庫）
- 對 C++ 的最低支持
- liblog（Android 日誌記錄）
- libz（Zlib 壓縮）
- libGLESv1_CM.so (OpenGL ES 1.0)
- libGLESv2.so (OpenGL ES 2.0)
- libGLESv3.so (OpenGL ES 3.0)
- libEGL.so（原生 OpenGL 表面管理）
- libOpenSLES.so（OpenSL ES 1.0.1 音頻支持）
- libOpenMAXAL.so（OpenMAX AL 1.0.1 支持）
- libandroid.so（原生 Android 活動支持）
- 支持 OpenGL，如下所述
請注意，Android NDK 的未來版本可能會引入對其他 ABI 的支持。如果設備實現與現有的預定義 ABI 不兼容，則它絕不能報告對任何 ABI 的支持。
請注意，設備實現必須包含 libGLESv3.so，並且必須符號鏈接（符號）鏈接到 libGLESv2.so。在聲明支持 OpenGL ES 3.0 的設備實現上，除了 OpenGL ES 2.0 函數符號之外，libGLESv2.so 還必須導出 OpenGL ES 3.0 函數符號。
3.4.1。 Web 視圖兼容性
Android 開源實現使用來自 Chromium 項目的代碼來實現
android.webkit.WebView [資源，10 ]。因為為 Web 渲染系統開發全面的測試套件是不可行的，所以設備實現者必須在 WebView 實現中使用 Chromium 的特定上游構建。具體來說：
android.webkit.WebView實現必須基於來自上游 Android 開源項目 for Android 4.4 的 Chromium 構建。此版本包括一組特定的 WebView 功能和安全修復程序。 [資源，83 ]
- WebView 報告的用戶代理字符串必須採用以下格式：
Mozilla/5.0 (Linux; Android $(VERSION); $(LOCALE); $(MODEL) Build/$(BUILD)) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 $(CHROMIUM_VER) Mobile Safari/537.36
- $(VERSION) 字符串的值必須與
- $(LOCALE) 字符串的值是可選的，應該遵循國家代碼和語言的 ISO 約定，並且應該參考設備當前配置的區域設置。如果省略，尾隨分號也必須被刪除。
- $(MODEL) 字符串的值必須與
- $(BUILD) 字符串的值必須與
- $(CHROMIUM_VER) 字符串的值必須是上游 Android 開源項目中 Chromium 的版本。
- $(VERSION) 字符串的值必須與
WebView 組件應該盡可能多地支持 HTML5 [參考資料，11 ]。
設備實現必須包含用於一般用戶網頁瀏覽的獨立瀏覽器應用程序。獨立瀏覽器可能基於 WebKit 以外的瀏覽器技術。但是，即使使用備用瀏覽器應用程序，提供給第三方應用程序的
android.webkit.WebView組件也必須基於 WebKit，如第 3.4.1 節所述。
獨立的瀏覽器應用程序（無論是基於上游 WebKit 瀏覽器應用程序還是第三方替代品）應該盡可能多地支持 HTML5 [參考資料，11 ]。最低限度，設備實現必須支持與 HTML5 相關的這些 API：
3.5. API 行為兼容性
每種 API 類型（託管、軟、原生和 Web）的行為必須與上游 Android 開源項目 [資源，3 ] 的首選實現一致。一些特定的兼容性領域是：
- 設備不得更改標準 Intent 的行為或語義
上面的列表並不全面。 The Compatibility Test Suite (CTS) tests significant portions of the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to ensure behavioral compatibility with the Android Open Source Project. For this reason, device implementers SHOULD use the source code available via the Android Open Source Project where possible, rather than re-implement significant parts of the system.
3.6. API Namespaces
Android follows the package and class namespace conventions defined by the Java programming language. To ensure compatibility with third-party applications, device implementers MUST NOT make any prohibited modifications (see below) to these package namespaces:
Prohibited modifications include:
- Device implementations MUST NOT modify the publicly exposed APIs on the Android platform by changing any method or class signatures, or by removing classes or class fields.
- Device implementers MAY modify the underlying implementation of the APIs, but such modifications MUST NOT impact the stated behavior and Java-language signature of any publicly exposed APIs.
- Device implementers MUST NOT add any publicly exposed elements (such as classes or interfaces, or fields or methods to existing classes or interfaces) to the APIs above.
A "publicly exposed element" is any construct which is not decorated with the "@hide" marker as used in the upstream Android source code. In other words, device implementers MUST NOT expose new APIs or alter existing APIs in the namespaces noted above. Device implementers MAY make internal-only modifications, but those modifications MUST NOT be advertised or otherwise exposed to developers.
Device implementers MAY add custom APIs, but any such APIs MUST NOT be in a namespace owned by or referring to another organization. For instance, device implementers MUST NOT add APIs to the com.google.* or similar namespace; only Google may do so. Similarly, Google MUST NOT add APIs to other companies' namespaces. Additionally, if a device implementation includes custom APIs outside the standard Android namespace, those APIs MUST be packaged in an Android shared library so that only apps that explicitly use them (via the
<uses-library> mechanism) are affected by the increased memory usage of such APIs.
If a device implementer proposes to improve one of the package namespaces above (such as by adding useful new functionality to an existing API, or adding a new API), the implementer SHOULD visit source.android.com and begin the process for contributing changes and code, according to the information on that site.
Note that the restrictions above correspond to standard conventions for naming APIs in the Java programming language; this section simply aims to reinforce those conventions and make them binding through inclusion in this compatibility definition.
3.7. Virtual Machine Compatibility
Device implementations MUST support the full Dalvik Executable (DEX) bytecode specification and Dalvik Virtual Machine semantics [ Resources, 17 ].
Device implementations MUST configure Dalvik to allocate memory in accordance with the upstream Android platform, and as specified by the following table. (See Section 7.1.1 for screen size and screen density definitions.)
Note that memory values specified below are considered minimum values, and device implementations MAY allocate more memory per application.
|Screen Size||Screen Density||Application Memory|
|small / normal / large||ldpi / mdpi||16MB|
|small / normal / large||tvdpi / hdpi||32MB|
|small / normal / large||xhdpi||64MB|
|small / normal / large||400dpi||96MB|
|small / normal / large||xxhdpi||128MB|
|small / normal / large||xxxhdpi||256MB|
|xlarge||tvdpi / hdpi||64MB|
3.8. User Interface Compatibility
3.8.1. Launcher (Home Screen)
Android includes a launcher application (home screen) and support for third party applications to replace the device launcher (home screen). Device implementations that allow third party applications to replace the device home screen MUST declare the platform feature
Android defines a component type and corresponding API and lifecycle that allows applications to expose an "AppWidget" to the end user [ Resources, 18 ]. Device implementations that support embedding widgets on the home screen MUST meet the following requirements and declare support for platform feature
- Device launchers MUST include built-in support for AppWidgets, and expose user interface affordances to add, configure, view, and remove AppWidgets directly within the Launcher.
- Device implementations MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. (See the App Widget Design Guidelines in the Android SDK documentation [ Resources, 18 ] for details.
- Device implementations that include support for lock screen MUST support application widgets on the lock screen.
Android includes APIs that allow developers to notify users of notable events [ Resources, 19 ], using hardware and software features of the device.
Some APIs allow applications to perform notifications or attract attention using hardware, specifically sound, vibration, and light. Device implementations MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware. For instance, if a device implementation includes a vibrator, it MUST correctly implement the vibration APIs. If a device implementation lacks hardware, the corresponding APIs MUST be implemented as no-ops. Note that this behavior is further detailed in Section 7.
Additionally, the implementation MUST correctly render all resources (icons, sound files, etc.) provided for in the APIs [ Resources, 20 ], or in the Status/System Bar icon style guide [ Resources, 21 ]. Device implementers MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation; however, such alternative notification systems MUST support existing notification resources, as above.
Android includes support for rich notifications, such as interactive Views for ongoing notifications. Device implementations MUST properly display and execute rich notifications, as documented in the Android APIs.
Android includes APIs [ Resources, 22 ] that allow developers to incorporate search into their applications, and expose their application's data into the global system search. Generally speaking, this functionality consists of a single, system-wide user interface that allows users to enter queries, displays suggestions as users type, and displays results. The Android APIs allow developers to reuse this interface to provide search within their own apps, and allow developers to supply results to the common global search user interface.
Device implementations MUST include a single, shared, system-wide search user interface capable of real-time suggestions in response to user input. Device implementations MUST implement the APIs that allow developers to reuse this user interface to provide search within their own applications. Device implementations 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 this functionality, the default behavior SHOULD be to display web search engine results and suggestions.
Applications can use the "Toast" API (defined in [ Resources, 23 ]) to display short non-modal strings to the end user, that disappear after a brief period of time. Device implementations MUST display Toasts from applications to end users in some high-visibility manner.
Android provides "themes" as a mechanism for applications to apply styles across an entire Activity or application.
Android includes a "Holo" 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 [ Resources, 24 ]. Device implementations MUST NOT alter any of the Holo theme attributes exposed to applications [ Resources, 25 ].
Android also includes a "Device Default" theme family as a set of defined styles for application developers to use if they want to match the look and feel of the device theme as defined by the device implementer. Device implementations MAY modify the DeviceDefault theme attributes exposed to applications [ Resources, 25 ].
From version 4.4, Android now supports a new variant theme with translucent system bars, allowing application developers to fill the area behind the status and navigation bar with their app content. To enable a consistent developer experience in this configuration, it is important the status bar icon style is maintained across different device implementations. Therefore, Android device implementations 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 [ Resources, 25 ].
3.8.7. Live Wallpapers
Android defines a component type and corresponding API and lifecycle that allows applications to expose one or more "Live Wallpapers" to the end user [ Resources, 26 ]. Live Wallpapers are animations, patterns, or similar images with limited input capabilities that display as a wallpaper, behind other applications.
Hardware is considered capable of reliably running live wallpapers if it can run all live wallpapers, with no limitations on functionality, at a reasonable framerate with no adverse affects on other applications. If limitations in the hardware cause wallpapers and/or applications to crash, malfunction, consume excessive CPU or battery power, or run at unacceptably low frame rates, the hardware is considered incapable of running live wallpaper. As an example, some live wallpapers may use an Open GL 1.0 or 2.0 context to render their content. Live wallpaper will not run reliably on hardware that does not support multiple OpenGL contexts because the live wallpaper use of an OpenGL context may conflict with other applications that also use an OpenGL context.
Device implementations capable of running live wallpapers reliably as described above SHOULD implement live wallpapers. Device implementations determined to not run live wallpapers reliably as described above MUST NOT implement live wallpapers.
3.8.8. Recent Application Display
The upstream Android source code includes a user interface for displaying recent applications using a thumbnail image of the application's graphical state at the moment the user last left the application. Device implementations MAY alter or eliminate this user interface; however, a future version of Android is planned to make more extensive use of this functionality. Device implementations are strongly encouraged to use the upstream Android user interface (or a similar thumbnail-based interface) for recent applications, or else they may not be compatible with a future version of Android.
3.8.9. Input Management
Android includes support for Input Management and support for third party input method editors. Device implementations that allow users to use third party input methods on the device MUST declare the platform feature
android.software.input_methods and support IME APIs as defined in the Android SDK documentation.
Device implementations that declare the
android.software.input_methods feature MUST provide a user-accessible mechanism to add and configure third party input methods. Device implementations MUST display the settings interface in response to the
3.8.10. Lock Screen Media Remote Control
Android includes support for Remote Control API that lets media applications integrate with playback controls that are displayed in a remote view like the device lock screen [ Resources, 74 ]. Device implementations that support lock screen in the device and allow users to add widgets on the home screen MUST include support for embedding remote controls in the device lock screen [ Resources, 69 ].
Android includes support for interactive screensavers called Dreams [ Resources, 76 ]. Dreams allows users to interact with applications when a charging device is idle, or docked in a desk dock. Device implementations MUST include support for Dreams and provide a settings option for users to configure Dreams.
Location modes MUST be displayed in the Location menu within Settings [ Resources, 87 ]. Location services provided through the
SettingInjectorService introduced in Android 4.4 must be displayed in the same Location menu [ Resources, 89 ].
Android 4.4 includes support for color emoji characters. Android device implementations MUST provide an input method to the user for the Emoji characters defined in Unicode 6.1 [ Resources, 82 ] and MUST be capable of rendering these emoji characters in color glyph.
3.9. Device Administration
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 [ Resources, 27 ]. Device implementations MUST provide an implementation of the
DevicePolicyManager class [ Resources, 28 ]. Device implementations that include support for lock screen MUST support the full range of device administration policies defined in the Android SDK documentation [ Resources, 27 ].
Device implementations MAY have a preinstalled application performing device administration functions but this application MUST NOT be set out-of-the box as the default Device Owner app [ Resources, 84 ].
Android provides an accessibility layer that helps users with disabilities to navigate their devices more easily. In addition, Android provides platform APIs that enable accessibility service implementations to receive callbacks for user and system events and generate alternate feedback mechanisms, such as text-to-speech, haptic feedback, and trackball/d-pad navigation [ Resources, 29 ]. Device implementations MUST provide an implementation of the Android accessibility framework consistent with the default Android implementation. Specifically, device implementations MUST meet the following requirements.
- Device implementations MUST support third party accessibility service implementations through the
android.accessibilityserviceAPIs [ Resources, 30 ].
- Device implementations MUST generate
AccessibilityEventsand deliver these events to all registered
AccessibilityServiceimplementations in a manner consistent with the default Android implementation.
- Device implementations MUST provide a user-accessible mechanism to enable and disable accessibility services, and MUST display this interface in response to the
Additionally, device implementations SHOULD provide an implementation of an accessibility service on the device, and SHOULD provide a mechanism for users to enable the accessibility service during device setup. An open source implementation of an accessibility service is available from the Eyes Free project [ Resources, 31 ].
Android includes APIs that allow applications to make use of text-to-speech (TTS) services, and allows service providers to provide implementations of TTS services [ Resources, 32 ]. Device implementations MUST meet these requirements related to the Android TTS framework:
- Device implementations MUST support the Android TTS framework APIs and SHOULD include a TTS engine supporting the languages available on the device. Note that the upstream Android open source software includes a full-featured TTS engine implementation.
- Device implementations MUST support installation of third-party TTS engines.
- Device implementations MUST provide a user-accessible interface that allows users to select a TTS engine for use at the system level.
4. Application Packaging Compatibility
Device implementations MUST install and run Android ".apk" files as generated by the "aapt" tool included in the official Android SDK [ Resources, 33 ].
Devices implementations MUST NOT extend either the .apk [ Resources, 34 ], Android Manifest [ Resources, 35 ], Dalvik bytecode [ Resources, 17 ], or renderscript bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices. Device implementers SHOULD use the reference upstream implementation of Dalvik, and the reference implementation's package management system.
5. Multimedia Compatibility
Device implementations MUST include at least one form of audio output, such as speakers, headphone jack, external speaker connection, etc.
5.1. Media Codecs
Device implementations MUST support the core media formats specified in the Android SDK documentation [ Resources, 58 ] except where explicitly permitted in this document. Specifically, device implementations MUST support the media formats, encoders, decoders, file types and container formats defined in the tables below. All of these codecs are provided as software implementations in the preferred Android implementation from the Android Open Source Project.
Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are unencumbered by third-party patents. Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may require patent licenses from the relevant patent holders.
Note that these tables do not list specific bitrate requirements for most video codecs because current device hardware does not necessarily support bitrates that map exactly to the required bitrates specified by the relevant standards. Instead, device implementations SHOULD support the highest bitrate practical on the hardware, up to the limits defined by the specifications.
|Type||Format / Codec||Encoder||Decoder||Details||File Type(s) / Container Formats|
|Audio||MPEG-4 AAC Profile (AAC LC)|| REQUIRED for device implementations that include microphone hardware and define ||REQUIRED||Support for mono/stereo/5.0/5.1* content with standard sampling rates from 8 to 48 kHz.|
|MPEG-4 HE AAC Profile (AAC+)||REQUIRED for device implementations that include microphone hardware and define android.hardware.microphone||REQUIRED||Support for mono/stereo/5.0/5.1* content with standard sampling rates from 16 to 48 kHz.|
|MPEG-4 HE AAC v2 Profile (enhanced AAC+)||REQUIRED||Support for mono/stereo/5.0/5.1* content with standard sampling rates from 16 to 48 kHz.|
|MPEG-4 Audio Object Type ER AAC ELD (Enhanced Low Delay AAC)||REQUIRED for device implementations that include microphone hardware and define android.hardware.microphone||REQUIRED||Support for mono/stereo content with standard sampling rates from 16 to 48 kHz.|
|AMR-NB|| REQUIRED for device implementations that include microphone hardware and define ||REQUIRED||4.75 to 12.2 kbps sampled @ 8kHz||3GPP (.3gp)|
|AMR-WB|| REQUIRED for device implementations that include microphone hardware and define ||REQUIRED||9 rates from 6.60 kbit/s to 23.85 kbit/s sampled @ 16kHz||3GPP (.3gp)|
|Mono/Stereo (no multichannel). Sample rates up to 48 kHz (but up to 44.1 kHz is recommended on devices with 44.1 kHz output, as the 48 to 44.1 kHz downsampler does not include a low-pass filter). 16-bit recommended; no dither applied for 24-bit.||FLAC (.flac) only|
|MP3||REQUIRED||Mono/Stereo 8-320Kbps constant (CBR) or variable bit-rate (VBR)||MP3 (.mp3)|
|MIDI||REQUIRED||MIDI Type 0 and 1. DLS Version 1 and 2. XMF and Mobile XMF. Support for ringtone formats RTTTL/RTX, OTA, and iMelody|
|PCM/WAVE||REQUIRED||REQUIRED||8-bit and 16-bit linear PCM** (rates up to limit of hardware).Devices MUST support sampling rates for raw PCM recording at 8000,16000 and 44100 Hz frequencies||WAVE (.wav)|
|Video||H.263|| REQUIRED for device implementations that include camera hardware and define ||REQUIRED|
|H.264 AVC|| REQUIRED for device implementations that include camera hardware and define ||REQUIRED||Baseline Profile (BP)|
|MPEG-4 SP||REQUIRED||3GPP (.3gp)|
|WebM (.webm) and Matroska (.mkv, Android 4.0+)***|
|WebM (.webm) and Matroska (.mkv, Android 4.0+)***|
- *Note: Only downmix of 5.0/5.1 content is required; recording or rendering more than 2 channels is optional.
- **Note: 16-bit linear PCM capture is mandatory. 8-bit linear PCM capture is not mandatory.
- ***Note: Device implementations SHOULD support writing Matroska WebM files.
- ****Note: For acceptable quality of web video streaming and video-conference services, device implementations SHOULD use a hardware VP8 codec that meets the requirements in [ Resources, 86 ].
5.2. Video Encoding
Android device implementations that include a rear-facing camera and declare
android.hardware.camera SHOULD support the following H.264 video encoding profiles.
|SD (Low quality)||SD (High quality)||HD (When supported by hardware)|
|Video resolution||176 x 144 px||480 x 360 px||1280 x 720 px|
|Video frame rate||12 fps||30 fps||30 fps|
|Video bitrate||56 Kbps||500 Kbps or higher||2 Mbps or higher|
|Audio channels||1 (mono)||2 (stereo)||2 (stereo)|
|Audio bitrate||24 Kbps||128 Kbps||192 Kbps|
Android device implementations that include a rear-facing camera and declare
android.hardware.camera SHOULD support the following VP8 video encoding profiles
|SD (Low quality)||SD (High quality)|| HD 720p|
(When supported by hardware)
| HD 1080p|
(When supported by hardware)
|Video resolution||320 x 180 px||640 x 360 px||1280 x 720 px||1920 x 1080 px|
|Video frame rate||30 fps||30 fps||30 fps||30 fps|
|Video bitrate||800 Kbps||2 Mbps||4 Mbps||10 Mbps|
5.3. Video Decoding
Android device implementations SHOULD support the following VP8, VP9 and H.264 video decoding profiles. Device implementations SHOULD also support dynamic video resolution switching within the same stream for VP8, VP9 and H.264 codecs.
|SD (Low quality)||SD (High quality)|| HD 720p|
(When supported by hardware)
| HD 1080p|
(When supported by hardware)
|Video resolution||320 x 180 px||640 x 360 px||1280 x 720 px||1920 x 1080 px|
|Video frame rate||30 fps||30 fps||30 fps||30 fps|
|Video bitrate||800 Kbps||2 Mbps||8 Mbps||20 Mbps|
5.4. Audio Recording
When an application has used the
android.media.AudioRecord API to start recording an audio stream, device implementations that include microphone hardware and declare
android.hardware.microphone MUST sample and record audio with each of these behaviors:
- The device SHOULD exhibit approximately flat amplitude versus frequency characteristics; specifically, ±3 dB, from 100 Hz to 4000 Hz
- Audio input sensitivity SHOULD be set such that a 90 dB sound power level (SPL) source at 1000 Hz yields RMS of 2500 for 16-bit samples.
- PCM amplitude levels SHOULD 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.
- Total harmonic distortion SHOULD be less than 1% for 1Khz at 90 dB SPL input level.
In addition to the above recording specifications, when an application has started recording an audio stream using the
android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source:
- Noise reduction processing, if present, MUST be disabled.
- Automatic gain control, if present, MUST be disabled.
From Android 4.4,
android.media.MediaRecorder.AudioSource class has a new audio source:
REMOTE_SUBMIX . Devices 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 can capture a mix of all audio streams except for the following:
Note: while some of the requirements outlined above are stated as "SHOULD" since Android 4.3, the Compatibility Definition for a future version is planned to change these to "MUST". That is, these requirements are optional in Android 4.4 but will be required by a future version. Existing and new devices that run Android are very strongly encouraged to meet these requirements , or they will not be able to attain Android compatibility when upgraded to the future version.
If the platform supports noise suppression technologies tuned for speech recognition, the effect MUST be controllable from the
android.media.audiofx.NoiseSuppressor API. Moreover, the "uuid" field for the noise suppressor's effect descriptor MUST uniquely identify each implementation of the noise suppression technology.
5.5. Audio Latency
音頻延遲是音頻信號通過系統時的時間延遲。 Many classes of applications rely on short latencies, to achieve real-time sound effects.
For the purposes of this section:
- "output latency" is defined as the interval between when an application writes a frame of PCM-coded data and when the corresponding sound can be heard by an external listener or observed by a transducer
- "cold output latency" is defined as the output latency for the first frame, when the audio output system has been idle and powered down prior to the request
- "continuous output latency" is defined as the output latency for subsequent frames, after the device is already playing audio
- "input latency" is the interval between when an external sound is presented to the device and when an application reads the corresponding frame of PCM-coded data
- "cold input latency" is defined as the sum of lost input time and the input latency for the first frame, when the audio input system has been idle and powered down prior to the request
- "continuous input latency" is defined as the input latency for subsequent frames, while the device is already capturing audio
- "OpenSL ES PCM buffer queue API" is the set of PCM-related OpenSL ES APIs within Android NDK; see NDK_root
Per Section 5 , all compatible device implementations MUST include at least one form of audio output. Device implementations SHOULD meet or exceed these output latency requirements:
- cold output latency of 100 milliseconds or less
- continuous output latency of 45 milliseconds or less
If a device implementation meets the requirements of this section after any initial calibration when using the OpenSL ES PCM buffer queue API, for continuous output latency and cold output latency over at least one supported audio output device, it MAY report support for low-latency audio, by reporting the feature "android.hardware.audio.low-latency" via the
android.content.pm.PackageManager class. [ Resources, 37 ] Conversely, if the device implementation does not meet these requirements it MUST NOT report support for low-latency audio.
Per Section 7.2.5 , microphone hardware may be omitted by device implementations.
Device implementations that include microphone hardware and declare
android.hardware.microphone SHOULD meet these input audio latency requirements:
- cold input latency of 100 milliseconds or less
- continuous input latency of 50 milliseconds or less
5.6. Network Protocols
Devices MUST support the media network protocols for audio and video playback as specified in the Android SDK documentation [ Resources, 58 ]. Specifically, devices MUST support the following media network protocols:
- RTSP (RTP, SDP)
- HTTP(S) progressive streaming
- HTTP(S) Live Streaming draft protocol, Version 3 [ Resources, 59 ]
6. Developer Tools and Options Compatibility
6.1. Developer Tools
Device implementations MUST support the Android Developer Tools provided in the Android SDK. Specifically, Android-compatible devices MUST be compatible with:
- Android Debug Bridge (known as adb) [ Resources, 33 ]
Device implementations MUST support all
adbfunctions as documented in the Android SDK. The device-side
adbdaemon MUST be inactive by default, and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge.
- Android includes support for secure adb. Secure adb enables adb on known authenticated hosts. Device implementations MUST support secure adb.
- Dalvik Debug Monitor Service (known as ddms) [ Resources, 33 ]
Device implementations MUST support all
ddmsfeatures as documented in the Android SDK. As
adb, support for
ddmsSHOULD be inactive by default, but MUST be supported whenever the user has activated the Android Debug Bridge, as above.
- Monkey [ Resources, 36 ]
Device implementations MUST include the Monkey framework, and make it available for applications to use.
- SysTrace [ Resources, 33 ]
Device implementations MUST support systrace tool as documented in the Android SDK. Systrace must be inactive by default, and there MUST be a user-accessible mechanism to turn on Systrace.
Most Linux-based systems and Apple Macintosh systems recognize Android devices using the standard Android SDK tools, without additional support; however Microsoft Windows systems typically require a driver for new Android devices. (For instance, new vendor IDs and sometimes new device IDs require custom USB drivers for Windows systems.) If a device implementation is unrecognized by the
adb tool as provided in the standard Android SDK, device implementers MUST provide Windows drivers allowing developers to connect to the device using the
adb protocol. These drivers MUST be provided for Windows XP, Windows Vista, Windows 7, and Windows 8, in both 32-bit and 64-bit versions.
6.2. Developer Options
Android includes support for developers to configure application development-related settings. Device implementations MUST honor the android.settings.APPLICATION_DEVELOPMENT_SETTINGS intent to show application development-related settings [ Resources, 77 ]. The upstream Android implementation hides the Developer Options menu by default, and enables users to launch Developer Options after pressing seven (7) times on the Settings > About Device > Build Number menu item. Device implementations MUST provide a consistent experience for Developer Options. Specifically, device implementations MUST hide Developer Options by default and MUST provide a mechanism to enable Developer Options that is consistent with the upstream Android implementation.
Android 4.4 introduces ART, an experimental Android runtime, accessible within the Developer Options menu for preview. Device implementations SHOULD include ART (libart.so) and support dual boot from Developer Options, but MUST keep Dalvik (libdvm.so) as the default runtime.
7. Hardware Compatibility
If a device includes a particular hardware component that has a corresponding API for third-party developers, the device implementation MUST implement that API as described in the Android SDK documentation. If an API in the SDK interacts with a hardware component that is stated to be optional and the device implementation does not possess that component:
- complete class definitions (as documented by the SDK) for the component's APIs MUST still be present
- the API's behaviors MUST be implemented as no-ops in some reasonable fashion
- API methods MUST return null values where permitted by the SDK documentation
- API methods MUST return no-op implementations of classes where null values are not permitted by the SDK documentation
- API methods MUST NOT throw exceptions not documented by the SDK documentation
A typical example of a scenario where these requirements apply is the telephony API: even on non-phone devices, these APIs must be implemented as reasonable no-ops.
Device implementations MUST accurately report accurate hardware configuration information via the
hasSystemFeature(String) methods on the
android.content.pm.PackageManager class. [ Resources, 37 ]
7.1. Display and Graphics
Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device, to ensure that third-party applications run well on a variety of hardware configurations [ Resources, 38 ]. Devices MUST properly implement these APIs and behaviors, as detailed in this section.
The units referenced by the requirements in this section are defined as follows:
- "Physical diagonal size" is the distance in inches between two opposing corners of the illuminated portion of the display.
- "dpi" (meaning "dots per inch") is the number of pixels encompassed by a linear horizontal or vertical span of 1". Where dpi values are listed, both horizontal and vertical dpi must fall within the range.
- "Aspect ratio" is the ratio of the longer dimension of the screen to the shorter dimension. For example, a display of 480x854 pixels would be 854 / 480 = 1.779, or roughly "16:9".
- A "density-independent pixel" or ("dp") is the virtual pixel unit normalized to a 160 dpi screen, calculated as:
pixels = dps * (density / 160).
7.1.1. Screen Configuration
The Android UI framework supports a variety of different screen sizes, and allows applications to query the device screen size (aka "screen layout") via
android.content.res.Configuration.screenLayout with the
SCREENLAYOUT_SIZE_MASK . Device implementations MUST report the correct screen size as defined in the Android SDK documentation [ Resources, 38 ] and determined by the upstream Android platform. Specifically, device implementations must report the correct screen size according to the following logical density-independent pixel (dp) screen dimensions.
- Devices MUST have screen sizes of at least 426 dp x 320 dp ('small')
- Devices that report screen size 'normal' MUST have screen sizes of at least 480 dp x 320 dp
- Devices that report screen size 'large' MUST have screen sizes of at least 640 dp x 480 dp
- Devices that report screen size 'xlarge' MUST have screen sizes of at least 960 dp x 720 dp
In addition, devices MUST have screen sizes of at least 2.5 inches in physical diagonal size.
Devices MUST NOT change their reported screen size at any time.
Applications optionally indicate which screen sizes they support via the
<supports-screens> attribute in the AndroidManifest.xml file. Device implementations MUST correctly honor applications' stated support for small, normal, large, and xlarge screens, as described in the Android SDK documentation.
Screen Aspect Ratio
The aspect ratio MUST be a value from 1.3333 (4:3) to 1.86 (roughly 16:9)
The Android UI framework defines a set of standard logical densities to help application developers target application resources. Device implementations MUST report one of the following logical Android framework densities through the
android.util.DisplayMetrics APIs, and MUST execute applications at this standard density.
- 120 dpi, known as 'ldpi'
- 160 dpi, known as 'mdpi'
- 213 dpi, known as 'tvdpi'
- 240 dpi, known as 'hdpi'
- 320 dpi, known as 'xhdpi'
- 400 dpi, known as '400dpi'
- 480 dpi, known as 'xxhdpi'
- 640 dpi, known as 'xxxhdpi'
7.1.2. Display Metrics
Device implementations MUST report correct values for all display metrics defined in
android.util.DisplayMetrics [ Resources, 39 ].
7.1.3. Screen Orientation
Devices MUST support dynamic orientation by applications to either portrait or landscape screen orientation. That is, the device must respect the application's request for a specific screen orientation. Device implementations MAY select either portrait or landscape orientation as the default.
Devices 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.
Devices MUST NOT change the reported screen size or density when changing orientation.
Devices MUST report which screen orientations they support (
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, MUST only report
7.1.4. 2D and 3D Graphics Acceleration
Device implementations MUST support both OpenGL ES 1.0 and 2.0, as embodied and detailed in the Android SDK documentations. Device implementations SHOULD support OpenGL ES 3.0 on devices capable of supporting OpenGL ES 3.0. Device implementations MUST also support Android Renderscript, as detailed in the Android SDK documentation [ Resources, 8 ].
Device implementations MUST also correctly identify themselves as supporting OpenGL ES 1.0, OpenGL ES 2.0, or OpenGL ES 3.0. That is:
- The managed APIs (such as via the
GLES10.getString()method) MUST report support for OpenGL ES 1.0 and OpenGL ES 2.0
- The native C/C++ OpenGL APIs (that is, those available to apps via libGLES_v1CM.so, libGLES_v2.so, or libEGL.so) MUST report support for OpenGL ES 1.0 and OpenGL ES 2.0.
- Device implementations that declare support for OpenGL ES 3.0 MUST support OpenGL ES 3.0 managed APIs and include support for native C/C++ APIs. On device implementations that declare support for OpenGL ES 3.0, libGLESv2.so MUST export the OpenGL ES 3.0 function symbols in addition to the OpenGL ES 2.0 function symbols.
Device implementations MAY implement any desired OpenGL ES extensions. However, device implementations MUST report via the OpenGL ES managed and native APIs all extension strings that they do support, and conversely MUST NOT report extension strings that they do not support.
Note that Android includes support for applications to optionally specify that they require specific OpenGL texture compression formats. These formats are typically vendor-specific. Device implementations are not required by Android to implement any specific texture compression format. However, they SHOULD accurately report any texture compression formats that they do support, via the
getString() method in the OpenGL API.
Android includes a mechanism for applications to declare that they wanted to enable hardware acceleration for 2D graphics at the Application, Activity, Window or View level through the use of a manifest tag
android:hardwareAccelerated or direct API calls [ Resources, 9 ].
In Android 4.4, device implementations 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.
In addition, device implementations MUST exhibit behavior consistent with the Android SDK documentation on hardware acceleration [ Resources, 9 ].
Android includes a
TextureView object that lets developers directly integrate hardware-accelerated OpenGL ES textures as rendering targets in a UI hierarchy. Device implementations MUST support the
TextureView API, and MUST exhibit consistent behavior with the upstream Android implementation.
Android includes support for
EGL_ANDROID_RECORDABLE , a EGLConfig attribute that indicates whether the EGLConfig supports rendering to an ANativeWindow that records images to a video. Device implementations MUST support
EGL_ANDROID_RECORDABLE extension [ Resources, 79 ].
7.1.5. Legacy Application Compatibility Mode
Android specifies a "compatibility mode" in which the framework operates in an 'normal' screen size equivalent (320dp width) mode for the benefit of legacy applications not developed for old versions of Android that pre-date screen-size independence. Device implementations MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.
7.1.6. Screen Types
Device implementation screens are classified as one of two types:
- Fixed-pixel display implementations: the screen is a single panel that supports only a single pixel width and height. Typically the screen is physically integrated with the device. Examples include mobile phones, tablets, and so on.
- Variable-pixel display implementations: the device implementation either has no embedded screen and includes a video output port such as VGA, HDMI or a wireless port for display, or has an embedded screen that can change pixel dimensions. Examples include televisions, set-top boxes, and so on.
Fixed-Pixel Device Implementations
Fixed-pixel device implementations MAY use screens of any pixel dimensions, provided that they meet the requirements defined this Compatibility Definition.
Fixed-pixel implementations MAY include a video output port for use with an external display. However, if that display is ever used for running apps, the device MUST meet the following requirements:
- The device MUST report the same screen configuration and display metrics, as detailed in Sections 7.1.1 and 7.1.2, as the fixed-pixel display.
- The device MUST report the same logical density as the fixed-pixel display.
- The device MUST report screen dimensions that are the same as, or very close to, the fixed-pixel display.
For example, a tablet that is 7" diagonal size with a 1024x600 pixel resolution is considered a fixed-pixel large mdpi display implementation. If it contains a video output port that displays at 720p or 1080p the device implementation MUST scale the output so that applications are only executed in a large mdpi window, regardless of whether the fixed-pixel display or video output port is in use.
Variable-Pixel Device Implementations
Variable-pixel device implementations MUST support at least one of 1280x720, 1920x1080, or 3840x2160 (that is, 720p, 1080p, or 4K). Device implementations with variable-pixel displays MUST NOT support any other screen configuration or mode. Device implementations with variable-pixel screens MAY change screen configuration or mode at runtime or boot-time. For example, a user of a set-top box may replace a 720p display with a 1080p display, and the device implementation may adjust accordingly.
Additionally, variable-pixel device implementations MUST report the following configuration buckets for these pixel dimensions:
- 1280x720 (also known as 720p): 'large' screen size, 'tvdpi' (213 dpi) density
- 1920x1080 (also known as 1080p): 'large' screen size, 'xhdpi' (320 dpi) density
- 3840x2160 (also known as 4K): 'large' screen size, 'xxxhdpi' (640 dpi) density
For clarity, device implementations with variable pixel dimensions are restricted to 720p, 1080p, or 4K in Android 4.4, and MUST be configured to report screen size and density buckets as noted above.
7.1.7. Screen Technology
The Android platform includes APIs that allow applications to render rich graphics to the display. Devices MUST support all of these APIs as defined by the Android SDK unless specifically allowed in this document. Specifically:
- Devices MUST support displays capable of rendering 16-bit color graphics and SHOULD support displays capable of 24-bit color graphics.
- Devices MUST support displays capable of rendering animations.
- The display technology used MUST have a pixel aspect ratio (PAR) between 0.9 and 1.1. That is, the pixel aspect ratio MUST be near square (1.0) with a 10% tolerance.
7.1.8. External Displays
Android includes support for secondary display to enable media sharing capabilities and developer APIs for accessing external displays. If a device supports an external display either via a wired, wireless or an embedded additional display connection then the device implementation MUST implement the display manager API as described in the Android SDK documentation [ Resources, 75 ]. Device implementations that support secure video output and are capable of supporting secure surfaces MUST declare support for
Display.FLAG_SECURE . Specifically, device implementations that declare support for
Display.FLAG_SECURE , MUST support HDCP 2.x or higher for Miracast wireless displays or HDCP 1.2 or higher for wired displays. The upstream Android open source implementation includes support for wireless (Miracast) and wired (HDMI) displays that satisfies this requirement.
7.2. Input Devices
- MUST include support for the Input Management Framework (which allows third party developers to create Input Management Engines - ie soft keyboard) as detailed at http://developer.android.com
- MUST provide at least one soft keyboard implementation (regardless of whether a hard keyboard is present)
- MAY include additional soft keyboard implementations
- MAY include a hardware keyboard
- MUST NOT include a hardware keyboard that does not match one of the formats specified in
android.content.res.Configuration.keyboard[ Resources, 40 ] (that is, QWERTY, or 12-key)
7.2.2. Non-touch Navigation
- MAY omit a non-touch navigation option (that is, may omit a trackball, d-pad, or wheel)
- MUST report the correct value for
android.content.res.Configuration.navigation[ Resources, 40 ]
- MUST provide a reasonable alternative user interface mechanism for the selection and editing of text, compatible with Input Management Engines. The upstream Android open source implementation includes a selection mechanism suitable for use with devices that lack non-touch navigation inputs.
7.2.3. Navigation keys
The Home, Recents and Back functions are essential to the Android navigation paradigm. Device implementations MUST make these functions available to the user at all times when running applications. These functions MAY be implemented via dedicated physical buttons (such as mechanical or capacitive touch buttons), or MAY be implemented using dedicated software keys on a distinct portion of the screen, gestures, touch panel, etc. Android supports both implementations. All of these functions MUST be accessible with a single action (eg tap, double-click or gesture) when visible.
The Back and Recents functions SHOULD have a visible button or icon unless hidden together with other navigation functions in full-screen mode. The Home function MUST have a visible button or icon unless hidden together with other navigation functions in full-screen mode.
The Menu function is deprecated in favor of action bar since Android 4.0. Device implementations SHOULD NOT implement a dedicated physical button for the Menu function. If the physical Menu button is implemented and the device is running applications with
targetSdkVersion > 10, the device implementation:
- for a device launching with Android 4.4, MUST display the action overflow button on the action bar when the action bar is visible and the resulting action overflow menu popu is not empty.
- for an existing device launched with an earlier version but upgrading to Android 4.4, SHOULD display the action overflow button on the action bar when the action bar is visible and the resulting action overflow menu popup is not empty.
- MUST NOT modify the position of the action overflow popup displayed by selecting the overflow button in the action bar.
- MAY render the action overflow popup at a modified position on the screen when it is displayed by selecting the physical menu button.
For backwards compatibility, device implementations MUST make available the Menu function to applications when
targetSdkVersion <= 10, either by a phsyical button, a software key or gestures. This Menu function should be presented unless hidden together with other navigation functions.
Android supports Assist action [ Resources, 63 ]. Device implementations MUST make the Assist action available to the user at all times when running applications. The Assist action SHOULD be implemented as a long-press on the Home button or a swipe-up gesture on the software Home key. This function MAY be implemented via another physical button, software key or gestures, but MUST be accessible with a single action (eg tap, double-click or gesture) when other navigation keys are visible.
Device implementations MAY use a distinct portion of the screen to display the navigation keys, but if so, MUST meet these requirements:
- Device implementation 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.
- Device implementations MUST make available a portion of the display to applications that meets the requirements defined in Section 7.1.1 .
- Device implementations MUST display the navigation keys when applications do not specify a system UI mode, or specify
- Device implementations MUST present the navigation keys in an unobtrusive "low profile" (eg. dimmed) mode when applications specify
- Device implementations MUST hide the navigation keys when applications specify
7.2.4. Touchscreen input
Device implementations SHOULD have a pointer input system of some kind (either mouse-like, or touch). However, if a device implementation does not support a pointer input system, it MUST NOT report the
android.hardware.faketouch feature constant. Device implementations that do include a pointer input system:
- SHOULD support fully independently tracked pointers, if the device input system supports multiple pointers
- MUST report the value of
android.content.res.Configuration.touchscreen[ Resources, 40 ] corresponding to the type of the specific touchscreen on the device
Android includes support for a variety of touch screens, touch pads, and fake touch input devices. Touch screen based device implementations are associated with a display [ Resources, 81 ] such that the user has the impression of directly manipulating items on screen. Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated. In contrast, a fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Android 4.0 includes the feature constant
android.hardware.faketouch , which corresponds to a high-fidelity non-touch (that is, pointer-based) input device such as a mouse or trackpad that can adequately emulate touch-based input (including basic gesture support), and indicates that the device supports an emulated subset of touchscreen functionality. Device implementations that declare the fake touch feature MUST meet the fake touch requirements in Section 7.2.5 .
Device implementations MUST report the correct feature corresponding to the type of input used. Device implementations that include a touchscreen (single-touch or better) MUST report the platform feature constant
android.hardware.touchscreen . Device implementations that report the platform feature constant
android.hardware.touchscreen MUST also report the platform feature constant
android.hardware.faketouch . Device implementations that do not include a touchscreen (and rely on a pointer device only) MUST NOT report any touchscreen feature, and MUST report only
android.hardware.faketouch if they meet the fake touch requirements in Section 7.2.5 .
7.2.5. Fake touch input
Device implementations that declare support for
- MUST report the absolute X and Y screen positions of the pointer location and display a visual pointer on the screen [ Resources, 80 ]
- MUST report touch event with the action code [ Resources, 80 ] that specifies the state change that occurs on the pointer going
upon the screen [ Resources, 80 ]
- MUST support pointer
upon an object on the screen, which allows users to emulate tap on an object on the screen
- MUST support pointer
upin the same place on an object on the screen within a time threshold, which allows users to emulate double tap on an object on the screen [ Resources, 80 ]
- MUST support pointer
downon an arbitrary point on the screen, pointer move to any other arbitrary point on the screen, followed by a pointer
up, which allows users to emulate a touch drag
- MUST support pointer
downthen allow users to quickly move the object to a different position on the screen and then pointer
upon the screen, which allows users to fling an object on the screen
Devices that declare support for
android.hardware.faketouch.multitouch.distinct MUST meet the requirements for faketouch above, and MUST also support distinct tracking of two or more independent pointer inputs.
Device implementations MAY omit a microphone. However, if a device implementation omits a microphone, it MUST NOT report the
android.hardware.microphone feature constant, and must implement the audio recording API as no-ops, per Section 7 . Conversely, device implementations that do possess a microphone:
- MUST report the
- SHOULD meet the audio quality requirements in Section 5.4
- SHOULD meet the audio latency requirements in Section 5.5
Android includes APIs for accessing a variety of sensor types. Devices implementations generally MAY omit these sensors, as provided for in the following subsections. If a device includes 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. For example, device implementations:
- MUST accurately report the presence or absence of sensors per the
android.content.pm.PackageManagerclass. [ Resources, 37 ]
- MUST return an accurate list of supported sensors via the
SensorManager.getSensorList()and similar methods
- 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.)
- MUST report all sensor measurements using the relevant International System of Units (ie metric) values for each sensor type as defined in the Android SDK documentation [ Resources, 41 ]
The list above is not comprehensive; the documented behavior of the Android SDK is to be considered authoritative.
Some sensor types are synthetic, meaning they can be derived from data provided by one or more other sensors. (Examples include the orientation sensor, and the linear acceleration sensor.) Device implementations SHOULD implement these sensor types, when they include the prerequisite physical sensors.
Android includes a notion of a "streaming" sensor, which is one that returns data continuously, rather than only when the data changes. Device implementations MUST continuously provide periodic data samples for any API indicated by the Android SDK documentation to be a streaming sensor. Note that the device implementations MUST ensure that the sensor stream must not prevent the device CPU from entering a suspend state or waking up from a suspend state.
Device implementations SHOULD include a 3-axis accelerometer. If a device implementation does include a 3-axis accelerometer, it:
- SHOULD be able to deliver events at 120 Hz or greater. Note that while the accelerometer frequency above is stated as "SHOULD" for Android 4.4, the Compatibility Definition for a future version is planned to change these to "MUST". That is, these standards are optional in Android but will be required in future versions. Existing and new devices that run Android are very strongly encouraged to meet these requirements in Android so they will be able to upgrade to the future platform releases
- MUST comply with the Android sensor coordinate system as detailed in the Android APIs (see [ Resources, 41 ])
- MUST be capable of measuring from freefall up to twice gravity (2g) or more on any three-dimensional vector
- MUST have 8-bits of accuracy or more
- MUST have a standard deviation no greater than 0.05 m/s^2
Device implementations SHOULD include a 3-axis magnetometer (ie compass.) If a device does include a 3-axis magnetometer, it:
- MUST be able to deliver events at 10 Hz or greater
- MUST comply with the Android sensor coordinate system as detailed in the Android APIs (see [ Resources, 41 ]).
- MUST be capable of sampling a range of field strengths adequate to cover the geomagnetic field
- MUST have 8-bits of accuracy or more
- MUST have a standard deviation no greater than 0.5 µT
Device implementations SHOULD include a GPS receiver. If a device implementation does include a GPS receiver, it SHOULD include some form of "assisted GPS" technique to minimize GPS lock-on time.
Device implementations SHOULD include a gyroscope (ie angular change sensor.) Devices SHOULD NOT include a gyroscope sensor unless a 3-axis accelerometer is also included. If a device implementation includes a gyroscope, it:
- MUST be temperature compensated.
- MUST be capable of measuring orientation changes up to 5.5*Pi radians/second (that is, approximately 1,000 degrees per second).
- SHOULD be able to deliver events at 200 Hz or greater. Note that while the gyroscope frequency above is stated as "SHOULD" for Android 4.4, the Compatibility Definition for a future version is planned to change these to "MUST". That is, these standards are optional in Android but will be required in future versions. Existing and new devices that run Android are very strongly encouraged to meet these requirements so they will be able to upgrade to the future platform releases.
- MUST have 12-bits of accuracy or more
- 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.
- MUST have timestamps as close to when the hardware event happened as possible. The constant latency must be removed.
Device implementations MAY include a barometer (ie ambient air pressure sensor.) If a device implementation includes a barometer, it:
- MUST be able to deliver events at 5 Hz or greater
- MUST have adequate precision to enable estimating altitude
- MUST be temperature compensated
Device implementations MAY include an ambient thermometer (ie temperature sensor). If present, it MUST be defined as
SENSOR_TYPE_AMBIENT_TEMPERATURE and it MUST measure the ambient (room) temperature in degrees Celsius.
Device implementations MAY but SHOULD NOT include a CPU temperature sensor. If present, it MUST be defined as
SENSOR_TYPE_TEMPERATURE , it MUST measure the temperature of the device CPU, and it MUST NOT measure any other temperature. Note the
SENSOR_TYPE_TEMPERATURE sensor type was deprecated in Android 4.0.
Device implementations MAY include a photometer (ie ambient light sensor.)
7.3.8. Proximity Sensor
Device implementations MAY include a proximity sensor. If a device implementation does include a proximity sensor, it MUST measure the proximity of an object in the same direction as the screen. That is, the proximity sensor MUST be oriented to detect objects close to the screen, as the primary intent of this sensor type is to detect a phone in use by the user. If a device implementation includes a proximity sensor with any other orientation, it MUST NOT be accessible through this API. If a device implementation has a proximity sensor, it MUST be have 1-bit of accuracy or more.
7.4. Data Connectivity
"Telephony" as used by the Android APIs and this document refers specifically to hardware related to placing voice calls and sending SMS messages via a GSM or CDMA network. While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network. In other words, the Android "telephony" functionality and APIs refer specifically to voice calls and SMS; for instance, device implementations that cannot place calls or send/receive SMS messages MUST NOT report the "android.hardware.telephony" feature or any sub-features, regardless of whether they use a cellular network for data connectivity.
Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones. However, if a device implementation does include GSM or CDMA telephony, it MUST implement full support for the API for that technology. Device implementations that do not include telephony hardware MUST implement the full APIs as no-ops.
7.4.2. IEEE 802.11 (Wi-Fi)
Android device implementations SHOULD include support for one or more forms of 802.11 (b/g/a/n, etc.) If a device implementation does include support for 802.11, it MUST implement the corresponding Android API.
Device implementations MUST implement the multicast API as described in the SDK documentation [ Resources, 62 ]. Device implementations that do include Wi-Fi support MUST support multicast DNS (mDNS). Device implementations MUST NOT filter mDNS packets (22.214.171.124) at any time of operation including when the screen is not in an active state.
126.96.36.199. Wi-Fi Direct
Device implementations SHOULD include support for Wi-Fi direct (Wi-Fi peer-to-peer). If a device implementation does include support for Wi-Fi direct, it MUST implement the corresponding Android API as described in the SDK documentation [ Resources, 68 ]. If a device implementation includes support for Wi-Fi direct, then it:
- MUST support regular Wi-Fi operation
- SHOULD support concurrent Wi-Fi and Wi-Fi Direct operation
188.8.131.52. Wi-Fi Tunneled Direct Link Setup
Device implementations SHOULD include support for Wi-Fi Tunneled Direct Link Setup (TDLS) as described in the Android SDK Documentation [ Resources, 85 ]. If a device implementation does include support for TDLS and TDLS is enabled by the WiFiManager API, the device:
- SHOULD use TDLS only when it is possible AND beneficial.
- SHOULD have some heuristic and NOT use TDLS when its performance might be worse than going through the Wi-Fi access point.
Device implementations SHOULD include a Bluetooth transceiver. Device implementations that do include a Bluetooth transceiver MUST enable the RFCOMM-based Bluetooth API as described in the SDK documentation and declare hardware feature android.hardware.bluetooth [ Resources, 42 ]. Device implementations SHOULD implement relevant Bluetooth profiles, such as A2DP, AVRCP, OBEX, etc. as appropriate for the device.
Device implementations that do include support for Bluetooth GATT (generic attribute profile) to enable communication with Bluetooth Smart or Smart Ready devices MUST enable the GATT-based Bluetooth API as described in the SDK documentation and declare hardware feature android.hardware.bluetooth_le [ Resources, 42 ].
7.4.4. Near-Field Communications
Device implementations SHOULD include a transceiver and related hardware for Near-Field Communications (NFC). If a device implementation does include NFC hardware, then it:
- MUST report the android.hardware.nfc feature from the
android.content.pm.PackageManager.hasSystemFeature()method. [ Resources, 37 ]
- MUST be capable of reading and writing NDEF messages via the following NFC standards:
- 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 6319-4)
- IsoDep (ISO 14443-4)
- NFC Forum Tag Types 1, 2, 3, 4 (defined by the NFC Forum)
- 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:
- SHOULD be capable of reading and writing NDEF messages via the following NFC standards. Note that while the NFC standards below are stated as "SHOULD", the Compatibility Definition for a future version is planned to change these to "MUST". That is, these standards are optional in this version but will be required in future versions. Existing and new devices that run this version of Android are very strongly encouraged to meet these requirements now so they will be able to upgrade to the future platform releases.
- NfcV (ISO 15693)
- MUST be capable of transmitting and receiving data via the following peer-to-peer standards and protocols:
- ISO 18092
- LLCP 1.0 (defined by the NFC Forum)
- SDP 1.0 (defined by the NFC Forum)
- NDEF Push Protocol [ Resources, 43 ]
- SNEP 1.0 (defined by the NFC Forum)
- MUST include support for Android Beam [ Resources, 65 ]:
- MUST implement the SNEP default server. Valid NDEF messages received by the default SNEP server MUST be dispatched to applications using the android.nfc.ACTION_NDEF_DISCOVERED intent. Disabling Android Beam in settings MUST NOT disable dispatch of incoming NDEF message.
- Device implementations MUST honor the android.settings.NFCSHARING_SETTINGS intent to show NFC sharing settings [ Resources, 67 ].
- MUST implement the NPP server. Messages received by the NPP server MUST be processed the same way as the SNEP default server.
- MUST implement a SNEP client and attempt to send outbound P2P NDEF to the default SNEP server when Android Beam is enabled. If no default SNEP server is found then the client MUST attempt to send to an NPP server.
- 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.
- SHOULD use a gesture or on-screen confirmation, such as 'Touch to Beam', before sending outbound P2P NDEF messages.
- SHOULD enable Android Beam by default
- MUST support NFC Connection handover to Bluetooth when the device supports Bluetooth Object Push Profile. Device implementations must support connection handover to Bluetooth when using android.nfc.NfcAdapter.setBeamPushUris, by implementing the "Connection Handover version 1.2" [ Resources, 60 ] and "Bluetooth Secure Simple Pairing Using NFC version 1.0" [ Resources, 61 ] specs from the NFC Forum. Such an implementation MUST implement the handover LLCP service with service name "urn:nfc:sn:handover" for exchanging the handover request/select records over NFC, and it MUST use the Bluetooth Object Push Profile for the actual Bluetooth data transfer. For legacy reasons (to remain compatible with Android 4.1 devices), the implementation SHOULD still accept SNEP GET requests for exchanging the handover request/select records over NFC. However an implementation itself SHOULD NOT send SNEP GET requests for performing connection handover.
- MUST poll for all supported technologies while in NFC discovery mode.
- SHOULD be in NFC discovery mode while the device is awake with the screen active and the lock-screen unlocked.
(Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications cited above.)
Android 4.4 introduces support for NFC Host Card Emulation (HCE) mode. If a device implementation does include an NFC controller capable of HCE and Application ID (AID) routing, then it:
- MUST report the
- MUST support NFC HCE APIs as defined in the Android SDK [ Resources, 90 ]
Additionally, device implementations MAY include reader/writer support for the following MIFARE technologies.
- MIFARE Classic (NXP MF1S503x [ Resources, 44 ], MF1S703x [ Resources, 45 ])
- MIFARE Ultralight (NXP MF0ICU1 [ Resources, 46 ], MF0ICU2 [ Resources, 47 ])
- NDEF on MIFARE Classic (NXP AN130511 [ Resources, 48 ], AN130411 [ Resources, 49 ])
Note that Android includes APIs for these MIFARE types. If a device implementation supports MIFARE in the reader/writer role, it:
- MUST implement the corresponding Android APIs as documented by the Android SDK
- MUST report the feature com.nxp.mifare from the
android.content.pm.PackageManager.hasSystemFeature()method. [ Resources, 37 ] Note that this is not a standard Android feature, and as such does not appear as a constant on the
- MUST NOT implement the corresponding Android APIs nor report the com.nxp.mifare feature unless it also implements general NFC support as described in this section
If a device implementation does not include NFC hardware, it MUST NOT declare the android.hardware.nfc feature from the
android.content.pm.PackageManager.hasSystemFeature() method [ Resources, 37 ], and MUST implement the Android NFC API as a no-op.
As the classes
android.nfc.NdefRecord represent a protocol-independent data representation format, device implementations MUST implement these APIs even if they do not include support for NFC or declare the android.hardware.nfc feature.
7.4.5. Minimum Network Capability
Device implementations 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 200Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet, etc.
Device implementations where a physical networking standard (such as Ethernet) is the primary data connection SHOULD also include support for at least one common wireless data standard, such as 802.11 (Wi-Fi).
Devices MAY implement more than one form of data connectivity.
7.4.6. Sync Settings
Device implementations MUST have the master auto-sync setting on by default so that the method
getMasterSyncAutomatically() returns "true" [ Resources, 88 ].
Device implementations SHOULD include a rear-facing camera, and MAY include a front-facing camera. A rear-facing camera is a camera located on the side of the device opposite the display; that is, it images scenes on the far side of the device, like a traditional camera. A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications.
7.5.1. Rear-Facing Camera
Device implementations SHOULD include a rear-facing camera. If a device implementation includes a rear-facing camera, it:
- MUST have a resolution of at least 2 megapixels
- SHOULD have either hardware auto-focus, or software auto-focus implemented in the camera driver (transparent to application software)
- MAY have fixed-focus or EDOF (extended depth of field) hardware
- MAY include a flash. If the Camera includes a flash, 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 by enabling the
FLASH_MODE_ONattributes of a
Camera.Parametersobject. Note that this constraint does not apply to the device's built-in system camera application, but only to third-party applications using
7.5.2. Front-Facing Camera
Device implementations MAY include a front-facing camera. If a device implementation includes a front-facing camera, it:
- MUST have a resolution of at least VGA (that is, 640x480 pixels)
- MUST NOT use a front-facing camera as the default for the Camera API. That is, the camera API in Android has specific support for front-facing cameras, and device implementations MUST NOT configure the API to to treat a front-facing camera as the default rear-facing camera, even if it is the only camera on the device.
- MAY include features (such as auto-focus, flash, etc.) available to rear-facing cameras as described in Section 7.5.1.
- MUST horizontally reflect (ie mirror) the stream displayed by an app in a CameraPreview, as follows:
- If the device implementation is capable of being rotated by user (such as automatically via an accelerometer or manually via user input), the camera preview MUST be mirrored horizontally relative to the device's current orientation.
- If the current application has explicitly requested that the Camera display be rotated via a call to the
android.hardware.Camera.setDisplayOrientation()[ Resources, 50 ] method, the camera preview MUST be mirrored horizontally relative to the orientation specified by the application.
- Otherwise, the preview MUST be mirrored along the device's default horizontal axis.
- MUST mirror the image displayed by the postview in the same manner as the camera preview image stream. (If the device implementation does not support postview, this requirement obviously does not apply.)
- MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage
7.5.3. Camera API Behavior
Device implementations MUST implement the following behaviors for the camera-related APIs, for both front- and rear-facing cameras:
- If an application has never called
android.hardware.Camera.Parameters.setPreviewFormat(int), then the device MUST use
android.hardware.PixelFormat.YCbCr_420_SPfor preview data provided to application callbacks.
- If an application registers an
android.hardware.Camera.PreviewCallbackinstance and the system calls the
onPreviewFrame()method when the preview format is YCbCr_420_SP, the data in the
onPreviewFrame()must further be in the NV21 encoding format. That is, NV21 MUST be the default.
- Device implementations MUST support the YV12 format (as denoted by the
android.graphics.ImageFormat.YV12constant) for camera previews for both front- and rear-facing cameras. (The hardware video encoder and camera may use any native pixel format, but the device implementation MUST support conversion to YV12.)
Device implementations MUST implement the full Camera API included in the Android SDK documentation [ Resources, 51 ]), regardless of whether the device includes hardware autofocus or other capabilities. For instance, cameras that lack autofocus MUST still call any registered
android.hardware.Camera.AutoFocusCallback instances (even though this has no relevance to a non-autofocus camera.) Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks must still be "faked" as described.
Device implementations MUST recognize and honor each parameter name defined as a constant on the
android.hardware.Camera.Parameters class, if the underlying hardware supports the feature. If the device hardware does not support a feature, the API must behave as documented. 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 . That is, device implementations MUST support all standard Camera parameters if the hardware allows, and MUST NOT support custom Camera parameter types. For instance, device implementations that support image capture using high dynamic range (HDR) imaging techniques MUST support camera parameter
Camera.SCENE_MODE_HDR [ Resources, 78 ]).
Device implementations 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.
Device implementations 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.
7.5.4. Camera Orientation
Both front- and rear-facing cameras, if present, MUST be oriented so that the long dimension of the camera aligns with the screen's long dimension. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. This applies regardless of the device's natural orientation; that is, it applies to landscape-primary devices as well as portrait-primary devices.
7.6. Memory and Storage
7.6.1. Minimum Memory and Storage
Device implementations MUST have at least 340MB of memory available to the kernel and userspace. The 340MB MUST be in addition to any memory dedicated to hardware components such as radio, video, and so on that is not under the kernel's control.
Device implementations with less than 512MB of memory available to the kernel and userspace MUST return the value "true" for
Device implementations MUST have at least 1GB of non-volatile storage available for application private data. That is, the
/data partition MUST be at least 1GB. Device implementations that run Android are very strongly encouraged to have at least 2GB of non-volatile storage for application private data so they will be able to upgrade to the future platform releases.
The Android APIs include a Download Manager that applications may use to download data files [ Resources, 56 ]. The device implementation of the Download Manager MUST be capable of downloading individual files of at least 100MB in size to the default "cache" location.
7.6.2. Shared External Storage
Device implementations MUST offer shared storage for applications. The shared storage provided MUST be at least 1GB in size.
Device implementations MUST be configured with shared storage mounted by default, "out of the box". If the shared storage is not mounted on the Linux path
/sdcard , then the device MUST include a Linux symbolic link from
/sdcard to the actual mount point.
Device implementations MUST enforce as documented the
android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage. Shared storage MUST otherwise be writable by any application that obtains that permission.
Device implementations MAY have hardware for user-accessible removable storage, such as a Secure Digital card. Alternatively, device implementations MAY allocate internal (non-removable) storage as shared storage for apps. The upstream Android Open Source Project includes an implementation that uses internal device storage for shared external storage APIs; device implementations SHOULD use this configuration and software implementation.
Regardless of the form of shared storage used, device implementations MUST provide some mechanism to access the contents of shared storage from a host computer, such as USB mass storage (UMS) or Media Transfer Protocol (MTP). Device implementations MAY use USB mass storage, but SHOULD use Media Transfer Protocol. If the device implementation supports Media Transfer Protocol:
- The device implementation SHOULD be compatible with the reference Android MTP host, Android File Transfer [ Resources, 57 ].
- The device implementation SHOULD report a USB device class of
- The device implementation SHOULD report a USB interface name of 'MTP'.
If the device implementation lacks USB ports, it MUST provide a host computer with access to the contents of shared storage by some other means, such as a network file system.
It is illustrative to consider two common examples. If a device implementation includes an SD card slot to satisfy the shared storage requirement, a FAT-formatted SD card 1GB in size or larger MUST be included with the device as sold to users, and MUST be mounted by default. Alternatively, if a device implementation uses internal fixed storage to satisfy this requirement, that storage MUST be 1GB in size or larger and mounted on
/sdcard MUST be a symbolic link to the physical location if it is mounted elsewhere.)
Device implementations that include multiple shared storage paths (such as both an SD card slot and shared internal storage) MUST NOT allow Android applications to write to the secondary external storage, except for their package-specific directories on the secondary external storage, but SHOULD expose content from both storage paths transparently through Android's media scanner service and android.provider.MediaStore.
Device implementations SHOULD include a USB client port, and SHOULD include a USB host port.
If a device implementation includes a USB client port:
- the port MUST be connectable to a USB host with a standard USB-A port
- the port SHOULD use the micro USB form factor on the device side. Existing and new devices that run Android are very strongly encouraged to meet these requirements in Android so they will be able to upgrade to the future platform releases
- the port SHOULD be centered in the middle of an edge. Device implementations SHOULD either locate the port 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 draws correctly when the device is oriented with the port at bottom. Existing and new devices that run Androidare very strongly encouraged to meet these requirements in Android so they will be able to upgrade to future platform releases.
- if the device has other ports (such as a non-USB charging port) it SHOULD be on the same edge as the micro-USB port
- it MUST allow a host connected to the device to access the contents of the shared storage volume using either USB mass storage or Media Transfer Protocol
- it MUST implement the Android Open Accessory API and specification as documented in the Android SDK documentation, and MUST declare support for the hardware feature
android.hardware.usb.accessory[ Resources, 52 ]
- it MUST implement the USB audio class as documented in the Android SDK documentation [ Resources, 66 ]
- it SHOULD implement support for USB battery charging specification [ Resources, 64 ] Existing and new devices that run Android are very strongly encouraged to meet these requirements so they will be able to upgrade to the future platform releases
- The value of iSerialNumber in USB standard device descriptor MUST be equal to the value of android.os.Build.SERIAL.
If a device implementation includes a USB host port:
- it MAY use a non-standard port form factor, but if so MUST ship with a cable or cables adapting the port to standard USB-A
- it 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[ Resources, 53 ]
Device implementations MUST implement the Android Debug Bridge. If a device implementation omits a USB client port, it MUST implement the Android Debug Bridge via local-area network (such as Ethernet or 802.11)
8. Performance Compatibility
Device implementations MUST meet the key performance metrics of an Android- compatible device defined in the table below:
|Application Launch Time|| The following applications should launch within the specified time.||The launch time is measured as the total time to complete loading the default activity for the application, including the time it takes to start the Linux process, load the Android package into the Dalvik VM, and call onCreate.|
|Simultaneous Applications||When multiple applications have been launched, re-launching an already-running application after it has been launched must take less than the original launch time.|
9. Security Model Compatibility
Device implementations MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs [ Resources, 54 ] in the Android developer documentation. Device implementations MUST support installation of self-signed applications without requiring any additional permissions/certificates from any third parties/authorities. Specifically, compatible devices MUST support the security mechanisms described in the follow sub-sections.
Device implementations MUST support the Android permissions model as defined in the Android developer documentation [ Resources, 54 ]. Specifically, implementations MUST enforce each permission defined as described in the SDK documentation; no permissions may be omitted, altered, or ignored. Implementations MAY add additional permissions, provided the new permission ID strings are not in the android.* namespace.
9.2. UID and Process Isolation
Device implementations MUST support the Android application sandbox model, in which each application runs as a unique Unix-style UID and in a separate process. Device implementations 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 [ Resources, 54 ].
9.3. Filesystem Permissions
Device implementations MUST support the Android file access permissions model as defined in the Security and Permissions reference [ Resources, 54 ].
9.4. Alternate Execution Environments
Device implementations MAY include runtime environments that execute applications using some other software or technology than the Dalvik virtual machine or native code. However, such alternate execution environments MUST NOT compromise the Android security model or the security of installed Android applications, as described in this section.
Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in Section 9.
Alternate runtimes MUST NOT be granted access to resources protected by permissions not requested in the runtime's AndroidManifest.xml file via the
Alternate runtimes MUST NOT permit applications to make use of features protected by Android permissions restricted to system applications.
Alternate runtimes MUST abide by the Android sandbox model. Specifically:
- Alternate runtimes SHOULD install apps via the PackageManager into separate Android sandboxes (that is, Linux user IDs, etc.)
- Alternate runtimes MAY provide a single Android sandbox shared by all applications using the alternate runtime
- Alternate runtimes and installed applications using an alternate runtime MUST NOT reuse the sandbox of any other app installed on the device, except through the standard Android mechanisms of shared user ID and signing certificate
- Alternate runtimes MUST NOT launch with, grant, or be granted access to the sandboxes corresponding to other Android applications
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.
The .apk files of alternate runtimes MAY be included in the system image of a device implementation, but MUST be signed with a key distinct from the key used to sign other applications included with the device implementation.
When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application. That is, if 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. If 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.
9.5. Multi-User Support
Android includes support for multiple users and provides support for full user isolation [ Resources, 70 ].
Device implementations MUST meet these requirements related to multi-user support [ Resources, 71 ]:
- As the behavior of the telephony APIs on devices with multiple users is currently undefined, device implementations that declare android.hardware.telephony MUST NOT enable multi-user support.
- Device implementations 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 [Resources, 54]
- Android includes support for restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments. Device implementations that include support for multiple users MUST include support for restricted profiles. The upstream Android Open Source Project includes an implementation that satisfies this requirement.
Each user instance on an Android device MUST have separate and isolated external storage directories. Device implementations MAY store multiple users' data on the same volume or filesystem. However, the device implementation MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to data owned by any other user. Note that removable media, such as SD card slots, can allow one user to access another's data by means of a host PC. For this reason, device implementations that use removable media for the external storage APIs MUST encrypt the contents of the SD card if multi-user is enabled using a key stored only on non-removable media accessible only to the system. As this will make the media unreadable by a host PC, device implementations will be required to switch to MTP or a similar system to provide host PCs with access to the current user's data. Accordingly, device implementations MAY but SHOULD NOT enable multi-user if they use removable media [ Resources, 72 ] for primary external storage.
9.6. Premium SMS Warning
Android includes support for warning users for any outgoing premium SMS message [ Resources, 73 ] . Premium SMS messages are text messages sent to a service registered with a carrier that may incur a charge to the user. Device implementations that declare support for
android.hardware.telephony 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. The upstream Android Open Source Project provides an implementation that satisfies this requirement.
9.7. Kernel Security Features
The Android Sandbox includes features that can use the Security-Enhanced Linux (SELinux) mandatory access control (MAC) system and other security features in the Linux kernel. SELinux or any other security features, if implemented below the Android framework:
- MUST maintain compatibility with existing applications
- MUST not have a visible user interface, even when violations are detected
- SHOULD NOT be user or developer configurable
If any API for configuration of policy is exposed to an application that can affect another application (such as a Device Administration API), the API MUST NOT allow configurations that break compatibility.
Devices MUST implement SELinux and meet the following requirements, which are satisfied by the reference implementation in the upstream Android Open Source Project.
- it MUST support a SELinux policy that allows the SELinux mode to be set on a per-domain basis with:
- domains that are in enforcing mode in the upstream Android Open Source implementation (such as installd, netd, and vold) MUST be in enforcing mode
- domain(s) for third-party applications SHOULD remain in permissive mode to ensure continued compatibility
- it SHOULD load policy from
/sepolicyfile on the device
- it MUST support dynamic updates of the SELinux policy file without requiring a system image update
- it MUST log any policy violations without breaking applications or affecting system behavior
Device implementations SHOULD retain the default SELinux policy provided in the upstream Android Open Source Project, until they have first audited their additions to the SELinux policy. Device implementations MUST be compatible with the upstream Android Open Source Project.
If the device implements functionality in the system that captures the contents displayed on the screen and/or records the audio stream played on the device, it MUST continuously notify the user whenever this functionality is enabled and actively capturing/recording.
9.9. Full-Disk Encryption
IF the device has lockscreen, the device MUST support full-disk encryption.
10. Software Compatibility Testing
Device implementations MUST pass all tests described in this section.
However, note that no software test package is fully comprehensive. For this reason, device implementers are very strongly encouraged to make the minimum number of changes as possible to the reference and preferred implementation of Android available from the Android Open Source Project. This will minimize the risk of introducing bugs that create incompatibilities requiring rework and potential device updates.
10.1. Compatibility Test Suite
Device implementations MUST pass the Android Compatibility Test Suite (CTS) [ Resources, 2 ] available from the Android Open Source Project, using the final shipping software on the device. Additionally, device implementers SHOULD use the reference implementation in the Android Open Source tree as much as possible, and MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code.
The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 4.4. Device implementations MUST pass the latest CTS version available at the time the device software is completed.
10.2. CTS Verifier
Device implementations MUST correctly execute all applicable cases in the CTS Verifier. The CTS Verifier is included with the Compatibility Test Suite, and is intended to be run by a human operator to test functionality that cannot be tested by an automated system, such as correct functioning of a camera and sensors.
The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional. Device implementations MUST pass all tests for hardware which they possess; for instance, if a device possesses an accelerometer, it MUST correctly execute the Accelerometer test case in the CTS Verifier. Test cases for features noted as optional by this Compatibility Definition Document MAY be skipped or omitted.
Every device and every build MUST correctly run the CTS Verifier, as noted above. However, since many builds are very similar, device implementers are not expected to explicitly run the CTS Verifier on builds that differ only in trivial ways. Specifically, device implementations that differ from an implementation that has passed the CTS Verifier only by the set of included locales, branding, etc. MAY omit the CTS Verifier test.
10.3. Reference Applications
Device implementers MUST test implementation compatibility using the following open source applications:
- The "Apps for Android" applications [ Resources, 55 ]
- Replica Island (available in Google Play Store)
Each app above MUST launch and behave correctly on the implementation, for the implementation to be considered compatible.
11. Updatable Software
Device implementations MUST include a mechanism to replace the entirety of the system software. The mechanism need not perform "live" upgrades - that is, a device restart MAY be required.
Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement:
- 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
The update mechanism used MUST support updates without wiping user data. That is, the update mechanism MUST preserve application private data and application shared data. Note that the upstream Android software includes an update mechanism that satisfies this requirement.
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, the device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.
12. Document Changelog
The following table contains a summary of the changes to the Compatibility Definition in this release.
|Section(s)||Summary of change|
|3.2.2. Build Parameters||Revised descriptions of BRAND, DEVICE, and PRODUCT. SERIAL is now required.|
|184.108.40.206. Default App Settings||New section that adds requirement to comply with new default application settings|
|3.3.1 Application Binary Interfaces|| Clarified allowed values for the |
|3.4.1. WebView Compatibility||Added Chromium as required WebView implementation.|
|3.7. Virtual Machine Compatibility||Added requirement for xxhdpi and 400dpi screen densities.|
|3.8.6. Themes||Updated to reflect use of translucent system bars.|
|3.8.12.地點||New section that adds requirement location settings be centralized.|
|3.8.13. Unicode||New section that adds requirement for emoji support.|
|3.9. Device Administration||Noted preinstalled administrative applications cannot be the default Device Owner application.|
|5.1. Media Codecs||Added VP9 decoder requirement. Added recommended specification for hardware VP8 codecs.|
|5.3. Video Decoding||Added VP9. Added recommendation for dynamic resolution switching.|
|5.4. Audio Recording|| Added |
|6.2.1 Experimental||New section that introduces the ART runtime and requires Dalvik as the default runtime.|
|7.1.1. Screen Configuration||Replaced 1.85 aspect ratio with 1.86. Added 400dpi screen density.|
|7.1.6. Screen Types||Added 640 dpi (4K) resolution configuration.|
|7.2.3. Navigation keys||Added Recents function as essential; demoted Menu function in priority.|
|7.3.6. Thermometer||Added SENSOR_TYPE_AMBIENT_TEMPERATURE as recommended thermometer.|
|220.127.116.11. Wi-Fi Tunneled Direct Link Setup||New section that adds support for Wi-Fi Tunneled Direct Link Setup (TDLS).|
|7.4.4. Near-Field Communications||Added Host Card Emulation (HCE) as a requirement. Replaced SNEP GET with Logical Link Control Protocol (LLCP) and added the Bluetooth Object Push Profile as a requirement.|
|7.4.6. Sync Settings||New section that adds requirement auto-sync data be enabled by default.|
|7.6.1. Minimum Memory and Storage|| Added |
|7.6.2. Shared "External" Storage||Editorial fixes such as change of section name, and moved text that fits in this section from section 9.5. Noted applications may write to their package-specific directories on secondary external storage.|
|7.7. USB||Added requirement all devices report a USB serial number.|
|9.5. Multi-User Support||Moved non multi-user specific text to section 7.6.2.|
|9.7. Kernel Security Features||Rewritten to note switch of SELinux to enforcing mode and requirement SELinux output not be rendered in the user interface.|
|9.8. Privacy||New section that adds requirement audio and video recording must trigger continuous notifications to the user.|
|9.9. Full-Disk Encryption||New section that adds requirement devices with lockscreen support full-disk encryption.|
|12. Document Changelog||New section that summarizes changes in the CDD by section.|
13. Contact Us
You can contact the document authors at firstname.lastname@example.org for clarifications and to bring up any issues that you think the document does not cover.