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.
"PixelOS is an AOSP based ROM, with Google apps included and all Pixel goodies. We aim to provide an experience similar to Google Pixel phones with numerous performance enhancements and a small amount of useful additional features."
Yes, but it doesn't really make that clear. I first thought that it was a replacement OS for Google Pixel phone which replicates the functionality of the original OS but adds enhancements and features.
That's the brand confusion born of appropriating Google's Pixel mark and the reason why trademark protection exists.
If you make a hamburger seasoning blend that approximates the taste of McDonald's and call it "McDonald's burger flavor", you're going to have a bad time with the legal system. I don't expect this to fly either.
You said, "I first thought that it was a replacement OS for Google Pixel phone", which was my experience as well. I was arguing that confusion began with the branding. It could be said that better copy on the landing page could offset it, but it's still a reasonable interpretation of the name 'PixelOS'.
Fair. I got to the "experience similar to Google Pixel phones" bit and thought well I've already got a pixel so I don't need this, but I see your point about the extras.
This is exactly what was on the front page when I looked, and I was confused as well. I own a Pixel device and have replaced the original OS with Lineage in order to get rid of some of Googles more aggressive behavior, like pushing Google Wallet in front of my face through notifications. I thought the intention for this ROM might be to get back some of the original Pixel OS functionality.
Motorola's first with a performant implementation of ARM Memory Tagging Extension
with more cheaper variants following. MTE is the hardware capability that GrapheneOS relies on for its claims of security (along with coding practices) and it's the reason GrapheneOS has only been released to certain Pixels to date.
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.
Nope, no affiliation at all, we're an independent community project. If anything, google makes life harder for us lol, play integrity is a constant cat and mouse thing for every custom rom
Just making it pass. Google advertises it as a way to find out if a device is secure with a locked bootloader and enforcing SELinux, but it's really just checking if it looks official. Finding a way to get through the checks is what lets you use your banking app on a custom ROM.
Do you work on all levels or just BASIC_INTEGRITY? (I understand that's already a ton of work, but increasingly I find banking apps need more even for basic functionality).
Don't you think you're likely to get taken down from a trademark claim?
The PIXEL trademark is owned by Google LLC and registered with the U.S. Patent and Trademark Office under multiple registrations (such as Registration No. 6634022 and No. 5091394) covering hardware, mobile devices, computers, and software.
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 (comment 2) and therefore the whole thread. My reading of this thread:
1. chrysoprace prefers GrapheneOS (over PixelOS)
2. jnkl says (paraphrased) "great, how are you going to run GrapheneOS if you don't have a Pixel?", this submission about PixelOS, which works on non-Pixel phones.
3. hurfdurf reacts by pointing out the Motorola Signature, will soon be available. Which is a counterpoint to (2), namely that GrapheneOS (soon) works on non-Pixel phones.
4. nicce circles back to the wide phone support of PixelOS by pointing out that GrapheneOS is still limited to Pixels and one Motorola model (which is still very limited, extending the argument of (2)).
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 my reading of (2) the whole chain makes sense and is consistent.
IANAL, but I assume that the situation is quite different in that when running GrapheneOS on a Pixel, the owner paid Google for being able to run the proprietary bits if they want to.
Also, GrapheneOS doesn't ship Google proprietary apps by default. It's the user installing Play Services, Pixel Camera, etc.
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.
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 (LaOS & crDroid) are distributed without GApps.
**Something certainly great for its users but creates risk for a backlash against custom OSes.
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%)
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.
And 95% of those people would never install a rom anyways.
This page speaks to the addressable market. Putting more cruft in to talk to more people would hurt the pitch for those who are the addressable market.
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.
dunno about the latest lineage, but on previous phones I had lineage without gapps
btw. I said about GrapheneOS "Same goes for GrapheneOS minus Google adware", I am aware GOS doesn't have Google by default, but it's still crappy Google ROM with zero customization and no features
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
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.
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.
> 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.
I meant more like installing LineageOS (which exists for most of the devices that PixelOS is ported for) and managing Google apps yourself - whether just installing a regular minimal GApps, or using MicroG. PixelOS is like a "give me Google everything" nuclear option.
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.
Tbf I (degoogled Graphene/ex-LOS user for more than a decade) can definitely see why you would rather have the mostly-AOSP-native Pixel experience on your smartphones than completely enshittified UIs that Samsung or Huawei provide...
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.
"PixelOS is an AOSP based ROM, with Google apps included and all Pixel goodies. We aim to provide an experience similar to Google Pixel phones with numerous performance enhancements and a small amount of useful additional features."
Was this not on the front page when you looked?
Yes, but it doesn't really make that clear. I first thought that it was a replacement OS for Google Pixel phone which replicates the functionality of the original OS but adds enhancements and features.
That's the brand confusion born of appropriating Google's Pixel mark and the reason why trademark protection exists.
If you make a hamburger seasoning blend that approximates the taste of McDonald's and call it "McDonald's burger flavor", you're going to have a bad time with the legal system. I don't expect this to fly either.
I don't know, I was never confused about the branding.
You said, "I first thought that it was a replacement OS for Google Pixel phone", which was my experience as well. I was arguing that confusion began with the branding. It could be said that better copy on the landing page could offset it, but it's still a reasonable interpretation of the name 'PixelOS'.
Fair. I got to the "experience similar to Google Pixel phones" bit and thought well I've already got a pixel so I don't need this, but I see your point about the extras.
This is exactly what was on the front page when I looked, and I was confused as well. I own a Pixel device and have replaced the original OS with Lineage in order to get rid of some of Googles more aggressive behavior, like pushing Google Wallet in front of my face through notifications. I thought the intention for this ROM might be to get back some of the original Pixel OS functionality.
This is text written for someone who already knows what all these things are.
Classic engineering communication error.
It doesn't help that GrapheneOS _only_ works on Pixel phones (and also doesn't mention this on their homepage).
That's _not_ true. See recent HN submissions about GrapheneOS on Motorola (signature 27).
Edit: https://news.ycombinator.com/item?id=50380810
Seems confirmed but not released yet?
Can't find it on
https://grapheneos.org/faq#device-support
https://grapheneos.org/releases
That's a flagship release - but it's
with more cheaper variants following. MTE is the hardware capability that GrapheneOS relies on for its claims of security (along with coding practices) and it's the reason GrapheneOS has only been released to certain Pixels to date.(2023) https://security.googleblog.com/2023/11/mte-promising-path-f...
At no point do they specify for whom they intend to provide this experience.
I read it as people who don't already have pixel phones, but clearly a lot of other people aren't, so they might need to be more explicit.
This does not really explain much, at all.
Also, is this a bot/LLM account?
Practically nothing useful on the About page. Can anyone chime in what this is exactly?
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.
You might have an opportunity in this market.
How does the project position in privacy?
That’s a good description. It would be nice to mention non-pixel phones on the home page
Has the project any affiliation with Google?
Nope, no affiliation at all, we're an independent community project. If anything, google makes life harder for us lol, play integrity is a constant cat and mouse thing for every custom rom
What changes do you make to improve Play Integrity?
Just making it pass. Google advertises it as a way to find out if a device is secure with a locked bootloader and enforcing SELinux, but it's really just checking if it looks official. Finding a way to get through the checks is what lets you use your banking app on a custom ROM.
Do you work on all levels or just BASIC_INTEGRITY? (I understand that's already a ton of work, but increasingly I find banking apps need more even for basic functionality).
Don't you think you're likely to get taken down from a trademark claim?
[flagged]
what are some pixel exclusive features ?
pixel launcher, at a glance, circle to search, the pixel wallpapers and theming plus a bunch of small stuff like the fonts, icons, boot animation etc
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.
GOS on non-Pixel-Phone?
https://news.ycombinator.com/item?id=50380810
GOS on non-Pixel-Phone or non-Motorola Signature 27?
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 (comment 2) and therefore the whole thread. My reading of this thread:
1. chrysoprace prefers GrapheneOS (over PixelOS)
2. jnkl says (paraphrased) "great, how are you going to run GrapheneOS if you don't have a Pixel?", this submission about PixelOS, which works on non-Pixel phones.
3. hurfdurf reacts by pointing out the Motorola Signature, will soon be available. Which is a counterpoint to (2), namely that GrapheneOS (soon) works on non-Pixel phones.
4. nicce circles back to the wide phone support of PixelOS by pointing out that GrapheneOS is still limited to Pixels and one Motorola model (which is still very limited, extending the argument of (2)).
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 my reading of (2) the whole chain makes sense and is consistent.
There is no way Google will let this live right?
Project has been around for a while, so it's got some resiliency built in.
Such projects existed for long time, I think Pixel Experience ROM was first.
Or it's an uphill battle (which is still being fought relatively well imho), like with GrapheneOS.
IANAL, but I assume that the situation is quite different in that when running GrapheneOS on a Pixel, the owner paid Google for being able to run the proprietary bits if they want to.
Also, GrapheneOS doesn't ship Google proprietary apps by default. It's the user installing Play Services, Pixel Camera, etc.
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.
It sounds like they include all the Google Spyware anyways, so I doubt they have a problem with that...
Only as long as it stays irrelevant. I find it amusing they have a "legal" page.
Why would Google be against more people installing their adware?
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 (LaOS & crDroid) are distributed without GApps.
**Something certainly great for its users but creates risk for a backlash against custom OSes.
Err...surely Google is going to sue? Can someone tell me how this is legal?
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%)
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.
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
[dead]
I think this is a bad name for the project if they don't want heat from Google.
I'd be a bit nervous re: the legal implications of using "Pixel" in the name of the project (I thought this was an official Google project).
An OS for the coomer consoomer.
“PixelOS is an AOSP based ROM”
95% of people won’t understand what this means.
And 95% of those people would never install a rom anyways.
This page speaks to the addressable market. Putting more cruft in to talk to more people would hurt the pitch for those who are the addressable market.
Good thing it's not the 1900s anymore and you are 3 seconds away from finding out.
I don't want google in my android.
Do it for the 2 XL!!
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.
Former Pixel owner
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.
>it's going to be Lineage or pretty much anything else but PixelOS/GrapheneOS
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
dunno about the latest lineage, but on previous phones I had lineage without gapps
btw. I said about GrapheneOS "Same goes for GrapheneOS minus Google adware", I am aware GOS doesn't have Google by default, but it's still crappy Google ROM with zero customization and no features
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
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.
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.
> 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.
I meant more like installing LineageOS (which exists for most of the devices that PixelOS is ported for) and managing Google apps yourself - whether just installing a regular minimal GApps, or using MicroG. PixelOS is like a "give me Google everything" nuclear option.
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.
Google is an ad company. They probably have so much tracking you can't get rid of.
Tbf I (degoogled Graphene/ex-LOS user for more than a decade) can definitely see why you would rather have the mostly-AOSP-native Pixel experience on your smartphones than completely enshittified UIs that Samsung or Huawei provide...
you forgot Xiaomi and Realme
[dead]