Compatibility framework changes (Android 13)

ACCOUNT_ACCESS_CHECK_CHANGE_ID

For apps targeting Android 13 (API level 33) and higher, enables checking for account access for the calling UID on all sync-related APIs.

ALLOW_COPY_SOLID_COLOR_VIEW

For apps targeting Android 13 (API level 33) and higher, allows an app to receive the SplashScreen.OnExitAnimationListener.onSplashScreenExit(SplashScreenView) callback, even when the splash screen only shows a solid color.

ALLOW_SECURE_ACTIVITY_DISPLAY_ON_REMOTE_DEVICE

For apps targeting Android 13 (API level 33) and higher, allows a secure activity to display on remote devices if required.

ALWAYS_SANDBOX_DISPLAY_APIS

Forces the packages it is applied to always have Display API sandboxing applied, regardless of windowing mode. The Display APIs will always provide the app bounds.

To learn more about this change, see Display#getRealSize and getRealMetrics: deprecation and sandboxing.

BORINGLAYOUT_FALLBACK_LINESPACING

For apps targeting Android 13 (API level 33) and higher, enables the fallback text line spacing (line height) for BoringLayout.

CALL_REDIRECTION_AUDIO_MODES

For apps targeting Android 13 (API level 33) and higher, allows use of audio modes for call audio redirection.

CAMERA_MIC_INDICATORS_NOT_PRESENT

Indicates that this device supports camera and microphone indicators. Will be false if present, because the CompatChanges#isChangeEnabled method returns true if the Change ID is not present.

CLEAR_SHOW_FORCED_FLAG_WHEN_LEAVING

For apps targeting Android 13 (API level 33) and higher, prevents the SHOW_FORCED flag from having any effect unless the caller is currently focused.

DEFER_BOOT_COMPLETED_BROADCAST_CHANGE_ID

For apps targeting Android 13 (API level 33) and higher, defer LOCKED_BOOT_COMPLETED and BOOT_COMPLETED broadcasts until the first time any process in the UID is started.

DISALLOW_DEADLINES_FOR_PREFETCH_JOBS

