(OTA and Factory Image) Android 12 Beta 4 with build SPB4.210715.011 is now available for download

The mountain view giant has currently released the new beta 4 version with build SPB4.210715.011 for its next big Android 12 update. All the OTA packages and factory images are available for download from the Google download page.

The new Android 12 Beta 4 supports the Pixel 3 and later, and it comes with a new August 2021 security patch.

About Android 12 Beta 4

• Release date: August 11, 2021
• Build: SPB4.210715.011
• Emulator support: x86 (64-bit), ARM (v8-A)
• Security patch level: August 2021
• Google Play Services: 21.24.18

Android 12 Beta 4 OTA Download

• Pixel 5
• Pixel 4a 5G
• Pixel 4a
• Pixel 4 XL
• Pixel 4
• Pixel 3a XL
• Pixel 3a
• Pixel 3 XL
• Pixel 3

Android 12 Beta 4 Factory Image Download

• Pixel 5
• Pixel 4a 5G
• Pixel 4a
• Pixel 4 XL
• Pixel 4
• Pixel 3a XL
• Pixel 3a
• Pixel 3 XL
• Pixel 3

According to Google, Android 12 Beta 4 fixed many issues:

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 the Google Assistant.
• Fixed an issue on Android Auto where Automatic Day and Night switching did not work.

Top open issues

See top open issues for the latest list of top open issues that have been reported by developers and users.

Other known issues

Based on our testing, you might encounter the following issues when using Android 12 Beta 4. These issues are already known, so there’s no need to file additional reports for similar 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

• 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 set up using the iOS app or by using the remote are intact.