Week 25, Development and Testing Updates

:mobile_phone: /e/OS Weekly Development and Testing Activities

  • Summary of weekly development and testing activities by /e/OS developers and volunteers.

  • Updated content is marked with the :new_button: emoji.


Release Updates

Current release v4.0 :new_button:

Staggered release 11 June 2026 - 22 June

  • This is a major release.

    • Which means that in addition to bug fixes and optimization, this release will include new features that enhance /e/OS and Murena services. Some of the features that come with v4.0 are
  • Feedback and Voting

  • Release notes

What is a staggered release

Please note the v4.0 release is a staggered release like all our releases.

Which means every day a small set of devices are released. The reason we do our releases in this manner, is we support 250+ devices.

If we release all builds at the same time the servers will crash as we will have thousands if not millions of simultaneous hits on the servers.

Official builds usually get released during the last days of the release process.

The release process usually takes about 7 to 10 days. For example, for v4.0 we started the release on 11 June and it will complete for all devices around 22 June.

Upcoming Milestones

:information_source: Releases planned in the future are marked as milestones in gitlab


Roadmap for 2026

:loudspeaker: Check out Gaël’s article on the roadmap for /e/OS and Murena in 2026


Murena Account Recovery Email

Ensure your Murena Workspace account (e.email or murena.io ) has a recovery email set.

  • New Accounts without a recovery email will face reduced functionality for 30 days and post that will be marked for deletion.
  • The process will be the same for existing accounts without a recovery email

:backhand_index_pointing_right: To check if your Murena account has a recovery email click here

  • Link will require you to log in to your Murena workspace.
  • In case your account is disabled, you can contact me - @Manoj on this forum and I can assist with getting the account re enabled.

Documentation

:open_book: Details on device app compatibility will be displayed in the supported device table :new_button:

:backhand_index_pointing_right: Build type word in the documentation will be changed to Release Type

:backhand_index_pointing_right: Build variants will be visible in the supported device table - basically there are two build variants -user and userdebug.

  • A simple explanation of what they mean would be available when user hovers the cursor on the terms.

:open_book: We are working on updating our documentation site.

  • Besides making navigation easier the plan is to make user contribution easier.
  • Currently under planning stage, will share details once there is any progress on it.

:bug: Want to report an issue in /e/OS.


:locked: Security Information

:shield: Security Patch Release Process explained here

  • We will be sharing a detailed document about our security policy.

:bar_chart: Previous Releases & User Feedback

4.0

3.7 / 3.7.1 / 3.7.2 / 3.7.3

3.6

Older Releases


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 32.0.6.11

Resources:

:clipboard: [Release Notes]( v32.0.6.11 · e / infra / ecloud / nextcloud · GitLab)

:house: Self-Hosting

Current Version: v26.0.8.23

Resources:

:clipboard: Release Notes

:open_book: Upgrade Guide

Status:

:memo: Self-hosting guide update pending

🔍 How to Check NextCloud Version

Method 1: Murena Settings

Go to Murena Settings

Look for “NextCloud xx user documentation”

Method 2: NextCloud Scan

Visit NextCloud scan link

Input https://murena.io

:information_source: Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad. This is normal - patches are tested before deployment.


:mobile_phone: GSI (Generic System Image)

Current Version: /e/OS A10 v1.17

Resources:

:inbox_tray: Download

:open_file_folder: Sources

Next Version: /e/OS T (A13) - skipping A11 and A12

:date: Release dates to be announced


:counterclockwise_arrows_button: OS OTA Information

:white_check_mark: Completed

  • :mobile_phone: OnePlus - Nord - avicii - A12 → A16

  • :mobile_phone: Teracube -2e - zirconia - A12 → A15

  • :mobile_phone: FP5 - Fairphone: A13 → A15

  • :mobile_phone: FP5 - Fairphone: A14 → A15

  • :mobile_phone: FP4 - Fairphone : A12 → A13

  • :mobile_phone: S9/9+ - Samsung : A11 → A12

  • :mobile_phone: GS290 - Gigaset : A11 → A12

  • :mobile_phone: GS290 - Gigaset : A10 → A11

  • :mobile_phone: FP3 - Fairphone : A12 → A13

  • :mobile_phone: S7/7+ - Samsung : A11 → A12

  • :mobile_phone: FP4 - Fairphone : A13 → A14

  • :mobile_phone: S8/8+ - Samsung : A11 → A12

:information_source: Note: OTA upgrades are for official or stable builds only

