@Revan_9766@mastodon.social The initial devices with GrapheneOS support should be available in 2027. The initial devices will be flagships so they'll be higher end hardware than Pixels at a higher price. Lower end devices will take more time to meet our requirements since the updates and security features aren't as good. It's mostly due to how Qualcomm handles it. The latest Snapdragon flagships have the best security features. We'll also need Motorola to start paying them for longer updates below flagships.
Google-approved android (these come with Google apps, and most importantly Google services, which are basically what is going to BD doing the blocking for the cause Keep Android Open is concerned about. Google services already has some additional attestation stuff in, which many banks use, which only work if you’ve got a stock google-approved OS)
Non Google approved android (generally based on AOSP which is the actually open source code Google publishes for android, these don’t come with google services so they fail the play store attestation, generally people will be needing microg to use stuff like YouTube, which is basically a light google services replacement)
Graphene OS (it gets its special category because it sandboxes apps so you can use Google services apps in a way that doesn’t give them access to the rest of your system and therefore shouldn’t be able to mess with what you want to install, best of both worlds but it’s not foolproof).
There are a few other projects like /e/ but that’s just AOSP with a coat of paint, graphene is a much more substantial change to how your phone locks down app access.
There are basically 3 types of OSs out there:
There are a few other projects like /e/ but that’s just AOSP with a coat of paint, graphene is a much more substantial change to how your phone locks down app access.
So does microG work good enough to run banking apps? That’s really the big question for most I think.