功能與 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.

使用者體驗和系統使用者介面

Android 16 可讓應用程式開發人員和使用者更有彈性地控管裝置，以符合自身需求。

以進度為主軸的通知

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

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

To learn more, see the Progress-centric notifications documentation page.

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

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

預測返回更新

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 has exposed control over the haptic actuator ever since its inception.

Android 11 added support for more complex haptic effects that more advanced actuators could support through VibrationEffect.Compositions of device-defined semantic primitives.

Android 16 adds haptic APIs that let apps define the amplitude and frequency curves of a haptic effect while abstracting away differences between device capabilities.

開發人員工作效率和工具

雖然我們大部分的努力都是為了改善您的工作效率，並以 Android Studio、Jetpack Compose 和 Android Jetpack 程式庫等工具為中心，但我們也一直在尋找各種方法，透過平台協助您實現願景。

動態桌布的內容處理

在 Android 16 中，動態桌布架構會獲得新的內容 API，以解決動態、使用者導向桌布的挑戰。目前，整合使用者提供內容的動態桌布需要複雜的服務專屬實作項目。Android 16 推出 WallpaperDescription 和 WallpaperInstance。您可以使用 WallpaperDescription 識別同一個服務中動態桌布的不同例項。舉例來說，如果桌布同時出現在主畫面和螢幕鎖定畫面，則兩者可能會顯示不同的內容。桌布挑選器和 WallpaperManager 會使用這項中繼資料，為使用者提供更優質的桌布，讓您能以更簡便的方式打造多樣化且個人化的動態桌布體驗。

效能和電池

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

系統觸發的剖析

ProfilingManager was added in Android 15, giving apps the ability to request profiling data collection using Perfetto on public devices in the field. However, since this profiling must be started from the app, critical flows such as startups or ANRs would be difficult or impossible for apps to capture.

To help with this, Android 16 introduces system-triggered profiling to ProfilingManager. Apps can register interest in receiving traces for certain triggers such as cold start reportFullyDrawn or ANRs, and then the system starts and stops a trace on the app's behalf. After the trace completes, the results are delivered to the app's data directory.

在 ApplicationStartInfo 中啟動元件

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

更完善的工作內省功能

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

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

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

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

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

自動調整刷新率

在 Android 15 中推出的適應性重新整理率 (ARR) 可讓支援硬體的螢幕重新整理率，透過獨立的 VSync 步驟調整至內容影格速率。這麼做可降低耗電量，同時避免需要切換模式，進而導致卡頓現象。

Android 16 在還原 getSupportedRefreshRates() 時，會引入 hasArrSupport() 和 getSuggestedFrameRate(int)，讓應用程式更容易利用 ARR。RecyclerView 1.4 在從彈跳或平滑捲動中進行調整時，會在內部支援 ARR，我們也持續致力於將 ARR 支援功能加入更多 Jetpack 程式庫。這篇關於影格速率的文章介紹許多可用來設定影格速率的 API，讓應用程式能直接使用 ARR。

ADPF 中的 Headroom API

The SystemHealthManager introduces the getCpuHeadroom and getGpuHeadroom APIs, designed to provide games and resource-intensive apps with estimates of available CPU and GPU resources. These methods offer a way for you to gauge how your app or game can best improve system health, particularly when used in conjunction with other Android Dynamic Performance Framework (ADPF) APIs that detect thermal throttling.

By using CpuHeadroomParams and GpuHeadroomParams on supported devices, you can customize the time window used to compute the headroom and select between average or minimum resource availability. This can help you reduce your CPU or GPU resource usage accordingly, leading to better user experiences and improved battery life.

無障礙設定

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.

使用手機麥克風輸入聲音，以便透過 LEA 助聽器進行語音通話

Android 16 adds the capability for users of LE Audio hearing aids to switch between the built-in microphones on the hearing aids and the microphone on their phone for voice calls. This can be helpful in noisy environments or other situations where the hearing aid's microphones might not perform well.

