Android 17 is the first since 3.x to add new APIs without releasing to the AOSP (grapheneos.social)

Article summary

The article discusses Android 17's new APIs without releasing to the AOSP, sparking concerns about Google's control over the operating system. The comments reveal a discussion about the implications of this move and the potential for alternative open-source options. Some commenters express frustration with Google's approach and consider switching to alternative operating systems like GrapheneOS or postmarketOS. The conversation also touches on the challenges and limitations of these alternatives.

Main themes

• Android and open-source
• Google's control and motivations
• Alternative operating systems
• Security and privacy
• Hardware manufacturer support
• Forking Android
• User freedom and convenience trade-offs

What commenters say

• Google's control over Android is problematic and may lead to a loss of freedom for users.
• Alternative open-source operating systems like GrapheneOS and postmarketOS offer a more secure and private option, but may lack certain features.
• The major phone OEMs are happy with Google's current approach and are unlikely to fork Android.
• Google's decisions regarding Android are motivated by a desire to increase control and revenue, potentially at the expense of user freedom.
• The development of alternative operating systems is hindered by the lack of support from hardware manufacturers and the complexity of maintaining a fork of Android.
• Some commenters believe that Google's actions are driven by external pressures, such as lobbying from three-letter agencies.
• The trade-off between security and convenience is a major consideration for users, with some prioritizing one over the other.
• The potential for a fork of Android, similar to the MariaDB fork of MySQL, is unlikely due to the complexity and cost of maintaining such a project.