Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to grant permissions for "access location in the background" and "receive text messages (SMS)" #16

Closed
Master0ne opened this issue Feb 19, 2021 · 7 comments

Comments

@Master0ne
Copy link

With latest ArrowOS 11 with Magisk Canary on a POCO X3 NFC and microG Installer Revived, I am unable to grant these two required permissions in microG Self-Check:

  • Permission to access location in the background
  • Permission to receive text messages (SMS)

When clicking on these two, nothing happens.

When trying to set permissions in app settings:

  • for the Location permission it does not even show the "Allow all the time" option
  • for the SMS permission changing it from "Deny" to "Allow" does not stick (I can click "Allow", but if I go back, microG Services Core is still under "Denied" and if clicking on microG Services Core again the SMS permission is on "Deny" again).

These problems do not occur when installing the microG components from the microG repo in F-Droid.

@nift4
Copy link
Owner

nift4 commented Feb 21, 2021

Can you give logs? Did you try the workaround mentioned at the microG issues?

@nift4
Copy link
Owner

nift4 commented Feb 21, 2021

microg/GmsCore#1099 (comment) and below

@nift4 nift4 closed this as completed Feb 21, 2021
@nift4 nift4 reopened this Feb 21, 2021
@Master0ne
Copy link
Author

@nift4 Sorry, no logs, already moved on to installing the required microG components through F-Droid using the F-Droid Privileged Extension Magisk Module.

I did play around with runtime-permission.xml and it made the "Allow all the time" option appear for the Location permission, but it nevertheless didn't work and I gave up on it prematurely.

I'm going to close this issue because I can not help analyze it any further, so nothing more to do unless someone else should stumble over the same issue.

@Izaic
Copy link

Izaic commented Apr 25, 2023

This is an issue again on the latest installer, however the previous one from February does not have this issue.

@nift4
Copy link
Owner

nift4 commented Apr 25, 2023

oof, i'll try to push a fix in the next update

@nift4
Copy link
Owner

nift4 commented Apr 25, 2023

just to verify, on what rom are you? (exact name + version please)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants