Nice, hopefully a good amount of sucriptions will start for Jolla and SFOS :).
But @jolla should actively start asking and also accepting money from european digital funds. If they completely turn to openness and transparency. I don’t see any conflict in getting governmental funding, in the means of providing a free and opensource infrastructure that europeans could then use. Instead of a product of a Duopolist, with incompatible data policies that lobbies EU institutions and politicians to keep up the duopoly…
Porting means, modify SFOS in a way that it can be flashed onto a not officially supported device. Then to provide the flash file and information ‘how to use’ to the public in some way for download and application. That’s hard work, but it has to be done only one time by the porter.
A user of a port has not to port SFOS because the port yet has to exist. The user ‘only’ has to find the information, find the download, find and get the requested device/version, follow the guide and hope for device manufacturer hasn’t changed anything. This is hard enough.
Thanks for your explanation. It’s nice being able to do such a thing. Must be fun for some. Yet this is not for everyone. I have a Volla 22 and I followed the threads about porting to a Gigaset with interest but did not find a clue for non-techsavvy people how to get that port. And of course there is no support for Android apps.
It’s also a difficult construction: Sailfish is licensed, has certificates, proprietary parts. It’s a company that leans on community devs too, but still this company is necessary to my opinion.
I would say community ports are for individuals who no longer need Android apps and want to experience the pure flavor of a real mobile Linux smartphone operating system.
Pure is the right word indeed. It’s called ‘purism’.
I am using just a few Android apps, only open source ones, because there are no Sailfish equivalents.
You should not expect to much and it is not fair to compare it with the two big ones.
I’m glad with the system we have and looking forward for the system to get even better…
With a subscribtion of some 10, € your not in a position to expect too much.
Still every little bit helps. Money, translating, coding…
What is a practical difference between https://shop.jolla.com and https://commerce.jolla.com ?
Thanks for info! Didn’t know that the ‘commercial…’ homepage exist. Worth to visit, very interesting.
You can install Waydroid on SFOS Ports. There is also a guide for this. It’s not as beautiful as original Jolla appsupport / Aliendalvik but it works and this way one can run Android apps on many SFOS ports.
I don’t disagree with your statement, but I really hope that we will get a device that fits my needs as a daily driver. Right now the camera and GPS things keep me away from SFOS as primary phone. And if Jolla wants to survive they need an amount of devices (in total numbers, not model variations) they can hit the market and work out if the box with the standard basic features of a modern smartphone. And that’s calls, messaging (including RCS), location, parental controls, photos, cloud storage and sync. If all this works out of the box a SFOS phone could hit the European market as a truly European phone and system that fully respects European data protection laws. So in the end adding those features would allow to start a specific marketing, maybe even together with a provider.
Small example: German Telekom has its own cloud service Magenta Cloud. That’s based on Nextcloud. So as a provider Telekom could sell a SFOS phone as data protection focused device and already has its own mail service and cloud storage, both not tied to any foreign company.
Buts that’s all just a try to think in future directions.
I would also be willing pay something (even monthly) if I’d knew that’s there’s active development and what to expect in the (hopefully near) future. Just remember what’s still missing for C2 and Xperia 10 IV/V.
So for me the missing Roadmap is the main reason that keeps me away from an immediate start of such support. But I agree that Jolla needs money, but up to now I just have the feeling that this money will just keep the company alive, without any further development of SFOS. But as, said - just my thoughts/feelings/opinion, and I’d be glad to get a proof that I’m wrong.
Honest question, why do you need RCS? I never missed it yet.
sick, nice to have the option!! would love to chip in once more of the stuff is open source!
Please see here:
Because I don’t use anything from Meta, but most people around still use WhatsApp. RCS chats allow sending everything with the native messages app of Android or iOS, and except a few cheap ones nearly every mobile provider supports RCS, and it’s mostly active on newer phones by default.
So in short: RCS offers (me) the same communication possibilities than other messengers without the need of installing a specific app and the need to registration. So I can reach everyone I need and can send files, photos and so on, especially as the service just uses my data plan like every other messenger.
@Seven.of.nine you know I know that
- but why do we need to change that ourselves, why are such things not done by default or at least a switch in the location settings?
I always try to think from a normal users point of view, not like us freaks and nerds. In the end Jolla will just ha e a chance to survive (and grow!) if they hit a wider market share, and for this a phone thst works out of the box is needed.
This I part of those all the smalls things I always like to remind, because there are so much things that don’t need much effort to be done, but would help to make SFOS better by default right when flashing or updating a device.
Subscribed for every month ! ![]()
I don’t want to go too far off-topic but this is something I do not understand about RCS. This is a complete Google-thing since most carriers do not provide an own server but rely on the Google one as it is cheaper for them. So even iPhone user are using a Google service here, and if SailfishOS would support RCS you would have a constant connection to Google if your carrier is using Google Jibe. Is this really better than an optional client from Meta with e2e encryption?
Besides, even on Android the Google server is refusing connection for rooted and unlocked devices, do you really think they would allow a SailfishOS implementation?
Thanks for the info. I was not aware of that.
Hence interesting question.
But, yes we’re a bit OT.
Let’s continue this subject here?
Monthly Subscription
using e-card
Using a port somebody made doesn’t mean you have to port anything. There’s no difference between official port and community port, they’re ported in the same way, and people are using both.
Again nobody said anything that you have to port anything. We’re talking about already made community ports. You’re mixing stuff and introducing false information.
Also incorrect, honestly, if you have no clue what you’re talking about, why do you even make such statements.
And you would be wrong.