此页面由 Cloud Translation API 翻译。

功能和 API 概览

Android 15 面向开发者引入了一些出色的新功能和 API。以下部分总结了这些功能，以帮助您开始使用相关 API。

如需查看新增、修改和移除的 API 的详细列表，请参阅 API 差异报告。如需详细了解新的 API，请访问 Android API 参考文档，新 API 会突出显示以方便查看。此外，如需了解平台变更可能会在哪些方面影响您的应用，请务必查看 Android 15 以 Android 15 为目标平台的应用对应用有影响的行为变更以及影响所有应用（无论 targetSdkVersion 如何）的行为变更。

摄像头和媒体

Android 15 包含各种功能，可改善相机和媒体体验，并可让您使用各种工具和硬件来支持创作者在 Android 上将其构想变为现实。

如需详细了解 Android 媒体和相机的最新功能和开发者解决方案，请参阅 Google I/O 大会的打造现代 Android 媒体和相机体验演讲。

弱光增强

Android 15 引入了低光增强，这是一种新的自动曝光模式，可供 Camera 2 和夜间模式相机扩展使用。“低光增强”功能可调整预览视频流在弱光条件下的曝光量。这与夜间模式相机扩展程序创建静态图片的方式不同，因为夜间模式会组合多张照片来制作单张增强图片。虽然夜间模式非常适合创建静态图片，但无法创建连续的帧流，但“低光增强”可以。因此，“低光增强”可以实现新的相机功能，例如：

提供增强的图片预览，以便用户更好地为弱光环境取景
在光线昏暗的环境下扫描二维码

如果您启用“弱光增强”，它会在光线较暗时自动开启，在光线较暗时关闭。

应用可以在光线昏暗的环境下录制预览流，以保存明亮的视频。

有关详情，请参阅弱光增强。

应用内相机控件

Android 15 添加了一个新扩展，用于在支持的设备上更好地控制相机硬件及其算法：

高级闪光灯强度调整，可让您在拍摄照片时精确控制 SINGLE 和 TORCH 模式下的闪光强度。

HDR 余量控制

Android 15 chooses HDR headroom that is appropriate for the underlying device capabilities and bit-depth of the panel. For pages that have lots of SDR content, such as a messaging app displaying a single HDR thumbnail, this behavior can end up adversely influencing the perceived brightness of the SDR content. Android 15 lets you control the HDR headroom with setDesiredHdrHeadroom to strike a balance between SDR and HDR content.

The brightness of SDR UI elements on the left screen appears to be more uniform than the brightness on the right screen, which simulates possible headroom issues when HDR and SDR content are mixed. By adjusting the HDR headroom, you can achieve a better balance between the SDR and HDR content.

音量控制

Android 15 introduces support for the CTA-2075 loudness standard to help you avoid audio loudness inconsistencies and ensure users don't have to constantly adjust volume when switching between content. The system leverages known characteristics of the output devices (headphones and speaker) along with loudness metadata available in AAC audio content to intelligently adjust the audio loudness and dynamic range compression levels.

To enable this feature, you need to ensure loudness metadata is available in your AAC content and enable the platform feature in your app. For this, you instantiate a LoudnessCodecController object by calling its create factory method with the audio session ID from the associated AudioTrack; this automatically starts applying audio updates. You can pass an OnLoudnessCodecUpdateListener to modify or filter loudness parameters before they are applied on the MediaCodec.

// Media contains metadata of type MPEG_4 OR MPEG_D
val mediaCodec = …
val audioTrack = AudioTrack.Builder()
                                .setSessionId(sessionId)
                                .build()
...
// Create new loudness controller that applies the parameters to the MediaCodec
try {
   val lcController = LoudnessCodecController.create(mSessionId)
   // Starts applying audio updates for each added MediaCodec
}

AndroidX media3 ExoPlayer will also be updated to use the LoudnessCodecController APIs for a seamless app integration.

虚拟 MIDI 2.0 设备

Android 13 添加了对使用 USB 连接到 MIDI 2.0 设备的支持，USB 使用通用 MIDI 数据包 (UMP) 进行通信。Android 15 扩展了对虚拟 MIDI 应用的 UMP 支持，使合成器应用能够像对待 USB MIDI 2.0 设备一样将合成器应用作为虚拟 MIDI 2.0 设备进行控制。

更高效的 AV1 软件解码

dav1d logo

dav1d, the popular AV1 software decoder from VideoLAN is now available for Android devices that don't support AV1 decode in hardware. dav1d is up to 3x more performant than the legacy AV1 software decoder, enabling HD AV1 playback for more users, including some low and mid tier devices.

For now, your app needs to opt-in to using dav1d by invoking it by name "c2.android.av1-dav1d.decoder". dav1d will be made the default AV1 software decoder in a subsequent update. This support is standardized and backported to Android 11 devices that receive Google Play system updates.

