Week 33, 2022: Development and Testing Updates

Builds and Releases


Status: :green_circle: Testing

ETA for release: To be decided

Issues fixed

More issues will be added or removed from this list in the next couple of days based on the progress in the testing.


Status: :green_circle: Released

  • Released for stable and dev builds on R and Q
  • Release Notes
  • Fixes
  • The following builds failed

R : bacon - guacamole - lavender

Q : bacon - davinci - marlin - sailfish - surnia

  • Team working on building for these devices. Will update as to when these device builds can be released

For details on future releases

Check link here


  • v1.2 available here
    • Sources available here

OS OTA upgrades

Status: :green_circle: in Progress


  • Samsung s9 / s9+
  • Samsung s7/ s7+


  • Samsung s8 /s8+
    • Pie to S OTA upgrade
    • ETA Sep end :crossed_fingers:
  • FP3
    • Q to R OTA upgrade
    • ETA not available
    • Will be planned after the release of the s8/s8+ OS OTA upgrade

Volunteer testers required

  • We are looking for volunteers to help test these OS OTA build
  • Check the post here for details.
  • Thanks to those who have already volunteered.
What we mean by OS OTA upgrade- Click to expand or close

:nerd_face: OTA OS upgrade means the upgrade to a higher OS level. Updates will be delivered Over the Air (OTA). The OTA upgrades are available on official builds only. Users who have unofficial or custom builds will not get the notification to install the upgrade build. They will have to manually download and flash the Q builds once they are released.

Easy Installer

Status: :green_circle: Released

macOS added

The macOS install guide available here for details

New devices added

The Easy Installer now supports 16 devices. Including

Vendor Device Name CodeName
Google Pixel 4 flame
Google Pixel 4XL coral
Google Pixel 4a sunfish
Oneplus 7T hotdogb
Oneplus 7 pro guacamole

/e/OS S

Status: :green_circle: Development and Testing

  • 70+ devices planned for /e/OS S or Android 12 upgrade.
  • Release will be in monthly batches of 20 devices.
  • For device details check this list for the device names
  • More devices will be added for upgrade
  • Please note we have as yet not opened up the code of /e/OS S to all users as the addition of patches and testing is still in progress. Attempts to build by forking will result in errors.

Unofficial ROM build refer the section ROM Builders - Unofficial and Custom

Section in Forum for build feedback

Have added a section on the forum where users can share their comments and feedback after a build is released

  • Feedback for v1.2 can be read and posted here

Recent Documentation updates

ROM Builders - Unofficial and Custom
  • A new Docker image has been released
  • 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:

Due to the large size of the android_prebuilts_prebuiltapks we have switched to using LFS, and now you will need to refer to android_prebuilts_prebuiltapks_lfs

We will publish some documentation around this soon.

End of official support for Nougat, Oreo and Pie 😞 For Pie, Oreo and Nougat the official /e/OS support draws to a close.

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.
  • 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: Murena One released
A phone from Murena with /e/OS installed has been launched and is available for purchase. Check the device specs here

Expect more device releases from Murena in future :grinning:

:nerd_face: Murena is the brand name and /e/OS is the operating system.

/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


Tank you again for the update.

Is it possible to add the versions in the status of the OS OTA upgrades.

I have read in some other comments that the OS OTA upgrades are about specific versions of the OS OTA upgrades.

I am waiting for the FP3 pie->Q OS OTA upgrade.

I have bought my FP3 in the /e/ store with pre-installed pie. If there is no FP3 pie->Q OS OTA upgrade comming then I have to make a plan.


You will have to make a plan.


I’m quite confused.

I’m currently on v1.1 on a Moto G (5S)

e_montana-userdebug 11 RQ3A.211001.001 eng.root.20220629.061054 dev-keys

I also dowloaded the 1.2 beta2 build, but not yet installed.

Now I see this v1.3.

I expected a v1.2 for my phone before the release of the v1.3, but evidently this is not the case.

What are the plans for /e/ update, for phones different from FPx and Samsung Sx ?

You might check out, @nottolino, if “Access to /e/OS test channel” is on (inadvertently) as this might explain it.

Settings > System > Developer options > Scroll to very near the bottom (item above AUTO-FILL > Access to /e/OS test channel

There isn’t even a plan yet for the FP3 upgrade … so let’s speculate :wink: .

Not inadvertedly, but on purpose !
After setting that option on, I was afraid to test the v1.2. I realized I’m not in the position to risk malfunctioning in my daily driver

If you are hoping for regular dev channel 1.2 I would expect Testing channel must be off.


Yes, you’re right, @aibd. After turning that off, I was immediately proposed the 1.2, 28th July.
Thanks once more

Bonjour Manoj

Savez vous où nous en sommes pour les les versions qui ont échouées? en particulier pour la version lavender?
merci pour votre réponse et pour votre travail

J’avais lu ça… Wait and see.

Comme mentionné dans le post initial, quelques constructions d’appareils ont échoué. J’attends une mise à jour de l’équipe mais je ne l’ai pas eue car hier était un jour férié en France comme en Inde. J’espère recevoir des mises à jour aujourd’hui.

Traduit avec Deepl. Toutes mes excuses pour les éventuelles erreurs de traduction.

As mentioned in the initial post, a few device builds failed. I am waiting for an update from the team but did not get it as yesterday was a holiday in France as well as India. Hope to get some updates today.

Translated using Deepl. Apologies for any errors in the translation.


Oh, this is really bad news. I was also waiting desperatly for this OTA update since I do not know a way to upgrade with locked bootloader without losing data… (eCloud-Backup does not yet work, right?)

@Manoj : Could you change that also in the overview? I was always reading the overview in hope that the OTA upgrade meant from pie which was the original FP3-version, which was also sold from the shop.

hi @chogo I have updated the information in the initial post

1 Like

A build team member is checking the reason why some device builds failed. Will update if there is any progress

1 Like

Hi @Manoj,

Do you have some news about the easy installer for the Fairphone 4 ?


Still under development and testing. Will update when there is something positive to report.

1 Like

Merci Manoj pour vos réponses

Thanks @Manoj for your reply :slight_smile:

1 Like

@Manoj Will v1.3 update the browser and the system webview again? Unfortunately, v1.2 still uses versions 100.x, which are already quite outdated and contain security vulnerabilities.
Do you know whether an update via App Lounge will be implemented so that the browser and the system webview can be updated independently from /e/OS itself?