Hi AnotherElk, thanks a lot for your answer, however, it will not allow me to install an “alarm”. I get the following message:
. But this will not stop me using Lineage_MicroG
and one more thing: I can see how busy you are replying and helping everywhere in this forum - THANK YOU!
Have you ever tried running the Self-Check in Microg Settings? What does it show? If everything’s marked as OK in there, push notifications should work
Hello,
Late reply, but I just wanted to say that I upgraded to 17.1 today.
I have been using Lineage for microg since quite some time. I was still on 16, because I had a lot to do lately. I upgraded from lineage 16 for microg to lineage 17.1 for microg. No problem while upgrading. And no problem so far.
My phone was a bit slow these last months and apps sometime crashed (telephone app while phone ringing, which made me miss calls, or the clock app while the alarm was on…). I hope that the upgrade will do the trick, because I don’t feel like a clean install right now!
Time to time, I also have apps crashing (mainly PokémonGo) or app suddenly provoking a reboot (mainly Whatsapp). But this latest is quite rare (once a week) so I can live with it 
But phone app never crashed for me.
I’m running the official LOS 17.1 (with OpenGapps pico)
Thanks for your answer!
It’s been almost a week now and I still have some apps crashing. Not the clock app any more (so long…), but I had the phone app today again. I also had two other apps almost once a day.
I don’t really have reboots though. What happens on my phone is that the screen freezes (the first times I thought the phone was about to restart), and after a while I get a message saying that the app is not responding. I can either close it or wait.
So: the phone doesn’t reboot and I don’t have to force a reboot; the app doesn’t close by itself.
Just made a search on the forum and found out that the issue happens to others as well:
Sorry to be so late to thank you for your input, but I was reluctant to post a negative answer and I was still hoping but up to now, even after the latest Lineage-Update) it is the same message: “Fehler bei der Push-Registrierung”. The Self-Check in Microg settings shows all green ticks, so nothing there. Maybe it is connected to my other problem, when I switch off data connection after having checked my emails, and swipe it on again, it will often (or never, but I am not sure of that) not connect again unless I restart the phone. But as said before, I can live with that.
I don’t use this myself, but perhaps registering manually would be worth a try …
Thank you AnotherElk, it was worth trying. I did it two times, but after the last “#” the typed digits simply disappear and the screen is back to the regular telephone app. Finally I tried it without the last “#” digit, but then it said something along the lines of “wrong code”. But it is okay, I am very happy with my Lineage for microG-FP2 which I am currently using. What bothers me more is the installation of Lineage for microG on a new FP3 which I planned to get ready for Christmas. But this is another topic.
Just a quick update on my situation as it may help others.
As I won’t have the time to do a full backup and a clean install before the holidays, I tried the advice found here:
So I turned off the transition animation scale, the window animation scale and the animator duration scale. Don’t know if it’s a coincidence, but I have had only one or two app crashes in the last 4 days.
You don’t happen do have some sort of firewall installed? If FCM servers can not be reached, this might explain the problems?
No, I don’t have any firewall, thank you for asking. At Christmas I will see my daughter for whom I installed Lineage OS for microG on my former FP2, I will know if she has the same problem.
But it does not matter at the moment, I have a more urgent problem, I really bricked the new FP3 which I was preparing for another of my children. I made the mistake of doing step 4 “erasing all data etc” in the wiki https://wiki.lineageos.org/devices/FP2/install and now when I start in recovery mode to apply the LineageOS installing zip, I get the notice on my PC "
I am just working on defining what the situation exactly is at the moment, it seems that even a factory reset does not work any more. When I boot the FP3, I get this:
No reply but an amendment. I got Lineage OS on the new FP3 now, so it is not bricked 
But I could not install the Lineage-MicroG zip, (ErrorCode::kDownloadMetadataSignatureMismatch) … Installation aborted. But the regular Lineage OS zip was accepted. So am extremely relieved now, and I will go on trying tomorrow after work. AND I am going to copy this to the correct thread - this one here is the thread for my own FP2.
Hey folks,
not sure, if the thread is right here, move my post if not…
I tried to upgrade lineage for microg 16.1 to 17.1 using the method described here: Upgrade LineageOS on FP2 | LineageOS Wiki
My TWRP version is 3.2.3-0.
Upgrade went fine, but lots of my apps didn’t start (incl. whatsapp, firefox, osmand and others). Others did (firefox klar, signal) but sometimes only the first try after a reboot.
First, I tried to install lineage for microg 17.1 again using the built in updater -> same behavior
Tried to wipe cache & dalvik -> same behavior
Tried to go back to 16.1 via the backups I made (made 2, just to be sure). -> phone does not boot. I get the white fairphone-logo und nothing happens (waited for at least 30min).
Any suggestions where to go from here? What would make sense to try?
Thanks in advance!
Ok, solved it. FYI:
I wiped everything with TWRP, put Lineage for microg 17.1 (newest) on a SC-Card and flashed it with TWRP.
Everything seems to work, Apps are still there and work.
I was a little too euphoric, I guess:
At first, everything worked fine. OS itself still does, but the problem with apps that do not start is back.
Let’s take whatsapp as an example, the same is valid for other apps like signal or firefox. I see the following behavior:
Tried the same for signal:
Any suggestions?
At least I could restore my backup now by
So I have a (more or less) working phone again
I have no suggestion (never encoutered this error) except the hard solution:
Hope you’ll solve the problem,
Olivier
Lineage for microG is building again!
Got an update today 
Hello guys,
I installed the new update (lineage-17.1-20210327-microG-FP2) via OTA and now my FP2 is not booting anymore.
My current setup:
)The first time booting after the update was successful. However, the root permissions were missing. I then booted into TWRP recovery and reinstalled magisk (21.4) there. Now it does not boot anymore. I only see the LOS boot animation for minutes and nothing happens except that the FP2 gets hot.
Wiping Cache/Dalvik did not help. Also uninstalling magisk did not make any change.
Do any of you have any idea what I can try to get it to boot again? I would like to avoid reinstalling the smartphone.
Cheers,
knefl
