Mozilla has added support for Google's Play Integrity API, known for blocking users of custom ROMs from accessing banking apps, to Firefox for Android.
Yes, those are all reasons why Google is a despicable company and how GrapheneOS is going to be more difficult to use with some apps (most likely banking or other more restrictive apps), will be subject to late official Android patching schedules, and how 3rd party apps will not be as usable on official devices, but that doesn’t mean GrapheneOS is just dead because Google is trying to kill all custom ROM support.
The Google Play services are already an issue for most ROMs and will be worsened after this, but many apps have releases within F-droid, Accrescent, or directly hosted via github. I don’t see how having that will change after this new requirement is in effect. A lot of GOS users already use free versions of apps anyways, that likely won’t be affected by this change at all as I understand it. Official app support from Google hosted APKs will be impacted. Most of these apps have workarounds like free open source alternatives or just using the website instead of an app. But some apps won’t and that might be a dealbreaker for some people.
From how I understand it, this is a splintering between free software and proprietary software but not a death knell.
Because every single third party app won’t work without the attestation keys, including the ones you listed. GrapheneOS won’t be able to push updates IF they won’t pay Google’s fees.
Google has never said they plan to remove bootloader unlocking as part of this change. If they do that will merely kill of pixels as a device choice. The graphene devs have been looking elsewhere for options for a while now, I’m not that worried
I use my rooted, untrusted Chinese Xiaomi spy phone just like an untrusted device…
Next time, I’ll look into open-source hardware and Linux as the operating system.
I dont give a s… about custom roms which are still based on android because Android and closed Hardware (qualcomm etc (Whether it’s grapheneOS… Lineage, or whatever… No one can do anything with the firmware regarding modems, etc… No one can say what undocumented command sets are available, etc. )) is cancer
The only truly viable alternative that used Android was Project Ara… which is why Google bought up the patents and shut the project down. Everything else is just a smokescreen.
Guess it’s nice I run graphene and can just block that, man that sucks though. I’m tired of Mozilla being only slightly better than the competition
graphene is ending this September
Yes, those are all reasons why Google is a despicable company and how GrapheneOS is going to be more difficult to use with some apps (most likely banking or other more restrictive apps), will be subject to late official Android patching schedules, and how 3rd party apps will not be as usable on official devices, but that doesn’t mean GrapheneOS is just dead because Google is trying to kill all custom ROM support.
The Google Play services are already an issue for most ROMs and will be worsened after this, but many apps have releases within F-droid, Accrescent, or directly hosted via github. I don’t see how having that will change after this new requirement is in effect. A lot of GOS users already use free versions of apps anyways, that likely won’t be affected by this change at all as I understand it. Official app support from Google hosted APKs will be impacted. Most of these apps have workarounds like free open source alternatives or just using the website instead of an app. But some apps won’t and that might be a dealbreaker for some people.
From how I understand it, this is a splintering between free software and proprietary software but not a death knell.
Because every single third party app won’t work without the attestation keys, including the ones you listed. GrapheneOS won’t be able to push updates IF they won’t pay Google’s fees.
This doesn’t apply to GrapheneOS.
Is this supposed to be ignorance?
this is a completely different issue not in any way related to what you first linked to?
it is.
This doesn’t impact graphene at all
refresh ↑
GrapheneOS will have to start accepting using microg in place of the Play Services.
I doubt it, I see no reason they couldn’t continue using sandboxed services as they do now
microg won’t work without Google’s bootloader locks🔐
Google has never said they plan to remove bootloader unlocking as part of this change. If they do that will merely kill of pixels as a device choice. The graphene devs have been looking elsewhere for options for a while now, I’m not that worried
Ah, the Motorola venture…
These days, you see grapheneOS users whining every day. It’s so funny (Because they continue to swear to grapheneOS every day… ).
Graphene is a meme OS. Just use Lineage, it works on more devices.
I use my rooted, untrusted Chinese Xiaomi spy phone just like an untrusted device… Next time, I’ll look into open-source hardware and Linux as the operating system. I dont give a s… about custom roms which are still based on android because Android and closed Hardware (qualcomm etc (Whether it’s grapheneOS… Lineage, or whatever… No one can do anything with the firmware regarding modems, etc… No one can say what undocumented command sets are available, etc. )) is cancer
The only truly viable alternative that used Android was Project Ara… which is why Google bought up the patents and shut the project down. Everything else is just a smokescreen.