android.permission-group.UNDEFINED permission #1099
Comments
|
Do you have location access enabled in system settings? |
|
Yes, I do, see image:
|
|
|
|
|
More info in case it is useful: |
|
The relevant permission in this case is |
|
Also had this issue (perhaps because I was doing a dirty upgrade), and was able to solve it by adding the permission manually in I wrote some more details about it in the XDA thread. Note that the Before that I also tried
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. |
|
Is this somewhat related to this problem? SolidHal/docker-lineage-cicd-17.1@fb179ac |
|
Thanks @mar-v-in but what @GeographicCone wrote applies to me too. |
|
@chilliger I do not think so as the previous release of microg gmscore worked correctly, although the self-check ui has changed so maybe the error was simply not showing |
@chilliger That is an unrelated issue. A short summary: not only does LineageOS on some devices come with preinstalled Qualcomm Location but it's been hard-coded into the framework overlay so that it's either Qualcomm or nothing: no other location service will work if you remove the Qualcomm APK. My device is affected too and I asked the maintainer about it recently, which led to some discussion you might find interesting if you're following that issue (the first post also links to an earlier discussion for another device, where in the end the APK and the hard-coded overlay settings were removed). However...
@JonnyTech For the record, background location in Android 10 did not work correctly in the previous version (see #986), unless you were using one of the unofficial builds by @FriendlyNeighborhoodShane (MinMicroG) after Feb 23 (I did). @mar-v-in has now fixed it, alongside other improvements (thanks!) and it works. As far as I see it the issue here is just that if the permissions don't get granted automatically behind the scenes, there is no way to do so through the UI. (As to why they were not granted, I'm not sure but I wanted to contribute the manual fix that worked for me – see above.) |
|
@JonnyTech can you try the following:
|
Disabled
Confirmed
Enabled
Confirmed
No, background permission still not enabled |
I am using a "vanilla" build of AOSP 10 GSI by @phhusson (https://github.com/phhusson/treble_experimentations/releases/) with stock 8.1 vendor which should have Qualcomm stuff untouched there. How do I verify that? |
I recall that in my case, before I applied the fix to |
Confirm, in my case i have in runtime-permissions.xml : and change 4300 > 3320 fixed issue. Havoc-OS 3.6 |
@McPcholkin I first put
Then the Permission Manager changed it to |
I verify this worked as well. What i did is this:
Havoc 3.7 P.s. I wonder why this issue didn't came up at testing before releasing (not trying to blame anyone ofc) |
Confirming that changing |
|
Yes, after changing that, the self-check is OK now. But for me, most apps including Google Maps are not able to access location. |
|
Hi everyone, i make XML patcher python script (i am not programmer so it may look ugly) it make @GeographicCone patch automatically. It my first experience of making Magisk modeles, so it may contain errors. P.S. |
@draekko One thing I didn't mention is that I was making the change from within recovery mode (TWRP). Here it is step-by-step for completeness:
Note: ownership and security context seems to be set fine after replacing the file on my device, so only I wouldn't assume it to work on a live system as the file might be overwritten from memory when you shutdown the device later but if you still want to try, I'd stop the Android runtime first (
Something like this could happen if you remove Qualcomm location APK and do not change the default framework overlay settings, a separate issue that was mentioned earlier (see my previous comment, and the first link in it for details). It could be something else as well though, so just a heads-up.
@McPcholkin Considering the XML here is more regular than it could be, you can just use
Note: I checked the file again and the flag on my device is now 3330. Go figure. |
|
@GeographicCone yeah i discovered it by myself afterwards, but thanks for clarifying your steps, it now works for me but i still have issues with fused location failing and no clear errors in the logcat and trying to figure if i need mapbox or vtm versions to make the maps work. Anywho trying to figure out how to proceed from there, thanks for the sed line there going to make life easier when it reverts after and change in file happens :) |
I have other target, I want make universal and flexible solution, Python I know a bit better than sed, so I chouse python. @draekko if you searching of working MicroG with location support you can find all needed magisk modules in my repos (for flexibility I split location and microG services). |
|
@McPcholkin Thanks for the info. I fixed my location issues though, vtm doesn't work at for me, and i finally realized i needed an api key for mapbox when looking at the build process. My issue for fused services happened with the scenario where scanning (wifi/etc) as was off (and in device only mode) but the modules were turned on and it was failing. Turning off the modules fixed it for me since i want device only gps anyways. I made my own magisk module for it. Now apps like All Trails, The Hiking Project, etc... work and maps are displayed. |
|
A follow-up for Android 11: The location of the xml file to edit has changed to:
The same edit still applies (change 4000 to 3320): Then reboot the devices and allow the permission in microg's self-check. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After installing
GmsCore-v0.2.11.202414.apkand rebooting, self-check does not allow me to grant permission toandroid.permission-group.UNDEFINEDon my Android 10 device. The device is rooted and the apk is in/system/priv-app/.The text was updated successfully, but these errors were encountered: