Android 16 release to AOSP without pixel specific source code

Andoid 16 has been released in AOSP without the device tree of the pixel phones. I have seen several custom rom developpers complaining that port may become more tedious (one from the grapheneos espcially).

As new phone will be release with Android 16, will it impact the people doing custom port of SFOS as well ? Sorry for the naive question, I do not have a good knowlegde on how to create a port.

Only if people are trying to port SFOS to the Pixel-phones.

there goes my plan to try to switch to pixel fold with graphene

1 Like

Android is a house of cards. The day Google decides to make it more closed, which seems the direction they are taking according to internal memos that have been leaked, all free distributions such as GFOS or Lineage are going to be dead.

The EU should channel a bit of funding to SFOS to achieve independence from the Apple-Google duopoly, but Jolla should also contribute a bit by making it truly open. Otherwise, it’s a slow death.

10 Likes

Same applies for Android App Support I guess