Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GrapheneOS has been ported to Android 17

discuss.grapheneos.org

Post reply on HN
Print view View original

411–420 of 653 posts

Re: GrapheneOS has been ported to Android 17

#411

Post by flawn »

cybertim wrote: post #223
RachelF wrote: post #57

Earlier quoted context omitted.

I too, liked it. However, some apps that I need for work, like Microsoft Authenticator, no longer work under GrapheneOS. https://www.theregister.com/on-prem/2026/03/10/microsoft-tig...

Graphene is NOT a jailbroken/rooted OS, its a real secure unrooted, bootloader locked OS, and MS Authenticotor works just fine. If anything does not work its related to dependency of the App maker on a certain attestation google play services grapheneos.org/articles/attestation-compatibility-guide

This does not play a role - even if you lock your bootloader Play Integrity Checks still fails, and that means you can't use certain apps, MDM and overall restricts your usage. Thank Google for that.

Re: GrapheneOS has been ported to Android 17

#412

Post by gck1 »

Sayrus wrote: post #409
gck1 wrote: post #402

Earlier quoted context omitted.

Oh, then the biggest pain point I've had is now resolved. I should give it another go. I've seen payments being another problem - but Garmin watch handles it for me. And paying with a watch becomes a conversation starter with merchants for some reason.

I'm not sure how Garmin works, but for instance with Google Wallet-compatible watches, you need a phone where wallet can run. I've had this setup for a year where I loaded the cards from another phone and used a watch to pay. However Wallet didn't like this setup. Tokens expired at varying delays, sometimes a day, sometimes a week or payment failed without reasons. Nowadays, I just use my bank's app which work fine o…

You only need a phone to add the card to the watch. After that it works without a phone.

I was actually very surprised Garmin supported the country I'm in. They don't even support the language script, I get squiggles, but payments - better than Google Wallet.

Re: GrapheneOS has been ported to Android 17

#413

Post by pferde »

Gigachad wrote: post #267
dlenski wrote: post #266

Earlier quoted context omitted.

I've just refused to install such things on my phone. You want me to have email and teams/slack on my phone? Sorry, I won't install the spyware. Want to pay for me to have a second phone with it? Okay. No? Well then, I just won't have email on my phone.

Sure if you are in a strong stable position in life you can do that. The average person doesn’t want to rock the boat and cause troubles in their life so they install the invasive mdm profile. It needs to be made illegal imo. The company should provide you a device if you need one for the job.

"I would love to, but I do not have a compatible phone. I cannot afford it."

Re: GrapheneOS has been ported to Android 17

#414

Post by microtonal »

samplifier wrote: post #308
dns_snek wrote: post #283

Earlier quoted context omitted.

> by revoking network you don't lose privacy Be careful, apps can still communicate with other apps, e.g. revoking the network permission doesn't stop apps from fetching and displaying ads over the network. I don't know enough about Android internals to understand the mechanisms behind it, but clearly there are ways for apps to exfiltrate data. > Trying to use Network as a complete data exfiltration toggle isn't the…

Eye opener. Thanks for the warning! GrapheneOS sandboxes all apps including GSF as far as I understand. It would be nice if full capabilities could be exposed or at least shown in the app settings. There is the "All permissions" view which has a "have full network access" item with the following details: `Allows the app to create network sockets and use custom network protocols. The browser and other applications pro…

Every Android app can do IPC with Android apps in the same profile. So an app without Network Access could cooperate with an app with Network Access to communicate with the outside world. Of course, most notably, a lot of apps communicate with Play Services and people generally leave on network access for Play Services to avoid breaking to much stuff.

There has been talk of developing 'IPC scopes', similar to how there are contact scopes.

Re: GrapheneOS has been ported to Android 17

#415

Post by molybd3num »

davidwritesbugs wrote: post #287
LeoPanthera wrote: post #280

Earlier quoted context omitted.

That was a hilariously tone-deaf incident, but it's hardly comparable. Google pushed ads. Apple gave you a free album.

Yes, but a _U2_ album. An ad is 30 seconds of irritation, but a U2 album is like having broken glass sown under your skin.

yeah but you aren't forced to listen to it

Re: GrapheneOS has been ported to Android 17

#416

Post by Semaphor »

kakacik wrote: post #386
goerg wrote: post #265

Earlier quoted context omitted.

There is a list of compatible banking apps: https://privsec.dev/posts/android/banking-applications-compa...

Big list, unfortunately one of my banks is not there (BCGE, Switzerland), most probably meaning I can't even login into ebanking in any other way since they have their properietary authentication app (CrontoSign, also not listed). Its rather small regional/cantonal bank so I get it, even though that region is Geneva, mecca of (some types of) banking. Other banks that I use are there. Almost perfect...

Being missing means they haven’t been tested, not that they don’t work. Generally they probably only don’t work if they require the google play verification thingy

Re: GrapheneOS has been ported to Android 17

#417

Post by master-lincoln »

Scrounger wrote: post #315
OtomotO wrote: post #257

Earlier quoted context omitted.

What about banking Apps? No problem there? Some of them have ridiculous secur... compliance rules.

> What about banking Apps? No problem there? Most banking apps work, but Google Pay/NFC payments won't work.

I know a handful of german banks that have their own nfc payment apps that still work in Graphene

Re: GrapheneOS has been ported to Android 17

#418

Post by mFixman »

jordand wrote: post #12

I've been running GrapheneOS for 7 months now and I'm not going back. When I bought my Pixel 10 last year, I wasn't actually planning on trying Graphene for a while....until I noticed Google had force bundled a 'Wicked For Good' movie promo theme with the latest security update.

What's the status of banking apps, Google / Microsoft authenticator, and Google Wallet? Those were the things preventing me from abandoning stock Android.

Re: GrapheneOS has been ported to Android 17

#419

Post by herrherrmann »

mFixman wrote: post #418
jordand wrote: post #12

I've been running GrapheneOS for 7 months now and I'm not going back. When I bought my Pixel 10 last year, I wasn't actually planning on trying Graphene for a while....until I noticed Google had force bundled a 'Wicked For Good' movie promo theme with the latest security update.

What's the status of banking apps, Google / Microsoft authenticator, and Google Wallet? Those were the things preventing me from abandoning stock Android.

You can check this crowdsourced list for the compatibility of banking apps: https://github.com/PrivSec-dev/privsec.dev/blob/main/content...

Authenticators should work normally, as far as I know (unless Google Authenticator does anything special). Can’t say anything about Google Wallet. There might be more lists/forums where people share which setups are (not) working well for them.

In general, I had these concerns as well until a few months ago. But I am much more optimistic these days that things will just work well out of the box (have read many positive sentiments in blog posts and here on Hacker News).

Re: GrapheneOS has been ported to Android 17

#420

Post by Itoldmyselfso »

veidr wrote: post #186

I have always wondered what this OS looks like. They have an incredibly detailed website with zero screenshots.

It's valid question for people unfamiliar with the project, but it is the AOSP in terms of looks, GrapheneOS does not customize the UI in any way beyond what their own features require as additions. Note that Pixel OS is not AOSP. The default home app of course also influences the experience quite the bit unless you replace it, which is what I'd personally recommend everyone to do as it's so incredibly barebones. Lawnchair is already a big step up as an open source alternative.
Post reply on HN