Known Issues With The Android N Developer Preview

Android N AH 00074

Today is one of the biggest days in the Android calendar for this year, as today is the day when Google released the latest version of Android, Android N. This is of course, only a preview version and one which is primarily designed for developers to get to better grips with the changes included, while also providing a more wide-scale level of feedback on the various bugs and issues that might be encountered. As a result, this is not intended for Android device owners to make use of as a daily operating system.

That said and in spite of being aimed at developers, it is likely a number of Android device owners will choose to download the factory images and test out the latest features that are on offer with Android N. If you are someone who is planning on flashing the latest image to your Nexus device, then it is worth knowing what are some of the issues with this very early and alpha release of Android N. Thankfully, Google has detailed a number of them.


In the release notes for this first developer preview Google notes that the performance of apps and the system in general is “periodically slow / janky” further noting that devices could “become occasionally unresponsive“. Google also adds that the longer you use the preview for, the more apparent this particular issue becomes. In addition, a number of apps are said to be not functionally as expected with the developer preview, including a number of the Google apps. Following which, a number of CTS approved apps like Android Pay do not seem to be functioning either. Adding to the list of known issues, battery life is also affected for both screen-on and screen-off usage. In fact, these issues listed are just the main overriding issues and Google does note that there are a number of further specific issues with the likes of the dialer, System UI, Android for Work, Keyboard, Video playback, Wi-Fi, split-screen multi-window, picture-in-picture, Bluetooth pairing and general issues during booting. As such there is too many to detail in full here, but those interested in reading a full breakdown of all the known issues can do so by clicking here.