Now that the first Android 15 developer preview has been released on all supported Pixel devices, it's safe to assume that your fingers will want to give it a try. If you want to install it on your Pixel, you can follow the steps below in the guide here.
However, if you are still on the fence about installing Android 15 Developer Preview on your device because you are too afraid of possible errors, then this article is for you as we list all the known issues.
Keep in mind that these known issues are reported by Google. This means that the company is actively working on fixing them.
Android platform
An issue with sideloading the Developer Preview 1 release sometimes caused the device to display a "Device is corrupted" message after the sideload is complete. Due to the potential disruption that this issue can cause, we've temporarily disabled the OTA image until we can troubleshoot the issue further. To resolve this issue, we recommend that developers flash the factory image and test the device instead.
When you add a face model for Face Unlock, the preview screen appears to be trimmed or cropped.
When the app window transitions to Picture-in-Picture (PIP) mode, the picture-in-picture window disappears if the device rotates before the picture-in-picture conversion is complete.
When a locked SIM card is inserted into an unlocked device, the user is not prompted to enter a PIN to unlock the SIM card. To resolve this issue, manually lock and unlock the device.
Android Studio & Tools
The Android 15 Preview API level (Van IllaiceCream) does not appear in the preview configuration window.
In some cases, the latest version of the Android SDK build-tools that includes the Android 15 Preview SDK isn't available when checking for updates in Android Studio.
When configuring a new project in Android Studio, the Android 15 Preview SDK version is not listed in the target SDK version and minimum SDK version drop-down menus.
Sometimes, if an Android virtual device (*d) using an Android 15 system image boots in embedded mode, the virtual device (*d) fails to boot.
If you boot an Android virtual device (*d) with an Android 15 system image and then reboot using Adb Reboot or another method, the virtual device (*d) will appear offline.
There is an issue with the Android emulator that sometimes prevents the app from redeploying to the Android virtual device (*d) after **d is closed.
There was an issue with the Android emulator that caused the hearing device accessibility shortcut to launch multiple settings app windows.
There is an issue with the Android emulator that causes the notification window to flicker when typing a direct reply.
An issue with the Android emulator sometimes causes the authentication flow in the app to fail with a "Google Play Services keeps stopping" message.
There is an issue with the Android emulator that causes **Perf to crash when running the CPU profile.
There is an issue with the Android emulator that is causing the languages listed in the system language settings to display incorrect characters.
Problems with the Android emulator can sometimes cause the QR code scanner to display a "Something is wrong" message and fail to launch.
On some Android virtual devices, the viewfinder of the Android QR code scanner is sometimes cropped or resized to a smaller size.
Skia is not yet compatible with the Android 15 Preview SDK, which prevents 3D mode from being enabled in the Layout Inspector.
There is an issue in Android Studio that causes Device Manager to temporarily stop displaying "Missing System Image. A warning message appears after adding or removing SDK platforms using the SDK Manager.
In some cases, there was an issue with the Android emulator that didn't load the Google Discover feed.
Applications
The Google Play Store sometimes crashes with a null pointer exception when trying to update an app.
The Google TV app sometimes fails to launch*** and instead displays the message "**Movies & TV is temporarily unavailable".
Google also claims that all of these issues are known, which means that if you're using Android 15 Developer Preview, then you don't actually have to keep reporting them. We have mentioned several times that you should only install this update if you are satisfied with the issues that exist here. If you want a smoother experience, then you shouldn't go for it.