本頁面由 Cloud Translation API 翻譯而成。

行為變更：指定 Android 15 以上版本的應用程式

和先前的版本一樣，Android 15 也包含可能影響運作的行為變更下列行為變更僅適用於符合下列條件的應用程式：指定 Android 15 以上版本。如果您的應用程式指定 Android 15 以上版本您必須修改應用程式，才能正確支援這些行為，

請務必查看影響所有應用程式的行為變更清單在 Android 15 上執行，無論應用程式的 targetSdkVersion 為何。

核心功能

Android 15 修改或擴充 Android 系統的各種核心功能。

前景服務變更

針對 Android 15 的前景服務，我們將進行下列變更。

同步處理前景服務逾時行為
新增媒體處理前景服務類型
BOOT_COMPLETED 廣播接收器啟動前景服務的相關限制
應用程式擁有 SYSTEM_ALERT_WINDOW 權限時，啟動前景服務的限制

資料同步處理前景服務逾時行為

Android 15 introduces a new timeout behavior to dataSync for apps targeting Android 15 (API level 35) or higher. This behavior also applies to the new mediaProcessing foreground service type.

The system permits an app's dataSync services to run for a total of 6 hours in a 24-hour period, after which the system calls the running service's Service.onTimeout(int, int) method (introduced in Android 15). At this time, the service has a few seconds to call Service.stopSelf(). When Service.onTimeout() is called, the service is no longer considered a foreground service. If the service does not call Service.stopSelf(), the system throws an internal exception. The exception is logged in Logcat with the following message:

Fatal Exception: android.app.RemoteServiceException: "A foreground service of
type dataSync did not stop within its timeout: [component name]"

To avoid problems with this behavior change, you can do one or more of the following:

Have your service implement the new Service.onTimeout(int, int) method. When your app receives the callback, make sure to call stopSelf() within a few seconds. (If you don't stop the app right away, the system generates a failure.)
Make sure your app's dataSync services don't run for more than a total of 6 hours in any 24-hour period (unless the user interacts with the app, resetting the timer).
Only start dataSync foreground services as a result of direct user interaction; since your app is in the foreground when the service starts, your service has the full six hours after the app goes to the background.
Instead of using a dataSync foreground service, use an alternative API.

If your app's dataSync foreground services have run for 6 hours in the last 24, you cannot start another dataSync foreground service unless the user has brought your app to the foreground (which resets the timer). If you try to start another dataSync foreground service, the system throws ForegroundServiceStartNotAllowedException with an error message like "Time limit already exhausted for foreground service type dataSync".

Testing

To test your app's behavior, you can enable data sync timeouts even if your app is not targeting Android 15 (as long as the app is running on an Android 15 device). To enable timeouts, run the following adb command:

adb shell am compat enable FGS_INTRODUCE_TIME_LIMITS your-package-name

You can also adjust the timeout period, to make it easier to test how your app behaves when the limit is reached. To set a new timeout period, run the following adb command:

adb shell device_config put activity_manager data_sync_fgs_timeout_duration duration-in-milliseconds

新增媒體處理前景服務類型

Android 15 推出了新的前景服務類型 mediaProcessing。這個服務類型適用於轉碼媒體檔案這類作業。適用對象例如媒體應用程式可能會下載音訊檔案播放不同格式的內容你可以使用 mediaProcessing 前景服務，這樣即使應用程式位於背景。

系統允許應用程式的 mediaProcessing 服務執行共計 6 次 24 小時制，然後系統就會呼叫正在執行服務的 Service.onTimeout(int, int) 方法 (於 Android 推出) 15)。服務目前有幾秒鐘需要呼叫 Service.stopSelf()。如果服務未呼叫 Service.stopSelf() 時，系統會擲回內部例外狀況。系統會透過以下訊息在 Logcat 中記錄例外狀況：

Fatal Exception: android.app.RemoteServiceException: "A foreground service of
type mediaProcessing did not stop within its timeout: [component name]"

為避免例外狀況，您可以採取下列其中一種做法：

