Week 30, 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.1.1 :new_button:

What is a staggered release

Please note that all /e/OS releases are staggered releases.

Which means, during the release days, 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.

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

:backhand_index_pointing_right: Check out the new look Documentation site. :new_button:
:backhand_index_pointing_right: Now anyone with a /e/OS Gitlab account can edit the Documentation site. Your changes will be posted as a Merge Request and post a review and approval will get published. :new_button:
:backhand_index_pointing_right: Devices with official builds will not have community builds showing up in the installation guides.

  • The community versions of the devices we sell or sold has been removed from the documentation.

  • We would prefer users to eventually shift to the official builds. That way the maintenance of the devices is easier and more efficient.

  • For now the community builds are being built and can be access by adding community to the device image download link replacing official. For example: /e/OS community starlte download

    :open_book: v4.0 release included new features that enhance /e/OS and Murena services. Some of the features that come with v4.0 are

    • Murena Passwords
    • Murena Sign
      • Currently compliant with SES only. We are working on AES.
    • Murena Meet
    • Murena Vault
    • Backup
    • Google data migration
      :backhand_index_pointing_right: Documentation on all the new features being updated and modified based on feedback from user and testing teams.
      :backhand_index_pointing_right: Please note some of these features are in the beta phase. Additional development, detailed testing and improvement are in progress. We look forward to your comments and feedback on these features.

:open_book: Details on device app compatibility is now 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.

: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: Curent and Previous Releases and User Feedback


: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: FP3 - FP3 - A13 → A15

  • :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: OnePlus - nord - avicii - A14 - A16
  • :mobile_phone: Galaxy S9* - A12 → A15 :crossed_finger :crossed_fingers:
  • :mobile_phone: GS290* - A12 → A15 (v4.1.1) :crossed_fingers :crossed_fingers:
  • :mobile_phone: Teracube - emerald - A15 → A16
  • :mobile_phone: Teracube - sapphire - A14 → A16
  • :mobile_phone: Teracube - zirconia - A15 → A16
  • :mobile_phone: Murena One - A12 → A16

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

:backhand_index_pointing_right: A device with an official build name if not mentioned in this list does not mean the device has been abandoned. We continue efforts to build for all official devices we ever sold on the Murena Store. Dates of release of these builds will be shared when available.

:clipboard: To Be Planned :new_button:

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

  • :mobile_phone: Galaxy S8* - A12 → A15

  • :mobile_phone: Galaxy S7* - A12 → A15

  • :mobile_phone: Nothing - CMF Phone1 - A12 → A16 / A15 :crossed_fingers:

  • :mobile_phone: Murena Two - A13 → A16

(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

15 Likes

Hello @Manoj,
I am looking forward to release 4.1.

I have made an observation regarding push.murena.com: I sometimes get a 502 error when accessing the URL of a topic channel. This may be the reason that e.g. my Molly messages sometimes arrive only if I open the app. [1] I also sometimes get an error with UP-Example for the same reason. [2]
These 502 errors have appeared several times during the last week.

Could you ask the infrastructure team whether there are currently some problems with push.murena.com, e.g. during the evening, when there may be a larger workload?
If possible, I would also suggest to update the nginx installation that is used as a reverse proxy because it is a legacy version. [3]

[1] I am using mollysocket.yourdevice.ch as Molly Socket server, which reliably works.
[2] I use version 2.2.0 because newer versions do not recognize foundation.e.ntfy, as noted in the backlog.
[3] The 502 error page is a default error page from the nginx installation and includes the server version. While “security by obscurity” is not generally a good idea, I have also read that web servers should not expose their respective version, which includes the server header in the response. On the other hand, I could not write this if the version were not shown. :thinking:

I have passed the comment to the developers. Will get back with their response.

1 Like

This is a list of all devices with official builds. The plan is to upgrade them to the OS version mentioned. For most of them the development is in progress or testing phase.
Will share ETAs once they are available.

The older devices like the S7/7+ or S8/8+ may not get upgrades as the devices have reached their EOL as per date sold.

Vendor Name CodeName Current OS Upgrade OS
Fairphone FP6 FP6 A15 A15 to A16
Fairphone FP4 FP4 A14 A14 to A16
Fairphone FP3/3+ FP3/3+ A15 A15 to A16
Fairphone FP5 FP5 A15 A15 to A16
Gigaset GS6/Pro GS6_venus A16 Already on A16
Gigaset GS290 GS290 A12 A12 to A16
Google Pixel 5 redfin A13 A13 to A16
Google Pixel 7 panther A15 A15 to A16
Google Pixel 8 shiba A15 A15 to A16
Google Pixel Tablet tangorpro A14 A14 to A16
Murena One One A12 A15 or A16
Murena Two Two A13 A13 to A16
Nothing CMF Phone 1 tetris A14 A14 to A16
OnePlus Nord avicii A16 A12 to A16
Samsung S9 starlte A15 A12 to A16
Samsung S9+ star2lte A15 A12 to A16
Samsung S7 herolte A12 No updates
Samsung S7+ hero2lte A12 No updates
Samsung S8 dreamlte A12 No updates
Samsung S8+ dream2lte A12 No updates
SHIFT SHIFTPhone 8 otter A14 A14 to A16
Teracube 2e zirconia A15 A14 to A16
Teracube 2e emerald A15 A14 to A16
Teracube 2e sapphire A14 A14 to A16
Volla volla tablet mimir A14 A14 to A16
9 Likes

Nice finally the FP6

Is this correct?

FP3 is on A15 and the upgrade says A13 to A16…?

4 Likes

Thanks. I corrected that.

2 Likes

Thanks! So there’s going to be an upgrade to A16 for FP3—that’s a nice surprise; I had expected A15 to be the final version…

1 Like

There is no final version for any of the devices. We will move all devices possible to A17 once the source code is updated for /e/OS. The only exception would be devices which are too old and would not be able to handle the latest OS versions.
The team understands we had delayed the OS upgrades for some devices in the past but now we will work to reduce the time between new OS release and /e/OS adoption.

7 Likes

If i understand well the goal is to have all device sold by murena (and always supported) to A16. After that, will Murena clean the code of /e/ OS ? May be some feature are more easier to code with an uniform version of Android.

1 Like

This sounds like music to my ears! Thank’s Dev Team.

There is a difference between a definite future and “the plan is”.
There’s no fundamental change in messaging here to what was said earlier about the FP3.

… and it’s still consistent with the overall info …

2 Likes