Week 10 2024: Development and Testing Updates

Summary of Weekly development and testing activities by /e/OS developers and volunteers. Efforts mentioned here are continuation of tasks in progress or new development activities. Updated content will have the :new: emoji.


v1.20 :new:

Status: :green_circle: Release ongoing

:point_right: 22 Feb to 4 Mar

  • Release notes are available here

  • The next set of new devices along with existing ones that will be upgraded ( all builds on /e/OS T)

    • have been released as of today 4 March
  • Build feedback and voting for v1.20 here

Info about ongoing development tasks click here

Development and internal testing

  • Updated version of the Bliss Launcher or Bliss launcher 3
  • Currently undergoing testing and code cleanup. Launch planned early 2024.
  • /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. Launch planned early 2024 :crossed_fingers:
  • Easy Installer to be updated to flash /e/OS T builds. ETA to be planned
  • 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 planned

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

Upcoming milestones information

Stable support dropped for these devices :new:

  • The documentation guides are in the process of being updated
  • Easy Installer will flash the dev build for these devices :fire:
    • Google Pixel 4a sunfish
    • Google Pixel 4a 5G bramble
    • Google Pixel 4 XL coral
    • Google Pixel 4 flame
    • OnePlus 7 Pro guacamole
    • OnePlus 7T hotdogb
    • OnePlus 8 instantnoodle
    • OnePlus 8 Pro instantnoodlep

:point_right: stable builds will be available for devices we sell in our Murena Shop. That means stable builds will continue to be available for the following devices FP3 , FP4 ,FP5 , Murena one, Murena Two, GS290, zirconia, emerald, herolte, hero2lte, dreamlte, dream2lte, starlte, star2lte, redfin

Previous 5 releases & user feedback

Links to the last 5 releases click here

New Documentation guide :new:

:nerd_face: Users may have noticed a difference in the internal storage size on fresh installations. We have created guide to explain this. You can find the guide here