开发者工作效率和工具

虽然我们的大部分办公工作都围绕 Android Studio、Jetpack Compose 和 Android Jetpack 库等工具展开，但我们始终在平台中寻找方法来帮助您更轻松地实现愿景。

OpenJDK 17 更新

Android 15 continues the work of refreshing Android's core libraries to align with the features in the latest OpenJDK LTS releases.

The following key features and improvements are included:

Quality-of-life improvements around NIO buffers
Streams
Additional math and strictmath methods
util package updates including sequenced collection, map, and set
ByteBuffer support in Deflater
Security updates such as X500PrivateCredential and security key updates

These APIs are updated on over a billion devices running Android 12 (API level 31) and higher through Google Play System updates, so you can target the latest programming features.

改进了 PDF

Android 15 includes substantial improvements to the PdfRenderer APIs. Apps can incorporate advanced features such as rendering password-protected files, annotations, form editing, searching, and selection with copy. Linearized PDF optimizations are supported to speed local PDF viewing and reduce resource use.

The latest updates to PDF rendering include features such as searching an embedded PDF file.

The PdfRenderer has been moved to a module that can be updated using Google Play system updates independent of the platform release, and we're supporting these changes back to Android 11 (API level 30) by creating a compatible pre-Android 15 version of the API surface, called PdfRendererPreV.

We value your feedback on the enhancements we've made to the PdfRenderer API surface, and we plan to make it even easier to incorporate these APIs into your app with an upcoming Android Jetpack library.

语言切换自动优化

Android 14 added on-device, multi-language recognition in audio with automatic switching between languages, but this can cause words to get dropped, especially when languages switch with less of a pause between the two utterances. Android 15 adds additional controls to help apps tune this switching to their use case. EXTRA_LANGUAGE_SWITCH_INITIAL_ACTIVE_DURATION_TIME_MILLIS confines the automatic switching to the beginning of the audio session, while EXTRA_LANGUAGE_SWITCH_MATCH_SWITCHES deactivates the language switching after a defined number of switches. These options are particularly useful if you expect that there will be a single language spoken during the session that should be autodetected.

改进了 OpenType Variable Font API

Android 15 improves the usability of the OpenType variable font. You can now create a FontFamily instance from a variable font without specifying weight axes with the buildVariableFamily API. The text renderer overrides the value of wght axis to match the displaying text.

Using the new API, this simplifies the code for creating a Typeface considerably:

Kotlin

val newTypeface = Typeface.CustomFallbackBuilder(
            FontFamily.Builder(
                Font.Builder(assets, "RobotoFlex.ttf").build())
                    .buildVariableFamily())
    .build()

Java

Typeface newTypeface = Typeface.CustomFallbackBuilder(
            new FontFamily.Builder(
                new Font.Builder(assets, "RobotoFlex.ttf").build())
                    .buildVariableFamily())
    .build();

Previously, to create the same Typeface, you would need much more code:

Kotlin

val oldTypeface = Typeface.CustomFallbackBuilder(
            FontFamily.Builder(
                Font.Builder(assets, "RobotoFlex.ttf")
                    .setFontVariationSettings("'wght' 400")
                    .setWeight(400)
                    .build())
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 100")
                        .setWeight(100)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 200")
                        .setWeight(200)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 300")
                        .setWeight(300)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 500")
                        .setWeight(500)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 600")
                        .setWeight(600)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 700")
                        .setWeight(700)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 800")
                        .setWeight(800)
                        .build()
                )
                .addFont(
                    Font.Builder(assets, "RobotoFlex.ttf")
                        .setFontVariationSettings("'wght' 900")
                        .setWeight(900)
                        .build()
                ).build()
        ).build()

Java

Typeface oldTypeface = new Typeface.CustomFallbackBuilder(
    new FontFamily.Builder(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 400")
            .setWeight(400)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 100")
            .setWeight(100)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 200")
            .setWeight(200)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 300")
            .setWeight(300)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 500")
            .setWeight(500)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 600")
            .setWeight(600)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 700")
            .setWeight(700)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 800")
            .setWeight(800)
            .build()
    )
    .addFont(
        new Font.Builder(assets, "RobotoFlex.ttf")
            .setFontVariationSettings("'wght' 900")
            .setWeight(900)
            .build()
    )
    .build()
).build();

Here's an example of how a Typeface created with both the old and new APIs renders:

An example of how Typeface rendering differs using new and old
APIs

In this example, the Typeface created with the old API doesn't have the capability to create accurate font weights for the 350, 450, 550 and 650 Font instances, so the renderer falls back to the closest weight. So in this case, 300 is rendered instead of 350, 400 is rendered instead of 450, and so on. By contrast, the Typeface created with the new APIs dynamically creates a Font instance for a given weight, so accurate weights are rendered for 350, 450, 550, and 650 as well.

