And for those still needing Google services for corporate or whatever reasons, there’s a strong solution at Google Play Services on Xperia 10 III Sailfish 4.4.0.64 (now 5.0.0.73) - #92 by lkraav that I’m (and probably many silent thread lurkers) daily-driving hard. Mostly everything works, aside from some potential deep-layer hiccups like Google Workspace MDM etc.
(PS Really, 12 GB RAM is so welcome. At strong native + Android app load, X10III starts out snappy, but as we run close to memory and ZRAM limits, swap usage can have really laggy UX for a while until low-memory killer processes figure their stuff.)
False advertising or not, I’d say Android app compatibility, microG and whatnot should all be carefully thought of when marketing this phone. I think we all want to see a non big-tech phone taking over, but people in general depend so much on apps, that this is something worth paying attention to.
The Android layer can’t be THE selling point for SFOS.
AAS is a crutch, a sweetener, a hole filler. I’m glad it exits and I can run some android apps. If AAS can get better without takings bandwidth from SFOS devs, go for it.
It’s delusional to expect 100% compatibility from AAS. If that’s really needed, then for that part an Android derivative with better privacy is probably a better fit.
I think it is one of the main selling points, and I think the company knows it.
(I hope they also know that they have a dedicated base for who that is NOT the main point of SFOS.)
BUT
It’s delusional to expect 100% compatibility from AAS.
Unfortunately that’s the sort of statement you simply don’t make in advertising.
Why? Because Jolla AppSupport works in launching Android OS instance. The same Android OS like Google phones. Only with no Google services because of licensing problems.
So if Jolla’s Android system OS instance is the same as with Google phone system OS instance, it means both work with banking, messaging, everyday apps. In technical sense.
And yes alot of applications work with AppSupport with no change needed to user. Just try and search sailfishos dot app website, like in previous comments, for app you need.
But yes reality is abit different. Just to be clear its not Jolla’s fault. Jolla doesnt control what Google does with Android OS and what things developers do with the apps. I dont think Google gives Google services license to use in “virtual machines”(lets use a simpler term for AppSupport technical approach).
Abit different because first because like others said marketing is abit bold, they should use more ‘may work’ and things. Second because you as user (just my personal proposal, did not test and dont have test device for it) need to install Google services, enter Google account, have root (if its possible with Jolla AppSupport implementation) and use some modules that trick Google security attestation. This is not default configuration and will not be supported by Jolla so its unoficial lets say community modifications. But this should give you really near full capability of using banking apps and other apps that might be more picky.
Yes I agree SailfishOS must prioritize Sailfish development and use (like to create and use apps in Sailfish and create ports for Sailfish). Its the way to go. But I think to attract people to (unfortunately) niche and very small platform you need to have in between option. Because if no app works for user, its not a smart phone, its dumb phone. When Linux mobile will be in talks as same as is now Linux desktop, then we can chat about using Linux in full and chat about people coming to us here with no Android support issues.
Abit offtopic. But anyone ever tried rooting newest AppSupport (I think Android 13)? Like is it at all possible? What about attestation? Play integrity api check shows virtual integrity? Would be good to know
