Sailfish OS – Independent Mobile OS
sailfishos.org
sailfishos.org
Furthermore, the parent company Jolla, did a horrible job with their tablet fundraiser and subsequent crash. This bred a lot of badwill in many like me. For me the biggest issue wasn't even the loss of money, since I understood the risks involved with a hardware fundraiser. It's that they were not transparent or open with the community; infrequent and opaque updates were the norm. Then all of a sudden they ran out of money and we're told maybe if we're lucky we'll get a refund eventually? They'll have to do a lot better to gain my trust.
For comparison, I also funded the Pyra [0], an ultra portable mini computer which runs Debian. Despite having paid more, and having already waited much longer, I have no big complaints. The team posts very detailed updates every 1 or 2 weeks. When anything goes wrong or things get delayed, they include it in the update.
Edit: It seems the UI library, Silica, is sort of half open, half closed: https://github.com/dm8tbr/sailfishsilica-qt5. Really think Jolla should look at that.
Plus, you might just be able to use anbox to run signal anyways. https://anbox.io/
It's far from a perfect solution, but I feel like it comes closer to the mark than Signal.
https://www.reddit.com/r/GPDPocket/comments/6idnia/linux_on_...
Oh, nevermind, they take Bitcoin, which means other people paid for my new phone :-)
Are these updates available to the public or only pre-orderers? I'd be interested in following if the content is available. Is it the "Pyra News" section of the forum?
This brings no advantages over AOSP. And in before people pull the argument of Google Apps, Android is perfectably usable without any of the Google proprietary software.
In a virtual machine maybe, surely not on any phone where most device drivers are closed blobs. H4x0r5 may hide backdoors into compromised play store apps, but governments do it in device drivers, with 100% success rate because a closed source device driver is something 100% of the user base has installed, keeps running 24/7 at maximum privileges and has 0 chances to audit or examine.
Today closed device drivers, binary blobs etc. are places to look for malware; until a device is completely open it cannot call itself safe or secure.
Of course Sailfish doesn't solve that problem, neither does Linux, BSD or whatever. I wasn't making a pissing contest between operating system (which is likely what trigger happy downvoters got) but simply stating a sad fact: closed device drivers are the best place to put spyware on and get 100% success, period. They can't be audited, they can't be uninstalled, they always run and they have maximum privileges.
If I'm wrong (and trust me, I hope so) I want facts proving it.
And yes they are entitled to keep whatever they like proprietary, as long as they stop trying to pretend they are interested in promoting an open source mobile OS, out side of the AOSP internals. If I'm wrong and they have contributed significantly to the AOSP apps then I take that back.
I've heard Bruce Perens talk about it a few times, and even on the OSI website (https://opensource.org/history) they state...
"The conferees believed the pragmatic, business-case grounds that had motivated Netscape to release their code illustrated a valuable way to engage with potential software users and developers, and convince them to create and improve source code by participating in an engaged community. The conferees also believed that it would be useful to have a single label that identified this approach and distinguished it from the philosophically- and politically-focused label "free software." Brainstorming for this new label eventually converged on the term "open source", originally suggested by Christine Peterson."
You could be right though and some may have seen the non-commercial aspects of the word free as a tertiary benefit, but the primary stated goal was to distance itself from the ideals and politics of free software.
I agree with you though on the last part. Even as someone who uses the term free software, I often use the term open source while using search engines because searching free software brings up sites with freeware/adware/shareware and stuff I don't want. I also think using loan words like "libre" are a stretch for your general public. At work I tend to use "Free and Open Source Software".
LineageOS is also better, but includes proprietary drivers: https://lineageos.org/
Sailfish has proprietary drivers AND many of the GUI components are proprietary. I don't know if this list is still up-to-date: https://wiki.merproject.org/wiki/SailfishOSS
Tidbits of my personal opinion:
- SailfishOS is much more unixy - getting a shell, setting up a SSH server and syncing files with rsync was no problem at all. I have not yet understood the directory structure of LineageOS
- The permission of apps was a problem, but not more so than on my laptop. Ideally one could solve this by only installing trusted apps, but this was unfortunately not an option (Whatsapp)
- The native e-mail client actually knew about e-mail. On LineageOS, I had to install K9mail to get such simple things as proper treatment of signatures delimited by '-- '
- The user interface on Sailfish was much more usable, in particular the swipe gestures to quickly close apps as well as the tiled view from which you can directly interact with open and running apps. Feels more like a proper computer instead of a single-threaded/single-application-at-a-time thing.
- I actually trusted the team at Jolla with providing decent updates etc. With LineageOS, I am using some unofficial ROM provided by a random guy on a largely random forum which may or may not work with over-the-air updates (it’s claimed to work but I haven’t tried it yet). I definitely trust my phone less now than I did before.
- The hardware is of course much better on the OnePlus -- had Jolla/Sailfish sold something equally good or even only slightly worse, I would have bought that again.
No need for random forums. You should have been able to download an official LineageOS build from https://download.lineageos.org
> No need for random forums. You should have been able to download an official LineageOS build from https://download.lineageos.org
But even if this worked (from what I have read, others had problems), there still would be nothing to make me trust "LineageOS", as I said in the reply to your sibling - there is no real name associated to the project, no GPG key embedded in the web of trust anywhere that I can find and not even on the download page are actually signed binaries I can verify myself to be trustworthy. Not even the Wikipedia page of the project lists a single individual involved!
But you're right, it's not GPG, and hence no web of trust behind LineageOS.
I'd actually trust my phone more (using the official LineageOS build) as basic system components are FOSS (although there are some firmware blobs).
Yes, but everything I have read, anybody who tried only the official ROM had various problems, e.g. with the camera. Hence I settled on an unofficial ROM.
But even if I used the official ROM, there is absolutely nothing on the LineageOS website that makes me trust them. No real names, no GPG keys, nothing. Just "The LineageOS project", a bunch of pseudonyms in the blog entries and apparently some LLC. Even their "Legal" sub-page does not contain anything at all.
They'll be releasing official SailfishOS images for Xperia X somewhere next month iirc, see https://sailfishos.org/community6/ (scroll down). It'll not be free however, the price they revealed is 50€, and iirc it's yearly.
Note: I used Sailfish OS for 2 years
It's even less open-source than AOSP.
At least Jolla claims to test and verify behavior of applications offered in their store, but it is up to you to trust any third-party applications you run.
True, good point about the testing!
I've used a Lumia and it was pretty much worthless because I couldn't find any of the apps I normally use...
I've tried that in the past, and it worked quite well. There are a lot of good apps on F-Droid, then you can get access to others through APKMirror, or methods of downloading from the Play Store. Of those, I'd say about half work without complaint (including Whatsapp), a quarter complain and still work, and a quarter don't work. I also used (and still use) a few web apps for things like weather.
At this point all they'd need to do to make this whole thing make sense is to open source it...
Why wouldn't a fork of Android be a functional mobile Linux OS?
Most of Sailfish's UI components are proprietary, which is a more severe issue IMHO.
I've got a super computer in my pocket, there's no excuse to be so slow and jittery, it's been 20 years now, it's time to give up on the "java will be as fast as c one day" dream. Most apps are glorified list views yet they still take several seconds to start.
There's a tonne of google crapware that comes with every phone that can't be removed. Google has been promising to split this out of the OS for a quite few years now yet I don't see any progress. This is the only issue that forking would solve (while creating others).
The development story is the worst I've ever encountered. Untestable God-classes that every activity has to inherit from. Awful convoluted build tools that require and IDE to use (they aren't documented). A hideous xml based UI library that pretends it's as simple as HTML but makes things more complicated. The list goes on.
No one does security updates. Even googles flagship phones will only get 3 years of security updates at best. If you buy a mid-range phone you can expect a year if you're lucky.
I refuse to believe this is the best we can do.
I agree, but I don't see how Sailfish fixes these points. For example I can't buy any phones with Sailfish pre-installed and 3 years of security updates guaranteed.
The best thing to fix the update problem would be open-source drivers IMHO. And Sailfish isn't about that, it uses the same proprietary drivers as Android.
> The development story is the worst I've ever encountered. Untestable God-classes that every activity has to inherit from. [...] A hideous xml based UI library that pretends it's as simple as HTML but makes things more complicated. The list goes on.
I have developed an Android app and agree! It definitely is awful. But due to the large community you could achieve quite a lot, without having tested it I would assume that developing feature-rich apps for Sailfish is harder right now.
> Awful convoluted build tools that require and IDE to use (they aren't documented).
AFAIK Sailfish uses Qmake and QtCreator which are even worse IMHO. Regarding the documentation Android has lots of StackOverflow answers going for it.
Would be interesting to know the opinion of someone who has developed an app for both systems though.
Jolla has been releasing Sailfish OS updates every few months for the last three and a half years. I imagine that they would keep doing that as long as they stay alive. But my imagination is no guarantee. Especially since I can also imagine their hardware vendor partners not wanting to have to work on regularly updating their modifications to changing versions of the base system.
IIRC for Sony devices you get 1 year of Sailfish updates for 50 €.
As far as I know, Jolla has completely stopped selling their hardware. I don't know if you would be able to buy a used one. A quick eBay search didn't bring up anything.
This very same "we" engineering community chose to give all its mindshare and attention to Android at the time so this is basically the scenario we deserve.
Reminds me of when I tried to buy a Jolla phone after my N9 and that thing was nearly impossible to get in the US.
They've announced it will be available in September. That doesn't necessarily mean it will be released when they claim.
They have a history of releasing overly optimistic press releases and then failing to deliver on time or at all. [0]
[0] Jolla tablet backer here, still waiting for my refund 3 years later
I've been using for past couple of months, and I can't say I miss anything from Google play services. I highly recommend if you happen to have one of the (few) supported devices.
Honest question. Not intending to be snarky. Reminds me of the many Chrome knock-offs that focused on a particular aspect of browsing. Any advancement/advantage would be quickly adopted by the mainstream market leaders.
An enormous amount of open source development on Linux is not driven by a "market" in the sense of making money either. This doesn't answer your question directly, but maybe the question is ill-posed. Do we want or need a "viable market" that looks like crappy ad-infested Android bloatware?
(Just to be clear, no, I am not saying that all Android apps are alike.)
On the bottom of the homepage.
Quite disingenuous if only Android 4.4 and below is supported.
Oh, and note that Android support is a commercial feature. You will not get it with any third-party device.
For the time being. I'd wager many/most new applications start with minimum 5.0 unless they have an explicit reason to choose otherwise.
> no results found
However any mobile OS advertising itself as 'private and secure' is just lying if it is installed on a handset that hasn't dealt with the baseband issue - and none of them have or likely will.
That device is huge, I'd much rather carry around a smartphone in my pocket that is a fraction of the size and weight.