Hello everyone, I’m interested in the topic:
“Android will become a closed platform from September onwards. ”What relevance does this topic have for Sailfish OS 5.x? https://keepandroidopen.org/
Thanks!
Someone correct me if I am wrong, but that affect developers more? I would imagine as AAS is currently on A13 level, it won’t immediately affect as there is still few levels to upgrade. Hopefully that will just bring more users and DEVS to SailfishOS and we will have more native apps
2 Likes
I was thinking more or less the same… Isn’t this more a gift for us? Will this not push developers in our direction?
1 Like
I have at least thought so. I see this as good thing for alternative systems, hopefully even adds pressure towards EU to look own option like Sailfish
AFAIU the version for Sony devices use a slightly altered Android kernel. Nothing will change there.
No idea about the J2.
If an Android kernel weren’t available anymore for new devices, I’d say quickly fork what still is, so we (all, not just SFOS) at least have something to start with in the future.
Also, may Google burn in hell for what it did and still does to FOSS and Linux.
11 Likes
No, it isn’t.
Developers aren’t developing for SFOS because they haven’t heard of it, and if they did, they think the userbase is too small.
You can make developing for Android more difficult. That doesn’t change the reason I just mentioned.
The biggest change for developers would mean they will have to use their API’s more, with less insight in compatibility or alternatives. This will mean more and more apps won’t work without an official google build of android, and less compatibility for SFOS AAS.
EDIT: Of course, I am talking about the big companies and organisations. Not about the amazing work this community and other small enthousiasts are doing.
3 Likes
Today I got the alarm by FDroid and posted it here too. This means trouble for de-googled systems and for FDroid. Not unexpected though: Google is a nasty monopolist.
Here is work for the EU.
Sailfish will be untouched and it could even be to Jolla’s advantage if Sailfish matures further.
Does anyone know what it means for Android support?
Jolla could temporarily hire tech experts for testing Jolla2’s and optimising them with GPS.
Devs could develop good working alternatives for Android apps.
Banks can be contacted to get their attention.
It’s important that Jolla2 gets good reviews in tech sites. We could contact the tech journalists of our newspapers. Jolla could contact tel.providers to sell Jolla2.
Just some ideas.
You cold link your topic:
2 Likes
You have done it for me. Thanks!
Hello, as I learned today, the Open Source Project (AOSP) will continue.
Distributions like Ubuntu Touch with Waydroid, and I think Sailfish OS as well, will not be affected.
It’s primarily intended to affect stock Android from Google.
One can only hope that such developments will awaken even more people worldwide to
distance themselves from monopolists.
2 Likes
This whole time as I have understood it, Google just wants to stop or make it as hard as possible to use alternative app stores. Someone correct me if I am wrong, but this is mainly affecting people developing apps for android? And people that would like to use those apps, without forcing dev to send gov ids to google etc
1 Like
Google plans to attack OpenAndroid in September. . This means FDroid and de-googled systems will be in trouble. Fortunately Jolla Sailfish will be unharmed but what will it mean for android support?
https://keepandroidopen.org/
6 Likes
Probably not much changes for AAS in short term as it is still few upgrades away from even current android level. In long term, who knows, could even boost Sailfish usage
2 Likes
It is not exactly a duplicate but may better moved to
2 Likes
Google plans to attack OpenAndroid in September. . This means FDroid and de-googled systems will be in trouble. Fortunately Jolla Sailfish will be unharmed but what will it mean for android support?
https://keepandroidopen.org/
7 Likes
Google started this process already many years ago, e.g. have a look here: Google’s iron grip on Android: Controlling open source by any means necessary - Ars Technica
I think taking open-source components and replacing them with „re-engineered” proprietary code is unethical but this is what happened. Nobody complained back in the days and nobody regulated Google.
In relation to SFOS but also AOSPs that make use of microG like LineageOS, /e/OS, GraphenOS…etc., the question would be how to handle updated Android apps in future that require GAPS with more stringent rules that might break microG functionally. Would they work or not for us? It also depends on developers and the big player apps that require GAPS. I suppose they will unfortunately do as they did already years ago, they simply don’t care about this1% of alternative folks that we are. We need to find a solution, I mean not just SFOS community but all AOSPs and other Linux mobile & desktop distros that can run APK files.
3 Likes
Good morning, I came across an interesting article on this topic at Linux news…
Yes, that’s highly likely, actually a “gift”…
Perfect!, only about 3 months ago, I installed QtCreator 6.10.1 to make apps for a (crappy & cheap) Android phone.
Getting the SDK set up and running properly, has been a journey within itself, let alone using it.
So, thanks to this post, I now realise I’m wasting time playing with this stuff, so thanks for posting!
Rob Braxman, Rob Braxman Tech has been covering this and other Privacy matters for years. His latest Youtube/Odysee video posted yesterday Wednesday 3 March, explains in detail what Google is doing to AOSP. They have been chipping away at it for years - remember when the included keyboard was removed ? It’s the end of it as we use it now. Whilst Sailfish OS itself is Linux App Compatibility is based on AOSP - check on Wiki.