[Nexus 6P General] i42o:
Known Issues

Accessibility

Unable to listen to TTS output when pitch is set near maximum level.

Accessibility features and settings may be disrupted with the user adds a Work profile, including magnification gesture and setting. Accessibility state is restored when the user next touches the associated settings.

Camera

The Camera app has exhibited instability; it may crash in various circumstances, such as when launched in multi-window mode.

Pressing the shutter continuously in panorama mode may cause the Camera app to crash.

Audio

A platform audio player issue prevents some apps from functioning normally. For example, Skype and other apps are affected by this issue.

Connectivity

When a Bluetooth Low Energy (BLE) peripheral role device advertises a service and a BLE central role device connects, the peripheral role device disconnects very quickly.

Wi-Fi connection may be dropped when the screen is off.

RFCOMM connections are unstable and may result in data corruption and dangling connections.

The active network state (NetworkInfo.getState() and NetworkInfo.getDetailedState()) might return incorrect values during some restricted background scenarios.

Launcher

The default launcher’s All Apps tray may become unresponsive after cycling screen off / screen on. Returning to the homescreen and relaunching the All Apps tray may resolve this issue.

Keyboard

When updating a device running Android 6.0 or earlier to the N Developer Preview, Google Keyboard does not preserve preferences data such as recent emoji and sound settings.

Google Indic Managed Keyboard may be unstable.

When entering text in a password field, the user can select Russian as the input language but the keyboard remains in English. This prevents the user from entering Russian-language passwords.

Locale and languages

When using a right-to-left (RTL) locale, the system may unexpectedly switch to left-to-right (LTR) presentation after restarting the device.

Media

Media playback be be unreliable on Nexus 9 and Nexus Player, including issues playing HD video.

Multi-window mode

Device may freeze when changing orientation in multi-window mode.

Several apps currently have issues with multi-window mode:

The system UI may crash when docking Settings > Display > Screen brightness to multi-window.

The Camera app may crash when launched in multi-window mode.

YouTube may crash when launched into multi-window mode. To fix the issue, you can clear the YouTube app’s data at Storage > Apps > YouTube.

Google Play services

Apps using Google Cast through Google Play services may be unstable when the user selects a system locale that uses letters and numbers outside of the ASCII range.

Work and enterprise

The Device Policy app may crash when the user unlocks the device with the "device policy status" screen pinned.

After setting up a work profile with file-based encryption enabled and then turning off Work, users must unlock primary profile screen lock to once again access Work apps.

Cannot open work apps after reboot in file-based-encryption with work mode off.

Device reboots when removing the security pattern lock and opening work app/personal app in the multi-window.

Setting DISALLOW_VPN_CONFIG is causing the consent dialog to appear in always-on-vpn set by Device Policy Client.

Traffic is not locked down until VPN is connected in always-on-vpn mode.

External storage

Apps may become unstable when the user moves them from internal storage to adoptable external storage (this can include SD card or devices attached over USB).

Screen zoom and multiple APKs in Google Play

On devices running Android N, Google Play services 9.0.83 incorrectly reports the current screen density rather than the stable screen density. When screen zoom is enabled on these devices, this can cause Google Play to select a version of a multi-APK app that’s designed for smaller screens. This issue is fixed in the next version of Google Play services and will be included in a later Developer Preview release.

On devices running Android N, Google Play services 9.0.83 currently reports Vulkan support but not Vulkan version. This can cause Google Play to select a version of a multi-APK app that’s designed for lower Vulkan support on devices with higher version support. Currently, the Google Play Store does not accept uploads of Apps which use Vulkan version targeting. This support will be added to the Google Play Store in the future and fixed in the next version of Google Play services (to be included in a later Developer Preview release) any N devices using the version of Google Play services 9.0.83 will continue to receive versions of Apps targeting basic Vulkan support.

Notifications

MessagingStyle does not show notifications with "null" (self) sender.

Developer Preview 3

I'll wait... Lol.