Post by @GrapheneOS@grapheneos.social
Received my @jolla phone today. After first excitment about the build quality of the device the frustration started... 🧵
@jolla in the packaging there is a cardboard cover on top of the phone, that talk about privacy and this is your phone.
However, when you first boot, it immediately asks you to create a Jolla account to get access to the Jolla app store, which apparently is required to get Sailfish OS updates.
Why do I need to create an account in order to get OS updates?!
@jolla okay, let's ignore that for now. This means I can't use the build in app store. How do I install apps? Apperently there's something called OpenRepo. Okay, lets go there. Can I install apps now? No, you first need to install Storeman.
@jolla so I try to install storeman, which indicates it was successful, but the app icon never shows up anywhere. So I can't open the store. How to debug this? Use the file browser to open the install log. To bad that I don't seem to have a file browser and I can't install one.
Very disappointing first use experience. I wanted a phone that feels more like Linux. Instead I get the same app store BS again that drove me away from Apple and to some extend GrapheneOS.
@jolla but if I end up installing android apps through the android app support, I might as well upgrade to a Pixel 10 and continue using @GrapheneOS...
@jolla @GrapheneOS nice! After enabling Developer Mode I can now use the build in terminal to cat the storeman install log. Apparently a linking error!
nothing provides 'libsailfishsecrets.so.0()(64bit)'
I stand corrected. This absolutely is a #linux experience... 😐
@jolla @GrapheneOS tried to pkcon refresh but it just hangs at 10% an never completes. Yeah, I think I'm going to return this.
@britter @jolla @GrapheneOS What a disappointment. 🫤 Sounds like nobody ever tested the "no account" path?
@OmegaPolice @britter @jolla @GrapheneOS graphene don't ask any account but you need 2 or 3 appstore (fdroid, aurora store (playstore)).
The only downside is the lack of "official" (from bank as graphene often fix their crappy security control so the app load) support for bank, state
I hope Motorola to lobby hard for graphene support in the EU level
@maya @OmegaPolice @britter Most banking apps work on GrapheneOS but many have memory corruption bugs and incorrect anti-tampering code requiring our per-app exploit protection compatibility mode toggle.
Around 10% of banking apps are unavailable due to banning using a non-Google-approved OS. Around a dozen banking apps began specifically permitting GrapheneOS in addition to a Google-approved OS which is growing.
There's a good list based on ongoing user reports:
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
@GrapheneOS @maya @OmegaPolice @britter Notably, most work with the limitation of disallowing NFC payment. Which is just as ridiculous but oh well, I can live w/o that.
@ljrk @maya @OmegaPolice @britter In Europe, there are multiple tap-to-pay options compatible with GrapheneOS. Curve Pay, PayPal and many European banking apps permit tap-to-pay. Google Pay bans using GrapheneOS and most banks around the work delegate this to Google Pay. There was a trend towards doing it in Europe and many apps migrated to it which ended support for tap-to-pay on GrapheneOS. The trend has largely stopped.
Google Pay has a monopoly outside of Europe which is the main problem.
@GrapheneOS@grapheneos.social @ljrk@todon.eu @maya@gs.lexinova.eu @OmegaPolice@hachyderm.io @britter@chaos.social And without GMS? I think Curve Pay uses GMS.
@GrapheneOS @ljrk @OmegaPolice @britter from what i remember curve pay is not very good privacy wise
@maya @ljrk @OmegaPolice @britter Banks and neobanks both have terrible privacy. The private options are cash, Monero and similar options. Many businesses are phasing out support for cash and many governments are placing stricter limitations on it.