동작 변경사항: 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
• New media processing foreground service type
• Restrictions on BOOT_COMPLETED broadcast receivers launching foreground services
• Restrictions on starting foreground services while an app holds the SYSTEM_ALERT_WINDOW permission

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 포그라운드 서비스를 시작합니다. 서비스가 시작될 때 앱이 포그라운드에 있으므로 앱이 백그라운드로 전환된 후 6시간 동안 서비스가 계속 실행됩니다.
4. mediaProcessing 포그라운드 서비스를 사용하는 대신 WorkManager와 같은 대체 API를 사용하세요.

앱의 mediaProcessing 포그라운드 서비스가 지난 24시간 동안 6시간 동안 실행된 경우 사용자가 앱을 포그라운드로 가져와 (타이머 재설정) 않는 한 다른 mediaProcessing 포그라운드 서비스를 시작할 수 없습니다. 다른 mediaProcessing 포그라운드 서비스를 시작하려고 하면 시스템에서 '포그라운드 서비스 유형 mediaProcessing의 시간 제한이 이미 소진되었습니다'와 같은 오류 메시지와 함께 ForegroundServiceStartNotAllowedException을 발생시킵니다.

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:

• 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

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에서는 최신 OpenJDK LTS 출시의 기능과 일치하도록 Android의 핵심 라이브러리를 새로고침하는 작업을 계속하고 있습니다.

다음과 같은 변경사항은 Android 15 (API 수준 35)를 타겟팅하는 앱의 앱 호환성에 영향을 미칠 수 있습니다.

• 문자열 형식 지정 API 변경: 이제 다음 String.format() 및 Formatter.format() API를 사용할 때 인덱스, 플래그, 너비, 정밀도의 유효성 검사가 더 엄격해집니다.

  • String.format(String, Object[])
  • String.format(Locale, String, Object[])
  • Formatter.format(String, Object[])
  • Formatter.format(Locale, String, Object[])

  예를 들어 인수 색인 0이 사용되면 (형식 문자열의 %0) 다음 예외가 발생합니다.

  IllegalFormatArgumentIndexException: Illegal format argument index = 0
  

  이 경우 인덱스 1 (형식 문자열의 %1)을 사용하여 문제를 해결할 수 있습니다.

• Arrays.asList(...).toArray()의 구성요소 유형 변경: Arrays.asList(...).toArray()를 사용하면 결과 배열의 구성요소 유형이 기본 배열 요소의 유형이 아닌 Object가 됩니다. 따라서 다음 코드는 ClassCastException을 발생시킵니다.

  String[] elements = (String[]) Arrays.asList("one", "two").toArray();
  

  이 경우 결과 배열에서 String를 구성요소 유형으로 유지하려면 대신 Collection.toArray(Object[])를 사용하면 됩니다.

  String[] elements = Arrays.asList("two", "one").toArray(new String[0]);
  

• 언어 코드 처리 변경사항: Locale API를 사용할 때 히브리어, 이디시어, 인도네시아어의 언어 코드가 더 이상 더 이상 지원되지 않는 형식 (히브리어: iw, 이디시어: ji, 인도네시아어: in)으로 변환되지 않습니다. 이러한 언어 중 하나의 언어 코드를 지정할 때는 ISO 639-1의 코드 (히브리어: he, 이디시어: yi, 인도네시아어: id)를 대신 사용하세요.

• 무작위 int 시퀀스 변경: https://bugs.openjdk.org/browse/JDK-8301574에서 변경된 사항에 따라 이제 다음 Random.ints() 메서드는 Random.nextInt() 메서드와 다른 숫자 시퀀스를 반환합니다.

  • Random.ints(long)
  • Random.ints(long, int, int)
  • Random.ints(int, int)
  • Random.ints()

  일반적으로 이 변경사항으로 인해 앱이 중단되는 동작이 발생하지는 않지만 코드는 Random.ints() 메서드에서 생성된 시퀀스가 Random.nextInt()와 일치한다고 가정해서는 안 됩니다.

새 SequencedCollection API는 앱의 빌드 구성에서 compileSdk를 업데이트하여 Android 15 (API 수준 35)를 사용하면 앱의 호환성에 영향을 줄 수 있습니다.

