12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon) | Flash | Link | 2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024 |
12.1.0 (SQ3A.220605.009.B1, Jun 2022) | Flash | Link | 157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2 |
June 6, 2022 1:00pm Comment Adam Conway
June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more
Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.
Pocket Operator
![]()
Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.
The app was not found in the store.
Go to store Google websearch
Vaccination Cards
![]()
Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.
More “At a Glance” alerts
Video Player
00:00
00:33
The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.
Nest Doorbell video feed
![]()
Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.
Flashlight reminder
Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.
Coming soon: Air Quality alerts
If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.
Conversation Mode exits beta
![]()
Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.
More features
Real Tone Filters
Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.
Car Crash Detection comes to Canada
Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.
More Chat translation languages
Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.
Download and install the June feature drop
The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.
Pixel Update Bulletin—May 2022
Published May 2, 2022
The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-05-05 or later address all issues in this bulletin and all issues in the May 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
All supported Google devices will receive an update to the 2022-05-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.
Announcements
- In addition to the security vulnerabilities described in the May 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.
Security patches
Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Pixel
CVE References Type Severity Component CVE-2022-20120 A-203213034* RCE Critical Bootloader CVE-2022-20117 A-217475903* ID Critical Titan-M CVE-2021-4083 A-216408350
Upstream kernelEoP High Kernel CVE-2022-20118 A-205707793* EoP High Kernel CVE-2022-20119 A-213170715* ID High Display/Graphics CVE-2022-20121 A-212573046* ID High USCCDMService Qualcomm components
CVE References Severity Component CVE-2021-35084 A-204909067
QC-CR#3001178Moderate WLAN CVE-2021-35085 A-204012850
QC-CR#3001331Moderate WLAN CVE-2021-35092 A-204909309
QC-CR#2985885 [2]Moderate Modem CVE-2021-35098 A-190503256
QC-CR#2966419Moderate Audio Qualcomm closed-source components
CVE References Severity Component CVE-2021-35079 A-204908838* Moderate Closed-source component Functional patches
For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.
Common questions and answers
This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
Security patch levels of 2022-05-05 or later address all issues associated with the 2022-05-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
2. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
3. What do the entries in the References column mean?
Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
4. What does an * next to the Android bug ID in the References column mean?
Prefix Reference A- Android bug ID QC- Qualcomm reference number M- MediaTek reference number N- NVIDIA reference number B- Broadcom reference number U- UNISOC reference number
Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.
Versions
Version Date Notes 1.0 May 2, 2022 Bulletin Published
Sigh.... Still no face unlock it seemsArgh. I had my post with May's update by accident, and there are two factory images this month, one specifically for Verizon again.
More than likely there were more changes to the Verizon radio.img (modem) than they had time to integrate into the universal factory image's radio.img. I'm sure it'll go back down to one image per month in the near future.My phone is from Google. My carrier is Verizon. Guess that I install the A1 version for the June update.
I wonder why last month there was one version for all carriers and this month there is a separate version for VZ.
i saw those rumor posts, and I didn't get excited, I thought no way. Maybe some day.
Let us know how that goes, i too am on factory unlocked on vzw networkso I'm gonna try the VZW variant first this time and see. I hope it helps
I'll be updating today, probably wait for a bit to see if any issues arise with what version of magisk to runLet us know how that goes, i too am on factory unlocked on vzw network
Yup that's why I'm waiting a couple of days (i was caught by the initial unrootable December update so i hold off even though i use magisk canary)I'll be updating today, probably wait for a bit to see if any issues arise with what version of magisk to run
Thank you for your report!
Howdy @Hecke92! You can find it by clicking on the blue "General" quick filter at the top of the list of threads in this section:
I have an unlocked phone from the Google store. My service is through Spectrum which uses Verizon's towers. I've always flashed the Universal/US firmware version except for once. The one time I flashed Verizon's it seemed like it made my signal a lot worse. I'm still confused about which one I should be flashing though.More than likely there were more changes to the Verizon radio.img (modem) than they had time to integrate into the universal factory image's radio.img. I'm sure it'll go back down to one image per month in the near future.
I have NEVER flashed the VZW version on any phone and dont have any plans to do so now. Been with VZW for nearly 30 years....my .02I have an unlocked phone from the Google store. My service is through Spectrum which uses Verizon's towers. I've always flashed the Universal/US firmware version except for once. The one time I flashed Verizon's it seemed like it made my signal a lot worse. I'm still confused about which one I should be flashing though.![]()
In the end, whatever works best for you is the correct one, so you're good no matter which. Neither one will "break" your phone, you can always switch to the other if you don't like one. In theory, the Verizon one is the one you would want, but only you can determine which one works best, just as you had previously.I have an unlocked phone from the Google store. My service is through Spectrum which uses Verizon's towers. I've always flashed the Universal/US firmware version except for once. The one time I flashed Verizon's it seemed like it made my signal a lot worse. I'm still confused about which one I should be flashing though.![]()
Magisk Changelog
v25.1
- [MagiskBoot] Fix ramdisk backup being incorrectly skipped
- [MagiskBoot] Add new feature to detect unsupported dtb and abort during installation
- [Zygisk] Change binary hijack paths
- [App] Fix incorrect recovery mode detection and installation
- [MagiskInit] Fix config not properly exported in legacy SAR devices
- [General] Enforce the Magisk app to always match or be newer than magiskd
v25.0
- [MagiskInit] Update 2SI implementation, significantly increase device compatibility (e.g. Sony Xperia devices)
- [MagiskInit] Introduce new sepolicy injection mechanism
- [MagiskInit] Support Oculus Go
- [MagiskInit] Support Android 13 GKIs (Pixel 6)
- [MagiskBoot] Fix vbmeta extraction implementation
- [App] Fix stub app on older Android versions
- [App] [MagiskSU] Properly support apps using sharedUserId
- [MagiskSU] Fix a possible crash in magiskd
- [MagiskSU] Prune unused UIDs as soon as system_server restarts to prevent UID reuse attacks
- [MagiskSU] Verify and enforce the installed Magisk app’s certificate to match the distributor’s signature
- [MagiskSU] [Zygisk] Proper package management and detection
- [Zygisk] Fix function hooking on devices running Android 12 with old kernels
- [Zygisk] Fix Zygisk’s self code unloading implementation
- [DenyList] Fix DenyList on shared UID apps
- [BusyBox] Add workaround for devices running old kernels
2022.6.19 Magisk v25.1
Another major release! A lot of the changes aren’t visible at the surface, but v25 is actually a really substantial upgrade!v25.1 fixes some minor bugs over v25.0. The following are the same as v25.0 release notes.
MagiskInit Rewrite
A significant portion of magiskinit (the critical software that runs before your device boots up) is completely rewritten from scratch. Ever since Android introduced Project Treble in Android 8.0, Magisk has been constantly fighting against the increasingly complex partitioning and early mount setups of all kinds of devices, sometimes with weird OEM specific implementations. It got to a point that magiskinit had become so complicated that few people (including myself!) were aware of every detail, and maintaining this piece of software like this was clearly not sustainable. After many months of planning (yes, this whole re-architecture has been in my head for a long time) and some help from external contributors, a whole new sepolicy injection mechanism is introduced into Magisk, solving the “SELinux Problem” once and for all.
Since this is a full paradigm shift on how Magisk hot-patch the device at boot, several behaviors that many developers implicitly relied on might not exist. For example, Magisk no longer patches fstabs in most scenarios, which means AVB will remain intact; some custom kernels rely on AVB being stripped out for them by Magisk.
MagiskSU Security Enhancements
The superuser functionality of Magisk has not seen much changes ever since its introduction. v25 focuses on making root permission management more accurate and secure:
Many might not realize, but using a trusted, unmodified Magisk app is really important. Magisk’s root daemon treats the Magisk app differently and gives it blanket root access without any restrictions. A modded Magisk app can potentially backdoor your device.
- Add a whole new package tracking system to ensure malicious UID reuse attack cannot be performed
- Properly support and implement the UX in the Magisk app for packages using sharedUserId
- Enforce root manager APK signature verification to combat the rampant unofficial Magisk app “mods”
And in case some of you are about to put on your tin foil hats, this is not designed to “vendor lock-in”; the goal is to make sure your root management app comes from the same developer of the underlying root implementation. Magisk’s build system allows custom distributors to use its own signing keys, and in addition, I am also providing official debug builds which skips any signature verification for development.
Revisions
33.0.2 (May 2022)
- fastboot
- Support for the vendor_kernel_boot partition.
12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon) | Flash | Link | 2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024 |
12.1.0 (SQ3A.220605.009.B1, Jun 2022) | Flash | Link | 157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2 |
June 6, 2022 1:00pm Comment Adam Conway
June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more
Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.
Pocket Operator
![]()
Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.
The app was not found in the store.
Go to store Google websearch
Vaccination Cards
![]()
Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.
More “At a Glance” alerts
Video Player
00:00
00:33
The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.
Nest Doorbell video feed
![]()
Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.
Flashlight reminder
Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.
Coming soon: Air Quality alerts
If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.
Conversation Mode exits beta
![]()
Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.
More features
Real Tone Filters
Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.
Car Crash Detection comes to Canada
Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.
More Chat translation languages
Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.
Download and install the June feature drop
The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.
Pixel Update Bulletin—May 2022
Published May 2, 2022
The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-05-05 or later address all issues in this bulletin and all issues in the May 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
All supported Google devices will receive an update to the 2022-05-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.
Announcements
- In addition to the security vulnerabilities described in the May 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.
Security patches
Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Pixel
CVE References Type Severity Component CVE-2022-20120 A-203213034* RCE Critical Bootloader CVE-2022-20117 A-217475903* ID Critical Titan-M CVE-2021-4083 A-216408350
Upstream kernelEoP High Kernel CVE-2022-20118 A-205707793* EoP High Kernel CVE-2022-20119 A-213170715* ID High Display/Graphics CVE-2022-20121 A-212573046* ID High USCCDMService Qualcomm components
CVE References Severity Component CVE-2021-35084 A-204909067
QC-CR#3001178Moderate WLAN CVE-2021-35085 A-204012850
QC-CR#3001331Moderate WLAN CVE-2021-35092 A-204909309
QC-CR#2985885 [2]Moderate Modem CVE-2021-35098 A-190503256
QC-CR#2966419Moderate Audio Qualcomm closed-source components
CVE References Severity Component CVE-2021-35079 A-204908838* Moderate Closed-source component Functional patches
For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.
Common questions and answers
This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
Security patch levels of 2022-05-05 or later address all issues associated with the 2022-05-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
2. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
3. What do the entries in the References column mean?
Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
4. What does an * next to the Android bug ID in the References column mean?
Prefix Reference A- Android bug ID QC- Qualcomm reference number M- MediaTek reference number N- NVIDIA reference number B- Broadcom reference number U- UNISOC reference number
Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.
Versions
Version Date Notes 1.0 May 2, 2022 Bulletin Published
Depends on your reason to disable verity and verification. Magisk no longer strips avb from fstab so custom kernels had a problems booting on Canary 24303+, including Beta 25, but that has been fixed and incorporated into the kernels/AK3 themselves now so you can use Beta 25 with custom kernels, even though Magisk continues to strip avb from fstab.are people sticking with 24.2 Magisk instead of updating while still on stock A12 firmware?
or is Magisk 25 fine and does not need you to disable verity and vbmeta?
12.1.0 (SQ3A.220605.009.A1, Jun 2022, Verizon) | Flash | Link | 2b4b1d476a6e80fd9fe09ace45e8abbd654a4d4a6fc51d39f0fd76f5a2c6a024 |
12.1.0 (SQ3A.220605.009.B1, Jun 2022) | Flash | Link | 157e22840d4d4fde9f90d7de3d6ba6930922e9376096040d68501d155c997cb2 |
June 6, 2022 1:00pm Comment Adam Conway
June Feature Drop for Google Pixels includes At a Glance improvements, Pocket Operator, and more
Every three months, Google rolls out new features to Pixel phones outside of the usual Android OS updates for years, and the company refers to them as “Feature Drops.” They’re usually released alongside a security patch, and the most recent one brought improvements to live caption, night mode in Snapchat, and a whole lot more. Now the June Feature Drop is now available (alongside June security patches), and it packs a ton of cool stuff you can try out on any Pixel smartphone release between the Pixel 4 and the latest Pixel 6 series.
In case you’re wondering, the June feature drop is based on the QPR3 builds that Google has been testing over the last few months. It’s currently unknown if Google will continue to beta test quarterly platform releases in the future.
Pocket Operator
![]()
Made in collaboration with teenage engineering, Pocket Operator is a new app that will let you shoot videos and “turn them into fun music and video cut-ups.” You can layer sounds, add visual effects, create patterns and beats, and mix it all together to make your own unique tracks. It’s available on the Google Play Store now, and you can check it out down below. It works on the Pixel 5 and newer, and currently, it’s only available in English.
The app was not found in the store.
Go to store Google websearch
Vaccination Cards
![]()
Google has had the ability to add a vaccine card to your Google Pay for quite a while now, but now the company says you can add a shortcut to it to your home screen to quickly and easily get access to it at any time. It’s available in Australia, Canada, and the U.S.
More “At a Glance” alerts
Video Player
00:00
00:33
The Pixel 6 series debuted a revamped “At a Glance” widget, which can display your calendar events, flight boarding pass, workout stats, and more on your home screen and lockscreen. Since its release, Google has added several new features to the widget to further expand its capabilities. Now the company is adding three new features to it.
Nest Doorbell video feed
![]()
Google added Nest Doorbell alerts back in January to the At a Glance widget, and they can tell you if “Someone’s at your door”. This can help you find out if a package has arrived, or if someone is just trying to get your attention out the front of your house. Now you can see an actual video feed from your doorbell too, right on your home screen.
Flashlight reminder
Ever left your flashlight turned on on your phone? It’s pretty embarrassing, but I’m pretty sure that we’ve all been there. Now you’ll be able to see if it’s on straight from your home screen, without needing to turn your phone around to catch it.
Coming soon: Air Quality alerts
If you live in the U.S., Australia, or India, soon you’ll get Air Quality alerts in your At a Glance widget for your current location.
Conversation Mode exits beta
![]()
Google previously added “Conversation Mode” to the Sound Amplifier app in the December feature drop, and it’s been in beta since then. It uses on-device machine learning to block out surrounding noise. Conversation Mode is exclusively available to Pixel phone owners, and now it’s exiting beta. It’s designed for people with hearing loss to filter out sounds around them. It amplifies their voice, and you uses the camera to focus on whatever their phone should be properly listening to.
More features
Real Tone Filters
Google introduced Real Tone with the Pixel 6 series last year to help users accurately capture various skin tones. The Real Tone functionality used an updated face detection algorithm capable of recognizing more diverse faces in a wider array of lighting conditions, resulting in a better representation of different skin tones.
At I/O this year, Google expanded on the functionality and announced that it would implement Harvard professor Dr. Ellis Monk’s scale in Search and Photos to achieve similar results across all its products. These filters are now rolling out to users of Google Photos.
Car Crash Detection comes to Canada
Google’s Car Crash Detection is rolling out in Canada now to Google Pixel 3 users and above, though excluding the Pixel 3a. It can, as the name suggests, detect if you’re in a car crash and act accordingly. It’s a safety feature that could potentially save lives.
More Chat translation languages
Chat translation in messages will now be available in Traditional Chinese, Dutch, Korean, Thai, and Turkish for Pixel 6 and Pixel 6 Pro.
Download and install the June feature drop
The June feature drop is now available for all eligible Pixel smartphones, and you can download it by checking for an update in your device’s settings.
Pixel Update Bulletin—May 2022
Published May 2, 2022
The Pixel Update Bulletin contains details of security vulnerabilities and functional improvements affecting supported Pixel devices (Google devices). For Google devices, security patch levels of 2022-05-05 or later address all issues in this bulletin and all issues in the May 2022 Android Security Bulletin. To learn how to check a device's security patch level, see Check and update your Android version.
All supported Google devices will receive an update to the 2022-05-05 patch level. We encourage all customers to accept these updates to their devices.
Note: The Google device firmware images are available on the Google Developer site.
Announcements
- In addition to the security vulnerabilities described in the May 2022 Android Security Bulletin, Google devices also contain patches for the security vulnerabilities described below.
Security patches
Vulnerabilities are grouped under the component that they affect. There is a description of the issue and a table with the CVE, associated references, type of vulnerability, severity, and updated Android Open Source Project (AOSP) versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Pixel
CVE References Type Severity Component CVE-2022-20120 A-203213034* RCE Critical Bootloader CVE-2022-20117 A-217475903* ID Critical Titan-M CVE-2021-4083 A-216408350
Upstream kernelEoP High Kernel CVE-2022-20118 A-205707793* EoP High Kernel CVE-2022-20119 A-213170715* ID High Display/Graphics CVE-2022-20121 A-212573046* ID High USCCDMService Qualcomm components
CVE References Severity Component CVE-2021-35084 A-204909067
QC-CR#3001178Moderate WLAN CVE-2021-35085 A-204012850
QC-CR#3001331Moderate WLAN CVE-2021-35092 A-204909309
QC-CR#2985885 [2]Moderate Modem CVE-2021-35098 A-190503256
QC-CR#2966419Moderate Audio Qualcomm closed-source components
CVE References Severity Component CVE-2021-35079 A-204908838* Moderate Closed-source component Functional patches
For details on the new bug fixes and functional patches included in this release, refer to the Pixel Community forum.
Common questions and answers
This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
Security patch levels of 2022-05-05 or later address all issues associated with the 2022-05-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Google device update schedule.
2. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
3. What do the entries in the References column mean?
Abbreviation Definition RCE Remote code execution EoP Elevation of privilege ID Information disclosure DoS Denial of service N/A Classification not available
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
4. What does an * next to the Android bug ID in the References column mean?
Prefix Reference A- Android bug ID QC- Qualcomm reference number M- MediaTek reference number N- NVIDIA reference number B- Broadcom reference number U- UNISOC reference number
Issues that are not publicly available have an * next to the Android bug ID in the References column. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
5. Why are security vulnerabilities split between this bulletin and the Android Security Bulletins?
Security vulnerabilities that are documented in the Android Security Bulletins are required to declare the latest security patch level on Android devices. Additional security vulnerabilities, such as those documented in this bulletin are not required for declaring a security patch level.
Versions
Version Date Notes 1.0 May 2, 2022 Bulletin Published
Note that this is mainly for the officially listed "Unlocked" Pixel 6 Pro, available directly from the Google Store. All of this will also apply to any other (carrier-specific) variant of the Pixel 6 Pro which you can achieve an unlocked bootloader on. This includes T-Mobile and AT&T variants. It's likely Verizon variants will never be able to unlock their bootloader, or if so it will require paying the right person to do so.
Feel free to ask about general questions, but for anything that's specific to your variant, you should use one of the other already existing threads. You'll find Verizon, AT&T, and T-Mobile-related threads in those respective search results.
Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device.
Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, your local bank's app, or even the ability to install some apps like NetFlix. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it.
There are no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. You will also continue to receive updates (if you've merely unlocked the bootloader, you can take updates as normal) unlike Samsung, Sony, et cetera, which have permanent major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to manually update each month, and to keep root/re-root.
All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. There are at least one or two other How To Guide threads in this section in which folks discuss how to get around banking app restrictions when you're rooted or just have an unlocked bootloader. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
If users persist in discussing banking apps in this thread, I will have this thread locked and only update this first post when there is new and updated information regarding the subjects of the title of the thread: Unlocking the Pixel 6 Pro bootloader, rooting, and TWRP. See @Pekempy's thread Working SafetyNet with Pixel 6 Pro Android 12
Honorable mention to @Jawomo's aodNotify - Notification Light / LED for Pixel 6 Pro! (XDA link) / Notification light / LED for Pixel - aodNotify (Play Store link), which in my opinion restores useful functionality missing in most phones these days. It also solves some subjective issues some folks have with AOD (Always On Display), and/or solves/works around the problem where AOD is required for the optical fingerprint reader to work without the screen being on.
OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.
- You'll need this if you're going to unlock the bootloader on your Pixel 6 Pro: SDK Platform Tools (download links for Windows, Mac, and Linux). Note that you can find links to download the tools elsewhere, but I wouldn't trust them - you never know if they've been modified. Even if the person providing the link didn't do anything intentionally, the tools could be modified without them being aware. Why take a chance of putting your phone security further at risk?
- You can alternately use the tools from the SDK Manager, but most of us will want to stick to the basic tools-only without the complications of the full development manager.
- For Windows, get Google's drivers here Get the Google USB Driver (ADB will likely work while the phone is fully booted, but if you're like me, you'll need these drivers for after you "adb reboot-bootloader", to be able to use ADB and Fastboot.
- Thanks to @96carboard for posting the details of unlocking the bootloader, be sure to thank him in his post. Unlocking or locking the bootloader will wipe the device every single time, so be sure to have your data backed up before doing so, or better yet, just unlock it as soon as you get the device. Keep in mind that unlocking the bootloader or rooting might affect your phone's capability to use banking apps such as Google Pay, or your local bank's app. If you're going to re-lock the bootloader, make sure the ROM you have on your phone is completely stock (by flashing the latest official firmware) BEFORE re-locking it. My experience on my Pixel 1 was that there were no negative consequences if you unlock or re-lock the bootloader other than it will wipe your phone, and while unlocked you get a brief screen when you boot the phone telling you (and anyone who sees your phone at the time) that the bootloader is unlocked. All of this should still be the case. You will also continue to receive updates. Unlike Samsung, Sony, et cetera, which have major consequences with reduced functionality even if you un-root and re-lock your bootloader. If you're actually rooted (not just bootloader unlocked), you'll have to perform extra steps to keep root/re-root.:
The unlock process works like this:
1) Take brand new fresh phone out of box. Do NOT put sim card in it, just power it on (you can put a SIM card if you want, you just don't have to).
2) When it starts harassing you to join Google, hit "skip" and "remind me tomorrow" as applicable until you reach home screen. YOU DO NOT need to plug in a google account.
3) Settings --> About --> Build number. Repeatedly tap it until it says you're a developer.
4) Back --> Network --> WiFi and connect it.
5) Back --> System --> Developer --> OEM unlocking (check), USB debugging (check), plug in USB, authorize on the phone when requested.
Using the Platform Tools previously mentioned in command line/terminal:
6) #7) #Code:adb reboot-bootloader
Code:fastboot flashing unlock
Now that you've unlocked it, it has been wiped, so repeat 1-4, then disable all the google spyware, and go ahead and start using it while waiting for aosp and root.
Official Instructions for Locking/Unlocking the Bootloader
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).
@V0latyle posted a new thread with some very important and fascinating information about the increased difficulty to root Android 12: Read this before rooting. Be sure to thank him there.
I would guess that this should be the appropriate URL for official TWRP custom recovery for the Pixel 6 Pro, but who knows when/if that will actually be made available, and it may become available unofficially in these forum sections before being made official. I'll adjust this URL as needed. https://twrp.me/google/googlepixel6pro.html.
@Freak07's Kirisakura-Kernel for the Pixel 6 Pro (and possibly the Pixel 6)
@DespairFactor's Despair Kernel (I believe also for both the P6P and P6)
@tbalden's CleanSlate Kernel
@acuicultor's Radioactive Kernel
It's also handy to have to the full official firmware available, whether it's to recovery from accidents or for actual development. Note the official link to the general Factory Images for Nexus and Pixel Devices page. The following link goes directly to the Pixel 6 Pro (Raven) section: Pixel 6 Pro Factory Images. I prefer to actually bookmark a link to the device listed immediately below the device I want the firmware for, because Google dumbly (in my opinion) puts the latest firmware at the bottom of the list for each particular device, and that ends up making you scroll a lot after a year or two of monthly updates.
Note: You can still get the December 2021 Factory Images and OTA from this thread, if you need them for any reason: Alternate links to December - all full factory images and OTAs available
Back to modding!
- Use the latest Magisk Stable (in my case, I keep the app "hidden" / renamed)
- Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)
- Extracted the new boot.img
- Copied new boot.img to the phone
- Patched the new boot.img with Magisk Stable
- Renamed Magisk'd boot.img so I know what version of firmware it's for
- Copied the Magisk'd boot.img back to the computer
- Disabled all my Magisk Modules
- Removed the "-w " from the flash-all.bat
- Re-edited the flash-all.bat to verify I saved it with the "-w " taken out
- Open a Command Prompt, navigated to S:\platform-tools
- adb reboot bootloader
- flash-all.bat
- Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)
- adb reboot bootloader
- fastboot flash boot kernel.img (renamed Magisk'd boot.img)
- fastboot reboot
- Unlock, check everything's working
- Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue
- Reboot, unlock, made sure everything's working
I may append these first four posts with further useful information or links as needed.
33.0.1 (March 2022)
- adb
- Fixes Windows mdns crashes.
- Fixes enable-verity/disable-verity on old devices.
- Fixes "install multiple" on old devices
- Improves the help output to include all supported compression methods.
Revisions
32.0.0 (January 2022)
- adb
- Fixed adb w/o args SEGV regression.
- fastboot
- Reinstated recovery execution from b/158156979 (removal of preprocessor guards for root/secure).