Please note that all /e/OS releases are staggered releases.
Which means, during the release days, every day a small set of devices are released.
The reason we do our releases in this manner, is we support 250+ devices.
If we release all builds at the same time the servers will crash as we will have thousands if not millions of simultaneous hits on the servers.
Official builds usually get released during the last days of the release process.
The release process usually takes about 7 to 10 days.
Feedback poll
We will also have a poll to rate this build.
I have updated to v4.2 on my device and it is working well
I updated to v4.2 but I am having issues (Please share the issue details on this thread)
I am not able to update to v4.2 (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.
You are running a testing build. If there is something you still not understand please raise it on your already active thread Fairphone 6 toujours pas Android 16
Murena canât win.
Feedback topic and release notes roughly upon release ⊠users: We werenât notified in advance!
Notification in advance, declared as such ⊠users: Where is everything? Itâs not there!
There is some issue with the definition of what is (or should be) an early notificationâŠ. Being notified in advance means that users installing an update should know what this update will change on their system before installing it, which basically means having access to comprehensive release notes. Missing important information (such as v4.1.1 dropping Seedvault without mentioning it in the release notes) is what is causing friction here.
Here, you are being notified in advance that the release note are not yet readyâŠ.which is great but why provide a link to the release notes if they are not yet ready then? It is like reading every single week for months now that the team will release a statement about security in e/OSâŠbut we are still waiting for this statement. We donât ask for more communication but for better communication!
Devilâs advocate role here, but I see your point of view as someone experienced with all the aspects, but many people here arenât or just arenât regular enough to know this. Murena isnât any company but most people are accustomed to how commercial companies do things a general way, Murena does it their way. Not to say thereâs something wrong with this but itâs to be expected because of the many non-standard concepts:
The version numbering. v3.9 vs 4.0 seems like a massive milestone but since itâs the same AOSP most of the time, sometimes 4.0 A14 to 4.0 A15 feels more different.
The disassociation of version of âOSâ with the version of Android itâs based on is still difficult to explain.
The different release tracks (dev, community, release, stable, etc.).
The specific jargon like GSI, AOSP, builds, codenames, security baselines.
The release notes that are shared beforehand or issues to report on Gitlab is difficult for people unexperienced with Gitlab to navigate.
Most communication is in text, not in illustrative ways.
Some launches may not follow the earlier traditions.
Confusing or open to interpretation communication (like Android version updates and âoriginal OS version security baselineâ).
To reiterate, Iâm not saying this as critique but I recognize the recurring confusion people have, itâs difficult to navigate when Murena and development arenât in your top 20 activities for the week. I understand how this all works (around 90% I guess), but Iâve been here for a few years. Itâs up to Murena to decide if this is all a bug or a feature.
Thanks for the release, but I lost access to my SD card after updating to 4.2 on Samsung S10e (beyond0lte). Now Android asks me if I want to format itâŠ
I canât tell if it is directly related to the update or if it is a pure coincidence ?
4.2 installed flawlessly on my Fairphone 3+ today.
On an interesting side note, I was able to install Fairphoneâs own new simple âFairphone Galleryâ app (that premiered today alongside their new Fairphone 6+) on my FP3+ today and it seems to work normally. If others want to test it as well, feel free. I would not think that it is strictly tied to Fairphones.
Release : 19 Aug to 24 Aug (staggered release)
Do not share test build information on the forum or in this thread
