Post AxXMtuNjcgosYe8V8K by GrapheneOS@grapheneos.social
 (DIR) More posts by GrapheneOS@grapheneos.social
 (DIR) Post #AxXMtg5qkOC8F7f1JQ by thawkade@lethallava.land
       2025-08-25T17:34:53.852Z
       
       0 likes, 0 repeats
       
       @notavi10@critter.cafe So you're out of luck if you have a Samsung or similarly locked/unmoddable ones though :/
       
 (DIR) Post #AxXMthduzD2Z34bk3M by mcc@mastodon.social
       2025-08-25T17:54:05Z
       
       0 likes, 0 repeats
       
       @thawkade @notavi10 also good luck actually running alt androids at this point as the play protect noose tightens. do you want to use an app belonging to a bank? do you want to use a services app published by a government? do you want to purchase a single ebook? even if your device supports these OSes, you're forced into living essentially off the grid
       
 (DIR) Post #AxXMtigR7KeIHAnGcK by GrapheneOS@grapheneos.social
       2025-08-25T18:00:52Z
       
       0 likes, 0 repeats
       
       @mcc @thawkade @notavi10 Status quo is that the vast majority of Android apps work on GrapheneOS. Banking apps are a special case where ~10% or so disallow it.We've been convincing major banks to permit GrapheneOS alongside what the Play Integrity API permits. Several banks began permitting GrapheneOS in the past month including Swissquote. We're actively working towards a universal solution to this in the EU through the EU requiring banking apps to permit competing operating systems.
       
 (DIR) Post #AxXMtjoGvgVjllT2TA by mcc@mastodon.social
       2025-08-25T18:07:11Z
       
       0 likes, 0 repeats
       
       @GrapheneOS @thawkade @notavi10 I find that corporate DRM systems are fragile like hummingbirds. I have purchased a number of Adobe Digital Editions protected books, and I find that these are not even compatible with *the Android version of Adobe Digital Editions*. If the *single* app that can run my purchased ebooks turns out not to work, it is already too late to switch back from LineageOS or whatever I picked.
       
 (DIR) Post #AxXMtkyaaoMFO3InBo by mcc@mastodon.social
       2025-08-25T18:08:29Z
       
       1 likes, 0 repeats
       
       @GrapheneOS @thawkade @notavi10 Although I'm glad you're working with alt OSes, any solution which is specific to GrapheneOS is useless to me because I will never buy a Google phone and (for what I understand to be sound reasons) GrapheneOS is unlikely to run anywhere else in the forseeable future. I am not interested in the security guarantees of a Pixel phone. I am trying to get the right to live as a human without having made those security guarantees. Freedom from Google is the point.
       
 (DIR) Post #AxXMtoKK8SWfmKUgz2 by GrapheneOS@grapheneos.social
       2025-08-25T18:04:17Z
       
       0 likes, 0 repeats
       
       @mcc @thawkade @notavi10The gradually growing adoption of the Play Integrity API by banking apps is a problem but nearly entirely limited to banking and financial apps. Regulation is the only universal solution, but the status quo isn't that bad and we're making decent progress convincing apps to allow GrapheneOS without regulations.There are some government apps doing it but we're making a lot of progress. It goes against other policies by the same governments. They move slowly though.
       
 (DIR) Post #AxXMtuNjcgosYe8V8K by GrapheneOS@grapheneos.social
       2025-08-25T18:05:38Z
       
       0 likes, 0 repeats
       
       @mcc @thawkade @notavi10 Convincing these apps to allow anything is much harder than our focus which is convincing them to permit GrapheneOS in addition to a Google Mobile Services stock OS. We're not trying to convince them to roll back the checks entirely in most cases. We're only trying to convince them to use Android's standard hardware attestation API and permit GrapheneOS with it. Once they're convinced of that, it's easy for them to permit non-GMS hardware and other operating systems.
       
 (DIR) Post #AxXMu0qJbLFKb1YPVw by GrapheneOS@grapheneos.social
       2025-08-25T18:06:47Z
       
       0 likes, 0 repeats
       
       @mcc @thawkade @notavi10 The main barrier we face is getting in contact with the developers or people who can make decisions. Getting past their walls of customer support and handling of external communication is often difficult. In many cases, our users have accomplished it without our involvement through reviews, customer support requests, etc. A growing number of these apps explicitly support GrapheneOS and even test it. It shouldn't be necessary but they insist on doing these checks.