Support and Release Notes

Two primary support channels are available to you when developing and testing with the Android Q Beta.

Please file bugs at https://developer.android.com/preview/bug for device-specific, system, and Google App bugs. Please search for existing bugs that match your issue before filing your own. You can indicate that you're also encountering an issue by clicking the star button.
For issues in other apps, please contact the developer directly.

To discuss issues or ideas with other developers working with the Android Q Beta, join the android_beta community on Reddit.

Android Q Beta 3

Date: May 2019
Build: QPP3.190404.015
Emulator support: x86 (32/64-bit)
Security patch level: May 2019
Google Play services: 16.7.90
API diff:

API 28 → Beta3

Beta 2 → Beta3

About Android Q Beta 3

The Android Q Beta 3 update includes several new features and APIs as well the latest optimizations and bug fixes for developers and early adopters. It’s suitable for development, testing, and general use. Please note that Android Q Beta 3 is still in active development, so the Android system and apps may not work as expected.

As with previous versions, Android Q includes behavior changes to help improve performance, battery life, security, and privacy. In some cases, these can affect apps until they are updated to support Android Q, so you might see issues ranging from minor to signficant. In general, most apps work as expected, but please review the known issues listed below to get a better idea of what to expect from Android Q Beta 3.

You can install this release on any Pixel device or any of the devices from our partners that are listed in the Android Q Beta devices page. Android Q Beta 3 GSI system images are also available for testing. If you don’t have a physical device, you can test using the Android emulator. See Get Android Q for details on how to get started with Android Q Beta 3.

General advisories

Please be aware of these general notes about the release:

This release may have various stability, battery, or performance issues on supported devices.
For users with accessibility needs, this release may not be appropriate for daily use.
Some apps may not function as expected when running on this release. This includes Google’s apps as well as other apps.
Android Q Beta devices are not Compatibility Test Suite (CTS)-approved, but they have passed preliminary testing and provide a stable set of prerelease APIs for developers. Apps that depend on CTS-approved builds might not work as expected on Android Q Beta 3.
For a list of devices that can run Android Q beta, see the Android Q Beta Devices page.

Top issues for users

Users running Android Q Beta 3 are likely to see these general issues. Please report app-specific issues directly to the app developer.

Top open issues

Banking and finance apps might not work as expected.

Top resolved issues

Apps such as Google Photos and other photos/camera apps that were unable to find photos or videos should now be working properly.

Known issues, Android Platform

Bionic libraries and dynamic linker paths

Some apps and games that depend on DRM or security libraries might crash due to a change to Bionic libraries and dynamic linker paths in Android Q. App and library developers should read more detailed information in the Behavior Changes for All Apps.

Permissions

The Physical activity permission does not correctly control access to the user’s step count.

Android Enterprise

Device Policy Controller apps targeting Android Q should no longer call WifiManager.saveConfiguration(). This method is now deprecated.
Devices provisioned using a QR code may display a black screen after setup is complete. To continue, return to the device’s home screen.
If a manual system update is attempted on a device that already has a system update in progress, the device restarts.
If a fully-managed device that’s already provisioned is tapped against an NFC tag with valid provisioning parameters, the device triggers the provisioning flow instead of displaying a notification that it’s already set up.
If Hide sensitive work content is enabled for a work profile:
- The lock screen fails to hide the content of work profile notifications.
- The notifications drawer incorrectly hides work profile notification content.
Activities launched in a work profile don't honor the theme set on a device.
Devices in lock task mode don’t support fully gestural navigation.
The work profile security challenge screen doesn’t respond to the home gesture when fully gestural navigation is enabled.
Canceling work profile provisioning causes a device to crash.
Links to notification settings may not open from notification bubbles for apps that are only installed in a work profile.
It’s not possible to make calls from work profile contacts.

API changes

Hung renderer detection

The WebViewRendererClient class has been renamed to WebViewRenderProcessClient.
onRendererUnresponsive() has been renamed to onRenderProcessUnresponsive().
onRendererResponsive() has been renamed to onRenderProcessResponsive().

Android Q Beta 2 patch

