Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sailfish Mobile OS

sailfishos.org

Post reply on HN
Print view View original

121–130 of 148 posts

Re: Sailfish Mobile OS

#121

Post by gbraad »

brylie wrote: post #112
tpoacher wrote: post #92

I used to own a Jolla phone, and there was something magical about it. At the time, their ideas and execution were a breath of fresh air, and the experience was amazing even despite some unavoidable teething problems. I happily used it as my daily driver for about 2 years, proudly showing it off to friends at every opportunity, and not wanting to switch to another phone. Now, as such things go, many of the unique ide…

> Jolla had to close From the best I can tell, Jolla is still an active company: https://jolla.com/

they had to reorganize/laid off a large amount of personnel

Re: Sailfish Mobile OS

#122

Post by ZuLuuuuuu »

necovek wrote: post #117
ZuLuuuuuu wrote: post #108

Earlier quoted context omitted.

I cannot get pass the cookie screen without "accept all". I cannot find "accept selected" or something like that.

If you click "analytics" checkbox, button above changes from "accept all" to "save & proceed". Unchecking it again hopefully does what you desire.

Indeed checking analytics turned the button to "save & proceed" and after unchecking, the button remained like that.

Re: Sailfish Mobile OS

#123

Post by saidinesh5 »

vrinsd wrote: post #78
saidinesh5 wrote: post #64

Earlier quoted context omitted.

The basics of making phone calls, texting etc .. all work well on most of the devices - official/community supported. Older one plus devices, Motorola devices. The guy who ports to some Motorola phones simply doesn't give up and keeps maintaining his ports up to date. Here's the status of various devices: https://wiki.merproject.org/wiki/Adaptations/libhybris

