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

和先前版本一樣,Android 15 也包含可能會影響應用程式的行為變更。以下行為變更僅適用於指定 Android 15 以上版本的應用程式。如果您的應用程式指定 Android 15 以上版本,建議您視情況修改應用程式,以支援這些行為。

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

核心功能

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

前景服務異動

We are making the following changes to foreground services with Android 15.

Data sync foreground service timeout behavior

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:

  1. 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.)
  2. 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).
  3. 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.
  4. 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

New media processing foreground service type

Android 15 推出了新的前景服務類型 mediaProcessing。此服務類型適合用於轉碼媒體檔案等作業。舉例來說,媒體應用程式可能會下載音訊檔案,需要將其轉換成其他格式後再播放。您可以使用 mediaProcessing 前景服務,確保即使應用程式處於背景執行狀態,轉換也能繼續進行。

系統允許應用程式的 mediaProcessing 服務在 24 小時內執行總共 6 小時,之後系統會呼叫執行中的服務 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]"

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

  1. 請讓服務實作新的 Service.onTimeout(int, int) 方法。應用程式收到回呼時,請務必在幾秒內呼叫 stopSelf()。(如果您沒有立即停止應用程式,系統會產生失敗)。
  2. 請確認應用程式的 mediaProcessing 服務在任何 24 小時內的總執行時間不超過 6 小時 (除非使用者與應用程式互動,重新設定計時器)。
  3. 只有在使用者直接互動時才啟動 mediaProcessing 前景服務;由於您的應用程式在服務啟動後位於前景,因此應用程式進入背景後,您的服務剩下六小時。
  4. 請改用 WorkManager 等其他 API,而非 mediaProcessing 前景服務。

如果應用程式的 mediaProcessing 前景服務在過去 24 小時內已執行 6 小時,您就無法啟動其他 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

Restrictions on BOOT_COMPLETED broadcast receivers launching foreground services

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:

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

Restrictions on starting foreground services while an app holds the SYSTEM_ALERT_WINDOW permission

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

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

Apps that target Android 15 (API level 35) and higher can no longer change the global state or policy of Do Not Disturb (DND) on a device (either by modifying user settings, or turning off DND mode). Instead, apps must contribute an AutomaticZenRule, which the system combines into a global policy with the existing most-restrictive-policy-wins scheme. Calls to existing APIs that previously affected global state (setInterruptionFilter, setNotificationPolicy) result in the creation or update of an implicit AutomaticZenRule, which is toggled on and off depending on the call-cycle of those API calls.

Note that this change only affects observable behavior if the app is calling setInterruptionFilter(INTERRUPTION_FILTER_ALL) and expects that call to deactivate an AutomaticZenRule that was previously activated by their owners.

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 包含多項變更,可提升系統安全性,協助保護應用程式和使用者免受惡意應用程式侵害。

受限的 TLS 版本

Android 15 會限制 TLS 1.0 和 1.1 版本的使用。這些版本先前已在 Android 中淘汰,但現在已禁止用於指定 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 introduces new optional security measures to make intents safer and more robust. These changes are aimed at preventing potential vulnerabilities and misuse of intents that can be exploited by malicious apps. There are two main improvements to the security of intents in Android 15:

  • Match target intent-filters: Intents that target specific components must accurately match the target's intent-filter specifications. If you send an intent to launch another app's activity, the target intent component needs to align with the receiving activity's declared intent-filters.
  • Intents must have actions: Intents without an action will no longer match any intent-filters. This means that intents used to start activities or services must have a clearly defined action.

In order to check how your app responds to these changes, use StrictMode in your app. To see detailed logs about Intent usage violations, add the following method:

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 有兩項與視窗內嵌相關的變更:預設會強制執行邊到邊,且有設定變更,例如系統列的預設設定。

Edge-to-edge enforcement

如果應用程式以 Android 15 (API 級別 35) 為目標版本,在搭載 Android 15 的裝置上預設會顯示無邊框模式。

以 Android 14 為目標版本,但未在 Android 15 裝置上採用無邊框模式的應用程式。


如果應用程式指定 Android 15 (API 級別 35) 為目標,且在 Android 15 裝置上採用無邊框設計,這個應用程式主要使用 Material 3 Compose 元件,可自動套用插邊。這個畫面不會受到 Android 15 無邊框強制措施的負面影響。

