Week 21, Development and Testing Updates

Manoj · May 17, 2026, 10:18pm

/e/OS Weekly Development and Testing Activities

Summary of weekly development and testing activities by /e/OS developers and volunteers.
Updated content is marked with the emoji.

Release Updates

Upcoming v4.0

Team is busy in putting the finishing touches to v4.0
As the version number indicates it will be a major release
As we near its completion, we will share more details of important updates and improvements that would come as part of v4.0
We will have a live launch event for the release of v4.0 (date and links will be shared)

ETA for v 4.0: June 2026

Current v3.7.x

Feedback and Voting
Release notes
As part of v3.7 we also released v3.7.1, v3.7.2 and v3.7.3
v3.7.1 had browser specific updates
v3.7.2 was specific for A13 builds
v3.7.3 released for all devices with May security patches
- Feedback and voting 3.7 / 3.7.1 / 3.7.2 / 3.7.3
- Release notes
Testing of A16 for OnePlus nord avicii issue still in progress

Upcoming Milestones

Releases planned in the future are marked as milestones in gitlab

Milestones
v4.0 will not be showing up there and may show up as v3.8

Murena Account Recovery Email

Ensure your Murena Workspace account (e.email or murena.io ) has a recovery email set. New Accounts without a recovery email will face reduced functionality for 30 days and post that will be marked for deletion. The process will be the same for existing accounts without a recovery email

To check if your Murena account has a recovery email click here

Link will require you to log in to your Murena workspace.
In case your account is disabled, you can contact me - @Manoj on this forum and I can assist with getting the account re enabled.

Documentation

We are working on updating our documentation site.

Besides making navigation easier the plan is to make user contribution easier.
Currently under planning stage, will share details once there is any progress on it.

Migrating your data from google cloud to your Murena account

Follow the instructions in this guide.

Want to report an issue in /e/OS.

Create the bug in Gitlab.
If you are facing an issue in creating the ID, create or use your Murena workspace ID as suggested here.

Security Information

Security Patch Release Process explained here

We will be sharing a detailed document about our security policy.

Previous Releases & User Feedback

3.7 / 3.7.1 / 3.7.2 / 3.7.3

3.6

3.5

Murena Cloud and Self-Hosting

Murena Cloud

Current Version: 32.0.6.11

Resources:

[Release Notes]( v32.0.6.11 · e / infra / ecloud / nextcloud · GitLab)

Self-Hosting

Current Version: v26.0.8.23

Resources:

Release Notes

Upgrade Guide

Status:

Self-hosting guide update pending

🔍 How to Check NextCloud Version

Method 1: Murena Settings

Go to Murena Settings

Look for “NextCloud xx user documentation”

Method 2: NextCloud Scan

Visit NextCloud scan link

Input https://murena.io

Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad. This is normal - patches are tested before deployment.

GSI (Generic System Image)

Current Version: /e/OS A10 v1.17

Resources:

Download

Sources

Next Version: /e/OS T (A13) - skipping A11 and A12

Release dates to be announced

OS OTA Information

Completed

OnePlus - Nord - avicii - A12 → A16
Teracube -2e - zirconia - A12 → A15
FP5 - Fairphone: A13 → A15
FP5 - Fairphone: A14 → A15
FP4 - Fairphone : A12 → A13
S9/9+ - Samsung : A11 → A12
GS290 - Gigaset : A11 → A12
GS290 - Gigaset : A10 → A11
FP3 - Fairphone : A12 → A13
S7/7+ - Samsung : A11 → A12
FP4 - Fairphone : A13 → A14
S8/8+ - Samsung : A11 → A12

Note: OTA upgrades are for official or stable builds only

Under Development and Testing

FP4 - FP4 - A14 → A16
FP6 - FP6 - A15 → A16
FP5 - FP5 - A15 → A16
FP3 - FP3 - A13 → A15 (ETA 1- 2 months)
OnePlus - nord - avicii - A14 - A16 (v4.0 )
Galaxy S9* - A12 → A15

To Be Planned

Google Pixel tablet - tangorpro - A14 → A15
Murena One - A12 → A15
GS290* - A12 → A15
Galaxy S8* - A12 → A15
Galaxy S7* - A12 → A15

(Devices marked with an ‘*’ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)

Check the section titled A16 Updates below

📖 What is OS OTA Upgrade?

Traditional Process:

Download correct OS build from supported device list

Download stock ROM from vendor site (for some devices)

Back up your data

Install stock ROM, then /e/OS ROM

Restore backups if needed

OTA Benefits:

Simplifies the entire process

Requires significant development and testing

A16 Updates

We plan to update all devices currently on A12, A13, A14 and A15 to A16
In case any device is not able of handling the A16 builds we will share that information.
The team expects that A16 would not be buildable or installable on some of the older gen devices like the Samsung S7 or S8. There could be more.
- For such devices we we will work on getting them to the highest OS version possible.
As you may be aware A12 does not receive security patches anymore. This will next impact A13 and so on. This is a standard Google policy to end of life (EOL) older Android versions.
All devices we sell in our shop, with official builds are priority candidates for OTA OS upgrade to A16.
- Official builds get OTA OS upgrades.
- Community devices require manual upgrade.
(Ideally in all cases, take backups while upgrading the OS of your device)

