How to enable system package replacement with MicroG in 3.3.0.16 [answered]
asked 2020-04-10 13:34:14 +0300
Somehow I messed up with MicroG services core when updating some Android Apps.
Signature spoofing does not work anymore.
The problem:
- After having installed microG services core, I cannot enable "enable system package replacement" with the Android settings from Sailfish's settings. Accordingly, the Self-Check of microG services core fails with respect to signature spoofing
In the Android settings I cannot check "enable system package replacement" :
This is because the step "push the "<|" Android back arrow" now (in 3.3.0.14) results in quitting the settings instead of leading to the main screen of the Android Settings App, as suggested in DrYak's instructions:
I made a factory reset, and thereafter I could enable system package replacement und 3.2.0 - following DrYak's instructions. This doesn't work in 3.3.0.14 because there is no way to access the main screen of Android settings (at least, I couldn't find one)
Any idea (DrYak?)?
EDIT: with my Xperia 10 I didn't do the same mistake, so everything is fine and system package replacement is (still) enabled BUT I also cannot change this setting. Therefore I believe it is somehow tied to the changes in 3.3.0.14 regarding Android support and in particular how settings for Android Apps are delt with in the Sailfish settings.
BTW: everything was fine after installing 3.3.0.14 until I mistakenly "updated" microG services core by means of Aurora Store (instead of using F-Droid). I was so stupid to press "update all"
you did not update MicroG but let Google takover :(
You have to blacklist
peterleinchen ( 2020-04-10 17:10:44 +0300 )com.google.android.gms
in Aurora (and in case also Yalp) store!
@peterleinchen: I guess you are right
is there any way to get writ of Google again?
And: it's only part of the problem: apparently settings for Android Apps are different in 3.3.0.14 than they used to be before. That's why I cannot enable system package replacement
AkiBerlin ( 2020-04-10 17:36:53 +0300 )orly?
peterleinchen ( 2020-04-10 17:47:47 +0300 )I am not on 3.3.0 yet but did not read that Android settings are different (only that the bug/feature/workaround to get to full Android settings is gone, you'll need coderus AlienDalvikControl)?
What is different?
What about method 2?
AlienDalvik Control from.coderus on openrepos?
peterleinchen ( 2020-04-11 17:51:44 +0300 )Sorry, as I am overwhelmed by my day job currently (I develop a bioinformatics pipeline for analyzing deep sequencing data of viruses. You can guess what work looks like given the current SARS-CoV-2 outbreak).
So I didn't have anytime to test the early release of 3.3.0
I saw Coderus made a 3.3.0 compatible upgrade of of AlienDalvik Control. Maybe that one can open the settings and help you grant the signature spoofing permission ?
DrYak ( 2020-04-18 08:21:07 +0300 )