동작 변경사항: 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.

• New media processing foreground service type
• Restrictions on BOOT_COMPLETED broadcast receivers launching foreground services

New media processing foreground service type

Android 15 introduces a new foreground service type, mediaProcessing. This service type is appropriate for operations like transcoding media files. For example, a media app might download an audio file and need to convert it to a different format before playing it. You can use a mediaProcessing foreground service to make sure the conversion continues even while the app is in the background.

For more information about the mediaProcessing service type, see Changes to foreground service types for Android 15.

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.

사용자 환경

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

창 인셋 변경사항

Android 15에서는 창 인셋과 관련된 두 가지 변경사항이 있습니다. 베타 1에서는 더 넓은 화면 범위가 적용됩니다. 시스템 표시줄의 기본 구성을 비롯한 향후 구성 변경사항도 있습니다.

Edge-to-edge enforcement

Apps will be edge-to-edge by default on devices running Android 15 if the app is targeting Android 15.

This is a breaking change that might negatively impact your app's UI. The changes are as follows:

• 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 is deprecated and does not affect gesture navigation.
  • setNavigationBarContrastEnforced and R.attr#navigationBarContrastEnforced continues 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 is 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 three button navigation.
  • setNavigationBarContrastEnforced and R.attr#navigationBarContrastEnforced is true by default, which adds an 80% opaque background across three button navigation.
• Status bar
  • Transparent by default.
  • The top offset is disabled so content will draw 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. Otherwise apps will crash with an IllegalArgumentException. ALWAYS is the only allowed option so that users don't see a Black bar caused by the display cutout in landscape mode and therefore appear edge-to-edge.

The following example shows an app before and after targeting Android 15, and before and after applying insets.

If your app:

• is already edge-to-edge and applies insets, you are mostly unimpacted, except in the following scenarios. However, even if you feel you aren't impacted, we recommend you test your app.
  • Your app crashes because 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 may be due to your splashscreen. Until a fix is available, set window.attributes.layoutInDisplayCutoutMode = WindowManager.LayoutInDisplayCutoutMode.always.
  • There may 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
• is not edge-to-edge, you are most likely impacted. In addition to the scenarios for apps that are already edge-to-edge, you will need to 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 will 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 may consume insets using Scaffold's 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".
• must offer custom background protection to three button navigation or the status bar, you app should place a composable or view behind the system bar using WindowInsets.Type#tappableElement() to get the three button navigation bar height or WindowInsets.Type#statusBars.

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

The list of deprecated and disabled APIs are:

• R.attr#statusBarColor
• R.attr#navigationBarColor
• R.attr#navigationBarDividerColor
• Window#setDecorFitsSystemWindows
• Window#setStatusBarColor
• Window#setStatusBarContrastEnforced
• Window#setNavigationBarColor
• Window#setNavigationBarDividerColor
• Window#getStatusBarColor
• Window#getStatusBarContrastEnforced
• Window#getNavigationBarColor
• Window#getNavigationBarDividerColor

Stable configuration

이 변경사항은 베타 1에서 테스트할 수 없지만 곧 제공될 예정입니다.

앱이 Android 15 이상을 타겟팅하면 Configuration에서 더 이상 시스템 표시줄을 제외하지 않습니다. 레이아웃 계산을 위해 Configuration 클래스에서 화면 크기를 사용하는 경우 필요에 따라 적절한 ViewGroup, WindowInsets 또는 WindowMetricsCalculator와 같은 더 나은 대안으로 대체해야 합니다.

Configuration는 API 1부터 사용할 수 있었습니다. 일반적으로 Activity.onConfigurationChanged에서 가져옵니다. 창 밀도, 방향, 크기와 같은 정보를 제공합니다. Configuration에서 반환되는 창 크기에 관한 한 가지 중요한 특징은 이전에 시스템 표시줄을 제외했다는 것입니다.

구성 크기는 일반적으로 리소스 선택(예: /res/layout-h500dp)에 사용되며 여전히 유효한 사용 사례입니다. 그러나 레이아웃 계산에 사용하는 것은 항상 권장되지 않습니다. 그렇게 한다면 이제 그만두어야 합니다. Configuration 사용을 사용 사례에 따라 더 적합한 값으로 바꿔야 합니다.

이 메서드를 사용하여 레이아웃을 계산하는 경우 CoordinatorLayout 또는 ConstraintLayout와 같은 적절한 ViewGroup를 사용하세요. 이 메서드를 사용하여 시스템 탐색 메뉴의 높이를 결정한다면 WindowInsets를 사용하세요. 앱 창의 현재 크기를 알아보려면 computeCurrentWindowMetrics를 사용하세요.

다음 목록에서는 이 변경사항의 영향을 받는 필드를 설명합니다.

• Configuration.screenWidthDp 및 screenHeightDp 크기에서 더 이상 시스템 표시줄을 제외하지 않습니다.
• Configuration.smallestScreenWidthDp는 screenWidthDp 및 screenHeightDp의 변경사항의 간접적인 영향을 받습니다.
• Configuration.orientation는 정사각형에 가까운 기기에서 screenWidthDp 및 screenHeightDp의 변경사항으로 간접적인 영향을 받습니다.
• Display.getSize(Point)는 구성 변경사항의 간접적인 영향을 받습니다. 이 기능은 API 수준 30부터 지원 중단되었습니다.
• Display.getMetrics()는 API 수준 33부터 이미 이와 같이 작동했습니다.

UltraTextHeight 속성의 기본값이 true로 설정됩니다.

For apps targeting Android 15, 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.

카메라 및 미디어

Android 15에서는 Android 15 이상을 타겟팅하는 앱의 카메라 및 미디어 동작을 다음과 같이 변경합니다.

오디오 포커스 요청 제한사항

Apps that target Android 15 must be the top app or running an audio-related 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.

A foreground service is considered audio-related if its type is mediaPlayback, camera, microphone, or phoneCall.

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.

<

이 Android 버전의 변경사항을 자세히 알아보려면 Android 15의 비 SDK 인터페이스 제한사항 업데이트를 참고하세요. 비 SDK 인터페이스에 관한 일반적인 내용을 자세히 알아보려면 비 SDK 인터페이스 제한사항을 참고하세요.