Dutch university to start handing out only Fairphones to employees, instead of buying iPhones or Samsung.
-
@wsslmn @alloalli @vosje62 @BuyFromEU First, /e/OS would have to work without leaks to Google. And companies should provide apps for the (working) /e/os , also without leaking data to Google.
@Fietsbel @wsslmn @alloalli @BuyFromEU
When i looked for it in 2024 all apps I needed worked good on e/os.
And there is good info available on that.That some apps will never work will be in most cases intentionally. If you want to make money with it by data grabbing, you don't want to work it to work on another os where you can't grab the data.
-
@Fietsbel @wsslmn @alloalli @BuyFromEU
When i looked for it in 2024 all apps I needed worked good on e/os.
And there is good info available on that.That some apps will never work will be in most cases intentionally. If you want to make money with it by data grabbing, you don't want to work it to work on another os where you can't grab the data.
@vosje62 @wsslmn @alloalli @BuyFromEU Obviously, I don’t engage in criminal activities on my phone. I hinted at home-managing apps like Tahoma, apps for security systems already in place, banking apps, and the like.
-
@alloalli @vosje62 @wsslmn @BuyFromEU That‘s not correct: also Android Open Source was developed and is thus owned by Google, see https://en.wikipedia.org/wiki/Android_(operating_system)
So, legally, Google could still interfere remotely, I suppose. And Google comes under U.S. law, and you know what that means with the creepy orange in the White House.@Fietsbel @vosje62 @wsslmn @BuyFromEU
as I read it in Wikipedia: the AOSP software is free under Apache licence, but the name Android and it's logo are Google's propretairy, so a software system based on AOSP but renamed like e/os can't be influenced by Google
Quote from Wikipedia:
"While AOSP is free, the "Android" name and logo are trademarks of Google, who restrict the use of Android branding on "uncertified" products" -
@mfr @TrVr @BuyFromEU @murena that looks a very, very minor inconvenience. Yes tap to pay doesn't work unless you use Curve, which is owned by a zionist. I just bring the credit card with me
️@danielezomg @mfr @TrVr @BuyFromEU @murena indeed i no longer use wallet and just use my cards. Just as convenient without the extra analytics
-
Dutch university to start handing out only Fairphones to employees, instead of buying iPhones or Samsung.
@BuyFromEU Nice! If only they were #Linux powered too
-
Dutch university to start handing out only Fairphones to employees, instead of buying iPhones or Samsung.
@BuyFromEU Very pleased with my Fairphone. It was in my pocket when I fell off my bike going too fast down a hill and broke my arm. It probably saved my hip. It was still ringing, so I decided to replace the screen. Still going well 3 years later.
-
@wsslmn @alloalli @vosje62 @BuyFromEU First, /e/OS would have to work without leaks to Google. And companies should provide apps for the (working) /e/os , also without leaking data to Google.
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU But the Wikipedia page you are linking to says /e/OS does *not* leak data to Google (they challenges people to find leaks).
The reason is that /e/OS does not use Google Play Services, but emulates it using microG. Of course, if you are installing apps from the Play Store and using the Google notification service, you will leak data, but that is your own choice.
-
@wsslmn @alloalli @vosje62 @BuyFromEU The issue is: who maintains and updates the code? On my current iPhone it‘s Apple, with any version of Android, it would be Google, am I right? So there would be a possibility for Google then to intrude into my phone, and the problem would not really be solved, except maybe for experts familiar with the details of the source code. If that level is required: that’s too much, especially for ordinary people without any affinity with science or technology. 1/
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU Yes and no. Google maintains AOSP code, but Google does not directly push compiled code to an /e/OS phone.
The /e/OS developers take the AOSP code, rip out things (like Google bits they don't like) and put their own bits on top. Then they compile the whole system (minus device firmware blobs) themselves and push the result out as an OS image.
So Google does not have direct control over an /e/OS phone.
-
@wsslmn @vosje62 @BuyFromEU My idea would be to develop all necessary apps also for EU-made phones with EU-made OS.
@Fietsbel @wsslmn @vosje62 @BuyFromEU /e/OS is a European OS. Yes, it is built on AOSP, but it would be silly not to do that. Using AOSP makes it so that you don't have to develop the whole mobile OS from scratch and gives compatibility with Android apps.
Murena compiles /e/OS from the AOSP source with their own changes on top of it. If Google ever stops publishing AOSP sources, the E foundation/Europe could fork the AOSP project and continue developing it.
-
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU Yes and no. Google maintains AOSP code, but Google does not directly push compiled code to an /e/OS phone.
The /e/OS developers take the AOSP code, rip out things (like Google bits they don't like) and put their own bits on top. Then they compile the whole system (minus device firmware blobs) themselves and push the result out as an OS image.
So Google does not have direct control over an /e/OS phone.
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU Other Android vendors also build their own images from AOSP with their changes on top of it.
*However*, they also include Google Play Services, which gets privileged access to everything. /e/OS replaces Play Services by microG, which is an open source implementation of many of the Play Service APIs (needed for app compatibility).
-
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU Other Android vendors also build their own images from AOSP with their changes on top of it.
*However*, they also include Google Play Services, which gets privileged access to everything. /e/OS replaces Play Services by microG, which is an open source implementation of many of the Play Service APIs (needed for app compatibility).
-
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU But the Wikipedia page you are linking to says /e/OS does *not* leak data to Google (they challenges people to find leaks).
The reason is that /e/OS does not use Google Play Services, but emulates it using microG. Of course, if you are installing apps from the Play Store and using the Google notification service, you will leak data, but that is your own choice.
@danieldk @wsslmn @alloalli @vosje62 @BuyFromEU If they wouldn‘t fear leaks, they wouldn’t „challenge“ people to find any, would they? - Yes, that’s clear to me, regarding the apps. But then the developers of the Apps would have to provide a version for open-source /e/OS, without any leaks to Google, of course.
-
@Fietsbel @wsslmn @alloalli @vosje62 @BuyFromEU Other Android vendors also build their own images from AOSP with their changes on top of it.
*However*, they also include Google Play Services, which gets privileged access to everything. /e/OS replaces Play Services by microG, which is an open source implementation of many of the Play Service APIs (needed for app compatibility).
@danieldk @wsslmn @alloalli @vosje62 @BuyFromEU Okay thanks, that’s good news. Hope the developers won‘t overlook any leaks to Google.
-
@Fietsbel @wsslmn @vosje62 @BuyFromEU /e/OS is a European OS. Yes, it is built on AOSP, but it would be silly not to do that. Using AOSP makes it so that you don't have to develop the whole mobile OS from scratch and gives compatibility with Android apps.
Murena compiles /e/OS from the AOSP source with their own changes on top of it. If Google ever stops publishing AOSP sources, the E foundation/Europe could fork the AOSP project and continue developing it.
@danieldk @wsslmn @vosje62 @BuyFromEU That‘s good news. So, at least people with Android Smartphones seem to be on the safe side.
-
@danieldk @wsslmn @vosje62 @BuyFromEU That‘s good news. So, at least people with Android Smartphones seem to be on the safe side.
@Fietsbel @wsslmn @vosje62 @BuyFromEU Yeah, though the situation is a bit more dire, a lot of Android manufacturers don't allow you to unlock the boot loader anymore, so you cannot install another os like /e/OS. Devices like Fairphone and Google Pixel are the exception.
-
@Fietsbel @wsslmn @vosje62 @BuyFromEU Yeah, though the situation is a bit more dire, a lot of Android manufacturers don't allow you to unlock the boot loader anymore, so you cannot install another os like /e/OS. Devices like Fairphone and Google Pixel are the exception.
@danieldk @wsslmn @vosje62 @BuyFromEU I see. The Fairphone with /e/OS might be the way to go, but migration to it from an iPhone seens a major task to me. Besides I nees a couple of home Apps and must be sure they are available for that configuration.
-
@danieldk @wsslmn @vosje62 @BuyFromEU I see. The Fairphone with /e/OS might be the way to go, but migration to it from an iPhone seens a major task to me. Besides I nees a couple of home Apps and must be sure they are available for that configuration.
@Fietsbel don't forget that there are apps that won't be available for any alternative os. Their business model includes data tracking.
-
@Fietsbel don't forget that there are apps that won't be available for any alternative os. Their business model includes data tracking.
@vosje62 @danieldk @wsslmn @BuyFromEU Well, European companies need not follow their „business model“ on medium or long term. Alternatives can and should be developed.
