Google uses AI technology to translate content into your preferred language. AI translations can contain errors.

功能與 API 總覽

Android 15 為開發人員推出了強大的新功能和 API。以下各節會簡要說明這些功能，協助您開始使用相關 API。

如需新增、修改及移除 API 的詳細清單，請參閱 API 差異比較表。如要進一步瞭解新增的 API，請參閱 Android API 參考資料 - 針對 Android 15，請尋找在 API 級別 35 中新增的 API。如要瞭解平台變更可能對應用程式造成的影響，請務必查看指定 Android 15 的應用程式和所有應用程式的 Android 15 行為變更。

相機和媒體

Android 15 包含多種功能，可提升相機和媒體體驗，並提供工具和硬體，協助創作者在 Android 上實現創意。

如要進一步瞭解 Android 媒體和相機的最新功能和開發人員解決方案，請觀看 Google I/O 的「打造現代 Android 媒體和相機體驗」演講。

低光源增強

Android 15 introduces Low Light Boost, an 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 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 adds an extension for more control over the camera hardware and its algorithms on supported devices:

Advanced flash strength adjustments enabling precise control of flash intensity in both SINGLE and TORCH modes while capturing images.

HDR 動態範圍控制

Android 15 會選擇適合底層裝置功能和面板位元深度的 HDR 空間。對於含有大量 SDR 內容的網頁 (例如顯示單一 HDR 縮圖的訊息應用程式)，這種行為可能會對 SDR 內容的觀看亮度造成負面影響。在 Android 15 中，您可以使用 setDesiredHdrHeadroom 控制 HDR 空間，以便在 SDR 和 HDR 內容之間取得平衡。

左側螢幕的 SDR UI 元素亮度似乎比右側螢幕的亮度更均勻，模擬 HDR 和 SDR 內容混合時可能出現的動態範圍問題。調整 HDR 安全邊界後，SDR 和 HDR 內容之間的平衡度會更佳。

音量控制

Android 15 開始支援 CTA-2075 音量標準，協助您可避免音訊音量不一致的情況，同時確保使用者不必一直調整音量。系統會利用輸出裝置 (耳機和喇叭) 的已知特性，以及 AAC 音訊內容提供的音量中繼資料，智慧調整音訊音量和動態範圍壓縮等級。

如要啟用這項功能，請務必確保檔案含有音量中繼資料您的 AAC 內容，並在應用程式中啟用平台功能。為此，您透過以下方式將 LoudnessCodecController 物件執行個體化：呼叫其 create 工廠方法，並與音訊來自相關聯 AudioTrack 的工作階段 ID；本系統就會開始自動套用音訊更新您可以傳遞 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 新增了支援功能，可透過 USB 連線至MIDI 2.0 裝置，並透過通用 MIDI 封包 (UMP) 進行通訊。Android 15 將 UMP 支援擴展至虛擬 MIDI 應用程式，讓合成應用程式可透過虛擬 MIDI 2.0 裝置控制合成器應用程式，就像使用 USB MIDI 2.0 裝置一樣。

更有效率的 AV1 軟體解碼

dav1d 標誌

dav1d 是 VideoLAN 推出的熱門 AV1 軟體解碼器，適用於不支援硬體 AV1 解碼功能的 Android 裝置。dav1d 的效能比舊版 AV1 軟體解碼器高出 3 倍，可讓更多使用者 (包括部分低階和中階裝置) 播放 HD AV1 影片。

您的應用程式必須透過名稱 "c2.android.av1-dav1d.decoder" 呼叫 dav1d，才能選擇使用 dav1d。在後續更新中，dav1d 將成為預設的 AV1 軟體解碼器。這項支援功能已標準化，並向後移植至接收 Google Play 系統更新的 Android 11 裝置。

開發人員工作效率和工具

我們致力於提升開發人員的工作效率，因此大部分工作都圍繞著 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 Jetpack PDF library uses these APIs to simplify adding PDF viewing capabilities to your app.

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.

自動切換語言的改良功能

Android 14 在音訊中新增了裝置端多語言辨識功能，可自動切換語言，但這可能會導致字詞遺漏，尤其是在兩次發音之間的暫停時間較短時。Android 15 新增了額外控制項，協助應用程式根據用途調整此切換功能。EXTRA_LANGUAGE_SWITCH_INITIAL_ACTIVE_DURATION_TIME_MILLIS 會將自動切換限制在音訊工作階段的開頭，而 EXTRA_LANGUAGE_SWITCH_MATCH_SWITCHES 會在指定次數的切換後停用語言切換功能。如果您預期在工作階段中會使用單一語言，且該語言應自動偵測，這些選項就特別實用。

