Week 34, 2023: Development and Testing Updates

Release Information


Status: :green_circle: Pending release

  • Release notes will appear here once the release is triggered
  • Release will be staggered with select devices being released per day

ETA: Release starting from 21 Aug to 28 Aug :crossed_fingers:

Devices missing on v1.13

Devices which missed v1.13 will be released as part of v1.14.

Upcoming milestones / Released

/e/OS T builds

Status : :green_circle: Build and testing

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.

  • First list of devices getting the /e/OS T build.
  • Builds will require manual download and installation by users. It is advisable to take a complete backup of data before any OS upgrade.

ETA : Mid Sep :crossed_fingers:


Photos taken on /e/OS

A post on the forum invites users to share photos taken using camera apps on /e/OS. The idea while encouraging the community to unleash their creative side also gives us opportunity to judge the performance of the camera apps.
Judging from the response the post has received, the chances of it becoming a regular post seems to be quite bright :smile:


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


Check the NextCloud version 🤓 Some users were checking how they could verify the current NextCloud version?
  • You can check the complete documentation and current NC version under https://murena.io/settings/help >> NextCloud xx user documentation. The xx should show 25 now
  • Another way to check the current version is to check the NextCloud scan link 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 :neutral_face: 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

  • Download here
    • 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 …

  • The release of Fairphone FP4 in the US through the Murena Store was one
  • … ???

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)
    • All OTA OS upgrades are on stable builds
Under development
  • Samsung: Galaxy S9/S9+ : Q (A10)→ Android 11 (R)
    • 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


This upgrade has already been completed, hasn’t it?

I reckon so. Version 1.12.5-r in July.

/e/ image ROM download - zirconia

The download pages for manual install wouldn’t say whether it would really be made available OTA, but https://ota.ecloud.global/api/v1/zirconia/dev does say so.

1 Like

According to https://forum.fairphone.com/t/software-update-fp4-sp2j-b-086-20230807/99042 there is a new update for Fairphone 4 solving a very annoying and usage limiting problem with random inputs on display.

Is it possible to add this to the FP4 update as it is made for Android 12? This is really needed for Fairphone users.

Thanks in advance for reply

1 Like

Waiting on a word from the team on its availability OTA before updating that entry. Team members are on leave. Have one confirmation but waiting for a second confirmation.



Final version 1.14 is now available for many devices.

However, for Gauguin (Mi 10T Lite), still nothing! The latest final version is 1.11-s, and the latest beta is 1.12-s.

Is it possible to have news for this device?

  • Is it a mistake/an oversight?
  • Is this phone no longer being maintained?
  • Are the developers working on another project, such as switching to Android T?

Please note that this message is not a complaint. We’re well aware that there aren’t necessarily many maintainers. It’s just a need for information.

Thank you for your general work on /e/OS, which is very good.

1 Like

No device has been dropped. In case some devices are missing, the reason is usually that the builds failed in that particular iteration. The usual response is we try to start a new build in the same cycle. If that does not work, we add it to the next iteration. Will check what is happening here with Gauguin and update.
Also in case a device is being dropped, it will be mentioned in these weekly updates.


Hi everyone,

/e/OS 1.14 is Android 13 now ? Or it’s postponed in mid-september ?

/e/OS 1.14 is Android 10/11/12 :wink:

Android 13 is likely to be added from v1.15


Thanks for the reply. So /e/OS T is postponed to mid-september.


/e/OS T builds

Status : :green_circle: Build and testing

ETA : Mid Sep :crossed_fingers:


Hi guys,

now while 1.14 is rolling out, Lisa got stuck on 1.11 - anyone has news about this device?

Nice to hear that, at least…

Bonjour @Manoj , je voulais savoir s’il est prévu que le S8 de migré vers /e/OS T dans un avenir futur ou le développement s’arrête à /e/OS R ?

I wanted to know if there are any plans for the S8 to migrate to /e/OS T in the future, or is development stopping at /e/OS R?


We will attempt the /e/OS T upgrade for all devices where possible. The first set should come out by September and possibly with v1.15 which is the next release. Post that, we will work on the next set of devices to be upgraded. Plus, we will also share a list of new devices to be added to the supported list.