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.
Replying from Sailfish.
It’s a mixed bag. VoLTE is required in Australia (no 2G or 3G anymore) and SFOS does support it so that’s good, but for some reason calls are stuck on speakerphone as the earpiece speaker doesn’t work. The GPS lock is quite slow. I also don’t have working cameras, and every time I unplug the charger the phone reboots.
On the plus side, the Android app support is really good (though I still use native SFOS apps wherever possible, but for banking etc. its handy). I have no stability problems, its pretty rock solid bar for the charger issue. I’ve daily driven it since about October last year, and honestly if I could make private phone calls it would be perfectly fine for me.
I will note that community developed ports are available for other devices with potentially better hardware compatibility, but the Android app support is not included as it’s proprietary (though Waydroid exists as an alternative) and VoLTE support is touch and go on other devices.
In regards to the slow GPS lock, is it possible to switch the location provider to beacondb?
https://beacondb.net/
Yeah I’m in AU so that isn’t an amazing review. Hopefully they get there in a few years, I run Linux on desktop, servers and ebook reader and love it.