功能與 API

Android 16 為開發人員推出了強大的新功能和 API。以下各節將摘要說明這些功能，協助您開始使用相關 API。

此外，也請查看平台變更可能對應用程式造成的影響。詳情請參閱下列頁面：

• 應用程式指定 Android 16 為目標版本時會涉及的行為變更
• 影響所有應用程式的行為變更，無論 targetSdkVersion 為何。

核心功能

Android 包含可擴充 Android 系統核心功能的新 API。

2025 年將發布兩項 Android API

• This preview is for the next major release of Android with a planned launch in Q2 of 2025. This release is similar to all of our API releases in the past, where we can have planned behavior changes that are often tied to a targetSdkVersion.
• We're planning the major release a quarter earlier (Q2 rather than Q3 in prior years) to better align with the schedule of device launches across our ecosystem, so more devices can get the major release of Android sooner. With the major release coming in Q2, you'll need to do your annual compatibility testing a few months earlier than in previous years to make sure your apps are ready.
• We plan to have another release in Q4 of 2025 which also will include new developer APIs. The Q2 major release will be the only release in 2025 to include planned behavior changes that could affect apps.

In addition to new developer APIs, the Q4 minor release will pick up feature updates, optimizations, and bug fixes; it will not include any app-impacting behavior changes.

We'll continue to have quarterly Android releases. The Q1 and Q3 updates in-between the API releases will provide incremental updates to help ensure continuous quality. We're actively working with our device partners to bring the Q2 release to as many devices as possible.

Using new APIs with major and minor releases

Guarding a code block with a check for API level is done today using the SDK_INT constant with VERSION_CODES. This will continue to be supported for major Android releases.

if (SDK_INT >= VERSION_CODES.BAKLAVA) {
  // Use APIs introduced in Android 16
}

The new SDK_INT_FULL constant can be used for API checks against both major and minor versions with the new VERSION_CODES_FULL enumeration.

if (SDK_INT_FULL >= VERSION_CODES_FULL.[MAJOR or MINOR RELEASE]) {
  // Use APIs introduced in a major or minor release
}

You can also use the Build.getMinorSdkVersion() method to get just the minor SDK version.

val minorSdkVersion = Build.getMinorSdkVersion(VERSION_CODES_FULL.BAKLAVA)

These APIs have not yet been finalized and are subject to change, so please send us feedback if you have any concerns.

使用者體驗和系統 UI

Android 16 可讓應用程式開發人員和使用者進一步控管及彈性設定裝置，以符合自身需求。

以進度為主的通知

Android 16 推出以進度為主的通知，協助使用者順暢追蹤使用者啟動的端對端歷程。

Notification.ProgressStyle 是一種新的通知樣式，可讓您建立以進度為主的通知。主要用途包括共乘、外送和導航。在 Notification.ProgressStyle 類別中，您可以使用點和區隔，表示使用者歷程中的狀態和里程碑。

詳情請參閱「以進度為主軸的通知」說明文件。

在螢幕鎖定畫面上顯示以進度為主的通知。

通知欄中顯示以進度為主的通知。

預測返回更新

Android 16 adds new APIs to help you enable predictive back system animations in gesture navigation such as the back-to-home animation. Registering the onBackInvokedCallback with the new PRIORITY_SYSTEM_NAVIGATION_OBSERVER allows your app to receive the regular onBackInvoked call whenever the system handles a back navigation without impacting the normal back navigation flow.

Android 16 additionally adds the finishAndRemoveTaskCallback() and moveTaskToBackCallback. By registering these callbacks with the OnBackInvokedDispatcher, the system can trigger specific behaviors and play corresponding ahead-of-time animations when the back gesture is invoked.

更豐富的觸覺回饋

自推出以來，Android 就提供觸覺感應致動器控制項。

Android 11 新增了對更複雜的觸覺效果支援，進階的致動器可透過裝置定義語義原始類型的 VibrationEffect.Compositions 支援此類效果。

Android 16 新增觸覺 API，讓應用程式定義觸覺效果的振幅和頻率曲線，同時抽象化裝置功能之間的差異。

開發人員工作效率和工具

我們致力於提升您的工作效率，因此大部分工作都圍繞著 Android Studio、Jetpack Compose 和 Android Jetpack 程式庫等工具進行，但我們也持續在平台中尋找各種方法，協助您實現願景。

