Google used the March security update to roll out security vulnerability fixes and a handful of functional updates to the Pixel 3 and Pixel 3 XL. Now, the search giant is pushing out the April Android security patch that focuses on squashing bugs in the operating system and on Google’s hardware.
According to the security bulletin, Google has addressed 11 issues. The Android security patch fixes vulnerabilities in the system, Qualcomm components, framework, and media framework.
As per usual, Google states that none of these vulnerabilities were used to harm any end-users.
Pixel-specific updates
The April Android security patch also patches a number of issues on the Pixel 3 and Pixel 3 XL. You can find the functional updates below:
- Improves Voice-Unlocking performance for Google Assistant
- Adjust Wi-Fi connectivity during eSIM activation on certain carriers
- Improves Bluetooth connectivity on Pixel devices
- Removes screen flash when ambient display wakes for some Pixel 3 devices
Some of those updates will likely be very welcome to Pixel owners who are dealing with these various issues. Let us know in the comments if this update brings any big difference for usability.
If you don’t want to wait for the February security patch to make its way to your phone or tablet, you can download the latest factory image or OTA file from the links below. From there, you can either flash a fresh build to your phone or sideload the OTA update.
- Pixel 3 XL: Factory Image, OTA
- Pixel 3: Factory Image, OTA
- Pixel 2 XL: Factory Image, OTA
- Pixel 2: Factory Image, OTA
- Pixel XL: Factory Image, OTA
- Pixel: Factory Image, OTA
Just like with the Nexus 6P and Nexus 5X, it looks like Google dropped support for the Pixel C. This shouldn’t come as too much of a surprise as the tablet received updated for four months after its promised period of support. You will have to check for third-party ROMs and other resources online if you want ongoing firmware and security upgrades for any of the devices.
from Android Authority https://ift.tt/2HPcvgh
via IFTTT
0 comments:
Post a Comment