Week 16 2024: Development and Testing Updates

Summary of weekly development and testing activities by /e/OS developers and volunteers. Updated content have the :new: emoji.


v2.0 :fire: :new:

Status :green_circle: Testing

The next release will be v2.0

  • Issues and fixes
  • Bliss Launcher v3
  • UI and Wallpaper updates
  • Fix for the issue where /e/OS users required to login to use Notes app
  • Fairphone: FP4 : S (A12) → T (A13) OS OTA upgrade build :crossed_fingers:
  • Shift6mq axolotl - script based installation - lockable bootloader- dedicated maintainer

:point_right: There will be no updates for Motorola Moto G5 ‘cedric’ until the issue with the bluetooth and wifi is resolved. There is an issue on this in gitlab. No ETA available for now.

ETA: End of April :crossed_fingers:

Roadmap for 2024

Gael 's roadmap for 2024

Upcoming milestones information

Ongoing development tasks
  • 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. Tablet launch planned early 2024 :crossed_fingers:
  • Easy Installer to be updated to flash /e/OS T builds. ETA to be planned

Previous 5 releases & user feedback

Links to the last 5 releases click here

Documentation :new:

Recent updates
  • A guide on how users can bypass spam filtering on Murena Cloud. This is a workaround as we have received a few complaints from users that their regular emails were being marked as spam.

    • Following the instructions from this guide the user can bypass the Murena webmail spam filters
    • The guide is accessible from:
  • 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
      • 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
  • As part of the testing team you can share your comments on the dedicated testing telegram channel.


Murena Cloud and Self hosting :new:

Murena cloud NextCloud version upgraded :fire:

Murena cloud current version

:point_right: Murena cloud Next Cloud

Self Hosting current version

:point_right: Self hosting Murena cloud v 26.0.8


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

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

  • Fairphone: FP3 : S (A12) → T (A13)

    • All OTA OS upgrades are on stable builds
  • Fairphone: FP4 : S (A12) → T (A13)
    • ETA v2.0
To Plan
  • Samsung: S9/9+ : R(A11) → S(A12)

  • Samsung: S8/8+ : R(A11) → S(A12)

    • ETA - probably with v2.1 :crossed_fingers:
Our definition of an OS OTA upgrade

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


Support dropped for :new:

List of devices for which support has been dropped
  • Nothing Phone(1) Spacewar
    • Multiple bugs in the last build. No dedicated maintainer on /e/OS or LOS side.
  • Motorola Motorola Moto G7 Play channel
    • Partition space issues
  • Google Pixel XL marlin
    • Partition space issues
  • Google Pixel sailfish
    • Partition space issues
  • Google Nexus 7 2013 flox
    • Partition space issues
  • LG V30 (T-Mobile) ‘h932’
    • Build issues
  • LG v30 ‘joan’
    • Build issues
  • All Nokia devices
    • 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.

    • Partition space issues are reported for devices where we have been unable to build with even the minimal /e/OS build. 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.

No more 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
    • No dedicated maintainers
  • Huawei
    • Unable to unlock bootloader
  • ASUS
    • unlocking tool not working for last couple of months.

:nerd_face: As you may be aware the bootloader needs to be unlocked to flash a custom ROM like /e/OS.

: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

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.

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 deGoogled mobile OS and online servicesphone


Does this mean version 2.0 will allow us to go to Wallpaper & Style in Settings and choose our own colors including Material You styles?

1 Like

I am really looking forward to the update to Bliss Launcher v3. Can you please give some sneak previews of what to expect… Please?

Will Bliss 3 allow the user to install and choose Trebuchet as the default home screen / launcher?

1 Like

We will be sharing some screenshots soon. Currently, the builds are all getting ‘built’ and undergoing testing.


No BlissLauncher v3 will not be providing options to install other launchers from within its interface. User can always download and install launchers they want and set them as default.


thanks for enumerating the reason why a device was dropped

OK I mis-phrased my question - I’ll try again:

In /e/OS 1.x,

  • users could not install Trebuchet from App Lounge or F-Droid because it was already present in the ROM
  • but users could not use Trebuchet as their default home screen / launcher in Settings | Apps | Default apps because /e/ changed the Trebuchet code to disable the ‘HOME SCREEN’ intent.

Has that changed in /e/OS 2.x so that users can install Trebuchet from App Lounge and can set it as default home screen / launcher in Settings | Apps | Default apps .



Does this mean version 2.0 will allow us to go to Wallpaper & Style in Settings and choose our own colors including Material You styles?

We can hope so but I think the chances are low, sadly

1 Like

@Manoj Any news on this question please? Is use of Trebuchet disabled in /e/OS 2.x as it was in /e/OS 1.x?


In v2.x trebuchet is not disabled by /e/OS. Users can download and install it but they should not remove Bliss Launcher using adb or as root as some of the packages in BL are common across all launchers. For now Trebuchet is not in App Lounge. I have asked the team to add it to the App Lounge. If an issue can be raised on gitlab to add Trebuchet to the app lounge, that would be better.


That’s great - thanks Manoj.

Trebuchet is available from F-Droid, but it is known there as ‘Launcher3’ (com.android.launcher3). Maybe it is already in App Lounge under that name

Is there any news about the FP4 display issue? Was the team successful in resolving it? :crossed_fingers:t2:

The issue on the FP4 was detected on the upgrade build which is on T. The FP4 will receive a v2.0 on /e/OS S. The upgrade to T build is being pushed to v2.1


Thx @Manoj for the update! That’s sad news, I’m really looking forward to get Android 13 so that some underlying FP4 issues are being fixed (e. g. the display brightness issue).
Are you considering to bring this newer firmware fixes to Android 12 / an S build instead of T? Android 13 is not soooo important for me, but especially the brightness things makes my Fairphone really hard to use outside in the bright sun.

Not possible. Fairphone released the firmware update including the brightness fix only for Android 13, not 12. Therefore e foundation is not able to apply the patch to S

Oh no, that’s sad :disappointed_relieved::tired_face:

1 Like

I wait for a general change for the FP4, too.
For me is is the ending of the bad battery life during “do nothing”.
Somebody gave me hope that it will maybe better with A13 “T”:

But every time I read “next release” will come T to FP4.
So: Sorry, I don’t interested in e2.0. I need working basics…


Indeed, 1rst release of Android T upgrade on FP4 was “eventually” scheduled for… April 2023… (more than 1 year now).

Since then, the upgrade has been systematically postponed until the next update…

I guess it’s a pain to make it work correctly on the FP4. But better late than buggy :wink:

1 Like

What I don’t get is that T for FP4 exists in the dev/community branch for a while now.

@Manoj can you provide an explanation as to why it works on dev/community but on stable/official there is such a fundamental bug as the touch screen?