Installing gapps on Alien Dalvik is a bit of a mess, as it actually involves taking the system.img from /opt/alien and implementing it directly. I can link to the original guides relating to installing the Gapps, but there’s no guarantee this will work on SFOS 4, now that it’s implemented with Android 9 as the base for AD.
As for MicroG, your solution to SafetyNet is the DroidGuard Helper that should be installed alongside GmsCore. In a strange event, I installed all of the MicroG assets in 188.8.131.52, SafetyNet refused to register. I also was never able to add my Google account. Some strange regression with how the built-in Webview worked, I’m not sure. By sheer magic, after upgrading to 184.108.40.206, SafetyNet registered without a hitch, and the Webview in AD 9 loaded the Google login just fine. There’s no telling how important the account is, as all of my apps seemed to work fine with just GmsCore installed and detected, but it should be enough. May need to test further now that I can actually use SafetyNet and my Google account in AD.
The installs working for me are
- microG Services Core (GmsCore) version 0.2.15.204713
- microG DroidGuard Helper version 0.1.0-10-gf64bf69
- microG Services Framework Proxy version 0.1.0
- FakeStore version 0.0.2
All of these versions are readily available in the F-Droid repo. As is the case always, make sure to enable signature spoofing where applicable.
And an obvious disclaimer, Jolla, the Sailfish community, F-Droid, or microG’s developers are NOT responsible for anything that happens with your Google account. Using microG, while it IS a clean-room re-engineering of Google services for Android software, is technically against the terms of service. It may be in your best interest to use a dummy Google account, or even no Google account at all using microG if possible.