For me the most interesting piece from the Mastodon thread is the fact that the Motorola partnership was born out of Google making it more difficult for non-OEMs to get access to AOSP source code (emphasis mine):
Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It’s completely ridiculous and they’ve gradually become very slow at handling requests. They’re in clear violation of the GPLv2 now.
[…]
These changes won’t negatively impact GrapheneOS on upcoming Motorola Mobility devices. In fact, it’s a major part of why our partnership exists. It only negatively impacts Pixels and hurts Google more than anyone else. Google wants to make Pixels worse for no apparent reason.
This also means that in the future Motorola devices will get faster security updates on GrapheneOS than Pixels.
i’ve been waiting too, but now that i know that the motorola phone will cost more than a pixel, now i think i just might give up and go with a pixel instead.
For me the most interesting piece from the Mastodon thread is the fact that the Motorola partnership was born out of Google making it more difficult for non-OEMs to get access to AOSP source code (emphasis mine):
This also means that in the future Motorola devices will get faster security updates on GrapheneOS than Pixels.
This is exactly why I’ve waited to get a Graphene OS phone, Google can’t be trusted.
i’ve been waiting too, but now that i know that the motorola phone will cost more than a pixel, now i think i just might give up and go with a pixel instead.