Android P Support and Release Notes

Two primary support channels are available to you when developing and testing with the Android P Developer Preview: Please file bugs at device-specific, system, and Google App bugs. For issues in other apps, please contact the developer directly.

To discuss issues or ideas with other developers working with Android P Developer Preview, join the Developer Preview Google+ community.

Developer Preview 1

Date: March 2018
Build: PPP1.180208.014 (Pixel, Pixel XL, Pixel 2, Pixel 2 XL)
Emulator support: x86 & ARM (32/64-bit)
Security patch level: March 2018
Google Play services: 12.4.46
API diff: API 27 → DP1

General advisories

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

  • This release has various stability and performance issues on all devices that make it not suitable for daily use on phone or tablet, especially for non-developers.
  • System and app performance are 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.
  • Some apps may not function normally on Developer Preview 1. This includes Google’s apps as well as other apps.
  • This early build is not Compatibility Test Suite (CTS) approved.
  • This initial release of Android P Developer Preview is available by manual download only. OTA updates through the Android Beta Program aren’t supported for this release. Android P will be available through the program in the next Preview milestone.

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.

System UI

  • The Google Assistant doesn’t recognize the “Ok Google” hotword if it’s trained during setup. By retraining the Google Assistant after finishing the setup workflow, however, you can then use the hotword.
  • The Google Assistant doesn’t load any information for the “What’s on my screen” query.
  • The following issues occur after selecting a simulated device cutout (Settings > System > Developer options > Drawing > Simulate a display with a cutout):
    • Popup windows, those that have set the FLAG_LAYOUT_NO_LIMITS parameter, extend under the cutout.
    • In landscape mode, the status bar takes up too much vertical space near the top edge of the device.
    • In landscape mode, the system reports too high a value for the width of the window that an app can use to display its UI.
    • If a window overlaps with the area next to the cutout, but not with the cutout itself, DisplayCutout is set to null.
  • If the Google Assistant is launched after docking multiple apps in split-screen mode, pressing the Home button doesn’t display the complete home screen.
  • When recording a new pattern for unlocking the device, the system only shows the first few segments of the pattern.
  • When the Autofill UI is shown for an app and the app is killed, the UI might remain shown until the device is restarted.
  • When viewing the All Apps screen, the WallpapersWidgets, and Home Settings buttons each appear in white near the bottom of the screen.


  • Zero-touch enrollment, when provisioning a device, incorrectly shows an error dialog stating the device is already set up.
  • The system spell checker isn’t available to apps in the work profile which means misspelled words aren’t highlighted.
  • The DISALLOW_SHARE_INTO_MANAGED_PROFILE user restriction doesn’t prevent a device user from pasting clipboard data into a work profile.
  • After tapping the Back button from apps running in LockTask mode, a device user might return to the launcher.
  • The Google Apps Device Policy app doesn’t complete provisioning of a device or work profile when setting a corporate account in the Setup Wizard. The device user returns to the Setup Wizard after provisioning. As a workaround, device users can provision a work profile by adding an account in the Settings app.
  • Work apps’ badges are rendered incorrectly intermittently.
  • In Quick Settings, the “Device is managed by your organization” disclosure is obscured by the carrier name.


Interactions with Android Studio

  • If you add widgets like RecyclerView and GridLayout to an Instant App, older versions of the respective libraries are added as dependencies.
  • If you create a TV or Wear project and set the minimum SDK version to 'P', the Gradle sync fails.
  • If you create a project with a basic activity and set the minimum SDK version to 'P', an exception occurs in the Studio core process.