细化的换行符控件

从 Android 15 开始，TextView 和底层换行符可以将文本的给定部分保留在同一行中，以提高可读性。您可以通过在字符串资源或 createNoBreakSpan 中使用 <nobreak> 标记来利用此换行符自定义功能。同样，您可以使用 <nohyphen> 标记或 createNoHyphenationSpan 避免断字的情况。

例如，以下字符串资源不包含换行符，而是在不希望的位置显示文本“Pixel 8 Pro”进行渲染：

<resources>
    <string name="pixel8pro">The power and brains behind Pixel 8 Pro.</string>
</resources>

相比之下，此字符串资源包含 <nobreak> 标记，该标记会封装短语“Pixel 8 Pro.”并防止换行符：

<resources>
    <string name="pixel8pro">The power and brains behind <nobreak>Pixel 8 Pro.</nobreak></string>
</resources>

这些字符串的呈现方式差异如下图所示：

用于设置一行文本的布局，其中词组“Pixel 8 Pro”未使用 <nobreak> 标记进行换行。

同一行文本的布局，其中词组“Pixel 8 Pro”用 <nobreak> 标记封装。

应用归档

Android and Google Play announced support for app archiving last year, allowing users to free up space by partially removing infrequently used apps from the device that were published using Android App Bundle on Google Play. Android 15 now includes OS level support for app archiving and unarchiving, making it easier for all app stores to implement it.

Apps with the REQUEST_DELETE_PACKAGES permission can call the PackageInstaller requestArchive method to request archiving an installed app package, which removes the APK and any cached files, but persists user data. Archived apps are returned as displayable apps through the LauncherApps APIs; users will see a UI treatment to highlight that those apps are archived. If a user taps on an archived app, the responsible installer will get a request to unarchive it, and the restoration process can be monitored by the ACTION_PACKAGE_ADDED broadcast.

图形

Android 15 引入了最新的图形改进，包括 ANGLE 以及对 Canvas 图形系统的补充。

对 Android 的 GPU 访问功能进行现代化改造

Vulkan logo

Android hardware has evolved quite a bit from the early days where the core OS would run on a single CPU and GPUs were accessed using APIs based on fixed-function pipelines. The Vulkan® graphics API has been available in the NDK since Android 7.0 (API level 24) with a lower-level abstraction that better reflects modern GPU hardware, scales better to support multiple CPU cores, and offers reduced CPU driver overhead — leading to improved app performance. Vulkan is supported by all modern game engines.

Vulkan is Android's preferred interface to the GPU. Therefore, Android 15 includes ANGLE as an optional layer for running OpenGL® ES on top of Vulkan. Moving to ANGLE will standardize the Android OpenGL implementation for improved compatibility, and, in some cases, improved performance. You can test out your OpenGL ES app stability and performance with ANGLE by enabling the developer option in Settings -> System -> Developer Options -> Experimental: Enable ANGLE on Android 15.

The Android ANGLE on Vulkan roadmap

Roadmap of upcoming changes to the Android GPU APIs.

As part of streamlining our GPU stack, going forward we will be shipping ANGLE as the GL system driver on more new devices, with the future expectation that OpenGL/ES will be only available through ANGLE. That being said, we plan to continue support for OpenGL ES on all devices.

Recommended next steps

Use the developer options to select the ANGLE driver for OpenGL ES and test your app. For new projects, we strongly encourage using Vulkan for C/C++.

对 Canvas 的改进

Android 15 continues our modernization of Android's Canvas graphics system with new capabilities:

Matrix44 provides a 4x4 matrix for transforming coordinates that should be used when you want to manipulate the canvas in 3D.
clipShader intersects the current clip with the specified shader, while clipOutShader sets the clip to the difference of the current clip and the shader, each treating the shader as an alpha mask. This supports the drawing of complex shapes efficiently.

性能和电池

Android 将继续专注于帮助您提高应用的性能和质量。Android 15 引入了新的 API，可帮助您更高效地执行应用中的任务、优化应用性能，以及收集有关应用的数据洞见。

如需了解省电最佳实践、调试网络和功耗问题，以及我们如何提高 Android 15 和最新 Android 版本中后台工作的电池效率，请参阅 Google I/O 大会上的提高 Android 平台上后台工作的电池效率演讲。

ApplicationStartInfo API

In previous versions of Android, app startup has been a bit of a mystery. It was challenging to determine within your app whether it started from a cold, warm, or hot state. It was also difficult to know how long your app spent during the various launch phases: forking the process, calling onCreate, drawing the first frame, and more. When your Application class was instantiated, you had no way of knowing whether the app started from a broadcast, a content provider, a job, a backup, boot complete, an alarm, or an Activity.