改良的 OpenType 變數字型 API

Android 15 improves the usability of the OpenType variable font. You can 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 API 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.

精細的換行符號控制項

Starting in Android 15, a TextView and the underlying line breaker can preserve the given portion of text in the same line to improve readability. You can take advantage of this line break customization by using the <nobreak> tag in string resources or createNoBreakSpan. Similarly, you can preserve words from hyphenation by using the <nohyphen> tag or createNoHyphenationSpan.

For example, the following string resource doesn't include a line break, and renders with the text "Pixel 8 Pro." breaking in an undesirable place:

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

In contrast, this string resource includes the <nobreak> tag, which wraps the phrase "Pixel 8 Pro." and prevents line breaks:

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

The difference in how these strings are rendered is shown in the following images:

Layout for a line of text where the phrase "Pixel 8 Pro." isn't wrapped using a <nobreak> tag.

Layout for the same line of text where the phrase "Pixel 8 Pro." is wrapped using a <nobreak> tag.

封存應用程式

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

使用開發人員選項在裝置上啟用 16 KB 模式

切換「以 16KB 頁面大小啟動」開發人員選項，即可在 16 KB 模式下啟動裝置。

在 Android 15 的 QPR 版本中，您可以使用特定裝置上的開發人員選項，以 16 KB 模式啟動裝置，並執行裝置端測試。使用開發人員選項前，請依序前往「設定」>「系統」>「軟體更新」，並套用所有可用的更新。

下列裝置提供這項開發人員選項：

Pixel 8 和 8 Pro (搭載 Android 15 QPR1 以上版本)
Pixel 8a (搭載 Android 15 QPR1 以上版本)
Pixel 9、Pixel 9 Pro 和 Pixel 9 Pro XL (搭載 Android 15 QPR2 以上版本)
Pixel 9a (搭載 Android 16 以上版本)

圖形

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 持續將 Android 的 Canvas 圖形系統改良為現代化版本，並提供額外功能：

Matrix44 提供 4x4 矩陣，用於轉換座標，您應在 3D 中操控畫布時使用此矩陣。
clipShader 會將目前的短片與指定的著色器相交，而 clipOutShader 會將短片設為目前的短片與著色器的差異，並將每個著色器視為 Alpha 遮罩。這可有效繪製複雜的形狀。

效能和電池

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 類別，可讓您從應用程式內收集剖析資訊，例如記憶體快照資料、記憶體快照資料、堆疊取樣等。它會為您的應用程式提供回呼，並提供標記來識別輸出檔案，該檔案會傳送至應用程式的檔案目錄。API 會實施頻率限制，盡可能降低對效能的影響。

如要簡化應用程式中的剖析要求建構程序，建議您使用對應的 Profiling AndroidX API (適用於 Core 1.15.0-rc01 以上版本)。

SQLite 資料庫改善項目

Android 15 推出 SQLite API，可公開基礎 SQLite 引擎的進階功能，針對應用程式可能出現的特定效能問題進行調整。這些 API 已隨 SQLite 更新至 3.44.3 版一併提供。

開發人員應參考提升 SQLite 效能的最佳做法充分運用 SQLite 資料庫，尤其是處理大型資料集時或執行容易受到延遲時間影響的查詢時

唯讀延遲交易：在發出唯讀交易 (不包含寫入陳述式) 時，請使用 beginTransactionReadOnly() 和 beginTransactionWithListenerReadOnly(SQLiteTransactionListener) 發出唯讀 DEFERRED 交易。這類交易可以同時執行，如果資料庫處於 WAL 模式，則可以與 IMMEDIATE 或 EXCLUSIVE 交易同時執行。
資料列計數與 ID：新增了 API 以擷取已變更的計數資料列或上次插入的資料列 ID，且無須發出額外查詢。 getLastChangedRowCount() 會傳回資料列數量最新的 SQL 陳述式已插入、更新或刪除目前交易，而 getTotalChangedRowCount() 會傳回目前連線的計數。 getLastInsertRowId() 會傳回要在目前連線中插入的最後一列的 rowid。
原始陳述式：發布原始 SQlite 陳述式，略過便利性以及可能會產生的任何額外處理負擔。

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，其中包含一組 UriRelativeFilter 物件，可形成一組必須滿足的 Intent 比對規則，包括網址查詢參數、網址片段，以及封鎖或排除規則。

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

以下是 AndroidManifest 語法範例：

<intent-filter android:autoVerify="true">
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.BROWSABLE" />
  <category android:name="android.intent.category.DEFAULT" />
  <data android:scheme="http" />
  <data android:scheme="https" />
  <data android:host="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:

