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

:star: v3.0.4 :new:
:calendar: Release dates : This week :crossed_fingers:

Feed back and Poll

Release note will show up here post release

  • 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 will be sent 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

:star: Release after v3.0.4
v 3.1 :crossed_fingers:

What will come with 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

  • Release was 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

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

    :calendar: ETA for release of /e/OS V or AOSP 15 will be along with v3.1

  • 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

16 Likes
2

I am on /e/OS 3.0.1-t-20250606498724-official-FP3, however, v3.0.2 never showed. Do I need to worry?

3

Hey,
try to refresh a couple of times. Most of the times it works after 5-7 times of refresh.

4

There is an update in the version number that will come next. Please check the initial post in this thread for details of the v3.0.4 and what will come as part of it to each build.

2 Likes
5

Thanks @kipry - I am aware of this ‘trick’ - still no update.

6

Okay, thanks, got it now :slight_smile: There never was 3.0.2 for A13.

2 Likes
7

Can you please clarify on official herolte (Android 12)?
As there is still no 3.02, I assume it will be 3.01 → 3.04 directly, is that correct?

1 Like
8

Yes A12 or /e/OS S device builds which did not get v3.0.2 will directly go to v3.0.4

1 Like
9

Is there any news on the FP5 OTA to AOSP14? Any manual (official) OTA images keep failing to install via Updater or Recovery and the 60/90Hz bug is getting annoying…

2 Likes
10

Hey, this is something what I also like to know too! I am on Version 3.0.1-t on my recently bought Fairphone 5 and saw that now there is only Android 14 available online, while I am still stuck on Android 13. Would be nice to have Android 14 ^^.
But besides that, I think its amazing that we got a Dev Update every week! Love to read them as a huge tec nerd XD. It was the right choice to move to e /os (even if Curve doesnt work with my debit card yet, but thats a minor issue).

1 Like
11

if you search for “voice to text” in doc.e.foundation you can’t get a hit on the posted articles.

that elasticsearch doing the search field in the doc pages should be made to 1. index the new page I gess and 2. boost exact string matches

1 Like
12

The optimization of the search on the doc site is a feedback we have on our task list.

5 Likes
13

What a mess. I didn’t update my FP5 from 2.9-t official because of all the people who reported issues with the update. Now I see that there is a 3.0.1-t, but also a 3.0.4 coming up, and also a 3.0.2-a14 that I cannot update to because there still is no OTA. And in this chaos of updates, bug reports, bricked phones, android versions… there is little info, because there is chaos around a useless feature that sends people’s biometric data to openAI. I miss Google’s Android.

14

I understand what you mean. I am confident that the issues will be solved. Always remember, there was a reason in the first place why you took the more complicated step. Go the normal path. If 3.0.4 is available for you, you should be fine with an update. Prepare a backup of your data before you do.

1 Like
15

So for the murena fp6, there will be an OTA Update soon?

16

Just in case you really do … https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone

(Edit: FP6 users reading this … for now, don’t!)

2 Likes
17

Thanks, as usual helpful stuff you point out here.

Hopefully they will soon release community build, feels strange having official installed without locking bootloader…

18

Hi. My FP5 is on 3.01-t-20250606498724-official-FP5. When in developer options ‘connect to /e/ OS test channel’ is disabled, there is no updates available under ;Updater’, if enabled there are two updates ‘3.0.4’ and 3.0.4-beta’. As I understand versions on the test channel may not stable, which is why I’m hesitant to apply an update from there. On the other hand from the information here I understand that v3.0.4 is official and hence stable? Can I expect that it is showing in the Updater even when ‘connect to /e/ OS test channel’ is disabled? Thanks.

20

You have official, more patience is needed, allways. The idea is to find bugs in thet time and prevent from getting to you

1 Like
21

I really would not do this unless you want to be actually testing. Maybe counter intuitive but Testing stable / official is a more robust level of testing to see that official could be ok to publish.

I will not contradict you but do you know this? The installer traditionally would “hold back” from the very latest published ROM at least for a few days.

1 Like