Week 40, 2023 : Development and Testing Updates

Release Information


Status: :green_circle: Released

  • Build Feedback

  • Release notes

  • /e/OS T builds were also released as part of v1.15
    :point_right: Some device builds were not published by 28th due to some issues on the server. Initially the count was 59. The team is working on the issue and has reduced the count.

  • Working with the team to release all pending builds in this week

  • /e/OS T build recovery builds were missing. The recovery zip files to have additional partitions which need to be flashed to get the /e/OS T build to work.

    An alternate method to get the partitions
    • Download latest release of payload-dumper-go (https://github.com/ssut/payload-dumper-go/releases) to the same directory (*) where you downloaded the /e/OS T build ZIP file

    • Open terminal and cd to (*) directory

    • Extract payload: unzip e–s–dev-lemonadep.zip payload.bin

    • Here the example of the lemonadep file has been taken. Replace with the zip file of your zip

    • Extract payload-dumper-go: tar xzvf payload-dumper-go_1.2.2_linux_amd64.tar.gz payload-dumper-go

    • run ./payload-dumper-go -partitions dtbo,vendor_boot -o . payload.bin command — needed files will appear in (*) directory.

    • This method can be used as a temporary measure while the team resolves the issues with the builds and adds the partitions to the recovery zip file

Next set of devices on the supported list :fire:

Check out this list of devices that we will add to the /e/OS supported list.


Upcoming milestones / Releases

Upcoming releases

Status : :green_circle: Testing and development

  • Updated version of the Bliss Launcher
  • A tablet with /e/OS T. Tablet name will be shared once we have the go ahead from build team.

ETA: To be announced

:nerd_face: ETA: Estimated time of arrival - term used in software development to denote the estimated time when a product can be expected to be released.


Previous 5 releases & user feedback


:warning: Posting information on test builds

  • Please do not post information or links to /e/OS test builds on the forum.
  • 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 and do some minor level of testing on custom ROMS, you are welcome to join the testing team
  • As part of the testing team you can share your comments on the dedicated testing telegram channel.


Murena cloud updated to NC

Status : :green_circle: Released

Self hosting Murena cloud v

Status : :green_circle: Released


How to check the NextCloud version 🤓 You can find the complete documentation and current NC version under https://murena.io/settings/help >> NextCloud xx user documentation. The xx should show the latest version. - Another way to check the current version is to check the [NextCloud scan link](https://scan.nextcloud.com) and input https://murena.io this should display the current version number as well as the security level. > Please note if MurenaCloud patch number is not the same as the NC patch number, the rating would show up as bad 😐 This is not exactly a problem. We do not immediately jump to the next NC patch as soon as it is released. We first test it and then set out with the deployment.



Status: :green_circle: Released :new:

  • Download available here](https://doc.e.foundation/support-topics/understand-and-use-gsi.html)
    • Sources available here
    • version is /e/OS Q (A10)
    • S (A12) and R (A11) version of GSI yet to be planned. Awaiting developer availability
    • Frequently we see users complain about the GSI OS versions not being in sync with the ROM OS versions. As mentioned we do have developer bandwidth issues. If there are users who have development skills we welcome them to share their expertise and help speed up the process in the true spirit of an Open Source project.


Roadmap for 2023 and beyond

Read this post where Gaël shares his vision on the Murena and /e/OS roadmap into 2023 and beyond

This is just a sneak peek into exciting news we would be sharing in the days to come.
For example …

Subscribe to our newsletter to get the news first hand. All links available below.


OS OTA upgrades

What OS OTA upgrade means

Usually for /e/OS ROMs to upgrade the OS you have to do the following

  • If available download the correct OS build from the supported device list
  • For some devices you also need to download the stock ROM from the vendor site.
  • Take a back up of your data
  • First install the Stock ROM
  • Next install the /e/OS ROM. Here you can take help of the install guides available on our documentation site.
  • If required apply the backups you downloaded before starting the whole process

An alternate to this tedious process is where we offer the user the option to upgrade the OS OTA. This option is available for stable device builds only.
This process is easy for the user but requires a lot of development and testing effort.

Different /e/OS build types

  • Gigaset: GS290 : Q (A10)→ Android 11 (R)
  • Oneplus: avicii : A12
  • OnePlus : avicii : Q ( A10) → R (A11)
  • Fairphone: FP4 : R ( A11) → S (A12)
  • Fairphone:FP3 : R (A11) → S (A12)
  • Fairphone:FP3 : Q (A10) → R (A11)
  • Samsung: s7 / s7+ : Nougat (A7) → Q (A10)
  • Samsung: s9 / s9+ : Oreo (A8) → Q (A10)
  • Samsung: s8 / s8+ : Pie (A9) → R (A11)
  • Teracube: 2e / zirconia: Q (A10) to R (A11)
  • Teracube: emerald & zirconia : R (A11) to S (A12)
    • All OTA OS upgrades are on stable builds
Under Testing 🆕
  • Samsung: Galaxy S9/9+ : Q (A10)→ R(A11)
  • Gigaset: GS290: R(A11) → S (A12)
    • All OTA OS upgrades are on stable builds


Support dropped

Only one OS version per device

  • Support of multiple OS versions on the same device has been stopped
  • Upgrade your device to the latest OS version available.
    • For example, if /e/OS R (Android 11) builds are available for your /e/OS Q (Android 10) build, upgrade to the latest version which in this case would be A11.

Nokia devices

  • All Nokia devices

    • It is not possible to officially unlock Nokia bootloaders + lack of dedicated maintainer
  • Google

    • Google Nexus 7 2013 flox
    • Device has partition size issues. Not able to build /e/OS ROMs for this device even with minimal build

    :nerd_face: Minimal build is a setting in /e/OS build which removes the following default applications (LibreOffice viewer, PDFViewer, Maps and Weather)from the source code and builds a smaller version of the ROM.


Check real time availability of /e/OS and related services websites
OS upgrade info specific to the FP3
  • The FP3 OTA OS update from Pie to Q/R is not possible as encryption method changed on FP3 between Pie and Q/R. It is not possible to change the method while updating.
  • The team spent a great deal of time on this, but has not been able to resolve this problem. For now, the manual process is the only way to upgrade the FP3 from pie to other OS versions.
End of official support for Nougat, Oreo and Pie 😞 Pie, Oreo and Nougat the official /e/OS support has ended.

Reasons for dropping official support are:

  • newly released applications like App Lounge, Advanced privacy code has not been customized for these OS versions.
  • lack of dedicated ROM Maintainers
  • no support upstream (Lineage dropped support for Pie sometime back)
  • device trees will continue to exist in the Gitlab and users with build skills can create custom ROMs on these builds
  • Security patches and vendor patches for the Pie, Oreo and Nougat code will be updated based on availability.

:nerd_face: Google stops security patches for OS after some time. Similarly, Vendors drop support for older models when they release newer models in the market. Then it depends on developers from various communities to backport the patches.

Device and Vendor specific Announcements

:loudspeaker: Gigaset GS290

  • We have stopped the sales of the Gigaset GS290 on the eSolutionsShop as the vendor has stopped production of the device. We will continue support for existing users.

:loudspeaker: Message being shared on the request of our vendor partners

  • Vendors whose phones we sell on our eSolutions Store do not directly sell /e/OS flashed devices.
  • The vendors only sell their devices with their own stock ROM.
  • To get pre flashed /e/OS phones, you have to purchase them from the eSolutions Shop.

:loudspeaker: /e/OS Pre flashed device sales

  • We sell directly in EU, US, Canada.
  • Find details of what devices are available in which countries here eSolutions Shop.
  • In Australia we do not sell directly. You can purchase preflashed /e/OS devices from this site

:loudspeaker: Murena One released
A phone from Murena with /e/OS installed has been launched and is available for purchase. Check the device specs here

Expect more device releases from Murena in future :grinning:

:nerd_face: Murena is the brand name and /e/OS is the operating system.

Different /e/OS build types

Check out this guide to understand differences between build types on /e/OS

/e/OS website and social media Links


  • Facing issues with devices you purchased from us ? Send a mail with details to helpdesk@e.email


Telegram Channel

Social Media


Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone


Please repaire the Link:

1 Like

Thanks for pointing that out. Have corrected the link.

1 Like

Could you confirm the date when pixel 7 pro will be added ?

Expect to release Pixel 7 pro ‘cheetah’ this week along with the other new devices :crossed_fingers:


Can you share information when murena stire purchased phones will get the T OTA upgrade?

In Gael’s “roadmap 2023”-post we learned: “we are finally going to integrate the long-awaited voice recognition feature.”

Any news on that?

No ETA available as yet. As mentioned previously, we do plan OTA OS upgrades for all devices we sell on the Murena Store. The Fairphone devices upgrade to /e/OS T will have to be planned. Will share details when I have something more positive to report.

1 Like

Here’s a short excerpt from " Week 32, 2023: Development and Testing Updates", section “e/OS/ T builds”:

Status : :green_circle: Postponed to August along with v1.14 :crossed_fingers:

Team is working on adding firmware along with the T builds. This will make it easier for users to flash the builds without having to flash the stock ROM first.

Now, that (with an additional delay to v1.15) e/OS/ T has been released, let me please ask:

Where are these announced “firmware adaption easing” packages?

Any ETA on the T version for axolotl? https://images.ecloud.global/dev/axolotl/

Since axolotl is supposed to get T, I guess this applies (see first post) …

I’m looking at purchasing an FP5 or P7-Pro (cheetah) to load e/OS onto. Are there any dev builds up for these devices yet?

Fairphone 5 is in testing … https://gitlab.e.foundation/e/qa/testing-community/-/issues/55

1 Like

Hello. This is my first post on the forum.
When can we expect the T recovery files?
I have 4 phones waiting for 1.15 T instalation and NONE of them have the 1.15 recovery files: Oneplus 5, Sony Xperia XZ2, Sony Xperia XZ3 and Sony Xperia XZ2 premium.
I’d like to try the T on Oneplus 5 as it has a cracked screen and original OS so minimal loss if bricking (I’ve not yet managed to brick any phone of the many I had). Then move to XZ2 and XZ3 that are now running 1.15S . XZ2 premium is to be flashed later (1.16). I’ve checked and my XZ3 has the recovery 1.15S even if it’s not present on the device download page: https://images.ecloud.global/dev/akatsuki/
Manoj can you please insist to the team to solve the problem of missing T recovery files? I’m waiting for the T (13 is my favourite number) since the release of LineageOS 20.
Thanks in advance!

I discussed the issue with the team. They have put in a fix with the resolution but unfortunately it would not show up till the v1.16 is rolled out. The builds and partitions files inside recovery zips has created some confusion in the build process. Will keep you updated on the progress.


Thank you Manoj for your very quick answer. Any “bet” on the release of 1.16? I’ve seen that the milestone for it expires on 10 october but doubt it will be released next week.
I’d say that week 41 will see the beta state and week 42 the announcement of lauch… whishfull thinking.

That’s a bummer :frowning: Been waiting so long already…

v1.16 should be coming out around mid October :crossed_fingers:


Will 1.16 include firmware partitions as well for T?

Will this fix also repair all the collateral damage done to the respective device sections on the images server for all those devices which don’t need any recovery zip, but may stick with the good old recovery img (solely)?