LineageOS building seems to fire on less cylinders than usual, so the new build for the Fairphone 2 is nowhere near it seems.
I don’t know yet whether I’ll still get to it when it’s there or just sit this one out.
Anyway, TWRP 3.2.2-0 is out (Nooooo, the nice 3-2-1-0 sequence is gone 
).
Hmm, the Fairphone 2 build is still in queue, but its up in the LOS Updater (in Settings).
Updater getting updates before they are built … what a time to be alive .
Other possibilities: OS is not on the current build? Updater is malfunctioning?
Hmmm … building seems to progress fairly fast despite there being only two instances building things, usually there were three instances in the past and a build took hours when I had a look … server upgrades perhaps? At this pace, there should be a build tomorrow afterall 
.
Hmm, perhaps its cause I use LOS + microG. They had it available since about noon of 4th.
That’s it. They forked the whole thing, of course they could build independently.
Update installed via TWRP 3.2.2-0 (Releases)
lineage-14.1-20180704-nightly-FP2-signed.zip (Changelog)
Security patch level: 05 Jun 2018 (Settings - About phone)
The following things work for me so far:
For things that might not work there’s a bugtracker.
I checked the changelog the last weeks. There was no change recorded except one. Does it in this case make sense to update every week? Probably not?!
Nobody is forced to update if the changelog indicated it wouldn’t matter for the respective personal needs 
.
I’m in TWRP regularly anyway to make a system backup, so I don’t mind updating LineageOS afterwards when I’m there anyway, and for me there’s updating Open GApps, too.
And I don’t like things not working when it matters, so I better test run some things I need or which were hinted at by others.
These LineageOS builds are built automatically without a beta tester process afterall as far as I see it.
Update installed via TWRP 3.2.2-0 (Releases)
lineage-14.1-20180711-nightly-FP2-signed.zip (Changelog)
Security patch level: 05 Jun 2018 (Settings - About phone)
The following things work for me so far:
For things that might not work there’s a bugtracker.
Update installed via TWRP 3.2.2-0 (Releases)
lineage-14.1-20180719-nightly-FP2-signed.zip (Changelog)
Security patch level: 05 Jun 2018 (Settings - About phone)
The following things work for me so far:
For things that might not work there’s a bugtracker.
Update installed via TWRP 3.2.2-0 (Releases)
lineage-14.1-20180725-nightly-FP2-signed.zip (Changelog)
Security patch level: 05 Jul 2018 (Settings - About phone)
The following things work for me so far:
For things that might not work there’s a bugtracker.
Short questions only as I never used open_gapps:
Thanks!
Using LoS 14.1 here on my new (and encrypted) FP2. I tried to install the latest update via the included updater, but that didn’t work. I don’t get a prompt to decrypt and the update doesn’t start. Is there a how to for encrypted phones and could someone point me there?
Edit:
Using TWRP 3.2.2. Where does the updater app store the zip file? I could just install it by myself.
Thanks,
Singu
There:
/data/lineageos_updates/
The last version of TWRP broke the auto update.
Thanks, manually installed the update. Were there important fixes in TWRP 3.2.2 or is it “safe” to use TWRP 3.2.1 then?
I would say, no issue to use the previous version until the fix comes.
Enjoy your FP2 with LOS!
Thank you !
(I just edited the topic title to make clear it’s about official LineageOS 14.1 here, while unofficial LineageOS 15.1 is over there.)
Digging up something old …
When I went through all the settings in 15.1 I found those here, perhaps they were there in 14.1 already? But doesn’t matter much, there will be a switch to 15.1 somewhen sooner or later …
Settings
This seems to have all the info about when each Google Play services module was last updated.
But beware … If they were installed with TWRP while TWRP didn’t have the correct date and time, those modules can end up with a last updated date in January 1970 .