Miscellaneous Information

Real-Time Service Status

eCloud Real-Time Status

/e/OS Real-Time Status

New Gitlab account creation

If you are trying to create a new /e/OS Gitlab ID and facing issues with the email ID, you can try and create a Murena Workspace ID and use it to log into Gitlab. Check the updated documentation here

🎫 Helpdesk Services

For Paying Murena Customers

Murena device purchasers

Paid Murena cloud account holders

Active donors from the past year

Response Time

5-10 day response wait period due to high volume of requests.

Contact

Murena Helpdesk Contact Form

For Free Users

Forum

GitLab Issues

Telegram Channels

Warning: Old helpdesk email IDs are no longer monitored.

📱 Device and Vendor Announcements

Gigaset GS290

Sales stopped (vendor ceased production)

Support continues for existing users

Murena One

Sales stopped

Support continues for existing users

Murena Two

Sales stopped

Support continues for existing users

Pre-Flashed Devices

Available in EU, US, Canada, and Australia. Check the complete list on the Murena shop

Purchase via Murena Shop

🌐 /e/OS Website and Social Media Links

Official Websites

Telegram Channels

Social Media

Newsletters

To send in your Donations : Use the email ID donation@murena.io

Important Notice

Do Not Post Test Build Information on the Forum

Why this is important:

Test builds are untested and may cause device issues

These builds can potentially soft brick user devices

Such information can confuse other users who don’t see these builds in the updater

Not all forum users are experts in custom ROM installation

For Interested Testers:

If you understand custom ROMs and can perform basic testing

Join the testing team

Share feedback on the dedicated Telegram channel

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

Aroun · May 18, 2026, 9:01pm

Will the Google pixel 8 and the CMF phone 1 which are on official build also receive OTA update to A16 at some point?

Manoj · May 18, 2026, 10:26pm

All devices - official as well as community will get the latest OS build possible. For some an A16 may not be possible. For such devices it would be the next lower level possible. For example, if A16 is not possible then it would be A15. Official builds get OTA OS upgrades which take time as the changes need to be seamless and avoid data loss. Both Pixel 8 shiba and cmf 1 will get the OTA update. The ETA is the unknown factor at this time. Will share dates once I get them from the developers.

Aroun · May 18, 2026, 10:51pm

Amazing, thank you for the confirmation!

Grueneenergie · May 19, 2026, 4:38pm

Hi there. I am currently on latest a14 on my oneplus 9 pro. can i just install latest a16 via recovery? do i keep all my apps like banking etc working? o.c. ill do a backup just in case, but is it generally possible without a full reset?

Thanks for reply. Greetings

cemoi71 · May 20, 2026, 8:16am

Hello to the e.team.
I’d like to give you a question about your roadmap for the next version of the software.
We had shortly since a couple of month the integration of the A16 variant for many phones.
If we observe how it was integrated, for a huge amount of devices it wasn’t not really esay obsiously.
Then currently we observe that for some devices there is for the A16 version still some issue.
Having a look on the 4.0 of eos is great i’ll enjoy it.
But i’m not really happy to make the transition from v3.7.x onto 4.0 if there is still many mess on many devices with the 3.7.x
Would it be not wise to make the v3.x version more stable before to go on the 4.0?
Means make a v3.8, and 3.9 until all a16 are well fine?
Then afterwards would the 4.0 not really chaotic…

Manoj · May 20, 2026, 9:14am

There would be a live presentation to share what would come as part of v4.0 At present we are testing those features and getting towards the v4.0 release.

cemoi71 · May 20, 2026, 11:33am

hmmm yes that’s great…
maybe I’ve explain my self something wrong…

First now I’d like to ask how the transistion will be done? directly from v3.7.x into 4.0?
or smoothly with further 3.8 & 3.9 ?

I’d suggest more to go smoothly because of more instabilities revealed during the last eos versions by/after integration of the A16. variant for each devices…

Seems to me that currently there are still resident issues which are on the v3.7.
A new main version on eos could maybe make the a stronger problem by deploiment of the new one.
Would be maybe better that first the last v3 version goes stable on the whole park before to deploy the naxt one.
(just a naiv question of someone who have no idea on how it works by the eos dev team)

Manoj · May 20, 2026, 11:47am

There is no v3.8 or v3.9. The next build is v4.0

soyl · May 20, 2026, 1:47pm

I hope updates come soon. Google will eventually leave Android 14 without security updates.

Doppel-D · May 20, 2026, 3:11pm

What brings you to that speculation?

sophimae · May 20, 2026, 5:11pm

The first number is refering to the feature set or feature release of e/OS. The number behind is just the version within that feature release.

To put simply. Whatever 3.8 would have been, 4.0 is. The 4 only denotes, that there are bigger new features that are significant enough to say that that’s a big jump. Like Android goes from say 15 to 16, /e/OS goes from 3 to 4. The number antecendent is just a reference as to which update within that feature set it is.

