The first Android P Developer Preview is causing problems for some Pixel and Pixel 2 users and today we want to take you through what you need to know about these early Android P problems.
Google’s released an Android P beta ahead of the update’s official release for Pixel devices in the third quarter of the year. The company’s Nexus 6P and Nexus 5X aren’t included in beta testing and neither device will get Android P when it officially touches down.
The company’s Android P Developer Preview gives Pixel users a chance to try the operating system’s new features ahead of the public release and it also helps Google squash bugs before the software ships out to thousands of people around the world.
The Android P Developer Preview is exciting, but like most betas, it’s plagued with a variety of problems. Some of these issues are minor bugs, others are far more problematic.
If you’re thinking about trying Android P ahead of its official release, you should be familiar with these issues before you install. This way you won’t be caught off guard if and when something goes wrong.
If you’re already testing Android P on your device you should be keeping an eye out for problems and reporting what you see to Google so it can improve the final product.
In this guide we’ll take you through these early Android P problems, provide you with potential fixes, show you where to find Android P feedback, show you how to report bugs, and tell you about what’s coming next for Android P users.
Android P Problems
The first Android P Developer Preview is suffering from a variety of issues including bugs and various performance issues. Google’s highlighted several of these.
According to Google, system and app performance on Android P can be “periodically slow and janky” and devices “may become occasionally unresponsive.” The company says these issues might become more acute with prolonged use.
Google says Android P battery life “may be regressed in this early release for screen-on and screen-off use cases”. It also says some apps (including its own) may not function normally on Developer Preview 1. This is precisely why some people should stay put on Android Oreo.
Other known Android P problems include:
- 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 Wallpapers, Widgets, 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.
- Bluetooth crashes if a Host Controller Interface (HCI) command times out.
We’ve also heard about Android P installation issues, lockups and freezes, sound problems, issues with fingerprint sensors, and various connectivity (Bluetooth, Wi-Fi, GPS) problems.
How to Report Android P Problems
If you do see an Android P problem on your Pixel, Pixel XL, Pixel 2, or Pixel 2 XL you’ll want to report the issue to Google . Your feedback will help the company identify and fix issues, and help add polish to the final release. There are a few different ways to send feedback about Android P.
- If you find an issue in the Android platform or APIs, NDK, Android runtime (ART), device hardware, or support libraries, you can send Google your feedback right here.
- If you discover an app that’s not working properly with Android P you’ll want to report your issue right here.
- And if you find an issue with a third-party SDK, you can report the issue here.
You can also track the status of Android P issues using the newly upgraded the Developer Preview issue tracker. This is the same tracker tool Google uses.
How to Fix Android P Problems
If you run into Android P issues you can’t rely on Google to fix your problems. Beta updates won’t come every week and the next release will probably bring its own collection of bugs.
If you decide to try Android P you’ll need to be extremely proactive when it comes to fixing issues. Fortunately, there are a ton of resources out there.
Our broad list of fixes for the most common Nexus Android issues is a great place to start if you’re struggling on the beta. We’ve also put together more specific guides to fixing Pixel and Pixel 2 issues.
Our guides will show you how to fix bad battery life, issues with Wi-Fi, problems with Bluetooth, random reboots, and many other issues.
If you’re unable to find a fix for your problem there, and there’s no guarantee you will, you’ll want to take a look at Google’s Pixel help forum. XDA’s Pixel and Pixel 2 forums are also excellent resources.
Where to Find Android P Feedback
If you rely on your phone for work or school projects and communication, you’ll definitely want to consider staying put on Android 8.1.
There are some benefits to installing Android P right now, but many Pixel users are better of on official software. At least for now. Google will improve Android P over time so it might be worth it to wait a few more weeks for the second or third preview to arrive.
To assist you we’ve put together a guide that will take you through the best reasons to, and not to, install Android P on your Pixel or Pixel 2.
As we push away from the Android P release date, you’ll want to monitor feedback from Android P users. We’re seeing feedback emerge on social media sites like Twitter and YouTube and We’re also it on Google’s Pixel Help Forums, XDA-Developers, and Android-centric forums like Android Central Forums.
Short-term feedback can be extremely useful, but you’ll also want to make sure you dig into long-term feedback from Android P users if you’re on the fence about installing the early software.
Google’s release an official Android P release timeline and it’ll be a few weeks before the company rolls out the second Developer Preview with bug fixes for some of these early issues.
The second beta is slated to arrive sometime in early May. After that, Google will ramp things up with two developer previews (three and four) set for June. The fourth Android P beta will be the first release candidate.
The fifth developer preview will arrive sometime in July or August followed by an official release in Q3.
Each of these previews will come with its own set of issues, but expect the later versions of Android P to be far more polished than these early builds.
March Nexus 5X Android 8.1 Oreo Impressions
Before we get into an early look at the update's performance on the Nexus 5X, a few notes about the installation process.
If you're currently running the Android 8.1, and we assume most of you are, it shouldn't take you too long to transition from an older Android 8.1 build to this one.
It took us just a few minutes to download and sideload the software onto our Nexus 5X.
We've been using the March Android 8.1 Oreo on the Nexus 5X for a few days now and the update is performing well in key areas including battery life, connectivity, and UI speed.
Battery drain is a common Android problem, but we haven't noticed anything on our Nexus 5X. Battery life is about the same as it was on the last build.
If you do start to encounter battery life issues, take a look at our guide to fixing bad Android Oreo battery life.
We've been able to connect the Nexus 5X to multiple routers including eero mesh Wi-Fi. Speeds are fast and reliable. We've also successfully connected the Nexus 5X to several Bluetooth devices including headphones and speakers.
The Nexus 5X feels snappy with the new Android 8.1 build on board. It's still early, but animations and transitions are smooth and we haven't experienced any lag or general sluggishness.
So far so good. That said, if you're feeling leery, you probably should wait for the OTA. If you're feeling especially nervous, wait for long-term feedback to arrive.