這項重大變更可能會對應用程式的 UI 造成負面影響。這項異動會影響下列 UI 區域:

  • 手勢控點導覽列
    • 預設為透明。
    • 底部位移已停用,因此除非套用插邊,否則內容會在系統導覽列後方繪製。
    • setNavigationBarColorR.attr#navigationBarColor 已淘汰,不會影響手勢操作模式。
    • setNavigationBarContrastEnforcedR.attr#navigationBarContrastEnforced 仍不會影響手勢操作模式。
  • 三按鈕操作
    • 預設不透明度為 80%,顏色可能與視窗背景相符。
    • 底部偏移已停用,因此內容會在系統導覽列後方繪製,除非套用插邊。
    • setNavigationBarColorR.attr#navigationBarColor 預設會設為與視窗背景相符。如要套用此預設值,視窗背景必須是顏色可繪項目。這個 API 已淘汰,但仍會影響三按鈕操作模式。
    • setNavigationBarContrastEnforcedR.attr#navigationBarContrastEnforced 預設為 true,這會在三按鈕操作列中加入 80% 不透明度的背景。
  • 狀態列
    • 預設為透明。
    • 頂端位移已停用,因此除非套用插邊,否則內容會在狀態列後方繪製。
    • setStatusBarColorR.attr#statusBarColor 已淘汰,對 Android 15 沒有影響。
    • setStatusBarContrastEnforcedR.attr#statusBarContrastEnforced 已淘汰,但仍會影響 Android 15。
  • 螢幕凹口
    • 非浮動視窗的 layoutInDisplayCutoutMode 必須為 LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYSSHORT_EDGESNEVERDEFAULT 會解讀為 ALWAYS,這樣使用者就不會看到因螢幕凹口而產生的黑邊,且畫面會顯示到螢幕邊框。

以下範例顯示應用程式在指定 Android 15 (API 級別 35) 前後,以及套用插邊前後的樣貌。

以 Android 14 為目標版本,但未在 Android 15 裝置上採用無邊框模式的應用程式。
如果應用程式指定 Android 15 (API 級別 35) 為目標,且在 Android 15 裝置上採用無邊框設計,不過,由於 Android 15 強制採用無邊框設計,許多元素現在會遭到狀態列、3 鍵導覽列或螢幕凹口遮蔽。隱藏的 UI 包括 Material 2 頂端應用程式列、懸浮動作按鈕和清單項目。
如果應用程式以 Android 15 (API 級別 35) 為目標,且在 Android 15 裝置上採用無邊框設計,並套用插邊,就不會隱藏 UI。
如果應用程式已採用無邊框設計,請檢查下列事項

如果您的應用程式已無邊框並套用插邊,則大多不會受到影響,但下列情況除外。不過,即使您認為應用程式不受影響,我們仍建議您進行測試。

  • 您有非浮動視窗,例如使用 SHORT_EDGESNEVERDEFAULT 而不是 LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYSActivity。如果應用程式在啟動時當機,可能是因為啟動畫面。您可以將核心啟動畫面依附元件升級至 1.2.0-alpha01 以上版本,或設定 window.attributes.layoutInDisplayCutoutMode = WindowManager.LayoutInDisplayCutoutMode.always
  • 可能會有流量較低的畫面,且使用者介面遭到遮蔽。確認這些較少造訪的畫面沒有遭到遮蔽的 UI。流量較低的螢幕包括:
    • 新手上路或登入畫面
    • 設定頁面
如果應用程式尚未採用無邊框設計,請檢查下列項目

如果您的應用程式尚未採用無邊框設計,很可能就會受到影響。除了已採用無邊框設計的應用程式情境,您也應考量下列事項:

  • 如果應用程式在 Compose 中使用 Material 3 元件 (androidx.compose.material3),例如 TopAppBarBottomAppBarNavigationBar,這些元件可能會不受影響,因為它們會自動處理插邊。
  • 如果應用程式使用 Compose 的 Material 2 元件 (androidx.compose.material),這類元件本身不會自動處理插邊。不過,您可以存取插邊,然後手動套用。在 androidx.compose.material 1.6.0 以上版本,請使用 windowInsets 參數,為 BottomAppBarTopAppBarBottomNavigationNavigationRail 手動套用插邊。同樣地,對 Scaffold 也是使用 contentWindowInsets 參數。
  • 如果應用程式使用 Views 和 Material 元件 (com.google.android.material),您可能不需採取額外行動,因為大多數以 Views 為基礎的 Material 元件 (例如 BottomNavigationViewBottomAppBarNavigationRailViewNavigationView) 都會處理插邊。不過,如果您使用 AppBarLayout,就需要新增 android:fitsSystemWindows="true"
  • 如果是自訂可組合函式,請手動將插邊套用為邊框間距。如果內容位於 Scaffold 內,您可以使用Scaffold 邊框間距值取用插邊。否則,請使用其中一個 WindowInsets 套用邊框間距。
  • 如果應用程式使用 Views 和 BottomSheetSideSheet 或自訂容器,請使用 ViewCompat.setOnApplyWindowInsetsListener 套用邊框間距。對於 RecyclerView,也請使用這個事件監聽器套用邊框間距,同時新增 clipToPadding="false"