讓您的服務實作新的 Service.onTimeout(int, int) 方法。應用程式收到回呼時，請務必在stopSelf() 幾秒內。(如果您沒有立即停止應用程式，系統會自動產生新的失敗。)
確認應用程式的 mediaProcessing 服務僅在總計每 24 小時為 6 小時 (除非使用者與應用程式互動，重設計時器)。
只因直接使用者而啟動 mediaProcessing 前景服務互動；因為您的應用程式在服務啟動時位於前景。並在應用程式進入背景的六小時後，獲得完整的服務存取權。
不使用 mediaProcessing 前景服務，而是改用替代選項 API，例如 WorkManager

如果應用程式的 mediaProcessing 前景服務已在最後 24，您必須mediaProcessing啟動另一項前景服務，除非使用者將應用程式移至前景 (重設計時器)。如果發生以下情況：嘗試啟動另一項 mediaProcessing 前景服務，系統將擲回 ForegroundServiceStartNotAllowedException 並顯示「前景服務時間已達上限」等錯誤訊息輸入 mediaProcessing」。

如要進一步瞭解 mediaProcessing 服務類型，請參閱 Android 15 的前景服務類型：媒體處理。

測試

如要測試應用程式的行為，您可以啟用媒體處理逾時 (即使應用程式不是以 Android 15 為目標 (只要應用程式是在 Android 15 裝置)。如要啟用逾時，請執行下列 adb 指令：

adb shell am compat enable FGS_INTRODUCE_TIME_LIMITS your-package-name

此外，您也可以調整逾時期限，方便測試達到限制時，應用程式就會繼續運作。如要設定新的逾時期限，請執行以下 adb 指令：

adb shell device_config put activity_manager media_processing_fgs_timeout_duration duration-in-milliseconds

`BOOT_COMPLETED` 個啟動前景服務的廣播接收器限制

There are new restrictions on BOOT_COMPLETED broadcast receivers launching foreground services. BOOT_COMPLETED receivers are not allowed to launch the following types of foreground services:

dataSync
camera
mediaPlayback
phoneCall
mediaProjection
microphone (this restriction has been in place for microphone since Android 14)

If a BOOT_COMPLETED receiver tries to launch any of those types of foreground services, the system throws ForegroundServiceStartNotAllowedException.

Testing

To test your app's behavior, you can enable these new restrictions even if your app is not targeting Android 15 (as long as the app is running on an Android 15 device). Run the following adb command:

adb shell am compat enable FGS_BOOT_COMPLETED_RESTRICTIONS your-package-name

To send a BOOT_COMPLETED broadcast without restarting the device, run the following adb command:

adb shell am broadcast -a android.intent.action.BOOT_COMPLETED your-package-name

當應用程式擁有 `SYSTEM_ALERT_WINDOW` 權限時，啟動前景服務的限制

Previously, if an app held the SYSTEM_ALERT_WINDOW permission, it could launch a foreground service even if the app was currently in the background (as discussed in exemptions from background start restrictions).

If an app targets Android 15, this exemption is now narrower. The app now needs to have the SYSTEM_ALERT_WINDOW permission and also have a visible overlay window. That is, the app needs to first launch a TYPE_APPLICATION_OVERLAY window and the window needs to be visible before you start a foreground service.

If your app attempts to start a foreground service from the background without meeting these new requirements (and it does not have some other exemption), the system throws ForegroundServiceStartNotAllowedException.

If your app declares the SYSTEM_ALERT_WINDOW permission and launches foreground services from the background, it may be affected by this change. If your app gets a ForegroundServiceStartNotAllowedException, check your app's order of operations and make sure your app already has an active overlay window before it attempts to start a foreground service from the background. You can check if your overlay window is currently visible by calling View.getWindowVisibility(), or you can override View.onWindowVisibilityChanged() to get notified whenever the visibility changes.

Testing

To test your app's behavior, you can enable these new restrictions even if your app is not targeting Android 15 (as long as the app is running on an Android 15 device). To enable these new restrictions on starting foreground services from the background, run the following adb command:

adb shell am compat enable FGS_SAW_RESTRICTIONS your-package-name

應用程式何時可修改「零打擾」模式的全域狀態異動

以 Android 15 為目標的應用程式無法再透過修改使用者設定或關閉 DND 模式，變更裝置上「零打擾」(DND) 模式的全域狀態或政策。而是必須為應用程式提供 AutomaticZenRule，系統會將此系統結合至全域政策和目前最嚴格的政策，如果呼叫先前影響全域狀態 (setInterruptionFilter、setNotificationPolicy) 的現有 API，會導致隱式 AutomaticZenRule 建立或更新，系統會根據這些 API 呼叫的呼叫週期開啟或關閉這項功能。

請注意，當應用程式呼叫 setInterruptionFilter(INTERRUPTION_FILTER_ALL)，並預期呼叫來停用擁有者先前啟用的 AutomaticZenRule 時，這項變更只會影響可觀測的行為。

OpenJDK API 變更

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

Some of these changes can affect app compatibility for apps targeting Android 15 (API level 35):

Changes to string formatting APIs: Validation of argument index, flags, width, and precision are now more strict when using the following String.format() and Formatter.format() APIs:
For example, the following exception is thrown when an argument index of 0 is used (%0 in the format string):
```
IllegalFormatArgumentIndexException: Illegal format argument index = 0
```
In this case, the issue can be fixed by using an argument index of 1 (%1 in the format string).
Changes to component type of Arrays.asList(...).toArray(): When using Arrays.asList(...).toArray(), the component type of the resulting array is now an Object—not the type of the underlying array's elements. So the following code throws a ClassCastException:
```
String[] elements = (String[]) Arrays.asList("one", "two").toArray();
```
For this case, to preserve String as the component type in the resulting array, you could use Collection.toArray(Object[]) instead:
```
String[] elements = Arrays.asList("two", "one").toArray(new String[0]);
```
Changes to language code handling: When using the Locale API, language codes for Hebrew, Yiddish, and Indonesian are no longer converted to their obsolete forms (Hebrew: iw, Yiddish: ji, and Indonesian: in). When specifying the language code for one of these locales, use the codes from ISO 639-1 instead (Hebrew: he, Yiddish: yi, and Indonesian: id).
Changes to random int sequences: Following the changes made in https://bugs.openjdk.org/browse/JDK-8301574, the following Random.ints() methods now return a different sequence of numbers than the Random.nextInt() methods do:
Generally, this change shouldn't result in app-breaking behavior, but your code shouldn't expect the sequence generated from Random.ints() methods to match Random.nextInt().

The new SequencedCollection API can affect your app's compatibility after you update compileSdk in your app's build configuration to use Android 15 (API level 35):

Collision with MutableList.removeFirst() and MutableList.removeLast() extension functions in kotlin-stdlib

The List type in Java is mapped to the MutableList type in Kotlin. Because the List.removeFirst() and List.removeLast() APIs have been introduced in Android 15 (API level 35), the Kotlin compiler resolves function calls, for example list.removeFirst(), statically to the new List APIs instead of to the extension functions in kotlin-stdlib.

If an app is re-compiled with compileSdk set to 35 and minSdk set to 34 or lower, and then the app is run on Android 14 and lower, a runtime error is thrown:
```
java.lang.NoSuchMethodError: No virtual method
removeFirst()Ljava/lang/Object; in class Ljava/util/ArrayList;
```
The existing NewApi lint option in Android Gradle Plugin can catch these new API usages.
```
./gradlew lint

MainActivity.kt:41: Error: Call requires API level 35 (current min is 34): java.util.List#removeFirst [NewApi]
      list.removeFirst()
```
To fix the runtime exception and lint errors, the removeFirst() and removeLast() function calls can be replaced with removeAt(0) and removeAt(list.lastIndex) respectively in Kotlin. If you're using Android Studio Ladybug | 2024.1.3 or higher, it also provides a quick fix option for these errors.

Consider removing @SuppressLint("NewApi") and lintOptions { disable 'NewApi' } if the lint option has been disabled.

Collision with other methods in Java

New methods have been added into the existing types, for example, List and Deque. These new methods might not be compatible with the methods with the same name and argument types in other interfaces and classes. In the case of a method signature collision with incompatibility, the javac compiler outputs a build-time error. For example:

Example error 1:

javac MyList.java

MyList.java:135: error: removeLast() in MyList cannot implement removeLast() in List
  public void removeLast() {
              ^
  return type void is not compatible with Object
  where E is a type-variable:
    E extends Object declared in interface List

Example error 2:

javac MyList.java

MyList.java:7: error: types Deque<Object> and List<Object> are incompatible;
public class MyList implements  List<Object>, Deque<Object> {
  both define reversed(), but with unrelated return types
1 error

Example error 3:

javac MyList.java

MyList.java:43: error: types List<E#1> and MyInterface<E#2> are incompatible;
public static class MyList implements List<Object>, MyInterface<Object> {
  class MyList inherits unrelated defaults for getFirst() from types List and MyInterface
  where E#1,E#2 are type-variables:
    E#1 extends Object declared in interface List
    E#2 extends Object declared in interface MyInterface
1 error

To fix these build errors, the class implementing these interfaces should override the method with a compatible return type. For example:

@Override
public Object getFirst() {
    return List.super.getFirst();
}

安全性

Android 15 包含促進系統安全性的調整，有助於保護應用程式以及惡意應用程式的使用者

啟動安全的背景活動

Android 15 protects users from malicious apps and gives them more control over their devices by adding changes that prevent malicious background apps from bringing other apps to the foreground, elevating their privileges, and abusing user interaction. Background activity launches have been restricted since Android 10 (API level 29).

Other changes

In addition to the restriction for UID matching, these other changes are also included:

Change PendingIntent creators to block background activity launches by default. This helps prevent apps from accidentally creating a PendingIntent that could be abused by malicious actors.
Don't bring an app to the foreground unless the PendingIntent sender allows it. This change aims to prevent malicious apps from abusing the ability to start activities in the background. By default, apps are not allowed to bring the task stack to the foreground unless the creator allows background activity launch privileges or the sender has background activity launch privileges.
Control how the top activity of a task stack can finish its task. If the top activity finishes a task, Android will go back to whichever task was last active. Moreover, if a non-top activity finishes its task, Android will go back to the home screen; it won't block the finish of this non-top activity.
Prevent launching arbitrary activities from other apps into your own task. This change prevents malicious apps from phishing users by creating activities that appear to be from other apps.
Block non-visible windows from being considered for background activity launches. This helps prevent malicious apps from abusing background activity launches to display unwanted or malicious content to users.

更安全的意圖

Android 15 導入了新的安全措施，提高意圖的安全性和實用性穩健成長這些異動旨在防範潛在的安全漏洞，濫用可能遭到惡意應用程式攻擊的意圖。在這方面 Android 15 的意圖安全性提升：

比對目標意圖篩選器：指定特定元件的意圖必須準確符合目標的意圖篩選器規格如果傳送意圖啟動其他應用程式的活動，目標意圖元件對應至接收活動宣告的意圖篩選器
意圖必須包含動作：系統將不再比對不含動作的意圖任何意圖篩選器都行這表示用於啟動活動或服務必須明確定義動作
待處理意圖：待處理意圖的創作者為 視為包含意圖的寄件者，而非待處理意圖的傳送者意願

，瞭解如何調查及移除這項存取權。

Kotlin


fun onCreate() {
    StrictMode.setVmPolicy(VmPolicy.Builder()
        .detectUnsafeIntentLaunch()
        .build()
    )
}

Java


public void onCreate() {
    StrictMode.setVmPolicy(new VmPolicy.Builder()
            .detectUnsafeIntentLaunch()
            .build());
}

使用者體驗和系統 UI

Android 15 包含幾項變更，目的是創造更一致的體驗。直覺的使用者體驗

視窗插邊變更

Android 15 的視窗插邊有兩項變更：根據預設，系統會強制執行無邊框設計，以及設定變更 (例如系統列的預設設定)。

邊緣到邊緣強制執行

在搭載 Android 15 的裝置上，應用程式預設為無邊框設計指定 Android 15 (API 級別 35) 為目標。

採用無邊框設計，指定 Android 15 (API 級別 35) 的應用程式安裝在 Android 15 裝置上這個應用程式大多使用 Material 3 Compose 元件系統會自動套用插邊這個畫面不會受 Android 15 強制採用的無邊框措施。

這項破壞性變更可能會對應用程式的 UI 造成負面影響。變更會影響下列 UI 區域：

手勢控點導覽列
- 預設為透明。
- 已停用底部偏移，因此內容會在系統導覽後繪製除非套用插邊
- setNavigationBarColor和R.attr#navigationBarColor是且不會影響手勢操作模式。
- setNavigationBarContrastEnforced 和 R.attr#navigationBarContrastEnforced 繼續於以及手勢操作
三按鈕操作
- 根據預設，透明度會設為 80%，色彩可能會與視窗相符背景。
- 已停用底部偏移，因此內容會在系統導覽列後方繪製除非套用了插邊
- setNavigationBarColor和R.attr#navigationBarColor是設定為符合視窗背景。視窗背景必須是顏色可繪項目，才能套用此預設值。這個 API 但會繼續影響三按鈕操作
- setNavigationBarContrastEnforced 和根據預設，R.attr#navigationBarContrastEnforced 為 true，因此系統會新增三按鈕操作模式下的不透明背景：80%。
狀態列
- 預設為透明。
- 系統會停用頂部位移，因此內容會在狀態列後方繪製，除非則套用插邊。
- setStatusBarColor和R.attr#statusBarColor是並且對 Android 15 沒有任何影響。
- setStatusBarContrastEnforced 和 R.attr#statusBarContrastEnforced 已淘汰，但仍有在 Android 15 上生效
螢幕凹口
- 非浮動視窗的值必須為 layoutInDisplayCutoutMode LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS。SHORT_EDGES、NEVER和系統會將 DEFAULT 解讀為 ALWAYS，因此使用者不會看見黑色顯示出「無邊框」提示。

以下範例是指定前後對照的應用程式 Android 15 (API 級別 35) 及套用插邊前後的版本。

，瞭解如何調查及移除這項存取權。

採用無邊框設計，指定 Android 15 (API 級別 35) 的應用程式安裝在 Android 15 裝置上不過，許多元素現在會由狀態隱藏工具列、三按鈕導覽列，或螢幕凹口。採取無邊框措施隱藏的 UI 包含 Material 2 頂端應用程式列、懸浮動作按鈕和清單項目。

，瞭解如何調查及移除這項存取權。

要檢查應用程式是否已採用無邊框設計

如果您的應用程式已經採用無邊框設計，並套用插邊，那麼您影響程度最高，不過下列情況除外。即使您認為您不妨測試應用程式。

您有一個非浮動視窗，例如 Activity，在使用 SHORT_EDGES、NEVER 或 DEFAULT 取代 LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS。如果您的應用程式在啟動時異常終止，這可能是因為啟動畫面所致您可將核心肌群 splashscreen 依附元件至 1.2.0-alpha01 或之後設定 window.attributes.layoutInDisplayCutoutMode = WindowManager.LayoutInDisplayCutoutMode.always。
部分流量較低的畫面可能會遭遮蔽，驗證這些較少造訪的畫面沒有遮蔽 UI。低流量畫麵包括：
- 登入或登入畫面
- 設定頁面

檢查應用程式是否為無邊框應用程式的方法

如果您的應用程式尚未採用無邊框設計，那麼您很有可能受到影響。於除了採用無邊框設計的應用程式相關情境外請考慮以下幾點：

如果您的應用程式使用 Material 3 元件 ( androidx.compose.material3) 在 Compose 中，例如 TopAppBar BottomAppBar 和 NavigationBar，這些元件可能不會自動處理插邊。
如果應用程式使用 Material 2 元件 ( androidx.compose.material) 就不會自動處理插邊不過，您可以存取插邊並手動套用在 androidx.compose.material 1.6.0 中然後，使用 windowInsets 參數手動套用插邊 BottomAppBar、TopAppBar、 BottomNavigation和 NavigationRail。同樣地，對以下項目使用 contentWindowInsets 參數： Scaffold。
如果應用程式使用檢視畫面和 Material 元件 (com.google.android.material)，多數以檢視畫面為基礎的 Material BottomNavigationView、BottomAppBar 等元件 NavigationRailView 或 NavigationView，處理插邊，且不需要其他作業不過，您需要新增 android:fitsSystemWindows="true" 若使用 AppBarLayout。
如果是自訂可組合項，請手動將插邊套用為邊框間距。如果您的在 Scaffold 內的內容，您可以使用 Scaffold 取用插邊邊框間距值。否則，請使用 WindowInsets。
如果應用程式使用 View 和 BottomSheet、SideSheet 或自訂來套用邊框間距 ViewCompat.setOnApplyWindowInsetsListener。適用對象 RecyclerView，使用這個事件監聽器套用邊框間距，同時新增 clipToPadding="false"。

檢查應用程式是否必須提供自訂背景保護的事項

如果您的應用程式必須在三按鈕操作模式下提供自訂背景保護措施狀態列時，應用程式應將可組合項或檢視畫面放置在系統列後方使用 WindowInsets.Type#tappableElement() 取得 3 按鈕導覽列高度或 WindowInsets.Type#statusBars。

其他無邊框資源

詳情請參閱「Edge to Edge View」和「Edge to Edge Compose」指南。

已淘汰的 API

下列 API 現已淘汰：

穩定設定

If your app targets Android 15 (API level 35) or higher, Configuration no longer excludes the system bars. If you use the screen size in the Configuration class for layout calculation, you should replace it with better alternatives like an appropriate ViewGroup, WindowInsets, or WindowMetricsCalculator depending on your need.

Configuration has been available since API 1. It is typically obtained from Activity.onConfigurationChanged. It provides information like window density, orientation, and sizes. One important characteristic about the window sizes returned from Configuration is that it previously excluded the system bars.

The configuration size is typically used for resource selection, such as /res/layout-h500dp, and this is still a valid use case. However, using it for layout calculation has always been discouraged. If you do so, you should move away from it now. You should replace the use of Configuration with something more suitable depending on your use case.

If you use it to calculate the layout, use an appropriate ViewGroup, such as CoordinatorLayout or ConstraintLayout. If you use it to determine the height of the system navbar, use WindowInsets. If you want to know the current size of your app window, use computeCurrentWindowMetrics.

The following list describes the fields affected by this change:

Configuration.screenWidthDp and screenHeightDp sizes no longer exclude the system bars.
Configuration.smallestScreenWidthDp is indirectly affected by changes to screenWidthDp and screenHeightDp.
Configuration.orientation is indirectly affected by changes to screenWidthDp and screenHeightDp on close-to-square devices.
Display.getSize(Point) is indirectly affected by the changes in Configuration. This was deprecated beginning in API level 30.
Display.getMetrics() has already worked like this since API level 33.

routeTextHeight 屬性預設為 true

For apps targeting Android 15 (API level 35), the elegantTextHeight TextView attribute becomes true by default, replacing the compact font used by default with some scripts that have large vertical metrics with one that is much more readable. The compact font was introduced to prevent breaking layouts; Android 13 (API level 33) prevents many of these breakages by allowing the text layout to stretch the vertical height utilizing the fallbackLineSpacing attribute.

In Android 15, the compact font still remains in the system, so your app can set elegantTextHeight to false to get the same behavior as before, but it is unlikely to be supported in upcoming releases. So, if your app supports the following scripts: Arabic, Lao, Myanmar, Tamil, Gujarati, Kannada, Malayalam, Odia, Telugu or Thai, test your app by setting elegantTextHeight to true.

`elegantTextHeight` behavior for apps targeting Android 14 (API level 34) and lower.

`elegantTextHeight` behavior for apps targeting Android 15.

針對複雜的字母形狀變更 TextView 寬度

而在舊版 Android 中，部分文字敘述的字型或語言複雜的形狀可能會畫出前一個字元區域或下一個字元區域的字母。在某些情況下，這類字母會在開頭或結束位置遭到截斷。自 Android 15 起，TextView 會分配寬度，以便繪製足夠的空間以便應用程式向左側避免剪輯。

這項變更會影響 TextView 決定寬度的方式，因此 TextView 在預設情況下，如果應用程式指定 Android 15 (API 級別 35) 或更高。您可以呼叫 TextView 上的 setUseBoundsForWidth API。

由於新增左側邊框間距可能會導致現有版面配置無法對齊依預設，即使指定 Android 15 以上版本的應用程式，也不會新增邊框間距。但是，您可以透過呼叫 setShiftDrawingOffsetForStartOverhang。

以下範例說明這些變更如何改善部分應用程式的文字版面配置以及字型和語言

標準版面配置，顯示遞迴字型的英文文字。部分字母遭到截斷。以下是對應的 XML：

<TextView
    android:fontFamily="cursive"
    android:text="java" />

相同英文文字的版面配置，寬度和加寬邊框間距。以下是對應的 XML：

<TextView
    android:fontFamily="cursive"
    android:text="java"
    android:useBoundsForWidth="true"
    android:shiftDrawingOffsetForStartOverhang="true" />

泰文標準版面配置。部分字母遭到截斷。以下是對應的 XML：

<TextView
    android:text="คอมพิวเตอร์" />

相同泰文文字的版面配置，如果增加寬度和邊框間距。以下是對應的 XML：

<TextView
    android:text="คอมพิวเตอร์"
    android:useBoundsForWidth="true"
    android:shiftDrawingOffsetForStartOverhang="true" />

EditText 可感知本地化的預設行高

In previous versions of Android, the text layout stretched the height of the text to meet the line height of the font that matched the current locale. For example, if the content was in Japanese, because the line height of the Japanese font is slightly larger than the one of a Latin font, the height of the text became slightly larger. However, despite these differences in line heights, the EditText element was sized uniformly, regardless of the locale being used, as illustrated in the following image:

Three boxes representing `EditText` elements that can contain text from English (en), Japanese (ja), and Burmese (my). The height of the `EditText` is the same, even though these languages have different line heights from each other.

For apps targeting Android 15 (API level 35), a minimum line height is now reserved for EditText to match the reference font for the specified Locale, as shown in the following image:

Three boxes representing `EditText` elements that can contain text from English (en), Japanese (ja), and Burmese (my). The height of the `EditText` now includes space to accommodate the default line height for these languages' fonts.

If needed, your app can restore the previous behavior by specifying the useLocalePreferredLineHeightForMinimum attribute to false, and your app can set custom minimum vertical metrics using the setMinimumFontMetrics API in Kotlin and Java.

相機與媒體

Android 15 針對應用程式的相機和媒體行為進行下列變更並指定 Android 15 以上版本為目標。

要求音訊焦點的限制

以 Android 15 為目標的應用程式必須是頂層應用程式或執行前景服務，才能要求音訊焦點。如果應用程式嘗試要求焦點，但不符合上述其中一項要求，呼叫會傳回 AUDIOFOCUS_REQUEST_FAILED。

如要進一步瞭解音訊焦點，請參閱管理音訊焦點一文。

更新非 SDK 限制

Android 15 內含最新的受限制非 SDK 清單介面是以與 Android 開發人員合作為基礎，並採用內部測試。我們會盡可能確保公開的替代方案，然後再限制非 SDK 介面使用

如果您的應用程式並不是以 Android 15 為目標版本，則其中某些變更可能無法立即對您造成影響不過，雖然應用程式可以存取某些非 SDK 介面 (視應用程式的目標 API 級別而定)，但使用任何非 SDK 方法或欄位時，均可能面臨應用程式故障的高度風險。

如果不確定應用程式是否使用非 SDK 介面，您可以測試應用程式來確認。如果您的應用程式仰賴非 SDK 介面，則建議您開始規劃遷移至 SDK 替代方案。我們瞭解有些應用程式具備使用情境非 SDK 介面如果您除了為應用程式中的某個功能使用非 SDK 介面外，已別無他法，則應要求新的公用 API。

如要進一步瞭解此 Android 版本中的變更，請參閱 Android 15 的非 SDK 介面限制更新內容。如要進一步瞭解非 SDK 介面的一般資訊，請參閱非 SDK 介面的限制。

行為變更：指定 Android 15 以上版本的應用程式

核心功能

前景服務變更

資料同步處理前景服務逾時行為

Testing

新增媒體處理前景服務類型

測試

BOOT_COMPLETED 個啟動前景服務的廣播接收器限制

Testing

當應用程式擁有 SYSTEM_ALERT_WINDOW 權限時，啟動前景服務的限制

Testing

應用程式何時可修改「零打擾」模式的全域狀態異動

OpenJDK API 變更

安全性

啟動安全的背景活動

Other changes

更安全的意圖

Kotlin

Java

使用者體驗和系統 UI

視窗插邊變更

邊緣到邊緣強制執行

要檢查應用程式是否已採用無邊框設計

檢查應用程式是否為無邊框應用程式的方法

檢查應用程式是否必須提供自訂背景保護的事項

其他無邊框資源

已淘汰的 API

穩定設定

routeTextHeight 屬性預設為 true

針對複雜的字母形狀變更 TextView 寬度

EditText 可感知本地化的預設行高

相機與媒體

要求音訊焦點的限制

更新非 SDK 限制

`BOOT_COMPLETED` 個啟動前景服務的廣播接收器限制

當應用程式擁有 `SYSTEM_ALERT_WINDOW` 權限時，啟動前景服務的限制