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

Current Status:

:calendar: Release date : 3rd June :new:

9f0d3f1083d9b12ad26f4e282461932c57e750ff_2_690x361

:loud_sound: For complete details of what will be coming as part of the v3.0 release tune into the presentation…read more

:information_source: You can add your queries regarding v3.0 to the post linked above. The team will be answering them during the presentation.

:point_right: Audio video recordings of the presentation would be available for viewing later.

:point_right: Build Feedback and voting

:point_right: Release notes will show up here once the release is initiated

  • As you may have read in the roadmap linked above, some new features are proposed. While the team is working on finishing most of the topics in time for the release, Pl note some of the tasks may require more development and testing efforts.

  • Features like MDM may already be showing up in the OS. These features will be removed/ disabled by default / greyed out and will not work even if activated as there is still work to be done on them.

    • We will share details of these upcoming features on our documentation site. Some of these features like MDM are more relevant to corporate users and are not exactly for the average user.
  • Build code would show up as v2.10 and may be renamed to v3.0 based on the decision to go ahead by the development team.

  • :information_source: Some 2025 roadmap features will be developed in private repositories to prevent sharing unstable code with unresolved bugs. Once development and testing are complete, the code will be publicly released. :information_source:

  • The build for these devices failed during the beta release testing

     Samsung Galaxy S10 beyond1lte
     Samsung Galaxy S10+ beyond2lte
     Samsung Galaxy S10 5G beyondx
     Samsung Galaxy Note10 d1
     Samsung Galaxy Note10 5G d1x
     Samsung Galaxy Note10+ d2s
     Samsung Galaxy Note10+ 5G d2x
     Samsung Galaxy F62 f62
     Samsung Galaxy Tab S6 Lite gta4xl
     Xiaomi POCO X3 NFC surya
    

    While we will try to get the build working again it might not be possible to fix it before the v3.0 release. The team will work on resolving the issues on these device builds and publish these with future releases.

: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 th 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

16 Likes

The update for Samsung Galaxy S10+ beyond2lte works well

e_beyond2lte-user 13 TQ3A.230901.001 eng.root.20250531.215020

Only the update of 2.8 to 3.0 for the verdion 14 (U) is not working at the momement.

@Manoj, I think this is an important information for many. I assume that most will run eOS on 13 (T).

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 kicked to a newer Android version?
Best, T.

We have temporarily stopped the roll out of v3.0 builds as some device users have complained of issues with the builds.
As you may be aware devices like FP5 users have had issues post the release.

Will update on the release resumption and progress on the issue resolution.

5 Likes

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

  1. please read all the steps carefully before starting
  2. connect your phone via USB to a PC
  3. When you arrive on the recovery mode with the error tap “Try again”
  4. Disconnect the USB cable
  5. Wait for SIM pin request
  6. Type your PIN code and validate
  7. Reconnect the USB cable
  8. Unlock your screen
  9. Quickly go to Settings > Network and Internet > VPN > gear icon next to Advanced Privacy > Always on VPN
  10. Tap to disable “Always on”
  11. Tap on “Forget VPN” at the bottom of the screen and “Forget” in the dialog which opens
  12. Disable “Hide my IP” in the Advanced Privacy widget

Attaching a video ( sorry it is in french ) of these steps Murena

6 Likes

Thanks a lot! If we are still on version 2.9 can we update directly to 3.0.1 (when the build will be published of course)?

We are working on releasing v3.0.1 official builds later today. :crossed_fingers:

The team has shared a step by step guide on how to flash the builds in feedback thread.

v3.0.1 community builds would be coming out on Monday.

2 Likes