Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on programming.dev

13 replies

lemmy.world

Wow no responses. Pixel 7 pro here.

Still on Android 14. Not recalled yet for me fyi

6

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)

8
lemmy.ca

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.

2
Die4Everreply
programming.dev

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

1
lemmy.ca

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.

2

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"

4
lemmynsfw.com

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

2

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.

2

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.

1

You reached the end