Week 39, 2023: Development and Testing Updates

Release Information


Status: :green_circle: Released :new:

/e/OS T builds

Status : :green_circle: Released :new:

  • Staggered release. All devices from this list
    to get updates by 28 September
    Some of the devices which require firmware partitions to be installed will get the firmware partitions included in the recovery zip file. There is an issue with the recovery zip files not showing up on the images server. Following up with the team regarding this. Will update.
  • Builds will require manual download and installation by users. It is advisable to take a complete backup of data before any OS upgrade.
  • We plan to add OS OTA upgrade to /e/OS T for devices purchased from the MurenaStore. No ETAs for now.

Update: Issue with the updater

An issue has been reported with the updater due to which some users are not able to see the latest builds. Please check this post for a temporary fix as the team works on a permanent solution to the problem.

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 …

  • The release of Fairphone FP4 in the US through the Murena Store was one
  • Fairphone 5 with /e/OS release

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)
  • Samsung: Galaxy S9/9+ : Q (A10)→ R(A11) :new:
  • Gigaset: GS290: R(A11) → S (A12) :new:
    • 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


Thr link goes to the wrong place.

1 Like

Thanks for pointing our the error @chrisrg . Have corrected it.


Hi Manoj,

We expect to release the OTA OS Upgrade for the Galaxy S9/S9+ stable build this coming monday. Q (A10) to R (A11)"

Is this still happening today?

Yes, it is still targetted for release today.

1 Like

Thanks. I look forward to seeing whats different in the newer Android version.

:blush: :+1: :sparkler: :fireworks:

17:30 GMT. No S9+ OTA ATM.

It will still be “today” for much longer in IDLW or “Anywhere on Earth” :wink: .

Also, don’t forget to always refresh the updater a few times when checking (in case of a staggered release).

The task is marked as complete in the plan. Will check with the team once they are in office and get back with the response.

Update: The OS OTA upgrade build should show up only for those on v1.14 Q build and it will upgrade their device to v1.15 R stable build.


Samsung Galaxy S9 and S9+ update to Android 11, in addition to a firmware update

Is there some place that lists the issues addressed by the firmware update in the OTA R release ?

I’ve already updated to 1.15 Q (Samsung Galaxy S9)
Will the update to 1.15 R (Android 11) not trigger OTA now?

It’s depends, are you in stable or dev build ?
The OTA upgrade to 1.15-R for the S9 (starlte) is only release for stable builds at the moment.

I think stable. Is there a way to check?

1 Like

So it seems I’m on dev version so will not get android 11…

Is there any way to switch to stable without formatting?

e-1.15-t-20230918331436-dev-starlte is out !
if you are on dev branch, you can now get a T build based on Android 13
simply download it and reboot to recovery to apply
(if you already have one of the latest Q samsung Firmware installed, check the baseband version in -->settings -->about and compare to https://samfw.com/firmware/SM-G960F : last four letters are for /version /year /mounth /release)

some concerned users claim not, but i don’t understand why…

hi piero, thanks for the info, one question: how can i install the latest samsung firmware? have i to go back to stock rom?

you also could flash only necessary part “BL” bootloader and “CP” modem

Got the 1.15-r-20230814330641-stable-star2lte OTA update.

A straight forward, successful update, thanks very much.

This version includes the firmware update?

1 Like