Even though I enable signature spoofing in the Android app settings, MicroG Can’t grant signature spoofing permissions on the Jolla C2.
1 Like
So I’m not the only one…
1 Like
I’m in the same boat. Checked multiple times that I followed the instructions carefully.
double check the application rights on the android side (app permissions, “Spoof package signatures”);
make sure you have:
- microG Compoanion
- microG Services Core
installed from F-droid; both of these need signature spoofing.
After Sailfish OS 5.0.0.21 update I can give permission, and now I have all of the checks. Still not able to use android apps that require google play services.
1 Like
Make sure you have the correct versions of the packages ; on xperia 10v ii its
microg core : 0.2.27.223616
conpanion: 0.2.1
might depend on the aosp verdion tho, so not sure these numbers apply to aosp 14 (or was it 15?)
alsp after enabling all this spoofing stuff, you have to reboot.
Im wondering actually, how comes the appsupport needs the spoofing?
Surely F-droid takes care of any version matching if you use that?
Source? Surely restarting the AAS is enough. It has no connection to the actual OS.
Huh? MicroG needs it; because some apps are silly.
And for completeness; i’m not getting further than @matti.tujula either - and we definitely should.
3 Likes
not on xperia 10ii im afraid 
also, the last updates unsetted the package spoofing option.
microg runs in appsuport or not?
Again, source.
Yes, but that does not make AAS “need spoofing”.
Do you mean “why it has a spoofing setting”?
Source : personal experience (twice now with the latest update); there might be a bug somewhere
and no, I didnt write “aas needs spoofing” (please stick to what I write ),
I mean given microg runs in appsupport; why dont app support fool the relevant options required for it to work to be set? For instance, it should recognize microg is installed; and hence pre-set the app rights configuration for it to be ready for use; with the option for the users to disable it…not leave the mess to sort out for an average joe user who doesnt know anything of android and is probably quite uninterested in all things android anyways (why would he use sailfishos otherwise?), and hence easily frustrated with the mess he has to go through just to get dome basic functionality any other phone offers out of the box…
Please check for the latest versions (0.3.3) in F-Droid, 0.2.27 is now about two years out of date. It won’t install the updates automatically because the newer versions are signed with a different key.
1 Like
0.33 is the one that gets installed, but when you check versions , it says “suggested” on 0,27.
Made no difference to use that one for me.
On xperia 10 ii, at least it didnt work with the latest versions.
What do you mean by didn’t work? I have microG 0.3.2 on my Xperia 10 II, and I haven’t really run into anything that doesn’t work.
Same on my 10 III - all checks pass.
Thanks for this. I was able to get whatsapp backup working with Xperia Iii. Hope will be able to put everything to Xperia 10 V XQ-DC72, once this model is supported.
1 Like
I could not find the FakeStore in the repo, but the FakeStore is now part of MicroG Companion. So just install MicroG Companion if you need the FakeStore
2 Likes
Same here. This means the instructions need an update, right ?
There are quite some differences from the instructions, no ?
Jolla C2 here :
- In F-Droid : I get a constant message about apps built with an older version of Android and cannot be updated automatically
- There is no FakeStore anywhere (but @Rawnar wrote it’s part of microG Companion)
- In microG Settings : The Self-Check reports all items supported in Signature spoofing support and Installed packages
- The two banking apps I tried, have no Spoof package signature option under Permissions. None of them starts.
2 Likes