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.
deleted by creator
Get a FairPhone with /e/OS. Give money to people who actually want to see an open ecosystem, not lock it down.
Anti Commercial-AI license
deleted by creator
Oh sweet! a question then for you: can you explain what the FairPhone is missing in terms of security? Do you maybe have notes comparing it to the Pixel? As a security layman, I’m curious.
Anti Commercial-AI license
There is a fairly all-or-nothing-security group of people within the GrapheneOS community. They will defend using a Google device on the claim of enhanced security.
Security is nice, but I’ll take a hit to security if it means I get to support the growth of an ecosystem that respects the user.
I got one a few months ago. I guess the updates will stay for the next 5/7 years (shitty guess) as long as GrapheneOS stays on Android 15, but my next phone will not be a Pixel if Google does shit like that.
I bought a cheap Pixel 8a, no need to pay the full price unless you need big emulators.
Much like their “no longer recommended” older pixels, it feels like they could likely continue to provide OS updates well into future Android versions. However, without access to the device-specific releases they may begin to lag behind on firmware updates