I had downloaded it but never rebooted to update because I heard about some issues and decided to wait. Now it’s saying I’m up to date with Android 13?
You must log in or register to comment.
Yes the update most likely was withdrawn for people who had not yet installed it due to a significant issue affecting Pixel 6. You’re missing absolutely nothing of value on Android 13 in the meantime
Wow no responses. Pixel 7 pro here.
Still on Android 14. Not recalled yet for me fyi
I wouldn’t expect them to recall it from users who already installed (I think Android downgrades are tricky), but I only downloaded the update and never installed it (never rebooted for it)
Ditto [UK EE]
Haven’t been allowed to download the November patches yet.
Same issue occured with me. Downloaded 14 but never got around to install. Just checked and I’m “up to date” on Android 13. Pixel 6 Pro.
It’s not impossible. The update isn’t set in stone until you reboot into the Android UI. Prior to reboot it can be discarded trivially. Post reboot but prior to starting up the Android UI, it can be rolled back.
yes would be easy for them to do, I just don’t think I’ve seen Google do this before
It would be interesting to see if it’s an actual cloud-controlled recall feature or whether it’s something simpler like timed expiry of an installed but not activated update. Haven’t dug into update_engine for that. Could also be in the upper updater layer, outside of update_engine.
At least on Chrome OS, update engine does have a recall feature. The server can say, “if you’ve downloaded and installed an update and you’re waiting to boot into it, cancel it and stick with what you have”
One issue I’ve had since updating is that people can’t hear me on outgoing calls sometimes unless I reboot.
Strange thing is that the proximity sensor would also not disable the display during a call as it was set to.
I primarily flash from factory images because I’m rooted and it’s a pain. They still have the Android 14 images up from October to November.
