Frank Slootweg <this@ddress.is.invalid> wrote

>> It's a Samsung Galaxy S10+.
>
> Thanks for the confirmation. BTW, mine is a Samsung Galaxy A51, a
> little over 3 years old, came with Android 10, now on 13.
>
> So the strange things are that 1) we (YTIW! :-)) didn't get notified
> that there was a 'Google Play system update', 2) my phone didn't
> download it and 3) your phone downloaded it, but didn't tell you to
> restart.

For that last issue, I believe there is a switch for that, as I've
seen it in passing in the past - but I'll have to look for it Frank.

Meanwhile, as with Frank's Samsung Galaxy A51 and AJL's S10+, my
free T-Mobile Samsung Galaxy A32-5G also updates all the time, where it
started life as Android 11, then 12 and now Android 13 over the years.
<https://i.postimg.cc/X7n5YVVs/galaxy-update-upgrade.jpg>

But the Android version is just a number - it's only one of many layers
of how Android updates most of its components essentially forever [1].
1. User apps are often updated forever (and very many are open source);
2. Key apps like Chrome are updated forever (many are open source);
3. Firmware (such as the Qualcomm modem firmware) are updated by Qualcomm;
4. Security updates (these are sometimes monthly or quarterly for years);
5. Android versions (these are change Android 11, say, to Android 12);
6. Core modules (updated either over GPS on the net or OTA by partners);
7. In addition, all core modules are donated to AOSP to maintain forever.

As Frank is realizing, Android updates in a series of asynchronous layers.
a. Some of those updates (as Frank noted today) occur during a reboot.
b. Others seem to occur seamlessly (without the user even noticing).
c. Most seem to have a switch to determine how they update though.

Hence it's wonderful that Frank is coming to the realization that Android
updates in layers, which we've discussed many times on this newsgroup.

In fact, I think my phone has been updated too frequently lately.
<https://groups.google.com/g/comp.mobile.android/c/nJ1tR7mMlI4/m/7MqhKYeKBwAJ>

Such that I've even turned _off_ some of the many Android update layers.
*Quick: Can I stop, prevent or stave off the upcoming December update?*
<https://groups.google.com/g/comp.mobile.android/c/udGDxJVcvxo>

Still, unlike the primitive iOS monolith, there are so many Android update
layers that it's hard to control (or even notice) the many Android updates.

One place to look though, but it's only one place so keep that in mind, is
Settings > About phone > Software information >
<https://i.postimg.cc/4ymqRF7n/updateallapps11.jpg>

Notice there are additional Android sub components listed there.
1. Android version
2. Google Play system update
3. Baseband version
4. Kernel version
5. Build number
6. SE for Android status
7. Knox version
8. Service provider software version
9. Carrier configuration version
10. Security software version
11. Android security patch level

However, I think, perhaps, the most important might be these though:
*Android version*
*Google Play system update*
*Android security patch level*

In summary, it's great that Frank is attempting in this thread to figure
out the frequency of the update to the 34 core packages in Android 13.
--
[1] Forever in this context means nobody can find any EOL date
(even if there were an EOL date, they're all donated to AOSP).