Week 48 : Development and Testing Updates

/e/ R rollout

Status: :green_circle: On Track

  • Last week we released the builds for week 46 and 47.

    Builds that Failed I have moved all the devices that failed to build to Week 52. This is the list of devices that failed to build

    Xiaomi POCO F3 / Redmi K40 / Mi 11X (alioth) , Google Pixel 4a 5G (bramble) , OnePlus One (bacon) , Google Pixel 4 XL (coral) , Google Pixel 4 (flame), OnePlus ‘8T’ (kebab)

    We are facing an issue with devices which came out on Android 11. The team has recently added some technically sound porting experts. Feel confident that they would be able to crack the issue with these devices.

  • Check out the Release plan for /e/ R on new and supported devices

    List gets updated when build fails for specific devices

    :information_source: Installation Tip for /e/R

    Devices with Stock 11 ROM should flash the stock ROM first before flashing /e/ R .
    Pl note this will wipe out your existing data. Take backups if required.
    Manual upgrade is required as the default Updater application does not upgrade the OS and on detecting a different OS tends to block the installation. Read the next section for details

    To find your device codename you can run this command in the console of an adb enabled PC with you phone connected via a usb data cable

    $ adb shell getprop ro.product.device

  • One side effect of this release schedule is that we would be identifying devices that can be dropped from our list of supported devices.

Update 3 Dec Week 48 devices have been released.

v0.19 release issue on S9 / S9+

Status: :yellow_circle: Work in progress

An issue was reported by some s9 /s9+ users on stable builds. We stopped the releases for these particular devices when the user feedback started coming in. As of now we have received 3-4 user complaints.

  • The reason we identified for the issue is that some traffic was not redirected to the correct docker image during a maintenance cycle. This unfortunately resulted in the incorrect code being pushed to user devices. Team to work on action to avoid such issues in future.

:information_source: Advise to users impacted by this particular issue: Pl write to helpdesk@e.email with all available details

OS OTA Upgrade Testing

Status: :red_circle: On hold

  • Based on the previous issue the release of the upgrade code is on hold

Apps Store updates

Status: :green_circle: On track

A new version of the apps store is undergoing testing. This is the list of changes coming as part of the new version

  • Integrated Search Fragment with Google Play API
  • Resolved multiple memory leaks
  • Switched to the latest APIs, libraries and removed all deprecated code
  • Layout and theme adjustments to the UI to improve UX
  • Improved memory and performance efficiency
  • Major application refactoring to modularize code for speed and scalability
  • Code is still being tested and will undergo changes based on the test results.
  • There are other issues opened separately so we can track the points shared by Nervuri in his analysis. Post the current development and testing developers will take up these issues.
  • These fixes should be available with the next build …v0.20


Status: :green_circle: On track

More issues will be assigned to this release for v0.20. ETA as yet not decided.

  • Track progress here

Easy Installer update

Status: :green_circle: New version released

A new version of the Easy installer v0.13-3-beta has been released… The change log includes

Refactor user interface related to flashing device

  • Refactor Configuration file
  • Handle “Too many devices detected”
  • Update version number to v0.13.3-beta
  • Fixed e-mail registration API Url
  • Update Russian translations
  • Update German translations
  • Update Dutch translations
  • Update config file for arch-linux build

Thanks to @steadfasterX @Wildermuth_F @Edoardo_Regni @sprainbrains @vincent.bourgmayer and Israel Pereira for your contributions

This post will be updated through the week

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


What is the status of the Q and R versions? Are the various problems being fixed?

Hi @contre as a member of the testing team you would be one of the first to know when the issues are fixed as they will be released for testing.


Add Oneplus 8T ‘kebab’ to the list :wink:
I hope that the problems can be fixed with the build/Android 11

1 Like

Thanks for pointing that out. Have added ‘kebab’ to the failed builds device list.

1 Like

Is there any news about the OnePlus 9 Pro build state?
If I missed a thread, please link it, thanks :slight_smile:

When you take a look at the release page you will notice that it was moved to week 52. This essentially means that the build has failed, most likely due to issues with android 11 out of the box. :thinking:

Thanks for replying. I wasn’t sure, if there’s anything known about.
I’m aware about the general information about week 52 and so.

Is there anything I can help with, maybe testing or something else?