Week 13 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.

Release :new:


Status :green_circle: To be initiated

  • Release notes will show up here

  • Build Feedback

  • Builds that missed v1.20 will be available in v1.21

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

Coming with v1.21

  • Fairphone: FP3 : S (A12) → T (A13) OS OTA upgrade build

Not coming with v1.21

  • Fairphone: FP4 : S (A12) → T (A13) OS OTA upgrade build - issues remain with the touch feature post upgrade. Team working on resolving the bug.

ETA: 26 Mar to 1 April

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

Previous 5 releases & user feedback

Links to the last 5 releases click here

Documentation Updates :new:

  • The Supported devices table now displays the Safetynet and Rootbeer status for all devices in the list. For devices which show a :question: we would request users to run a test and share the feedback with us. The forum post on this is here.

  • Stable builds are now referred to as Official and dev builds are Community. This change will be visible in our Supported device list.

  • Official / Stable support dropped for these devices

    • Easy Installer will flash the community or previously known as 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
  • Transfer data from iPhone and iCloud to /e/OS and Murena Cloud guide

  • How to backup and restore and /e/OS device

  • Users may have noticed a difference in the internal storage size on fresh installations. We have created a guide to explain this.

  • Upgrade guides have been removed from the Documentation site. The recommended method to install is first flash the stock ROM (where required as per the guides) and then a clean install of /e/OS. This process will format the device and will include data loss. Users are advised to take a backup before proceeding with the format.

: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)
  • Fairphone: FP4 : S (A12) → T (A13)
    • ETA v1.21
To Plan
  • Samsung: S9/9+ : R(A11) → S(A12)
    • ETA Will be shared later


Support Dropped :new:

Support dropped for these devices

  • Motorola Motorola Moto G7 Play channel
  • Google Pixel XL marlin
  • Google Pixel sailfish
    • We have been unable to build builds for the device post v1.17 which was on /e/OS T.
    • Users with ROM building skills will be able to create customized builds of the channel if they so desire as the device trees will be available on our servers.
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

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


this page has not been updated yet :


Yes, it was in this weeks list to be updated.


We may drop Nothing ‘Spacewar’ Phone 1. LOS has no maintainer and last build has multiple bugs. Unless a user steps up and volunteers to become the ROM Maintainer for this device the chances are it will be dropped. Will update the progress of the discussion.

Hey @Manoj, is there any update to ETA of Bliss 3? “Early 2024” seems not to be feasible anymore :wink:

By the way, what will be new in Bliss launcher 3? Is there some info available?

Thank you and best regards,

We will be sharing the details soon and still make it ‘Early 2024’ .




Yes indeed! With an /e/OS v2.0
Which should be coming up soon.

Update: v1.21 maybe the last in the v1.xx series. We are planning on having v2.0 for the next release. This would include v3.0 of the BlissLauncher besides other updates.
Will share more details in the next couple of days.

ETA would be : April end :crossed_fingers:


Is there any Project/Branch on Gitlab where we can observe how Bliss Launcher 3 dev is going?

At the moment the BlissLauncher v3 development is only visible to the internal development team. The code will be opened for all only prior to release. Will be sharing the release date through these posts.


FP4 users pl note the update added to the initial post. The team is working on resolving the issue but for now the release of the upgrade build has been postponed. Will update.


I suppose it has to do with keeping the tablet secret :laughing:.

I’m admittedly new to /e/OS and Bliss Launcher, and coming from years of stock-ish Android (Nokia then Samsung phones), the current Bliss Launcher unfortunately got a no-go quite fast. Not that it doesn’t have its good sides, but the lack of some useful features made me switch to another launcher after barely a week of use.
Bliss Launcher 3 seem to at least address some of my concerns, so I’m kinda looking forward to try it, but beside the widget on any page feature, I didn’t find anything on what is planed.
Why not show off more of the features as they are built, even without releasing the code itself, so the community can discuss about them and offer their feedback ?

Thank you. What exactly is this touch feature that causes the issue?

The smartphone screen where you use your finger to activate apps or do any activity. This is buggy.

1 Like

Thx for the update :muscle:t2: do you have a link for the related FP4 issue? I’d be curios…

The issue is marked internal and only accesible to the development team as it is was detected on a build which has not been released to users.

I’m quite curious too, I thought it was about the ghost touch problem but if the issue concerns the touch feature itself, then I wonder how it became known just a few days before delivering 1.21.

Anyway, the FP4 OTA upgrade was originally supposed to happen with 1.19 and will likely arrive with 1.22 (or 2.0?). Our patience is being tested :slight_smile: Good luck to the team to solve the bug.

Just saw the new blog post by @GaelDuval. Looking forward to all the new features coming soon. Few questions. Last year he mentioned that Advanced Privacy would be released as a stand alone app. Is that available? Can we please get the settings back in “Wallpaper and style” to choose our own colors and have Material You in version /e/ OS 2.0? Will /e/ OS 2.0 include Android 14?

1 Like

Hello Manoj,

Does that means that we have to go back to stock rom first before installing hte next upgrade (like Q to T for example) ?

Thank you

Yes if the device requires a flashing of the stock ROM first then that is the first step. Before installing /e/OS. That way the new OS firmware will be added to the device.

1 Like