In a recent development, Google has released new Android 14 QPR2 builds equipped with the April 2024 security patch for an array of its devices including Pixel 7, 7 Pro, 7a, Fold, 8, and 8 Pro. Interestingly, there isn’t an on-device OTA (Over-The-Air) update available at this time for these models. This announcement comes after a delay of two weeks from the usual update schedule. Traditionally, mid-cycle or mid-month releases like these Android 14 QPR2 updates are not listed on Google’s official Factory/OTA Images site. This would typically suggest that these are global builds rather than ones targeted at users in specific countries who haven’t received the April update yet.
The update saga took an intriguing turn on April 18 when reports surfaced that Pixel phones on Verizon were beginning to receive a new on-device OTA update. This update is notably small, coming in at under 7 MB. However, Verizon has not yet released changelogs related to this update. At the same time, there have been no signs of a similar OTA update for Pixel phones on other carriers, such as Google Fi, leaving the specifics of the update a bit of a mystery for now.
The build numbers for the affected devices have seen slight alterations, with the “B1” suffix being appended to the numbers for Pixel 7/Pro, Pixel 7a, and Pixel 8/Pro models. Meanwhile, the Pixel Fold’s build has shifted from “A1” to “A2”, indicating that these changes represent minor updates to the system.
Despite these updates, as of Wednesday afternoon, Pixel owners who have already installed the April security patch report that they are not seeing new on-device OTA updates. Efforts to reach out to Google for additional clarity on the situation have been made.
Looking forward, Google is not expected to release Android 14 QPR3 until June, suggesting that the next update is likely to be another minor one. In the meantime, the Android community has its eyes set on the larger horizon, with Android 15 Beta 1 already out. However, early feedback hints that the absence of NFC (Near Field Communication) functionality for tap-to-pay processes could be a significant hindrance for those looking to use the beta as their daily driver.
As this situation develops, it will be interesting to see how Google manages the rollout of its updates across different devices and carriers, and whether any additional features or crucial fixes will be included in upcoming patches or versions. Google and Verizon have yet to provide substantial comments on the matter, leaving users and enthusiasts eagerly awaiting more information.
Source
