428
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Oct 2025
428 points (100.0% liked)
Privacy
42824 readers
664 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 6 years ago
MODERATORS
When will F-Droid stop working on stock android?
There's nothing set in stone yet. Google just committed to doing it is all that's happened so far. But the response against it has been pretty heavy and we'll see how it goes. We have to speak up right now and organize our communities like this post is doing.
LOL. There's dozens of us here.
Try Graphene today. IT WORKS
Samsung s22 and s25, checking in. Graphene won't be viable for the vast, overwhelming majority of Android users today or in the coming seasons.
I hope people figure out some kind of virtualization/docker-containerization solution to the coming Goo-lag.
I'm still holding some hope that maybe Samsung's flavor of the OS won't have the restriction of requiring Google keys. Specially considering that Samsung has its own "Galaxy Store" with app submissions controlled by them, not Google.
Though it's possible they might simply extend the signatures accepted to include also the ones signed by them ^^U ..still it would give them a competitive edge to remove the restriction so they might be incentivized to do it.
I'm hopeful that the hackers will win. I will never underestimate the power of motivated, scorned engineers.
Probably by removing some google service or some other gimmick it can be bypassed
Except for stuff you really need like online banking, tap payments and digital ids
All my banking apps and credit card apps have worked flawlessly on Graphene OS. You're correct that tap to pay doesn't work, which is a bummer. But that is just Google spyware as well, honestly.
I heard about this a while ago, but I remember the GrapheneOS team talking about suing Google if they didn't allow them to pass play integrity checks like they should be able to, but Google just doesn't let them. That's the only reason tap to pay doesn't work and some baking apps have issues, its Google purposefully limiting graphene OS so they have a competitive edge somewhere.
Sadly not the case here.
No they work. It's not like LineageOS. Both Bank apps I now need, work on GrapheneOS but did not on LineageOS. It is my compromise without being compromised.
Plenty of bank apps work just fine. None of the ones I've tried had problems, except Santander, which works perfectly after changing a setting.
Not here in Norway. You need BankID which is an app that well, requires a lot of stuff.
get the physical button-device sent to you by ypur bank
Personally I don't need or want any of those things on my phone.
You can do online banking via a browser, it's clunky but you generally just need to be more prepared
Manageable.
I don't have time today
Ok, I’ll extend your deadline til Monday then. ;)
Even on GrapheneOS, sure it uses a sandboxed Google Play Store, which is obviously great for users, but the developers of Android apps still have to hand over their personal data to Google specifically as this new decree from the Lords of the Google fiefdom entails.
Because FOSS developers rightly value their personal privacy, this decree effectively kills incentive for FOSS developers to continue making and maintaining apps for Android. Running GrapheneOS doesn't circumvent this.
It's like I'm saying "I'm hungry" and you say "Go for a run, it's healthy for you." I mean... it's true that running is healthy... but the act of running doesn't solve the problem of me being hungry...
As I understand it the sandboxed google apps are entirely optional. You can go completely free with GrapheneOS just like with LineageOS.
Too, you can shove Google into its own separate User from everything else and keep it locked down in an always on VPN or the like. You don't owe it the primary user on your phone. You can even keep that user shutdown such that none of it runs until you explicitly switch over and run it.
GrapheneOS is pretty dang impressive.
Depends on your location. There is a timeline table here:
https://developer.android.com/developer-verification/guides
I see September 2026 as a tough date.
Don't wait. GOS just works.
On one phone. The rest of are shit out of luck because we didn't buy the one phone from the company that is causing the problem in the first place.
They're working with an (unrevealed) major OEM to bring a compatible device to market sometime next year.
https://old.reddit.com/r/GrapheneOS/comments/1o32gpg/blackberry_phones/nivsx0k/
Here's hoping its a device with an SD card slot and optionally a 3.5 jack. The Pixel's lack of those is the one reason I haven't made the switch.
Apparently not. But it will later come to other cheaper offerings of the company which will probably have a headphone connector.
This isn't a scalable solution. There aren't enough affordable, used Pixels for everyone in the ecosystem to adopt between now and the Goo-lag.