Date: April 2019
Build: QPP2.190228.023
Emulator support: x86 (32/64-bit)
Security patch level: April 2019
Google Play services: 16.0.88
API diff:

API 28 → Beta2

Beta 1 → Beta2

About Android Q Beta 2 patch

This patch update for Android Q Beta 2 includes a small number of bug fixes for developers and early adopters. It is suitable for development, testing, and general use. Android Q Beta 2 is an early Beta and is still in active development, so the Android system and apps may not always work as expected.

As with previous versions, Android Q includes behavior changes to help improve performance, battery life, security, and privacy. In some cases, these can affect apps until they are updated to support Android Q, so you might see impacts ranging from minor issues to more significant functionality limitations. In general, most apps will work as expected, but please review the known issues listed below to get a better idea of what to expect from Android Q Beta 2.

You can install this release on any Pixel device and the Android emulator. See Get Android Q for details on how to get started with Android Q Beta.

General advisories

Please be aware of these general notes about this release:

This release may have various stability, battery, or performance issues on supported devices.
For users with accessibility needs, this release may not be appropriate for daily use.
Some apps may not function as expected when running on this release. This includes Google’s apps as well as other apps.
Android Q Beta devices are not Compatibility Test Suite (CTS) approved, but they have passed preliminary testing and provide a stable set of prerelease APIs for developers. Apps that depend on CTS-approved builds might not work normally on Android Q Beta 2.
Android Q Beta is available on Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, and Pixel 3 XL.

Top issues for users

Users running Android Q Beta 2 are likely to see these general issues. Please report app issues directly to the app developer.

Top open issues

Users might experience problems with apps that access photos, videos, media, or other files stored on your device, such as when browsing or sharing in social media apps.
Banking and finance apps might not work as expected.
Google Photos and other apps that work with photos and cameras might be unable to find photos or videos after you update your device to Beta 2. For ways to resolve the issue, see the Google Photos and Camera apps section below.

Top resolved issues

The following issues have been resolved in the patch update to Android Q Beta 2:

Apps that were crashing on startup because of issues with execute-only memory should now function normally. We’ve modified the associated Android Q behavior change so that it now applies only to apps targeting Android Q or higher, rather than to apps targeting API 26 or higher.
Permissions managed through Settings should now function normally after app re-installation or device reboot, including permissions for Unknown Sources and others. We’ve fixed the app ops issue that was causing the permissions to be reset.

Known issues, Android platform

Android Q Beta 2 contains the following known platform-related issues.

Access to files in external storage

Android Q introduces a new feature called Scoped Storage that gives users better control over app access to the Photos and Videos or the Audio collections via new runtime permissions. Apps can use their private sandbox without permission, but they need new permissions to access shared collections for photos, videos and audio. Apps using files in shared collections—for example, photo and video galleries and pickers, media browsing, and document storage—may behave differently under Scoped Storage.

We recommend getting started with Scoped Storage as soon as possible. The developer guide has details on key use cases. If you discover that your app has a use-case that’s not supported by Scoped Storage, please let us know as soon as possible.

In Beta 2, Scoped Storage is enabled by default for new app installs, as well as for app installs and restores after a full device reset in Beta 2. For testing, make sure to enable Scoped Storage for your app using the adb command.

Performance and battery

System and app performance is known to be periodically slow and janky, and devices may become occasionally unresponsive. These problems may become more acute with prolonged use.

Execute-only memory

In Android Q, executable segments of system-provided binaries/libraries are mapped into memory execute-only (non-readable) as a hardening technique against code-reuse attacks. This may affect some apps if they attempt to read the execute-only memory. See the documentation for this change for details on how to identify execute-only memory crashes and how to mark the segments that your app needs to read.

WebView

Users and apps may experience crashes when using a Beta version of WebView. To resolve, uninstall the update in Settings using the Uninstall update button on the app info page. Future beta versions of WebView will not be installed on your device until they are compatible with Q, so you should only need to do this once.

Android Enterprise

