Week 41, 2023: Development and Testing Updates

Release Information


Status: :green_circle: Testing
ETA: Mid Oct :crossed_fingers:

Issues with the /e/OS T release

  • Devices for which /e/OS T builds were released are missing recovery builds.

  • This is important because additional partitions which were to be flashed before the actual flashing of the /e/OS T builds were to be included in the recovery zip files.

  • We regret this error on our part

  • The issue is expected to be resolved with the v1.16 release

    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 the zip file by running this command
      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 by running this command tar xzvf payload-dumper-go_1.2.2_linux_amd64.tar.gz payload-dumper-go

    • now run ./payload-dumper-go -partitions -o dtbo,vendor_boot

    • Here the two partition files expected for this device dtbo and vendor_boot are mentioned

    • 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

  • We do have plans to release OS OTA upgrades to /e/OS T for devices we sell on the Murena Shop. For now the upgrade is a manual process. Will share more information around this when available.

Update 9 Oct There is a delay in the release of the /e/OS T build for FP3. Will share date once I have more information.


Status: :green_circle: Released

New devices added to the supported list

Check out this list of devices that have been added to the /e/OS supported list.

:point_right: This list of devices has been released. For now they have the same issues with the recovery file being missing. Expect the issue to be resolved with the next build - v1.16


Upcoming milestones / Releases

Upcoming development :new:

Status : :green_circle: Testing and development

  • Updated version of the Bliss Launcher
    • Currently undergoing testing and code cleanup.
  • /e/OS browser will be updated to the latest chromium version. Team is working on adding some features to the interface
  • A tablet with /e/OS T. Tablet name will be shared once we have the go ahead from build team. The release is tied with the launch of the updated Bliss launcher. Release will be delayed and may not be in 2023
  • Easy Installer to be updated to flash /e/OS T builds.
  • GSI builds to be made to run on /e/OS T. As users may be aware the current GSI is on /e/OS Q.We will skip (Android 11) R and (Android 12) S and directly update the GSI to (Android 13) T.

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


Where can I find 1.15-T for the FP3? My wife has the FP3 from Murena and is currently on 1.15-S. How does she get T?


As I guess this was overlooked in the last thread, I’ll try again:

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

Any news on that?

Currently you would have to install it manually. Maybe there is going to be an “OTA” update in the future, but this is not sure yet (I’m waiting for it, too).

1 Like

There is a delay in the release of the /e/OS T build for the FP3. Will share more details once I get the ETA information.


Maybe for that, it’s impossible to choose a digital assistant app :confused:

1 Like

Could you please name at least one device for which a v1.15 T recovery build is available on the images server?


I was really hoping for Christmas …

What is the current status of the Murena Fairphone 5 release? Is it still on track to start shipping mid-October?

1 Like

How or where do I learn what partitions I should dump using the payload-dumper-go for my particular device? And when I get those what am I supposed to do with them? I§d very much like to understand this in general so any documentation pointers are very welcomed. I do have motorola edge 30 dubai that I’d like to try.

you should begin from reading your device’s documentation here https://doc.e.foundation/devices/dubai/install in order to understand all the flashing steps.
And about the files you are looking for, if you are a windows user, you could take a look at my answer in this thread Cant unzip recovery file to get files for flashing partitions - #13 by LilBeth
Hope it helps.

There are some bugs still open against the FP5 code, on which the developers are working on and has top priority. I have been given a v1.16 timeline by the team for the release of the FP5 code. We expect this release to happen in the second half of this month. :crossed_fingers:


Sorry if this has been discussed about the Fairphone 3, but I couldn’t find something in this forum.

There was some trouble with the original Android T/13 for the FP3 and the fingerprint sensor.
Post on the Fairphone forum: Link!
With the update the fingerprint sensor doesn’t match the needed security requirements, such as in some banking apps. So for some apps it isn’t working anymore.

Is the /e/os team aware of this problem?

Will check and get back. The FP3 /e/OS T build is still under development and testing phase. Will check with the team if this issue is also in their scope.

Update: The team mentioned that the issue has some side effects if fixed, including decreased security on the device. As an explanation, it shared a post made on an external telegram channel …attaching a partial screenshot of the rather lengthy explanation…


My oneplus 5 has received with T a function Names “charge control”. This allows you to limit the charging of the battery. As far as I know, it is a function that was introduced with LineageOS 20.
I very much welcome this feature!
My question: Will all devices get this feature?

I can use it on two Xiaomies, both running 1.15 T /e/OS.

Moto G7 Plus has it also

If fixed? This leaves the question … since official LineageOS includes the fix … will /e/OS include the fix, too, or not?

In case not … just see what Fairphone went through in their forum, and prepare accordingly :wink: .

Just saying. I don’t use the fingerprint sensor, I have no stakes in this.


I use it for my KeePass Database.

I don’t want to type 20+ digits on a smartphone each time I want to open an app :sweat_smile:

And so it begins :slight_smile: .

1 Like