功能與 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 introduces Low Light Boost, a new auto-exposure mode available to both Camera 2 and the night mode camera extension. Low Light Boost adjusts the exposure of the Preview stream in low-light conditions. This is different from how the night mode camera extension creates still images, because night mode combines a burst of photos to create a single, enhanced image. While night mode works very well for creating a still image, it can't create a continuous stream of frames, but Low Light Boost can. Thus, Low Light Boost enables new camera capabilities, such as:

  • Providing an enhanced image preview, so users are better able to frame their low-light pictures
  • Scanning QR codes in low light

If you enable Low Light Boost, it automatically turns on when there's a low light level, and turns off when there's more light.

Apps can record off the Preview stream in low-light conditions to save a brightened video.

For more information, see Low Light Boost.

應用程式內相機控制選項

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 導入了行動號召 -2075 音量標準的支援，可以幫助您避免音訊音量不一致的問題，並確保使用者在切換內容時，不必持續調整音量。系統運用輸出裝置的已知特性 (耳機和喇叭)，以及 AAC 音訊內容中提供的音量中繼資料，有智慧調整音訊的音量和動態範圍壓縮等級。

如要啟用這項功能，您必須確保 AAC 內容可以使用音量中繼資料，並在應用程式中啟用平台功能。為此，您可以使用相關 AudioTrack 的音訊工作階段 ID 呼叫其 create 工廠方法，藉此執行個體化 LoudnessCodecController 物件；這樣就會自動開始套用音訊更新。您可以傳遞 OnLoudnessCodecUpdateListener 以修改或篩選音量參數，然後再套用至 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 也會更新以使用 LoudnessCodecController API，完美整合應用程式。

虛擬 MIDI 2.0 裝置

Android 13 added support for connecting to MIDI 2.0 devices using USB, which communicate using Universal MIDI Packets (UMP). Android 15 extends UMP support to virtual MIDI apps, enabling composition apps to control synthesizer apps as a virtual MIDI 2.0 device just like they would with an USB MIDI 2.0 device.

更有效率的 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 會繼續更新 Android 核心程式庫，以便與最新版 OpenJDK LTS 中的功能保持一致。

新功能和改善項目如下：

這些 API 是透過 Google Play 系統更新，在超過十億部搭載 Android 12 (API 級別 31) 以上版本的裝置上更新，因此您可以指定最新的程式設計功能。

改善 PDF

Android 15 包含大幅改善 PdfRenderer API。應用程式可以整合進階功能，例如轉譯受密碼保護的檔案、註解、表單編輯、搜尋以及選取等進階功能。系統支援線性 PDF 最佳化作業，可加快本機 PDF 的檢視速度並減少資源用量。

PDF 轉譯功能的最新更新內容包含搜尋嵌入式 PDF 檔案等功能。

PdfRenderer 已移至可透過 Google Play 系統更新的模組 (不受平台版本影響)，為支援回溯至 Android 11 (API 級別 30) 的更新，請建立 Android 15 之前的相容 API 介面版本 (稱為 PdfRendererPreV)。

我們十分重視您對 PdfRenderer API 介面所做出的改進，希望您提供寶貴的意見，並規劃透過即將推出的 Android Jetpack 程式庫，更輕鬆地將這些 API 整合至應用程式。

自動語言切換修正功能

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 變數字型 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++.

改善畫布

Android 15 持續翻新 Android 的 Canvas 圖形系統，並提供新功能：

  • Matrix44 提供 4x4 矩陣，可轉換在 3D 中操控畫布時應使用的座標。
  • clipShader 會將目前片段與指定的著色器交錯，clipOutShader 則會將片段設為目前片段和著色器的差異，同時將著色器視為 Alpha 遮罩。這個做法可讓您有效率地繪製複雜的形狀。

效能和電池

Android 會持續專注於提升應用程式的效能和品質。Android 15 導入了新的 API，可提高應用程式工作的執行效率、最佳化應用程式效能，以及收集應用程式的相關深入分析資訊。

如果想瞭解省電的最佳做法、針對網路與電源使用情形進行偵錯，以及深入瞭解我們如何改善 Android 15 和新版 Android 中背景工作的電池效能，請參閱 Google I/O 大會的「改善 Android 上的背景工作的電池效能」演講內容。

ApplicationStartInfo API

