Pixel 10 - Experimental support for GrapheneOS is now available!

carmelo42

Dannyjelll At SFR, here in France. Without subscription and unlocked.

Eirikr70

carmelo42 OEM unlocked or just ISP unlocked ?

FredoFr

carmelo42 same for me, my 7 was dying... Sfr offert me better price for the 10pro than for the 9 pro, because they didn't have anymore the 9 pro in stock.

carmelo42

Eirikr70 both (I have activated the toggle "unlock OEM")

Eudyptula

I'm worried about the future of Pixel phones. Personally I see Pixel 11 series as my new upgrade path, but I'm worried it won't support GrapheneOS (at which point I'm not buying a Pixel).

I'm also worried we may come to a point where the government passes a law which says devices cannot run alternate operating systems. Which happened briefly for network equipment.

It's quite worrying. And seeing as Chromium and Chrome might be bought by an AI company now because of the government trying to do something good, how much can we actually trust their competence? What they actually should've done was to block things like removing JPEG XL code because AVIF couldn't compete against the better standard. Anti-competition actions like that. As well as mandate it's openness. Google is now in control of not only the only public space but which companies can win through. And when the government steps in because of monopoly status, we risk something way worse?! Will it even stay open source in the future?!

The same can be said about Android. It should be mandated to stay open source and give everyone a levelled playing field. if Android becomes (more) proprietary and bootloaders are sealed shut, we all out of luck.

akc3n

Eudyptula but Google is not required to sell Chrome or Android? Am I missing something or are you not aware of last week's ruling by a US judge?

23Sha-ger

Eudyptula I'm also worried we may come to a point where the government passes a law which says devices cannot run alternate operating systems.

Governments don't give s**t what you run on your device. If that will ever happen, it will be solely
Google's decision or any other OEM for that matter. iOS devices cannot run custom OS because Apple wanted
it to be this way.

Murcielago

Eudyptula

I'm worried about the future of Pixel phones. Personally I see Pixel 11 series as my new upgrade path, but I'm worried it won't support GrapheneOS (at which point I'm not buying a Pixel).

If you don't want to change your device until next year (that's my guess cause you're referring to the Pixel 11), you have plenty of time to see how things evolve.

Either the Pixel 11 will be supported, or you can buy a Pixel 10 (which will be supported in the future), or you can get a Pixel 9 Pro, which will be supported for many years to come.

By the time these devices reach the end of their life, there may also already be another device option available: GrapheneOS seems to be working with a major Android OEM towards future devices officially supporting GrapheneOS.

It's quite worrying. And seeing as Chromium and Chrome might be bought by an AI company now because of the government trying to do something good, how much can we actually trust their competence

Just to add in what akc3n already stated:

Google not required to sell Chrome or Android, judge rules in win for tech giant

The same can be said about Android. It should be mandated to stay open source and give everyone a levelled playing field. if Android becomes (more) proprietary and bootloaders are sealed shut, we all out of luck.

Do you have any information about Android is going to become closed source? To my knowledge:

Google confirmed to Android Authority that it is committed to publishing Android’s source code, so this change doesn’t mean that Android is becoming closed-source. The company will continue to publish the source code for new Android releases, so when Google releases Android 16 later this year, we’ll get the source code for the update. In addition, Google will continue to publish the source code for Android’s Linux kernel fork, as it is licensed under GPLv2, which mandates source code releases, and is separate from AOSP.

source: https://www.androidauthority.com/google-android-development-aosp-3538503/

Regarding to bootloader not beeing unlockable anymore, there has been some inaccurate rumors circling.

1000Plateaus

Murcielago

Exactly. I needed a phone this month, so couldn't wait until Pixel 10 was fully supported by GOS. I just got a Pixel 9 Pro with a great deal (since it was last year's phone). It still has 6 years of support from GOS devs, which is excellent.

alwaysdreaming

I just bought the 9 XL Pro. I suddenly need a new phone so bought the 10 XL Pro yesterday, then immediately cancelled when I saw Graphene wasn't ready yet. Blessing in disguise; the gains in the 10 series are so minimal that if they were opinion polls they'd be within the margin of error, and I got the 9 for almost €400 less than the 10 is going for. I can take 1 year fewer of software updates for that. And I get Graphene from day one.
Much gratitude going out from me to everyone running the Graphene project.

RNDMNM

Hello, I hope you're all doing well. And, I also hope this doesn't sound rude, but I was curious if we could get a status update. I do not have social media of any kind and depend solely upon this forum for updates. I purchased the 10 early when there was a promotional deal going on, believing it could be the last supported device. The GrapheneOS team does amazing work and I know you're all working hard, I just wasn't sure what the status was at this point. Thank you very much. Again, hopefully this didn't come across in any negative way.

wizoatk

RNDMNM

At the risk of seeming flippant ...

Pixel 10 - still too early to ask us when it will be supported!

userofgos

RNDMNM I do not have social media of any kind and depend solely upon this forum for updates.

I believe one could expect a reply on this thread by GrapheneOS when the Pixel 10 is officially supported. In the meantime, you don't need a social media account on X or Mastadon to view GrapheneOS' posts and updates on the progress:

de0u

RNDMNM I do not have social media of any kind and depend solely upon this forum for updates.

I am quite confident that when there is a stable release for the Pixel 10 it will show here: https://grapheneos.org/releases

Note that there is an Atom feed: https://grapheneos.org/releases#release-announcements

RNDMNM

userofgos Oh cool! I didn't know about xcancel. I can see replies too. That's great! Thank you.

RNDMNM

Based on some replies I was reading, it looks as though Android 16 QPR1 wasn't released. I thought it had on September 3rd, which led to my initial question. To be honest, I'm still fairly new to Android so I don't even really know where to go for status updates/releases, etc. Regardless, I'm a little more aware now, thank you.

userofgos

RNDMNM I thought it had on September 3rd

Only for StockOS, it still hasn't been pushed to AOSP yet which is necessary for GrapheneOS.

RNDMNM

userofgos Makes sense now :D

wizoatk

RNDMNM

At the risk of confusing things ...

We don't know how much Pixel 10 support will be included in QRP1 AOSP source, as Pixel 10 was released on a separate device branch and then received a day 1 upgrade to QRP1. End result is that we might have to wait for Android 16 QRP2 source for full and proper support for GrapheneOS on Pixel 10. QRP2 source is expected early December.

RNDMNM

wizoatk Oh wow. Well, that changes a lot of things for me. I appreciate the heads up, hopefully it doesn't come to that but I guess if worse comes to worse I'll need to use stock until December.

Bismark

wizoatk ughhh

wizoatk

RNDMNM

Hopefully, it's obvious that my brain was acronym impaired and I meant QPR (Quarterly Platform Release) not QRP.

« Previous Page Next Page »