-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add note about flashing after /data has been set up #43
Comments
oh the npem script is actually supposed to do this -- i always used to get the same error (pm fails, broken pipe) at the start of running npem so it probably fails due to that, will debug |
The readme does recommend you not to do a dirty flash:
But yeah, if running the script didn't fix it then something else is going on. The broken pipe error is a red herring because android embeds a broken toybox, the shell complains about weird exit codes from grep etc. in pipes. If pm throws an error, that's an issue. You could try running the install and grant commands manually and see what happens. |
Hmm that issue only happened with gmscore for some reason, hasn't happened with my custom unifiednlp build https://github.com/git-bruh/unifiednlp-standalone Will investigate if I ever have to flash gmscore again |
Hi, I spent a few hours troubleshooting this error today:
It occurs when you try to run
adb shell pm grant com.google.android.gms android.permission.ACCESS_BACKGROUND_LOCATION
. I was trying this because location permission was not being granted to microg and even after adding this permission to the xml files in the minmicrog zip, it didn't work.Turns out that if you install microg after setting up your rom, you have to run
pm install -r /path.to/GmsCore.apk/
to make it both a system and user application -- microg/GmsCore#1100 (comment)Would be nice to have this mentioned somewhere in the README
I was doing this on lineage 19.1 official (non-microg) as I only need unifiednlp functionality and not the rest of gmscore so signature spoofing isn't necessary
The text was updated successfully, but these errors were encountered: