More Reading

Post navigation

45 Comments

  • So, should I assume the P6’s will get their updates the end if the month again?

    • I’d put a pretty high wager on Verizon delivering on the last Monday of May. Another huge FAIL.

    • Same here…unlocked P6P from Google using Verizon. We are “Screwed” once again.

  • Still no May update for my Google Store purchased unlocked P6P on Verizon sim. 5/3/23.

  • Still haven’t gotten the April update on my 6 Pro. Xfinity mobile. Wonder when I’ll get May?

  • Hopefully this will finally fix the lock screen issues that my Pixel 7 Pro has had since day 1.

  • Anyone else have a bug where it takes Bluetooth headphones a minute or two before it’ll play without slipping?

  • 26.44MB on my Pixel 7 Pro (unlocked by running on Fi). First scan didn’t show an update but then I tried again 30 min later and now it’s downloading at 3:30PM EST.

  • Highly doubt the Verizon pixel six series will go though considering Google or Verizon shoved the updates till the end of the month. Heck, the pixel 6 only got April last Friday.

    • It’s most decidedly Verizon. They are ALWAYS the ones who hold up updates. They did improve….day isn’t over…it could still release for them. However the last couple months they completely muffed it.

      • It was only the 6 series that was delayed tho, so it was something specific to to Pixel 6 series and the Verizon network. Even pixel 6 with Verizon MNVO sims were not getting the update such as Visible and TracFone. So I don’t think Verizon was holding out for no reason.

      • I’ve had Verizon since 2001 and my first Pixel was the 2xl. Once they fixed the check for update button in 2017, Verizon has never held back an update other than if Google delayed it for everyone. Something has changed.

  • They still haven’t fixed the bug causing all Smart Lock options to completely disappear at random? There are 2 workarounds I am aware of. Turn off the Trusted Agent for Smart Lock (Google) and turn it back on. Or reboot the phone. It’s really annoying, because it causes Smart Lock to just not work at all.

    • I thought this was only a bug on the 14 beta. Are you telling me it happens on 13 with you as well?

      • Yes I’ve had this issue ever since the March update hit my Pixel 7 Pro. I’ve never been on Beta, and have always stayed on the main stable releases.

        • I never had it until I went to Android 14 but have always been on beta

      • FWIW, I’ve never had that issue and never heard of it until just now haha

    • I caught this after the last update on my Pixel 5 too. It was incredibly annoying and just made me think more about going Samsung next phone, esp. if the Pixel 8 isn’t smaller and about the same size as the 5. It’s amazing how many of these bugs make it into nearly every update. I’m sure it happens to Samsung’s and every other OEM too, but I’ve consistently had something break on my phone at least every few months on my Pixels and I can’t imagine Samsung is that bad now.

      • I’m tempted to switch to Samsung for that 6.1″ flagship (or near flagship) level life. I have really grown tired of how insanely big the Pixel Pro phones are.

  • I just got my April update on my Google Store bought p6p on vzw last night.

  • FYI– For anyone on the Verizon build from a few days ago, do not try and sideload. The May 1 build is dated older and will give you an error. It also mentioned that trying and rebooting can cause the phone to not start. Luckily mine restarted fine, just wanted to warm other users.

      • Tried flashing the new OTA and after it served the file to my phone, it game me the error.

    • Can anyone else confirm this? I’m so mad. It’s like Verizon purposefully did that to prevent side loading.

      • Confirmed…tried to sideload last night 5/2 and received the same error.

  • Yay! Google finally got back on track with a timely monthly update instead of postponing them like they have the last 4 months or so

Comments are closed.

back to top