Android 13 QPR3 Beta 3.2

Android 13 QPR3 Beta 3.2 released with new bug fixes

Amid Android 14 developments, Google released the Android 13 QPR3 Beta 3.2 for Pixel devices. The latest rollout carries a variety of bug fixes that aims to improve the internal aspects of smartphones. Besides, it checks on the network segments to offer efficient connectivity.

To be mentioned, the new beta build arrived two weeks after the last release. Meanwhile, it increases the capability of the device to fight against potential threats found in the recent build.

Speaking of the details, the new Android 13 beta is rolling out with the T3B3.230413.009 version along with the May 2023 security patch. Whereas, Pixel 6, 6 Pro, and 6a at Verizon are getting the update with the T3B3.230413.009.A1 build number, accompanying the April 2023 security patch.

In case you are having a Pixel handset ranging between Pixel 7 series to Pixel 4a in your pocket which is already running a QPR3 beta, then you will automatically attain the latest rollout via the OTA medium.

Follow our socials → Google News, Telegram

Moving to the changelog, the update mainly addresses problems related to the network segment. It mends issues with WiFi and LTE coverage, and further resolves SIM card setup in the device. You can check more details in the changelog given below.

Android 13 QPR3 Beta 3.2: Fixes

  • Fixed an input synchronization issue with the system UI that caused Windows to stop receiving touch input or to receive touch input in the wrong location. (Issue #279560321)
  • Fixed an issue that could cause calls over Wi-Fi to disconnect unexpectedly.
  • Fixed an issue that could prevent a SIM card from being detected properly or from being activated during phone setup.
  • Fixed an issue where a device could fail to register IMS over Wi-Fi when leaving LTE coverage and entering Wi-Fi coverage.
  • Fixed issues that caused unexpected dips in cellular connectivity speeds or reliability.

Android 13 QPR3 Beta 3.2


Android 13 QPR3 Beta 3.2 released with new bug fixes

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

To Top