自 2025 年 3 月 27 日起，我們建議您使用 android-latest-release 而非 aosp-main 建構及貢獻 AOSP。詳情請參閱「Android 開放原始碼計畫變更」。
相容性常見問題 (FAQ)
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本文件將解答 Android 相容性方面的常見問題。
哪些類型的裝置可與 Android 相容？
Android 軟體可移植至多種不同裝置，包括無法正常執行第三方應用程式的裝置。Android 相容性定義說明文件 (CDD) 會列出視為相容的特定裝置設定。
舉例來說，雖然 Android 原始碼可移植至沒有相機的手機上執行，但 CDD 規定所有手機都必須有相機。這可讓開發人員在編寫應用程式時，使用一致的功能組合。
CDD 會持續演進，反映市場現況。舉例來說，CDD 1.6 版僅支援手機。不過，2.1 版允許裝置省略電話硬體，讓平板電腦式音樂播放器等非手機裝置也能相容。在 Google 進行這些變更的同時，我們也強化了 Google Play 的功能，讓開發人員可以繼續控管應用程式可供下載的位置。以電話服務為例，管理簡訊的應用程式在媒體播放器上並無用處，因此 Google Play 允許開發人員將該應用程式限制在手機裝置上。
如果我的裝置相容，是否會自動取得 Google Play 和品牌資訊存取權？
否。存取權並非自動授予。Google Play 是由 Google 營運的服務。取得 Google Play 軟體和品牌授權的先決條件，就是必須達到相容性。裝置符合 Android 相容性要求後，您應填寫 授權 Google 行動服務中的聯絡表單，以便取得 Google Play 存取權。
是否必須符合相容性規定？
否。您可以選擇是否加入 Android 相容性計畫。Android 原始碼是開放的，因此任何人都可以使用它建構任何類型的裝置。不過，如果您想在產品中使用 Android 名稱，或是想存取 Google Play，請務必確認裝置相容性。
相容性認證費用是多少？
為裝置取得 Android 相容性無須付費。Compatibility Test Suite 是開放原始碼，任何人皆可使用進行裝置測試。
誰會決定相容性定義？
Google 負責 Android 平台和產品的整體方向，因此會維護每個版本的相容性定義說明文件 (CDD)。Google 會與提供意見的各種原始設備製造商 (OEM) 協商，為新版 Android 草擬 CDD。
每個 Android 版本支援新裝置的時間長度為何？
Android 的程式碼是開放原始碼，因此 Google 無法禁止使用者使用任何版本啟動裝置。相反地，Google 選擇不授權 Google Play 用戶端軟體，以便在舊版上使用。這可讓任何人繼續提供過時的 Android 版本，但這些裝置無法使用 Android 名稱，且會在 Android 應用程式生態系統之外存在，就像是無法相容的裝置一樣。
裝置是否可以使用不同的使用者介面，且仍與應用程式相容？
Android 相容性計畫會判斷裝置是否可執行第三方應用程式。裝置隨附的使用者介面元件 (例如主畫面、撥號程式和配色方案) 通常不會對第三方應用程式造成太大影響。因此，裝置建構人員可以自由自訂使用者介面。相容性定義文件會限制原始設備製造商 (OEM) 可在哪些方面變更系統使用者介面，以免影響第三方應用程式。
何時會發布新版 Android 的相容性定義？
Google 的目標是在對應的 Android 平台版本趨於一致且允許時，發布新版 Android 相容性定義說明文件 (CDD)。雖然 Google 無法在第一款搭載該軟體的旗艦機型出貨前，發布 Android 軟體版本的最終 CDD 草稿，但最終 CDD 一律會在第一款裝置出貨後發布。不過，Google 會在可行情況下發布 CDD 草稿。
如何驗證裝置製造商的相容性聲明？
我們沒有針對 Android 裝置相容性的驗證程序。不過，如果裝置要納入 Google Play，Google 通常會先驗證裝置的相容性，再同意授權 Google Play 用戶端軟體。
如果宣稱相容的裝置日後發現有相容性問題，會發生什麼情況？
通常，Google 會要求您發布更新的系統映像檔，以便修正任何相容性問題。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間：2025-06-12 (世界標準時間)。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-06-12 (世界標準時間)。"],[],[],null,["# Compatibility Frequently Asked Questions (FAQ)\n\nThis document contains answers to general questions about Android compatibility.\n\nWhat types of devices can be Android-compatible?\n------------------------------------------------\n\nAndroid software can be ported to many different devices,\nincluding some on which third-party apps don't run properly. The\n[Android Compatibility Definition Document (CDD)](/docs/compatibility/cdd)\nspells out the specific device configurations that are considered compatible.\n\nFor example, though the Android source code could be ported to run on a\nphone that doesn't have a camera, the CDD requires all phones to have a camera.\nThis allows developers to rely on a consistent set of capabilities when writing\ntheir apps.\n\nThe CDD continues to evolve to reflect market realities. For example,\nversion 1.6 of the CDD supports only cell phones. But version 2.1 allows devices\nto omit telephony hardware, enabling non-phone devices such as tablet-style\nmusic players to be compatible. As Google makes these changes, Google also\naugments Google Play to allow developers to retain control over where\ntheir apps are available. To continue the telephony example, an app that\nmanages SMS text messages isn't useful on a media player, so Google\nPlay allows the developer to restrict that app exclusively to phone devices.\n\nIf my device is compatible, does it automatically have access to Google Play and branding?\n------------------------------------------------------------------------------------------\n\nNo. Access isn't automatic. Google Play is a service operated by Google.\nAchieving compatibility is a prerequisite for obtaining access to the\nGoogle Play software and branding. After a device is\n[qualified as an Android-compatible device](/docs/compatibility/overview#build),\nyou should complete the contact form included in\n[licensing Google Mobile Services](/docs/setup/community#for-business-inquiries)\nto seek access to Google Play.\n\nIs compatibility mandatory?\n---------------------------\n\nNo. The Android Compatibility Program is optional. The Android source\ncode is open, so anyone can use it to build any kind of device. However, if\nyou want to use the Android name with your product, or want access\nto Google Play, you must first\n[ensure that your device is compatible](/docs/compatibility/overview#build).\n\nHow much does compatibility certification cost?\n-----------------------------------------------\n\nThere's no cost to obtain Android compatibility for a device. The\nCompatibility Test Suite is open source and available to anyone for device\ntesting.\n\nWho determines the compatibility definition?\n--------------------------------------------\n\nGoogle is responsible for the overall direction of Android as a\nplatform and product, so Google maintains the Compatibility Definition Document\n(CDD) for each release. Google drafts the CDD for a new Android version in\nconsultation with various OEMs who provide input.\n\nHow long is each Android version supported for new devices?\n-----------------------------------------------------------\n\nAndroid's code is open source, so Google can't prevent someone from using any\nversion to launch a device. Instead, Google chooses not to license the\nGoogle Play client software for use on obsolete versions. This allows anyone to\ncontinue to ship obsolete versions of Android, but those devices can't use the\nAndroid name and exist outside of the Android apps ecosystem, just as if they\nweren't compatible.\n\nCan a device have a different user interface and still be compatible?\n---------------------------------------------------------------------\n\nThe Android Compatibility Program determines whether a device can run\nthird-party apps. The user interface components shipped with a\ndevice (such as home screen, dialer, and color scheme) don't\ngenerally have much effect on third-party apps. As such, device builders are\nfree to customize the user interface. The Compatibility\nDefinition Document restricts the degree to which OEMs are permitted to alter\nthe system user interface for areas that impact third-party apps.\n\nWhen are compatibility definitions released for new Android versions?\n---------------------------------------------------------------------\n\nGoogle's goal is to release a new version of the Android Compatibility\nDefinition Document (CDD) when the corresponding Android platform version has\nconverged enough to permit it. While Google can't release a final draft of a CDD\nfor an Android software version before the first flagship device ships with\nthat software, final CDDs are always released after the first device.\nHowever, wherever practical Google releases draft versions of CDDs.\n\nHow are device manufacturers' compatibility claims validated?\n-------------------------------------------------------------\n\nThere is no validation process for Android-powered device compatibility.\nHowever, if the device is to include Google Play, Google typically validates\nthe device for compatibility before agreeing to license the Google Play\nclient software.\n\nWhat happens if a device that claims compatibility is later found to have compatibility problems?\n-------------------------------------------------------------------------------------------------\n\nTypically, Google's asks you to release updated system images that fix any\ncompatibility problems."]]