Are you saying that Plasma Mobile runs on any device that is supported by libhybris? I was asking about Plasma Mobile ( https://plasma-mobile.org/get/ ) that the parent mentioned switching to and I wasn't aware that libhybris is a requirement.

If you want a plasma mobile device, your best option is to find devices that are supported by PostmarketOS. That is a distro (kind of like Ubuntu etc ...), which under the hood can use libhybris to talk to Android drivers etc..

https://wiki.postmarketos.org/wiki/Devices

There maintainers create configurations for those specific devices to make them work well with postmarket OS:

https://gitlab.com/postmarketOS/pmaports/-/blob/master/devic...

Re: Sailfish Mobile OS

#124

Post by jcelerier »

happosai wrote: post #73
vrinsd wrote: post #50

Earlier quoted context omitted.

The Sailfish guys are actually the creators of libhybris. If you run SailfishOS you have to first have Android flashed onto the phone. They use the same kernel, camera drivers, GPU drivers, etc as the original OEM including the prorprietary wireless BLOBs and the Android Radio-Interface-Layer ("RIL"). I've spoken to the Sailfish guys awhile back and I get why they did this -- 10+ years ago there was basically no choi…

Libhybris is great for making a tech demo. I wouldn't base a product on such hack, anymore than sell Linux laptops with ndiswrapper... If something doesn't work in the binary android drivers, the vendor won't help you (we support only android, sir). Nor can you fix the drivers yourself, because you don't have the sources or the knowledge how drivers work.

"and yet, it works". To this day my Jolla is the best phone I had, always fluid and reactive compared to much more recent and powerful Android phones. I don't remember any driver issue with it.

Re: Sailfish Mobile OS

#125

Post by nmfisher »

rickdeckard wrote: post #94
bsimpson wrote: post #57

Did something happen that made Sailfish relevant again? Surprised to see it on the front page today. It's unfortunate that they're taking a closed source model when others like System76 and Librem are using their hardware sales to fund open source development. There's also webOS, which was originally funded by Palm and doesn't seem to have any open source development any longer, and the Maui project which is basicall…

> There's also webOS, which was originally funded by Palm and doesn't seem to have any open source development any longer, After a short stint at HP, webOS is now owned by LG, they use it as the OS for their Home Entertainment (TVs, projectors,...) and nowadays also as an Automotive OS platform. Open Source: https://www.webosose.org/

It's very much alive, too - LG just sponsored a hackathon to develop games for the new webOS store (including a Flutter-specific stream) with some legitimately good prizes (I think first prize was $100k, second was $80k).

Re: Sailfish Mobile OS

#126

Post by izacus »

Doctor_Fegg wrote: post #109
izacus wrote: post #102

Earlier quoted context omitted.

The banking regulation is usually introduced across whole EU and this includes new recommendation to phase out 2FA via SMS. Not all countries have caught up yet, but you can expect that to change within a few years.

Which doesn't preclude hardware keypads, which British banks have been issuing for at least 15 years now.

They may have, but here in central EU they stopped to save costs and now the only option on many banks is having a smartphone.

Re: Sailfish Mobile OS

#128

Post by tiltowait »

necovek wrote: post #115
bsimpson wrote: post #57

Did something happen that made Sailfish relevant again? Surprised to see it on the front page today. It's unfortunate that they're taking a closed source model when others like System76 and Librem are using their hardware sales to fund open source development. There's also webOS, which was originally funded by Palm and doesn't seem to have any open source development any longer, and the Maui project which is basicall…

TBH, I prefer all of WebOS (on HP Pre 3), Maemo/Meego (on Nokia N9 and N900) and Ubuntu Touch (on Meizu MX4) over Android for the UX qualities. Obviously, they lacked in phone hardware and app selection, but basic experience was unmatched. IIRC, Sailfish was inspired or derived from Maemo, so I wouldn't be surprised it took some great stuff with it. Hitting the critical mass is tricky without having hundreds of milli…

WebOS was so good. If it had stuck around, I’d likely be using it instead of iOS.

Re: Sailfish Mobile OS

#129

Post by NotPractical »

izacus wrote: post #82
NotPractical wrote: post #34

Earlier quoted context omitted.

So the EU attempts to invade your privacy using smartphones [1] and forces duopoly-brand smartphones upon its citizens, yet it fails to compel Apple to allow true sideloading, so you're stuck choosing between "no freedom but some privacy" or "no privacy but some freedom"? Their digital policy initiatives overall seem like a net loss for EU citizens as it stands. [1] https://www.theverge.com/2024/6/19/24181214/eu-chat…

You really had to stretch a lot of bullshit just to rant over chat control here, didn't you?

I was trying to make a case that when you add up everything the EU has done recently with regards to digital policy, you get a net loss for EU citizens. Their attempt at chat control decrements the score by a significant amount. Amending the DMA to have it not be completely useless would increment it by a significant amount, but it is unknown if that will happen yet.

Re: Sailfish Mobile OS

#130

Post by memsom »

silisili wrote: post #42
FormerBandmate wrote: post #29

Earlier quoted context omitted.

BlackBerry was a huge player. They declined, as with Nokia, entirely because they didn’t use a platform

Well, their problems were manifold and I think the movie does a decent job explaining them. Highly recommend, if you haven't seen it yet. They didn't evolve, took the iPhone as a joke, and when finally playing catch-up, the hardware was awful. If they'd have seen the writing on the wall and responded in kind, I think we'd have all three players around today. Nokia...I don't even want to talk about. I'm still half con…

Nokia failed because Nokia was Nokia.

To elaborate - Nokia innovated a lot. But internally Nokia was chaotic. They were Google, before Google got the reputation for creating projects only to kill them when they had hardly started.

Couple this with the absolute dictatorship that the Symbian division had over what they were releasing as a cellular device, and Meego/Maemo never had a chance. Up till the N900 the Maemo division was blocked from having cellular. After the N900 it was too late really. They clambered to make the N9, but it was at the breaking point and so they did the burning memo thing. The N9 was basically the blueprint for the Windows Phone models Nokia released.

Post reply on HN