Week 27, 2023: Development and Testing Updates

Release Information


Status : :green_circle: Testing to start

  • Issues to be tested
  • issues will be added or removed from this list as the testing proceeds


Status : :green_circle: Released

Devices that reported issues with the v1.12.3

  • Yoga Tab 3 Plus LTE YTX703L - build missed - team has been informed and should add it as part of v1.13
  • LG G5 H830 issues reported with build rebooting. Option being considered includes to withdraw builds that do not have dedicated maintainers and are reported by users as having serious issues

Devices that missed receiving v1.12.3

  • Redmi Note 8 / 8T - “ginkgo” - R
  • Xiaomi POCO F3 / Redmi K40 / Mi 11X - “alioth”
  • Mi A2 “jasmine_sprout”
  • Mi 10T Lite / Mi 10i / Redmi Note 9 Pro 5G “gauguin”

Will update what the response from the team is on these builds. The usual process is to add in the next release.

Update 4 July v1.12.5 has been released for Teracube emerald and zirconia (2e) stable users. They should be able to see it in their updater app. This has the fix for the calls not connecting issue. Will update when fix goes on dev.

/e/OS T builds

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

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 :new:

  • Release notes available here :new:
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.


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.

  • :partying_face: On July 5th we shall be sharing some exciting news with our users in the US…stay tuned


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


Whilst it is very disappointing that the update to T has been postponed, anything that makes installation easier, is a good thing and worth waiting a month for.


That would indeed be a major plus in terms of convenience :+1: (I know, Fairphone 3 and 4 users – not sure about FP2 – have been enjoying this from the start – although some might never have been aware of it because it was always a given :wink: ).


v1.12.5 has been released for Teracube emerald and zirconia (2e) users. They should be able to see it in their updater app. This has the fix for the calls not connecting issue. For now, it is on stable builds. Will get back when the dev build will be available.


On my Redmi 8T running on 1.11, the built-in OTA update check doesn’t seem to find the 1.12.3 update yet.

Hi @Manoj,
If version 1.12.3 for Teracube emerald is bugged (no phone call possible), I can’t but recommend to remove it from https://images.ecloud.global/stable/emerald/.
I don’t think there is any added value to leave it in this directory.

Agreed. I’d hate to see some unsuspecting AT&T user install it.

I can confirm that the call issue is fixed. The access point I added for Cricket to 1.10 has carried over. I can save and edit access points, and make calls with 1.12.5


Thanks for pointing that out. I have asked the build team to remove it.

1 Like

Thank you for the weekly update @Manoj really appreciate your work guys. However, I haven’t seen any updates since v1.11 for Poco F3. Has the development been dropped for the device? Thank you.

Thanks for pointing this out. Sharing the feedback with the build team. Will update on the reponse.

Hi @Manoj What about 1.12.3 release for Xiaomi jasmin_sprout and gauguin devices ?
Thanks for anyu news.

1 Like

Adding to the list of devices which missed v1.12.3…shared with build team.


Hello, please also add Oneplus 3 to the “missing list”.

Have created an issue specifically for this.


Hi @Manoj What about 1.12.3 or 5 release for Xiaomi [miatoll] (https://images.ecloud.global/dev/miatoll/) devices ?
Thanks for anyu news.

Adding miatoll to the list of devices missing the build. This is a surprisingly long list of devices that missed a build. The team is creating a script which will share the list of device names that miss the final build. That way the build team is aware first instead of having users alert it.



Samsung Galaxy S5 (kltedv) missed the latest build.
Thank You

Thanks for sharing the device codename, Added to the list. We have created a script that had retrieved the complete list. Will add the names to the issue on gitlab.