Earlier quoted context omitted.
Yes, you install the Google Play store via the GrapheneOS App Store. The OS comes with like 5 apps out of the box. The rest is up to you. Biggest caveats that I've encountered: tap to pay via Google Wallet is a no go, Android Auto can be flaky, MDM managed work profiles don't work at the moment, and some apps that use the Google Play integrity API fail to validate and refuse to work (I've only encountered one app tha…
Tap to pay is mostly NFC? So is there an alternative app?
GrapheneOS has been ported to Android 17
371–380 of 653 posts
Re: GrapheneOS has been ported to Android 17
#372Earlier quoted context omitted.
This is a thing now https://volla.online/en/operating-systems/volla-os/
I don't see anything they offer for security that's not also in AOSP/LineageOS/eOS/stock/etc. Which is not to say that's not enough for most people, but why highlight them? It doesn't seem comparable to the laser-focus GrapheneOS has on security
Re: GrapheneOS has been ported to Android 17
#373I've been running GrapheneOS for over an year now. Bought a Pixel 6a last year as a cheap way to test waters, but pretty soon I upgraded to discounted Pixel 9. It took a while to set the basics (coming from iPhone), and I'm still have a couple of stuff missing, but at this point don't intend to use anything else (for as long as possible). The biggest hurdles for me were - should I use separate profiles and how to get…
Re: GrapheneOS has been ported to Android 17
#374I was using GrapheneOS for years, until the battery died while I was on an important call, trying to get someplace. Plugged it in, but little did I remember that I had installed OS update that was pending app optimization phase that happens during next boot. GrapheneOS has some hardening in this phase, which as I understand, essentially has to rebuild all apps without cache. And as I have a ton of apps, I was parked…
Sounds reasonable. People tend to install way too many apps on their phones and than blame the phone about short battery life or too many notifications.
Re: GrapheneOS has been ported to Android 17
#375Earlier quoted context omitted.
Presumably any new Android 17 features that aren't counter to GrapheneOS's mission, such as "Bubbles allows you to turn any app into a compact, floating window" https://blog.google/products-and-platforms/platforms/android...
Does GrapheneOS run on tablets? I don't see a whole chat app (shown in the example) fitting on my phone screen alongside something like a web browser, and the screenshot is from a square screen
Re: GrapheneOS has been ported to Android 17
#376So I still need to buy a Google phone to get it? No thank you.
Everything else is meh, bad, or atrocious.
Next year we'll have Motorola flagship(s) to choose from. Can't wait.
Re: GrapheneOS has been ported to Android 17
#377Earlier quoted context omitted.
Only Google Pixel’s and Fairphone’s currently provide bare minimum for 3rd-party OS support: working verified boot with user-provided signing keys. None of the other phones doing that yet Fairphone cant be supported because it does not keep up with Android updates and in particular Linux kernel updates. Currently supported Fairphone’s have EOL (outdated, not supported) Linux kernel version. They are bad in terms of o…
There are a lot of devices with the ability to install another OS and lock the device with verified boot, but none with the required updates and security features other than Pixels. Fairphones are near the bottom for security among the available options. It's not one of the main issues with their devices but Fairphone has had a lot of issues with verified boot including using publicly available sample private keys fo…
Re: GrapheneOS has been ported to Android 17
#378Earlier quoted context omitted.
To get a sense of the project and its goals I recommend reading this post[1]. Buying a used Pixel is economical, environmental, and likely doesn't support Google. Pixels are the only secure and open android devices that could work for the project and meet the extensive requirements[2]. This is because GrapheneOS takes real steps to protect user privacy and security, not features that degrade security and don't increa…
[flagged]
Motorola announced it on 2nd of March 2026.
Re: GrapheneOS has been ported to Android 17
#379I'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.
Any issues with banking insurance or healthcare applications?
The vast vast majority of apps (99%+) are compatible and those that are broken is due to bugs in the apps which GOS catches, but these exploit protections can be disabled, and apps that use the monopolistic play integrity api.
The only apps that are permanently broken are those using the strongest play integrity api which is security theatre.
Here's a community created list of banking applications and their current status on GOS.
https://privsec.dev/posts/android/banking-applications-compa...
Re: GrapheneOS has been ported to Android 17
#380Earlier quoted context omitted.
To get a sense of the project and its goals I recommend reading this post[1]. Buying a used Pixel is economical, environmental, and likely doesn't support Google. Pixels are the only secure and open android devices that could work for the project and meet the extensive requirements[2]. This is because GrapheneOS takes real steps to protect user privacy and security, not features that degrade security and don't increa…
> Buying a used Pixel is economical, environmental, and likely doesn't support Google Interesting. What do you think are reasons for google to run Pixel then? Not being sarcastic here, but what links you shared (thank you) say imply there are almost no benefits for Google to run Pixels and as we all know, Google is not a company doing charities.