GmsCore: android.permission-group.UNDEFINED permission

Also had this issue (perhaps because I was doing a dirty upgrade), and was able to solve it by adding the permission manually in /data/system/users/0/runtime-permissions.xml:

<pkg name="com.google.android.gms">
  <item name="android.permission.ACCESS_BACKGROUND_LOCATION" granted="true" flags="3320" />

I wrote some more details about it in the XDA thread. Note that the flags= attribute is important.

Before that I also tried pm grant com.google.android.gms android.permission.ACCESS_BACKGROUND_LOCATION which seems to work but doesn’t fix the problem.

The relevant permission in this case is android.permission.ACCESS_BACKGROUND_LOCATION. Does it help to un-grant location permission (in system settings) and then re-grant (either through self-check or system settings)

I don’t think the location settings can be accessed from the UI at all, at least for me (Android 10, current LOS 17.1):

This just takes me to Settings → Location, where I can only go to App permission → microG Services Core and get the same modal dialog again.

Hi everyone, i make XML patcher python script (i am not programmer so it may look ugly) it make @GeographicCone patch automatically. You can download patcher here I not know how correctly and safe modify XML file in shell script, so it written on python, it mean you also need python to use this patcher, so i also make python installer magisk module. You can download python here

It my first experience of making Magisk modeles, so it may contain errors.

P.S. @GeographicCone thanks for solution, it also work for AFWall+ storage problem.

@GeographicCone

Note that the flags= attribute is important.

Confirm, in my case i have in runtime-permissions.xml :

<pkg name="com.google.android.gms">
    <item name="android.permission.ACCESS_FINE_LOCATION" granted="true" flags="300" />
    <item name="android.permission.FAKE_PACKAGE_SIGNATURE" granted="true" flags="300" />
    <item name="android.permission.READ_EXTERNAL_STORAGE" granted="true" flags="4300" />
    <item name="android.permission.ACCESS_COARSE_LOCATION" granted="true" flags="300" />
    <item name="android.permission.READ_PHONE_STATE" granted="true" flags="300" />
    <item name="android.permission.GET_ACCOUNTS" granted="true" flags="300" />
    <item name="android.permission.WRITE_EXTERNAL_STORAGE" granted="true" flags="4300" />
    <item name="android.permission.ACCESS_BACKGROUND_LOCATION" granted="false" flags="4300" />
  </pkg>

and change 4300 > 3320 fixed issue.

Havoc-OS 3.6

I verify this worked as well. What i did is this:

1. Cleared Storage and Cache for MicroG App from settings Settings > Apps > MicroG > Storage & Cache
2. From adb shell i edited /data/system/users/0/runtime-permissions.xml and changed the numbers 4300 to 3320 as suggested.
3. I rebooted - then microg was not working again
4. I had to manually allow the permissions in the Settings > Apps > MicroG App > Permissions. Location could now be set to Allow all the time`.

Havoc 3.7

P.s. I wonder why this issue didn’t came up at testing before releasing (not trying to blame anyone ofc)

@GeographicCone

Note that the flags= attribute is important.

Confirm, in my case i have in runtime-permissions.xml :

<pkg name="com.google.android.gms">
    <item name="android.permission.ACCESS_FINE_LOCATION" granted="true" flags="300" />
    <item name="android.permission.FAKE_PACKAGE_SIGNATURE" granted="true" flags="300" />
    <item name="android.permission.READ_EXTERNAL_STORAGE" granted="true" flags="4300" />
    <item name="android.permission.ACCESS_COARSE_LOCATION" granted="true" flags="300" />
    <item name="android.permission.READ_PHONE_STATE" granted="true" flags="300" />
    <item name="android.permission.GET_ACCOUNTS" granted="true" flags="300" />
    <item name="android.permission.WRITE_EXTERNAL_STORAGE" granted="true" flags="4300" />
    <item name="android.permission.ACCESS_BACKGROUND_LOCATION" granted="false" flags="4300" />
  </pkg>

and change 4300 > 3320 fixed issue.

Havoc-OS 3.6