187
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 07 Jul 2026
187 points (99.5% liked)
Android
34331 readers
445 users here now
DROID DOES
Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
founded 3 years ago
MODERATORS
This is not accurate. They updated the app to actively block GrapheneOS and other third-party Android builds.
The distinction is critical; unsupported combinations often work.
They updated the app to use the Play Integrity API, which GOS does not meet.
Not that it means anything, of course. GOS is far more secure than Google's laughable excuse of a certification.
They updated the app to use the "Play Integrity[sic] API," which actively blocks GOS.
"Does not meet" implies there is something reasonable GOS could do to "fix" it, which untrue and misleading. The malice on Google's and Volkswagen's part is an important part of the story.
Requiring a valid Play Integrity API response is a blanket enforcement on all custom ROMs, regardless of security measures.
This was not a targeted attack on Graphene. GOS users just tend to be more vocal and....paranoid.
"Does not meet" has more than one meaning. Don't play dumb.
I didn't say the attack was "targeted" only on GOS; you made that up yourself. But it is an attack, as opposed to something with a valid excuse.
Also: it's only paranoia if they aren't actually out to get you.
Big companies have been trying to lock out custom ROMs for years, it's a giant cat and mouse game. The integrity bullshit thing is just another move. And the fascists in charge have been stripping regulations which is allowing these companies to make such bold moves.
I think we're on the same page here. I apologize for coming off so harsh.
That is until the official Motorola partnership happens with GoS and Motorola. It's the missing piece for integrity verification as of current listed requirements on Google's documentation. They needed to have first class support from a major OEM. Looking forward to seeing how Google will change that maliciously. This includes attestation.
The pessimist in me thinks the GrapheneOS Motorola partnership won't happen, Google will put pressure on Motorola and make it fail. I really hope I'm wrong though.
Good point, I didn't think about that. It will be very interesting to see what happens.
Interesting indeed. I know I'll be buying one pretty much no matter what as long as reasonably priced.