Week 26 2024: Development and Testing Updates

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



Status: Testing :green_circle:

Issues to be fixed

ETA: End of June or early July :crossed_fingers:


Status :green_circle: Released :new:

Upcoming milestones information

Important Device support information

:point_right: /e/OS R support to be dropped with v2.2

:nerd_face: Reason why /e/OS R builds have been stopped:
Google has stopped security patches. LineageOS has also dropping support. For most of the older devices vendors would also have stopped vendor patches.We would not be able to continue support as it would require backporting security patches which will require dedicated resources and is not a viable long term solution. Users are advised to upgrade to newer OS and builds where available. We will be evaluating which of the devices currently on /e/OS R can be updated to S or T. The builds if released would require manual installation and data backup. Except for the s7/s7+ and s8/s8+ which would be getting OTA OS upgrade builds with v2.2

:point_right: Devices to be upgraded

  • Devices getting /e/OS T build (manual upgrade + may require stock to be flashed + data back to be taken )
    • bardock —already has a T build. R and Q will be removed.
    • bardockpro —already has a T build. R and Q will be removed.
    • chiron —already has a T build. R and Q will be removed.
  • Names of devices which will get a T build will be added to this list

:point_right: Device being evaluate for continued support (currently on /e/OS R)

FP2 , X00P , X01AD , X01BD , YTX703F , YTX703L , a5y17lte , a7y17lte , addison , ahannah , albus ,cedric , d800 ,d801 ,d802 , d803, d850 , d851, d852 , d855, dream2lte , dreamlte , ether , f400 , ginkgo , hannah , hero2lte , herolte , hlte , hltechn , hltekor , hltetmo , jactivelte , jasmine_sprout , jason ,jflteatt, jfltespr , jfltevzw , jfltexx , jfvelte , klte ,klteactivexx , klteaio, kltechn , kltechnduo , klteduos, kltedv , kltekdi , kltekor , lavender ,lithium , ls990 , montana , obiwan ,oneplus3, platina , rhannah , s3ve3gds , s3ve3gjv , s3ve3gxx ,scorpio ,shamu, sirius ,suzuran ,twolip ,victara ,vs985 , wayne ,whyred ,x2,
z3, z3c , zl1

  • Most of these devices marked for being dropped from official support. We are checking how support can be continued for the FP2.

To check your device codename refer this table

The OS OTA build coming with v2.2 for S7/ 7+ and S8/ 8+ will upgrade these device from R to S

Devices we will not support will be marked as legacy in the documentation and not receive any more builds

Support to continue for these LG devices

  • h830, h850 , h870 ,h872 ,h910 ,h918 ,h990,ls997 ,rs988 ,us996,
    us996d , us997 ,vs995
  • We had mentioned in one of our previous threads that support would be dropped. The issue with these devices was resolved and support will continue for these LG devices.

:nerd_face: Reason for builds to be dropped include build failure, no dedicated maintainer to debug. /e/OS users with ROM Maintainer skills are welcome to take up the task of maintaining these devices.

Ongoing development tasks
- A web based version of Easy Installer to be released replacing the existing desktop version. At present the team is working on the development and testing of this tool. Will share ETA for release.

Murena 2 specific information

  • Back cover’s received from vendor. Sending out the same first to the crowdfunding backers.Back covers for users in France sent out. Out of France orders were sent starting on Thursday 30 May. The option to purchase the backcover to be added to the website.
  • The camera out of focus issue where reported, has been identified as a hardware issue. We do not have spare parts to make replacements. Send in your phone details to the helpdesk@e.email ID and the team will offer a refund with discount vouchers for future purchases.
  • The Murena 2 saw heavy demand and is now fully sold out. We are working hard to create a new and even better model in our Murena line for our users.

Previous 5 releases & user feedback


:point_right: ASUS does not provide an official method to unlock their devices. We will be adding a note to the effect that the install guides are only for those who have devices which are already unlocked.

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. The stable builds for any of these devices if still being released will be stopped. Users will then have to switch to the dev branch. They can do so by flashing using the EasyInstaller. This would include data loss so take backups if required.
      • 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
  • Nothing Phone(1) Spacewar
  • Motorola Motorola Moto G7 Play channel
  • Google Pixel XL marlin
  • Google Pixel sailfish
  • Google Nexus 7 2013 flox
  • LG V30 (T-Mobile) h932
  • LG v30 `joan
  • Galaxy M20 m20lte
  • All Nokia devices
  • Huawei - no official unlocking method available
  • ASUS devices - builds for devices which are already unlocked. No official unlocking method available.

: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
  • Download available here

    • Sources available here
    • version is /e/OS Q (A10)

    :point_right: The v1.17 GSI build is the last build and is on /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

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

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

  • 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
Testing 🆕
  • Samsung: S7/7+ : R(A11) → S(A12)
    • ETA v2.2 :crossed_fingers:
  • Samsung: S8/8+ : R(A11) → S(A12)
    • ETA v2.2 :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


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


Hello Manoj,

Murena 2 specific information

  • The option to purchase the backcover to be added to the website.

When will this option finally come to buy the back cover in the shop. I have a murena 2 waiting for it since Feb and still I’m not able to buy the back cover…

I have mailed support and they also do not state a clear date…

Your efforts to keep the Fairphone 2 alive are very appreciated :+1:
Hope it’s gonna work.

Yes, although it’s a bit surprising the FP2 gets singled out like this.
The Fairphone 2 is a 32-bit device. The internet wants to tell me Android 12 and newer are 64-bit only.

There are links in the Fairphone forum to https://lineageos.org/Changelog-27/#deprecations and to https://lineageos.org/Sunsetting-LineageOS-18.1/, which seem to have some details on why Android 11 seems to be the end of the road technically.

In my understanding continued support for the Fairphone 2 would either mean to overcome these technical limitations and get newer Android than 11 on this 32-bit device somehow (which nobody did so far), or to backport new security patches to Android 11, which LineageOS deemed unfeasible to do (see the sunsetting article link above), while one different project seems to do this.

We’ll have to see what the plan is and not get our hopes up too high, I suppose.

The sales team has a few available and should be marking availability on the website soon. Will update if I get an ETA from them.

I suppose this clears the way for /e/OS U (android 14)? Any news on that?

Yes, it is WIP. No ETA as yet. Will share dates once I get them.


@Manoj , will this PR that looks to have been forgotten during 2.1 merged with the 2.2 ? FP5: Set up double tap to wake (!27) · Merge requests · e / devices / android_device_fairphone_FP5 · GitLab

Thanks for pointing that out @Dremor. On further testing, we found the issue was not being resolved by the fix. The comments in the MR have been updated. We shall assign a milestone to it once we have it.

1 Like