I can confirm 16.0 encrypts, and TWRP 3.2.3-0 as expected can’t handle the encryption, so business as usual there.
Installing 16.0 with a data partition encrypted with LineageOS 14.1 to make it work with TWRP (complete Advanced Wipe in TWRP otherwise) doesn’t result in a bootable OS (which worked with 15.1), with boot attempts resulting in:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you’ll have an opportunity to restore any data that was backed up to your Google Account.
RESET PHONE"
… where RESET PHONE is a button, but does nothing.
The TWRP factory reset (Wipe - Swipe to Factory Reset) doesn’t help.
Wiping everything apart from system doesn’t help either.
Really reformatting system and cache to ext4 instead of only wiping before installing 16.0 doesn’t help either.
Installing via TWRP’s Install or via TWRP’s ADB sideload makes no difference.
With or without installing addonsu-16.0-arm-signed.zip makes no difference (I had included it in the install first and then checked again without it).
Seems 16.0 doesn’t like the old encryption … yet?
I know it’s supposed to be TWRP’s fault for not playing along with the new encryption, but 15.1 runs fine with the old encryption.
Thank you @chrmhoffmann and @z3ntu. I really think that your contribution to the Fairphone cause cannot be overestimated.
And while they probably won’t read this, the same goes for Fairphone’s own developers whose certainly frustrating struggle with the horrible challenges of G00gle certification comes with much less glossy spotlight, but deserves no less recognition. Maybe a Purple Heart would be appropriate for you folks.
First of all, thank you a lot @chrmhoffmann and @z3ntu!!! Looking forward to testing it.
I have the same question as @lklaus and the following: Any first estimates on the mobile network standby battery drain issue? How does 16.0 perform?
Fantastic news!
I read this after Fairphone’s statement saying they were discontinuing Fairphone 2.
Thanks to @chrmhoffmann and @z3ntu my Fairphone 2 (and my partner’s…) will hopefully still be in my pocket well after the planned 5 years (I’ve had mine since January 2016…).
Let me express how grateful I am for all this work you put in over the past two years.
After activating flight mode over night and deactivating it again in the morning, my phone didn’t connect to the mobile network anymore. (WiFi worked fine, but the network provider didn’t.)
Also, at reboot the SIM PIN was not requested anymore. I thus ended up without any mobile connection.
I’m back on 15.1 now, for the time being (also because I didn’t want to start from scratch with factory settings…)
I didn’t upgrade.
After encrypting with 14.1, I wiped data and formatted system and cache and installed 16.0 from scratch.
Next I will try to rm - rf data before installing, as wiping only deletes all the files, but leaves the (then empty) directory structure in place … at least for me, don’t know whether that’s intended.
Then I’ll try your idea and install 15.1 on the 14.1 encryption, then upgrade to 16.0.
(bold by me) I hope that nobody is bitten to death by bugs (pun intended)!
only the homescreen was reset (maybe also other things). Wifi credentials are still there.
