> CTO having zero regard for his customers and having the gall to tell us to install a new OS ourselves for our own safety after we paid him to offload the trou

> CTO having zero regard for his customers and having the gall to tell us to install a new OS ourselves for our own safety after we paid him to offload the trouble of handling security for us, you get no more of my business. I continued development of the OS under the AndroidHardening name and it's available entirely for free as a permissively licensed open source project: https://github.com/GrapheneOS https://github.com/GrapheneOS It's not a product, and you don't have to pay anything for the replacement. If you have a 1st generation Pixel, that support isn't quite ready yet, but if it's a 2nd generation Pixel the successor has been around since December. I had no way to reach out to the users and customers once James had taken over, especially after he locked me out of my email account and stole the open source project's Twitter account by rolling back the email from danielmicay@gmail.com to daniel.micay@copperhead.co. He covered up what had happened and heavily misrepresented it. You seem to believe a bit too much of what you were told by them. If you wanted help installing another OS, you just had to contact me. I often walk people through stuff like this. I'm perfectly willing to do that. It took time to rebuild things, so there wasn't immediately a direct replacement. The infrastructure was all taken over, donations to the project were stolen and this all happened right before Android Pie was released which required a major migration to get it done within a week or so of release to continue releasing full security updates for Pixels. What exactly was I supposed to do when there was an attempt to take over the project? It was not going to be possible to ever release a non-compromised update again due to loss of the infrastructure, and a complete betrayal by the company that had agreed to support the project while agreeing that I would own and control it. The project would never have had any use for the signing keys again. They were entirely a liability. They obviously weren't going to be turned over to the corrupt company and you see for yourself that they did have not even provided full security updates for almost an entire year and misrepresented that fact to their users. It's a scam now, without any actual work on privacy / security and is simply based on stolen legacy code under a license they don't have permission to use.