Device Policy Controller apps targeting Android Q should no longer call WifiManager.saveConfiguration(), as this method is deprecated.
If the admin of a work profile or fully managed device sets screen lock quality to complex, DevicePolicyManager.getPasswordComplexity() incorrectly returns PASSWORD_COMPLEXITY_NONE.
If a manual system update is attempted on a device that already has a system update in progress, the device will restart.
If Hide sensitive work content is enabled for a work profile:
- The lock screen fails to hide the content of work profile notifications.
- The notifications drawer incorrectly hides work profile notification content.
Activities launched in a work profile don't honor the theme set on a device.
Some provisioning screens may display incomplete graphics that resemble a loading animation (spinning circle). To proceed with provisioning, tap Next.
Devices provisioned using a QR code may display a black screen after setup is complete. To escape it, return to the device’s home screen.
If a fully managed device is provisioned with the extra PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED set to false:
- No search bar is displayed in Settings.
- The launcher prediction row shows the loading animation indefinitely.
If a fully managed device that’s already provisioned is tapped against an NFC tag with valid provisioning parameters, the device triggers the provisioning flow instead of displaying a notification that it’s already set up.

Known issues: Android Studio and tools

To compile and use Android Q SDK APIs, set the following in your app's build.gradle file:
```
compileSdkVersion: 'android-Q'
buildToolsVersion: "29.0.0 rc1"
targetSdkVersion: 'Q'
```
For Beta 2, the default value for android:extractNativeLibs was changed back to true from false in the <application> element for app manifest files. This restores the same behavior that existed prior to Android Q Beta 1.

For more information about the benefits of using android:extractNativeLibs="false", see Avoid extracting native libraries.
In some versions of Android Studio, building an app bundle with minSdkVersion="Q" might fail. This issue is now fixed in the bundletool 0.9.0 and Android Studio 3.4 RC2. If you are still seeing this issue, please update to the latest version of Android Studio in the canary or beta release channel.
If you use adb from Platform Tools 28.0.2 or higher, you might not be able to authorize an emulator (AVD) for adb access. The issue is fixed in Emulator Canary 28.1.12+ and Stable Emulator 28.0.25+. To resolve the issue, update to use Emulator 28.0.25 or higher on Stable or 28.1.12 or higher on Canary.
In Android Studio 3.3, the Profilers window is unable to load profilers for Android Q devices. Please update to the latest canary version of Android Studio for profiling on Android Q devices.
Android Q emulator may fail to boot in older versions of Android Studio. To resolve the issue, update to Emulator 28.1.12 or higher in the latest versions of Android Studio.

Known issues, Google apps

Based on our testing, you might encounter functional issues while using the Google apps below on Beta 2. These issues are already known, so there’s no need to file additional reports for similar issues.

Google Photos and Camera apps

Google Photos on Android Q Beta 2 may be unable to create collages or manage photos and videos as expected.
In some cases, the Google Photos app or other camera or photo app may be unable to store, find, or delete photos, videos, and screenshots after you update your device to Beta 2. If you experience issues with a camera app or photo gallery, try one of the workarounds below:

Reset the app’s storage permissions in Settings.
1. First, reset the storage permissions in the photos app. Go to Settings > Apps & notifications > Permission manager > Storage > <app name>. Set the storage permissions to Deny, and then reset the storage permissions to Allow.
2. Next, reset the storage permissions in the camera app. Go to Settings and reset the camera app by using the same method as described in step 1.
3. Clear the app’s cache. Go to Settings > Storage > <app name>, and press Clear cache.
4. Finally, if available, force stop the app. Go to Settings > Storage > <app name>, and press Force stop.
Reset the app’s permissions using the adb tool
- If the photo app and camera still do not function normally, use the adb tool to reset the permissions with the command below. Replace package-name with the package name of the app.
```
adb shell cmd appops set package-name android:legacy_storage allow && \
adb shell am force-stop package-name
```
For Google Photos, the command would be as follows:
```
adb shell cmd appops set com.google.android.apps.photos android:legacy_storage allow && \
adb shell am force-stop com.google.android.apps.photos
```
For Google Camera, the command would be as follows:
```
adb shell cmd appops set com.google.android.GoogleCamera android:legacy_storage allow && \
adb shell am force-stop com.google.android.GoogleCamera
```