Every stability improvement there would have been if they decided to make a 3.8 version, is now in 4.0.

Also, as it seems you think the number would go to 9: They could, if they wanted to, make a version 4.11 if it is the twelfth update. The numbers are just a human decision and, thus, arbitrary.

AnotherElk · May 20, 2026, 6:01pm

Emphasis is on eventually.

Android 13 ran out of security update support fairly recently. If Google doesn’t change the scheduling compared to the past years, Android 14 should get security updates until early 2027.
You can also see that in your screenshot.

Currently there’s no need to panic. (Emphasis is on currently .)

cemoi71 · May 21, 2026, 7:10am

that’s exactly the point that i want to discuss.
the big jump will be done. but the integration of the A16 was done by the last v3.x version and is not really stable enough for me. there are still many bugs on the A16 parts.
my opinion, ist really postpone the 4.0 and make really the v3 espeially for the A16 stable enough. otherwise the 4.0 will be too hard..
But i’m not the developer nor the stakeholder…
Hope that people know what they do. as I told is just my opinion. but for me it’s clear.

sophimae · May 21, 2026, 9:08am

I think you don’t understand how development works. There is nothing missing. Every stability improvement they would have done they still do. There is nothing that gets left behind.

Features are also continuously developed. These are not so much shared resources as these things are done parallel to each other anyways.

Delaying 4.0 feature release would change nothing in development about how many stability improvements they work on and release. Just instead of naming it 3.8 it also packs some new features and is named 4.0. It is the exact same thing.

If it makes you happy name 4.0 3.8 in your head canon, because that is the reality. It is just names, nothing else. Development of stability fixes happens all the time simultaneously and will happen regardless of whether the name of the OS is 3.8 or 3.9 or 4.0 or 2.32 for that matter. It is just a name and just does not matter in terms of stability development.

If you don’t understand that, I don’t know how to explain it to you in better terms. The question you are asking is just not a question because it builds upon a premise that is not correct.

AnotherElk · May 21, 2026, 11:04am

The abstract concept of version numbers is as @sophimae explains. It is of little real consequence which label gets slapped onto a next release that is being worked on, it’s still the next release.

But which release is being worked on as the next one could be changed, which I think is what @cemoi71 wanted to propose (but most likely will not get).
We know the label “4.0” is bound to new features, this is an organisational choice in development and marketing. If development would for whatever reason switch to work on a different new release as the next one without the new feature set it most likely would organisationally not get the “4.0” label, although it abstractly could.

cemoi71 · May 21, 2026, 11:26am

I understand how it works more or less. but
as you told with the 4.0 comes more workload because of new tools new functionalities new stuffs. if the 3.7 is still so buggy, how is the probability that the 4.0 will be much more buggy?
I’d say much higher (we talk about probability).
if the current version has is payload, and where increased with a new comer variant A16, with much more payload issues.
could you please tell how will the effectiv payload on working on new stuffs with the last increased payload with issues?
Is just an addition…
not forget the amount of devices differencies, there are not just only 10 devices, and how many variants? a14 a15 a16 ?.
Really, make the dev in pause, to fixe as mass of issues which will comes with the new 4.0 payload.
is just mathematical a+b+c
As I tell I hope that eos dev Team discuss &tailors well between each other and the whole team till strategy are well informed and confident about the strategy.
I find it something risky, but I’ve no glue of what about they discussed, how is the stand of the whole platform.

Manoj · May 21, 2026, 10:43pm

About the upcoming v4.0 release
Software releases have a major release and minor release. The upcoming v4.0 is a major release. The purpose behind a major release is to address long standing user requests for additional features and enhancements. These features improve the current functionality of the OS. Minor releases usually have bug fixes and slight improvements.

Major Release: 1.0, 2,0, 3.0 & 4.0
Minor Release: 3.1, 3 .2 …

Anyone who has browsed this forum or the /e/OS Gitlab will have read the hundreds of requests we get for enhancements from users.

These requests are addressed in the major version release. This is also what we promise in our roadmaps.

The version change is also to address the changes that come about in Android source code or the changes we are facing in the software environment around us.

Needless to say, we do endless rounds of testing before each release. Users volunteer to help our QA teams find and debug bugs in the OS code. Once identified these bugs are removed from the code by our developers and the code is again tested. The issues are closed only when the bug is not visible in the final code. If it still exists that code bit is not released and moved to a future release for resolution.

The whole point of software development is to move ahead with change and improvements. If there are bugs encountered on the way, we find them and resolve them. To sit and wait for the current code base to become perfect will also mean ignoring the changes coming in the third-party software most of us use or the upgrades that have happened upstream. I cannot emphasis enough how much testing we put into each release - major or minor.

We will share details of what will come as part of the v4.0 release.

Espadon · May 22, 2026, 5:52am

@Manoj Have-you some informations on restart of GSI version? Or the GSI’s developpement is stopped?

Manoj · May 22, 2026, 5:59am

For now, it is not in one of the priority tasks list. It has not been stopped but not being taken up right now. At present as you can imagine it is all about v4.0 with the various teams.
Will check with the developers as to when they plan to restart work on the GSIs.