Conversation

Replying to
I expect some of the defense of Android to rest on AOSP and the capability to roll your own ROM, build your own marketplace, etc. Defaults like this will come up but could be explained away because "Android is not a monopoly" and certainly wasn't in 2009. 1/
2
1
Replying to
AOSP requires tons of dev get it to build/boot at all. Then you have to do tons of dev if you want to use boot security, or to remove even -some- of the proprietary bits. Combine that with keeping up with updates and it is a full time job. I tried.
1
2
Replying to and
That's not an accurate or fair assessment of our work. It is not what we do and what the project provides. GrapheneOS builds privacy and security technologies. AOSP is a solid base for us and we've never had problems building it. You continue to misrepresent the actual issues.
2
1
GrapheneOS works well on devices that never shipped with Google apps and services. You completely misrepresent the project and what we actually work on. Suggest reading the content on our site which explains the project. Not sure how you can still so completely misunderstand it.
1
1
There are smartphones not shipping with Google apps and services. GrapheneOS can run just fine on those. They do not offer comparable privacy and security, so they aren't our officially supported devices. If there were better options than Pixels we wouldn't support future Pixels.
1
1
Again, the purpose of GrapheneOS is not to offer users an alternative OS without Google apps and services for their existing device. It is not what the project develops and we clearly explain on our site that it isn't a goal. We will continue choosing the best available devices.
1
Show replies