:test_tube: Under Development and Testing

  • :mobile_phone: FP4 - FP4 - A14 → A16
  • :mobile_phone: FP6 - FP6 - A15 → A16
  • :mobile_phone: FP5 - FP5 - A15 → A16
  • :mobile_phone: FP3 - FP3 - A13 → A15 (v4.0) :crossed_fingers:
  • :mobile_phone: OnePlus - nord - avicii - A14 - A16 (v4.0 :crossed_fingers: )
  • :mobile_phone: Galaxy S9* - A12 → A15 :crossed_fingers:
  • :mobile_phone: GS290* - A12 → A15 (v4.1) :crossed_fingers:

:backhand_index_pointing_right: All official builds are candidates for upgrade to A16 or the next OS for which build is possible.

:clipboard: To Be Planned :new_button:

  • :mobile_phone: Google Pixel tablet - tangorpro - A14 → A15

  • :mobile_phone: Murena One - A12 → A15

  • :mobile_phone: Galaxy S8* - A12 → A15

  • :mobile_phone: Galaxy S7* - A12 → A15

(Devices marked with an ‘*’ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)

:backhand_index_pointing_right: Check the section titled A16 Updates below

📖 What is OS OTA Upgrade?

Traditional Process:

:inbox_tray: Download correct OS build from supported device list

:inbox_tray: Download stock ROM from vendor site (for some devices)

:floppy_disk: Back up your data

:counterclockwise_arrows_button: Install stock ROM, then /e/OS ROM

:counterclockwise_arrows_button: Restore backups if needed

OTA Benefits:

:white_check_mark: Simplifies the entire process

:warning: Requires significant development and testing


:speaker_high_volume: A16 Updates :speaker_high_volume: :new_button:

  • We plan to update all devices currently on A12, A13, A14 and A15 to A16 :speaker_high_volume:

  • In case any device is not able of handling the A16 builds we will share that information.

  • The team expects that A16 would not be buildable or installable on some of the older gen devices like the Samsung S7 or S8. There could be more.

    • For such devices we we will work on getting them to the highest OS version possible.
  • As you may be aware A12 does not receive security patches anymore. This will next impact A13 and so on. This is a standard Google policy to end of life (EOL) older Android versions.

  • All devices we sell in our shop, with official builds are priority candidates for OTA OS upgrade to A16.

    • Official builds get OTA OS upgrades.
    • Community devices require manual upgrade.

    (Ideally in all cases, take backups while upgrading the OS of your device)


:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status

:mobile_phone: /e/OS Real-Time Status

New Gitlab account creation

  • If you are trying to create a new /e/OS Gitlab ID and facing issues with the email ID, you can try and create a Murena Workspace ID and use it to log into Gitlab. Check the updated documentation here

🎫 Helpdesk Services

:white_check_mark: For Paying Murena Customers

:mobile_phone: Murena device purchasers

:cloud: Paid Murena cloud account holders

:heart_with_ribbon: Active donors from the past year

:alarm_clock: Response Time

:hourglass_not_done: 5-10 day response wait period due to high volume of requests.

:telephone_receiver: Contact

:ticket: Murena Helpdesk Contact Form

:free_button: For Free Users

:speech_balloon: Forum

:bug: GitLab Issues

:mobile_phone: Telegram Channels

:warning: Warning: Old helpdesk email IDs are no longer monitored.

📱 Device and Vendor Announcements

:mobile_phone: Gigaset GS290

:stop_sign: Sales stopped (vendor ceased production)

:white_check_mark: Support continues for existing users

:mobile_phone: Murena One

:stop_sign: Sales stopped

:white_check_mark: Support continues for existing users

:mobile_phone: Murena Two

:stop_sign: Sales stopped

:white_check_mark: Support continues for existing users

:shopping_cart: Pre-Flashed Devices

:globe_showing_europe_africa: Available in EU, US, Canada, and Australia. Check the complete list on the Murena shop

:shopping_cart: Purchase via Murena Shop

🌐 /e/OS Website and Social Media Links

:globe_with_meridians: Official Websites

:house: Murena

:mobile_phone: /e/OS Website

:books: Documentation

:bug: Report Bugs

:open_book: How to Report Bugs

:mobile_phone: Telegram Channels

:speech_balloon: Available Channels

:mobile_phone: Social Media

:mobile_phone: XDA

:bird: X

:elephant: Mastodon

:briefcase: LinkedIn

:memo: Medium

:e_mail: Newsletters

:newspaper: eFoundation News

:tada: Murena Promotions

