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.

  • thatonecoder@lemmy.ca
    22·
    1 day ago

    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.

    • Novaling@lemmy.zipEnglish
      2·
      19 hours 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.orgEnglish
      71·
      1 day ago

      It does not “use” AOSP, it’s built on AOSP, like every Android device.

      AOSP is like the foundation of any Android OS.

    • Brujones@lemmy.world
      9·
      1 day ago

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

        • corn@reddthat.comEnglish
          2·
          18 hours ago

          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.

        • Brujones@lemmy.world
          9·
          1 day ago

          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.

            • Brujones@lemmy.world
              5·
              20 hours ago

              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·
                19 hours ago

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

                • Brujones@lemmy.world
                  4·
                  19 hours ago

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