在舊版 Android 中，應用程式啟動程序有點複雜。要判斷應用程式內的是從冷、暖還是熱狀態啟動，並不容易。此外，您也很難知道應用程式在各種啟動階段花費的時間，包括建立程序、呼叫 onCreate、繪製第一個影格等。將 Application 類別例項化時，您無法得知應用程式是從廣播、內容供應器、工作、備份、啟動完成、鬧鐘或 Activity 啟動。

Android 15 上的 ApplicationStartInfo API 提供了以上所有功能。甚至可以選擇在流程中加入自己的時間戳記，以在同一位置收集時間資料。除了收集指標，您還可以使用 ApplicationStartInfo 直接最佳化應用程式啟動作業。舉例來說，您可以在應用程式因為廣播訊息而啟動時，避免在 Application 類別中耗費大量成本的 UI 相關程式庫。

應用程式大小詳細資訊

自 Android 8.0 (API 級別 26) 起，Android 納入 StorageStats.getAppBytes API，可將應用程式的安裝大小匯總為單一位元組，包括 APK 大小、從 APK 擷取的檔案大小，以及在裝置上產生的檔案 (例如預先 (AOT) 編譯程式碼) 在內。這個數字在您的應用程式使用儲存空間方面沒有非常少見。

Android 15 新增了 StorageStats.getAppBytesByDataType([type]) API，可讓您深入分析應用程式使用相同空間的情形，包括 APK 檔案分割、AOT 和加速相關程式碼、DEX 中繼資料、程式庫，以及引導式設定檔。

應用程式代管的剖析

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 透過 UriRelativeFilterGroup 支援更精準的 Intent 解析，UriRelativeFilterGroup 包含一組 UriRelativeFilter 物件，形成一組 Intent 比對規則，每個物件必須滿足每個條件都必須符合規則，包括網址查詢參數、網址片段，以及封鎖或排除規則。

您可以在 AndroidManifest XML 檔案中，使用新的 <uri-relative-filter-group> 標記定義這些規則，並視需要加入 android:allow 標記。這些標記可包含使用現有資料標記屬性的 <data> 標記，以及新的 android:query 和 android:fragment 屬性。

以下是 AndroidManifest 語法的範例：

<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>

私人空間

The private space can be unlocked and locked to show or hide sensitive apps on a device.

Private space lets users create a separate space on their device where they can keep sensitive apps away from prying eyes, under an additional layer of authentication. The private space uses a separate user profile. The user can choose to use the device lock or a separate lock factor for the private space.

Apps in the private space show up in a separate container in the launcher, and are hidden from the recents view, notifications, settings, and from other apps when the private space is locked. User-generated and downloaded content (such as media or files) and accounts are separated between the private space and the main space. The system sharesheet and the photo picker can be used to give apps access to content across spaces when the private space is unlocked.

Users can't move existing apps and their data into the private space. Instead, users select an install option in the private space to install an app using whichever app store they prefer. Apps in the private space are installed as separate copies from any apps in the main space (new copies of the same app).

When a user locks the private space, the profile is stopped. While the profile is stopped, apps in the private space are no longer active and can't perform foreground or background activities, including showing notifications.

We recommend that you test your app with private space to make sure your app works as expected, especially if your app falls into one of the following categories:

查詢所選相片存取權最近的使用者選取項目

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

Android 版 Privacy Sandbox

Android 15 includes the latest Android Ad Services extensions, incorporating the latest version of the Privacy Sandbox on Android. This addition is part of our work to develop new technologies that improve user privacy and enable effective, personalized advertising experiences for mobile apps. Our privacy sandbox page has more information about the Privacy Sandbox on Android developer preview and beta programs to help you get started.

Health Connect

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:

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 supports partial screen sharing so users can share or record just an app window rather than the entire device screen. This feature, first enabled in Android 14 QPR2, includes MediaProjection callbacks that allow your app to customize the partial screen sharing experience. Note that for apps targeting Android 14 (API level 34) or higher, user consent is now required for each MediaProjection capture session.

使用者體驗和系統 UI

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

如要進一步瞭解如何使用 Android 15 的最新改善功能來改善應用程式的使用者體驗，請參閱 Google I/O 大會的「改善 Android 應用程式的使用者體驗」講座。

