We are considering dropping OnePlus one bacon from the /e/ R upgrades. Despite our best efforts the device refuses to build! Developers are working on getting the other devices in this list 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 14 Oct Devices marked for Week 41 have been released
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: On track
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 if a fingerprint was set to unlock the device before upgrading it got lost post the upgrade. We have a fix for this and are plan to add it to the build before release to all stable build users.
All supported devices get the updates. The exceptions are devices where we have issues while building or are not working correctly with the newer versions of /e/.
The last premium Galaxy series, That you can repair by yourself … as a FairPhone !
but available everywhere in the world !..
(2x less efficient, 10x cheaper)
I was discussing this with the porting team members yesterday. We will check how to move all the nougat devices to newer versions of the /e/OS. In some cases the devices are too old and have issues getting built on newer /e/OS versions.
Nougat is good enought if it is easier for dev or maintainers, but
for some old devices, problem will be the /system partition size, even with Nougat
are we really not able to / ready to modify PIT ?
What I suggested to the team was to try what needs to be done to get some of these older devices working on /e/. The whole point of supporting such a wide range of devices is we get to cover devices from all locations and vendors.
It would definitely be easier to stick to a small set of devices which sell the most.
The downside of this is it promotes e-waste. Vendors will release new devices every year with only slight variations on previous models. It is business for them. On the other hand we all have our favorite devices which are now obsolete due to the march of newer OS versions.
At /e/ we hope to support devices as long as vendor support and security patches are available.
Working on the OS upgrades where possible is also a plus point for these ‘old faithful’ devices
Most of them are UI related. If possible , Yes we will fix and add them to the build before releasing. If not possible to fix in time it gets moved to the next build.