: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](https://doc.e.foundation/testers) 
- As part of the testing team you can share your comments on the dedicated testing telegram channel. 


Murena Cloud updates

Murena cloud and Self-hosting version details click here

Updated to NC

Status : :green_circle: Released

  • We have upgraded Murena.io nextcloud backend to NC26, which includes performance improvements, bug fixes and security patches.
  • The release notes are available here

Self hosting Murena cloud v 26.0.8 :new:


How to check the NextCloud version click here 🤓 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.


Current GSI version click here


  • Download available here
    • Sources available here
    • version is /e/OS Q (A10)
  • :point_right: The Q v1.17 GSI build is the last build in /e/OS Q
  • :point_right: GSI OS version will next move to T or A13 skipping the R and S versions. Dates for development will be shared


OS OTA Related information

What OS OTA upgrade means click here

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: Galaxy S9/9+ : Q (A10)→ R(A11)

  • Samsung: s8 / s8+ : Pie (A9) → R (A11)

  • Teracube: 2e / zirconia: Q (A10) to R (A11)

  • Teracube: emerald & zirconia : R (A11) to S (A12)

  • Samsung: S7 ‘herolte’ ‘hero2lte’: Q ( A10) → R (A11)

  • Google Pixel ‘redfin’: S(A12) → T(A13)

  • Gigaset: GS290: R(A11) → S (A12)

    • All OTA OS upgrades are on stable builds
  • Fairphone: FP3 : S (A12) → T (A13)
    • ETA v1.21


Support Dropped

Multiple OS versions
  • Support for /e/OS Q is being dropped for most of the devices.

  • Exception would be Samsung S7 / edge herolte and hero2lte which will be upgraded to /e/OS R or Android 11 :new:

  • Support of multiple OS versions on the same device has been stopped.

  • If you see multiple OS version builds on the download page, switch to the latest /e/OS version.

  • In most devices it would require a manual download and installation. Take a backup before proceeding.

  • We will add a text on the images server mentioning that older OS versions are no longer supported.

  • No longer supported will mean that build would not be made in the older OS.

  • It is always advised to switch to the newer OS versions as some of applications may not work correctly on older OS as application developer stop supporting older OS.

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.


Murena Two now available for purchase

Where to buy the Murena Two and Murena One from?

A phone from Murena with /e/OS installed has been launched and is available for purchase. Check here. Select a country and check availablility and device specs

Expect more device releases from Murena in future :grinning:

:nerd_face: Murena is the brand name and /e/OS is the operating system.


Vendor specific information

Bootloader unlockable devices

As you may be aware the bootloader needs to be unlocked to flash a custom ROM like /e/OS.
The vendors of the following devices are preventing the unlocking of the bootloader

  • Huawei
  • ASUS - unlocking tool reported as not working for last couple of months.

:point_right: We have added a warning on the install pages for these devices to warn our users before they try to attempt to flash /e/OS.


Misc information

Upgrade guides removed

We have removed the upgrade guides from our Documentation site. Users who are planning to upgrade the /e/OS installation on their device are now advised to

  • Follow the instructions given in the command line install guide
  • If suggested in the guide, first install the stock ROM
  • Next if required flash additional partitions
  • Finally a fresh install of the latest /e/OS build
  • Follow the instructions for your devices. The instructions would be different across devices.
  • This advice is specific for OS upgrades ie. from a lower OS version to a higher version for e.g. /e/OS R to /e/OS S or Android 11 to Android 12.
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 and Australia
  • Find details of what devices are available in which countries here Murena Shop.
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 and Support


  • Facing issues with devices you purchased from us ? For issues you would want support on from the /e/OS support team, send in the details using the contact form


Telegram Channel

Social Media


Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online servicesphone


Thanks for the information, one question, you haven’t mentioned in the stable builds support the pixel 5, will there be stable builds in the future? i hope so :+1:

Hi Manoj, isn’t S7-upgrade completed by now with distribution of 1.20?
(again: many thanks for the effort!)


:slight_smile: thanks missed moving that to the completed section.


redfin is Pixel 5 isn’t it? So there should be OTA updates in the future, about OTA upgrades (to V A14) can Manoj maybe say more.

A14 ? We are working on completing the current set of A13 releases. A14 will take some time.

1 Like

He asked about future :woman_shrugging:. T(A13) is under testing, so the next will be V(A14) whenever it comes :smiley: .

:loudspeaker: Pl note the next set of device to be added to the support list and the upgrade of existing devices to /e/OS T have been released as of today 4 March… :new:


Hello Manoj, is there a plan or a date to migrate to 28? Thanks

Thanks. Have added it now.

Hi @Julien first it would be 27 in the next month :crossed_fingers: and then 28 later. Will share dates when I have more inputs.

1 Like

Device that did not receive builds as part of v1.20 as the builds failed

  • Google Pixel XL merlin
  • Motorola Moto G7 Play channel
  • Google Pixel sailfish
  • LG V30 joan
  • LG V30 h932

The team will try and rerun the builds or they will be available as part of v1.21


@Manoj App Lounge seems down on both my wife’s and my phone. The refresh session message keeps going on and on. Nothing suspicious on https://status.e.foundation/ though. Do you have any info from the team?

I still don’t see version 1.20 in the Updater on a Galaxy Tab S6 Lite (gta4xlwifi).

The updater app does not support upgrades from one version of /e/OS to another (/e/OS-S to /e/OS-T), and will block installation to any update for a different version. Upgrading manually requires similar steps to installing /e/OS for the first time.

By the way: The big brother Lineage Android Distribution (LOS) expects stock firmware Android 13 to be installed on the tablet ‘gta4xlwifi’ for the installation of LOS 20.0 (~ /e/OS-T).

So if I wouldn’t follow updates here, I would never notice there is a newer version and just stop receiving any updates at all?

I don’t find an upgrade guide here. I guess I have to follow this guide with the respective /e/OS builds?

1 Like

As the needed parts of the upgraded stock firmware are expected to be included in /e/OS-T builds,
I understand, you simply have to download, reboot to recovery, and apply… to upgrade from “s” to “t”.

Just DON’T WIPE OR FORMAT ANYTHING (don’t apply “factory-reset”)
as explained at step (8) or (9) of the general guide i shared [HOWTO] an Unified Install Guide Project for /e/ - #4 by piero

1 Like

I can confirm this. The upgrade path was like this for me and it worked. Never forget to charge the phone in advance.

1 Like

AppLounge is working for me. I just checked. Tried downloading and installing and that worked as well. Are you still facing the issue?