Recent pixel errors include strange software bugs known to Google

Recent pixel errors include strange software bugs known to Google

Tech Highlights:

  • Those with the Pixel 3a to Pixel 5a had received a notification alerting them that they had received an update that will install Android 12 on their phones. The update weighs in at a zaftig-like 1.5GB. The buzz around the water cooler this morning is that the Android 12 update was sent a second time to the Pixel 3, Pixel 3a, Pixel 4, Pixel 4a, Pixel 5, and Pixel 5a lineups. Some older Pixel models receive a prompt to install the Android 12 update for a second time – Latest Pixel problems introduce bizarre software issues that Google knows about.

  • In a weird twist of déjà vu, certain Pixel devices that previously received the Android 12 upgrade last month are being prompted to reinstall Android 12 with the November security update. The update appears to have had no effect, and later that afternoon, Google wrote that “We apologise for the message you received. Not to worry, we’ve fixed the problem and you may dismiss it.” Even if they use a different carrier, some Pixel owners received a second Android 12 update intended for Verizon devices.

Some older Pixel models receive a prompt to install the Android 12 update for a second time. Interestingly, the Pixel 6 and Pixel 6 Pro were not included among the models that received a second prompt to update to Android 12. The new Pixel models came with Android 12 out of the box which might explain why it didn’t receive a second update; after all, it never actually received a first one. It is not known whether an Android Beta Program enrollment (in the past or present) improved the odds of a Pixel user receiving the second update.

One Reddit user whose Pixel 4 XL runs on AT&T and has been updated to Android 12 described the craziness that descended into Pixel-land and said that when he received the second Android 12 update, he “assumed this was some glitch with former and current Beta users since I was one, but it seems non-Beta users have gotten this as well.”

Now that Google has said that you can disregard the second update, by all means, go ahead and do so. After all, wasting storage on an update that you already have installed on your phone. Interestingly, it appears that the second update pushed out by mistake contained Verizon specific-files that were disseminated globally. It would seem that Google was trying to fix the issue that has seen Verizon owners of the Pixel 6 and Pixel 6 Pro fail to receive the update they were due. Instead, Google sent out the Verizon update to non-Verizon phones. Funny how that works.
More craziness for Pixel users as usual

He added that “I’ve also heard reports that this is a Verizon build of the software, so I’m not touching it until Google comes out with an official statement about it or the notification just disappears on its own. EDIT: The notification seemed to disappear on it’s own not too long ago, so I guess Google took notice? Who knows.”

And yet another Pixel user stated that “I’m staying on Android 11 forever. Not making the jump to Android 12, made it in my Pixel 4 and I’m really not into it. My Pixel 5 will stay on 11 for as long as I can hold it.”

Once again, we have to tell you that this is so typical for the launch of a new Pixel model. Verizon locked Pixel 6 models don’t receive a scheduled update which ends up being sent to older Pixel handsets not locked to Verizon. Flickering light appears on the display, and there are three different issues with the under-display fingerprint scanner.

We will be happy to hear your thoughts

      Leave a reply

      Tech Reviews, News and Guides