Installing microG on Sailfish OS

That’s true, you have to do the brutal way. The soft way is not enough. On my C2 all checkboxes in the microG selftest are checked (using microG 3.5). But my android apps have no connection to mobile data. Are there any solutions to this behavior?

Jolla knows (IIRC it’s DNS issue) and they are working on it.

2 Likes

Fixes for microG were also teased on this week’s community meeting, by the way!

11 Likes

Have you increased the root partition? In my case problem appeared after that.

1 Like

For me microG 0.3.5 works on my Jolla C2. and all checkboxes are ticked. 0.3.6 doesn’t work.

Consistent behaviour. It looks like 0.3.5 believes signature spoofing is correct, while it’s not (it’s old). 0.3.6 checks correctly and informs you.

after C2 flashing and partition increasing?

1 Like

Yes, i have the latest Firmware with 10GB Root Partition. I first installed 0.3.4, that worked, updated to 0.3.6 it doesn’t worked anymore. so i removed all microg packages and installed 0.3.5. Now it works.

1 Like

Ok, so I agree 0.3.5 works but I had to wipe out App support again in a brutal way and start from scratch.

1 Like

Sorry if the information is mentioned somewhere already, this thread is pretty long and I didn’t read all posts. I spend few hours to make microG working on my Xperia 10 II, Sailfish OS version 4.6.0.15.

Recent version 0.3.6 was not working for me, I was unable to get spoofed signatures. But the GmsCore 0.2.29 with FakeStore 0.2.1 works fine…

edit: MicroG 0.3.6 works fine on SFOS 5.0.0.55, Xperia 10.II

2 Likes

5.0.0.55 fixed the signature spoofing issue and now all checkboxes are correctly checked.

4 Likes

How the heck have you guys gotten signature spoofing to work? Specifically on 5.0.0.55. It keeps showing as unchecked for me and as a result MobilePay complains about Google Play Services being missing. Mind, I am now using microG 0.3.6, but at least according to relnotes latest should work now? Have any of you had success with getting it set up without wiping away AppSupport?

1 Like

When is a AppSupport installation “modified”?

To be more precise, when “removing” AAS as instructed in the help artickle, do i have to remove all android apps, or is it only most important to uninstall some very specific apps/packages so that these are overwritten when reinstalling AAS?

Clean removal, Step 2:
2) Uninstall your Android apps installed from other app stores

Or is it most crucial to follow not just the clean removal but the brutal way removal with:

  1. Run the following commands in the Terminal. Note that they remove all of your installed Android apps and their data, too, in addition to AppSupport.
# Sailfish OS version 5 and higher
devel-su
rm -rf /home/.appsupport
rm -rf /home/appsupport-root
rm -rf /home/defaultuser/android_storage
reboot

I would prefere to only remove the parts that are really necessary. :wink:

1 Like

Have you checked the Disable Android AppSupport system package verification in Android AppSupport settings?

All I did was check that, install microG Services and microG Companion and that’s it. No need to wipe out AppSupport.

3 Likes

Aha! Yep turning on the “Disable Android AppSupport system package verification” option did the trick. Thank you very much for the help on that one! MobilePay now no longer blocks, including with microG 0.3.6.

:partying_face:

1 Like

I properly checked the option but MicroG still tells me to “check the documentation on which steps might be required”
What I am missing?…

Edit: I finally got it to work but I had to wipe out AppSupport the hard way.

doesn’t work for me on the C2, inlcuding re-installing AppSupport, and microG and having disabled the android appsupport system package verification

Thank you for the updated instructions. Very clear. Worked on my C2 after re-installing AsppSupport.

I received my C2 (second batch) a few days ago. It came with 5.0.0.55 installed.

I installed Appsupport and enabled spoofing, installed microG by following these updated instructions exactly.
Yet I did get the “check the documentation” message and the boxes unchecked.
I tried the clean removal and reinstallation of Appsupport - didn’t help.

Then I used the “brutal way” and now all the boxes are checked!

Trying the same thing twice and expecting different results is the definition of being an engineer!

6 Likes

I had to do the same as you, removal of Appsupport via the „brutal way” an re-installing it did the job. This updated instruction by @flypig -Jolla is superb! One needs to read it carefully. MicroG is working as it should now.
The only thing I’m wondering is that some banking apps (older version of my banking app works, new one not) are nowadays checking if the device is rooted or the name of the device is ”suspicious”. In AOSP with LineageOS or eOS, I would then install Magisk via TWRP and hide the rooted device. This way banking apps would work there, I wonder how we could do a similar approach in SFOS.