Week 31, 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

Upcoming Release

v3.1

  • revolut fix (for devices with locked bootloader only - revolut requires a locked bootloader to work)
    • with some updates on the revolut side, users on the forum have been commenting the app has started working even on unlocked bootloader devices - community builds. This has not been confirmed from all.
  • Some of the issues and fixes coming in v3.1
  • Second batch of devices on A15 to be released.

ETA : First week of Aug :crossed_fingers:

Current Release

:star2: - /e/OS V or AOSP 15 - We have released the first batch of device builds on A15. The list can be viewed here

  • The rest of the existing and new device builds failed during the compile process. The reason were there were last minute updates in upstream code. We will incorporate the upstream changes and release these builds with the v3.1 release

:warning: Server Outage :warning:

Current Status:

  • 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. Find more details here

    • NextCloud Desktop client works if client synchronization as mentioned below, is enabled.

  • MurenaRecovery folder- The folder is being enabled and made visible for users. We started with premium users and are in the process of enabling and making it visible for all users who were impacted.

    • While waiting for the folders to show up users are advised to back up their device data to avoid overwriting older files with newer files

    • The MurenaRecovery folder will be visible for a couple of months (end date not decided as yet)

    • For more details check out this guide

  • Notes sync with cloud is possible post the v2.9 release. If still not syncing after upgrading to v2.9, take a backup of your local notes before proceeding and enabling Client Synchronization by following these steps.

Client Synchronization
Log in your murena account . In dashboard >> Your profile (top right )>> Settings >> Client Synchronization (left side menu) enable checkbox.

This is to be done only if you want the data on your device and the cloud to be in sync. If you do not want them to be in sync you can keep the check box unchecked.

Backup your existing device data

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

Documentation has been released for the following features

  • Murena Voice to text

  • Murena Vault

  • Find my device

  • Murena Find - replacement of Spot - updates made in the documentation site to replace spot with Find.

  • In Documentation we now refer to the OS version number for example /e/OS V will now be referred as A15. /e/OS U will be A14 and so on. This is to avoid the confusion of tracking version numbers and characters.

Security patch related inputs

An explanation on how we go ahead with the relase of security patches is available here

Upcoming Releases

  • :new: A draft list of devices identified for release with /e/OS A15 has been shared :new:

    • Existing Devices which will get A15 builds

    • New Devices

    • :information_source: Please note these are initial lists. Some devices may not support A15. The lists will be updated in the days to come.

    • We will add or remove device names from this list based on user or build team feedback.

  • Tentative release dates of builds to come in the future.

Ongoing Development Tasks
  • /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

  • Current Version: 29.0.16.4 :new:

  • Changelog
    :point_right: Some users may be seeing message saying that the server software is end of life. This is NextCloud’s way of reminding us to upgrade the software. We are working on upgrading the software as part of these releases. Date of release of the upgrade will be shared.

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)

  • Eligibility:

  • Murena device purchasers.

  • Paid Murena cloud account holders.

  • Active donors from the past year.

  • Please note due to the high volume of requests the helpdesk has a 5-10 day response wait period.

  • Contact: Murena Helpdesk

  • Free Users: Support available via:

  • Forum

  • GitLab

  • Telegram Channels

: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

Do Not Post Test Build Information on the Forum

  • Test builds are untested and may cause device issues.

    • These builds are as yet untested and under development and may in some cases cause user devices to soft brick.

    • Such information can confuse other users who do not see these builds in the updater.

    • Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds

    • If you are genuinely interested in helping with the testing activities and also understand how to fix bugs and are able to do some basic testing on custom ROMS, you are welcome to join the testing team

    • 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

14 Likes
2

Awesome news!
Looking forward to 3.1 (A15)

3 Likes
3

Probably should be *an
(No big deal but if I understand correctly these reports will mostly get copied to the next week, so)

1 Like
4

Is there any way to see what devices will get the official and community updates next? I’m waiting for the a15 official rom for the pixel 8, but the weekly updates are not very clear on the distinction in progress between community and official.

4 Likes
5

Thanks. Have corrected it in the initial post.

1 Like
6

The complete list of existing devices which will get A15 is here

The first set that received the A15 builds is here.

We are working on getting the remaining devices on A15. The problem with releasing a list of ‘this comes next’ is some of the builds will fail. We are trying to build the entire list of devices and release it with v3.1
Will check with the build team if they have the final list of what builds succeeded.

5 Likes
7

Are you aware that an official build to be released, then it needs to be developed to land in the updater of every user with official devices? That is also called ‘OS OTA upgrade’.

In this weekly update there is the section for weekly OS OTA upgrade.

1 Like
8

Sadly FP5 is still to be planned…

2 Likes
9

Yes and I was asking because I could not find what i needed from there.

10

Now you know and understand?

11

Why are you being pedantic? I asked a very basic question after searching for a while and obviously did not get the answer. Acting condescending is not helpful.

12

Manoj responded to your question. mihi was taking time to see if it answered your question. I don’t belive anyone is being condecending. Please also realize that not everyone has English as their primary language.

4 Likes
13

It is just as @Baggypants was writting, I was just checking you have no open questions.

The knowledge of users here varies, there might be follow up questions, just trying to show you can ask more if still no everything is clear.

14

Update:

  • We will be dropping support for A12 or /e/OS S.
  • The official builds of A12 will continue until we move them to A13 or higher OS version ,which would be OTA OS builds where possible.
  • This move is inline with our policy of supporting 3 OS versions at a time.
  • We will be pushing all supported device to higher OS versions where possible.
13 Likes