For me, MicroG is still working on both, my XA2 and the Xperia 10 under 184.108.40.206
Hi, I can confirm it, it happened to me too.
Same, everything was and still is working post-upgrade.
Thank you for the reports, I updated and it indeed still works as it should.
One problem I faced is that themepack support was preventing Aliendalvik from starting and I had to remove it.
I confer the opposite. MicroG failed to function correctly on a freshly flashed 220.127.116.11, with the systems working after dealing with signature spoofing (both with the img patching method and the symlink) but never allowing me to add an account or use SafetyNet, and many programs still weren’t registering with GCM. After updating to 4.0, MicroG SafetyNet started working, and I was able to add not one but two Google accounts, and all applications had both working GCM and notifications.
Just in case it’s for someone’s benefit: I had issues with Android apps relying on Google Play Services after updating my XA2 from 3.4 to 4.
I also had issues with Whatsapp after updating my XA2 with Gms to 4.0.
After failing to successfully follow the guide mentioned by coco, I decided to re-flash my XA2 with a fresh 4.0 install.
I was impressed to find out Whatsapp now works out of the (store) box, as all the Android I use. Not need for third party softs anymore !
Yes, Whatsapp (and Android apps mostly) do work on Xperia 10 and XA2 without MicroG or other helpers.
I have never used Google services or MicroG.
Working for me after 4.0 update. I don’t use Whatsapp, though, but other GServices apps working fine…
Please be weary that this guide requires you to unpack and repack your system.img file. Doing so may lead to losing some selinux capabilities stored in the xattr (extended attribute). Without these capabilities, your android ends up being broken in subtle ways that are not easy to spot (e.g.: logcat doesn’t work anymore).
I would strongly suggest that you consider installing microG instead(*) as that one doesn’t necessarily requires modifying the system.img partition (only if some of your app require the older mapsv1 API). You can mostly get by simply by using the “spoofing signature” feature of AlienDavlik introduced a few SFOS versions ago.
If you decide to modify your system.img any way, I would very strongly suggest that you rely on an approach that doesn’t rely on unpack system.img but loop mounting it instead (see my example for mapsv1).
I was pleasantly surprised that with Jolla’s latest SFOS and microG’s latest surprise, even my bank’s PhotoTAN works correctly. (But the “background android apps grab the camera and do not release it” bug is still present every now and then).
(*) - speaking of which: dear Jolla, you promised that you’re going to transfer the howto from the old askbot to the new forum. Are you going to do it? I think mine might be still relevant but myself am busy fighting some pandemic (you might have heard about) in my day job so I don’t have time to port it to the new forum.
Since Sailfish 3.4 I had problems with micoG. In Salifish 3.3 everthing including cloud messaging was working very well. My hope was, that the update to 4.0 will solve the problem, but this was not the case. So I read all the comments hear… At the end I had a deeper look at the micoG settings app. Out of some reason the “google device registration” was disabled. So cloud messaging couldn’t work. So I activated device registration rebooted the os. It took few minutes (!!) until android app support was running. But after this I could activate google cloud messaging… After next reboot android app support started fast as normal (without delay of minutes). I started apps using cloud messaging and they asked for permission to use the service.
So try to play around with your settings. Maybe this solves your problem to…
Forgive me, ultimately, before installing any Android app, you need to give these commands:
[Type your password]
ln -s / home / defaultuser / home / nemo
and then signature spoofing will work on Kali too?
Thanks for this hint. But…
In what folder do I have to set this link? In / or in /home/nemo ?
Since there are a lot of blanks in the command it is not quite clear what is the name of the link and what is the path.
Is it probably
ln -s /home/defaultuser/home nemo
or something else?
It would be very nice of you if you could tell me the correct command. Thank you very much in advance.
Best regards, Uwe.
of course! And sorry for the bad writing!
So, the command I used was:
[Type your password]
ln -s /home/defaultuser /home/nemo
Thank you very much! In the meantime I also found out that the command has to be like you said. (I was totally wrong…)
But the problem is that on my SFOS 18.104.22.168 (XA2) there is no defaultuser in folder /home. Is this correct?
After entering of devel-su I’m in folder /home/nemo. Applying the ln-command it creates a sym-link defaultuser in folder /home/nemo which points to /home/nemo.
But after restarting aliendalvik the Signature Spoofing Checker starts up but closes itself after some seconds without any output.
What I’m also wondering about is that Aliendalvik Control (9.3.1-1) looks different from earlier versions (e.g. no settings button)…
Best regards, Uwe.
And what, imagine! Well you solved it!
I don’t know what to tell you, I’m sorry: in my XA2 (even after several clean installations yes Sailfish) I always found defaultuser in home …
As for Aliendalvik Control, Coderus is working on it together with Patchmanager, still they don’t work on Sailfish 4.
Thanks for answering.
But I’m a bit confused. I have the feeling I did’nt solve it …
Is your defaultuser in /home just a (empty?) file or is it a folder?
Best regards, Uwe.
I’m sorry but I just don’t remember what was in defaultuser before I created the symbolic link with nemo.
As I said above, the proper way to fix the issue is this one:
However, if you are still nemo, and not defaultuser, you are not affected by this particular issue.
Sounds like @uwelabs is nemo? In that case there must be something else not working with the microG install or spoofing settings.