My banking app works fine on GrapheneOS today, but not every banking app does. If it depends on Google Play Integrity with strong integrity it won't because Google has successfully sold the blatant anti-competitive lie that you need to vendor lock-in your users to their OS to get security on mobile.

Secured credentials work fine, everything works fine except stuff that by design is locked in to Google like Google Pay.

And if a bank does this, tell them that they can do remote attestation for GrapheneOS phones as well:

https://grapheneos.org/articles/attestation-compatibility-gu...

tell them how? the clerk in my local branch won't be able to do anything with that information.

E-mail their support or technical department? I had some questions to my bank with regards to degoogled Android support and they just answered. Some banks have also fixed GrapheneOS support after customers asked.

> Will the sandboxed google play permit banking apps to work using TPM and secured credentials?

Apps that don't work don't fail due to technical reasons but because upstream says so, i.e. Google Wallet. My banking app works just fine.

> I would expect whatever you initialised before grapheneOS is wiped before you can run the alternate OS.

Yes.

> Is termux possible with a root/sudo function?

GOS doesn't support root by itself since they deem it a security risk, but it's possible.

I don't think GrapheneOS team would partner with a vendor unless their security/usability standards were met (considering how long it took since the initial announcement) so I'm expecting feature parity with Pixel variants.

I'm just really curious if this phone is going to pass Google's conformance tests and whatnot. I feel like some of that is incompatible with GrapheneOS's security model, so I wonder what's going to happen there.

I think most banking apps already do work on GrapheneOS (not sure about TPM/secured credentials though). Graphene IIRC keeps a compatibility list somewhere. Some don't work, of course, but more do than I would have expected.

For me, the big question is if Google Wallet & its NFC payments will work. They don't on GrapheneOS currently, but if Motorola plans for this to be a fully Google-certified phone with GApps and everything, it will have to, somehow.

MyGov is my governments portal. (I'm australian) I'd have to maintain another path to do tax, Medicare, related functions. This is an embuggerance.

You can keep your old phone around for it but they should solve the problem. Motorola can likely help us with getting it resolved once things are further along.

And its only getting worse. The extreme push for myID everything, is really not helping the ecosystem of things.

And on top of attestation, good luck if you've ever changed your legal name, in getting myID to behave at all.

> Graphene IIRC keeps a compatibility list somewhere.

This is the community-maintained banking app compatibility list: https://privsec.dev/posts/android/banking-applications-compa...

No, grapheneOS fails both DEVICE_INTEGRITY and STRONG_INTEGRITY checks.

By default. It can be mitigated.