I am generally hesitant about installing new versions of e/os on my phone. Of course, I know that you are reliant on users doing just this so, that you can identify any bugs or fixes that are needed. But, as a linux user, I generally install LTS versions which have a known end of support date so, that I can upgrade when I am ready to. I was not sure, with e/os, how long specific builds are supported for or if older builds are no longer supported after major upgrades have been released? I am currently still using 2.9.
1 Like
Good question, not sure though if that comparison may be a category-error (?) or I maybe miss your point anyways…
Linux LTS gets patches or security fixes too, is that correct?
In that case I would not look at the eOS-version but rather on the Android-version behind it.
Than it would be “not upgrading” (next Android version) instead of “not updating” (changes, fixes, patches, no change of Android version) in eOS-terms.
I think staying on one version makes you miss security patches and other fixes, that’s probably the one thing to consider. If you can live with that for whatever reason you should be fine.
In case you decide later: sometimes jumping many versions at once might include issues - but observing the forum (build feedback threads) and the release notes or asking in advance is a good way of dealing with that (rather general) risk.
So here you / we have an open source environment in Linux.
Android OS is proprietary ex-Linux licenced to manufactures by Google to do what they can with it at their price point.
Meanwhile Google shares much not all of the code with AOSP – /e/OS users running a branch of AOSP.
-
Device users are in the hands of Vendors providing security patches. Once upon a time this could extend for as little as 18 months, now “green” benefits are seen and Vendor SPL are often currently quite long.
-
OS Google provides to AOSP Android SPL for “a few years”. It depends how you measure that length from initial or manufacturer’s release. [1]
So this is a lot different from the original proposal by Linus Torvalds on the 1970 IBM PC specification The IBM PC
If hard to answer a “General question” here is a “user story”. My “other phone” is a OnePlus One bacon built, one might say, for long life and Custom builds. [2]
It would take an /e/ historian to confirm this but I think supported from e-0.3 or thereabouts.
Vendor security patches stopped Sept 2016.
This will be the indicative date when manufacturer support ceased.
Currently Android SPL is Nov 2024 as I didn’t build myself an update since 
Technically running AOSP A13 it should be possible and have Android SPL of July 2025.
/e/OS support stopped primarily as the partitions as delivered were too small for the full /e/ system (can be fixed) and lately for other reasons in my case as “too difficult” requiring for instance ultra legacy from LineageOS.
[1] Alluded to and better told Article from GrapheneOS about /e/OS - #4 by Bowibit
Another angle Oldest phone with newest Android version (just for fun) – no general answer (from me).
If bought new in 2014 I would have got 11 years out of it, with /e/OS (including the spell with own Custom) for 90%.
My IBM PC built 2008 runs Debian 12 just fine.
But now reading your post below, perhaps I do cover the issue (at least in part) of why Updates are such a big thing and should really be taken “every time” if one intends to be “fully networked” as a smartphone tends to be. Two or more phones judiciously configured can help avoid fingerprinting.
Sorry - have changed the category. Yes - Linux LTS versions are usually supported for up to about 5 years for security patches etc. but, don’t get feature updates. If you just want an OS that will work reliably and are not bothered about using the latest versions of software, it is a sensible choice. I wasn’t sure if I could effectively do the same thing with my phone, by delaying the large updates.
Sorry, Yes, I sure get your point and I did not mean the category of your post but I wondered whether that comparison works at all … now I guess the why to the doubt in the back of my head is the answer:
Updates of eOS are in most cases a mixture of security patches and the like and feature updates.
So in most cases (= simply relying on OTA, no ROM-builds on your own etc.) You cannot choose only the security update w/o the rest.
Not sure what that would be called in the Linux-world … “rolling release” maybe?
1 Like
| Android Name | AOSP version | last AOSP SPL | last /e/ version | end of /e/ support |
|---|---|---|---|---|
| Nougat | android 7 | 2020/02 | e-0.21-n | 2022/01 |
| Oreo | android 8 | 2021/02 | e-0.21-o | 2022/01 |
| Pie | android 9 | 2022/02 | e-0.23-p | 2022/03 |
| Quince Tart | android 10 | 2023/02 | e-1.17-q | 2023/11 |
| Red Velvet Cake | android 11 | 2024/02 | e-2.2-r | 2024/07 |
| Snow Cone | android 12 | 2025/02 | e-3.0.4-s | 2025/07 |
| Tiramisu | android 13 | 2026/02 | ||
| Upside Down Cake | android 14 | 2027/02 | ||
| Vanilla Ice Cream | android 15 | 2028/02 | ||
| Baklava | android 16 | 2029/02 | ||
| C…? | android 17 | 2030/02 |
3 Likes