Week 19, 2022 : Development and Testing Updates

Builds and Releases


Status: :green_circle: Undergoing Testing

The next major milestone for /e/OS is the release of v1.0.
With this, we will move out of the beta phase and release v1.0 builds for all users. This will not include Oreo or Nougat devices (refer to details in the Oreo and Nougat devices section below)

  • Milestone details here

  • Some issues in the gitlab may be marked confidential by their owners and will not be visible to all.

    :nerd_face: Issues get marked confidential as they contain user logs or user device information. At times when we are working on a new feature and not exactly sure if it will work, we mark it confidential during the development phase.

  • ETA for release 24 May 2022 :crossed_fingers:

  • The code name for this release is Alicante
    :nerd_face: We will not have a v0.24 as the build numbering will now start with v1.0

Answers to some queries around v1.0

  • The v1.0 release does not mean we will have no bugs pending in the /e/OS gitlab:disappointed:.
    Dev team will be prioritizing issues and will fix them. You can check the fixes coming as part of v1.0 in the milestone link shared above.
  • GSI builds will be available even after release of v1.0
    • Sources of last GSI release are available here

New Murena.io email IDs + hide-my-email + email filters

Status: :green_circle: Released

Check these guides for more information on

New devices being added, existing devices being upgraded

Check out the list of devices we will add or existing one that will be upgraded. These builds will come along with the v1.0

  • OS version will be /e/OS R


Status: :green_circle: Released

  • Release notes

  • Fixes and updates

  • This will be the last release before v1.0

  • OS versions released

    • R - dev & stable
    • Q - dev & stable
    • Pie - dev
  • OS version Not released

    • Oreo
    • Nougat

OS OTA Upgrade

s7 /s7 edge

Status: :yellow_circle: Testing

  • We are testing the OTA OS upgrade for s7 / s7 edge.
  • With the focus on v1.0 there is a slight delay here. Do not have an ETA on the release as yet.

Oreo and Nougat devices

  • We will try to upgrade devices where possible. Builds are failing for devices on these two operating systems. We may eventually have to drop support for devices stuck on Oreo and Nougat unless we get ROM Maintainers willing to build and debug issues for Oreo and Nougat
  • We had a request for log files for these failed builds. Checked and found, team does not retain log files. May be users who make unofficial build for nougat and Oreo can pitch in.

ROM Builders - Unofficial and Custom

  • A new Docker image has been released
  • If you use Docker for your builds, upgrade to this Docker build before running your custom-builds.
  • Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs
    • You will have to install git-lfs (sudo apt-get install git-lfs)
    • After completing a repo sync, you will have to run repo forall -c 'git lfs pull'

:nerd_face: Reason behind these changes:

Development Activity

Status: :green_circle: In Progress

A summary of issues dev team is investigating or working on

  • Bliss launcher upgrading and existing issue resolution
  • eDrive code refactoring to optimize the application
  • Updating Applications where forked …ongoing task
  • EasyInstaller to adapt to upgrade OS builds…investigation only
  • /e/OS S or Android 12 …porting activity will be planned after v1.0

This is a subset of what the team is working on. Most of these tasks are under development and testing phase. Some of the issues will be confidential and not visible to all users.


:loudspeaker: Roadmap 2022

:loudspeaker: Teracube 2e and emerald
Teracube users please note there are two different versions of the device now. 2020 released devices are classified as 2e on our site, and those released in 2021 are code named emerald. We have added a warning in the guides to help users. 2e guide and emerald guide.

: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.
  • Find details of what devices are available in which countries here eSolutions Shop.
  • In Australia we do not sell directly. You can purchase preflashed /e/OS devices from this site

:loudspeaker: Porting and New Devices

  • Efforts to port new devices continue and details will be shared once we have working builds available :crossed_fingers:

/e/OS Links


  • Facing issues with devices you purchased from us ? Send a mail with details to <helpdesk@e.email>


Telegram Channel

Social Media

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


This would be easier to do if you could provide

  1. A list of the devices for which builds are failing
  2. A tag or version number to use for attempting builds
1 Like

Pete, we stopped all Oreo and Nougat builds some time back. Also, you can pick up the last v0.23 code to build upon.
The point is not only going to be building for these devices as a one time attempt, it will also be to get a dedicated device maintainer for them to continue building them. We would need volunteers to take up the maintainers’ role for these devices. If there are any volunteers for that role, we can resume the builds for these devices.

1 Like

I did start to make such a list last week – it might not be fully accurate – but I will paste it here hastebin.

Edit the list is nominally devices listed at Nougat and Oreo – I do not include whether builds might have failed.


I do really hope there are some people, with the skills, to bump the Oreo and Nougat devices up to /e/OS v1.0 :pray:

1 Like

We need one maintainer per device. So I’d be veeery happy if someone w/ debugging skillz could be found for…

Samsung Galaxy Note 2 (N7100) :pray::pray:

@Manoj any news about R build for ginkgo? Just checking. :slight_smile:

ginkgo is there in the list of devices moving to R and coming along with v1.0

1 Like

Great news, thanks! I assume v1.0 will also include ih8sn, so great opportunity to test without magisk at the same time.

@Manoj, all Nougat builds are gone. :scream:


Thanks for raising this. Have asked the team to check and restore them ASAP

1 Like

Hi @Vance, firstly, I am not certain if the list I made is totally representative of all the devices under threat. clarified below. For instance, quoting from Info about Samsung Galaxy Note 2 (3G) - n7100 we see at the foot of the page

Maintainers ⚈ /e/OS Build Team.

Edit, (see following post) not an indication of ongoing support.

I did a little research on the device:

Without the device a builder might get stuck. With some community participation a device owner might be able to do some work on this subject, Working with proprietary blobs | LineageOS Wiki, to see if the device tree could possibly be updated for pie. I do not know if this was already attempted, and possibly failed. More research required.

I have an interest in at least exploring the concept of “Community device support” – it is yet to be seen if this would be acceptable to the /e/ dev team!

@Manoj the job of providing fuller information on my earlier list is proving hard for me (I will continue !) Regarding the above quoted Maintainers being the /e/OS Build Team would it be possible to produce a slight fine tune of my list with something a bit like:

  • /e/OS Build Team can continue to support.
  • /e/OS Build Team has insufficient support ?

@aibd Unfortunately all the nougat and Oreo devices come in this category.

As mentioned, in the initial post if we get a dedicated maintainer we can start the support for that particular device.

1 Like

Has VoLTE been added yet? I just got a message again that I have until July 1 to switch to VoLTE or I will have to drop /e/ and go another route…

Metro: Urgent! Enable VoLTE on your phone by July 1, 2022 to avoid service issues. Visit our support page for instructions on how to update your VoLTE settings: metro-tmo.com/volte1 .

1 Like

Depends on the device. You didn’t specify.

1 Like

Samsung Galaxy S9+

Another thing that would be nice to have, which not sure if it’s related, Wi-Fi calling?

And I guess the feature request I opened for Samsung SmartView (MiraCast)

Yes please add VoLTE

Mine is Redmi Note 4 Mido.

In the US it seems … I think you might want to contact support in this case.

VoLTE has been around since early 2018 on S9/S9+