I found the release notes here: Releases · e / os / 🚀 Releases · GitLab.
The installation guide for my device offers two options: Community or Stable (Install /e/OS on a Fairphone FP5 - “FP5”):
Could you clarify which of these options the release notes correspond to?
A very good question … as far as I understand, stable=official builds are built to the same recipe. This, imho, provides consistency from a support POV.
Community=dev builds might have slightly more advanced features, device dependant … but this is not a certain or fixed feature.
The release notes should really apply to both, I believe. I do not have experience of dev=community builds “lagging” wrt release notes … (but it is just conceivable that some device on a dev=community build might fail to run (nicely) some “new feature” seen in release notes.)
On the other hand some community=dev build might contain some advanced feature which in time may become “standard” or may be dropped, as time passes, but I have no experience of this either.
I noticed the release notes include an Assets section with an archive of notes. Could someone please guide me on where to download the latest version of /e/OS for my device?
To understand the difference between /e/OS builds check this guide
Both are builded by the /e/team infrastructure…
when
are builded and shared by enthousiast users…
Exactly as you quoted …
… which is found from Smartphone Selector
→ FP5 Info about Fairphone FP5 - FP5
→ install page Install /e/OS on a Fairphone FP5 - “FP5”
… but Release notes for Android 13 (T) are also available v2.6.3-t · e / os / 🚀 Releases · GitLab
You have found them very early … sometimes the builds are published and we are asked “why no release notes ?”.
However when e-2.6.3 is published, some devices will get Android 14 (U) and some Android 13 (T).
Are new /e/OS builds universal, or does each phone have its own version?
I’m curious if there’s a single /e/OS build for all devices, or if each phone requires its own specific version.
If the builds are device-specific, what’s the reason behind this? For example, in my experience with Ubuntu, there’s usually a single build that works across different hardware configurations.
Even improved, all were respective to standard from legacy IBM x86 Personal Computer architecture.
Each smartphone or tablet model is an unique cocktail, proprietary designed.
This approach is limited even with Ubuntu (or PC OSes in general for that matter) and doesn’t cover different processor architectures, see for instance https://ubuntu.com/download/server#architectures or Download Windows 11 Arm64. Different builds are being offered for those, too.
Android smartphones just complicate this one step further, requiring unique builds for their unique hardware setups, as @piero pointed out.
Android smartphones only share the same builds when sharing the exact same hardware (e.g. under different branding) or when they differ in minor hardware details unrelated to the core chipset which one single build can still cover (e.g. Fairphone 3 and 3+ get the same builds).
This topic was automatically closed after 60 days. New replies are no longer allowed.