I tried to install microG with Magisk which only kind of worked: as the f-droid version of the German Corona Warn App now detects the presence of Exposure Notification, it refuses to use it’s built-in version. But as the installation of microG with Magisk doesn’t come with signature spoofing, the version of the Corona App from PlayStore/aurora doesn’t work either. So I removed microG again and wait for a 17.1-build, I guess. Or does nanodroid provide signature spoofing? In this case I might try it.
If the problem is related with signature shooting you forgot to install the nanodroid patcher module.
The only difference between vanilla lineageos and microg one lies in predone patching. Before nanodroid (may the developer be sanctified by the pope) existed I used to use only prepatched ROMs, otherwise features missed
Is it just me or had other people the same experience? I don’t know if it’s the correct name for the options. Under “Digital Wellbeeing” is some “Night Mode” (“Schlafenszeitmodus” in german). It can set your display colors to grayscale when it turns on. It goes on at the time I set. But there is no grayscale and yes I had turned it on.
Yes several people have reported an issue about screen color settings ; I opened a ticket on the official bugtracker: https://gitlab.com/LineageOS/issues/android/-/issues/2920
By the way @dk1978, maybe put the official bugtracker URL in the first post would help people report issues more clearly and would help you track them, what do you think?
2 Likes
I shied away from this because there are patching instructions on the site that seemed too error prone for my daily used phone.
I’m coming from a SGS5 with Linage and used the Bluetooth tethering sometimes when my internet has problems. My PC doesn’t have Wifi, but a Bluetooth dongle, so I used Bluetooth tethering to share my Phones internet.
AFAIK this needs to be activated in some kind of linage config file before build, can this be done or is it a Fairphone-3-Issue ( i never looked, if the stock has Bluetooth tethering, since i directly moved to linage)?
If it’s a Linage-Issue, should i create an Issue on Gitlab?
Ok, I’m afraid I have to go back to stock ROM or /e/. DB Navigator for example doesn’t want to play along when I try to book.
“There is no valid certificate on the device to establish a secure connection.”
At which point did that happen? I tapped on “zur Buchung”, this would work. But i don’t want to buy a useless ticket 
Interesting. Exactly when I tap on “Weiter zur Buchung” the pop-up appears.
Do you have certificates in “Einstellungen - Sicherheit - Verschlüsselung und Anmeldedaten - vertrauenswürdige Anmeldedaten?”
That’s long
The left “System”-Tab is populated, the right " Nutzer" (user) is empty.
Ok. For me, too. This is strange, or I’m on the wrong path here…
Did you install it fresh, or came it from a backup?
Freshly installed, I came from LOS 17.1 GSI. Backup didn’t work so I formatted /data.
I have other strange effects like that my phone won’t reboot but stay off until I press power for about 30 seconds or so…
This effect is present on my phone also. I’m still planning to try to catch some log and open an issue…
With the DB navigator, I’m at a loss… Maybe you could try to catch a logcat?
Yes, I could do this tomorrow. Btw, interesting that you have the sane effects with reboot. On LOS 17.1 GSI this was working.
I don’t have the GSI version, but the normal LOS17.1 and when I click on “Weiter zur Buchung” I can go to the next screen.
OK, it seems I am hit by a bug which is not specific to official LOS but by my particular installation.
Hello everybody,
I just wanted to point out that there might be a problem with the MicroG+LineageOS builds because the last available on the MicroG website dates from the 10th of December, but since then there have been 3 builds of LineageOS 16 and 2 of the 17.1 version on the LineageOS website.
Is there a website where we could check the MicroG build process ?
The builds for Lineage for MicroG needs to be initiated manually.
So, for now, it will happen every month around the same date.
The builds for Lineage 17.1 were started today, so the new build will be available soon, I guess.
It seems like the order is in general alphabetical and first LOS 15, LOS 16 and then 17.1.
You can follow the process on the download page when you sort all devices by “last changed”
Cheers
4 Likes
Just a quick FYI for those interested:
LOS4microG 17.1 has officially landed over here: https://download.lineage.microg.org/FP3/
8 Likes