Week 26, 2023: Development and Testing Updates

Release Information


Status : :green_circle: Released

  • Release process is staggered and started on 20 June. Expect to publish all builds by 28 June .
  • Dev builds will be published initially. Stable builds to follow.
  • Release notes


/e/OS T builds

Status : :yellow_circle: Postponed
Update 27 June We have postponed the release of /e/OS T to August.
The reason behind this decision is the 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.
  • Users will have to download and install the T builds after taking backup of their data.


Upcoming releases

Status : :green_circle: Pending release

  • 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.


Telegram based support channel for Portuguese speakers :new:

A new telegram support channel has been added for Portuguese language speakers

Murena cloud updated to NC

  • Release notes available here


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.


:information_source: If some users are seeing notes disappearing or Murena Cloud services not accessible anymore, we request them to connect to Murena Cloud and accept the TOS (Terms of Service) popup. The team is working on a fix for this issue


v1.12.3 :new:

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 some exciting news we would be sharing in the days to come. Subscribe to our newsletter to get the news first hand. All links available below.


Self-hosted eCloud upgrade

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

Completed - GS290 >> Q (A10)→ Android 11 (R) :new: - Oneplus nord aviccii >> A12(stable) - FP4 >> R ( A11) to S (A12)stable - FP3 >> R (A11) to S (A12) stable - FP3 >> Q (A10) to R (A11) stable - OnePlus Nord >> Q ( A10) to R (A11) (stable build) - Samsung s7 / s7+ >> Nougat (A7) to Q (A10) - Samsung s9 / s9+ >> Oreo (A8) to Q (A10) - Samsung s8 /s8+ >> Pie (A9) to R (A11) OTA upgrade
Under development
  • Teracube 2e zirconia Q (A10) to R (A11) - To be released ASAP :new:
  • Galaxy S9/S9+ Q (A10)→ Android 11 (R) - No ETA as yet


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

eCloud related websites

/e/OS related

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 😞 For Pie, Oreo and Nougat the official /e/OS support draws to a close.

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


Hi @Manoj,
Could you please confirm that the issue concerning the devices Murena One and Teracube (2e and emerald) that missed v1.11 build has been fixed, so these devices will have v1.12.3 ?

For example, I don’t see stable release for emerald in https://images.ecloud.global/stable/emerald/.

I think it is not released yet, for sunfish (Pixel 4a) stable is also not available yet

Was checking with the team, and they confirmed that the zirconia (2e) and emerald updates as well as One should be released with v1.12.3

1 Like

"Under development

  • Galaxy S9/S9+ Q (A10)→ Android 11 (R) - No ETA as yet“
    Could you briefly explain where the difficulties lie. There has been no progress at this point for many weeks.

Have I missed that? Where is it? :wink:

Developer bandwidth is the main issue. We need more developers.


You have missed nothing. The announcement has not been made as yet.


@Manoj In the release notes :

Upgrade of Teracube 2e (2020) to Android 11

Coming from Android 10 (Q) with stable build, is this offered as an OTA upgrade or manual upgrade?

The stable zirconia upgrade from Q to R will be OTA.

1 Like

Hello @Manoj,

Will there be any guides/tutorials on how to do the upgrade properly? I’m a bit paranoid about making my phone unusable.
I used the easy installer at the time and even with this great tool it wasn’t so easy for a novice.

What’s needed is a more or less detailed procedure giving the necessary steps.

I’m sorry but when I read this :
ADB sideload can be used to upgrade to t build.
There is no need to flash stock

I barely understand what it’s talking about…
I know there are a lot of topics on this forum dealing with the subject but if we could have something official or at least validated by /e/ it wouldn’t be bad.

BTW thank you so much for the T upgrade :wink:

1 Like

The release of /e/OS T builds has been postponed.
They will now be released in August with v1.14 :crossed_fingers:
The reason behind this postponement is the team is working on adding the firmware and vendor updates to the builds. This would make it easier for the user to flash the ROM instead of first flashing the Stock ROM.
Will update on the progress of the work.


Hey @Manoj,

Sad to read you postponed /e/OS T but if it’s for the best, good choice :slight_smile:


Some builder users ask when T working sources will be available for unofficial builds ?


it is not necessairy for devices not maintained anymore by their vendors

That’s an excellent news for devices still maintained !

1 Like

So users are still prevented from using Trebuchet as Homescreen / Launcher :frowning:

Since /e/ OS T has been postponed I would like to install /e/ S Stable on my hotdogb. Has the issue been resolved that was encountered last month when installing /e/ OS S the touchscreen stopped working because of some type of partition mismatch? Also, reported here OnePlus 7T ‘No Touch Display’ after install - /e/OS Devices / OnePlus - /e/OS community

Just did a clean install of /e/ OS Stable S 1.12.3 via Command Line on my OnePlus 7T (hotdogb) and can confirm the loss of touchscreen right away on the setup screen is still there. I’m surprised there are not more people reporting this then what there is the post I linked previously. @Manoj do you have any insight into what the status is on this?

There is an issue around this in Gitlab Pl can you add details to that issue like steps you took to flash as well as logs if any. Have passed on the feedback to the team.


Thank you. Sorry, I forgot that I reported that in Gitlab. I have updated that with information from my previous post.