12 May Update The OTA OS upgrade testing from /e/ Oreo to /e/ Q on the S9 was successful. Will share details of the steps in the documentation we will release for this. As it was a sideload there was no data loss. To be honest it was a test device and all I had were the default apps with a couple of ID’s . All the same the data as retained across the upgrade.
Work will start on adapting for more devices soon.
Any testers available We would like to have a few users willing to test the S9 upgrade. Anyone interested ? You should have the /e/ OS oreo build on your S9 and ideally it should be a test device. Let me know in case you would like to help test the OTA upgrade for the S9.
Check out this post with more details
We are starting the customization of the source code for Android R soon. No ETA’s as yet but it took about 2-3 months for the Q customization which gives a rough idea about the time lines… New device additions
Starting from week 21 we will be adding a set of devices to the supported list. I will share the device names as we reach the ETA’s . The best part in these devices is we have dedicated ROM Maintainers for them.
As mentioned in the initial post I did not find any data loss after the sideload. I did not do any wipe or format it was a direct TWRP sideload using the adb commands. You can also do a sideload through the TWRP screen >> Advanced >> ADB sideload and on the PC you run the adb sideload commands.
We will share a document on how to upgrade you can follow that when it comes out.
It seems like Google abandoned it’s naming scheme since “Android 10”. So no more “Sweets” nor letters at all. From Android 10 on it’s just “Android 11” and it’s follow-up “Android 12”. You should get used to that too
Although this would bring up some altered naming for the /e/-OS releases too.
How about just restarting with “A”?
I estimate it will be a few years until that could lead to confusion, and then somebody smart would say “Haha! That letter could actually be confused with this older Android version we had in Stone Age!” and we would all smile about it for a moment and just get on with it .
I would actually support that.
You just made it sound at first like Google’s change of mind concerning letters and sweets should somehow force /e/ to make a change in the current /e/ version string, a necessity to follow Google I don’t quite see that strongly. And then I just gave a pragmatic example how to deal with going beyond the letter Z, I don’t pretend it would be awesomely clever, it just wouldn’t break anything either.
Somebody in Redmond is taking notes just now for when they need more ideas on how to annoy all the non-paying Windows users away to Linux to concentrate on what they really make money with nowadays .