Week 24, 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.


Roadmap for 2025

Release

v3.0.1

Current Status:

:calendar: Release dates : Updated
:point_right: 11 June Official builds
:point_right: 09 June Community builds

  • The release will be staggered to avoid issues.

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
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 till the end of June.

    • 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

  • 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


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

Glad to hear y’all are fixing the issues with 3.0. I’m still on 2.9 because I saw the issues with devices stuck in recovery and chose not to update. Will we be able to use OTA to go directly from 2.9 to 3.0.1?

It seemed like it probably will from the post, but I’d like to be sure.

For the moment, I advise you to stay with version 2.9, since 3.0 and 3.0.1, I have encountered major problems.

1 Like

Read Gaël’s reasoning for using OpenAI for the speech to Text feature.

2 Likes

There is currently no OTA upgrade available for official devices as FP3 and FP4.

Did you mean this?

There is no OTA Upgrade planned with 3.0 not even avicii was considered I guess since 3.0 brought more features, etc. than usual

There is an update in the release dates for v3.0.1 it will be staggered and as per these dates.

:point_right: 11 June Official builds
:point_right: 09 June Community builds

2 Likes

The dates have been updated

:point_right: 11 June Official builds
:point_right: 09 June Community builds

3 Likes

Hello Manoj,

A quick update on the Find My Device feature. It doesn’t work with two SIMs, and there’s no SIM preference.
You’d need to assign a SIM for sending in the option’s settings.
More generally, for dual SIM use, it would be good to be able to assign a SIM to be used in the Contacts app for each number. This is an option available on other apps, and it’s very useful.

2 Likes

Hi Manoj, I see that version 3.0 has greatly improved performance. My question is, will this same version 3.0.X release the V branch or will /e/OS V go up to version 3.1? Will there be a test session like there was with U, which released an alpha in November 2024? Will there be a V test session?

is it just me, or has the POCO x3 Pro been removed from the list of compatible phones?

1 Like

The poco x3 has not been removed from the list of compatible phones. It has received the v3.0.1 build. If a device is to be removed from the supported list we would inform users on the forum.

could online find the NFC version in the list, so i asked. Thank you.

I still don’t have the MurenaRecovery folder in my Files! And I just noticed that

The MurenaRecovery folder will be visible till the end of June.

What do I do? Thanks.

The process has till end of this month to complete. I will message you for your account details.

Update:
I checked with the team and it should take about 1-2 weeks for the MurenaRecovery folders to appear for all free accounts

4 Likes

v3.0.1 official builds rollout has started. Again it will be staggered across the devices. Which means not all official builds will be released at once.

5 Likes

I saw v3.0.1 show up as an OTA update yesterday on my Google Pixel 5 (redfin), but today it’s gone again. Did it have to be retracted too?

Just refresh with the button a couple of times, like 5 then you might get surprised

1 Like

No way :astonished: After spamming the update button exactly 5 times, the update appeared again. Seems like sometimes, violence is the answer…

Thanks for the tip!

No violence just how it is defined to work. This way not every person gets the update and like you experienced sometimes it goes away again.

1 Like