Well, we had a good run. It was nice while it lasted…
This was the problem I had with custom firmware back when I modded Android phones — you never knew if the custom firmware developers/packagers were even going to support your phone until after you bought it.
One phone was widely supported? So you buy the next one and no one wants to support it for whatever reason. One developer says “if you buy me one I will develop for it” thinking no one actually will, and when the community actually does so, he flips it on Swappa and you never hear from him again. Shit like that.
But if you’ll pay iPhone 17 Pro prices for an iPhone 11 powered phone that comes with personal data collection out the wazoo, you’ll probably pony up for the more expensive Motorola phone coming out that they’ve (tentatively?) committed to.
I think GOS is established enough it can pull through. Won’t be easy at all though.
I do hope Motorola can give some good official support as a manufacturer.
Motorola CFW support was spotty in the past, when they were an American company. Now they are part of Lenovo (? Not sure if they still are) so maybe they do things differently now. They always had decent hardware, and their Android forks were very minimal later on (in their independent time; before they were further from AOSP) and ran pretty good for the most part. But they did not like to update their phones. Motorola phones often shipped with the Android version they would EOL on. Motorola used to be a piss-poor choice for modding back then.
I expect better from them now, but I don’t predict it.
Also, I realise the issue is with Pixel, not Graphene. Still, I would be upset if I bought a Pixel 11 planning to de-Google it.
