Week 26, Development and Testing Updates

Manoj · June 21, 2026, 10:15pm

/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

Current release v4.0

Staggered release 11 June 2026 - 22 June

This is a major release.
- Which means that in addition to bug fixes and optimization, this release will include new features that enhance /e/OS and Murena services. Some of the features that come with v4.0 are
  - Murena Passwords
  - Murena Sign
  - Murena Meet
  - Murena Vault
  - Backup
  - Google data migration
- Documentation on all the new features being shared. Please note some of these features are in beta phase. Additional development and improvement is in progress. We look forward to your comments and feedback on these features.
Feedback and Voting
Release notes

What is a staggered release

Please note the v4.0 release is a staggered release like all our releases.

Which means 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. For example, for v4.0 we started the release on 11 June and it will complete for all devices around 22 June.

Upcoming Milestones

Releases planned in the future are marked as milestones in gitlab

Milestones

Roadmap for 2026

Check out Gaël’s article on the roadmap for /e/OS and Murena in 2026

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

Details on device app compatibility is now displayed in the supported device table

Build type word in the documentation will be changed to Release Type

Build variants will be visible in the supported device table - basically there are two build variants -user and userdebug.

A simple explanation of what they mean would be available when user hovers the cursor on the terms in the supported devices list table.

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.

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

4.0

3.7 / 3.7.1 / 3.7.2 / 3.7.3

3.6

Older Releases

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

FP3 - FP3 - A13 → A15
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
OnePlus - nord - avicii - A14 - A16 (v4.0 )
Galaxy S9* - A12 → A15
GS290* - A12 → A15 (v4.1)

All official builds are candidates for upgrade to A16 or the next OS for which build is possible.

A device with an official build name if not mentioned in this list does not mean the device has been abandoned. We continue efforts to build for all official devices we ever sold on the Murena Store. Dates of release of these builds will be shared when available.

To Be Planned

Google Pixel tablet - tangorpro - A14 → A15
Murena One - 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

urs_lesse · June 22, 2026, 9:28am

I think this can be moved to Completed now? And congratulations for this!

Manoj · June 22, 2026, 9:46am

Thanks for the confirmation that the upgrade OS has been received and is working. Conveying the message to the developers. Have moved the FP3 to the completed section.

Espadon · June 22, 2026, 3:17pm

May be, you could clean this portion?? I don’t think we need to 2 lines for FP3, FP4, FP5 or GS290 - Gigaset

@Manoj : Have-you got some infromations about the smartphone Hiroh I remember of a launch in february 2026.

strugk · June 22, 2026, 6:43pm

@Manoj you keep promising features here that will only be introduced in v4.1: (Passwords, Meet) - it is confusing

Bene · June 22, 2026, 7:11pm

These apps are apparently part of Murena workspace, which itself has its own app in the OS. So somehow, these components were part of this release.

But I’m totally with you, this isn’t something I would suspect to show up in the details of an OS release, but more in the details of an Workspace update.

So yeah, some more differentiation which is part of the OS and its bundled Android apps and the new web apps in Workspace would be great for some less confused users

Manoj · June 22, 2026, 10:30pm

For information about the devices sold on the Murena Shop you would have to check with the Helpdesk which is set up exclusively to serve the Murena product and services paying customers queries. Use the contact form and send them your queries.

AnotherElk · June 23, 2026, 10:04am

Users are discussing developments regarding this here … 👋 Meet your everyday privacy HIROH

mu88 · June 23, 2026, 3:29pm

Out of curiosity, @Manoj what did the team say regarding the FP4 as mentioned by you here Week 25, Development and Testing Updates - #29 by Manoj

equalizer · June 23, 2026, 5:16pm

I think it was something like “under developing an testing” and “work in progress”. No ETA confirmed

Manoj · June 23, 2026, 10:28pm

The team member said they would require about a month to develop the A16 build for the FP4 unless there are some unforeseen complications. Will share the progress once I get more inputs from the team.

Antho · June 24, 2026, 6:02pm

Just out of curiosity, why does it take longer for “official" phones like fairphone to have upgrades compared to phones not sold by murena?

AnotherElk · June 24, 2026, 6:16pm

Official Android version upgrades via the updater need a lot of additional development and testing work to prepare compared to “just” releasing the builds for download and manual install.
See the opening post of this topic, section " What is OS OTA Upgrade?".

Manoj · June 24, 2026, 10:36pm

The difference between the official and community channels builds is in the mode in which they are installed.
Both channels get their normal updates on a monthly basis. In that we share security patches, bug fixes.
The difference comes in the OS upgrade builds. These come usually once or twice in a year. For example, from A14 to A15 or A16.

For community builds the upgrade builds require a manual install process. Download the build, in some cases install the stock ROM first and then flash the /e/OS ROM.

For official builds - the devices we sell or sold on our murena shop, the process is a bit more complicated. We build the ROM in such a way that the upgrade happens with a click. This means no manual download of the build, no flashing of the stock ROM and then flashing like the community builds. For official builds we include the stock ROM in the /e/OS build where possible. In official builds the OS upgrade happens seamlessly with zero data loss. As you can imagine this requires more efforts especially development and testing. We put the builds through endless testing cycles. Official builds have device maintainers who help with the development, debug of their devices.

In both channels, official and community we always recommend you take a backup of your data. The installation steps for both channels are available on the guides in our documentation.

There are cases where this OS upgrade process is not smooth for example in the recently released S9 OS upgrade builds there is a factory reset required because these old devices have an issue with FDE encryption which requires a format before the upgrade.

We are working on releasing upgrade builds for all devices we sold on our Murena shop - old and newer models. The ETAs of when the builds will be released will be shared in these weekly posts.