Last Updated on
Android 12 Beta 4 has been deemed the first stable build by Google, but ultimately, it’s not the final product. It’s always wise to know with an unreleased operating system what its current issues are and whether you can deal with them or not. make sure to bookmark our Android hub for any guidance you may need with Google’s titanic operating system.
Developer-reported issues
- Fixed various issues with WebView that could make apps crash intermittently.
- Fixed an issue where the date did not appear in the notification shade. (Issue #189569006)
- Fixed issues where a device sometimes stopped responding to touch input in apps or on the Home screen. (Issue #189426854)
- Fixed an issue where screen-on time was missing from battery usage information in the Settings app. (Issue #188657464)
- Fixed an issue where the estimated amount of remaining battery in the status bar displayed off of the screen. (Issue #188616134)
- Fixed an issue where sometimes a black bar appeared on the lock screen. (Issue #190738110)
- Fixed an issue where the App Overview button stopped working when using 3-button navigation. (Issue #188969484)
- Fixed an issue where volume controls and sliders were not displayed correctly. (Issue #190795682)
- Fixed an issue where the brightness slider in Quick Settings moved to the minimum value when the phone was locked. (Issue #190784671)
- Fixed an issue where the phone locked when launching the camera by double-pressing the power button. (Issue #188797848)
- Fixed issues where the system incorrectly applied fullscreen and immersive mode on the home screen and in some apps. (Issue #189233176, Issue #180691018)
- Fixed an issue where the page indicator dots for Quick Settings were incorrect. (Issue #189108526)
- Fixed an issue where the notification shade sometimes flickered when swiping down to access notifications. (Issue #189744186)
- Fixed an issue where sometimes the brightness was lower on one half of the screen when viewing apps in landscape mode. (Issue #190064553)
- Fixed an issue where the phone indicated that a phone call was still ongoing even after the call had ended. (Issue #191838222)
- Fixed issues that prevented notification bubbles from opening in some apps. (Issue #189350738)
- Fixed an issue where toggling wallet options off in a device’s lock screen settings did not remove wallet options from the lock screen. (Issue #190805901)
- Fixed an issue where the Settings app crashed when a user tried to access Themes and Styles settings. (Issue #190786058)
- Fixed issues that prevented some apps from printing files or photos. (Issue #190169675)
- Fixed an issue where the icon in the volume slider was not centered when the volume was set to the minimum level. (Issue #190577754)
Other resolved issues
- Fixed an issue where app icons were sometimes cut off when using the SplashScreen API.
- Fixed an issue where, after setting an Animated Vector Drawable and a setOnExitAnimationListener(), the vector drawable’s animation stopped when the callback was called.
- Fixed an issue for devices that had both a device-wide password and a work profile security challenge where the work challenge did not prompt the user to unlock when a user tapped a work app’s notification on the lock screen.
Android 12 Beta 3 Known Bugs and Issues
All apps
- In some scenarios, users of apps that have been granted the Display over other apps permission and render full-screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
- When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.
Google apps
- In some cases after updating a device to Beta 3, Google Maps crashes whenever it is launched by a secondary user.
Android platform
- For devices with multiple users, in some cases after updating the device to Beta 3, the device crashes and reboots when trying to switch to a secondary user.
Android Studio and tools
- When installing an app that has a targetSdkVersion of “S” from Android Studio, developers might see the following error:
“Installation did not succeed.
The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
List of apks:
[0] ‘…/build/outputs/apk/debug/app-debug.apk’
Installation failed due to: ‘null’”
- The likely cause is that one or more of the app’s activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest preview release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.
- The latest preview version of the Android SDK Build Tools (31.0.0) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.
Android Auto
- When playing music on Youtube Music on Android Auto, some users may experience audio playing out of the phone instead of the vehicle speakers or no audio at all in Toyota Cars.
- When using Google Maps navigation on Android Auto, some users may experience issues with text being blurry.
- Users may face issues while selecting a destination in Waze.
- Phone may become unresponsive or stuck on the lock screen after starting Android Auto.
- In some scenarios, Google Maps might not be able to provide different route options while using Android Auto.
- Music may get paused when the phone is locked.
- Users might hear Music audio while trying to reply to an SMS using Google Assistant.
- Automatic Day and Night switching may not work.
Android TV
- Hotplugging the HDMI cable might cause video playback to fail on some display sinks.
The best way to find bugs and issues with an operating system such as Android 12 is to release a Beta or Developer version, such as Android 12 Beta 4, for the masses to report back on what issues they’ve been having. It’s free quality assurance testing and some great publicity for Android 12 features.
Android 12 Beta 4 Fixed Errors, Bugs and Issues
If you’re ready to install Android 12 Beta 4, head over to our How-To page that covers OEM and Pixel installations. If you’re still unsure and need a bit of positive encouragement, here are some of the fixes present in Android 12 Beta 4:
Developer-reported Issues
- Fixed issues that prevented some notifications about missed calls from being dismissed. (Issue #193718971, Issue #194388100)
- Fixed issues where system theme colors did not apply to some Quick Settings tiles. (Issue #190633032, Issue #190338020)
- Fixed an issue where Quick Settings tiles did not align to the grid when dragging or rearranging them. (Issue #188641280)
- Fixed an issue where the alarm and mute icons did not display in the notification bar. (Issue #186769656)
- Fixed an issue where the primary Home screen was blank when swiping back to it from another page. (Issue #189435745)
- Fixed an issue where, when a Bluetooth device was connected, audio could not be heard after routing the audio to the phone during a call. (Issue #192585637)
- Fixed an issue where the Calendar widget wouldn’t load after it was added to the Home screen. (Issue #188799206)
- Fixed an issue where toggles for some options in the Settings app were not visible. (Issue #193727765)
- Fixed an issue where widgets would sometimes disappear after restarting the device. (Issue #191363476)
- Fixed an issue where RCS messages did not work when a VPN was active. (Issue #189577131)
- Fixed issues that sometimes caused devices to crash and restart. (Issue #194272305)
- Fixed an issue that caused multiple notifications about foreground service launch restrictions to display. (Issue #194081560)
- Fixed an issue where the wrong app would sometimes open when opening an app from the dock or Home screen area. (Issue #194766697)
- Fixed an issue where double-tapping the device’s screen would not wake it in some cases. (Issue #190453834)
- Fixed an issue where the cell signal strength was not displayed in the status bar. (Issue #190894572)
- Fixed an issue where if a screen recorder was active, the notification shade did not animate properly when closing. (Issue #191276597)
Other resolved issues
- Fixed an issue where, when playing music on Youtube Music on Android Auto, some users experienced audio playing out of the phone instead of the vehicle speakers or no audio at all in Toyota Cars.
- Fixed an issue where, when using Google Maps navigation on Android Auto, some users experienced issues with text being blurry.
- Fixed an issue where users couldn’t select a destination in Waze while using Android Auto.
- Fixed an issue where the phone became unresponsive or stuck on the lock screen after starting Android Auto.
- Fixed an issue where, in some scenarios, Google Maps could not provide different route options while using Android Auto.
- Fixed an issue on Android Auto where music would pause when the phone was locked.
- Fixed an issue on Android Auto where users sometimes heard Music audio while trying to reply to an SMS using Google Assistant.
- Fixed an issue on Android Auto where Automatic Day and Night switching did not work.
Android 12 Beta 4 Known Bugs and Issues
For top unresolved bugs and errors, Google has its own Issue Tracker for Android 12 Beta 4 here. This is great for reporting undiscovered bugs, but here’s a list of known issues that are currently being worked on:
All apps
- In some scenarios, users of apps that have been granted the Display over other apps permission and render full-screen overlays might find touches blocked on Android 12 until the developer updates the app. Affected users can temporarily turn off the permission in Settings, which can always be accessed using the settings icon in the notification shade. If an app you use is affected by this issue, you can contact the app developer directly to let them know.
- When a user attempts to add another account to the device under Settings > Passwords & accounts, the UI turns black and the back button becomes unresponsive.
Google apps
- When connected to a Bluetooth headset, users running the beta version of the Phone app might experience a crash loop when trying to make a call. This issue is caused by the Phone app not having the required Nearby Devices’ permission. In addition, users can’t grant the Nearby Devices permission to the Phone app either from the Permissions screen in App info, or through the Permissions manager.
To work around these issues, users can grant the Nearby Devices permissions to the Phone app using the following adb commands. If you need to set up adb first, see Connect to a device over Wi-Fi.
“adb shell pm grant com.google.android.dialer android.permission.BLUETOOTH_SCAN && adb shell pm grant com.google.android.dialer android.permission.BLUETOOTH_CONNECT && adb shell pm grant com.google.android.dialer android.permission.BLUETOOTH_ADVERTISE”
- Users should also check the Play Store for any Phone by Google beta updates that are available to receive the latest fixes.
- In some cases after updating a device to Beta 4, Google Maps crashes whenever it is launched by a secondary user.
Android platform
- For devices with multiple users, in some cases after updating the device to Beta 4, the device crashes and reboots when trying to switch to a secondary user.
Android Studio and tools
- When installing an app that has a targetSdkVersion of “S” from Android Studio, developers might see the following error:
“Installation did not succeed. The application could not be installed: INSTALL_FAILED_VERIFICATION_FAILURE
List of apks:
[0] ‘…/build/outputs/apk/debug/app-debug.apk’
Installation failed due to: ‘null’”
- The likely cause is that one or more of the app’s activities, services, or broadcast receivers includes intent-filters, but does not explicitly set a value for android:exported. Android 12 requires setting an explicit value for this attribute on all <activity>, <service>, and <receiver> components that also have an <intent-filter> defined. For more information, see Safer exporting of components. Note: This issue is already solved in the latest release of Android Studio Arctic Fox. To get the latest fixes and enhancements when targeting Android 12, we recommend installing a preview version of Android Studio alongside your stable version.
- The latest preview version of the Android SDK Build Tools (31.0.0) is not compatible with Android Studio versions prior to Android Studio Arctic Fox.
Android Auto
- After a user receives the OTA from Android 11 to Android 12 Beta and using Wireless Android Auto, some users may encounter a crash with Android Auto when trying to establish a Bluetooth connection. We are looking into this and a fix will be made available in the next Android 12 Beta release.
Android TV
- Hotplugging the HDMI cable might cause video playback to fail on some display sinks.
- Android Google Home App (GHA) version 2.42.1.11 or above is required to perform the 2nd screen set up. Performing setup using the iOS app or by using the remote is intact.
Android 12 Beta 3 Errors, Bugs, And Issues
The following applies to Android 12 Beta 3, although it’s always wise to run the latest build possible. This may differ with OEM preview programs.
