Skip Navigation
14 comments
  • 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.

  • Funny to see that GrapheneOS on Pixels is more up-to-date than Android on Pixels

  • 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.

  • 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.

14 comments