The ApplicationStartInfo API on Android 15 provides all of this and more. You can even choose to add your own timestamps into the flow to help collect timing data in one place. In addition to collecting metrics, you can use ApplicationStartInfo to help directly optimize app startup; for example, you can eliminate the costly instantiation of UI-related libraries within your Application class when your app is starting up due to a broadcast.

详细的应用大小信息

Since Android 8.0 (API level 26), Android has included the StorageStats.getAppBytes API that summarizes the installed size of an app as a single number of bytes, which is a sum of the APK size, the size of files extracted from the APK, and files that were generated on the device such as ahead-of-time (AOT) compiled code. This number is not very insightful in terms of how your app is using storage.

Android 15 adds the StorageStats.getAppBytesByDataType([type]) API, which lets you get insight into how your app is using up all that space, including APK file splits, AOT and speedup related code, dex metadata, libraries, and guided profiles.

应用管理的性能剖析

Android 15 包含全新的 ProfilingManager 类，可让您从应用内收集性能分析信息。我们计划使用 Android Jetpack API 封装该类，这将简化性能分析请求的构建过程，但核心 API 将允许收集堆转储、堆配置文件、堆栈采样等信息。它使用提供的标记为您的应用提供回调，用于标识输出文件，该文件将传递到应用的文件目录。该 API 会限制速率限制，以最大限度地降低对性能的影响。

SQLite 数据库改进

Android 15 introduces new SQLite APIs that expose advanced features from the underlying SQLite engine that target specific performance issues that can manifest in apps.

Developers should consult best practices for SQLite performance to get the most out of their SQLite database, especially when working with large databases or when running latency-sensitive queries.

