Week 29, 2025: Development and Testing Updates

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

Current Release

:star: v3.0.4 :new:
:calendar: Release dates : Release initiated

Feed back and Poll

Release notes

  • Release is specifically to handle a 0 day exploit in browser which was revealed a couple of days back.
    • Check this video for details. (Please note this video is on Youtube)
    • Details of another issue also reported can be read here

We felt it was important to address these issues immediately instead of waiting for the v3.1 development and testing to complete, which could take a couple of days more to complete.

:point_right: About v3.0.4

  • Release goes out to both official and community devices

  • Community devices that did not get v3.0.2 will directly move from v3.0.1 to v3.0.4

  • Official devices will move from v3.0.2 to v3.0.4

  • A 13 Official/Community will move 3.0.1 to 3.0.4 this includes June security patch and browser update and accessibility related updates

  • A 14/15 Community move from 3.0.1 to 3.0.4 includes June security patch, browser update and accessibility related updates

  • A 14/15 Official builds move from 3.0.2 to 3.0.4 contains June security patch and Browser updates

:star2: - /e/OS V or AOSP 15 - We are checking if the A15 builds can be released with v3.0.4

:star: Release coming after v3.0.4

v 3.1 :crossed_fingers:

What will come with v3.1

  • revolut fix (for devices with locked bootloader only - revolut requires a locked bootloader to work)
  • Will share link to issues and fixes coming in v3.1

:warning: Server Outage :warning:

Current Status:

  • Email: Send receive 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. 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.

Compensation for outage impacted users: Impacted paying users should have started getting emails with details on getting compensation for the service outage duration.


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

Upcoming Releases

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

    • Existing Devices which will get am /e/OS V build

    • New Devices

    • :information_source: Please note these are initial lists. Some devices may not support AOSP 15 or /e/OS V. 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

@Manoj

I installed e-3.0.4-a14-20250709507533-community-FP3 three days ago. Is it safe to upgrade to e-3.0.4-a15-20250713508366-community-FP3 (which has become available in the meantime, see below) from there?

From https://ota.ecloud.global/community/FP3/:

grafik

UPDATE: I jumped the gun, evaded deserved punishment.

6 Likes

Yes. As mentioned in the initial post. We are targeting to release A15 along with v3.0.4
No point waiting for v3.1 as the A15 builds were already available.

3 Likes

starlte’s last official release was v3.0.1-s, i.e. there wasn’t a v3.0.2-s. Will it get a v3.0.4-s release or a v3.0.4-t release or has it been decided to not support it any longer ?

I just UPGRADED my beyond2lte from

Android 14
e-2.8-a14-20250220470208-community-beyond2lte

to

Android 15
e-3.0.4-a15-20250713508366-community-beyond2lte

Works. No issues so far.

3 Likes

I just did that via local update on a pixel 4a :+1:

edit: and with Tab S5e (SM-T725)

1 Like

Hello,

I also have a FP3 with 3.0.4-community installed. But in my case, my bootloader is locked (because relocking on community builds was permitted few versions before). Was your bootloader also locked when you did the upgrade to a15 ? Do you think it is possible ? Did you just sideloaded the a15 build or you did a clean install ?

Thanks in advance !

Sideload. My data, settings and apps were carried over. As to the bootloader question, I helped a local Fairphone 3 user (who permanently rents the phone from Commown) to upgrade his FP3 from Android 10 (stable) to Android 13 (official) last week. We did not need to change the bootloader status (it was locked) to upgrade from 10 to 11 and from 12 to 13 (via ADB sideload; the upgrade from 11 to 12 was possible through the Updater).

2 Likes

Thanks for your info.
I couldn’t (dirty) upgrade my Fairphone 3 (a14 → a15) via sideloading, because i’m missing out on updating the recovery. I can’t find any recovery image. Would be wonderful, if you are inclined to share how you’ve upgraded your FP3. :upside_down_face: Thank you very much!

Well, I don’t know from what versions you are starting :thinking:

Anyway, just a few ideas that might be relevant:

  • I never updated the recovery separately, only ever as a “by-product” in the course of a general update/upgrade.
  • I had updated OTA to 3.0.4-a14-community first, then (dirty upgrade, ADB sideload) to 3.0.4-a15-community
  • the file you need begins “e-3.0.4-a15…”, not “IMG-e-3.0.4…” (you need to edit the URL before the download)
2 Likes

Thanks for your time and effort! Appreciate it.
Sorry, I was a bit sparse with my Infos. I’ve managed now to (dirty) upgrade from 3.0.4 (a14) to 3.0.4 (a15). Fairphone 3 community.

This Hint made the difference for me. :point_down:

After altering the URL and erasing the “IMG” part, i was able to perform sideloading without any hiccups. I used this thread as guidance. No need top update the recovery.
Nice to have such a helpfull community.

2 Likes

Glad to have spared the good @piero the job at least once :grinning:

2 Likes

I done the upgrade from a14 to a15 successfully as I reported here : Feedback for v3.0.4 - #48 by Mamalo

adb sideload with OTA package downloaded as described below worked perfectly without issues during the update.

2 Likes

Be advise if you’re on FP3 official, the update to 3.0.4 will NOT upgrade you to A15, but you will remain on A13…

Yeah, I’m on an FP5, was on 3.0.1-t-xxx now running 3.0.4-t-xxx; if I’m reading the thread correctly, android 15 will be rolled out for the official OTAs with 3.1 and the 3.0.4 with A15 is for community / side load /“dirty” updates? I do find it difficult to follow how the builds break down.

1 Like

There is a difference between builds made available on the download pages for manual install and Android version upgrades being distributed OTA (via the updater).

While OTA updates within the same Android version are arriving regularly via the updater (until /e/OS support for the Android version on the device in question ends somewhen), and while /e/OS builds based on a new Android version might already get published on the download pages for manual install, OTA upgrades to a new Android version via the updater are being specially prepared and tested by the developers per device and per upgrade step before they are being made available (because the in-place upgrade process is tricky and it needs to be made sure that ideally it will successfully complete for most users of the device in question).

As long as an OTA upgrade to a new Android version isn’t available for your device, /e/OS updates via the updater will stay within the same Android version.
Please see the first post of these weekly development updates, section OS OTA Information, to follow progress on this …

… meaning as of now an OTA upgrade to Android 15 via the updater is not in actual sight yet for the Fairphone 5.

3 Likes