For apps targeting Android 13 (API level 33) and higher, disallows setting a deadline (using JobInfo.Builder.setOverrideDeadline(long)) for prefetch jobs ( JobInfo.Builder.setPrefetch(boolean). Prefetch jobs are meant to run close to the next app launch, so they are not allowed to have deadlines. However, the system doesn't drop or cancel any previously scheduled prefetch jobs with a deadline.

There's no way for an app to keep a perpetually-scheduled prefetch job with a deadline. Prefetch jobs with a deadline will run and apps under this restriction won't be able to schedule new prefetch jobs with a deadline. If a job is rescheduled (by providing true using JobService.jobFinished(JobParameters, boolean) or JobService.onStopJob(JobParameters)'s return value), the deadline is dropped. Periodic jobs require all constraints to be met, so these restrictions do not apply to their deadlines.

DOWNSCALED

This change is the gatekeeper of all per-app buffer downscaling changes. Disabling this change prevents the following scaling factors from working:

• DOWNSCALE_30
• DOWNSCALE_35
• DOWNSCALE_40
• DOWNSCALE_45
• DOWNSCALE_50
• DOWNSCALE_55
• DOWNSCALE_60
• DOWNSCALE_65
• DOWNSCALE_70
• DOWNSCALE_75
• DOWNSCALE_80
• DOWNSCALE_85
• DOWNSCALE_90

When this change is enabled for an app package, the app is forcibly resized to the highest enabled scaling factor. For example, 80% is used if both 80% and 70% are enabled.

DOWNSCALE_30

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 30% vertical and horizontal resolution of the real display.

DOWNSCALE_35

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 35% vertical and horizontal resolution of the real display.

DOWNSCALE_40

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 40% vertical and horizontal resolution of the real display.

DOWNSCALE_45

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 45% vertical and horizontal resolution of the real display.

DOWNSCALE_50

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 50% vertical and horizontal resolution of the real display.

DOWNSCALE_55

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 55% vertical and horizontal resolution of the real display.

DOWNSCALE_60

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 60% vertical and horizontal resolution of the real display.

DOWNSCALE_65

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 65% vertical and horizontal resolution of the real display.

DOWNSCALE_70

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 70% vertical and horizontal resolution of the real display.

DOWNSCALE_75

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 75% vertical and horizontal resolution of the real display.

DOWNSCALE_80

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 80% vertical and horizontal resolution of the real display.

DOWNSCALE_85

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 85% vertical and horizontal resolution of the real display.

DOWNSCALE_90

When DOWNSCALED is also enabled, enabling this change for a package forces the app to assume it's running on a display with 90% vertical and horizontal resolution of the real display.

DUMP_IGNORES_SPECIAL_ARGS

For apps targeting Android 13 (API level 33) and higher, dump(String, FileDescriptor, PrintWriter, String[]) is not called if dumpsys activity is called with some special arguments.

DYNAMIC_RECEIVER_EXPLICIT_EXPORT_REQUIRED

When enabled, requires an app to explicitly set either Context.RECEIVER_EXPORTED or Context.RECEIVER_NOT_EXPORTED when registering a receiver for an unprotected broadcast in code.

To learn more, see the section on Safer exporting of context-registered receivers.

ENABLE_PENDING_INTENT_BAL_OPTION

For apps targeting Android 13 (API level 33) and higher, protects PendingIntent from being abused to start background activity.

ENABLE_SIMPLIFIED_DARK_MODE

For apps targeting Android 13 (API level 33) and higher, allows web content to apply light or dark style according to the app's theme and WebView to attempt to darken web content by algorithmic darkening when appropriate. Refer to setAlgorithmicDarkeningAllowed(boolean) for details.

ENABLE_TOUCH_OPAQUE_ACTIVITIES

For apps running on Android 13 (API level 33) or higher, makes activities consume all touches within their task bounds.

ENABLE_USE_EXACT_ALARM

For apps targeting Android 13 (API level 33) and higher, allows certain kinds of apps to use Manifest.permission.USE_EXACT_ALARM to schedule exact alarms.

ENFORCE_INTENTS_TO_MATCH_INTENT_FILTERS

For apps targeting Android 13 (API level 33) and higher, components will stop receiving intents from external callers that do not match its declared intent filters. When an app registers an exported component in its manifest and adds an intent filter, the component can be started by any intent, even those that do not match the intent filter. This has proven to be something that many developers find counterintuitive. Without checking the intent when the component is started, in some circumstances this can allow third- party apps to trigger internal-only functionality.

ENFORCE_STRICT_QUERY_BUILDER

When enabled, the SQLiteQueryBuilder verifies all CalendarProvider2 query selections against malicious arguments.

FORCE_DISABLE_HEVC_SUPPORT

Force disable an app from supporting the HEVC media capability. Apps should declare their supported media capabilities in their manifest but this flag can be used to force an app into not supporting HEVC, hence forcing transcoding while accessing media encoded in HEVC. Setting this flag will override any OS level defaults for apps. It is disabled by default, meaning that the OS defaults take precedence. Setting this flag and FORCE_ENABLE_HEVC_SUPPORT is an undefined state and will result in the OS ignoring both flags.

FORCE_ENABLE_HEVC_SUPPORT

Force enable an app to support the HEVC media capability Apps should declare their supported media capabilities in their manifest but this flag can be used to force an app into supporting HEVC, hence avoiding transcoding while accessing media encoded in HEVC. Setting this flag will override any OS level defaults for apps. It is disabled by default, meaning that the OS defaults would take precedence. Setting this flag and FORCE_DISABLE_HEVC_SUPPORT is an undefined state and will result in the OS ignoring both flags.

FORCE_NON_RESIZE_APP

Forces the packages it is applied to to be non-resizable.

FORCE_RESIZE_APP

Forces the packages it is applied to to be resizeable. We only allow resizing in fullscreen windowing mode, but not forcing the app into resizeable multi-windowing mode.

GET_API_SIGNATURES_FROM_UICC_PORT_INFO

For apps targeting Android 13 (API level 33) and higher, allows a SIM card can have more than one ICCID active at the same time. Support for this is provided by Multiple Enabled Profiles (MEP).

GWP_ASAN

Enables sampled native memory bug detection in apps.

To learn more about using GWP-ASan, see the GWP-ASan guide.

ICC_CLOSE_CHANNEL_EXCEPTION_ON_FAILURE

For apps targeting Android 13 (API level 33) and higher, an exception is now thrown whenever an ICC close channel operation fails.

KEYSTORE_OPERATION_CREATION_MAY_FAIL

When enabled, keystore operation creation might fail according to the new pruning strategy. Keystore used to work under the assumption that the creation of cryptographic operations always succeeds. However, the KeyMint backend has only a limited number of operation slots.

In order to keep up the appearance of "infinite" operation slots, the Keystore daemon would prune least recently used operations if there was no available operation slot. As a result, good operations could be terminated prematurely. This opened up AndroidKeystore up to denial-of-service (DoS) and unintended livelock. For example, if multiple apps woke up at the same time due to power management optimizations and attempted to perform crypto operations, they start terminating each others operations without making any progress.

To break out of livelocks and to discourage DoS attempts, we have changed the pruning strategy for such that it prefers clients that use few operation slots briefly. As a result, single operations that don't linger inactive for more than 5 seconds will almost always conclude unhampered by the pruning strategy. There are still some operations related to file system encryption that can prune even these operations, but those cases are extremely rare. As a side effect of this new pruning strategy operation, creation can now fail if the client has a lower pruning power than all of the existing operations.

Pruning strategy: To find a suitable candidate, we compute the malus for the caller and each existing operation. The malus is the inverse of the pruning power (caller) or pruning resistance (existing operation). For the caller to be able to prune an operation, it must find an operation with a malus higher than its own. For more details on the pruning strategy, see the implementation of operation.rs. On Android 11 (API level 30) and lower, KeyStore2 will poll the Keystore daemon for a free operation slot. For apps targeting Android 11 (API level 30) and lower, it will still look like cipher and signature object initialization always succeeds—however, it may take longer to get an operation. All Android versions benefit from fairer operation slot scheduling and a better chance to successfully conclude an operation.

MEDIA_CONTROL_SESSION_ACTIONS

For apps targeting Android 13 (API level 33) and higher, media controls based on Notification.MediaStyle notifications now have actions based on the media session's PlaybackState, rather than the notification's actions.

To learn more about this change, see the section in the Android 13 behavior changes page about the changes to media controls.

NATIVE_HEAP_ZERO_INIT

Enable automatic zero-initialization of native heap memory allocations.

NATIVE_MEMTAG_ASYNC

Enable asynchronous (ASYNC) memory tag checking in this process. This flag only affects hardware supporting the ARM Memory Tagging Extension (MTE).

NATIVE_MEMTAG_SYNC

Enables synchronous (SYNC) memory tag checking in this process. This flag only affects hardware supporting the ARM Memory Tagging Extension (MTE). If both NATIVE_MEMTAG_ASYNC and this option are enabled, this option takes precedence and MTE is enabled in SYNC mode.

NEVER_SANDBOX_DISPLAY_APIS

Forces the packages it is applied to never have Display API sandboxing applied for a letterbox or SCM activity. The Display APIs will continue to provide DisplayArea bounds.

To learn more about this change, see Display#getRealSize and getRealMetrics: deprecation and sandboxing.

NOTIFICATION_LOG_ASSISTANT_CANCEL

For apps targeting Android 13 (API level 33) and higher, enables listeners to understand the more specific reason provided for notification cancellations from an assistant, rather than using the more general REASON_LISTENER_CANCEL.

NOTIFICATION_PERM_CHANGE_ID

For apps targeting Android 13 (API level 33) and higher, enables behavior changes related to the runtime permission for notifications.

To learn more about this change, see the page about the new notification runtime permission.

NOTIFICATION_TRAMPOLINE_BLOCK_FOR_EXEMPT_ROLES

For apps targeting Android 13 (API level 33) and higher, Activity starts coming from broadcast receivers or services in response to notification and notification action clicks are be blocked for UX and performance reasons for previously-exempt role holders (browsers).

OVERRIDABLE_COMPONENT_CALLBACKS

For apps targeting Android 13 (API level 33) and higher, registerComponentCallbacks(ComponentCallbacks) adds a ComponentCallbacks to Activity or ContextWrapper.getBaseContext() instead of always adding to getApplicationContext().

OVERRIDE_CAMERA_RESIZABLE_AND_SDK_CHECK

When enabled this change id forces the packages it is applied to ignore the current value of android:resizeableActivity as well as target SDK equal to or below M and consider the activity as non-resizeable. In this case, the value of camera rotate and crop will only depend on the needed compensation considering the current display rotation.

OVERRIDE_CAMERA_ROTATE_AND_CROP_DEFAULTS

When enabled this change id forces the packages it is applied to override the default camera rotate and crop behavior and always return CaptureRequest.SCALER_ROTATE_AND_CROP_NONE. The default behavior along with all possible override combinations is discussed in the table below.

OVERRIDE_MIN_ASPECT_RATIO

This change is the gatekeeper of all changes that force a given minimum aspect ratio. Enabling this change allows the following minimum aspect ratios to be applied:

• OVERRIDE_MIN_ASPECT_RATIO_LARGE
• OVERRIDE_MIN_ASPECT_RATIO_MEDIUM
• OVERRIDE_MIN_ASPECT_RATIO_PORTRAIT_ONLY

When this change is enabled for an app package, the minimum aspect ratio given in the app's manifest is overridden to the largest enabled aspect ratio unless the app's manifest value is higher.

OVERRIDE_MIN_ASPECT_RATIO_LARGE

When OVERRIDE_MIN_ASPECT_RATIO is also enabled, enabling this change for a package sets the activity's minimum aspect ratio to a large value as defined by OVERRIDE_MIN_ASPECT_RATIO_LARGE_VALUE.

OVERRIDE_MIN_ASPECT_RATIO_MEDIUM

When OVERRIDE_MIN_ASPECT_RATIO is also enabled, enabling this change for a package sets the activity's minimum aspect ratio to a medium value as defined by OVERRIDE_MIN_ASPECT_RATIO_MEDIUM_VALUE.

OVERRIDE_MIN_ASPECT_RATIO_PORTRAIT_ONLY

When OVERRIDE_MIN_ASPECT_RATIO is also enabled, enabling this change for a package limits any other changes that force an activity's minimum aspect ratio to a certain value—such as OVERRIDE_MIN_ASPECT_RATIO_LARGE and OVERRIDE_MIN_ASPECT_RATIO_MEDIUM—to activities that also have a portrait orientation.

RATE_LIMIT_TOASTS

Enables rate limiting on the number of Toast.show() calls to prevent overburdening the user with too many toasts in a limited time. Any attempt to show more toasts than allowed in a certain time frame will result in the toast being discarded.

REQUEST_LISTENING_MUST_MATCH_PACKAGE

For apps targeting Android 13 (API level 33) and higher, calling TileService.requestListeningState(Context, ComponentName) checks that the calling package (UID) and the package of the target ComponentName match. The system also checks that the context used can take actions on behalf of the current user.

RETURN_ADVANCED_VIDEO_PROFILES

For apps targeting Android 13 (API level 33) and higher, controls the kind of video profiles returned by getAll(String, int).

SHOULD_RESOLVE_PORT_INDEX_FOR_APPS

For apps targeting Android 13 (API level 33) and higher, allows SIM cards to enable Multiple Enabled Profiles (MEP) on different ports. To preserve backward compatibility for carrier apps, when an app that targets API level 32 or lower calls the switchToSubscription or download APIs without specifying the port index, the system retains the existing behaviour by always using port index 0 even if the device itself has MEP eUICC enabled.

SWITCH_WITHOUT_PORT_INDEX_EXCEPTION_ON_DISABLE

For apps targeting Android 13 (API level 33) and higher, the system throws an exception whenever switchToSubscription() is called without portIndex to disable a subscription.

THROW_ON_INVALID_PRIORITY_VALUE

For apps targeting Android 13 (API level 33) and higher, the system throws an exception when an app provides an invalid priority value using JobInfo.Builder.setPriority(int). Legacy apps may be incorrectly using the API, so the call silently fails if they continue using the API.

USE_EXPERIMENTAL_COMPONENT_ALIAS

When enabled, the system allows the "android" package to use component aliases.