Google's new developer verification requirements starting September 2026 will force ALL Android app developers to register with Google - even those avoiding the Play Store entirely. F-Droid, the tr...
As far as I understood from Graphene, when Google released the source code for Android 16, they also stripped all the reference code for Pixel devices.
Historically, Google would ship the code for Pixel and a software emulator as “reference designs”. Now, it’s only shipped with the emulator.
The Graphene Team needed to reconstruct the pixel code from the Android 15 release. Fortunately, the divergence between Android 15 and 16 was minimal, but I’m certain the division will widen as time goes by.
yeah i think i understood it like that too, but they sounded confident that this was a one time issue and that it wont really be a problem now for future releases
but sry i am not really sure what you mean/ the connection is to the topic/ the os/ driver and firmware blobs?
… except for the binary os blobs, that’ll need to be reverse engineered to run it on… well… any real hardware /s
but these are firmware and drivers from the hardware manufactures and not the OS
As far as I understood from Graphene, when Google released the source code for Android 16, they also stripped all the reference code for Pixel devices.
Historically, Google would ship the code for Pixel and a software emulator as “reference designs”. Now, it’s only shipped with the emulator.
The Graphene Team needed to reconstruct the pixel code from the Android 15 release. Fortunately, the divergence between Android 15 and 16 was minimal, but I’m certain the division will widen as time goes by.
yeah i think i understood it like that too, but they sounded confident that this was a one time issue and that it wont really be a problem now for future releases
but sry i am not really sure what you mean/ the connection is to the topic/ the os/ driver and firmware blobs?