(Sharing details in advance as some users have requested that they be given an advance notice of a release)
Feedback poll
We will also have a poll to rate this build.
I have updated to v3.4 on my device and it is working well
I updated to v3.4 but I am having issues (Please share the issue details on this thread)
I am not able to update to v3.4 (Please share the issue details on this thread)
0voters
To report issues with the build or applications raise an issue on gitlab. Ideally first discuss the issue here and check if users of the same device on this build are having the same issue.
When sharing your feedback or issues, Please add the following details
Vendor Name
Device name
Device CodeName
Version of /e/OS or Stock which existed previously
Refer this guide to share more details in your feedback
Do not share test build information on the forum or in this thread
This thread has been created specifically for posting information on official and community /e/OS builds.
To understand the difference between build types refer this guide
Please do not post information or links to /e/OS test builds on the forum.
The test builds are as yet untested and under development, and may in some cases cause user devices to soft brick.
Such information can confuse other users who do not see these builds in the updater.
Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds
If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team
As part of the testing team you can share your comments on the dedicated testing telegram channel.
Booted v3.4 first time yesterday at 16:04, after installing on WLAN, install time 1:13 hrs, display on 1 min., three break-offs.
Since then it used up 63% of battery capacity, resulting in a projected running time of about 1,42 days. This is even worse than the dev-version which offered a running time of about 2,08 days, and again the worst version ever.
On the screenshot you can see that network and ntfy leave extremely high numbers:
Have you by chance tested the GPS? If it works I might update despite the battery consumption, but if not I think I’ll stick to 3.2 for one more version. Thanks!
Perhaps it would be better to keep these topics closed until the public release is online. As can be seen here (and in the previous editions on 3.3. etc.), beta users keep ignoring Manoj’s request not to post feedback to beta releases in these topics.
Update v.3.4 is now available in the community version for local update for the Fairphone 3, Fairphone 4, Fairphone 5 and Fairphone 6. It is not available yet right now in the Updater**, and not in the official version yet.
Release notes are up now
Novelties from the release notes for Fairphones:
The Fairphone (Gen. 6)
Fairphone Moments is now available on /e/OS: It’ll be automatically updated via App Lounge whenever an update is available. To enable this feature please go to Settings > System > Switch and select Fairphone Moments
The Fairphone Camera app is now enabled by default for a better photography experience, while the /e/OS Camera remains available as a toggleable option
Fairphone 5
Mobile Data and VoLTE are now enabled by default out-of-the-box, while VoWiFi is disabled by default to ensure better initial connectivity stability
Android SPL:
This /e/OS 3.4 version includes all Android security patches available as of January, 1st.
This is a mystery: why can’t there be once for all a page everyone knows with ordinary and binding informations about what has been released and what hasn’t? Herewith I suggest this.
This page could be provided in the top line:
Donate to e Foundation — Murena handsets with /e/OS — Own a part of Murena! — Releases
And there could be an automatic growing table like this:
date
release
official
community
2026-01-dd
3.4
…
…
2025-12-dd
3.3
…
…
…
…
…
…
Or, because of different release dates, there could be two separate tables:
date
release
official
2026-01-dd
3.4
…
2025-12-dd
3.3
…
…
…
…
date
release
community
2026-01-dd
3.4
…
2025-12-dd
3.3
…
…
…
…
And in the right columns of these tables could be remarks, excluded or delayed devices, links to the release notes, whatever.
The problem is: every single time when a release is published a forum post comes up a week or two weeks before but you never know when the update is and this post gets then longer and longer with answers and after some days it’s not on top anymore because of other topics. When you are in vacation or you couldn’t read the forum for a while you get the question - what’s the last release? I would find such a page much more professional than these forum posts. These posts have another meaning: they are important for user feedback and solving configuration problems.
BTW: these tables could also show completed downloads. So they could also document the distribution history.
I tell it again: this is “build feedback”. For me as a developer a build is not a release. I do several builds each day but not every month a release. The release dates are difficult to find and it’s also not easy to determine if it’s community or official.
I’m not using App Lounge. I only use FDroid and Aurora Store instead. Would it be possible to receive updates for Fairphone Moments (or also for Fairphone Camera) through FDroid or is the App lounge the only way to get those “apps” updated?
This URL is official only, community is on another page with other timestamps. And it’s only one concrete device.
This is something I also suggest related to this: make all variants of the same release have the same timestamp. (A timestamp isn’t needed at all when you have proper versioning. A build timestamp makes it indeed complicated: equal things should have equal names.)
no, this URL is not sufficient enough
at this URL, you will only see IMG- files
even contra-intuitive, also there, OTA files are hiden, you need to know the exact filename (that is the same minus the 4 “IMG-” caracters) to modify URL in the adress-bar
Release Date: 19 Jan to 26 Jan
Do not share test build information on the forum or in this thread
The Fairphone (Gen. 6)
It’ll be automatically updated via App Lounge whenever an update is available. To enable this feature please go to