為 LEA 助聽器提供環境音量控制

Android 16 adds the capability for users of LE Audio hearing aids to adjust the volume of ambient sound that is picked up by the hearing aid's microphones. This can be helpful in situations where background noise is too loud or too quiet.

相機

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:

相機夜間模式場景偵測

為協助應用程式瞭解何時切換至夜間模式相機工作階段，Android 16 新增了 EXTENSION_NIGHT_MODE_INDICATOR。如果支援，則可在 Camera2 的 CaptureResult 中使用。

這是我們在「Instagram 如何讓使用者拍出令人驚豔的低光照相」網誌文章中，曾簡短提及的即將推出的 API。這篇文章是實用指南，說明如何實作夜間模式，並提供個案研究，說明如何透過應用程式內的相機，分享更多高品質的夜間模式相片。

動態相片拍攝意圖動作

Android 16 adds standard Intent actions — ACTION_MOTION_PHOTO_CAPTURE, and ACTION_MOTION_PHOTO_CAPTURE_SECURE — which request that the camera application capture a motion photo and return it.

You must either pass an extra EXTRA_OUTPUT to control where the image will be written, or a Uri through Intent.setClipData(ClipData). If you don't set a ClipData, it will be copied there for you when calling 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 新增了 RuntimeColorFilter 和 RuntimeXfermode，讓您可以製作複雜的效果 (例如閾值、棕褐色和色調飽和度)，並套用至繪圖呼叫。自 Android 13 起，您可以使用 AGSL 建立可擴充 Shader 的自訂 RuntimeShaders。新的 API 會反映這項情況，新增由 AGSL 提供動力的 RuntimeColorFilter，可擴充 ColorFilter，以及 Xfermode 效果，讓您在來源和目的地像素之間實作以 AGSL 為基礎的自訂合成和混合效果。

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 introduces support for the Advanced Professional Video (APV) codec which is designed to be used for professional level high quality video recording and post production.

The APV codec standard has the following features:

• Perceptually lossless video quality (close to raw video quality)
• Low complexity and high throughput intra-frame-only coding (without pixel domain prediction) to better support editing workflows
• Support for high bit-rate range up to a few Gbps for 2K, 4K and 8K resolution content, enabled by a lightweight entropy coding scheme
• Frame tiling for immersive content and for enabling parallel encoding and decoding
• Support for various chroma sampling formats and bit-depths
• Support for multiple decoding and re-encoding without severe visual quality degradation
• Support multi-view video and auxiliary video like depth, alpha, and preview
• Support for HDR10/10+ and user-defined metadata

A reference implementation of APV is provided through the OpenAPV project. Android 16 will implement support for the APV 422-10 Profile that provides YUV 422 color sampling along with 10-bit encoding and for target bitrates of up to 2Gbps.

隱私權

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

Health Connect 更新

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 新增了對垂直顯示和測量文字的低階支援功能，為程式庫開發人員提供基本的垂直書寫支援。這項功能特別適合日文等常使用直式書寫系統的語言。Paint 類別已新增旗標 VERTICAL_TEXT_FLAG。使用 Paint.setFlags 設定這個標記時，Paint 的文字測量 API 會回報垂直進度，而非水平進度，而 Canvas 會垂直繪製文字。

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
            )
        }
    }
) {}

自訂測量系統

使用者現在可以在「設定」中，透過區域偏好設定自訂測量系統。使用者偏好設定會納入語言代碼，因此您可以在 ACTION_LOCALE_CHANGED 上註冊 BroadcastReceiver，以便在地區偏好設定變更時，處理語言代碼設定的變更。

使用格式化工具可協助您提供符合當地體驗的服務。舉例來說，如果使用者將手機設為英文 (美國)，或使用英文 (美國) 並將公制系統設為偏好的測量系統，則英文 (美國) 中的「0.5 英寸」會顯示為「12.7 公釐」。

如要找到這些設定，請開啟「設定」應用程式，並依序前往「系統」>「語言與地區」。