透過 Generated Previews API 提供更豐富的小工具預覽

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:

  1. At any time, the widget provider calls setWidgetPreview. The provided previews are persisted in AppWidgetService with other provider info.
  2. setWidgetPreview notifies hosts of an updated preview through the AppWidgetHost.onProvidersChanged callback. In response, the widget host reloads all of its provider information.
  3. 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 introduces new changes in Picture-in-Picture (PiP) ensuring an even smoother transition when entering into PiP mode. This will be beneficial for apps having UI elements overlaid on top of their main UI, which goes into PiP.

Developers use the onPictureInPictureModeChanged callback to define logic that toggles the visibility of the overlaid UI elements. This callback is triggered when the PiP enter or exit animation is completed. Beginning in Android 15, the PictureInPictureUiState class includes a new state.

With this new UI state, apps targeting Android 15 will observe the Activity#onPictureInPictureUiStateChanged callback being invoked with isTransitioningToPip() as soon as the PiP animation starts. There are many UI elements that are not relevant for the app when it is in PiP mode, for example views or layout that include information such as suggestions, upcoming video, ratings, and titles. When the app goes to PiP mode, use the onPictureInPictureUiStateChanged callback to hide these UI elements. When the app goes to full screen mode from the PiP window, use onPictureInPictureModeChanged callback to unhide these elements, as shown in the following examples:

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

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

This quick visibility toggle of irrelevant UI elements (for a PiP window) helps ensure a smoother and flicker-free PiP enter animation.

改善「零打擾」規則

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.

為通知管道設定 VibrationEffect

Android 15 支援使用 NotificationChannel.setVibrationEffect，透過管道為傳入的通知設定複合式震動，讓使用者不必查看裝置，就能區分不同類型的通知。

大螢幕與板型規格

Android 15 可讓應用程式充分運用 Android 的板型規格，包括大螢幕、可折疊式裝置和折疊式裝置。

改善大螢幕的多工處理效能

Android 15 gives users better ways to multitask on large screen devices. For example, users can save their favorite split-screen app combinations for quick access and pin the taskbar on screen to quickly switch between apps. This means that making sure your app is adaptive is more important than ever.

Google I/O has sessions on Building adaptive Android apps and Building UI with the Material 3 adaptive library that can help, and our documentation has more to help you Design for large screens.

封面螢幕支援

Your app can declare a property that Android 15 uses to allow your Application or Activity to be presented on the small cover screens of supported flippable devices. These screens are too small to be considered as compatible targets for Android apps to run on, but your app can opt in to supporting them, making your app available in more places.

連線能力

Android 15 會更新平台，讓應用程式存取最新的通訊和無線技術。

衛星支援

Android 15 continues to extend platform support for satellite connectivity and includes some UI elements to ensure a consistent user experience across the satellite connectivity landscape.

Apps can use ServiceState.isUsingNonTerrestrialNetwork() to detect when a device is connected to a satellite, giving them more awareness of why full network services might be unavailable. Additionally, Android 15 provides support for SMS and MMS apps as well as preloaded RCS apps to use satellite connectivity for sending and receiving messages.

A notification appears when the device connects to a satellite.

更流暢的 NFC 體驗

Android 15 致力於讓感應支付體驗更順暢、更穩定，同時繼續支援 Android 可靠的 NFC 應用程式生態系統。在支援的裝置上，應用程式可以要求 NfcAdapter 進入觀測模式，裝置在監聽但不回應 NFC 讀取器時，會傳送應用程式的 NFC 服務 PollingFrame 物件進行處理。PollingFrame 物件可在首次與 NFC 讀取器進行通訊前驗證，在許多情況下允許進行一次輕觸交易。

此外，應用程式現在可以在支援的裝置上註冊指紋，以便接收輪詢迴圈活動的通知，進而利用多個 NFC 感知應用程式順暢運作。

錢包角色

Android 15 introduces a new Wallet role that allows tighter integration with the user's preferred wallet app. This role replaces the NFC default contactless payment setting. Users can manage the Wallet role holder by navigating to Settings > Apps > Default Apps.

The Wallet role is used when routing NFC taps for AIDs registered in the payment category. Taps always go to the Wallet role holder unless another app that is registered for the same AID is running in the foreground.

This role is also used to determine where the Wallet QuickAccess tile should go when activated. When the role is set to "None", the QuickAccess tile isn't available and payment category NFC taps are only delivered to the foreground app.

安全性

Android 15 可協助您強化應用程式的安全性、保護應用程式資料，並讓使用者更清楚掌握及控管自己的資料。如要進一步瞭解我們採取哪些措施加強使用者保護措施，並保護應用程式防範新的威脅，請參閱 Google I/O 大會的「在 Android 上保護使用者安全」一文。

