I don't know that they'll care too much - how many people seriously install custom roms on their phone? I'm one of them, and I'm sure there are dozens of us, but probably not enough to make an impact on google's bottom line.
So I guess the point of this is to provide a Pixel-like experience to non-Pixel phones? It's a cool idea but I think I'll personally stick with GrapheneOS for my next phone.
There is a reason why GrapheneOS requires one of these phones (a separate secure processor is needed for proper device security and MTE stops a lot of memory vulnerability exploits).
I find it funny how this thread is a continuation of comments not understanding the previous one :-).
1. chrysoprace says "well, I'd rather use GrapheneOS than PixelOS"
2. jnkl notes that actually, if you run GrapheneOS, it means you have a Pixel, and therefore you don't need PixelOS (because you have a Pixel!).
3. hurfdurf does not understand the comment, and plugs a link there because I assume it's too difficult to just write "actually, soon there will also be Motorola phones that support GrapheneOS". Which misses the point, but is factually correct.
4. nicce apparently understands jnkl and play son the fact that hurfdurf was maybe just nitpicking (but really, I think they did not care about understanding the comment they were answering too, mostly just wanted to mention the Motorola stuff).
5. microtonal does not understand the comment and goes on explaining why GrapheneOS only runs on Pixel (and soon the Motorola) phones.
I guess that's life: half of the time, people don't even try to understand what the others are trying to say...
people don't even try to understand what the others are trying to say
I think that's very uncharitable, especially because you seem to have misread the thread yourself. Note: I don't say "people don't even try to understand [...]", because my charitable reading is that you misunderstood one of the comments and therefore the whole thread. My reading of this thread:
1. chrysoprace prefers GrapheneOS (over PixelOS)
2. jnkl says "great, how are you going to run GrapheneOS if you don't have a Pixel?", this refers to the fact that this submission refers to PixelOS, which works on non-Pixel phones.
3. hurfdurf reacts by pointing out the Motorola Signature, which will soon be available and shows that GrapheneOS works on non-Pixel phones.
4. nicce circles back to the wide phone support of PixelOS and points out that GrapheneOS is still limited to Pixels and one Motorola model.
5. microtonal (me) points out that this may be true, but GrapheneOS has requirements that make it impossible to go beyond these phones (implicit: yes, for the rest you need to use something else)
Note that my reading of (2) is different and in that reading the whole chain makes sense and is consistent.
It's always surprising how many people who like to tinker with their devices also deliberately want to tie themselves more into the Google ecosystem. I would've guessed that the Venn diagram of these two types of people wouldn't have much overlap, but the ROM's popularity kind of speaks for itself.
> It's always surprising how many people who like to tinker with their devices also deliberately want to tie themselves more into the Google ecosystem.
I don’t believe that there’s a realistic alternative. The Apple ecosystem is even more restrictive, while even in 2026 the non-Android Linux phone market appears to still be pretty uncompelling.
Simple: Pure AOSP without Google Play Services is garbage as quite a lot of apps openly rely on it and the built-in core apps (phone, messages, ...) haven't been maintained in a while. Most manufacturers (cough Samsung) insist on loading their Android with bloatware. Google's Pixel has barely any bloatware, but polished core apps.
FWIW my Pixel came with all kinds of manufacturer bloat (why would I need an app for Pixel Buds? I don't own any Pixel Buds!) but at least on Google you can get rid of that crap.
On Samsung I've had the disappointing experience of not being able to nuke some of their pre-installed applications. I was under the impression that you could disable any app (even if you can't uninstall it fully) but apparently Samsung did something to prevent that.
For what it's worth, AOSP is not really a ROM anyone uses from what I can tell. LineageOS and its many forks and siblings have better standard apps for launchers, browsers, music players, the works.
If you ignore the massive privacy problems and embrace the Google ecosystem, it's actually quite nice.
Google's ecosystem is a pain in the ass to work around if you don't like it, but I find it two steps above what Samsung is offering, for instance.
AOSP and Lineage are cool projects but their usability still falls behind devices like the Pixel by far. Copying some of the Pixel applications in (possibly after neutering them a little to cover for the privacy implications) can quickly turn a "works, I suppose" custom ROM into a usable experience.
AOSP of course does. Google has abandoned AOSP's to focus on the proprietary Play's ecosystem. Hell, Google has explicitly deprecated AOSP Dialer & Messaging (as has* Music, Calendar, Email), arguably the most essential apps for a smartphone. That said, Fossify (fork of pre-acquisition SMT) provides a very nice active FOSS app ecosystem (only missing a Maps alternative).
*Trivia: AOSP Music & Calendar actually had features removed.
one of the devs here, and yeah fair, the about page says nothing. it's a custom rom that makes non-pixel phones run like a pixel: aosp + gapps + the pixel exclusive features
put simpler, this replaces the stock android your manufacturer ships
Are you planning to release images for Pixel smartphones that will no longer be supported by Google?
I have a Pixel 6a with a battery that’s almost as good as new (no thanks, Google, for how you’ve handled the battery issue), and support for it will end in July.
I struggled to work out what it was for and why I might want to install it on my Pixel 10 Fold - until it I went to the download page and dawned on me that it's to make non-Pixel phones look like Pixel ones.
It might be worth mentioning the whole reason for this to exist on the site somewhere.
The idea is cool but as some pointed out the "About" page could be a bit more informative on what the rom contains (e.g. what is included, what is planned to be included, what are the limitations etc)
Also there are a lot of devices listed on the website but if you look a bit closer on the website you realize half of them are discontinued (38 active and 44 discontinued to be precise). I did some quick scrapping and this is the current status per brand:
Asus: 2/2 active (100%) /n
Nothing: 1/1 active (100%)
OnePlus: 8/10 active (80%)
Motorola: 4/5 active (80%)
Sony: 2/3 active (67%)
Realme: 5/10 active (50%)
Xiaomi: 16/33 active (48%)
Samsung: 0/12 active (0%)
Google: 0/4 active (0%)
10or: 0/1 active (0%)
Micromax: 0/1 active (0%)
Total: 38/82 active (46%)
Maybe it would make more sense to try to focus on one or two brands instead of trying to do all of them (at least at this stage)
We are an Open-Source Project, we do not get paid for what we do here and unfortunately because of that, a lot of maintainers come and go, and we can do nothing about it. I agree with the point we need to make it clearer as to what device is supported currently and what is inactive, we will work on that.
Came across it recently, like a week ago, while looking whether my phone has any custom ROMs. Cool but worth noting it's quite in legal gray area. Pixel is trademarked by Google & bundling GApps requires* MADA license from Google & takes* actions to bypass Play Integrity.
*It's why more known custom ROMs (LOs & crDroid) are distributed without GApps.
**Something certainly great for its users but creates risk for a backlash against custom OSes.
Why would I install horrible Google ROM with Google adware voluntarily instead of other ROM? Same goes for GrapheneOS minus Google adware.
If I am going to install 3rd party ROM (as I did on most of my phones in last 15 years), it's going to be Lineage or pretty much anything else but PixelOS/GrapheneOS.
GrapheneOS is not a "Google ROM". GrapheneOS is based on the Android Open Source Project, just like this project, just like LineageOS, and just like nearly every OEM OS. GrapheneOS is not affiliated with google and is not based on the google pixel stock OS.
pretty much every ROM is based on AOSP, that doesn't say anything new, the point was both Google and Graphene ROMs are barebone lacking basic features and have zero customization
GrapheneOS is not a "Google ROM". GrapheneOS is based on the Android Open Source Project, just like this project, just like LineageOS, and just like nearly every OEM OS. GrapheneOS is not affiliated with google and is not based on the google pixel stock OS.
45 comments
[ 0.22 ms ] story [ 49.0 ms ] thread1. chrysoprace says "well, I'd rather use GrapheneOS than PixelOS"
2. jnkl notes that actually, if you run GrapheneOS, it means you have a Pixel, and therefore you don't need PixelOS (because you have a Pixel!).
3. hurfdurf does not understand the comment, and plugs a link there because I assume it's too difficult to just write "actually, soon there will also be Motorola phones that support GrapheneOS". Which misses the point, but is factually correct.
4. nicce apparently understands jnkl and play son the fact that hurfdurf was maybe just nitpicking (but really, I think they did not care about understanding the comment they were answering too, mostly just wanted to mention the Motorola stuff).
5. microtonal does not understand the comment and goes on explaining why GrapheneOS only runs on Pixel (and soon the Motorola) phones.
I guess that's life: half of the time, people don't even try to understand what the others are trying to say...
I think that's very uncharitable, especially because you seem to have misread the thread yourself. Note: I don't say "people don't even try to understand [...]", because my charitable reading is that you misunderstood one of the comments and therefore the whole thread. My reading of this thread:
1. chrysoprace prefers GrapheneOS (over PixelOS)
2. jnkl says "great, how are you going to run GrapheneOS if you don't have a Pixel?", this refers to the fact that this submission refers to PixelOS, which works on non-Pixel phones.
3. hurfdurf reacts by pointing out the Motorola Signature, which will soon be available and shows that GrapheneOS works on non-Pixel phones.
4. nicce circles back to the wide phone support of PixelOS and points out that GrapheneOS is still limited to Pixels and one Motorola model.
5. microtonal (me) points out that this may be true, but GrapheneOS has requirements that make it impossible to go beyond these phones (implicit: yes, for the rest you need to use something else)
Note that my reading of (2) is different and in that reading the whole chain makes sense and is consistent.
I don’t believe that there’s a realistic alternative. The Apple ecosystem is even more restrictive, while even in 2026 the non-Android Linux phone market appears to still be pretty uncompelling.
On Samsung I've had the disappointing experience of not being able to nuke some of their pre-installed applications. I was under the impression that you could disable any app (even if you can't uninstall it fully) but apparently Samsung did something to prevent that.
For what it's worth, AOSP is not really a ROM anyone uses from what I can tell. LineageOS and its many forks and siblings have better standard apps for launchers, browsers, music players, the works.
Google's ecosystem is a pain in the ass to work around if you don't like it, but I find it two steps above what Samsung is offering, for instance.
AOSP and Lineage are cool projects but their usability still falls behind devices like the Pixel by far. Copying some of the Pixel applications in (possibly after neutering them a little to cover for the privacy implications) can quickly turn a "works, I suppose" custom ROM into a usable experience.
*Trivia: AOSP Music & Calendar actually had features removed.
put simpler, this replaces the stock android your manufacturer ships
I have a Pixel 6a with a battery that’s almost as good as new (no thanks, Google, for how you’ve handled the battery issue), and support for it will end in July.
You might have an opportunity in this market.
It might be worth mentioning the whole reason for this to exist on the site somewhere.
Also there are a lot of devices listed on the website but if you look a bit closer on the website you realize half of them are discontinued (38 active and 44 discontinued to be precise). I did some quick scrapping and this is the current status per brand:
Asus: 2/2 active (100%) /n Nothing: 1/1 active (100%)
OnePlus: 8/10 active (80%)
Motorola: 4/5 active (80%)
Sony: 2/3 active (67%)
Realme: 5/10 active (50%) Xiaomi: 16/33 active (48%) Samsung: 0/12 active (0%) Google: 0/4 active (0%) 10or: 0/1 active (0%) Micromax: 0/1 active (0%) Total: 38/82 active (46%)
Maybe it would make more sense to try to focus on one or two brands instead of trying to do all of them (at least at this stage)
What is there in the ROM keeps changing, every release, we will try to display that as well on the main page. We currently communicate changelogs thru our blog https://blog.pixelos.net/ and screenshots can be found here https://blog.pixelos.net/docs/resources/screenshots
*It's why more known custom ROMs (LOs & crDroid) are distributed without GApps.
**Something certainly great for its users but creates risk for a backlash against custom OSes.
95% of people won’t understand what this means.
If I am going to install 3rd party ROM (as I did on most of my phones in last 15 years), it's going to be Lineage or pretty much anything else but PixelOS/GrapheneOS.
Former Pixel owner
LineageOS has more Google than GrapheneOS which has literally 0 Google connections by default and replaces some of AOSP apps with there own.
https://grapheneos.org/faq#default-connections
https://grapheneos.org/faq#bundled-apps
Doesn't matter you will still have plenty of google connections because unlike GrapheneOS they do not care about privacy.