“grant it signature spoofing upon launch” this might not be enough. Did you permit spoofing in the android settings (via e. g. Aliendalvik control - via openrepos, Settings: Aliendalvik Control -> Settings -> Apps and notifications -> Apps settings (location, mic, camera) -> enable system package replacement -> Select your spoofing system and store if installed)
reboot
Yeah and there is the dangerous Aliendalvik control which might kill your upgrade to 3.4. But after setting the permission you can remove aliendalvik control from your system again. And it kills your system only if you have the wrong version installed.
Thanks for your reply.
I tried a lot of things and it seemed allowing spoofing in the android settings was the same as waiting for the popup to allow it when you first launch the app.
Thanks, I feel less alone, now
I wanted to try with an earlier version but shop.jolla.com only provides the latest.
On 3.4.0.24, I also tested mindthegapps, opengapps (playstore hangs or crashes), patching using haystack (spoofing doesn’t work or microg can’t access google servers), nothing worked.
I’ve just flashed 3.4.0.24 on an Xperia 10 plus dual SIM, and I’ve got the same issue.
I’ve followed The Yak’s guide on TJC, including enabling ‘system package replacement’ permissions in the Android Settings app for FakeStore, microG Services Core and Signature Spoofing Checker.
Unfortunately both apps show that the signature isn’t being spoofed.
Lucky you! I flashed 3.4.0.24 at least three times, but nothing: Signature spoofing doesn’t work on my Xperia XA2 Dual Sim!
Could I ask you, please, what guide did you follow or what procedure?
Could we say it works when the device is updated from 3.3 to 3.4 but not when it is directly flashed to 3.4?
Something to do with the renaming of the default user, perhaps?
That is why I recommend opening the android settings via the terminal with
apkd-launcher com.android.settings
There you can proceed as written by DrYak:
from the main screen of Android settings app:
Apps & notifications - Permissions, default apps
(after the apps) “App permissions - Apps using Location, Microphone, Camera” ( ^- warning it’s not in the same place as on other ROMs, it’s not among the Advanced permissions )
Here you can grant the “enable system package replacement” permission, a.k.a “Signature Spoofing”:
FakeStore (make so the empty package seem to contain “com.android.vending” coming from the genuine Google’s Play Store, so that apps checking for that are kept happy)
microG Service Core (make so “com.google.android.gms” seems to be coming from the genuine Google Play Service)
Signature Spoofing Checker (if you installed this option. It makes the checker apps’ screen go green if the spoofing works)
BUT, I have to add that I did all that after a full factory reset just one day BEFORE 3.4.0.22 (EA) was released, i.e still under 3.3.0.16
I just looked into com.android.settings on my Xperia 10 and still can see everything that is needed to enable signature spoofing - but as I just said, I was happy to have enabled signature spoofig just one day before the release of 3.4.0.22
Thank you very much for your reply!
I wanted to try to install a previous version again, on which spoofing worked and then update to 3.4.0.24, but fastboot mode doesn’t work for me…
I’ll have to buy another Xperia XA2 I’m afraid…
Do you mean can’t get “blue LED”? Sometimes it is the speed with which you push in USB-C when holding "volume down’ button in. Sometimes need to press and hold the power and the volume up button simultaneously until the device makes three vibrations if continually getting green LED.
No no: the fact is that it turns blue, but from the terminal it gives me an error: Found 0 devices:
Incorrect number of connected devices. Make sure there is exactly one device connected in fastboot mode.
I also have this problem, i think i’ll wait for it to be fixed rather than downgrading. Is it possible to mark this “i also have this problem” here on Sailfish OS Forum without creating a pointless reply?
