all issueshttps://gitlab.opengapps.org/opengapps/all/-/issues2020-07-04T02:35:46Zhttps://gitlab.opengapps.org/opengapps/all/-/issues/3com.google.android.gms.persistent missing permission2020-07-04T02:35:46Zdianlujitaocom.google.android.gms.persistent missing permissionI consistently got the following warning:
```
06-25 18:25:24.699 1556 2445 E DatabaseUtils: Writing exception to parcel
06-25 18:25:24.699 1556 2445 E DatabaseUtils: java.lang.SecurityException: Permission denial: writing to setting...I consistently got the following warning:
```
06-25 18:25:24.699 1556 2445 E DatabaseUtils: Writing exception to parcel
06-25 18:25:24.699 1556 2445 E DatabaseUtils: java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_DEVICE_CONFIG
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2018)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at com.android.providers.settings.SettingsProvider.mutateConfigSetting(SettingsProvider.java:1109)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at com.android.providers.settings.SettingsProvider.insertConfigSetting(SettingsProvider.java:1087)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:421)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at android.content.ContentProvider.call(ContentProvider.java:2152)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:277)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at android.os.Binder.execTransactInternal(Binder.java:1021)
06-25 18:25:24.699 1556 2445 E DatabaseUtils: at android.os.Binder.execTransact(Binder.java:994)
06-25 18:25:24.706 2357 7760 W aodo : updateFromConfigurations failed with SecurityException [CONTEXT service_id=204 ]
06-25 18:25:24.706 2357 7760 W aodo : java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_DEVICE_CONFIG
06-25 18:25:24.706 2357 7760 W aodo : at android.os.Parcel.createException(Parcel.java:2071)
06-25 18:25:24.706 2357 7760 W aodo : at android.os.Parcel.readException(Parcel.java:2039)
06-25 18:25:24.706 2357 7760 W aodo : at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:188)
06-25 18:25:24.706 2357 7760 W aodo : at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:140)
06-25 18:25:24.706 2357 7760 W aodo : at android.content.ContentProviderProxy.call(ContentProviderNative.java:658)
06-25 18:25:24.706 2357 7760 W aodo : at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:2312)
06-25 18:25:24.706 2357 7760 W aodo : at android.provider.Settings$Config.putString(Settings.java:15161)
06-25 18:25:24.706 2357 7760 W aodo : at android.provider.DeviceConfig.setProperty(DeviceConfig.java:538)
06-25 18:25:24.706 2357 7760 W aodo : at aodm.a(:com.google.android.gms@202117037@20.21.17 (120400-316502805):2)
06-25 18:25:24.706 2357 7760 W aodo : at aodo.a(:com.google.android.gms@202117037@20.21.17 (120400-316502805):25)
06-25 18:25:24.706 2357 7760 W aodo : at aodo.b(:com.google.android.gms@202117037@20.21.17 (120400-316502805):39)
06-25 18:25:24.706 2357 7760 W aodo : at aodo.a(:com.google.android.gms@202117037@20.21.17 (120400-316502805):54)
06-25 18:25:24.706 2357 7760 W aodo : at aodo.f(:com.google.android.gms@202117037@20.21.17 (120400-316502805):4)
06-25 18:25:24.706 2357 7760 W aodo : at aodo.d(:com.google.android.gms@202117037@20.21.17 (120400-316502805):29)
06-25 18:25:24.706 2357 7760 W aodo : at com.google.android.gms.platformconfigurator.PhenotypeConfigurationUpdateListener.a(:com.google.android.gms@202117037@20.21.17 (120400-316502805):4)
06-25 18:25:24.706 2357 7760 W aodo : at com.google.android.gms.platformconfigurator.PhenotypeConfigurationUpdateListener.onHandleIntent(:com.google.android.gms@202117037@20.21.17 (120400-316502805):16)
06-25 18:25:24.706 2357 7760 W aodo : at com.google.android.chimera.IntentOperation.onHandleIntent(:com.google.android.gms@202117037@20.21.17 (120400-316502805):2)
06-25 18:25:24.706 2357 7760 W aodo : at qgs.onHandleIntent(:com.google.android.gms@202117037@20.21.17 (120400-316502805):4)
06-25 18:25:24.706 2357 7760 W aodo : at ctx.run(:com.google.android.gms@202117037@20.21.17 (120400-316502805):5)
06-25 18:25:24.706 2357 7760 W aodo : at ctw.run(:com.google.android.gms@202117037@20.21.17 (120400-316502805):10)
06-25 18:25:24.706 2357 7760 W aodo : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
06-25 18:25:24.706 2357 7760 W aodo : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
06-25 18:25:24.706 2357 7760 W aodo : at java.lang.Thread.run(Thread.java:919)
```
It's fixed after adding the following to `/etc/default-permissions/opengapps-permissions-q.xml`, however it turns out that I'm not even allowed to fork a project here thus unable to make a merge request.
```xml
<exception package="com.google.android.gms.persistent">
<permission name="android.permission.WRITE_DEVICE_CONFIG" fixed="false"/>
</exception>
```nezorflamenezorflamehttps://gitlab.opengapps.org/opengapps/all/-/issues/2priv-app perms are missing from whitelist, causing bootloops2020-02-11T11:17:48Zrazorlovespriv-app perms are missing from whitelist, causing bootloopsThe wellbeing app was updated yesterday and it needs some new perms whitelisted.
Please remove the following builds: 11 feb, pie and q, arm and arm64, nano and larger.
fix here: https://gitlab.opengapps.org/opengapps/all/merge_request...The wellbeing app was updated yesterday and it needs some new perms whitelisted.
Please remove the following builds: 11 feb, pie and q, arm and arm64, nano and larger.
fix here: https://gitlab.opengapps.org/opengapps/all/merge_requests/8
Note: In case you weren't aware, there is a script you could use to help prevent this repeated issue, to update your priv-app whitelist.
https://source.android.com/devices/tech/config/perms-whitelist#generating-whitelists
@nezorflamenezorflamenezorflamehttps://gitlab.opengapps.org/opengapps/all/-/issues/1LineageOS 16.0 Bootloop2019-12-05T20:35:38ZZus SamuelLineageOS 16.0 BootloopI've been pulling the latest commits into a custom LineageOS 16.0 build environment.
Up until recently, the system has been booting, but the latest pulls have been causing a bootloop.
I suspect that some privapp permissions are missing. ...I've been pulling the latest commits into a custom LineageOS 16.0 build environment.
Up until recently, the system has been booting, but the latest pulls have been causing a bootloop.
I suspect that some privapp permissions are missing. Looks like a similar issue was fixed in this commit: https://gitlab.opengapps.org/opengapps/all/commit/66ea7a3282ae364ae454ff7f955c6aebb545464d but I'm still experiencing issues.
Unfortunately, I can't seem to pull a logcat from the bootloop to narrow down the issue (can't figure out why all the methods I've tried haven't worked)