Week 17, 2025: Development and Testing Updates

/e/OS Smartphone Operating System Development Updates
1

Weekly Development and Testing Activities

Summary of weekly development and testing activities by /e/OS developers and volunteers. Updated content has the :new: emoji.

Release

v3.0 :new:

Current Status:

Testing in progress

  • Details of what will come as part of the v3.0 will be shared.

  • As the version number suggests it would include some important updates and optimizations.

  • ETA : To be decided

:warning: Server Outage :warning:

Current Status:

  • Email: Working

  • Device Builds: Legacy OS builds for Pie, Q, or R are not available and will display a file/page not found error. We will add these builds at a later date. No ETA available for now.

  • Murena Cloud Services and File Drive Access:

  • Access restored for users.

  • Apps enabled on the Murena Cloud Dashboard. Sync for some apps may not work.

  • MurenaRecovery folder not visible yet; will be enabled ASAP.

  • Team working to enable all third-party app access. NextCloud Desktop client works if client synchronization as mentioned below, is enabled.

  • Notes sync with cloud possible post v2.9. If not syncing after upgrading to v2.9.Take a backup of your local notes before proceeding… Log in your murena account . In dashboard >> Your profile (top right )>> Settings >> Client Synchronization (left side menu) enable checkbox. This should start the sync.

  • Users are advised to back up their device data as full restoration of sync may overwrite or delete local data.

  • Compensation: Details on compensating paying users for service downtime will be shared via email and newsletter.

Upcoming Releases

Your feedback required

:point_right: Thanks to all those who have already shared their comments on these posts.

Ongoing Development Tasks

  • /e/OS V (Android 15) code work in progress. No ETA available.

  • /e/OS GSI on T (Android 13): Team exploring OTA availability and app to detect compatibility. ETA will be shared.

Previous Releases & User Feedback

Murena Cloud and Self-Hosting

Murena Cloud

  • In Progress v29.x.x development work

  • Current Version: 28.0.9.6

  • Changelog

Self-Hosting

  • Current Version: v26.0.8.23

  • Release Notes

  • Upgrade Guide

  • Next release planning in progress. ETA will be shared.

  • Self-hosting guide update is pending.

How to Check NextCloud Version

:information_source: Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad :neutral_face:. This is not an issue; patches are tested before deployment.

GSI

  • Current Version: /e/OS Q v1.17

  • Download

  • Sources

  • Next Version: /e/OS T (Android 13), skipping R and S. Release dates will be shared.

OS OTA Information

Completed

  • Fairphone: FP4: S (A12) → T (A13)

  • Samsung: S9/9+: R (A11) → S (A12)

  • Gigaset: GS290: Q (A10) → R (A11)

  • OnePlus: avicii: A12

  • Fairphone: FP3: S (A12) → T (A13)

  • Samsung: S7/7+: R (A11) → S (A12)

  • FP4: T (A13) → U (A14) :new:

  • S8/8+: R (A11) → S (A12) :new:

:information_source: All OTA upgrades are for stable or official builds.

Testing
  • OnePlus: avicii: S (A12) → U (A14)
To Be Planned

  • FP5

  • FP3

Definition of OS OTA Upgrade

  • Download the correct OS build from the supported device list.

  • For some devices, download the stock ROM from the vendor site.

  • Back up your data.

  • Install the stock ROM, then the /e/OS ROM.

  • Restore backups if needed.

OTA upgrades simplify this process but require significant development and testing.

Miscellaneous Information

Helpdesk Services (For Paying Murena Customers)

:warning: Old helpdesk email IDs are no longer monitored.

Device and Vendor Announcements

  • Gigaset GS290: Sales stopped as the vendor ceased production. Support continues for existing users.

  • Pre-Flashed Devices: Available in EU, US, Canada, and Australia via the Murena Shop.

/e/OS Website and Social Media Links

Websites

Telegram Channels

Social Media

Newsletters

:warning: Do Not Post Test Build Information on the Forum :warning:

  • Test builds are untested and may cause device issues.

  • Interested testers can join the testing team and share feedback on the dedicated Telegram channel.

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

9 Likes
2

Thanks for the weekly update. I have some general questions that I hope you or someone else from the team will be able to answer to:

  • Will a 2025 roadmap be published, as you mentioned here? We are almost in May…
  • On Gitlab I see that versions 2.10 and 2.11 are in the works, yet you mention version 3.0. What will be the next version? When will changelogs be published?
  • Why are most of the developments taking place in repositories that are not public?
  • Why didn’t previous changelogs mention the addition of the Murena MDM app? Why is the app not mentioned at all in the public part of Gitlab? Why has a closed-source app been pushed to all users without their consent?
  • Two weeks ago, Google fixed two zero-days in an Android security patch. Those vulnerabilities have been exploited by hackers. When will /e/OS receive security updates for this? All /e/OS devices are extremely vulnerable.
  • On January 26, you shared that OTA updates to Android 14 for FP3 and FP5 had “To be planned”. Three months later, nothing has changed. When will these OTA updates will be planned, worked on, released?
6 Likes
3
  • Have requested for the Roadmap to be shared. If there is any progress on this will update.
  • We may test all the development parts of v3.0 and if we are confident it can be released go ahead with the release. Most probably 2.10 may be renamed to v3.0.
  • Release notes are published after a release is made. This has been the standard process for all previous releases.
  • Development is always done in private repositories with access only to developers. No one would be sharing code which is incomplete or not tested with users.
  • On MDM I had already written about it multiple times but I guess no one read it.

This is an example of a non fully functional code / apk which made it into a prod build. The team has been asked to remove it. Something that is still not fully functional or complete will not be mentioned in the release notes.

  • Just because Google releases a code we will not be able to include it in the code immediately. Those with coding experience will be able to understand that developers would need to check it against builds and see that it works before adding it.
  • Will update once they the team starts work on the FP3 / FP5 . For now the focus is on v3.0
8 Likes
4

I did read it, thank you for the explanation.

1 Like
5

Hello Manoj I have a few questions, I hope I’m not breaking the rules.

Would /e/OS V be arriving around the same time U arrived?

•For /e/OS V, given that LineageOS has shifted development of its version 22 to quarterly updates, moving from 22.1 to 22.2, etc., will adapting QPR updates to V affect its current development?

•Do you have a sheet specifying the requirements for obtaining an official /e/OS?

• Would version 3.0 have a longer development period, like version 2.0 did in 2024?

6

Work on the U or A15 is in full swing. We have an internal telegram channel where I can see the daily updates. But the ETA is not decided as yet.

We are merging the upstream changes into the code base

Usually devices we sell on our Murena Shop are the ones that get the official builds.

It is already under beta testing and yes it may take a little extra time as we are pushing in new features and fixes in it.

3 Likes
7

Here it is: https://gael-duval.medium.com/murena-e-os-2025-another-leap-towards-usable-privacy-for-all-991e5d29db80

5 Likes
8

Read the /e/OS road map for 2025 on the forum.

1 Like