Week 17, Development and Testing Updates

Manoj · April 19, 2026, 10:32pm

/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 v3.7

Status: Released

ETA: 16 April - 24 April

Feedback and Voting
Release notes
Please note the following devices will not be receiving the v3.7 build

Vendor	Name	CodeName	OS Version
Lenovo	Z6 Pro	zippo	A16
Xiaomi	Redmi Note 10S	rosemary	A15
Xiaomi	Mi MIX 2	chiron	A15
Nubia	Mini 5G	TP1803	A14
Xiaomi	Xiaomi Pad 5	nabu	A14,A13

These device builds failed on these OS versions. We will try to rebuild them if that works it will be released as part of v3.7 else they will be accommodated in v3.8 which should come out by May.
These builds failed due to changes coming in from the upstream code base.

OnePlus Nord Avicii OS upgrade issue post v3.7 upgrade release

Users who are facing an issue with network connectivity post the upgrade to A16 please share your comments in the issue created on gitlab
- Thanks to all those who have already shared their input on this issue.
- The developers are aware of the issue and have been asked to prioritize the fix.

A16 OS Release

Status: Released

List of Supported devices that got the A16 community build
New devices joining the supported devices list and come with A16 community build.
- These builds are community builds. Will require a manual download and install. Installation guides have been updated and share instructions on how to do a fresh install of the A16 builds. Take a backup before installation of a higher level OS.
- Official A16 builds will take some time. Will share information as to when they will be released.
- There will be further addtions to the list of devices we will release on A16.
- The plan is to update all devices where possible to the latest OS version.

Upcoming Milestones

Releases planned in the future are marked as milestones in gitlab

Milestones

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 planning 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.

Migrate 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. Check this suggestion.

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.6

3.5

Murena Cloud and Self-Hosting

Murena Cloud

Murena Cloud just got an update

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)

To Be Planned

Google Pixel tablet - tangorpro - A14 → A15
Murena One - A12 → A15
GS290* - A12 → A15
Galaxy S9* - 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 upgrades. The difference is the official builds get OTA OS upgrades. Community devices will require manual upgrade.
Will share dates and ETA once I get them from the team.

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

toggiburger · April 20, 2026, 3:29am

Hm, not sure if I’m missing something but shoudn’t the be this somewhere?

FP5 - FP5 - A15 → A16

Manoj · April 20, 2026, 3:48am

Yes indeed. Add the FP5 as well to the list.

Ivargiinotvi · April 20, 2026, 6:44am

Thank you for the great work! Can you say something about the shiftphone 8.1 official A16 build, as it isn’t mentioned above.

Manoj · April 20, 2026, 7:00am

All devices are due for an upgrade as older OS versions will eventually stop getting Google security packs, so we do need to upgrade all devices.
Will check for the Shiftphone 8.1

Update: The Shiftphone 8.1 is due for an update. For now, the team is first working on upgrading builds for all devices still struck on A12 and A13.

hakunamatata · April 20, 2026, 8:15am

Don’t mean to quarrel, but why are those upgrades prioritized over all the A12/A13 devices which are end of life for some time now?

Manoj · April 20, 2026, 8:21am

A12 and A13 devices upgrades is prioritized. Unless the devices are very old and would not scale up to A16 the builds are all on the topmost priority for the team. In case of devices, we cannot build on A16 as we mentioned we will go for a lower version build.

AnotherElk · April 20, 2026, 8:43am

The OS OTA section here is only about upgrades via the updater, which require extra development and testing and are done only for selected devices which mostly are or were sold by Murena themselves.
There are more upgraded builds being tried and done for /e/OS’s range of devices than are mentioned in this section.

Lobster · April 20, 2026, 9:32am

Hi @manoj,

Thanks for your huge daily work ! With this reasoning of devices prioritise if on A12/13, I would expect the Official FP3/3+ to be under development by now. Do you have any status to share on this ? I have concerns as no security updates are done any more and that could become pretty serious for a daily driver, isn’t it ?

Thanks a lot for your answer

Manoj · April 20, 2026, 9:46am

That is a concern we also share. Unfortunately, I do not have any ETAs to share. Will do once the team is close to a working upgrade build.