Apps with logic for work profiles that assumes that any installed copies of their app that aren't in the main profile are in the work profile.
Medical apps
Launcher apps
App store apps

查詢「選取的相片存取權」的最新使用者選取項目

Apps can now 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 包含最新的 Android Ad Services 擴充功能，其中整合了 Android 版 Privacy Sandbox 的最新版本。這項新增功能是我們開發新技術的一部分，旨在強化使用者隱私，並在行動應用程式中提供有效的個人化廣告體驗。我們的 Privacy Sandbox 頁面提供 Android 版 Privacy Sandbox 開發人員預覽版和 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 additional 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 擷取工作階段都需要使用者同意。

使用者體驗和系統 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:

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 introduces 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 another state.

With this UI state, apps targeting Android 15 (API level 35) 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 可讓應用程式自訂注意力管理 (請勿打擾) 規則，並決定何時啟用或停用具體做法是指示 Kubernetes 建立並維護一或多個代表這些 Pod 的物件Android 15 大幅強化上述規則，目標是改善使用者體驗包含以下強化項目：

將類型新增至 AutomaticZenRule，讓系統套用特殊類型來處理部分規則
將圖示新增至 AutomaticZenRule，讓模式更容易辨識。
將 triggerDescription 字串新增至 AutomaticZenRule，用來描述規則對使用者的有效條件
已新增 ZenDeviceEffects敬上到AutomaticZenRule，允許規則觸發灰階等事件顯示螢幕、夜間模式，或是調暗桌布

為通知管道設定 VibrationEffect

Android 15 supports setting rich vibrations for incoming notifications by channel using NotificationChannel.setVibrationEffect, so your users can distinguish between different types of notifications without having to look at their device.

媒體投影狀態列資訊方塊和自動停止

Media projection can expose private user information. A new, prominent status bar chip makes users aware of any ongoing screen projection. Users can tap the chip to stop screen casting, sharing, or recording. Also, for a more intuitive user experience, any in‑progress screen projection now automatically stops when the device screen is locked.

大螢幕和板型規格

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

改善大螢幕多工處理功能

Android 15 可讓使用者在大螢幕裝置上更妥善地進行多工處理。適用對象舉例來說，使用者可以儲存喜愛的分割畫面應用程式組合，以便快速，並將工作列固定在畫面上，即可快速切換應用程式。也就是說確保應用程式會自動調適，比以往更重要。

Google I/O 大會建構可自動調整的 Android 環境應用程式以及使用 Material 3 建構使用者介面自動調整程式庫這能幫助您，而我們的說明文件也更勝以往，能進一步協助您運用大型語言設計螢幕。

支援封面螢幕

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 持續擴大平台支援範圍，包括衛星連線，以及包含一些 UI 元素，確保衛星連線環境。

應用程式可以使用 ServiceState.isUsingNonTerrestrialNetwork() 執行下列操作：會偵測裝置是否與衛星連線可能無法使用完整網路服務的原因此外，Android 15 支援簡訊和多媒體訊息應用程式，以及預先載入的 RCS 應用程式可以收發訊息的衛星連線。

更流暢的 NFC 體驗

Android 15 正在努力讓輕觸付款體驗更流暢可靠，同時繼續支援 Android 強大的 NFC 應用程式生態系統。在支援的裝置上，應用程式可以要求 NfcAdapter 進入觀察模式，在該模式下，裝置會聆聽但不會回應 NFC 讀卡器，並傳送應用程式的 NFC 服務 PollingFrame 物件進行處理。PollingFrame 物件可用於在首次與 NFC 讀取器通訊前進行驗證，在許多情況下可支援單按鈕交易。

此外，應用程式可以在支援的裝置上註冊篩選器，以便在檢查迴圈活動發生時收到通知，進而與多個支援 NFC 的應用程式順利運作。

錢包角色

Android 15 推出了錢包角色，可與使用者偏好的錢包應用程式進行更緊密的整合。這個角色會取代 NFC 預設感應式付款設定。使用者可以依序前往「設定」>「應用程式」>「預設應用程式」，管理錢包角色持有人。

當您為付款類別註冊的 AID 轉送 NFC 輕觸動作時，就會使用錢包角色。除非另一個已註冊相同 AID 的應用程式在前景執行，否則點選動作一律會傳送至錢包角色持有者。

這個角色也用於決定 Wallet 快速存取設定方塊在啟用時應顯示的位置。將角色設為「None」時，系統就不會提供快速存取圖塊，且付款類別的 NFC 輕觸動作只會傳送至前景應用程式。

安全性

