this post was submitted on 18 Sep 2024
205 points (93.6% liked)

Privacy

31993 readers
507 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

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ByteWelder@lemmy.ml 5 points 1 month ago* (last edited 1 month ago) (5 children)

More specifically, Play Integrity API will fail on the Play Service integrity check. If I recall correctly, this is why Google Pay won’t work on GrapheneOS.

Some banks require the app to be used as second factor to log into their website.

[–] tehmics@lemmy.world 1 points 1 month ago* (last edited 1 month ago) (4 children)

Can you work around it with magisk like rooted stock android? I bought my pixel specifically for graphene but google pay is the main thing preventing me from switching

[–] Githyanki@lemmings.world 1 points 1 month ago (2 children)

You cannot root grapheneos, so the answer is no. That method does work on other rom's like lineage.

[–] ByteWelder@lemmy.ml 1 points 1 month ago* (last edited 1 month ago) (1 children)

Last time I checked, it was broken for years already. It’s been a while though. edit: Confirmed: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ Only basic/device attestation is working.

[–] tehmics@lemmy.world 1 points 1 month ago

I'm currently getting MEETS_DEVICE_INTREGRITY with play integrity fix, which is enough for Google Pay to work. The only thing that I haven't been able to do is drive for Uber or use RCS oddly enough. RCS happened to fix itself about a month ago as well.

load more comments (1 replies)
load more comments (1 replies)