605
GrapheneOS is finally ready to break free from Pixels, and it may never look back (www.androidauthority.com)
submitted 10 months ago by to c/privacy@lemmy.dbzer0.com
111 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 10 months ago (1 child)

There are definitely some things that do not work with GrapheneOS, though most haven't affected me as I don't use them (like banking apps).

  1. A lot of banking apps don't work, especially from some European banks. I believe there is a fairly well updated list available online.
  2. Android Auto can be made to work, but it's quirky and you have to fiddle with quite a few settings and possibly give up a fair amount of privacy to get some things going (like navigation). I'm still fighting with this.
  3. Many apps will initially not work until you figure out what permissions they actually need and which they can bend on.

I still personally think it is worth it, but I can only speak for myself.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 10 months ago (1 child)

    Banking apps have worked without issues, in my experience.

    The only things I've had issues with, is in-app purchases. Paid apps work, but the in app stuff is hit and miss.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 10 months ago

    Banking apps are highly variable, many work, many don't. I have also heard that there are some required 2FA apps used some some European banks that currently don't work. I don't use any of these, so it hasn't been an issue, but I just wanted to make sure the OP knew to be on the lookout.

  • permalink
  • fedilink
  • source
  • parent