• kotlin-stdlib의 MutableList.removeFirst() 및 MutableList.removeLast() 확장 함수와의 충돌

  Java의 List 유형은 Kotlin의 MutableList 유형에 매핑됩니다. List.removeFirst() 및 List.removeLast() API가 Android 15(API 수준 35)에서 도입되었으므로 Kotlin 컴파일러는 함수 호출(예: list.removeFirst())을 kotlin-stdlib의 확장 함수가 아닌 새 List API로 정적으로 확인합니다.

  앱이 compileSdk를 35로, minSdk를 34 이하로 설정하여 다시 컴파일된 후 Android 14 이하에서 실행되면 런타임 오류가 발생합니다.

  java.lang.NoSuchMethodError: No virtual method
  removeFirst()Ljava/lang/Object; in class Ljava/util/ArrayList;
  

  Android Gradle 플러그인의 기존 NewApi 린트 옵션은 이러한 새로운 API 사용을 포착할 수 있습니다.

  ./gradlew lint
  
  MainActivity.kt:41: Error: Call requires API level 35 (current min is 34): java.util.List#removeFirst [NewApi]
        list.removeFirst()
  

  런타임 예외 및 린트 오류를 수정하려면 Kotlin에서 removeFirst() 및 removeLast() 함수 호출을 각각 removeAt(0) 및 removeAt(list.lastIndex)로 대체할 수 있습니다. Android 스튜디오 Ladybug | 2024.1.3 이상을 사용하는 경우 이러한 오류에 대한 빠른 수정 옵션도 제공됩니다.

  린트 옵션이 사용 중지된 경우 @SuppressLint("NewApi") 및 lintOptions { disable 'NewApi' }를 삭제하는 것이 좋습니다.

• Java의 다른 메서드와 충돌

  기존 유형에 새 메서드(예: List 및 Deque)가 추가되었습니다. 이러한 새 메서드는 다른 인터페이스 및 클래스의 이름과 인수 유형이 동일한 메서드와 호환되지 않을 수 있습니다. 메서드 서명이 비호환성과 충돌하는 경우 javac 컴파일러는 빌드 시간 오류를 출력합니다. 예를 들면 다음과 같습니다.

  오류 예시 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
  

  오류 예시 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
  

  오류 예시 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
  

  이러한 빌드 오류를 수정하려면 이러한 인터페이스를 구현하는 클래스가 호환되는 반환 유형으로 메서드를 재정의해야 합니다. 예를 들면 다음과 같습니다.

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

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

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

사용자 환경 및 시스템 UI

Android 15에는 더 일관되고 직관적인 사용자 환경을 제공하기 위한 몇 가지 변경사항이 포함되어 있습니다.

창 인셋 변경사항

There are two changes related to window insets in Android 15: edge-to-edge is enforced by default, and there are also configuration changes, such as the default configuration of system bars.

Edge-to-edge enforcement

Apps are edge-to-edge by default on devices running Android 15 if the app is targeting Android 15 (API level 35).

This is a breaking change that might negatively impact your app's UI. The changes affect the following UI areas:

• Gesture handle navigation bar
  • Transparent by default.
  • Bottom offset is disabled so content draws behind the system navigation bar unless insets are applied.
  • setNavigationBarColor and R.attr#navigationBarColor are deprecated and don't affect gesture navigation.
  • setNavigationBarContrastEnforced and R.attr#navigationBarContrastEnforced continue to have no effect on gesture navigation.
• 3-button navigation
  • Opacity set to 80% by default, with color possibly matching the window background.
  • Bottom offset disabled so content draws behind the system navigation bar unless insets are applied.
  • setNavigationBarColor and R.attr#navigationBarColor are set to match the window background by default. The window background must be a color drawable for this default to apply. This API is deprecated but continues to affect 3-button navigation.
  • setNavigationBarContrastEnforced and R.attr#navigationBarContrastEnforced is true by default, which adds an 80% opaque background across 3-button navigation.
• Status bar
  • Transparent by default.
  • The top offset is disabled so content draws behind the status bar unless insets are applied.
  • setStatusBarColor and R.attr#statusBarColor are deprecated and have no effect on Android 15.
  • setStatusBarContrastEnforced and R.attr#statusBarContrastEnforced are deprecated but still have an effect on Android 15.
• Display cutout
  • layoutInDisplayCutoutMode of non-floating windows must be LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS. SHORT_EDGES, NEVER, and DEFAULT are interpreted as ALWAYS so that users don't see a black bar caused by the display cutout and appear edge-to-edge.

