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?

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    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.

    • Die4EverOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      yes would be easy for them to do, I just don’t think I’ve seen Google do this before

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        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.

        • adlr@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          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”