Update privapp permissions

[Roboe]

I don't have the time and a testing device handy nowadays to test this with a minimal confidence.¹

So, please, lend a hand if you can!

A user had a bad time when their device bootlooped after flashing microg_2020-04-07.zip:

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

https://forum.fairphone.com/t/bootloop-after-trying-to-remove-unifiednlp-fixed-but-how-to-switch-to-microg/65774/3

He proposed to add this privapp permission to the privapp-permissions-microg.xml file (similar to #13):

<permission name="android.permission.CHANGE_DEVICE_IDLE_TEMP_WHITELIST"/>

Other privapp permissions might be lacking too.

---

¹ On a personal note, I'm in the process of moving out of Android or even mobile technology altogether. So I'll probably stop updating these projects and mark them as unmaintained if noone steps up.