動態桌布的內容處理方式

In Android 16, the live wallpaper framework is gaining a new content API to address the challenges of dynamic, user-driven wallpapers. Currently, live wallpapers incorporating user-provided content require complex, service-specific implementations. Android 16 introduces WallpaperDescription and WallpaperInstance. WallpaperDescription lets you identify distinct instances of a live wallpaper from the same service. For example, a wallpaper that has instances on both the home screen and on the lock screen may have unique content in both places. The wallpaper picker and WallpaperManager use this metadata to better present wallpapers to users, streamlining the process for you to create diverse and personalized live wallpaper experiences.

效能和電池

Android 16 導入的 API 可協助您收集應用程式的深入分析資訊。

系統觸發的剖析

ProfilingManager 已在 Android 15 中新增，讓應用程式能夠在外部公開裝置上使用 Perfetto 要求收集分析資料。不過，由於這項剖析作業必須從應用程式啟動，因此應用程式很難或無法擷取啟動或 ANR 等重要流程。

為協助您完成這項工作，Android 16 為 ProfilingManager 導入系統觸發的剖析功能。應用程式可以註冊對特定觸發事件 (例如冷啟動 reportFullyDrawn 或 ANR) 的追蹤記錄興趣，系統就會代替應用程式啟動及停止追蹤記錄。追蹤記錄完成後，結果會傳送至應用程式的資料目錄。

在 ApplicationStartInfo 中啟動元件

ApplicationStartInfo 已在 Android 15 中新增，可讓應用程式查看程序啟動原因、啟動類型、啟動時間、節流和其他實用的診斷資料。Android 16 新增了 getStartComponent()，用於區分觸發啟動的元件類型，這有助於最佳化應用程式的啟動流程。

更深入瞭解工作

JobScheduler#getPendingJobReason() API 會傳回工作可能處於待處理狀態的原因。不過，工作可能會因多種原因而處於待處理狀態。

在 Android 16 中，我們推出了全新的 API JobScheduler#getPendingJobReasons(int jobId)，可傳回工作處於待處理狀態的多種原因，包括開發人員設定的明確限制，以及系統設定的隱含限制。

我們也推出 JobScheduler#getPendingJobReasonsHistory(int jobId)，可傳回最新約束條件變更的清單。

建議您使用 API 來偵測工作未執行的原因，特別是當您發現特定工作成功率降低，或特定工作完成時間延遲時，就需要進行偵錯。例如，在背景更新小工具時發生錯誤，或是在應用程式啟動前無法呼叫預先擷取工作。

這也能協助您進一步瞭解，某些工作是否因系統定義的限制而無法完成，而非明確設定的限制。

自動調整刷新率

Adaptive refresh rate (ARR), introduced in Android 15, enables the display refresh rate on supported hardware to adapt to the content frame rate using discrete VSync steps. This reduces power consumption while eliminating the need for potentially jank-inducing mode-switching.

Android 16 introduces hasArrSupport() and getSuggestedFrameRate(int) while restoring getSupportedRefreshRates() to make it easier for your apps to take advantage of ARR. RecyclerView 1.4 internally supports ARR when it is settling from a fling or smooth scroll, and we're continuing our work to add ARR support into more Jetpack libraries. This frame rate article covers many of the APIs you can use to set the frame rate so that your app can directly use ARR.

ADPF 中的 Headroom API

SystemHealthManager 引進 getCpuHeadroom 和 getGpuHeadroom API，旨在為遊戲和資源密集型應用程式提供可用 CPU 和 GPU 資源的預估值。這些方法可讓您評估應用程式或遊戲如何最佳化系統健康狀況，尤其是與其他Android 動態效能架構 (ADPF) API 搭配使用時，這些 API 可偵測熱控調節。

在支援的裝置上使用 CpuHeadroomParams 和 GpuHeadroomParams，您可以自訂用於計算預留空間的時間視窗，並選擇平均或最低資源可用性。這麼做可以協助您相應減少 CPU 或 GPU 資源使用量，進而提供更優質的使用者體驗和更長的電池續航力。

無障礙設定

Android 16 新增了無障礙 API 和功能，可協助您為所有使用者提供應用程式。