端對端加密金鑰管理服務

We are introducing the E2eeContactKeysManager in Android 15, which facilitates end-to-end encryption (E2EE) in your Android apps by providing an OS-level API for the storage of cryptographic public keys.

The E2eeContactKeysManager is designed to integrate with the platform contacts app to give users a centralized way to manage and verify their contacts' public keys.

內容 URI 的權限檢查

Android 15 導入了一組新的 API，可對內容 URI 執行權限檢查：

無障礙功能

Android 15 加入了改善使用者無障礙功能的功能。

更強大的點字功能

在 Android 15 中，我們讓 TalkBack 能夠支援透過 USB 和安全藍牙採用 HID 標準的點字顯示器。

如同滑鼠和鍵盤所使用的標準，Android 日後將支援更多點字顯示器。

國際化

Android 15 新增了多項功能，可在裝置以不同語言使用時提供更優質的使用者體驗。

CJK 變數字型

Starting with Android 15, the font file for Chinese, Japanese, and Korean (CJK) languages, NotoSansCJK, is now a variable font. Variable fonts open up new possibilities for creative typography in CJK languages. Designers can explore a broader range of styles and create visually striking layouts that were previously difficult or impossible to achieve.

How the variable font for Chinese, Japanese, and Korean (CJK) languages appears with different font widths.

跨字元理由

從 Android 15 開始，只要使用 JUSTIFICATION_MODE_INTER_CHARACTER，即可妥善運用字母間距。跨字詞正當理由首次於 Android 8.0 (API 級別 26) 推出，而跨字元正當化可為使用空白字元字元區隔的語言 (例如中文、日文等) 提供類似功能。

使用 JUSTIFICATION_MODE_NONE 顯示日文的版面配置。
使用 JUSTIFICATION_MODE_NONE 顯示英文文字的版面配置。


使用 JUSTIFICATION_MODE_INTER_WORD 顯示日文的版面配置。
使用 JUSTIFICATION_MODE_INTER_WORD 顯示英文文字的版面配置。


使用新的 JUSTIFICATION_MODE_INTER_CHARACTER 配置日文文字。
使用新版 JUSTIFICATION_MODE_INTER_CHARACTER 調整英文文字的版面配置。

自動換行設定

Android 13 (API 級別 33) 已開始支援日文和韓文的日文和韓文詞組換行符號。不過，詞組換行符號讓短行文字的可讀性提升了，但對於長行文字的效果不佳。在 Android 15 中，應用程式現在可以使用 LINE_BREAK_WORD_STYLE_AUTO 選項，只針對短行文字套用詞組換行符號。這個選項會針對文字選取最適合的字詞樣式選項。

如果是短行文字，則會使用以詞組為主的換行符號，其運作方式與 LINE_BREAK_WORD_STYLE_PHRASE 相同，如下圖所示：

如果是短行文字，LINE_BREAK_WORD_STYLE_AUTO 會套用詞組換行符號，讓文字更容易閱讀。 這與套用 LINE_BREAK_WORD_STYLE_PHRASE 相同。

對於較長的文字行，LINE_BREAK_WORD_STYLE_AUTO 使用不換行字詞樣式，其運作方式與 LINE_BREAK_WORD_STYLE_NONE 相同，如下圖所示：

對於長行文字，LINE_BREAK_WORD_STYLE_AUTO 不會套用換行字詞樣式，讓文字更容易閱讀。 這與套用 LINE_BREAK_WORD_STYLE_NONE 相同。

新日本 Hentaigana 字型

In Android 15, a new font file for old Japanese Hiragana (known as Hentaigana) is bundled by default. The unique shapes of Hentaigana characters can add a distinctive flair to artwork or design while also helping to preserve accurate transmission and understanding of ancient Japanese documents.

Character and text style for the Japanese Hentaigana font.

VideoLAN cone Copyright (c) 1996-2010 VideoLAN，任何人都可以使用或修改此標誌或修改後的版本，以參照 VideoLAN 專案或 VideoLAN 團隊開發的任何產品，但不代表專案背書。

Vulkan 和 Vulkan 標誌是 Khronos Group Inc.的註冊商標。

OpenGL 是註冊商標，OpenGL ES 標誌是 Khronos 許可使用的 Hewlett Packard Enterprise 商標。