Android 12 QPR3 Beta 3 includes a status bar icon for vibrate mode
We are still discovering some of the features of Android 12 QPR3 beta 3, which started rolling out to Pixels late last week. Thanks to an eagle-eyed user on Reddit, we now find out about the inclusion of a vibrate mode icon at the top of the status bar. This is a relatively minor feature, but nonetheless important, given that it disappeared from Android a few years ago.
Reddit user u/schrombear_23 spotted the new addition on Android 12 QPR3 Beta 3. “But strangely the icon is not showing on the lock screen (hopefully just a bug),” the user added (via Phone Arena). This reveal indicates that the upcoming June quarterly pixel feature drop will contain the new status bar icon. Google will begin rolling out the Feature Drop on June 6.
In addition to the status bar icon, the update also includes a “Always show icon in vibrate mode” switch under Sound and vibration. One of the easiest ways to enable/disable vibrate mode on Pixel devices is to press one of the two volume buttons and tap the vibrate icon in the pop-up window. This slider also allows users to control call and media volume levels.
Android 12 QPR3 Beta 3 also brings small changes to the Battery widget
Android 12 QPR3 Beta 3 would also bring some visual changes to the battery widget. While the widget lives under the Parameter services category, it now exists in a category simply called Batterythus facilitating its discovery.
The new status bar icon for vibrate mode finally means that users won’t have to press the volume buttons to find out if their phone is on vibrate mode. On the other hand, people who like their status bar uncluttered would find this new inclusion somewhat boring. Luckily, its visibility can be toggled via the Sound and vibration page under Settings.
The new update is available live for users participating in the Android 12 QPR3 beta program. All Pixel devices from the Pixel 4 and beyond are compatible with Android 12 QPR3 Beta 3. Google is also rolling out Android 13 betas to eligible devices. Considering the unstable nature of these builds, we recommend not trying it on your primary smartphone.