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?

  • netwren@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Wow no responses. Pixel 7 pro here.

    Still on Android 14. Not recalled yet for me fyi

    • Die4Ever@programming.devOP
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      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)

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

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

  • shitwolves@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I’ve downloaded the update but I have not yet rebooted. Does anyone know how to delete the update package? I’m afraid I’ll end up having to reboot at some point because of a crash or running out of battery. Pixel 5a

  • bloubz@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

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

  • oleorun@real.lemmy.fan
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    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.

  • fishos@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    1 year ago

    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.