Gmail

Gmail may experience crashes when using a Beta version of WebView. For more information, see the note on WebView above.

Known issues: Android Auto

Android Auto contains the following known issues in Android Q Beta 2.

Audio

Users might experience intermittent audio issues when using Android Auto from Android Q.

When a user attempts to invoke the Assistant by hotword, the Assistant sound plays, but the Assistant does not respond.
No sound is emitted when selecting a music app.
If the user receives a phone call while listening to music, audio is incorrectly rerouted to the phone speaker once the call is finished.
Audio skips approximately once per minute.

Permissions

Users might experience the following issues related to permissions on their devices.

Google Maps can't find the location of users in Android Auto if they have selected Allow only while the app is in use in Settings > Apps > Maps > Permissions > Location. Google Maps works as expected when selecting Allow all the time.
Waze freezes and does not refresh with current location if given While in use location permission.
Users can’t start wireless projection sessions with the HU if they don’t have the Always location permission set. If they have the While in use permission set, wireless connections won't work, although they can still connect to the HU via the USB cable.

Other

Users might also experience the following issues with Android Auto.

A warning toast is displayed upon starting Projection due to the background activity lockdown.
Users may not be able to connect to the car with the HU reporting that a "USB connect error has occurred".

Android Q Beta 2

Date: April 2019
Build: QPP2.190228.021
Emulator support: x86 (32/64-bit)
Security patch level: April 2019
Google Play services: 16.0.88
API diff:

API 28 → Beta2

Beta 1 → Beta2

About Android Q Beta 2

Welcome to Android Q Beta 2! This release is for developers and early adopters, and it’s suitable for development, testing, and general use. Android Q Beta 2 is an early Beta and is still in active development, so the Android system and apps may not always work as expected.

As with previous versions, Android Q includes behavior changes to help improve performance, battery life, security, and privacy. In some cases, these changes can affect apps until they are updated to support Android Q, so you might see impacts ranging from minor issues to more significant functionality limitations. In general, most apps will work as expected, but please review the known issues listed below to get a better idea of what to expect from Android Q Beta 2.

You can install this release on any Pixel device and the Android emulator. See Get Android Q for details on how to get started with Android Q Beta.

General advisories

Please be aware of these general notes about the release:

This release may have various stability, battery, or performance issues on supported devices.
For users with accessibility needs, this release may not be appropriate for daily use.
Some apps may not function as expected when running on this release. This includes Google’s apps as well as other apps.
Android Q Beta devices are not Compatibility Test Suite (CTS)-approved, but they have passed preliminary testing and provide a stable set of pre-release APIs for developers. Apps that depend on CTS-approved builds might not work normally on Android Q Beta 2.
Android Q Beta is available on Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, and Pixel 3 XL.

Top user-facing issues

Users running Android Q Beta 2 are likely to see these general issues. Please report app issues directly to the app developer.

Users might experience problems with apps that access photos, videos, media, or other files stored on your device, such as when browsing or sharing in social media apps.
Banking and finance apps might not work as expected.
Some apps might crash on startup because of legacy behaviors.
Some permissions managed through Settings may need to be set again after app re-installation or device reboot, including Unknown Sources and others.

Updated features

Android Q Beta 2 contains the following updates to features released in previous versions of the beta program.

Launcher icon visibility

In Android Q Beta 2, packages that don't declare any permissions in their respective manifest files are hidden from the All apps tray, as are the following types of apps:

System apps
Apps that don't contain any components inside their respective manifest's <application> tag

Known issues: Android platform

Android Q Beta 2 contains the following known platform-related issues.

Access to files in external storage

Performance and battery

System and app performance is known to be periodically slow and janky, and devices may become occasionally unresponsive. These problems may become more acute with prolonged use.

Permissions

Because of an issue in app ops, some permissions managed through Settings may have to be re-set each time an app package is installed and on reboot. This will be fixed in a future beta.

Execute-only memory

WebView

Android Enterprise