改良的無障礙 API

Android 16 adds additional APIs to enhance UI semantics that help improve consistency for users that rely on accessibility services, such as TalkBack.

Outline text for maximum text contrast

Users with low vision often have reduced contrast sensitivity, making it challenging to distinguish objects from their backgrounds. To help these users, Android 16 introduces outline text, replacing high contrast text, which draws a larger contrasting area around text to greatly improve legibility.

Android 16 contains new AccessibilityManager APIs to let your apps check or register a listener to see if this mode is enabled. This is primarily for UI Toolkits like Compose to offer a similar visual experience. If you maintain a UI Toolkit library or your app performs custom text rendering that bypasses the android.text.Layout class then you can use this to know when outline text is enabled.

Duration added to TtsSpan

Android 16 extends TtsSpan with a TYPE_DURATION, consisting of ARG_HOURS, ARG_MINUTES, and ARG_SECONDS. This lets you directly annotate time duration, ensuring accurate and consistent text-to-speech output with services like TalkBack.

Support elements with multiple labels

Android currently allows UI elements to derive their accessibility label from another, and now offers the ability for multiple labels to be associated, a common scenario in web content. By introducing a list-based API within AccessibilityNodeInfo, Android can directly support these multi-label relationships. As part of this change, we've deprecated AccessibilityNodeInfo#setLabeledBy and #getLabeledBy in favor of #addLabeledBy, #removeLabeledBy, and #getLabeledByList.

Improved support for expandable elements

Android 16 adds accessibility APIs that allow you to convey the expanded or collapsed state of interactive elements, such as menus and expandable lists. By setting the expanded state using setExpandedState and dispatching TYPE_WINDOW_CONTENT_CHANGED AccessibilityEvents with a CONTENT_CHANGE_TYPE_EXPANDED content change type, you can ensure that screen readers like TalkBack announce state changes, providing a more intuitive and inclusive user experience.

Indeterminate ProgressBars

Android 16 adds RANGE_TYPE_INDETERMINATE, giving a way for you to expose RangeInfo for both determinate and indeterminate ProgressBar widgets, allowing services like TalkBack to more consistently provide feedback for progress indicators.

Tri-state CheckBox

The new AccessibilityNodeInfo getChecked and setChecked(int) methods in Android 16 now support a "partially checked" state in addition to "checked" and "unchecked." This replaces the deprecated boolean isChecked and setChecked(boolean).

Supplemental descriptions

When an accessibility service describes a ViewGroup, it combines content labels from its child views. If you provide a contentDescription for the ViewGroup, accessibility services assume you are also overriding the description of non-focusable child views. This can be problematic if you want to label things like a drop-down (for example, "Font Family") while preserving the current selection for accessibility (for example, "Roboto"). Android 16 adds setSupplementalDescription so you can provide text that provides information about a ViewGroup without overriding information from its children.

Required form fields

Android 16 adds setFieldRequired to AccessibilityNodeInfo so apps can tell an accessibility service that input to a form field is required. This is an important scenario for users filling out many types of forms, even things as simple as a required terms and conditions checkbox, helping users to consistently identify and quickly navigate between required fields.

將手機設為 LE Audio 助聽器的語音通話麥克風

Android 16 新增了 LE Audio 助聽器功能，使用者可在助聽器內建麥克風和手機麥克風之間切換，以便進行語音通話。這項功能在吵雜的環境或其他助聽器麥克風效能不佳的情況下特別實用。

控制 LEA 助聽器的環境音量

Android 16 新增了 LE Audio 助聽器功能，可調整助聽器麥克風收錄到的環境音量。在背景噪音過大或過小時，這項功能就非常實用。

相機

Android 16 強化了對專業相機使用者的支援，可進行混合式自動曝光，並精確調整色溫和色調。新的夜間模式指標可協助應用程式瞭解何時該切換至夜間模式相機工作階段，以及何時該切換回來。新的 Intent 動作可讓您更輕鬆地拍攝動態相片，我們也持續改良 UltraHDR 圖片，支援 HEIC 編碼和 ISO 21496-1 草案標準的新參數。

混合式自動曝光