:bank: To send in your Donations : Use the email ID donation@murena.io


:warning: Important Notice

:prohibited: Do Not Post Test Build Information on the Forum

Why this is important:

:warning: Test builds are untested and may cause device issues

:fire: These builds can potentially soft brick user devices

:thinking: Such information can confuse other users who don’t see these builds in the updater

:busts_in_silhouette: Not all forum users are experts in custom ROM installation

For Interested Testers:

:test_tube: If you understand custom ROMs and can perform basic testing

:busts_in_silhouette: Join the testing team

:speech_balloon: Share feedback on the dedicated Telegram channel

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

12 Likes

starting with version 3.7.1, I had many crashes of some apps. Mostly in the background (reports via LogFox). Affected Apps are Breeze, Meine Barmer, Podcini, Amber, Netguard, Signal and Huawei AppGallery (many crahes recently for the last 2 Apps),

Update on the S9/S9+ :
While we are pushing the A15 official build for this device want users to know that the USB type C display output/HDMI will not work in A15 for Samsung galaxy S9 series
We will add this information in the device install guides.

1 Like

thanks for the update @Manoj :slight_smile:
regarding the 3 devices that are marked with a potential OTA update in v4.0, I’m just wondering (since the release should already have happened) whether it is still a possibility or if we’ll have to wait for the next one.

I see FP3 in the release notes of A15, so I imagine this one is done, but not the others.

As part of v4.0 both GS290 and S9/9+ upgrade builds are scheduled for release.

1 Like

OK, so FP3, GS290 and S9/9+ A12 → A15 OTA upgrades should be included, but not the A14 → A16 for avicii, is that right?

Avicii also gets the A16 upgrade.
Do you own all three devices.

Ah, great! I don’t own them but I manage several :wink:

An update on some of the older devices that we plan to or have been working on. These devices are still stuck on A12 or A13.

  • Once we have upgrade builds for these devices, we will discontinue A12 / A13 OS support across /e/OS
  • If possible, we will even target A16 for some of these devices.
  • If any of the devices marked to be started fail the upgrade process we will share the information on this forum.
Vendor Name codename Current OS Target OS Status
Gigaset GS290 GS290 A12 A15 Release pending
Google Pixel 5 redfin A13 A15 To be started
Murena Murena one A12 A15 Under Development
Murena Murena two A13 A15 To be started
Samsung Galaxy S8 dreamlte A12 A15 To be started
Samsung Galaxy S8+ dream2lte A12 A15 To be started
Samsung Galaxy S7 herolte A12 A15 To be started
Samsung Galaxy S7+ hero2lte A12 A15 To be started
4 Likes

What does “to be started” mean? You will start develop the upgrade? A12 means they are EOL for 15 months now…

We will start to build the ROM on A15. We do release builds for all these devices with backported security patches, where available on older OS version.

The following devices will not receive v4.0 as their builds have failed. The team will try to rebuild them but if the attempts fail then they will be released with v4.1
The builds failed due to code coming in at the last minute from upstream sources.

Vendor DeviceName CodeName OS versions
Motorola moto g200 5G xpeng A15,A14
Motorola edge 20 berlin A15,A14
Motorola edge 2021 berlna A15,A14
Motorola edge 30 dubai A15,A14
Nubia Mini 5G TP1803 A14
Xiaomi Redmi Note 10S rosemary A15
1 Like

hey, thanks for the amazing work as always.

I am not receiving the update on my FP5 A15 official build. Usually spamming the refresh button does the trick but it has been days and I still don’t get offered to upgrade. Is this normal?

Yes because the 4.0 version of /e/OS has not yet been released for the FP5 : /e/OS official FP5 download

1 Like

Official builds usually roll out the last in a release cycle. We start with the community build channel and then move on to the official builds.

3 Likes

Out of curiosity, is the team possibly making any fix between the release of community builds and the release of official builds?

Only asking because the random reboots are still occurring on 4.0 community on FP6 under low signal.conditions and I would like to know where is the best place and time to report that.

We have an issue open on gitlab since v3.1.3 . The issue started as one showing up when user travelled across countries.
Suggest you add your comments to it. The issue did not see any comments since last month. Pl mention that you are on v4.0 and the community build.
Where are you facing this issue …in the US? A general idea of the location is enough do not need specifics.

Canada. It occurs in various provinces of the country. It happens while stationary.

Please add this to the issue. I just discussed with the developer.

Why, after I updated cmf prone 1 to /e/os 4.0, I still have android 14 and not 16?

1 Like