Since when did AOSP become a graveyard? Why did Google halt almost all non-maintenance development on it?
Pajeets.Pajeets ruined the custom ROM scene and AOSP. I started flashing in 2013 and even by ~2018 it was pretty much done for.>okay but why did Google haltSee above.
>>108949578Google stopped fixing bugs by 2015.
they dont need to compete. it is mandatory to have iOS or Google Android with Play to participate in modern söyciety
the answer to every single tech question you have is unironically always gonna be because Indians
>>108949578>why use the FOSS Cell Broadcast Service, when you can use the proprietary Google Cell Broadcast Service>why use the FOSS Emergency Services, when you can use the proprietary Google Emergency Services>why use the FOSS Messages, when you can use the proprietary Google Messages>why use the FOSS Phone, when you can use the proprietary Google Phone>why use the FOSS Clock, when you can use the proprietary Google Clock>why use the FOSS Email, when you can use the proprietary GMailAnd so the FOSS AOSP stock applications are no longer maintained, in favour of the proprietary ones, which Google forces them to be part of GMS. That said, the underlying OS is getting updated. It's just that 3rd party ROMs usually must bring replacements for the unmaintained FOSS applications. At least there are alternatives, and the stock applications also sort of work, as the API level limitations apply to Play Store, and not to what Android can execute. Android 17 still runs the original Flappy Bird for instance, as long as your CPU can execute 32-bit code (SD8g2, Exynos 2200).
