No thanks, I’d rather use a Google Pixel with GrapheneOS
Image transcription:
buy privacy-first community driven phone look inside closed source OS with no recovery image and outdated dependencies
No thanks, I’d rather use a Google Pixel with GrapheneOS
Image transcription:
buy privacy-first community driven phone look inside closed source OS with no recovery image and outdated dependencies
Uh even this short stab is quite wrong. Here notes from Jolla itself for Sailfish OS 5.2
The base of Sailfish OS is a full blown Linux, way more open than Android (more options for the user, less secure than Graphene, which has that as main goal) you can easily install/compile Linux software on it.
Close source components are used. Parts of the UI (Jolla is open sourcing more and more), libhybris to run closed source Android drivers, Android App Support.
So yes its not as open source as debian, but offers more freedom to modify the OS than Graphene and gives you near full control.
So basically no need to outrage?
Also not got mine yet in batch 1.
I’m in batch 2, so I guess I’ll be waiting for a while still.
No, not at all. Just check the things claimed by @pewpew quickly with a search engine or an AI of your choice (Always check the sources it finds!) and you will see that the overwhleming majority is wrong and the rest is blown way out of proportion. See also my answer to his retort below.
It may be a private phone, but you don’t really know whats going on under those proprietary blobs.
Sailfish OS is the definition of proprietary software. You need to buy a subscription if you even want to install it on third party devices.
It’s like Windows but it claims to be private and commnunity driven while not providing the source code to the entire OS. It’s a little misleading to me
Please don’t hate on the one European company trying to do things right. Support them in making things better.
You also need a license to use Redhat Linux
Free to obtain and refresh every year for 16 devices
I do prefer a Fairphone, a Librem Phone or a PinePhone with postmarketOS though. Install Niri or MauiShell and Waydroid to it and you have pretty much it.
Yes tthats pretty much the closest you can get to fully open source today. I have a number of devices I use: A Pixel 5 with Graphene because the modern world relies to much on Android Apps, also used as hotspot, a Nokia N9 for reading and light browsing, occasional navigation a Nokia N900 with Maemo Leste for secure administrative work.
We also have Sailfish devices in the house
Pixel 5 are pretty good, I’d really like to have one of these because they’re the nearest-to-mainline-Linux Android phones.
Sorry, but no. AOSP and Graphene do not use any proprietary blobs. They are 100% open.
By your own post, SailfishOS uses closed source components.
So does Graphene.
Both ship: Firmware, the HAL components (which are way more critical in my eyes as they have low level hardware access and could hide anything from the OS) Example for these are: The Camera Stack, the Audio Stack, under Graphene the Widevine DRM components.
Sailfish can run without these, e.g. on the Pinephone. Graphene OS can’t Graphene additionally comes with an eSIM binary, which is disabled by default Sailfish comes with proprietary UI components, a choice the company made because of their limited manpower as it allowed them to provide features where currently no open source solution exists or existed at the time of implementation) examples are swipe gestures for the keyboard, MS Exchange support, Android App support. That not great, but far from a closed source system where everything is closed source. There exist many patches for UI components because they are partly open source.
The OS ist still Linux, that is true. It is even LInux+GNU which Android is not. It is Linux with closed source components, thats true too.