this post was submitted on 24 May 2025
115 points (94.6% liked)

Privacy

38001 readers
331 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

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

My current phone is 7 years old, does not support recent android versions, and battery life is becoming atrocious. This feels like right time to change my phone.

Currently, I know of & am considering 3 options:

  • Google Pixel
  • iPhone
  • Samsung Galaxy

I heard that Pixel is the best choice for privacy, despite it being Google^TM. Should I go with it, and install Graphene OS or similar options? The very fact that the name "Google" is attached makes me nervous. Also, I don't think I can trust android, so I would have to install Graphene OS or the like. In the case, app support would be lacking, though.

I am considering iPhone as well, since it has "reputation" of being secure. Of course, Apple can access my data, but that might be a good enough compromise? Honestly, I don't know. It's the best supported option as well - lots of apps support iPhone.

Galaxy is just the one that I am the most familiar with (my current one is Galaxy S8). I don't trust it, though. Do they even make good hardware nowadays?

EDIT: Turns out, Pixel phones are poorly supported by local telecomm companies. It is relatively cheap though. Still worth it?

EDIT2: I heard that data & message is fine, but the call quality is impacted by lack of VoLTE compatibility.

you are viewing a single comment's thread
view the rest of the comments
[–] thatonecoder@lemmy.ca 25 points 1 day ago (4 children)

Just to let you know, GrapheneOS uses AOSP (the base Android system) and sandboxed Google Play Services, making it compatible with 90% of all Android applications. From what I've heard (don't take my word for it), the apps that have the least compatibility / more breakage are banking ones.

[–] Dreaming_Novaling@lemmy.zip 5 points 1 day ago

The banking app thing is unfortunate, but then I kinda realized that I don't really need them anyway. I have all the features I need in browser, and text notifications set up for when I spend money.

The wallet not working REALLY sucks, but if I look on the bright side that's one less thing Google knows about me and my spending.

[–] Ulrich@feddit.org 7 points 1 day ago (1 children)

It does not "use" AOSP, it's built on AOSP, like every Android device.

AOSP is like the foundation of any Android OS.

[–] thatonecoder@lemmy.ca 8 points 1 day ago

Yes, that was a poor choice of words on my part; I do apologize about that.

[–] Brujones@lemmy.world 9 points 1 day ago (1 children)

While this tends to be true, the vast majority of the banking app incompatibilities are overcome with a simple app-specific toggle.

[–] whostosay@lemmy.world 7 points 1 day ago (2 children)

Which toggle is that and does it work with cash app?

[–] corn@reddthat.com 3 points 1 day ago (2 children)

The other answers are correct but I have not gotten cashapp to work. I use an old phone connected to my current phone via hotspot on the rare occasion I need cashapp.

I still recommend GrapheneOS regardless, almost everything else works with nothing more than minor tweaks. If you want something that "just works", you'll run into some hangups. Privacy unfortunately has a cost.

[–] whostosay@lemmy.world 3 points 1 day ago

Yeah I've been using graphene for about a year without many issues, cash app is the only one I still can't get working.

[–] whostosay@lemmy.world 2 points 1 day ago (1 children)

Dude the exploit protection compatibility mode worked. I'm logged in

[–] Brujones@lemmy.world 1 points 1 day ago
[–] Brujones@lemmy.world 10 points 1 day ago (2 children)

Exploit Protection Compatibility Mode. It's a setting that relaxes this particular security enhancement for a given app.

It's worth knowing that NFC payments do not work with Graphene currently.

[–] whostosay@lemmy.world 2 points 1 day ago

Oh shit, this is working.

[–] idefix@sh.itjust.works 5 points 1 day ago (1 children)

Oh I didn't know NFC payments were not working. No workaround?

[–] Brujones@lemmy.world 6 points 1 day ago (1 children)

Not currently. It will require Google to'allow' tap-to-pay on Graphene. Other NFC functions work fine.

For my use, it's not a big deal. Tapping my card is easy enough

[–] idefix@sh.itjust.works 2 points 1 day ago (1 children)

Thanks for the explanation. Unfortunately this is a major feature for me. I just don't carry cards anymore

[–] Brujones@lemmy.world 4 points 1 day ago

That's fair. Privacy and security generally come at some cost of convenience. Everyone has their own personal balance.

[–] someacnt@sh.itjust.works 4 points 1 day ago

Yeah, the problem is with the one banking app I frequent.