GrapheneOSWe're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support.
https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/
@springonion
- 68 Followers
- 0 Following
- 104 Posts
Good news for the #GrapheneOS folks whose banking apps have not been playing along nicely in recent times, with release 2026012800 SMS codes are now detected again and secure app spawning will no longer be picked up by wrong anti-tampering checks.
https://grapheneos.org/releases#2026012800
Remember to contribute to the list!
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
akc3nPlease consider nominating the @GrapheneOS project for this year's @protonprivacy fundraiser https://proton.me/blog/lifetime-fundraiser-survey-2025
> Since 2018, the Proton community has helped raise more than $4 million in direct grants to over 40 organizations defending privacy, free speech, and human rights.
Donations are what fund our work on upcoming features & improvements, maintaining our current ones, & the upkeep of our infrastructure.
More info:
https://discuss.grapheneos.org/d/28065
@thomholwerda At the same time we also have access to them thanks to the OEM we are working together with. However, the embargo means one can not publish the source code until it's pushed to AOSP. Nothing stops you from sharing the binary release though...which is what we've done in our latest release, opt-in for interested users. See here for more info:
@thomholwerda Android is also moving from monthly security updates to quarterly, which is awkward due to multiple reasons. For one, OEMs now get multiple months of early access to these patches, which substantially raises the chance for malicious actors to get their hands on them and cause harm that way.
@thomholwerda As for the changes Google has introduced, it has certainly been a change of pace. We had to backport the security related updates to Android 15 QPR2 while we were working on Android 16 following the removal of device specific code. That came unexpected however we have since updated our tools to accommodate for this.
@thomholwerda Hey, part of the GrapheneOS team here. We've seen your post on osnews.
Security is a cornerstone of our philosophy for sure, but I like to believe convenience and usability isn't left behind. Many of our features are tailored to sane defaults for a smooth experience, but can be tweaked up a notch if you prefer!
Swissquote has launched official support for GrapheneOS for their main app instead of it only being available for Yuh:
https://play.google.com/store/apps/details?id=com.swissquote.android
> What’s new
> - We now officially support GrapheneOS!
> - Bug fixes and minor improvements
They're verifying GrapheneOS via hardware attestation.
@rasmusjp Yeah I just created the account to join in on this topic. Would you mind linking me the post(s) in which you believe we're attacking them? Because right now we're portrayed as if we're deliberately excluding a part of the community from using GrapheneOS (among other things), and I like to believe it's reasonable for us to defend ourselves from these accusations and explain what's going on.
@rasmusjp We're not the ones acting hostile. Look at the blog post, the author is depicting us as the devil himself. We're debunking its many falsehoods, that's all.