Pim | # 51 | 2019-10-07, 09:48 | Report

Yes, without the ability to use apps like Whatsapp many people would need a second phone and then (soon after) will wonder why they would carry the one with Sailfish.

MartinK | # 52 | 2019-10-07, 11:03 | Report

This is pretty much how I see it as well. Sailfish OS just feels to me much more robust & "proper" as an OS. Not to mention being much more in control & being able to introspect what the system is doing, unlike with the interwoven bunch of google and vendor services running on a normal Android device, doing "something".

It is the unfortunate issue of many useful services being accessible only via an Android/iOS application, not having any public API and in general being unlikely we will have a native Sailfish OS application for every such service even if there is a usable API. On the other hand we have many robust a full featured native apps available.

This together creates the best of both worlds - an OS you can trust and control, robust if a bit limited native apps (most of them OSS) & the option to run Android apps for the rest, ideally as isolated from the rest of the system as possible.

kinggo | # 53 | 2019-10-07, 12:52 | Report

again.
Normal android device can run android without a trace of google. How is running an app dependent on google services like whatsup better on top of sailfish than it is on top of AOSP?
I agree that bunch of apps are needlessly tied too google services even if some of them will run just fine if we ignore complaint while some won't at all. Micro G can help but it's not a 100% solution. But even if we ignore all those apps and use just ones which don't need google services we still have much wider choice than on sailfish.
AOSP is open source with the same closed blobs that sailfish needs.
Bottom line is, using only OSS on AOSP will give more options than we have on sailfish. Is that enough to get us trough the day or do we need something that needs google is another question. All I need is an explanation why is using google over android emulator on top of sailfish better, safer, more private, whatever..... then using it on top of AOSP or some stock ROM that includes all of their services?

lantern | # 54 | 2019-10-07, 13:14 | Report

I see SFOS (in relation to dalvik) as a sandbox for android apps. I can make them see no contacts and they don't (shouldn't) have access to OS.

I think that's where Jolla should apply their time, create more controls, create all those fake-feeding of contacts/location/etc.
Android on SFOS should be the best android version (privacy-wise) out there.

Too bad, they don't really push it.

kinggo | # 55 | 2019-10-07, 15:07 | Report

how is that useful for whatsup that seems to be the reason #1?

lantern | # 56 | 2019-10-07, 15:21 | Report

I don't use whatsapp.

Bit I think you can create a specific contact-list inside dalvik. So whatsapp doesn't have all your contacts but only those that you talk with.

So your whole contact list doesn't get leaked.

It applies for all android apps. They are very chatty. And you can't really control what they do on your phone.

peterleinchen | # 57 | 2019-10-07, 19:09 | Report

THIS and more could be a deal maker.
But it looks neither Jolla is interested in such behaviour nor the 'community'

ajalkane | # 58 | 2019-10-07, 21:09 | Report

For me:

- I like to have a "GNU"/Linux device
- I like to be able to easily SSH / enable developer mode
- I like SailfishOS's swiping UI much more than Android's common UIs

Well, it seems I can run on my "GNU"/Linux device also Android apps in a container if I find it necessary. It's convenient to me if I really need those apps. And I use that option if it befits my other precautions such as privacy and malware and such considerations.

My needs are not very complex. But they're quite uniquely only provided by SailfishOS currently.

nonsuch | # 59 | 2019-10-08, 06:12 | Report

I understand the difference between Android and AOSP.
I know from personal experience that it's perfectly possible to use an Android phone without Gapps and what is commonly known as Google services.
But AOSP is still Google!
The Android Open Source Project is very much a Google project. They hold the reigns. They decide what gets coded and what doesn't.
The implications are vast - it's the main reason for me to not use any Google product, however open source it might be.

And the calls to Google servers are still there in AOSP, and developers of "alternative" OSs based on AOSP rarely bother to take those out. Something that never ceases to amaze me.

So yes, there are still "traces of Google" in AOSP.

juiceme | # 60 | 2019-10-08, 06:59 | Report

People have different needs and priorities. Funny how SFOS fills all my needs but Android does not...