No, also some banking apps won’t work. Those are easy enough circumvented by just making the bank browser page an icon. They require some strict certification that is basically exclusive to being android even though Graphene is designed to be more secure.
Google pay apparently just requires too much access, so including it would undermine the entire purpose.
I am a massive fan, and the drawbacks are few but very real if you value the things it cannot do. Definitely worth looking into its deficiencies before switching of course.
Its not cos google pay needs to much access its cos google pay needs a special certificate to sign the operating system. The Google android devs love GrapheneOS as they push lots of security patches and bug fixes so they tried to get GrapheneOS signed. Google then ignored GrapheneOS and their own android devs and refuses to sign GrapheneOS. Its purely because google are assholes who don’t want it to work on GrapheneOS.
It amuses me how banks are so anal about the environment their apps run in, but I can open my bank in any browser with god-knows-what plugins installed on whatever OS of my choosing and just because I’m using a browser suddenly it’s totally fine and meets all security requirements.
I’m 100% on linux and FOSS at my home - except for my phone unfortunately because of this reason. I’ve worked in FinTech, I understand why theoretically they won’t want to, but I was hoping some work around had been done. Unfortunately I depend on google pay, so it will have to wait for me.
If you have a smartwatch, does it support contactless payment? I have a Fitbit that does, technically it implements Apple Pay even though Fitbit is owned by Google now. I was able to set it up just fine through the Fitbit app on GrapheneOS (though I don’t think I’ve actually tested it yet).
That’s actually an idea there, I never thought of them as separate devices, more the watch is just a portal to the phone, but that’s a good idea. Keep the watch all googly and the phone graphene may work
No, also some banking apps won’t work. Those are easy enough circumvented by just making the bank browser page an icon. They require some strict certification that is basically exclusive to being android even though Graphene is designed to be more secure.
Google pay apparently just requires too much access, so including it would undermine the entire purpose.
I am a massive fan, and the drawbacks are few but very real if you value the things it cannot do. Definitely worth looking into its deficiencies before switching of course.
Its not cos google pay needs to much access its cos google pay needs a special certificate to sign the operating system. The Google android devs love GrapheneOS as they push lots of security patches and bug fixes so they tried to get GrapheneOS signed. Google then ignored GrapheneOS and their own android devs and refuses to sign GrapheneOS. Its purely because google are assholes who don’t want it to work on GrapheneOS.
It amuses me how banks are so anal about the environment their apps run in, but I can open my bank in any browser with god-knows-what plugins installed on whatever OS of my choosing and just because I’m using a browser suddenly it’s totally fine and meets all security requirements.
I’m 100% on linux and FOSS at my home - except for my phone unfortunately because of this reason. I’ve worked in FinTech, I understand why theoretically they won’t want to, but I was hoping some work around had been done. Unfortunately I depend on google pay, so it will have to wait for me.
If you have a smartwatch, does it support contactless payment? I have a Fitbit that does, technically it implements Apple Pay even though Fitbit is owned by Google now. I was able to set it up just fine through the Fitbit app on GrapheneOS (though I don’t think I’ve actually tested it yet).
That’s actually an idea there, I never thought of them as separate devices, more the watch is just a portal to the phone, but that’s a good idea. Keep the watch all googly and the phone graphene may work
FYI it does work, but be aware youll need (sandboxed) google play services installed on at least one profile of your phone to connect a wearOS device
Good callout, maybe I’ll try it out someday
A narrative the manufacturers push, so not surprising that the thought pattern developed that way.