How long for Updates?

Psyonico

Hi,

I'm thinking of switching to GrapheneOS, but I would need to buy a new phone to do so. I'm trying to decide if I should go with one of the Pixel 9s or if I should wait for the Pixel 10 which should be out next month. My question is: how long does GrapheneOS usually take to support the newest phone? I know things can change, but if support will be available shortly after release of the phone, it might be worth it, or I may just decide to buy the Pixel 9 now instead.

Any thoughts would be appreciated.

DeletedUser370

Psyonico I'm trying to decide if I should go with one of the Pixel 9s or if I should wait for the Pixel 10 which should be out next month. My question is: how long does GrapheneOS usually take to support the newest phone?

The GrapheneOS project have stated that the Pixel 10 will be supported if it meets their security requirements, but that it will take significantly longer to add initial support for it than for devices in the past, due to Google having stopped releasing the device tree code for Pixel devices.

From the GrapheneOS account in the community chat rooms: https://discord.com/channels/1176414688112820234/1176434710499557486/1392882250538024990 :

we can likely support the Pixel 10 but they've made it a lot harder to make initial support for it, more similar to a non-Pixel device
we can still do it
it's not going to be 24 hours from device launch as usual, that's for sure
[…]
Pixels will be harder to support now, more similar to non-Pixels, but at least they still have the latest OS release
[…]
if they don't support installing another OS or don't provide support for locking it and using those security features as the current ones do, then sure, we couldn't support it
we can still support the existing ones until end-of-life
[…]
it will make it take significantly longer to add support [for the Pixel 10] and then it should be about the same as it was before for updates

If you are considering a Pixel 10, then I think it makes sense to wait for it to be released and for GrapheneOS to add support for it before you buy one.

soul-adrift

Here's one approach you could take - or at least the approach I would recommend to my younger self starting over:

The Pixel 10's Tensor G5 chip will be manufactured by TSMC and is expected to give the phone better battery/power characteristics. So might be best to wait and see if this unfolds as expected, if not you'll be able to buy the 9/9a at nicer discounts either way.

In the interim, I would recommend you buy a very cheap used Pixel 5 or later as soon as possible whilst you wait for the Pixel 10 release.

It took me quite a time (2-3 months) to really understand how I wanted to use GrapheneOS and structure the apps, google playservices and VPNs across profiles. It is quite nice to have the luxury of experimenting with all this on a phone that is not both very expensive and your daily carry.

Hook the cheap Pixel up through just wifi and work your way through all the documentation on the website. In particular, you want to get yourself familiar with profiles; installing/updating apps from Google Playstore in one profile but using them in other profiles; and configuring your profiles & apps for best battery life.

After note: after a quick delve into ebay, depending on the country you live, used Pixels for experimenting with may not be as cheap as I was expecting when I wrote the above. So I accept my comments might not be that helpful afterall.

vlad

soul-adrift very cheap used Pixel 5

no longer supported. minimal currently supported device is pixel 6 series (and would remain so for like a one year more or slightly less).

Psyonico

You make a valid point about the Pixel 9 likely going on sale when the Pixel 10 launches. I think I was just looking at a prime day deal (save a whopping $50) and thinking about how my trade in might be valued slightly less in two month's time.

I actually have used GrapheneOS in the past, but I didn't make my way through the documentation and ended up having a really bad time with it. I now know about using the google play services in the sandbox to allow for things like notifications to work. I suppose I should look more into it while I wait for the 10 (or 9 to go on sale)

DeletedUser370

Psyonico I actually have used GrapheneOS in the past, but I didn't make my way through the documentation and ended up having a really bad time with it. I now know about using the google play services in the sandbox to allow for things like notifications to work.

In general, I'm observing that many users who say that they've found GrapheneOS difficult to use ended up having tried to use their migration to GrapheneOS to immediately start on a journey of completely "deGoogling" or immediately moving away from apps they used on their previous phone which they found convenient but also privacy-invasive. If you want to move to different apps or services it makes sense to do so gradually in order to avoid "privacy fatigue". I'd say just install Sandboxed Google Play and start from there.

Edit: You do not want to go with an end-of-life device. Not only do they lack security patches, but they also don't have the latest GrapheneOS features and are running older Android versions. You won't have a good experience with those.

Psyonico

DeletedUser370 In general, I'm observing that many users who say that they've found GrapheneOS difficult to use ended up having tried to use their migration to GrapheneOS to immediately start on a journey of completely "deGoogling" or immediately moving away from apps they used on their previous phone which they found convenient but also privacy-invasive.

I really had 2 main problems on my last try.

The first was that I didn’t understand the google play sandboxing thing and so most of my apps just didn’t work quite right, usually notification issues, but there were a few other minor things as well.

The second was that I am hard-of-hearing and I couldn’t get text-to-speech for maps apps to be loud enough for me to hear for directions while driving, even pumping directly into my hearing aids.

The first thing I know was user error, the second, I’m not sure about.

I actually have (mostly) de-googled still. I’m running an iPhone with no google apps on it, have switched to alternative browsers and search engines, etc. really, it’s only when I need to watch the occasional YouTube video that I touch google, because I haven’t found a de-googled app for iOS for YouTube, so I use their mobile site (not signed in).

I would like to swap back to GOS because I know that while iPhones are miles ahead of standard android, they still have privacy issues.

matchboxbananasynergy

In the past, we've supported new device in 1-2 days. This will not be the case for the Pixel 10. We're confident we can support it, but due to the changes Google made, we cannot provide an ETA.

It would be best for people looking to buy a Pixel 10 wait for us to officially support it before purchasing one.

The Pixel 9 series are still great, and I'm heavily considering getting a Pixel 9 Pro myself once the 10th gen devices come out, presumably at a discount.

DeletedUser370

Psyonico The second was that I am hard-of-hearing and I couldn’t get text-to-speech for maps apps to be loud enough for me to hear for directions while driving, even pumping directly into my hearing aids.

I can see how this would be a deal breaker for you. It is possible to create a new thread to ask users to assist you with troubleshooting the issue. It is also possible that this is an issue that has been corrected with Android 16. Or perhaps not. But those two things of course require that you have a device with GrapheneOS currently installed, which of course might not be convenient for you.