行为变更：以 Android 16 或更高版本为目标平台的应用

与早期版本一样，Android 16 包含一些行为变更，这些变更可能会影响您的应用。以下行为变更仅影响以 Android 16 或更高版本为目标平台的应用。如果您的应用以 Android 16 或更高版本为目标平台，您应该修改自己的应用以支持这些行为（如果适用）。

请务必查看对 Android 16 上运行的所有应用都有影响的行为变更列表（无论应用的 targetSdkVersion 如何）。

用户体验和系统界面

Android 16 进行了以下变更，旨在打造更一致、更直观的用户体验。

无边框设计停用退出选项

Android 15 enforced edge-to-edge for apps targeting Android 15 (API level 35), but your app could opt-out by setting R.attr#windowOptOutEdgeToEdgeEnforcement to true. For apps targeting Android 16, R.attr#windowOptOutEdgeToEdgeEnforcement is deprecated and disabled, and your app can't opt-out of going edge-to-edge.

For testing in Android 16 Beta 2, ensure your app supports edge-to-edge and remove any use of R.attr#windowOptOutEdgeToEdgeEnforcement. To support edge-to-edge, see the Compose and Views guidance. Let us know about concerns in our issue tracker on the feedback page.

需要迁移或停用预测性返回

对于以 Android 16 或更高版本为目标平台且在 Android 16 或更高版本的设备上运行的应用，预测性返回系统动画（返回主屏幕、跨任务和跨 activity）默认处于启用状态。此外，系统不会调用 onBackPressed，也不会再调度 KeyEvent.KEYCODE_BACK。

如果您的应用拦截了返回事件，并且您尚未迁移到预测性返回，请更新应用以使用受支持的返回导航 API；或者，在应用的 AndroidManifest.xml 文件的 <application> 或 <activity> 标记中将 android:enableOnBackInvokedCallback 属性设置为 false，以暂时停用此功能。

“返回主页”预测性返回动画。
预测性跨 activity 动画。
预测性跨任务动画。

优雅字体 API 已废弃并停用

以 Android 15（API 级别 35）为目标平台的应用的 elegantTextHeight TextView 属性默认设置为 true，从而将紧凑字体替换为更易于阅读的字体。您可以通过将 elegantTextHeight 属性设置为 false 来替换此设置。

Android 16 弃用了 elegantTextHeight 属性，并且在您的应用以 Android 16 为目标平台后，系统会忽略该属性。这些 API 控制的“界面字体”即将停用，因此您应调整所有布局，以确保以阿拉伯语、老挝语、缅甸语、泰米尔语、古吉拉特语、卡纳达语、马拉雅拉姆语、奥里亚语、泰卢固语或泰语呈现一致且可持续的文字。

对于以 Android 14（API 级别 34）及更低版本为目标平台的应用，或者对于通过将 elegantTextHeight 属性设置为 false 而替换默认值的以 Android 15（API 级别 35）为目标平台的应用，elegantTextHeight 行为。
对于以 Android 16 为目标平台的应用，或者对于未通过将 elegantTextHeight 属性设置为 false 来替换默认值的以 Android 15（API 级别 35）为目标平台的应用，elegantTextHeight 行为。

核心功能

Android 16 包含以下更改，用于修改或扩展 Android 系统的各种核心功能。

固定费率工作调度优化

Prior to targeting Android 16, when scheduleAtFixedRate missed a task execution due to being outside a valid process lifecycle, all missed executions immediately execute when the app returns to a valid lifecycle.

When targeting Android 16, at most one missed execution of scheduleAtFixedRate is immediately executed when the app returns to a valid lifecycle. This behavior change is expected to improve app performance. Test this behavior in your app to check if your app is impacted. You can also test by using the app compatibility framework and enabling the STPE_SKIP_MULTIPLE_MISSED_PERIODIC_TASKS compat flag.

设备规格

Android 16 对在大屏设备上显示的应用做出了以下更改。

自适应布局

With Android apps now running on a variety of devices (such as phones, tablets, foldables, desktops, cars, and TVs) and windowing modes on large screens (such as split screen and desktop windowing), developers should build Android apps that adapt to any screen and window size, regardless of device orientation. Paradigms like restricting orientation and resizability are too restrictive in today's multidevice world.

Ignore orientation, resizability, and aspect ratio restrictions

For apps targeting Android 16, Android 16 includes changes to how the system manages orientation, resizability, and aspect ratio restrictions. On displays with smallest width >= 600dp, the restrictions no longer apply. Apps also fill the entire display window, regardless of aspect ratio or a user's preferred orientation, and pillarboxing isn't used.

This change introduces a new standard platform behavior. Android is moving toward a model where apps are expected to adapt to various orientations, display sizes, and aspect ratios. Restrictions like fixed orientation or limited resizability hinder app adaptability, so we recommend making your app adaptive to deliver the best possible user experience.

You can also test this behavior by using the [app compatibility framework][a16-kilo-14] and enabling the UNIVERSAL_RESIZABLE_BY_DEFAULT compat flag.

Common breaking changes

Ignoring orientation, resizability, and aspect ratio restrictions might impact your app's UI on some devices, especially elements that were designed for small layouts locked in portrait orientation: for example, issues like stretched layouts and off-screen animations and components. Any assumptions about aspect ratio or orientation can cause visual issues with your app. Learn more about how to avoid them and improve your app's adaptive behaviour.

Allowing device rotation results in more activity re-creation, which can result in losing user state if not properly preserved. Learn how to correctly save UI state in Save UI states.

Implementation details

The following manifest attributes and runtime APIs are ignored across large screen devices in full-screen and multi-window modes:

The following values for screenOrientation, setRequestedOrientation(), and getRequestedOrientation() are ignored:

  • portrait
  • reversePortrait
  • sensorPortrait
  • userPortrait
  • landscape
  • reverseLandscape
  • sensorLandscape
  • userLandscape

Regarding display resizability, android:resizeableActivity="false", android:minAspectRatio, and android:maxAspectRatio have no effect.

For apps targeting Android 16, app orientation, resizability, and aspect ratio constraints are ignored on large screens by default, but every app that isn't fully ready can temporarily override this behavior by opting out (which results in the previous behavior of being placed in compatibility mode).

Exceptions

The Android 16 orientation, resizability, and aspect ratio restrictions don't apply in the following situations:

  • Games (based on the android:appCategory flag)
  • Users explicitly opting in to the app's default behavior in aspect ratio settings of the device
  • Screens that are smaller than sw600dp

Opt out temporarily

To opt out a specific activity, declare the PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY manifest property:

<activity ...>
  <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
  ...
</activity>

If too many parts of your app aren't ready for Android 16, you can opt out completely by applying the same property at the application level:

<application ...>
  <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
</application>

健康与健身

Android 16 包含与健康与健身数据相关的以下变更。

健康与健身权限

对于以 Android 16 或更高版本为目标平台的应用，BODY_SENSORS 权限将过渡到 android.permissions.health 下的精细权限，Health Connect 也使用这些权限。之前需要 BODY_SENSORS 或 BODY_SENSORS_BACKGROUND 的任何 API 现在都需要相应的 android.permissions.health 权限。这会影响以下数据类型、API 和前台服务类型：

如果您的应用使用这些 API，则现在应请求相应的精细权限：

这些权限与用于保护对 Health Connect（用于存储健康、健身和身心健康数据的 Android 数据存储区）读取数据的权限相同。