Purpose of having a fold phone

@ljs am i doin dis right ☕

@lkundrak perfect.

@xbezdick @lkundrak pixel 9 pro fold, not sure about hackability at this point.

Suspect it's pretty custom across the board so I'd doubt lineageos would be good with it.

On security front google promise 7 years of security updates for this, in stock form obv.

I _might_ try to root at some point.

This form factor is so good though

@ljs @xbezdick @lkundrak it's supposed to have full @GrapheneOS support so pretty hackable. No NFC payments though.

@algebraicterror @xbezdick @lkundrak @GrapheneOS oh noice!

@algebraicterror @ljs @xbezdick @lkundrak NFC payments work fine on GrapheneOS. Pixel 9 Pro Fold is a fully supported device and is one of the few Android devices with first class alternate OS support which does not void the warranty or disable important security features.

NFC payments work fine on GrapheneOS. It's certain services which ban using a non-Google-certified OS for payments including Google Pay. There are working tap-to-pay options available in some regions especially the EU.

@GrapheneOS @algebraicterror @xbezdick @lkundrak oh wow that's awesome!

And yeah, if you root the phone, that tends to break such things unless you do naughty workarounds...

I've been on stock android for a while though so not sure how the environment is today.

@ljs @xbezdick @lkundrak @algebraicterror Installing GrapheneOS doesn't involve rooting the device. We only support devices with official first class alternate OS support where we can use all the standard hardware-based security features. It doesn't involve any workarounds and is fully functional. The issue is that certain services either wrongly believe they're improving security through banning every non-Google-certified OS or want to exert control through it. It's hard to get them to stop.

@ljs @xbezdick @lkundrak @algebraicterror We publish a guide on how app developers insisting on checking for a Google certified OS can permit GrapheneOS by using hardware attestation themselves to confirm the device is either running the stock OS or GrapheneOS:

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

Google Pay uses the Play Integrity API to check for a Google certified OS with the device locked and forbids tap-to-pay otherwise. Most EU banks have their own non-Google implementation but US ones usually don't.

@GrapheneOS Right, apologies, czech banks only seem to support Google Pay so I assumed it's similar everywhere else, which is of course laughable.

@ljs @xbezdick @lkundrak @algebraicterror We published a thread about the Play Integrity API here:

https://grapheneos.social/@GrapheneOS/112878067304840664

It's a major antitrust issue where Google is trying to convince app developers to participate in artificially breaking app compatibility in the name of security. It's fake security since it permits an OS with no patches for a decade as long as it was certified by Google in the past. It's a ridiculous system and is really about enforcing their monopolies and control.

@GrapheneOS @ljs @xbezdick @lkundrak @algebraicterror I had missed this thread, and I'm glad you're at least considering taking action for Play Integrity. On payments, I'm afraid banks are in the process of letting GPay/Wallet (which blocks GrapheneOS) become a monopoly on Android as well, since it's already the most accepted option.

@algebraicterror @GrapheneOS I think one bank (Air Bank perhaps?) tried initially, but it was unreliable and people wanted google pay instead.