It seems as if updates newer than 20190823 have been taken offline to prevent further irritations. 5 minutes ago my secondary FP2 was not offered an update past that date.
Something I recently noticed (unrelated to the “no boot” issue with current builds):
When I was still using the official FPOS (Android 7), my FP2 would use Protected Management Frames when connected to a Wi-Fi with PMFs configured as “optional”.
Now (with LineageOS), when connecting to the same Wi-Fi, PMFs are not used anymore. And when I enforce PMFs on the AP, the phone won’t connect at all.
Did someone make similar observations? Are PMFs globally disabled in LineageOS for FP2?
I too run into the “non boot disaster” but round several corners I now managed to have a system back based on
lineage-16.0-20190823-nightly-FP2-signed.zip
which works so far. But by panicking around I managed to kill the function of some programs, so I decided I have to install from the scratch with the same zip (I have backups).
My question is whether I’m able to simply install from the sd-card (mobile) by TWRP, I would prefer that a lot, or do I have to do the sideload way?
I wonder whether they totally overshoot there at LineageOS currently.
With the 20190824 build something broke. That can happen. That was not even a week ago.
I guess taking the FP2 port off the automatic build process has started some further automatisms like the “The Fairphone FP2 is no longer maintained.” message. After a few days with the problem. When the maintainer is still around here in the forum (according to the forum software). When maintainers are all volunteers doing the development in their spare time.
I mean … can maintainers be on vacation? Can they be ill (hopefully not)? Can they have other stuff on their hands?
This handling of the situation doesn’t reflect well on the LineageOS project.
They can proactively declare a device not being maintained any more. If the maintainer gave them a notice that somebody else should take over. If there’s no sign of development for a long time, and contact with the maintainer fails. But not after a few days following a hiccup.
Take the device out of the build process, check, take the failing install files offline, check, but then try to contact the maintainer and give the whole affair some time to perhaps resolve itself.
Until @chrmhoffmann himself declares he stopped maintaining the Fairphone 2 port of LineageOS, or until the LineageOS project can present such a statement, I wouldn’t read too much into it and hope it’s automatisms not fully thought through at play here.
I’m on the latest Fritz!OS and there are no interesting events in the logs. Actually, I have the same problems with the WiFi (2.4 GHz) of the fiber modem which is plugged before the Fritz!Box, so it looks like a more general WiFi problem with LineageOS and/or the Fairphone 2 to me.