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

The system permits an app's mediaProcessing 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(). 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 mediaProcessing did not stop within its timeout: [component name]"

To avoid having the exception, you can do one 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 mediaProcessing 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 mediaProcessing 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 mediaProcessing foreground service, use an alternative API, like WorkManager.

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

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

Testing

To test your app's behavior, you can enable media processing 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 media_processing_fgs_timeout_duration duration-in-milliseconds

Restrictions on BOOT_COMPLETED broadcast receivers launching foreground services

출시되는 broadcast receiver BOOT_COMPLETED개에 새로운 제한사항이 있습니다. 포그라운드 서비스가 될 수 있습니다 BOOT_COMPLETED 수신기는 다음 유형의 포그라운드 서비스를 실행할 수 없습니다.

• dataSync
• camera
• mediaPlayback
• phoneCall
• mediaProjection
• microphone (이 제한은 이후 microphone부터 적용되었음 Android 14)

BOOT_COMPLETED 수신기가 이러한 유형의 포그라운드를 실행하려고 하는 경우 시스템에서 ForegroundServiceStartNotAllowedException을 발생시킵니다.

테스트

앱의 동작을 테스트하기 위해 앱이 Android 15를 타겟팅하지 않음 (앱이 Android 15 기기). 다음 adb 명령어를 실행합니다.

adb shell am compat enable FGS_BOOT_COMPLETED_RESTRICTIONS your-package-name

기기를 다시 시작하지 않고 BOOT_COMPLETED 브로드캐스트를 전송하려면 다음 안내를 따르세요. 다음 adb 명령어를 실행합니다.

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:

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

  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:

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

  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 restricts the usage of TLS versions 1.0 and 1.1. These versions had previously been deprecated in Android, but are now disallowed for apps targeting 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에서는 인텐트 보안이 두 가지 주요 사항이 개선되었습니다.

• 타겟 인텐트 필터와 일치: 특정 구성요소를 타겟팅하는 인텐트는 대상의 인텐트 필터 사양과 정확하게 일치하는지 확인합니다 다른 앱의 활동을 실행하기 위해 인텐트를 전송하는 경우 타겟 인텐트 구성요소는 수신 활동의 선언된 인텐트 필터와 일치해야 합니다.
• 인텐트에는 작업이 있어야 합니다. 작업이 없는 인텐트는 더 이상 인텐트 필터와 일치하지 않습니다. 이것은 활동이나 활동을 시작하는 데 사용된 인텐트가 서비스에 명확하게 정의된 작업이 있어야 합니다.

앱이 이러한 변경사항에 어떻게 반응하는지 확인하려면 다음을 사용하세요. 앱의 StrictMode 자세한 내용은 Intent 사용 위반에 관한 로그를 확인하려면 다음 메서드를 추가합니다.

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

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

사용자 환경 및 시스템 UI

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

창 인셋 변경

Android 15에는 창 인셋과 관련된 두 가지 변경사항이 있습니다. 가장자리에서 가장자리까지가 기본적으로 적용되며 시스템 표시줄의 기본 구성과 같은 구성 변경사항도 있습니다.

더 넓은 화면 적용

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. This example is not comprehensive, this might appear differently on Android Auto.

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

안정적인 구성

앱이 Android 15 (API 수준 35) 이상을 타겟팅하는 경우 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)은 Configuration의 변경사항에 간접적으로 영향을 받습니다. API 수준 30부터 지원 중단되었습니다.
• Display.getMetrics()는 API 수준 33부터 이미 이렇게 작동했습니다.

elegantTextHeight 속성이 기본적으로 true로 설정됨

Android 15 (API 수준 35)를 타겟팅하는 앱의 경우 elegantTextHeight TextView 속성이 기본적으로 true이 되므로 기본적으로 사용되는 소형 글꼴이 세로 측정값이 큰 스크립트로 대체되어 가독성이 훨씬 높아집니다. 좁은 글꼴은 레이아웃이 중단되는 것을 방지하기 위해 도입되었습니다. Android 13 (API 수준 33)은 텍스트 레이아웃이 fallbackLineSpacing 속성을 활용하여 세로 높이를 늘릴 수 있도록 허용하여 이러한 중단을 대부분 방지합니다.

Android 15에서는 소형 글꼴이 여전히 시스템에 남아 있으므로 앱에서 elegantTextHeight를 false로 설정하여 이전과 동일한 동작을 얻을 수 있지만 향후 출시에서는 지원되지 않을 가능성이 큽니다. 따라서 앱이 아랍어, 라오어, 미얀마어, 타밀어, 구자라트어, 칸나다어, 말라얄람어, 오디어, 텔루구어 또는 태국어 스크립트를 지원하는 경우 elegantTextHeight를 true로 설정하여 앱을 테스트합니다.

복잡한 글자 모양의 TextView 너비 변경

이전 버전의 Android에서는 복잡한 도형을 사용하는 일부 필기체 글꼴이나 언어에서 이전 또는 다음 문자의 영역에 문자를 그릴 수 있습니다. 이러한 문자가 시작 또는 끝 위치에서 잘리는 경우도 있었습니다. Android 15부터 TextView는 이러한 문자를 위한 공간을 그리기에 충분한 너비를 할당하고 앱이 왼쪽에 추가 패딩을 요청하여 클리핑을 방지할 수 있도록 합니다.

이 변경사항은 TextView가 너비를 결정하는 방식에 영향을 미치므로 앱이 Android 15 (API 수준 35) 이상을 타겟팅하는 경우 TextView는 기본적으로 더 많은 너비를 할당합니다. 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의 언어 인식 기본 행 높이

이전 버전의 Android에서는 텍스트 레이아웃이 현재 언어와 일치하는 글꼴의 행 간격을 충족하도록 텍스트 높이를 늘렸습니다. 예를 들어 콘텐츠가 일본어인 경우 일본어 글꼴의 줄 높이가 라틴어 글꼴의 줄 높이보다 약간 더 커서 텍스트의 높이가 약간 더 커졌습니다. 그러나 이러한 줄 높이의 차이에도 불구하고 다음 이미지와 같이 사용되는 언어와 관계없이 EditText 요소의 크기는 균일하게 조정되었습니다.

Android 15(API 수준 35)를 타겟팅하는 앱의 경우 이제 EditText가 지정된 언어의 참조 글꼴과 일치하도록 최소 줄 높이가 예약됩니다(다음 이미지 참고).

필요한 경우 앱은 useLocalePreferredLineHeightForMinimum 속성을 false로 지정하여 이전 동작을 복원할 수 있으며 Kotlin 및 Java에서 setMinimumFontMetrics API를 사용하여 맞춤 최소 카테고리 측정항목을 설정할 수 있습니다.

카메라 및 미디어

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

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

Android 15 (API 수준 35)를 타겟팅하는 앱은 오디오 포커스를 요청하려면 최상위 앱이거나 포그라운드 서비스를 실행 중인 앱이어야 합니다. 앱이 이러한 요구사항 중 하나를 충족하지 못할 때 포커스를 요청하려고 하면 호출이 AUDIOFOCUS_REQUEST_FAILED를 반환합니다.

오디오 포커스 관리에서 오디오 포커스에 대해 자세히 알아보세요.

업데이트된 비 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 인터페이스 제한사항을 참고하세요.