Week 20, Development and Testing Updates

[Manoj]

/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

• The next version release of /e/OS v4.0 is in the final development / testing phase
• 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

• Feedback and Voting

• Release notes

• As part of v3.7 we also released v3.7.1 and v3.7.2

• v3.7.1 had browser specific updates

• v3.7.2 was specific for A13 builds

• Testing of A16 for OnePlus nord avicii issue still in progress

• Feedback and voting 3.7 / 3.7.1 / 3.7.2 / 3.7.3

  • Check the Release Notes for more details

• v3.7.3 to be released for all devices with May security patches.

  • Release notes
  • ETA for v3.7.3 - Release Initiated

---

Upcoming Milestones

Releases planned in the future are marked as milestones in gitlab

• Milestones
• v4.0 will not be showing up there. Based on the QA results we will decide on how to go ahead with 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 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.7.1 / 3.7.2

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

Murena

/e/OS Website

Documentation

Report Bugs

How to Report Bugs

Telegram Channels

Available Channels

Social Media

XDA

X

Mastodon

LinkedIn

Medium

Newsletters

eFoundation News

Murena Promotions

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

[Manoj]

@Marsupilami

Great to hear that it’s moving on. But what about the promised A13 –> A16 upgrade for Google Pixel 5 (redfin), one of the official phones in the Murena store? Still not on the planned OTA upgrades list?

Would just like to add that this phone is special, in that it is the last one of Google’s phones to be in a small format that it can be comfortably operated with one hand. I’m sorry, but anything after that just falls out of my hand more easily. It’s really a pity that Google doesn’t offer smaller-format phones anymore. 6.0” screen, that’s the limit IMO.

Hi @Marsupilami the development team confirmed that they do have plans to upgrade the redfin. Do not have any firm ETAs as of now.

[Ivargiinotvi]

Can you tell me something about the OTA Update plans for the shift 8 (Otter) device? I bought it in the murena store and it doesn’t apear in the list above.

[silmathoron]

OnePlus - nord - avicii - A14 - A16 (v4.0 )

[Manoj]

Update: v3.7.3 release has been initiated for all devices. It is a staggered release, as usual and will be spread over a week.

• You can check the release notes for build details.

[equalizer]

Hi there Manoj,

would you mind telling me if there is an rough estimation of when the official update to A16 for the FP4 will be released? I read something about early 2026…

[piero]

@equalizer

I read something about early 2026…

it has already be released in march :

for a fresh install : https://images.ecloud.global/community/FP4/

for upgrading /e/ : https://ota.ecloud.global/api/v1/FP4/community/

@piero

to do it, you have several options :

they are the same as for regular update…
.

(it is recommended to take a backup of your things in case)

4. Universal Method, download the file on a computer, boot the phone into the recovery mode and use “apply update” then “from ADB” :

[equalizer]

Thank you. I should have specified I was talking about the official release.

Thanks anyway.

[Manoj]

FP4 Official to A16 is WIP. No ETA for now. It would be version A16.2 BTW.

[N200]

@Manoj

We will have a live launch event for the release of v4.0 (date and links will be shared)

Wow sounds exciting!!!

[GnuGorets]

Hi) Could you help, please, are you going to add support for devices with battery from 8000 mAh? Like OnePlus Turbo 6 / Nord 6 and OnePlus Turbo 6V / Nord CE 6

[Manoj]

The easiest way for us to add support is devices on the LineageOS device list. These devices have maintainers and complete device trees - the essential building blocks for all. In some cases device maintainers approach us and offer to help maintain certain devices or we take up the ROM building from scratch. This usually happens with popular models.

[Manoj]

Pl note the following devices would not be getting the v3.7.3 build.

Vendor	Name	Codename	OS version
Sony	Xperia XA2 Ultra	discovery	A16
Sony	Xperia 10	kirin	A16
Sony	Xperia 10 Plus	mermaid	A16
Sony	Xperia XA2	pioneer	A16
Sony	Xperia XA2 Plus	voyager	A16
Lenovo	Z6 Pro	zippo	A16
Xiaomi	Redmi Note 10S	rosemary	A15
Nubia	Mini 5G	TP1803	A14

• The reason is upstream code changes came in at the last minute.
• These devices will receive other OS version builds
• We will continue efforts to build for these devices and would release them if the efforts are successful.

[Nedo]

Hello,
for the FP4 I can currently see 3.7.3 A14 here

/e/OS official FP4 download

while I can see 3.7.3 A16 (and A14) here
https://ota.ecloud.global/api/v1/FP4/official/

In the initial post of this thread I can read that A16 for FP4 is under development and testing, so has it instead been officially released right now and the above mismatch is due to the ongoing staggered release?

Thanks

[Manoj]

The FP4 A16 builds are not ready as yet.
On the servers there would be test builds or builds a developer creates to check out particular features.
Suggest not to download such test builds unless you have devices which you do not use regularly and can be used for testing.

[Nedo]

Hi Manoj,
thanks for the info.

I thought that on those two links only the publicly-available-officially-released /e/OS releases could be found.
It is for me the first time that I notice such a “mismatch” between what available from those two links: after some time after a new release, those two links always showed the same latest version(s).

Anyhow (more generally speaking), I find it a bit confusing to have on those two links either the public versions and the “under development” ones without being able to clearly understand which is which between public and “under development”…

[Manoj]

@Nedo

I find it a bit confusing to have on those two links

The publically available link is the one which is accessible for devices when they go through the links on our documentation site. For example for the official FP4 it will be the link available here.

Ours is an open-source project where most of the source is visible if you spend time searching through gitlab. Not ever user does this or is expected to do this. Our testers, ROM maintainers would at any keep checking builds by posting it in gitlab. These builds are not for testing purposes.

[Nedo]

All clear now.

I misinterpreted the “official” word inside the two URLs I provided, by guessing it would mean “this is the public stuff which is already being pushed to the device” for both the URLs.

Now I will only use the images.ecloud.global URL for that “public stuff” regarding the FP4.

Thanks for the details