As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it’s more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
The complexity of getting the closed binary blobs to run modems and other hardware will make it exceedingly difficult to extract the necessary files and configurations to keep third-party OSes afloat. Then there’s the matter of carrier configs, carrier compatibility, expensive carrier certification, and even then, carriers may still just ban the device because they don’t like it.
Options will end up being:
Not impossible, just exceedingly difficult. These systems are heavily integrated and heavily proprietary.
Funny part is, this move will actually make Google lose more money, as Google will lose hardware/software sales, and software dev over this. More people will end up on iOS in the interim, and out of it will come some new mobile OS that will make Google’s mobile OS irrelevant in 10 years.
Let’s start now, start a company, base a new phone on QNX, have an Android emulation layer for apps until a proper SDK is developed, and just take the wind out of Google sooner than later.