Google 會運用 AI 技術將內容翻譯成你偏好的語言，但可能會出錯。

功能與 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 新增了擴充功能，可進一步控管相機硬體及其在支援裝置上的演算法：

進階閃光燈強度調整功能：在拍攝相片時，可在 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 裝置，並透過通用 MIDI 封包 (UMP) 進行通訊。Android 15 將 UMP 支援擴展至虛擬 MIDI 應用程式，讓合成應用程式可透過虛擬 MIDI 2.0 裝置控制合成器應用程式，就像使用 USB MIDI 2.0 裝置一樣。

更有效率的 AV1 軟體解碼

dav1d logo

dav1d, the popular AV1 software decoder from VideoLAN is 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.

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

畫布功能改善項目

Android 15 continues our modernization of Android's Canvas graphics system with additional 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 類別，可讓您從應用程式內收集剖析資訊，例如記憶體快照資料、記憶體快照資料、堆疊取樣等。它會為您的應用程式提供回呼，並提供標記來識別輸出檔案，該檔案會傳送至應用程式的檔案目錄。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 continues our investment in the Android Dynamic Performance Framework (ADPF), a set of APIs that allow games and performance intensive apps to interact more directly with power and thermal systems of Android devices. On supported devices, Android 15 adds ADPF capabilities:

A power-efficiency mode for hint sessions to indicate that their associated threads should prefer power saving over performance, great for long-running background workloads.
GPU and CPU work durations can both be reported in hint sessions, allowing the system to adjust CPU and GPU frequencies together to best meet workload demands.
Thermal headroom thresholds to interpret possible thermal throttling status based on headroom prediction.

To learn more about how to use ADPF in your apps and games, head over to the documentation.

隱私權

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 <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 android:query and android:fragment attributes.

Here's an example of the AndroidManifest syntax:

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

私人空間

使用者可透過私人空間在裝置上建立獨立空間，在多一層驗證機制下，隱藏敏感應用程式，防止他人窺探。私人空間會使用個別的使用者設定檔。使用者可以選擇使用裝置鎖定或專屬的鎖定因素來解鎖私人空間。

私人空間中的應用程式會顯示在啟動器的獨立容器中，並在私人空間鎖定時，隱藏在近期使用畫面、通知、設定和其他應用程式中。使用者產生和下載的內容 (例如媒體或檔案) 和帳戶會在私人空間和主空間之間分開。在私人空間解鎖後，您可以使用系統 Sharesheet 和相片挑選工具，讓應用程式存取不同空間的內容。

使用者無法將現有應用程式和相關資料移至私人空間。相反地，使用者可在私人空間中選取安裝選項，然後使用所需的應用程式商店安裝應用程式。私人空間中的應用程式會以個別副本的形式安裝，與主要空間中的任何應用程式不同 (同一個應用程式的新副本)。

使用者鎖定私人空間時，系統會停止設定檔。設定檔停止時，私人空間中的應用程式就會停止運作，無法執行前景或背景活動，包括顯示通知。

建議您使用私人空間測試應用程式，確保應用程式能正常運作，尤其是如果您的應用程式屬於下列任一類別：

應用程式包含工作資料夾的邏輯，假設應用程式的任何已安裝副本 (不在主要資料夾中) 都位於工作資料夾中。
醫療應用程式
啟動器應用程式
應用程式商店應用程式

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

現在應用程式只能醒目顯示最近選取的相片和影片授予媒體的部分存取權。這項功能可改善經常要求存取相片和影片存取權的應用程式使用者體驗。如要在應用程式中使用這項功能，請啟用查詢 MediaStore 時有 QUERY_ARG_LATEST_SELECTION_ONLY 引數透過 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 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.

健康資料同步

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 supports app 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 app screen sharing experience. Note that for apps targeting Android 14 (API level 34) or higher, user consent is 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:

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 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 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 的板型規格，包括大螢幕、翻蓋式和折疊式裝置。

改善大螢幕多工處理功能

Users can save their favorite split-screen app combinations for
quick access

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.

支援封面螢幕

應用程式可以宣告 Android 15 使用的屬性，讓 Application 或 Activity 顯示在支援翻轉裝置的小型封面螢幕上。這些螢幕太小，無法視為 Android 應用程式可執行的相容目標，但您的應用程式可以選擇支援這些螢幕，讓應用程式可在更多地方使用。

連線能力

Android 15 更新了平台，讓您的應用程式能使用通訊和無線技術的最新進展。

衛星支援

Android 15 持續擴大平台支援範圍，包括衛星連線，以及包含一些 UI 元素，確保衛星連線環境。

應用程式可以使用 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 register a filter 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 預設感應式付款設定。使用者可以依序前往「設定」>「應用程式」>「預設應用程式」，管理錢包角色持有人。

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

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

安全性

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

整合 Credential Manager 與自動填入功能

Starting with Android 15, developers can link specific views like username or password fields with Credential Manager requests, making it easier to provide a tailored user experience during the sign-in process. When the user focuses on one of these views, a corresponding request is sent to Credential Manager. The resulting credentials are aggregated across providers and displayed in autofill fallback UIs, such as inline suggestions or drop-down suggestions. The Jetpack androidx.credentials library is the preferred endpoint for developers to use and will soon be available to further enhance this feature in Android 15 and higher.

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

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，現在已變成可變字型。變數字型為中日韓語言開啟了創意排版的可能性。設計人員可以探索更多樣式，並製作出以往難以或無法達成的視覺效果強烈版面配置。

字元間距對齊

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

Layout for English text using the JUSTIFICATION_MODE_INTER_CHARACTER.

自動換行設定

Android 已開始在下列國家/地區支援日文和韓文的詞組換行符號： Android 13 (API 級別 33)。不過，雖然使用詞組的分行符號改善了簡短的文字易讀性，對長行文字的效果不佳。在 Android 15 中，應用程式只能針對短行套用以詞組為準的換行符號方法是使用 LINE_BREAK_WORD_STYLE_AUTO 如果有需要 SQL 指令的分析工作負載則 BigQuery 可能是最佳選擇這個選項可為文字選取最合適的字詞樣式選項。

以短行文字來說，使用以詞組為基準的換行符號，運作方式也相同如 LINE_BREAK_WORD_STYLE_PHRASE，如如下圖片：

如果是簡短的文字，`LINE_BREAK_WORD_STYLE_AUTO` 套用詞組換行，讓文字更清晰易讀。這與套用 `LINE_BREAK_WORD_STYLE_PHRASE`。

對於較長的文字，LINE_BREAK_WORD_STYLE_AUTO 會使用 no 斷行文字樣式，功能與 LINE_BREAK_WORD_STYLE_NONE，如如下圖片：

對於長行文字，`LINE_BREAK_WORD_STYLE_AUTO` 套用不換行的文字樣式，讓文字更清晰易讀。這與套用 `LINE_BREAK_WORD_STYLE_NONE`。

其他日文變體假名字型

在 Android 15 中，這是日文平假名 (也稱為 Hentaigana) 的字型檔案系統預設會整合在一起由於平假名字元的形狀獨特，因此可為圖像或設計增添獨特風格，同時也能確保古代日本文件的正確傳遞和理解。

VideoLAN cone Copyright (c) 1996-2010 VideoLAN. This logo or a modified version may be used or modified by anyone to refer to the VideoLAN project or any product developed by the VideoLAN team, but does not indicate endorsement by the project.

Vulkan and the Vulkan logo are registered trademarks of the Khronos Group Inc.

OpenGL is a registered trademark and the OpenGL ES logo is a trademark of Hewlett Packard Enterprise used by permission by 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

畫布功能改善項目

效能和電池

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`