Week 21 2024:Development and Testing Updates

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


v2.0 :new:

Status :green_circle: Released

Release Notes
User Feedback and voting

:fire: BlissLauncher v3 code opensourced :fire:

  • Some of the issues pointed out with the v2.0 release included
    • Redmi 8/8T ginkgo builds failing - the community device build has been recalled. Team will check on the issue based on bandwidth
    • Issues with 2 button navigation - Google has removed 2 button navigation from AOSP code. LineageOS is reverting it. The /e/OS dev team is of the opinion we should also remove it from our code to avoid issues.
    • Various issues reported in the User Feedback thread are being shared with developers. Response will be shared on the forum.
    • For serious issues first please check if other users of the same device and on same build are also facing the issue, before creating an issue with logs in the Gitlab. Enable /e/OS telemetry in Settings >>System >> Developer Options >> Enable /e/OS Telemetry for detailed logs.

Upcoming milestones information

Ongoing development tasks
- Easy Installer to be updated to flash /e/OS T builds. ETA to be planned

Murena 2 specific information

  • Back cover’s received from vendor. Sending out the same first to the crowdfunding backers. The option to purchase the backcover added to the website.
  • User facing issues with the camera focus can send in the details to the <helpdesk.e.email> ID for a resolution.
    Update 5 May: Back covers for users in France should have all been sent out. For others it should start on thursday 30 May.

Previous 5 releases & user feedback


Recent updates
Official builds not available for
  • 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
Support dropped for
  • Galaxy M20 m20lte - No dedicated maintainer upstream or with /e/OS

  • 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
  • Galaxy M20 m20lte

    • Build issues. No dedicated maintainers available.
  • 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.
  • 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.

Devices with MINIMAL APPS builds
  • Moto E5 Plus ahannah
  • Moto E5 Plus hannah
  • Moto E5 Plus rhannah
  • Moto G5 cedric
  • Moto G5S montana
    All devices ran into out of space error while building. Issue was resolved using the MINIMAL_APPS build
What MINIMAL_APPS flag means

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. In the case of certain devices we are unable to build with even the minimal /e/OS build.


: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

Murena cloud NextCloud version upgraded

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



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.1
To Plan
  • Samsung: S7/7+ : R(A11) → S(A12)

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

  • Samsung: S9/9+ : R(A11) → S(A12)

    • ETA - probably with v2.1 :crossed_fingers:
    • For devices with community builds on R we will move them to S but that will require the users to manually install it. This may involve data loss and backups should be taken if required. Official or stable builds get OTA OS upgrades
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


No more multiple OS versions
  • Support for /e/OS Q is being dropped for most of the devices.
  • 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.


Misc information

Read Gael 's roadmap for 2024

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


Ooof… I really hope they consider keeping in 2-Button because 3-Button is awful, and only Gesture is worse, in my opinion.

1 Like

"Official builds not available for
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

If I get this right, the stable version of these devices will be discontinued?!

Is there an option to switch to the dev/community version without dataloss?? Particularly the upgrade von R to T seems a challenge here…?

1 Like

Multiple users on devices which have not been upgraded have reported issues with wifi connectivity getting lost - icons showing no signal but still able to browse.

One of the solutions available is to upgrade to the latest builds.

There is an issue around this on gitlab as well, users can add their device and build details on that. Do not have any ETA on the resolution for this for now.

Similar Issues on the forum:


Thank you.
I found an updated version of the e/OS for my old S4-mini.
I will check.

Any news on the Murena Tablet?
I do not see it anymore in the startpost…

No, there is no news. In case you were able to listen to the v2.0 live launch event, you may have heard Gaël mention that the search for a partner to manufacture the tablets is still on.


Interesting I always thought you will colaborate with someone. Murena is getting more and more into Hardware :muscle::muscle:

I guess same approach as with the Murena 2 is not possible, else you would have allready tried it…

@Manoj bring back connectivity.ecloud.global:80 returning 204s and things will work again. Some users are stuck on versions and cannot upgrade

1 Like

Pl can you raise an issue around this if not already done and share the ID. I can pass this on to the team.

the same gitlab issue you quoted up the thread, see link - https://gitlab.e.foundation/e/backlog/-/issues/7975#note_544102 - thanks

Hi @Manoj
Would it be possible to jump to the latest version if some of the previous updates were skipped?

Thank you

The current advice from the developers is to go step by step, build by build, and not skip previous builds. Some of our users have experienced issues when jumping straight to the last builds.

1 Like

Had a long chat with the developers and various team on this. This was the response:

  1. Issue is for builds having the old captive portal ecloud links, which are reported as non-functional by the users.

  2. It works on the builds have the murena backend.

Since it works on newer builds any ways, I don’t think the mobile team can do much here.

The recommendation is for users to update, in some cases users are on versions as old as v0.12… We do not maintain such old version. The user can also upgrade to v1 build at least…

It is risky for them to stick to that many old versions as they are skipping a lot of security updates. The list of security updates being missed can be seen here


thanks for following up. I don’t know the amount of devices actively in use that are ‘stuck’ and do not have an upgrade path.

For anyone unable to upgrade, there is captiveportalcontroller, but it needs adb assistance, at which point a user could use adb itself to set the murena urls.

Edit: that said, upgrades of major versions have migration risks. /e/ up until today has no easy user backup & restore to give peace of mind for major upgrades. There’s little to no downside for ops to answer on that url. By the amount of users feedback it seems to be too early to sunset the url.


I understand. Thank you @Manoj

Dear @Manoj is there any plan for those who use the stable version to change to the community /Dev version?

The Easy Installer should flash the dev build for these devices. The stable builds were discontinued as we did not have dedicated maintainers for these phones.

But it has to be said that at least for those using a Oneplus8Pro this means reverting to stock OS, flashing Dev and losing all data…