This is just hearsay but apparently GrapheneOS will be unaffected from Play Store control.
this post was submitted on 26 Aug 2025
308 points (99.4% liked)
Privacy
41504 readers
357 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
What do you think will happen next?
Development of Linux on mobile will ramp up.
EU or similar wrecking Google over being monopolistic would be nice but unlikely.
Same but targeting phone manufacturers.
We need the EU to regulate Banking and Payment apps to not rely on Google apis first and mandate that they have to be available in open app stores or as apk.
They don't even do that with their own apps.
Maybe they can regulate themselves first as a start then. They already use Matrix, so it’s not like they are completely lost regarding IT Security and FOSS.
Right now the EU regulation is pushing banks to require more of Google or Apple because it's unclear and banks won't take a chance of getting fined.
Among the requirements are: ensure the device and the OS were not "altered". What does that mean exactly? Answer: [crickets].
But that's why many banks just go with the Google Play Integrity API.
load more comments
(5 replies)
From the EU to wreck Google e-Foundation, with advantage substituting GMail, GDocs and GDrive >Murena Workspace, Murena Phones (FairPhone) with /e/OS by default, Murena is OpenSource (GitLab) selfhostable or Freemium if not, including Murena Cloud., All 100% de-googled and encrypted, no knowledge. The EU offers enough alternatives, you only have to use these.
load more comments
(5 replies)
Plain burner flip phone and a wifi only Linux device that connects to a hotspot. F google and Apple.
@Sailor88@lemmy.world @ComradePedro@lemmy.ml
I'd really love a Linux phone (personally, I have a Linux PC and I use Arch, btw) so don't get me wrong when I question: what about the banking and government apps? Yeah, because finance systems are getting increasingly digital around the world and every payment will eventually need to involve banking apps, and you guessed it: just Android (Google) and iOS (Apple), no Linux, no KaiOS. One will eventually need apps to pay for rent and consumer bills, even for buying groceries, as fiat currency will get more digital and less physical.
And, no, European Union won't fight against it because, in fact, the same European Union is seeking to digitalize EUR (see "ECB publishes third progress report on the digital euro preparation phase", published by European Central Bank on 16 July 2025). It's not a matter of if, but when physical currencies will become ruled out, and "For Our Security™", Linux (alonside other alternative OSes) will either be ruled out from internet banking altogether or it'll be forced to comply with "security requirements" that, in practice, would turn Linux indistinguishable from Android and iOS.
And this seems to be where everywhere is headed, it's not just an European or USian phenomenon. The future is bleak.
You will use Monero or Parrish.
No, seriously though, the circular economy is growing and by contributing to it, you are giving the middle finger to these fuckers.
load more comments
(4 replies)
load more comments
(6 replies)
load more comments
(4 replies)
As of right now, it's looking like GrapheneOS will be unaffected, and Google has yet to lock down the bootloader. So this should remain a valid option for at least 2 years.
Other than that:
- Any smartphones with an unlocked bootloader + any ROMs without gapps
- Chinese smartphones with non-Google Android builds
- Linux smartphones
- Bonus: Huawei is about to release their own non-Android OS, but I wouldn't expect it to be privacy-friendly
Honestly there probably isn't any good, long-term solution. Personally I'm somewhat shocked we've gone this many years with reasonably open smartphones. Next step is probably closing bootloaders in new laptops, as part of the switch to ARM (which is already undergoing).
load more comments
(6 replies)
Yes, absolutely there is hope.
Phones that don't support Google play services (AKA any hardcore privacy phone) will not be directly effected by Google restricting sideloading. The restriction is only for phones that use the Google suite. (source: https://9to5google.com/2025/08/25/android-apps-developer-verification/ "This requirement applies to 'certified Android devices' that have Play Protect and are preloaded with Google apps.") Graphene OS isn't going anywhere, AOSP is open source, even if Google tried to make that change in the OS, the community would hard-fork AOSP instantly and continue like nothing ever happened.
Realistically this is going to squeeze people "in the middle" towards fully-google controlled Android (one exteme) and towards fully-de-googled Android (the other extreme). Its just elminating the middle. Which is bad for people trying to gradually de-google their life, but not as dire as it might seem.
On the bright side, this is an opportunity for play-services spoofing to become commonplace and easy, and could cause more apps to avoid google play services. The EU also has a shot at forcing google to allow sideloading, since they've recently been forcing Apple to move in that direction.
So, while not a bright future, its far from hopeless for privacy respecting Android phones.
This is the point, isn't it?
Lock down their own ecosystem because they're jealous of how Apple does it, so they can herd all users into their walled garden. Then close the gates behind them. There's no easy way out, you can't just wander back and forth anymore. You have to scale a wall in the dead of night and shed a tear as you look back and see everyone else having a lovely life, then set off into the dark forest of privacy on your own.
People hate friction in the first place. This is as much friction as they can realistically make on their own without triggering anti-trust cases and EU fines.
"Linux phones will skyrocketed" by who? Nerds, the comum user doesn't care if Android is proprietary or opensource, they don't even know.
There's already other mobile OS but have the same issue, no apps or developers interested on making apps for it.
FirefoxOS, Ubuntu touch, something else Linux based, it's for some nerds play on a secondary phone.
Comum people don't stop using Windows or macOS because it's proprietary or a privacy nightmare. EU didn't stop selling iPhones because it's proprietary.
It's the device vendors that decide which OS would ship, and people will use it
And yet Linux usage on desktop is rising.
Not as much as it should be IMO but it's fallacy to think things won't change.
Or is IBM still top dog?
load more comments
(1 replies)
load more comments
(3 replies)
Until substantially more people join the fight for privacy or something else fundamentally changes, I think there is a very real possibility of Google completely clamping down on Android while governments and workplaces mandate apps that only run on phones with all of Google or Apple's bells and whistles.
But the folks at GrapheneOS, Calyx, and Murena seem to be a devoted and resourceful bunch, so I am hopeful that they can give something for us to work with, even if Google pulls the plug, whether it's a fork of Android or rebasing to mobile Linux.
If that all falls through, I'll look for whichever phone supports Linux best and eventually move everything over. The vast majority of the apps I use regularly on my GrapheneOS phone aren't very demanding and have a decent alternative on Linux. And whatever apps are forced on me by other people will reside on a dedicated Android phone, ideally with a removable battery.
For this year, I'd still recommend a secondhand or reseller Pixel with GrapheneOS. Everything just works on it.
we need the devs who make lineageos to come up with something, because that's what most people have access to. and their stance is that they won't be doing anything to bypass any of google's restrictions.
that's if unlocking is still a thing in the near future.
Linux phone will hopefully become realistic thing.
But the more this goes on the more my attitude has changed. I now do far less on my phone, I'm more careful about what I expose to it. As a result I spend very little time on it and that's been great.
To be clear I hate what's happening, it's just been working out to improve my time.
Said this in another thread
So how long until celluar providers also say you have to have a trusted device to activate your SIM? Apple, Google, Samsung, automotive and Windows would be fine and they’d probably allow their branded or limited hotspots.
This would basically eliminate any Linux option (pc or phone), and DIY devices. I could see other OOB vendors getting on board to be certified to have a certificate issued to them.
with esim, this gets even easier for them to do.
Fuck it, I'm going back to Landline
Weary traveler, I beseeth thee to not harken down this path.
I hear tales of dark spirits haunting those old byways. Ones of greed, with an emotionless façade, and hunger for gold from too-eager souls.
load more comments
(2 replies)
load more comments
(1 replies)
Things are fine for now, but long term Google will force out FOSS third parties. Linux phones get better every day, though. I imagine Linux will be relatively ready for primetime by the time Graphene can no longer continue.
GrapheneOS still intends to support all the supported devices until EOL. The sideloading change doesn’t affect them. It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services. As per the rip out of the device trees for Pixels, that just makes Pixels like other phones. GrapheneOS has been able to expand it’s automation to build that device support themselves. For new devices, making the support will take longer than it did in the past though, but they will still support those Pixels, as long as they meet the hardware requirements and still allow third-party OS support with all security features intact. Besides that GrapheneOS is actively talking with a major Android OEM right now in order to help them reach the security requirements for a subset of their future devices. They are very optimistic about that.
Android is Linux of course since the Android kernel is a Linux kernel. I’m aware you are probablly referring to using traditional Linux OSes that are typically used on desktops on mobile phones. That would, however, be a significant regression for security. Android and iOS are both modern mobile OSes with an in-depth security model which includes a mandatory app sandbox with a sane permission model. This is not present on traditional desktop OSes. This is not meant to diss on those OSes, they are just children of their time, they were created much earlier, security practices have evolved. I can see why it would be a fun experience though to tinker with, it would just not be a secure experience and it’s unlikely to get there because the improvements in traditional Linux distros go much slower than they go on Android and Android is already massively ahead.
load more comments
(9 replies)
Well, I'm still hoping for Linux phones to skyrocket a bit when more people realize we're fucked with Google. But as of today I don't think we have a reliable alternative for day to day use...
We first need Linux phones to be reliable daily drivers; so far everyone I've encountered who has a linux phone says it's usable... wiþ caveats.
We have to eliminate þe caveats in at least a handful of phones, first.
load more comments
(1 replies)
At this point, I'm just hoping to grab a HarmonyOS phone soon. I'd rather have China hoovering up my data than the US, 5 &14-Eyes, and fascist US tech corporation. Terrible compromise, but I don't see an inexpensive Linux phone on the horizon any time soon.
load more comments
(5 replies)
Related: Has anyone here used Pretty Good Phone Privacy (PGPP)?
What about a Murena phone such as the Fairphone 6 ? Is /e/os impacted?
Fairphone 6, especially with /e/os is not an option atm from a security standpoint. But then again, no phone is except iPhones and Pixels (and more recent Samsung phones).
Fairphone 6 does not keep up with standard Android privacy/security patches and has no secure element to provide working disk encryption for typical users not using a strong password, among other flaws.
Regarding privacy, Murena is shilling their own proprietary Apps as alternatives to Google.
/e/OS includes numerous non-private apps and services. The Murena voice-to-text service included in /e/OS even sends user speech data to OpenAI with no local option compared to Apple and Google both offering offline speech-to-text support via local models which users can make sure is always used:
https://community.e.foundation/t/voice-to-text-feature-using-open-ai/70509
Taken from the Graphene OS forum
load more comments
(14 replies)
load more comments
(1 replies)
There's no hope for privacy at all as long as American and the 5 eyes exist.
load more comments
(1 replies)
I'm not gonna go looking for it or share it, but I am here using my Librem 5 and kinda feeling like that kid in the meme hitting a bong in the background while people in the foreground fight.
load more comments
(8 replies)
I'm afraid not.
I hope so. But I'm gonna be real grumpy about it when I can't tap to pay for shit anymore because all of the standardized payment apps will only work on signed Google and Apple devices.
load more comments
(2 replies)
view more: next ›