Android 15 可協助您提升應用程式安全性、保護應用程式資料，並讓使用者進一步瞭解及掌控自己的資料。如要進一步瞭解我們如何強化使用者防護措施，以及保護應用程式免於新威脅侵擾，請觀看 Google I/O 的這場演講。

整合 Credential Manager 與自動填入功能

從 Android 15 開始，開發人員可以將特定檢視畫面 (例如使用者名稱或密碼欄位) 與憑證管理工具要求連結，在登入程序中更輕鬆地提供客製化使用者體驗。當使用者將焦點放在其中一個檢視畫面時，系統會將相應要求傳送至憑證管理工具。系統會從各個供應器匯總產生的憑證，並顯示在自動填入備用 UI 中，例如內嵌建議或下拉式建議。Jetpack androidx.credentials 程式庫是開發人員偏好的端點，不久後將可在 Android 15 以上版本中進一步強化這項功能。

整合單鍵註冊和登入功能與生物特徵辨識提示功能

Credential Manager 會將生物特徵辨識提示訊息整合至憑證建立和登入程序，因此提供者不必管理生物特徵辨識提示訊息。因此，憑證提供者只需要專注於建立和取得流量的結果，並透過生物特徵辨識流程結果增強。這個簡化程序可建立更有效率且精簡的憑證建立和擷取程序。

端對端加密的金鑰管理

我們在 Android 15 中推出 E2eeContactKeysManager，這項功能可提供 OS 層級 API 來儲存加密編譯公用金鑰，方便在 Android 應用程式中進行端對端加密 (E2EE)。

E2eeContactKeysManager 旨在整合平台聯絡人應用程式，為使用者提供集中式方式，管理及驗證聯絡人的公開金鑰。

內容 URI 的權限檢查

Android 15 introduces a 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 新增了多項功能，可提升使用者無障礙體驗。

Better Braille

In Android 15, we've made it possible for TalkBack to support Braille displays that are using the HID standard over both USB and secure Bluetooth.

This standard, much like the one used by mice and keyboards, will help Android support a wider range of Braille displays over time.

國際化

Android 15 新增的功能和特性可提升使用者體驗，讓裝置在不同語言環境下都能順暢運作。

中日韓變數字型

從 Android 15 開始，適用於中文、日文和韓文 (CJK) 的字型檔案 NotoSansCJK，現在已變成可變字型。變數字型為中日韓語言開啟了創意排版的可能性。設計人員可以探索更多樣式，並製作出以往難以或無法達成的視覺效果強烈版面配置。

字元間的對齊方式

從 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 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 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`.

其他日文變體假名字型

In Android 15, a 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.

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

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

功能與 API 總覽 透過集合功能整理內容 你可以依據偏好儲存及分類內容。

相機和媒體

低光源增強

應用程式內攝影機控制項

HDR 動態範圍控制

音量控制

虛擬 MIDI 2.0 裝置

更有效率的 AV1 軟體解碼

開發人員工作效率和工具

OpenJDK 17 更新

PDF 改善項目

自動切換語言的改良功能

改良的 OpenType 變數字型 API

Kotlin

Java

Kotlin

Java

精細的換行符號控制項

封存應用程式

使用開發人員選項在裝置上啟用 16 KB 模式

圖形

更新 Android 的 GPU 存取權

The Android ANGLE on Vulkan roadmap

Recommended next steps

Canvas 改善項目

效能和電池

ApplicationStartInfo API

應用程式大小詳細資訊

應用程式管理的剖析

SQLite 資料庫改善項目

Android 動態效能架構更新

隱私權

螢幕錄影偵測

擴充 IntentFilter 功能

私人空間

查詢「選取的相片存取權」的最新使用者選取項目

Kotlin

Java

Android 版 Privacy Sandbox

健康資料同步

應用程式分享螢幕畫面

使用者體驗和系統 UI

使用 Generated Previews API 取得更豐富的小工具預覽畫面

Push API

When to call setWidgetPreview

子母畫面

更完善的「零打擾」規則

為通知管道設定 VibrationEffect

媒體投影狀態列資訊方塊和自動停止

大螢幕和板型規格

改善大螢幕多工處理功能

支援封面螢幕

連線能力

衛星支援

更流暢的 NFC 體驗

錢包角色

安全性

整合 Credential Manager 與自動填入功能

整合單鍵註冊和登入功能與生物特徵辨識提示功能

端對端加密的金鑰管理

內容 URI 的權限檢查

無障礙設定

Better Braille

國際化

中日韓變數字型

字元間的對齊方式

自動換行設定

其他日文變體假名字型

功能與 API 總覽

When to call `setWidgetPreview`