Test build OTA update failed to install on Oneplus 3T; twrp couldn’t handle the encryption and prompted a factory reset. That was a surprise!
EDIT: Started from scratch with fresh install of test build. Checked settings, phone not encrypted. Took the OTA and it failed again with unsuccessful encryption error, prompted factory reset. I couldn’t find the right steps in twrp this time to get back to the system.
In twrp “E: unable to decrypt FBE device” remained at the top of the output from the wiping actions, but installed test build again ok. I’ll leave it there for now.
For mido everything is working, i couldn t test functionalities using simcard (sms, telephone, mms …) or ecloud but all the rest seems to be working, even the OTA-update which seems to downgrade the device back to nougat… I will upload the testplan hopefully tomorrow
To read here in this forum like a prayer wheel that the Lineage for the S7 or S7 Edge does not provide an official build is pathetic, because other developers are obviously able to release continuously working ROMs for these “Premium” /e/Phones, e.g. => Builds for herolte.
Again and again you can read about what is planned for the future, what might be sometime in the future. Many answers are like text modules from a manual for first level online supporters. But the present does not look very pleasant.
/e/ has so many plans - yes, interesting ones and valuable for the /e/ project - but the small /e/ team with a minimal financial budget gives the impression that his list of priorities is in a mess.
The latest plan to support as many devices as possible, and its only unofficial /e/ builds, I consider counterproductive.
Your Lists of UNOFFICIAL /e/ builds (Part 1) + (Part 2) are longer than the official /e/ list, with over 50 of them working more or less well with e-7-nougat ROMs. If /e/ is not able to update these 7-nougat devices, they should be removed immediately from the the official /e/ list. Quality rather than quantity would be a more serious strategy for /e/.
Indeed I didn’t give you a precise release date because I can’t garantee you the precise date will be the good one (and we don’t know it anyway). I know it’s frustrating to have “in the future” but… at least that’s true.
When we look back at what have been done each year, we can see that a lot of things evolve in a good way so don’t worry, you will have your upgrade in the next couple of months for sure (/e/ Nougat will be deprecated in Q4 2020 so the upgrade will come before this).
Anyway I just asked to the one in charge of this in order to have updated informations and he answered that almost everything is ready for an Oreo test build. Expect it in the following weeks (again, no precise date). For the stable version on phones sold by /e/, it will of course be later (via OTA) because it will need further testing.
I think that what has been achieved is a lot for a quite little team. They are well organized and we can’t say it’s a mess. Yes it could be better, like everything I guess, but things evolve quickly in a good way and that’s why I think this project won’t die tomorrow.
This plan doesn’t impact the dev/maintainer team (see it more like a community plan), so it won’t change anything, except that the number of updated unofficial builds will be higher, and the list of requested devices will finally be listened to (yes it won’t be official builds but it’s much better than nothing).
I invite you to look at this topic, that’s precisely what will be done.
Hm, on my mido I have exactly a problem @chrisrg described:
So after the update is completed and phone reboot is performed, the phone wakes up and encryption error screen is shown with only “Reset phone” option available, and I’m not using encryption on my phone.
Build installed prior the update is the unofficial mido test update (e-0.9-p-2020070861902-test-mido.zip)
This is a bug. The nougat or downgrade versions should not be showing up on the Pie test builds. Ideally the updater should check the update version before adding it to the screen. Created a bug for this and follow up with the dev team.