Android 16 adds new hybrid auto-exposure modes to Camera2, allowing you to manually control specific aspects of exposure while letting the auto-exposure (AE) algorithm handle the rest. You can control ISO + AE, and exposure time + AE, providing greater flexibility compared to the current approach where you either have full manual control or rely entirely on auto-exposure.

fun setISOPriority() {
    // ... (Your existing code before the snippet) ...

    val availablePriorityModes = mStaticInfo.characteristics.get(
        CameraCharacteristics.CONTROL_AE_AVAILABLE_PRIORITY_MODES
    )

    // ... (Your existing code between the snippets) ...

    // Turn on AE mode to set priority mode
    reqBuilder.set(
        CaptureRequest.CONTROL_AE_MODE,
        CameraMetadata.CONTROL_AE_MODE_ON
    )
    reqBuilder.set(
        CaptureRequest.CONTROL_AE_PRIORITY_MODE,
        CameraMetadata.CONTROL_AE_PRIORITY_MODE_SENSOR_SENSITIVITY_PRIORITY
    )
    reqBuilder.set(
        CaptureRequest.SENSOR_SENSITIVITY,
        TEST_SENSITIVITY_VALUE
    )
    val request: CaptureRequest = reqBuilder.build()

    // ... (Your existing code after the snippet) ...
}

精確調整色溫和色調

Android 16 adds camera support for fine color temperature and tint adjustments to better support professional video recording applications. In previous Android versions, you could control white balance settings through CONTROL_AWB_MODE, which contains options limited to a preset list, such as Incandescent, Cloudy, and Twilight. The COLOR_CORRECTION_MODE_CCT enables the use of COLOR_CORRECTION_COLOR_TEMPERATURE and COLOR_CORRECTION_COLOR_TINT for precise adjustments of white balance based on the correlated color temperature.

fun setCCT() {
    // ... (Your existing code before this point) ...

    val colorTemperatureRange: Range<Int> =
        mStaticInfo.characteristics[CameraCharacteristics.COLOR_CORRECTION_COLOR_TEMPERATURE_RANGE]

    // Set to manual mode to enable CCT mode
    reqBuilder[CaptureRequest.CONTROL_AWB_MODE] = CameraMetadata.CONTROL_AWB_MODE_OFF
    reqBuilder[CaptureRequest.COLOR_CORRECTION_MODE] = CameraMetadata.COLOR_CORRECTION_MODE_CCT
    reqBuilder[CaptureRequest.COLOR_CORRECTION_COLOR_TEMPERATURE] = 5000
    reqBuilder[CaptureRequest.COLOR_CORRECTION_COLOR_TINT] = 30

    val request: CaptureRequest = reqBuilder.build()

    // ... (Your existing code after this point) ...
}

The following examples show how a photo would look after applying different color temperature and tint adjustments:

攝影機夜間模式場景偵測

To help your app know when to switch to and from a night mode camera session, Android 16 adds EXTENSION_NIGHT_MODE_INDICATOR. If supported, it's available in the CaptureResult within Camera2.

This is the API we briefly mentioned as coming soon in the How Instagram enabled users to take stunning low light photos blog post. That post is a practical guide on how to implement night mode together with a case study that links higher-quality in-app night mode photos with an increase in the number of photos shared from the in-app camera.

動態相片拍攝意圖動作

Android 16 新增了標準意圖動作 ACTION_MOTION_PHOTO_CAPTURE 和 ACTION_MOTION_PHOTO_CAPTURE_SECURE，可要求相機應用程式擷取動態相片並傳回。

您必須傳遞額外的 EXTRA_OUTPUT 來控制要寫入圖片的位置，或是透過 Intent.setClipData(ClipData) 傳遞 Uri。如果您未設定 ClipData，系統會在您呼叫 Context.startActivity(Intent) 時複製該值。

UltraHDR 圖片強化功能

Android 16 continues our work to deliver dazzling image quality with UltraHDR images. It adds support for UltraHDR images in the HEIC file format. These images will get ImageFormat type HEIC_ULTRAHDR and will contain an embedded gainmap similar to the existing UltraHDR JPEG format. We're working on AVIF support for UltraHDR as well, so stay tuned.

In addition, Android 16 implements additional parameters in UltraHDR from the ISO 21496-1 draft standard, including the ability to get and set the colorspace that gainmap math should be applied in, as well as support for HDR encoded base images with SDR gainmaps.

