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

Upcoming release

v3.0.3 :new:
:calendar: Release dates :
:point_right: To be decided

Coming as part of v3.1

  • /e/OS V or AOSP 15 - exact release date will be shared.
  • 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

Current release:
v3.0.2 :new:

  • Release will be available on official builds only
  • Release is specific to some accessibility related updates we have made
  • These accessibility related changes will be made available on community devices as part of v3.1
    Release date : 30 June
    Release note will show up here post release

v 3.0.1
:calendar: Released dates :
:point_right: 11 June Official builds
:point_right: 09 June Community builds

Build feedback and voting
Release notes

  • The v3.0.1 release was required as we got reports of some user devices facing issues post installing v3.0

Documentation released for the following features

Reason for the v3.0 issue and initial resolution

Communication shared on the forum on v3.0

All: With reference to the issue faced by some devices post update to v3.0 as you are aware we have stopped the release.

  • The team has identified the issue and is releasing v3.0.1: the issue is a 3.0 regression from Advanced Privacy for all users who enabled the “Hide my IP” feature with “Always-on” VPN flag.
  • v3.0.1 will go out for all devices, even those that have no issues with v3.0
  • The reason is we want to avoid other devices facing the same bug in the future.
  • It is important that you update to the v3.0.1 to remain in sync with the upcoming releases
  • We shall update when the v3.0.1 release will be published.
  • The v3.0.1 build will need to be sideloaded on the devices when they are published. This is specific to devices which had an issue. For those devices which did not have an issue with v3.0 normal OTA will work.

:point_right: Sideloading will help avoid overwriting existing user data.

  • Also note the v3.0.1 and v3.0 builds had the security patches updated so do not try to downgrade to older version as this can cause issues on the devices.

  • For those who are facing the issue after flashing v3.0 we have a workaround. Please be warned that it might not work for all the devices. The steps are as under:

    • please read all the steps carefully before starting
    • connect your phone via USB to a PC
    • When you arrive on the recovery mode with the error tap “Try again”
    • Disconnect the USB cable
    • Wait for SIM pin request
    • Type your PIN code and validate
    • Reconnect the USB cable
    • Unlock your screen
    • Quickly go to Settings > Network and Internet > VPN > gear icon next to Advanced Privacy > - Always on VPN
    • Tap to disable “Always on”
    • Tap on “Forget VPN” at the bottom of the screen and “Forget” in the dialog which opens
    • Disable “Hide my IP” in the Advanced Privacy widget
A step by step guide to install v3.0.1 on impacted devices
  • For those impacted by the v3.0 issues a post was shared on the forum with steps on how to flash the v3.0.1 build

: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 will then enable and make 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)

    • Should start showing up for all users free and premium

    • For more details check out this guide

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


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.

    :calendar: ETA for release of /e/OS V or AOSP 15 will be June.

  • 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

10 Likes

Hello Manoj
Do you have any news about the progress of the tests on oneplus nord? Is it favorable ?

1 Like

Is it correct that v3.0.2 is available only for official builds on AOSP14 and AOSP15, @Manoj ? For example, FP5 won’t receive this update.

I have the same question for Samsung Galaxy S7 HeroLte. and S7 Egde Hero2Lte

Hello AnotherElk !

The point of the question is to know if the only official builds will be on A14 and A15 and not on previous android version like s or t.

A better wording could have been :

Is it correct that v3.0.2 is available for official builds only on AOSP14 and AOSP15

2 Likes

The v3.0.2 build for FP5 has been released. It has been released on the U or A14 build.

1 Like

The command line instructions for the Pixel 7a state;

If the phone is on Google Android 15 do I have to downgrade to Android 14 before installing the Android 15 version of /e/os?

The release notes say so, yes: “/e/OS 3.0.2 version for Official devices on AOSP 14 or AOSP 15”

On Thursday, July 3 there will be a 2h maintenance on Murena Workspace, from 3:30 to 5:30 UTC (05:30 to 07:30 CEST).

We will deploy a new release based on the latest Nextcloud 29 image, which includes performance improvements, bug fixes and security patches. We will also release the Forms app for all users and take it out of the beta program.

We hope the new version pleases you and overcomes the inconvenience of this service disruption.

The Murena team

Update: This activity has been completed and all systems restored.

1 Like

In keeping with the request of a large number of users we will be switching to OS version numbers in our documentation . For example in place of /e/OS V it would display A15 . This may already be visible for the FP6. With the release of the A15 builds (expected later this month) the OS version will display the OS version number for all devices.

7 Likes

All: murena workspace is up post the maintenance update. It has now been upgraded to nextcloud-29.

-Note: passwords app is still disable. It is being updated in the background & it takes time to update. We expecting it to be enabled again in next 2-3 hours

Will update on the progress.

2 Likes

Hi @Manoj,

Perhaps this is planned, but would it be possible to develop unlocking like FaceID ?

Thanks

Since here only the A14 build is present with v3.0.2, does this mean that the OS OTA for FP5 (and FP3?) has been cancelled?

Or is this something we can still wait for:

Not cancelled. The efforts are ongoing. In case it is not possible I will update here. It takes time as the team had some big tasks on hand - release of v3.0 and working on the many features. Besides the A15 release is also due.

3 Likes

Thank you for the clarification. In the meantime, are there updates for the T (A13) build to be expected?

Update: We will release a v3.0.3 for both official and community builds.

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

We felt it was important to address these immediately instead of waiting for the v3.1 release which may take a couple of more days to complete.

To summarize :

  • Next release for official and community devices is v3.0.3
  • Community devices which did not get v3.0.2 will directly move from v3.0.1 to v3.0.3
  • Official devices will move from v3.0.2 to v3.0.3
  • The v3.0.3 release has the security fix for the two issues mentioned above.
  • ETA for release of v3.0.3 will be announced ASAP
7 Likes

For the Fairphone 5, version 3.0.2 is only compatible with Android 14. Will devices still running Android 13 have to wait for the OTA update to Android 14 to receive this security patch, or will a 3.0.3-t update be provided in the meantime?

2 Likes

Hi Manoj, just a quick: in January you wrote that the Gigaset GS290 will get an upgrade (it is still on S (A12) now), ), [Week 4, 2025: Development and Testing Updates - #22 by Manoj].
Now that A12 is not supported with security updates anymore: can you say when the GS290 will be upgraded to a newer Android version?
B.t. under “OS OTA Information” under “Completed” the Gigaset GS290 is still listed with" Q (A10) → R (A11)", actually it is officially on R (A11) → S (A12)
Best, T.
I asked this about a month ago, but then the 3.0.1 issue kicked in:

3 Likes

Not sure if it is as intended at the moment but FP6 is missing community build. Any time frame for it?