如果應用程式必須提供自訂背景保護功能,請檢查下列事項

如果應用程式必須為三按鈕操作模式或狀態列提供自訂背景保護,應用程式應使用 WindowInsets.Type#tappableElement() 取得三按鈕操作模式導覽列高度或 WindowInsets.Type#statusBars,在系統列後方放置可組合函式或檢視區塊。

其他無邊框資源

如要進一步瞭解如何套用插邊,請參閱「無邊框檢視區塊」和「無邊框 Compose」指南。

已淘汰的 API

下列 API 已淘汰,但尚未停用:

下列 API 已停用:

Stable configuration

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:

elegantTextHeight 屬性預設為 true

針對指定 Android 15 (API 級別 35) 的應用程式,elegantTextHeight TextView 屬性預設會變成 true,將預設使用的緊湊字型取代為具有大型垂直指標的某些指令碼,以便更容易閱讀。我們推出了精簡字型,以免版面配置中斷;Android 13 (API 級別 33) 允許文字版面配置利用 fallbackLineSpacing 屬性拉長垂直高度,藉此避免許多這類中斷情形。

在 Android 15 中,系統仍會保留精簡字型,因此應用程式可以將 elegantTextHeight 設為 false,以便取得與先前相同的行為,但未來版本不太可能支援這項功能。因此,如果您的應用程式支援下列文字:阿拉伯文、老撾文、緬甸文、泰米爾文、古吉拉特文、卡納達文、馬拉雅拉姆文、奧里雅文、泰盧固文或泰文,請將 elegantTextHeight 設為 true 來測試應用程式。

elegantTextHeight 指定 Android 14 (API 級別 34) 以下版本為目標版本的應用程式行為。
elegantTextHeight 指定 Android 15 為目標版本的應用程式行為。

複雜字母形狀的 TextView 寬度變化

In previous versions of Android, some cursive fonts or languages that have complex shaping might draw the letters in the previous or next character's area. In some cases, such letters were clipped at the beginning or ending position. Starting in Android 15, a TextView allocates width for drawing enough space for such letters and allows apps to request extra paddings to the left to prevent clipping.

Because this change affects how a TextView decides the width, TextView allocates more width by default if the app targets Android 15 (API level 35) or higher. You can enable or disable this behavior by calling the setUseBoundsForWidth API on TextView.

Because adding left padding might cause a misalignment for existing layouts, the padding is not added by default even for apps that target Android 15 or higher. However, you can add extra padding to preventing clipping by calling setShiftDrawingOffsetForStartOverhang.

The following examples show how these changes can improve text layout for some fonts and languages.

Standard layout for English text in a cursive font. Some of the letters are clipped. Here is the corresponding XML:

<TextView
    android:fontFamily="cursive"
    android:text="java" />
Layout for the same English text with additional width and padding. Here is the corresponding XML:

<TextView
    android:fontFamily="cursive"
    android:text="java"
    android:useBoundsForWidth="true"
    android:shiftDrawingOffsetForStartOverhang="true" />
Standard layout for Thai text. Some of the letters are clipped. Here is the corresponding XML:

<TextView
    android:text="คอมพิวเตอร์" />
Layout for the same Thai text with additional width and padding. Here is the corresponding 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 以上版本的應用程式,進行了下列攝影機和媒體行為變更。

要求音訊焦點的限制

Apps that target Android 15 (API level 35) must be the top app or running a foreground service in order to request audio focus. If an app attempts to request focus when it does not meet one of these requirements, the call returns AUDIOFOCUS_REQUEST_FAILED.

You can learn more about audio focus at Manage audio focus.

更新非 SDK 限制

基於與 Android 開發人員合作及最新的內部測試,Android 15 包含更新後的受限制非 SDK 介面清單。在限制非 SDK 介面之前,我們盡可能確保公開替代方案的可得性。

如果您的應用程式並不是以 Android 15 為目標版本,則此處所述的某些變更可能不會立即對您造成影響。不過,應用程式視目標 API 級別而定,可能可以存取某些非 SDK 介面,但使用任何非 SDK 方法或欄位時,應用程式停止運作的風險極高。

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

To learn more about the changes in this release of Android, see Updates to non-SDK interface restrictions in Android 15. To learn more about non-SDK interfaces generally, see Restrictions on non-SDK interfaces.