功能和 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 introduces progress-centric notifications to help users seamlessly track user-initiated, start-to-end journeys.

Notification.ProgressStyle is a new notification style that lets you create progress-centric notifications. Key use cases include rideshare, delivery, and navigation. Within the Notification.ProgressStyle class, you can denote states and milestones in a user journey using points and segments.

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 就提供了对触感反馈致动器的控制。

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 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 was added in Android 15, allowing an app to see reasons for process start, start type, start times, throttling, and other useful diagnostic data. Android 16 adds getStartComponent() to distinguish what component type triggered the start, which can be helpful for optimizing the startup flow of your app.

改进了作业自省

The JobScheduler#getPendingJobReason() API returns a reason why a job might be pending. However, a job might be pending for multiple reasons.

In Android 16, we are introducing a new API JobScheduler#getPendingJobReasons(int jobId), which returns multiple reasons why a job is pending, due to both explicit constraints set by the developer and implicit constraints set by the system.

We're also introducing JobScheduler#getPendingJobReasonsHistory(int jobId), which returns a list of the most recent constraint changes.

We recommend using the API to help you debug why your jobs may not be executing, especially if you're seeing reduced success rates of certain tasks or have bugs around latency of certain job completion. For example, updating widgets in the background failed to occur or prefetch job failed to be called prior to app start.

This can also better help you understand if certain jobs are not completing due to system defined constraints versus explicitly set constraints.

自适应刷新率

Android 15 中引入的自适应刷新率 (ARR) 可让受支持硬件上的显示屏刷新率使用离散的 VSync 步长来适应内容帧速率。这不仅降低了功耗，还无需进行可能导致卡顿的模式切换。

Android 16 引入了 hasArrSupport() 和 getSuggestedFrameRate(int)，同时恢复了 getSupportedRefreshRates()，以便您的应用更轻松地利用 ARR。RecyclerView 1.4 在从快速滑动或平滑滚动中稳定下来时会在内部支持 ARR，我们将继续努力，将 ARR 支持添加到更多 Jetpack 库中。这篇帧速率文章介绍了许多可用于设置帧速率的 API，以便您的应用可以直接使用 ARR。

ADPF 中的 Headroom API

SystemHealthManager 引入了 getCpuHeadroom 和 getGpuHeadroom API，旨在为游戏和资源密集型应用提供可用 CPU 和 GPU 资源的估算值。通过这些方法，您可以评估应用或游戏如何以最佳方式改善系统运行状况，尤其是在与用于检测热节流的其他 Android 动态性能框架 (ADPF) 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.

使用 LEA 助听器进行语音通话时，将手机用作麦克风输入

Android 16 新增了一项功能，让 LE Audio 助听器用户能够在助听器的内置麦克风和手机上的麦克风之间切换，以进行语音通话。在嘈杂的环境或助听器麦克风可能无法正常工作的其他情况下，这会很有帮助。

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。该博文提供了有关如何实现夜间模式的实用指南，并附有一份案例研究，该案例研究将应用内夜间模式照片质量的提升与通过应用内相机分享的照片数量的增加联系起来。

动态照片拍摄 intent 操作

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 继续致力于通过 UltraHDR 图片提供出色的图片质量。它添加了对 HEIC 文件格式的 UltraHDR 图片的支持。这些图片将获得 ImageFormat 类型 HEIC_ULTRAHDR，并包含类似于现有 UltraHDR JPEG 格式的嵌入式增益图。我们还在努力为 UltraHDR 添加 AVIF 支持，敬请期待。

此外，Android 16 在 UltraHDR 中实现了 ISO 21496-1 草稿标准中的其他参数，包括能够获取和设置应应用增益图算法的色彩空间，以及支持使用 SDR 增益图的 HDR 编码基础图片。

图形

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 在搭载 Wi-Fi 6 的 802.11az 的受支持设备上为 Wi-Fi 位置信息添加了对强大的安全功能的支持，让应用能够将该协议的更高精确性、更高可伸缩性和动态调度与安全增强功能（包括基于 AES-256 的加密和防范中间人攻击）相结合。这样，在近距离使用情形（例如解锁笔记本电脑或车门）时，便可更安全地使用该功能。802.11az 与 Wi-Fi 6 标准集成，可利用其基础架构和功能实现更广泛的采用和更轻松的部署。

通用测距 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 包含多种可改善媒体体验的功能。

改进了照片选择器

照片选择器为用户提供了一种安全的内置授权方式，让用户可以向应用授予对本地存储空间和云端存储空间中所选图片和视频的访问权限，而不是对整个媒体库的访问权限。通过 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 新增了 ACTIVITY_INTENSITY，这是一种根据世界卫生组织关于中等强度和剧烈强度活动的指南定义的新数据类型。每个记录都需要提供开始时间、结束时间以及活动强度（中等或剧烈）。

Health Connect 还包含支持健康记录的更新版 API。这样一来，应用便可以在征得用户明确同意的情况下，以 FHIR 格式读取和写入医疗记录。此 API 目前处于抢先体验计划阶段。如果您想参与，请报名参加抢先体验计划。

Privacy Sandbox on Android

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 添加了一些 API，这些 API 支持与其他应用共享对 Android Keystore 密钥的访问权限。新的 KeyStoreManager 类支持按应用 uid 授予和撤消对密钥的访问权限，并包含一个供应用访问共享密钥的 API。

设备规格

Android 16 为您的应用提供了支持，可让应用充分利用 Android 的设备规格。

适用于电视的标准化画质和音质框架

Android 16 中的新 MediaQuality 软件包公开了一组标准化 API，用于访问音频和图片配置文件以及与硬件相关的设置。这样，在线播放应用就可以查询配置文件并将其动态应用于媒体：

• 使用更大动态范围进行母版制作的电影需要更高的色彩准确度，才能看清阴影中的细微细节并根据环境光线进行调整，因此，最好使用色彩准确度优先于亮度的配置文件。
• 体育赛事直播通常采用较窄的动态范围进行母版制作，但通常是在白天观看，因此偏向亮度而非色彩准确度的配置文件可以获得更好的效果。
• 完全交互式内容需要尽可能减少处理以缩短延迟时间，并且需要更高的帧速率，因此许多电视都附带游戏配置文件。

借助此 API，应用可以在个人资料之间切换，用户可以享受调整支持的电视，以便尽可能适合其内容。

国际化

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

自定义衡量系统

用户现在可以在“设置”中的地区偏好设置中自定义测量系统。用户偏好设置包含在语言区域代码中，因此您可以在 ACTION_LOCALE_CHANGED 上注册 BroadcastReceiver，以便在地区偏好设置发生更改时处理语言区域配置更改。

使用格式设置程序有助于提供符合当地体验的服务。例如，对于将手机设置为英语（丹麦）或将手机设置为英语（美国）并将公制作为首选测量系统的用户，“0.5 in”的英语（美国）对应于“12,7 mm”。

如需找到这些设置，请打开“设置”应用，然后依次前往系统 > 语言和地区。