The following example shows an app before and after targeting Android 15 (API level 35), and before and after applying insets.

What to check if your app is already edge-to-edge

If your app is already edge-to-edge and applies insets, you are mostly unimpacted, except in the following scenarios. However, even if you think you aren't impacted, we recommend you test your app.

• You have a non-floating window, such as an Activity that uses SHORT_EDGES, NEVER or DEFAULT instead of LAYOUT_IN_DISPLAY_CUTOUT_MODE_ALWAYS. If your app crashes on launch, this might be due to your splashscreen. You can either upgrade the core splashscreen dependency to 1.2.0-alpha01 or later or set window.attributes.layoutInDisplayCutoutMode = WindowManager.LayoutInDisplayCutoutMode.always.
• There might be lower-traffic screens with occluded UI. Verify these less-visited screens don't have occluded UI. Lower-traffic screens include:
  • Onboarding or sign-in screens
  • Settings pages

What to check if your app is not already edge-to-edge

If your app is not already edge-to-edge, you are most likely impacted. In addition to the scenarios for apps that are already edge-to-edge, you should consider the following:

• If your app uses Material 3 Components ( androidx.compose.material3) in compose, such as TopAppBar, BottomAppBar, and NavigationBar, these components are likely not impacted because they automatically handle insets.
• If your app is using Material 2 Components ( androidx.compose.material) in Compose, these components don't automatically handle insets. However, you can get access to the insets and apply them manually. In androidx.compose.material 1.6.0 and later, use the windowInsets parameter to apply the insets manually for BottomAppBar, TopAppBar, BottomNavigation, and NavigationRail. Likewise, use the contentWindowInsets parameter for Scaffold.
• If your app uses views and Material Components (com.google.android.material), most views-based Material Components such as BottomNavigationView, BottomAppBar, NavigationRailView, or NavigationView, handle insets and require no additional work. However, you need to add android:fitsSystemWindows="true" if using AppBarLayout.
• For custom composables, apply the insets manually as padding. If your content is within a Scaffold, you can consume insets using the Scaffold padding values. Otherwise, apply padding using one of the WindowInsets.
• If your app is using views and BottomSheet, SideSheet or custom containers, apply padding using ViewCompat.setOnApplyWindowInsetsListener. For RecyclerView, apply padding using this listener and also add clipToPadding="false".

What to check if your app must offer custom background protection

If your app must offer custom background protection to 3-button navigation or the status bar, your app should place a composable or view behind the system bar using WindowInsets.Type#tappableElement() to get the 3-button navigation bar height or WindowInsets.Type#statusBars.

Additional edge-to-edge resources

See the Edge to Edge Views and Edge to Edge Compose guides for additional considerations on applying insets.

Deprecated APIs

The following APIs are deprecated but not disabled:

• R.attr#enforceStatusBarContrast
• R.attr#navigationBarColor (for 3 button navigation, with 80% alpha)
• Window#isStatusBarContrastEnforced
• Window#setNavigationBarColor (for 3 button navigation, with 80% alpha)
• Window#setStatusBarContrastEnforced

The following APIs are deprecated and disabled:

• R.attr#navigationBarColor (for gesture navigation)
• R.attr#navigationBarDividerColor
• R.attr#statusBarColor
• Window#setDecorFitsSystemWindows
• Window#getNavigationBarColor
• Window#getNavigationBarDividerColor
• Window#getStatusBarColor
• Window#setNavigationBarColor (for gesture navigation)
• Window#setNavigationBarDividerColor
• Window#setStatusBarColor

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:

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

우아한 텍스트 높이 속성의 기본값은 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.

복잡한 문자 도형의 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:

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:

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 15 includes updated lists of restricted non-SDK interfaces based on collaboration with Android developers and the latest internal testing. Whenever possible, we make sure that public alternatives are available before we restrict non-SDK interfaces.

If your app does not target Android 15, some of these changes might not immediately affect you. However, while it's possible for your app to access some non-SDK interfaces depending on your app's target API level, using any non-SDK method or field always carries a high risk of breaking your app.

If you are unsure if your app uses non-SDK interfaces, you can test your app to find out. If your app relies on non-SDK interfaces, you should begin planning a migration to SDK alternatives. Nevertheless, we understand that some apps have valid use cases for using non-SDK interfaces. If you can't find an alternative to using a non-SDK interface for a feature in your app, you should request a new public 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.