Great! Can it be installed “over” 15.1, or should it be a clean install?
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?
The Purple Heart is […] awarded […] to those wounded or killed while serving
(bold by me) I hope that nobody is bitten to death by bugs (pun intended)!
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.
You need to change keys. See here https://wiki.lineageos.org/signing_builds.html
If you don’t want to do this you need to install from scratch.
Does encrypted upgrade from 15.1 work?
I used TWRP to install the ZIP and OpenGApps on top of an existing LineageOS 15.1, without starting from scratch or doing anything else.
So far, the system works fine (except for Pixel Launcher, which keeps crashing).
Anything I’m missing concerning the keys?
Huge thanks for all your great work @chrmhoffmann and @z3ntu !
I thought you have to change keys when switching from official nightly to homegrown builds ?
Hmm - I probably just ignored the security warnings, at first
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…)
You cannot migrate from official nightly to user keys without the procedure I linked up there.
You loose system app settings if you do what you did, so I guess that explains that you have some random stuff.
Btw: @AnotherElk, did you do the user key change procedure when upgrading?
I flashed the image in TWRP over (unencrypted) LOS 15.1. No resetting of dalvik/cache.
Apps and settings all still there only the homescreen was reset (maybe also other things). Wifi credentials are still there.
I also had to reflash Magisk, F-Droid-priv. ext. and Nlp.
So far no issues with signing keys. I can imagine that this becomes an issue once we switch to the official release…
Camera Button does NOT work to start the App, but does WORK to take pictures in the app. Double pressing unlock button to start camera app works.
Location Services seems like G__%le removed the Battery Saving option
Wifi seems to take slightly longer to detect 5Ghz networks.
DNS-over-TLS is implemented in Pie
Huge thanks again for keeping up with the pace of Android upgrades
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.
I’m having this “sort of flight mode” also with LOS15.1, very annoying, at least it get’s away with manual rebooting the phone.
Thanks. Don’t forget the signing keys bit when going to 16.
I noticed that the adaptive brightness does not seem to work. Do I have to change some settings? Is anybody else experiencing this?
As far as I understand, I must have an Android Tree to generate the keys.
Do you mind publishing the script migration.sh? For me myself that would be much easier.
Rest seems to be rock-solid