/e/ R builds have not been released. ETA for release of /e/ R v0.19 next week.
Releases are usually first sent out on dev channel and after a couple of days on to the stable channel. This time we have released most of the stable builds along with the dev as we had additional rounds of testing done.
In case v0.19 builds for your device have not come to your device OTA pl let me know in this thread, and I can have that checked out.
To understand difference between /e/ builds check this guide
Status: On Track
Week 43 devices were released on time last week
Release plan for /e/ R on new and supported devices
List will be updated in case the build fails for specific devices
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
Status: Slight delay
Release planned for stable s9 s9+ users who are still on oreo
OS OTA will not work for the dev Oreo s9 / S9+ builds.
Update will work only on the variant with ‘F’ in the device codename which is the international variant for e.g. SM-G960F
OS OTA will not work if the device is the Korean variant …denoted by the ‘N’ in the device for e.g. SM-G960N
Release planned in a couple of weeks. We had an issue where fingerprint set to unlock the device before upgrading got lost post the upgrade. Another issue was the dialer icon would move out of the dock post the upgrade. Fix being integrated to the build.
ETA after 2-3 weeks.
Status: Work in Progress
Nervuri pointed out an issue in the App Installer and even discussed and tested out the solutions the dev team proposed. He has shared a detailed analysis of the issue on his site.
An issue has been created to track the points raised by Nervuri
We genuinely appreciate such assistance in pointing out issues and flaws in the /e/OS or in its default set of applications. While the development team does routinely check for such issues a fresh pair of eyes helping out is always welcome. Will share updates on the progress in plugging these short comings in the /e/OS.
This post will be updated through the week