Android issues after upgrade to 3.2.0.12 (XA2)
asked 2019-11-09 14:31:08 +0200
Hello fellow SFOS users,
after Nokia N900 and N9, Jolla 1 and a lot of frustrating excursions into the land of Android, I decided to give Sailfish another try and got me an XA2 a couple of weeks ago. So far things have gone swell, although the support for Android apps requiring Google Services is quite a PITA - but I got that to work in 3.1.0.11. Unfortunately the upgrade to 3.2.0.12 went awry and the XA2 got stuck at the SONY boot screen, so back to the drawing board and flash 3.2.0.12 directly, thereby unfortunately losing most of my setup (yes, I did backup the data to mSD).
The question I have now, though: In 3.1.0.11 I had the WhatsApp and Car2Go apps running quite nicely with microG - after the upgrade to 3.2.0.12 and successively installing F-Droid, the microG-Repo, Services Core, Proxy, Fake Store and the Droid Guard Helper, both WhatsApp and Car2Go are still complaining that the Google Play Services are not available (or rather: That my device is not supported).
Die I miss anything? I don't remember WhatsApp having needed the Google Play Store dependency.
Thank you and best regards.
as far as I know whatsapp doesnt require google play services...
itdoesntmatt ( 2019-11-09 15:23:57 +0200 )editYeah, it doesn't. However, it doesn't mean that WhatsApp can't use the APIs if they're available on the device. The op's issue sounds like something is wrong providing those services.
Sakke ( 2019-11-09 15:33:39 +0200 )editIt was indeed working fine at the beginning of the week and suddenly stopped (I can't remember if I made any severe changes, but I don't think so). I am not able to make it work again. Could the NLP providers have anything to do with that? microG self check is all good except Phonesky signature and network-based location.
schlensman ( 2019-11-09 17:58:54 +0200 )edit