Like earlier releases, Android 13 includes behavior changes that may affect your app. The following behavior changes apply exclusively to apps that are targeting Android 13 or higher. If your app is targeting Android 13 or higher, you should modify your app to support these behaviors properly, where applicable.
Be sure to also review the list of behavior changes that affect all apps running on Android 13.
Notification permission affects foreground service appearance
If the user denies the notification permission, they still see notices related to these foreground services in the Foreground Services (FGS) Task Manager but don't see them in the notification drawer.
New runtime permission for nearby Wi-Fi devices
On previous versions of Android, the user needs to grant your app the
permission in order to complete several common Wi-Fi use cases related to
hotspots, Wi-Fi Direct connections, Wi-Fi RTT, and more.
Because it's difficult for users to associate location permissions with Wi-Fi
functionality, Android 13 (API level 33) introduces a new runtime permission in
permission group for apps that manage a device's connections to nearby access
points over Wi-Fi. This permission,
fulfills these Wi-Fi use cases.
As long as your app doesn't derive physical location information from the Wi-Fi
NEARBY_WIFI_DEVICES instead of
ACCESS_FINE_LOCATION when you
target Android 13 or higher and use Wi-Fi APIs. This process is
similar to the one you do in Android 12 (API level 31) and higher when you
assert that Bluetooth device information is never used for
Learn more about the nearby Wi-Fi devices permission.
Granular media permissions
The set of permissions that you request depends on the type(s) of media that your app needs to access:
|Type of media||Permission to request|
|Images and photos||
If the user previously granted your app the
the system automatically grants each of the new permissions to your app.
Otherwise, the system shows a user-facing dialog when your app
requests any of the permissions shown in the preceding table. In figure 1, the
app requests the
READ_MEDIA_AUDIO permission. If you request both the
READ_MEDIA_IMAGES permission and the
READ_MEDIA_VIDEO permission at the same
time, only one system permission dialog appears.
Migration steps when you target Android 13
After you target Android 13, declare the media permissions that
your app needs. To maintain compatibility with older versions of Android,
READ_EXTERNAL_STORAGE permission while setting
32, as shown in the following code snippet:
<manifest ...> <!-- Required only if your app targets Android 13. --> <!-- Declare one or more the following permissions only if your app needs to access data that's protected by them. --> <uses-permission android:name="android.permission.READ_MEDIA_IMAGES" /> <uses-permission android:name="android.permission.READ_MEDIA_AUDIO" /> <uses-permission android:name="android.permission.READ_MEDIA_VIDEO" /> <!-- Required to maintain app compatibility. --> <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" android:maxSdkVersion="32" /> <application ...> ... </application> </manifest>
Use of body sensors in the background requires new permission
Android 13 introduces the concept of "while in use" access for body sensors, such as heart rate, temperature, and blood oxygen percentage. This access model is very similar to the one that the system introduced for location in Android 10 (API level 29).
If your app targets Android 13 and requires access to body sensor
information while running in the background, you must declare the new
permission in addition to the existing
Intent filters block non-matching intents
When your app sends an intent to an exported component of another app that
targets Android 13 or higher, that intent is delivered if and
only if it matches an
<intent-filter> element in the receiving app.
Non-matching intents are blocked.
Exceptions where intent matching isn't enforced:
- Intents delivered to components that don't declare any intent filters.
- Intents originating from within the same app.
- Intents originating from the system; that is, intents being sent from the
"system UID" (uid=1000). System apps include
system_serverand apps that set
- Intents originating from root.
If a receiving app upgrades to Android 13 or higher, all intents
originating from external apps are delivered to an exported component if and only
if it matches its declared
<intent-filter> elements, regardless of the sending
app's target SDK version.
Performance and battery
Battery Resource Utilization
If the user places your app in the "restricted" state for background battery usage while your app targets Android 13, the system applies several limitations related to broadcasts.
Learn more about the new limitations for restricted background battery usage on the page that describes the Battery Resource Utilization features being introduced in Android 13.
Media controls derived from
For apps targeting Android 13 (API level 33) and higher, the system derives
media controls from
PlaybackState actions. This
allows the system to show a richer set of controls that are technically
consistent between phones and tablet devices, and also align with how media
controls are rendered on other Android platforms such as Android Auto and
Figure 2 shows an example of how this looks on a phone and tablet device, respectively.
Prior to Android 13, the system displayed up to five actions from the
notification in the order in which they were added.
In compact mode—for example, in the collapsed quick settings—up to
three actions specified with
Starting with Android 13, the system displays up to five action buttons based
PlaybackState as described in the following table. In compact mode, only the first three
action slots will be displayed. For apps that don't target Android 13 or those
that don't include a
PlaybackState, the system will display controls based on
Action list added to the
MediaStyle notification as described in the
Current state of the
Current state of the
|Pause||Current state of the
Custom actions are placed in the order in which they were added to the
App color theme applied automatically to WebView content
For apps targeting Android 13 (API level 33) or higher, the
method is deprecated, resulting in a no-op if the method is called.
Instead, WebView now always sets
the media query
prefers-color-scheme according to the app's theme attribute,
isLightTheme. In other
true or not specified,
light; otherwise, it is
dark. This behavior means that the web content's
light or dark style is applied automatically to match the app's theme if the
content supports it.
For most apps, the new behavior should apply the appropriate app styles automatically, however you should test your app to check for any cases where you might've been manually controlling dark mode settings.
If you still need to customize your app's color theme behavior, use the
method instead. For backward compatibility with previous Android versions, we
recommend using the equivalent
method in AndroidX.
See the documentation for that method to learn more about what behavior you can
expect in your app depending on your app's
targetSdkVersion and theme
Google Play services
Permission required for advertising ID
<manifest ...> <!-- Required only if your app targets Android 13 or higher. --> <uses-permission android:name="com.google.android.gms.permission.AD_ID"/> <application ...> ... </application> </manifest>
If your app does not declare this permission when targeting Android 13 or higher, the advertising ID is automatically removed and replaced with a string of zeroes.
If your app uses SDKs that declare the
AD_ID permission in the library's
manifest, then the permission is merged with your app's manifest file by
default. In this case, you don't need to declare the permission in your app's
To learn more, see Advertising ID in the Play Console Help.
Updated non-SDK restrictions
Android 13 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 13, some of these changes might not immediately affect you. However, while you can currently use 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 cannot 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 13. To learn more about non-SDK interfaces generally, see Restrictions on non-SDK interfaces.