圖形

Android 16 包含最新的圖像改善功能，例如使用 AGSL 的自訂圖像效果。

使用 AGSL 製作自訂圖像效果

Android 16 adds RuntimeColorFilter and RuntimeXfermode, allowing you to author complex effects like Threshold, Sepia, and Hue Saturation and apply them to draw calls. Since Android 13, you've been able to use AGSL to create custom RuntimeShaders that extend Shader. The new API mirrors this, adding an AGSL-powered RuntimeColorFilter that extends ColorFilter, and a Xfermode effect that lets you implement AGSL-based custom compositing and blending between source and destination pixels.

private val thresholdEffectString = """
    uniform half threshold;

    half4 main(half4 c) {
        half luminosity = dot(c.rgb, half3(0.2126, 0.7152, 0.0722));
        half bw = step(threshold, luminosity);
        return bw.xxx1 * c.a;
    }"""

fun setCustomColorFilter(paint: Paint) {
   val filter = RuntimeColorFilter(thresholdEffectString)
   filter.setFloatUniform(0.5);
   paint.colorFilter = filter
}

連線能力

Android 16 更新了平台，讓應用程式能使用最新的通訊和無線技術。

採用強化安全性的測距功能

Android 16 adds support for robust security features in Wi-Fi location on supported devices with Wi-Fi 6's 802.11az, allowing apps to combine the higher accuracy, greater scalability, and dynamic scheduling of the protocol with security enhancements including AES-256-based encryption and protection against MITM attacks. This allows it to be used more safely in proximity use cases, such as unlocking a laptop or a vehicle door. 802.11az is integrated with the Wi-Fi 6 standard, leveraging its infrastructure and capabilities for wider adoption and easier deployment.

一般測距 API

Android 16 includes the new RangingManager, which provides ways to determine the distance and angle on supported hardware between the local device and a remote device. RangingManager supports the usage of a variety of ranging technologies such as BLE channel sounding, BLE RSSI-based ranging, Ultra Wideband, and Wi-Fi round trip time.

隨附裝置管理工具裝置狀態

在 Android 16 中，我們推出了新的 API，用於繫結隨附應用程式服務。當 BLE 在範圍內且已連上藍牙時，服務就會繫結；當 BLE 超出範圍或藍牙已中斷連線時，服務就會解除繫結。應用程式會根據各種 DevicePresenceEvent 接收新的 'onDevicePresenceEvent()' 回呼。如需更多詳細資訊，請參閱「startObservingDevicePresence(ObservingDevicePresenceRequest)」一文。

媒體

Android 16 包含多項功能，可提升媒體體驗。

相片挑選工具改良功能

相片挑選工具提供內建的安全方法，讓使用者授予應用程式存取權，以便存取本機和雲端儲存空間中的所選圖片和影片，而非整個媒體庫。透過 Google 系統更新和 Google Play 服務，結合使用模組化系統元件，可支援 Android 4.4 (API 級別 19) 以下版本。整合作業只需要幾行程式碼和相關的 Android Jetpack 程式庫。

Android 16 對相片挑選工具進行了以下改善：

• 內嵌式相片挑選器：新 API，可讓應用程式將相片挑選器嵌入其檢視區塊階層。這樣一來，使用者就能感受到應用程式更整合的部分，同時仍可利用程序隔離功能，讓使用者能夠選取媒體，而應用程式不需要過度廣泛的權限。如要盡可能提高各平台版本的相容性並簡化整合作業，如果您想整合內嵌的相片挑選工具，請使用即將推出的 Android Jetpack 程式庫。
• 相片挑選器中的雲端搜尋功能：新的 API 可讓 Android 相片挑選器從雲端媒體供應器搜尋內容。相片挑選工具中的搜尋功能即將推出。

進階專業影片

Android 16 推出了對進階專業影片 (APV) 轉碼器的支援，該轉碼器專為專業級高品質影片錄製和後製作業而設計。

APV 編碼器標準具有下列功能：

