@Roboe
I wanted to try out the recent MicroG for using the german Corona-Warn-App. I was using latest LoS 17.1 and tried to flash microg_2020-04-07.zip over unifiednlp_2020-04-07.zip, which I have been using for months. I read that TWRP 3.4.0 doesn’t work and downgraded to TWRP 3.3.1 and was able to flash the microg-ZIP. Back in LOS I did just see the UnifiedNlp app and no MicroG app and chose to remove UnifiedNlp as described in the linked thread. That lead to a bootloop… I’m unable to boot into my Android. Any help is greatly appreciated!
Got it booting again by re-flashing latest modem.zip, unifiednlp_2020-04-07.zip and lineage-17.1-20201009-nightly-FP2-signed.zip. I have no idea which file helped me.
@Roboe How can I upgrade or switch from just UnifiedNlp to full MicroG now?
Tried a flash of microg_2020-04-07.zip again and got a bootlop, which seems to be caused by that:
10-10 20:57:08.892 9897 9897 W PackageManager: Privileged permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST for package com.google.android.gms - not in privapp-permissions whitelist
10-10 20:57:08.893 9897 9897 I PackageManager: Un-granting permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST from package com.google.android.gms (protectionLevel=18 flags=0x20883e45)
10-10 20:57:08.937 9897 9897 E System : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms: android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST}
10-10 20:57:08.938 9897 9897 E Zygote : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms: android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST}
10-10 20:57:08.938 9897 9897 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.google.android.gms: android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST}
10-10 20:57:09.735 10213 10213 I zygote : option[49]=-Xfingerprint:Fairphone/FP2/FP2:6.0.1/FP2-gms-18.04.1/FP2-gms-18.04.1:user/release-keys
10-10 20:57:12.831 10271 10271 W PackageManager: Privileged permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST for package com.google.android.gms - not in privapp-permissions whitelist
10-10 20:57:12.831 10271 10271 I PackageManager: Un-granting permission android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST from package com.google.android.gms (protectionLevel=18 flags=0x20083e45)
10-10 20:57:13.155 10271 10271 V PackageManager: Changing enabled state of com.google.android.gms/com.google.android.gms.nearby.messages.service.NearbyMessagesService to false
10-10 20:57:13.155 10271 10271 W PackageManager: Unable to change enabled state of com.google.android.gms/com.google.android.gms.nearby.messages.service.NearbyMessagesService to false
10-10 20:57:13.155 10271 10271 V PackageManager: Changing enabled state of com.google.android.gms/com.google.android.gms.nearby.discovery.service.DiscoveryService to false
10-10 20:57:13.156 10271 10271 W PackageManager: Unable to change enabled state of com.google.android.gms/com.google.android.gms.nearby.discovery.service.DiscoveryService to false
10-10 20:57:13.156 10271 10271 V PackageManager: Changing enabled state of com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity to false
10-10 20:57:13.156 10271 10271 W PackageManager: Unable to change enabled state of com.google.android.gms/com.google.android.gms.update.SystemUpdateActivity to false
10-10 20:57:13.156 10271 10271 V PackageManager: Changing enabled state of com.google.android.gms/com.google.android.gms.update.SystemUpdateGcmTaskService to false
10-10 20:57:13.156 10271 10271 W PackageManager: Unable to change enabled state of com.google.android.gms/com.google.android.gms.update.SystemUpdateGcmTaskService to false
10-10 20:57:13.156 10271 10271 V PackageManager: Changing enabled state of com.google.android.gms/com.google.android.gms.update.SystemUpdateService to false
10-10 20:57:13.156 10271 10271 W PackageManager: Unable to change enabled state of com.google.android.gms/com.google.android.gms.update.SystemUpdateService to false
10-10 20:57:13.208 443 1820 W installd: Ignoring /data/data/com.google.android.gms/lib with unexpected GID 0 instead of 10157
10-10 20:57:13.210 443 1820 W installd: Ignoring /data/data/org.microg.gms.droidguard/lib with unexpected GID 0 instead of 10158
@Roboe Well I made a full backup before, via adb backup -apk -shared -all -f /home/FP2.ab, but to be honest I wasn’t able to restore it .
What about adding the missing permission to the Zip you provide <permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST"/>? That would at least have prevented the boot loop .
Yes, ADB backup is horrible, but even minding that, it’s not thought to this case. ADB backup backs up apps. A NANDroid backup, the one you get with a recovery, is the one that should be used, because it backs up the system too.
Lack of time. Sorry. Developing this kind of mods and testing it’s a lot of work, and I don’t happen to have a testing phone handy nowadays neither. But I’m openingI opened an issue in the repo in case someone can lend a hand.
I’m now using the latest version of LineageOS for microG. The migration from official LoS to that one worked like a charm and before I made a full backup via TWRP + my own files via USB.
The Corona Warn App works like a charm and I’m also enjoying MapBox for apps which rely on Google Maps… good choice!
.
.