AnotherElk · April 20, 2026, 4:28pm

As mentioned before, /e/OS Android 15 community is available for manual install for FP3 users who want to strongly prioritise getting security updates right now … /e/OS community FP3 download

Of course community is not 100% the same as official (else it wouldn’t exist), and the manual install is not as convenient, and once official caught up to newer Android, community will most likely be phased out … but it’s out there, and it gets security updates.

Just mentioning for fellow FP3 users reading along.

Manoj · April 20, 2026, 10:28pm

We will be releasing a v3.7.1 which has updates to the Browser code. We are also working on adding patches to resolve the issue reported here. This particular issue seems to be due to upstream backpatches specific to A13 code.

The release notes showing up in advance seems to be an error.

Will update once I have more details later today.

Manoj · April 21, 2026, 6:48am

OnePlus Nord avicii users who experienced issues with the device, pl can you share the device model.

Settings >> About Phone >> Model

Pl add the details on the issue in gitlab

Lobster · April 21, 2026, 9:57am

Thanks for your help ! Will the change from Official to Community be with data loss ? Is it possible to reverse to official whenever available later on ? Data loss ? Nice to be able to count on skilled guys out there !

Manoj · April 21, 2026, 10:05am

Unfortunately, the move from Official to community will be a manual effort and may include data loss. Both builds are made with different keys. A clean format and install would be the best way after taking backups.

piero · April 21, 2026, 10:09am

UNOFFICIAL TIP :

if coming from an already installed “official” /e/OS and you want to upgrade to a15 “community” (without loosing data and locked bootloader)

using → Settings → System updater → Local_update
or using “recovery mode” and “adb sideload”

you will face a signature mismatch, simply choose “install anyway”
A clear guide to Upgrade your /e/OS to a new Android major version without loosing /data

Files for upgrading an existing /e/ system via local update or the /e/ recovery can be found here:

https://ota.ecloud.global/api/v1/FP3/community/

urs_lesse · April 21, 2026, 10:45am

@Lobster I guess you are on an FP3, so the download link would be at https://ota.ecloud.global/api/v1/FP3/community/. Here is my report of how I switched an FP3 from T-official to A15-community: https://community.e.foundation/t/feedback-for-v3-1-1/73830/46?u=urs_lesse As I remember, data was taken over and not reset – I did not need to change the (locked) bootloader, so no factory reset was triggered.

piero · April 21, 2026, 11:04am

there is yet no feedback about reverting from “community” to “official” without data loss…
But switching back to “official” with a new install (and data loss) will be possible if the command
fastboot flashing get_unlock_ability is able to return 1.
(check the possibility to enable the “allow OEM unlock” option in “–> Settings → system → Developper Options”) NEVER DISABLE IT !

Manoj · April 21, 2026, 12:01pm

Important:

We will be releasing a v3.7.1 build starting today for all devices except those on A13. The changes in v3.7.1 are given in the release notes.
- The changes are browser related as mentioned in the release notes
For A13 builds we will release a v3.7.2 with fix related to this issues

Manoj · April 21, 2026, 10:48pm

Why the additional v3.7.1 build is being released?

To explain, let me give you an idea of how we work towards a release

We have a set of milestones, which are future releases which will have bugs and issues assigned to them
Around 2-3 weeks before a release date we take stock of the state of the fixes. This is the code freeze date. All issues that are due for release in that particular build, say v3.7 are tested if they have been fixed. If yes, they are added to the release if not they will be pushed forward, based on the complexity or priority of the issue.
Pl note development does not stop due to this code freeze. Development on other issues and new features are all in progress on different code branches, but they would not be a part of this release
In certain cases, after we freeze the code, we get some important patches from upstream which on evaluation we feel we have to release ASAP to the users. The problem for us would be v3.7 has already reached a certain level of testing and is ahead in the release process
This is when you get releases like v3.7.1. this also goes through various levels of testing to qualify for a release.
Next we have another release which will be specific to A13 devices. That is the v3.7.2 which we are testing at present. Based on this build passing the QA test we will release it. Also note the version number of v3.7.2 can also be incremented in case there are further changes in that A13 specific build.