• 感知上無損的影片品質 (接近原始影片品質)
• 低複雜度和高吞吐量的單一影格編碼 (不含像素網域預測)，以便更妥善支援編輯工作流程
• 支援高位元速率範圍 (最高可達數 Gbps)，適用於 2K、4K 和 8K 解析度的內容，可透過輕量化熵值編碼方案啟用
• 為沉浸式內容和啟用平行編碼/解碼作業的框架平鋪作業
• 支援各種色度取樣格式和位元深度
• 支援多重解碼和重新編碼，且不會嚴重降低視覺品質
• 支援多視角影片和輔助影片，例如深度、alpha 和預覽
• 支援 HDR10/10+ 和使用者定義的中繼資料

OpenAPV 專案提供 APV 的參考實作項目。Android 16 將實作支援 APV 422-10 設定檔，提供 YUV 422 色彩取樣功能，以及 10 位元編碼和最高 2 Gbps 的目標位元率。

隱私權

Android 16 包含多項功能，可協助應用程式開發人員保護使用者隱私權。

健康資料同步更新

Health Connect adds ACTIVITY_INTENSITY, a data type defined according to World Health Organization guidelines around moderate and vigorous activity. Each record requires the start time, the end time, and whether the activity intensity is moderate or vigorous.

Health Connect also contains updated APIs supporting medical records. This allows apps to read and write medical records in FHIR format with explicit user consent.

Android 版 Privacy Sandbox

Android 16 incorporates the latest version of the Privacy Sandbox on Android, part of our ongoing work to develop technologies where users know their privacy is protected. Our website has more about the Privacy Sandbox on Android developer beta program to help you get started. Check out the SDK Runtime which allows SDKs to run in a dedicated runtime environment separate from the app they are serving, providing stronger safeguards around user data collection and sharing.

安全性

Android 16 內含多項功能，可協助您提升應用程式安全性及保護應用程式資料。

車鑰分享 API

Android 16 adds APIs that support sharing access to Android Keystore keys with other apps. The new KeyStoreManager class supports granting and revoking access to keys by app uid, and includes an API for apps to access shared keys.

裝置板型規格

Android 16 可讓應用程式充分運用 Android 的板型規格。

電視的標準化影像和音訊品質架構

The new MediaQuality package in Android 16 exposes a set of standardized APIs for access to audio and picture profiles and hardware-related settings. This allows streaming apps to query profiles and apply them to media dynamically:

• Movies mastered with a wider dynamic range require greater color accuracy to see subtle details in shadows and adjust to ambient light, so a profile that prefers color accuracy over brightness may be appropriate.
• Live sporting events are often mastered with a narrow dynamic range, but are often watched in daylight, so a profile that preferences brightness over color accuracy can give better results.
• Fully interactive content wants minimal processing to reduce latency, and wants higher frame rates, which is why many TV's ship with a game profile.

The API allows apps to switch between profiles and users to enjoy tuning supported TVs to best suit their content.

國際化

Android 16 新增多項功能，可提升使用者在不同語言環境下使用裝置的體驗。

直書文字

Android 16 adds low-level support for rendering and measuring text vertically to provide foundational vertical writing support for library developers. This is particularly useful for languages like Japanese that commonly use vertical writing systems. A new flag, VERTICAL_TEXT_FLAG, has been added to the Paint class. When this flag is set using Paint.setFlags, Paint's text measurement APIs will report vertical advances instead of horizontal advances, and Canvas will draw text vertically.

val text = "「春は、曙。」"
Box(
    Modifier.padding(innerPadding).background(Color.White).fillMaxSize().drawWithContent {
        drawIntoCanvas { canvas ->
            val paint = Paint().apply { textSize = 64.sp.toPx() }
            // Draw text vertically
            paint.flags = paint.flags or VERTICAL_TEXT_FLAG
            val height = paint.measureText(text)
            canvas.nativeCanvas.drawText(
                text,
                0,
                text.length,
                size.width / 2,
                (size.height - height) / 2,
                paint
            )
        }
    }
) {}

自訂計量系統

Users can now customize their measurement system in regional preferences within Settings. The user preference is included as part of the locale code, so you can register a BroadcastReceiver on ACTION_LOCALE_CHANGED to handle locale configuration changes when regional preferences change.

Using formatters can help match the local experience. For example, "0.5 in" in English (United States), is "12,7 mm" for a user who has set their phone to English (Denmark) or who uses their phone in English (United States) with the metric system as the measurement system preference.

To find these settings, open the Settings app and navigate to System > Languages & region.