Skip Navigation

It appears Google has stopped publishing device-specific source code for Pixel phones

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.

83 comments
  • Google is slowly closing access to everything. It's a boiled frog situation. All the red flags are there. We're fucked.

    • keep the faith - we are not fucked, we just need to move to different systems entirely.

      • There is currently no alternative to android. Every alternative is both less secure and less usable.

      • If there were other systems I'd be using them already.

      • 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:

        • Tearing apart ROMs for blobs and backport/reverse-engineering patches to make them run on alt OSes.
        • Find some hardware based on janky Chinese modems that will have little band support, lackluster performance, and likely banned by most carriers.
        • Start a new company with the pull to design a new phone OS and hardware with chip and carrier support.

        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.

  • While this was an inevitable move, it makes me curious if they are hitting a point where Gemini is becoming so integrated in all their software stacks and they're just insanely paranoid about any precious "AI" code leaking that they just decided to close the gates early.

    Probably for the best long-term. Having this weird dependency on the generosity of a corporation was always a liability. Whatever comes next can hopefully avoid it.

    Hopefully someone like the EU, to combat ewaste, eventually requires all hardware manufacturers to sell their mobile hardware with bootloader/firmware flashing unlocking requirements. The work then will be for the community to write support for all these various makes and models of device, but the endgame being actual device freedom. Although with the world seemingly leaning hard into Authoritarianism and Fascism, it might not end up being the right time and freedom will remain underground.

    A pity too, all phone hardware at its core is generic ARM computers with various devices connected to fairly generic interface busses. They just encrypt bits of code so the sauce to make things work is hidden.

83 comments