v0.19 : To be released
Status: On Track
Testing was started on 23 Sep. Release on dev channel to planned this week.
List of issues resolved
Pending for closure -
Pending issues will be moved to the next milestone.
To understand difference between /e/ builds types check this guide
/e/ R rollout
Status: On Track
Devices previously scheduled for release in week 37, 38 and 39 devices will be released this week
Issues detect with the builds on the following devices …team working on finding a resolution to the issues.
bramble, alioth , bacon , coral , flame , kebab , lemonadep , redfin, sargo
There is a possibility we may not upgrade OnePlus one
baconto /e/ R…despite our best efforts the device refuses to build. Efforts on to get the other devices to build.
Pl note these are device codenames.
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
- Release plan for /e/ R on new and supported devices
Update 8 Oct We have released the week 37, 38 ,39 and 40 devices The release plan has been updated
List will be modified in case builds fail or if issues come up during the build process
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
OS OTA Upgrade Testing
Status: Due for release
- 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
This thread will be updated through the week