From Newsgroup: comp.mobile.android

On 15/07/2024 14:21, Andrew wrote:

Jeff Layman wrote on Mon, 15 Jul 2024 09:10:05 +0100 :

I've been using a Google Pixel 6a for a while now. When I got it, it had >>> Android 13 and at some point I could install the update to Android 14.
But I never experienced any unattended updates without my consent. All
system updates and also app updates in Google Play have to be confirmed
before they get installed.

As I posted above, I'm going to check the versions at
<https://support.google.com/product-documentation/answer/14343500> but
/not/ manually update anything over the next couple of weeks, and then
see if my phone has the very latest versions or not. If it has, it means
the updates have taken place automatically. I assume from your comment
above that this doesn't happen with your Pixel 6a.

I think what Arno & Jeff said is good information because my point about Project Mainline updates is they're so seamless, people don't know they're happening monthly (on Pixels) or slightly less often on other OEM brands.
<https://www.esper.io/blog/what-is-project-mainline>

As you can see here, the updates are downloaded, but the user isn't told
that they are waiting for a reboot - but they happen when the user reboots.
<https://bayton.org/android/gpsu-system-update/>

Also, while we've discussed Project Mainline a few times on this ng, most people on this ng I believe are not aware that the concept even exists that Google is updating dozens of core packages monthly for Android 10+ forever.
<https://www.hexnode.com/blogs/android-project-mainline-everything-you-need-to-know/>

It's been that seamless since mainline started with Android 10.

Every subsequent version has been adding more & more mainline modules.
<https://www.xda-developers.com/bluetooth-ultra-wideband-mainline-modules-android-13/>

However, my phone is not set up by default in that I have the Google Play Store deleted from the user partition so any test by me might not reflect
how things work for most people who leave the Android set up by defaults.

Hence, I think it's a great idea that Jeff will be checking his update status, where here's a list of the core packages that are in Mainline.
<https://source.android.com/docs/core/ota/modular-system>

However, note that at least, you can manually update them at will.
<https://bayton.org/android/gpsu-system-update/>
Google Play System updates (Mainline)
Google Play System updates (also called Mainline updates)
are automatically downloaded but require a device reboot to be installed.
These updates won't trigger an automatic reboot and instead they are
installed on the next user, admin, or policy initiated reboot.
Reboots triggered by system update policy will install the
associated Google/OEM system update and any previously downloaded
Google Play System updates.
Google Play System updates can also be manually installed by navigating
to Settings > About > Android Version > Google Play system update.

I've had a look at those links and there is a lot of information there,
and it seems that some of it changed only last April.

I checked this morning and according to MAM (and my phone's Settings)
the current versions are:
Google Play Store:
41.8.14-31

Google Play Services:
24.26.32

Following the the support.google link I provided earlier, I see that the
Play Store is now at 41.9, and the Play services is at 24.27.

I'll report back in a couple of weeks after not downloading any updates
or rebooting (if the updates were downloaded silently).
--
Jeff

--- Synchronet 3.20a-Linux NewsLink 1.114