Device Policy Controller apps targeting Android Q should no longer call WifiManager.saveConfiguration(), as this method is deprecated.
If the admin of a work profile or fully managed device sets screen lock quality to complex, DevicePolicyManager.getPasswordComplexity() incorrectly returns PASSWORD_COMPLEXITY_NONE.
If a manual system update is attempted on a device that already has a system update in progress, the device will restart.
If Hide sensitive work content is enabled for a work profile:
- The lock screen fails to hide the content of work profile notifications.
- The notifications drawer incorrectly hides work profile notification content.
Activities launched in a work profile don't honor the theme set on a device.
Some provisioning screens may display incomplete graphics that resemble a loading animation (spinning circle). To proceed with provisioning, tap Next.
Devices provisioned using a QR code may display a black screen after setup is complete. To escape it, return to the device’s home screen.
If a fully managed device is provisioned with the extra PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED set to false:
- No search bar is displayed in Settings.
- The launcher prediction row shows the loading animation indefinitely.
If a fully managed device that’s already provisioned is tapped against an NFC tag with valid provisioning parameters, the device triggers the provisioning flow instead of displaying a notification that it’s already set up.

Known issues: Android Studio and tools

To compile and use Android Q SDK APIs, set the following in your app's build.gradle file:
```
compileSdkVersion: 'android-Q'
buildToolsVersion: "29.0.0 rc1"
targetSdkVersion: 'Q'
```
For Beta 2, the default value for android:extractNativeLibs was changed back to true from false in the <application> element for app manifest files. This restores the same behavior that existed prior to Android Q Beta 1.

For more information about the benefits of using android:extractNativeLibs="false", see Avoid extracting native libraries.
In some versions of Android Studio, building an app bundle with minSdkVersion="Q" might fail. This issue is now fixed in the bundletool 0.9.0 and Android Studio 3.4 RC2. If you are still seeing this issue, please update to the latest version of Android Studio in the canary or beta release channel.
If you use adb from Platform Tools 28.0.2 or higher, you might not be able to authorize an emulator (AVD) for adb access. The issue is fixed in Emulator Canary 28.1.12+ and Stable Emulator 28.0.25+. To resolve the issue, update to use Emulator 28.0.25 or higher on Stable or 28.1.12 or higher on Canary.
In Android Studio 3.3, the Profilers window is unable to load profilers for Android Q devices. Please update to the latest canary version of Android Studio for profiling on Android Q devices.
Android Q emulator may fail to boot in older versions of Android Studio. To resolve the issue, update to Emulator 28.1.12 or higher in the latest versions of Android Studio.

Known issues: Google apps

Google Photos

On Android Q Beta 2, Google Photos might be unable to create collages or manage photos and videos as expected.

Known issues: Android Auto

Android Auto contains the following known issues in Android Q Beta 2.

Audio

Users might experience intermittent audio issues when using Android Auto from Android Q.

When a user attempts to invoke the Assistant by hotword, the Assistant sound plays, but the Assistant does not respond.
No sound is emitted when selecting a music app.
If the user receives a phone call while listening to music, audio is incorrectly rerouted to the phone speaker once the call is finished.
Audio skips approximately once per minute.

Permissions

Users might experience the following issues related to permissions on their devices.

Google Maps can't find the location of users in Android Auto if they have selected Allow only while the app is in use in Settings > Apps > Maps > Permissions > Location. Google Maps works as expected when selecting Allow all the time.
Waze freezes and does not refresh with current location if given While in use location permission.
Users can’t start wireless projection sessions with the HU if they don’t have the Always location permission set. If they have the While in use permission set, wireless connections won't work, although they can still connect to the HU via the USB cable.
A warning toast is displayed upon starting Projection due to the background activity lockdown.
Users may not be able to connect to the car with the HU reporting that a "USB connect error has occurred".

Android Q Beta 1

Date: March 2019
Build: QPP1.190205.018.B4 (Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL)
Emulator support: x86 (32/64-bit)
Security patch level: March 2019
Google Play services: 12.4.46
API diff: API 28 → Beta1

General advisories

This Beta release is designed for use in compatibility testing and early development only. Please be aware of these general notes about the release:

This release may contain various stability and performance issues on devices that may make it not suitable for daily use on phone or tablet.
System and app performance are known to be periodically slow and janky, and devices may become occasionally unresponsive.
Battery life may be regressed in this early release for screen-on and screen-off use cases.
Some apps may not function normally on Beta 1. This includes Google's apps as well as other apps.
This early build is not Compatibility Test Suite (CTS) approved.
This initial beta release of Android Q is available as an OTA update as well as through the Android Beta program.

New features

Android Q Beta 1 includes the following new features.

Launcher icon visibility

In Android Q, the All apps tray displays a launcher icon for every package installed on the device, except for the following cases:

System apps
Apps that don't contain any components inside their respective manifest's <application> tag

Importantly, if an app contains code but doesn't have a launchable activity, its icon still appears in the All apps tray. When users select this icon, they're taken to the app's settings screen.

Known issues

Performance and battery

System and app performance is known to be periodically slow and janky, and devices may become occasionally unresponsive. These problems may become more acute with prolonged use.
Battery life may be regressed in this early release for screen-on and screen-off use cases.

New features

Launcher icon visibility - In Android Q, the All apps tray displays a launcher icon for every package installed on the device, except for the following cases:
- System apps
- Apps that don't contain any components inside their respective manifest's <application> tag
Importantly, if an app contains code but doesn't have a launchable activity, its icon still appears in the All apps tray. When users select this icon, they're taken to the app's settings screen.

Android Beta Feedback app

Sharing a screenshot with the app directly from the system notification may result in a crash. To mitigate this, share your screenshot from the Files app.
If using a work profile, granting the Phone permission to the app may cause uploads to fail or crash the app. To mitigate this, disable or deny the Phone permission in the app settings.

Android Studio

To compile and use Android Q SDK APIs, set the following in your app's build.gradle file:
- compileSdkVersion "android-Q"
- buildToolsVersion "29.0.0 rc1"
- targetSdkVersion "Q"

SDK

Android Studio occasionally encounters delays when profiling using an Android Q emulator system image.
If you are still using legacy appcompat support libraries (com.android.support), Android Studio produces a lint warning that this support library should not use a different compileSdkVersion. Version 28 is the final version of com.android.support, so we recommend that you migrate to AndroidX libraries (androidx.appcompat) moving forward. This lint warning does not trigger when using AndroidX libraries.
For Beta 1, the default value for android:extractNativeLibs was changed from true to false in the <application> element for app manifest files. If your app targets Android Q, contains native code, and does not explicitly specify android:extractNativeLibs="false", you should set android:extractNativeLibs to true in your app’s manifest file to preserve your app’s current behavior. For more information about the benefits of using android:extractNativeLibs="false", see Avoid extracting native libraries.

For apps with minSdkVersion="Q", building an app bundle fails with an error message similar to the following:

Execution failed for task ':app:packageDebugBundle'.
> java.util.concurrent.ExecutionException: com.android.tools.build.bundletool.utils.xmlproto.UnexpectedAttributeTypeException: Attribute 'minSdkVersion' expected to have type 'decimal int' but found:
  namespace_uri: "http://schemas.android.com/apk/res/android"
  name: "minSdkVersion"
  value: "Q"
  resource_id: 16843276

We expect to have an update for this issue later in the Beta cycle.

When using Gradle 3.2.0 for projects targeting Android Q, you might encounter a lint-related issue with an error message similar to "Could not transform android.jar to a mockable jar." This issue does not occur in Gradle 3.3.0 and later.

If you are working on an app that targets Android Q and are unable to upgrade to Gradle 3.3.0 or later, you can use one of the following workarounds:
- Disable lint for release builds
- Unzip and rezip android.jar

Android Enterprise

Activities launched in a work profile don't honor the theme set on a device.
If a fully managed device is provisioned with the extra PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED set to false, no search bar is displayed in Settings.
The user restriction DISALLOW_CONFIG_PRIVATE_DNS also prevents Device Policy Manager from configuring private DNS on a fully managed device. As a workaround, the caller should first configure the Private DNS mode and then set the user restriction.
Device Admin settings screen shows duplicate entries.