zlacker

>>moelf+(OP)
I love GrapheneOS. The biggest downside is that Google integrity API block wireless payments in Google Pay. All Dutch banks now advertise to install Google pay for wireless payments. I've tried asking Google to support GrapheneOS but they told me to do a feature request. Which I did and got no reply to. I've contacted the consumer market authority and made a formal complaint since Google and Apple share effectively a contactless payments duopoly and decide which OS distributions get access. Those are closed source and usually bundled with a lot of spyware. I also explained how the Google integrity API might affect banking availability in the future (and already does for some banking apps). They took it very seriously and I hope to hear from them in the future.

>>verslu+1B
Thanks for doing that. I tried GrapheneOS a few years ago in the states, and the bank thing wasn’t a huge problem (just carry rfid cards because there’s no google pay/apple pay).

The bigger problem came from apps that threw null point exceptions on startup when probing for google play crap.

The following failed for at least one week over a two month period: parkmobile, multiple ev charging networks, uber, lyft, yelp.

Is this still an issue, or are things more reliable these days? (Ignoring the Google integrity stuff.)

I noticed that GrapheneOS got more than 2x Google’s advertised battery life until I installed Google Play Services in a sandbox. Then it dropped to advertised. You might want to add that to your complaint. Halving everyone’s battery life is easily quantified economic damage. (Privacy is more important than bundling $50 of battery, then wasting it, but easier for Google to wave away with big words and doublespeak.)

>>hedora+f41
The app crashes I found were always due to the additional security hardening features in GrapheneOS. You can toggle these individually for each app.