Read-only deferred transactions: when issuing transactions that are read-only (don't include write statements), use beginTransactionReadOnly() and beginTransactionWithListenerReadOnly(SQLiteTransactionListener) to issue read-only DEFERRED transactions. Such transactions can run concurrently with each other, and if the database is in WAL mode, they can run concurrently with IMMEDIATE or EXCLUSIVE transactions.
Row counts and IDs: new APIs were added to retrieve the count of changed rows or the last inserted row ID without issuing an additional query. getLastChangedRowCount() returns the number of rows that were inserted, updated, or deleted by the most recent SQL statement within the current transaction, while getTotalChangedRowCount() returns the count on the current connection. getLastInsertRowId() returns the rowid of the last row to be inserted on the current connection.
Raw statements: issue a raw SQlite statement, bypassing convenience wrappers and any additional processing overhead that they may incur.

Android 动态性能框架更新

Android 15 继续投资开发 Android 动态性能框架 (ADPF)，这是一组 API，可让游戏和性能密集型应用更直接地与 Android 设备的电源和散热系统进行互动。在受支持的设备上，Android 15 将添加新的 ADPF 功能：

适用于提示会话的节能模式，用于指明其关联的线程应该优先考虑节能而非性能，非常适合长时间运行的后台工作负载。
可以在提示会话中报告 GPU 和 CPU 的运行时长，从而使系统能够同时调整 CPU 和 GPU 频率，以便更好地满足工作负载需求。
热余量阈值，用于根据余量预测来解释可能的热节流状态。

如需详细了解如何在应用和游戏中使用 ADPF，请参阅相关文档。

隐私权

Android 15 包含各种有助于应用开发者保护用户隐私的功能。

屏幕录制检测

Android 15 adds support for apps to detect that they are being recorded. A callback is invoked whenever the app transitions between being visible or invisible within a screen recording. An app is considered visible if activities owned by the registering process's UID are being recorded. This way, if your app is performing a sensitive operation, you can inform the user that they're being recorded.

val mCallback = Consumer<Int> { state ->
  if (state == SCREEN_RECORDING_STATE_VISIBLE) {
    // We're being recorded
  } else {
    // We're not being recorded
  }
}

override fun onStart() {
   super.onStart()
   val initialState =
      windowManager.addScreenRecordingCallback(mainExecutor, mCallback)
   mCallback.accept(initialState)
}

override fun onStop() {
    super.onStop()
    windowManager.removeScreenRecordingCallback(mCallback)
}

扩展的 IntentFilter 功能

Android 15 builds in support for more precise Intent resolution through UriRelativeFilterGroup, which contains a set of UriRelativeFilter objects that form a set of Intent matching rules that must each be satisfied, including URL query parameters, URL fragments, and blocking or exclusion rules.

These rules can be defined in the AndroidManifest XML file with the new <uri-relative-filter-group> tag, which can optionally include an android:allow tag. These tags can contain <data> tags that use existing data tag attributes as well as the new android:query and android:fragment attributes.

Here's an example of the AndroidManifest syntax:

<intent-filter>
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:scheme="http" />
  <data android:scheme="https" />
  <data android:domain="astore.com" />
  <uri-relative-filter-group>
    <data android:pathPrefix="/auth" />
    <data android:query="region=na" />
  </uri-relative-filter-group>
  <uri-relative-filter-group android:allow="false">
    <data android:pathPrefix="/auth" />
    <data android:query="mobileoptout=true" />
  </uri-relative-filter-group>
  <uri-relative-filter-group android:allow="false">
    <data android:pathPrefix="/auth" />
    <data android:fragmentPrefix="faq" />
  </uri-relative-filter-group>
</intent-filter>

私密空间

私密空间可让用户在设备上创建一个单独的空间，并通过一层额外的身份验证机制来防止敏感应用被窥探。私密空间使用单独的用户个人资料。当用户锁定私密空间后，资料会暂停，私密空间中的所有应用都不再活跃。用户可以选择对私密空间使用设备锁定或单独的锁定因数。

私密空间中的应用会显示在启动器中的单独容器中；当私密空间处于锁定状态时，私密空间中的应用不会出现在“最近用过”视图、通知、设置和其他应用中。在私密空间和主空间之间，用户可以生成和下载的内容（如媒体或文件）及帐号分开显示。在私密空间处于解锁状态时，可使用系统 Sharesheet 和照片选择器授权应用跨空间访问内容。

我们建议您使用私有空间测试应用，以确保应用按预期运行，尤其是当您的应用属于以下类别之一时：

具有工作资料逻辑的应用，即假定主资料中未包含其应用的任何已安装副本均位于工作资料中。
启动器应用
应用商店中的应用

查询所选照片访问权限的最近用户选择

It is now possible for apps to highlight only the most recently selected photos and videos when partial access to media permissions is granted. This feature can improve the user experience for apps that frequently request access to photos and videos. To use this feature in your app, enable the QUERY_ARG_LATEST_SELECTION_ONLY argument when querying MediaStore through ContentResolver.

Kotlin

val externalContentUri = MediaStore.Files.getContentUri("external")

val mediaColumns = arrayOf(
   FileColumns._ID,
   FileColumns.DISPLAY_NAME,
   FileColumns.MIME_TYPE,
)

val queryArgs = bundleOf(
   // Return only items from the last selection (selected photos access)
   QUERY_ARG_LATEST_SELECTION_ONLY to true,
   // Sort returned items chronologically based on when they were added to the device's storage
   QUERY_ARG_SQL_SORT_ORDER to "${FileColumns.DATE_ADDED} DESC",
   QUERY_ARG_SQL_SELECTION to "${FileColumns.MEDIA_TYPE} = ? OR ${FileColumns.MEDIA_TYPE} = ?",
   QUERY_ARG_SQL_SELECTION_ARGS to arrayOf(
       FileColumns.MEDIA_TYPE_IMAGE.toString(),
       FileColumns.MEDIA_TYPE_VIDEO.toString()
   )
)

Java

Uri externalContentUri = MediaStore.Files.getContentUri("external");

String[] mediaColumns = {
    FileColumns._ID,
    FileColumns.DISPLAY_NAME,
    FileColumns.MIME_TYPE
};

Bundle queryArgs = new Bundle();
queryArgs.putBoolean(MediaStore.QUERY_ARG_LATEST_SELECTION_ONLY, true);
queryArgs.putString(MediaStore.QUERY_ARG_SQL_SORT_ORDER, FileColumns.DATE_ADDED + " DESC");
queryArgs.putString(MediaStore.QUERY_ARG_SQL_SELECTION, FileColumns.MEDIA_TYPE + " = ? OR " + FileColumns.MEDIA_TYPE + " = ?");
queryArgs.putStringArray(MediaStore.QUERY_ARG_SQL_SELECTION_ARGS, new String[] {
    String.valueOf(FileColumns.MEDIA_TYPE_IMAGE),
    String.valueOf(FileColumns.MEDIA_TYPE_VIDEO)
});

Privacy Sandbox on Android

Android 15 包含最新的 Android 广告服务扩展程序，以及最新版 Privacy Sandbox on Android。我们致力于开发新的技术，以便更好地保护用户隐私，并为移动应用打造有效的个性化广告体验。这项新功能是我们的工作的一部分。我们的隐私沙盒页面详细介绍了 Privacy Sandbox on Android 开发者预览版和 Beta 版计划，以帮助您开始使用。

健康数据共享

Android 15 integrates the latest extensions around Health Connect by Android, a secure and centralized platform to manage and share app-collected health and fitness data. This update adds support for new data types across fitness, nutrition, skin temperature, training plans, and more.

Skin temperature tracking allows users to store and share more accurate temperature data from a wearable or other tracking device.

Training plans are structured workout plans to help a user achieve their fitness goals. Training plans support includes a variety of completion and performance goals:

Completion goals around calories burned, distance, duration, repetition, and steps.
Performance goals around as many repetitions as possible (AMRAP), cadence, heart rate, power, perceived rate of exertion, and speed.

Learn more about the latest updates to Health Connect in Android in the Building adaptable experiences with Android Health talk from Google I/O.

Android 15 支持局部屏幕共享，因此用户可以仅分享或录制应用窗口，而不是整个设备屏幕。此功能在 Android 14 QPR2 中首次启用，包含 MediaProjection 回调，可让您的应用自定义局部屏幕共享体验。请注意，对于以 Android 14（API 级别 34）或更高版本为目标平台的应用，现在需要针对每个 MediaProjection 捕获会话征得用户同意。

用户体验和系统界面

Android 15 为应用开发者和用户提供了更大的控制力和灵活性，让他们能够根据自己的需求配置设备。

如需详细了解如何利用 Android 15 的最新改进来提升应用的用户体验，请参阅 Google I/O 大会上的提升 Android 应用的用户体验演讲。

使用 Generated Previews API 提供更丰富的 widget 预览

Before Android 15, the only way to provide widget picker previews was to specify a static image or layout resource. These previews often differ significantly from the look of the actual widget when it is placed on the home screen. Also, static resources can't be created with Jetpack Glance, so a Glance developer had to screenshot their widget or create an XML layout to have a widget preview.

Android 15 adds support for generated previews. This means that app widget providers can generate RemoteViews to use as the picker preview, instead of a static resource.

Apps can provide Remote Views to the Widget Picker, so they can update the content in the picker to be more representative of what the user will see.

Push API

Apps can provide generated previews through a push API. Apps can provide previews at any point in their lifecycle, and don't receive an explicit request from the host to provide previews. Previews are persisted in AppWidgetService, and hosts can request them on-demand. The following example loads an XML widget layout resource and sets it as the preview:

AppWidgetManager.getInstance(appContext).setWidgetPreview(
   ComponentName(
       appContext,
       SociaLiteAppWidgetReceiver::class.java
   ),
   AppWidgetProviderInfo.WIDGET_CATEGORY_HOME_SCREEN,
   RemoteViews("com.example", R.layout.widget_preview)
)

The expected flow is:

At any time, the widget provider calls setWidgetPreview. The provided previews are persisted in AppWidgetService with other provider info.
setWidgetPreview notifies hosts of an updated preview through the AppWidgetHost.onProvidersChanged callback. In response, the widget host reloads all of its provider information.
When displaying a widget preview, the host checks AppWidgetProviderInfo.generatedPreviewCategories, and if the chosen category is available, calls AppWidgetManager.getWidgetPreview to return the saved preview for this provider.

When to call `setWidgetPreview`

Because there is no callback to provide previews, apps can choose to send previews at any point when they are running. How often to update the preview depends on the widget's use case.

The following list describes the two main categories of preview use cases:

Providers that show real data in their widget previews, such as personalized or recent information. These providers can set the preview once the user has signed in or has done initial configuration in their app. After this, they can set up a periodic task to update the previews at their chosen cadence. Examples of this type of widget could be a photo, calendar, weather or news widget.
Providers that show static information in previews or quick-action widgets that don't display any data. These providers can set previews once, when the app first launches. Examples of this type of widget include a drive quick actions widget or chrome shortcuts widget.

Some providers might show static previews on the hub mode picker, but real information on the homescreen picker. These providers should follow the guidance for both of these use cases to set previews.

画中画

Android 15 引入了对画中画 (PiP) 功能的新变更，可确保在进入画中画模式时能够更顺畅地过渡。这对于将界面元素叠加在其主界面之上的应用（将进入画中画模式）非常有用。

开发者使用 onPictureInPictureModeChanged 回调来定义用于切换叠加界面元素的可见性的逻辑。此回调会在画中画进入或退出动画播放完毕时触发。从 Android 15 开始，PictureInPictureUiState 类包含一个新状态。

借助这种新的界面状态，以 Android 15 为目标平台的应用会在画中画动画开始时立即观察到使用 isTransitioningToPip() 调用的 Activity#onPictureInPictureUiStateChanged 回调。在应用处于画中画模式时，有许多界面元素与应用无关，例如，包含建议、即将播出的视频、评分和标题等信息的视图或布局。当应用进入画中画模式时，使用 onPictureInPictureUiStateChanged 回调隐藏这些界面元素。当应用从画中画窗口进入全屏模式时，可以使用 onPictureInPictureModeChanged 回调来取消隐藏这些元素，如以下示例所示：

override fun onPictureInPictureUiStateChanged(pipState: PictureInPictureUiState) {
        if (pipState.isTransitioningToPip()) {
          // Hide UI elements
        }
    }

override fun onPictureInPictureModeChanged(isInPictureInPictureMode: Boolean) {
        if (isInPictureInPictureMode) {
          // Unhide UI elements
        }
    }

这种可快速切换不相关界面元素（适用于画中画窗口）的可见性切换有助于确保画中画进入动画更加流畅且无闪烁。

改进了“勿扰”规则

AutomaticZenRule lets apps customize Attention Management (Do Not Disturb) rules and decide when to activate or deactivate them. Android 15 greatly enhances these rules with the goal of improving the user experience. The following enhancements are included:

Adding types to AutomaticZenRule, allowing the system to apply special treatment to some rules.
Adding an icon to AutomaticZenRule, helping to make the modes be more recognizable.
Adding a triggerDescription string to AutomaticZenRule that describes the conditions on which the rule should become active for the user.
Added ZenDeviceEffects to AutomaticZenRule, allowing rules to trigger things like grayscale display, night mode, or dimming the wallpaper.

为通知渠道设置振动效果

Android 15 支持使用 NotificationChannel.setVibrationEffect 按渠道为传入的通知设置丰富的振动，以便用户可以区分不同类型的通知，而无需看自己的设备。

大屏设备和外形规格

Android 15 支持您的应用充分利用 Android 设备类型，包括大屏设备、可翻转设备和可折叠设备。

改进了大屏幕多任务处理

Android 15 为用户提供了更好的在大屏设备上进行多任务处理的方式。例如，用户可以保存他们喜欢的分屏应用组合以快速访问，还可以固定屏幕上的任务栏以在应用之间快速切换。这意味着，确保应用具有自适应能力比以往任何时候都更加重要。

Google I/O 大会举办了有关构建自适应 Android 应用和使用 Material 3 自适应库构建界面的会议，这对您有所帮助。我们的文档中包含更多可以帮助您针对大屏幕进行设计的文档。

封面屏幕支持

您的应用可以声明一项属性，Android 15 会使用该属性将您的 Application 或 Activity 呈现在支持的可翻转设备的小封面屏幕上。这些屏幕太小，无法被视为 Android 应用的兼容目标，但您的应用可以选择支持这些屏幕，从而让您的应用可在更多位置使用。

畅连乐享

Android 15 更新了该平台，让您的应用能够利用通信和无线技术领域的最新进展。

卫星支持

Android 15 继续扩展对卫星连接的平台支持，并添加了一些界面元素，以确保在卫星连接环境中提供一致的用户体验。

应用可以使用 ServiceState.isUsingNonTerrestrialNetwork() 检测设备何时连接到卫星，从而更好地了解为什么全网络服务不可用。此外，Android 15 支持短信和彩信应用以及预加载的 RCS 应用，以便使用卫星连接收发信息。

更顺畅的 NFC 体验

Android 15 is working to make the tap to pay experience more seamless and reliable while continuing to support Android's robust NFC app ecosystem. On supported devices, apps can request the NfcAdapter to enter observe mode, where the device listens but doesn't respond to NFC readers, sending the app's NFC service PollingFrame objects to process. The PollingFrame objects can be used to auth ahead of the first communication to the NFC reader, allowing for a one tap transaction in many cases.

In addition, apps can now register a fingerprint on supported devices so they can be notified of polling loop activity, which allows for smooth operation with multiple NFC-aware applications.

钱包角色

Android 15 引入了一个新的钱包角色，可让您与用户首选的钱包应用更紧密地集成。此角色取代了 NFC 默认的感应式付款设置。用户可以通过导航到设置 > 应用 > 默认应用来管理 Google 钱包角色持有者。

在为付款类别中注册的 AID 路由 NFC 触碰时，可使用“钱包”角色。除非已在前台运行为同一 AID 注册的另一个应用，否则点按操作会始终转到钱包角色持有者。

此角色还可用于确定钱包“快速访问”功能块在启用后应转到的位置。当角色设置为“无”时，“快速访问”功能块不可用，并且付款类别 NFC 触碰仅会传送到前台应用。

安全性

Android 15 可帮助您增强应用的安全性，保护应用的数据，并让用户更好地了解和控制其数据。请参阅 Google I/O 大会上的在 Android 设备上保护用户安全演讲，详细了解我们为改进用户保护措施并保护您的应用免受新威胁的工作。

适用于端到端加密的密钥管理

我们在 Android 15 中引入了 E2eeContactKeysManager，它提供用于存储加密公钥的操作系统级 API，有助于 Android 应用中的端到端加密 (E2EE)。

E2eeContactKeysManager 旨在与平台通讯录应用集成，使用户能够集中管理和验证其联系人的公钥。

针对内容 URI 的权限检查

Android 15 introduces a new set of APIs that perform permission checks on content URIs:

Context.checkContentUriPermissionFull: This performs a full permission check on content URIs.
Activity manifest attribute requireContentUriPermissionFromCaller: This enforces specified permissions on the provided content URIs at activity launch.
ComponentCaller class for Activity callers: This represents the app that launched the activity.

无障碍功能

Android 15 添加了一些功能来改进用户的无障碍功能。

改进盲文功能

在 Android 15 中，TalkBack 可以支持通过 USB 和安全蓝牙使用 HID 标准的盲文显示屏。

此标准与鼠标和键盘使用的标准非常相似，有助于 Android 随着时间的推移而支持更广泛的盲文显示屏。

国际化

Android 15 添加了一些特性和功能，可在以不同语言使用设备时补充用户体验。

CJK 可变字体

从 Android 15 开始，中文、日语和韩语 (CJK) 语言的字体文件 NotoSansCJK 现已成为可变字体。可变字体为 CJK 语言的广告素材排版开辟了新的可能性。设计师可以探索更广泛的样式，并创建以前难以或无法实现的具有视觉冲击力的布局。

字符间理由

Starting with Android 15, text can be justified utilizing letter spacing by using JUSTIFICATION_MODE_INTER_CHARACTER. Inter-word justification was first introduced in Android 8.0 (API level 26), and inter-character justification provides similar capabilities for languages that use the whitespace character for segmentation, such as Chinese, Japanese, and others.

Layout for Japanese text using JUSTIFICATION_MODE_NONE.

Layout for English text using JUSTIFICATION_MODE_NONE.

Layout for Japanese text using JUSTIFICATION_MODE_INTER_WORD.

Layout for English text using JUSTIFICATION_MODE_INTER_WORD.

Layout for Japanese text using the new JUSTIFICATION_MODE_INTER_CHARACTER.

Layout for English text using the new JUSTIFICATION_MODE_INTER_CHARACTER.

自动换行配置

Android started supporting phrase-based line breaks for Japanese and Korean in Android 13 (API level 33). However, while phrase-based line breaks improve the readability of short lines of text, they don't work well for long lines of text. In Android 15, apps can now apply phrase-based line breaks only for short lines of text, using the LINE_BREAK_WORD_STYLE_AUTO option. This option selects the best word style option for the text.

For short lines of text, phrase-based line breaks are used, functioning the same as LINE_BREAK_WORD_STYLE_PHRASE, as shown in the following image:

For short lines of text, `LINE_BREAK_WORD_STYLE_AUTO` applies phrase-based line breaks to improve the readability of the text. This is the same as applying `LINE_BREAK_WORD_STYLE_PHRASE`.

For longer lines of text, LINE_BREAK_WORD_STYLE_AUTO uses a no line-break word style, functioning the same as LINE_BREAK_WORD_STYLE_NONE, as shown in the following image:

For long lines of text, `LINE_BREAK_WORD_STYLE_AUTO` applies no line-break word style to improve the readability of the text. This is the same as applying `LINE_BREAK_WORD_STYLE_NONE`.

新日语 Hentaigana 字体

在 Android 15 中，默认情况下捆绑了旧版日语平假名（称为 Hentaigana）的新字体文件。形态独特的 Hentaigana 角色可为艺术作品或设计增添独特的风格，同时有助于准确传达和理解古代日本文献。

Vulkan 和 Vulkan 徽标是 Khronos Group Inc.的注册商标。

OpenGL 是注册商标，OpenGL ES 徽标是 Khronos 许可使用的 Hewlett Packard Enterprise 商标。

功能和 API 概览

摄像头和媒体

弱光增强

应用内相机控件

HDR 余量控制

音量控制

虚拟 MIDI 2.0 设备

更高效的 AV1 软件解码

开发者工作效率和工具

OpenJDK 17 更新

改进了 PDF

语言切换自动优化

改进了 OpenType Variable Font API

Kotlin

Java

Kotlin

Java

细化的换行符控件

应用归档

图形

对 Android 的 GPU 访问功能进行现代化改造

The Android ANGLE on Vulkan roadmap

Recommended next steps

对 Canvas 的改进

性能和电池

ApplicationStartInfo API

详细的应用大小信息

应用管理的性能剖析

SQLite 数据库改进

Android 动态性能框架更新

隐私权

屏幕录制检测

扩展的 IntentFilter 功能

私密空间

查询所选照片访问权限的最近用户选择

Kotlin

Java

Privacy Sandbox on Android

健康数据共享

局部屏幕共享

用户体验和系统界面

使用 Generated Previews API 提供更丰富的 widget 预览

Push API

When to call setWidgetPreview

画中画

改进了“勿扰”规则

为通知渠道设置振动效果

大屏设备和外形规格

改进了大屏幕多任务处理

封面屏幕支持

畅连乐享

卫星支持

更顺畅的 NFC 体验

钱包角色

安全性

适用于端到端加密的密钥管理

针对内容 URI 的权限检查

无障碍功能

改进盲文功能

国际化

CJK 可变字体

字符间理由

自动换行配置

新日语 Hentaigana 字体

When to call `setWidgetPreview`