Google shifts Android development to private internal branches for faster updates
Google is making a major change in its Android development process by moving all activities to private internal branches, starting next week. Under this new approach, engineers will work internally before releasing updates, which is a shift from the previous practice where changes were made privately but then published to the Android Open Source Project (AOSP). Now, Google's internal branches will only be accessible to companies with a Google Mobile Services (GMS) license, though the company assures that Android will remain open source, with new version source codes still being released.
The change is driven by delays in feature rollouts, bug fixes, and security updates, which Google attributes to the complexities of merging public and private code branches. Contributions to AOSP will still be accepted, but Google will control what is merged. Key Android components like the build system, update engine, Bluetooth stack, virtualization framework, and SELinux configuration will now be developed privately, with their source code released alongside new Android versions.
For users, this shift will not impact their experience with Android on their devices. However, independent developers relying on AOSP for early access may face delays, as the source code will remain available but with longer waits for public releases.
Related news
External links
- Exclusive: Google will develop the Android OS fully in private, here's whyAndroid Authority
- Google makes Android development private, will continue open source releases Ars Technica
- Google confirms Android development will soon become fully privateTechSpot
- Google is making Android development more of a private affairAndroid Police
- Google Takes Android Development PrivateDroid Life
Comments
This could be a good thing or a horrible thing. I am not sure yet. On one hand it means they have better quality control on other hand too much control means potentially worse direction for Android and the US gov forcing them to leave backdoors. Time to make a new mobile OS. Maybe something based on some version of BSD.
I really hope this isn't a dark path for Free Software...
It seems that its recent moves (upstreaming most code to Linux using "Generic Kernel Image", moving modules to its "Mainline architecture", adding Linux VM) is mainly an escape for Google to continue to get much control of Android (using AOSP) once they we'll need to sell Android. Rushing the development will allow to make as much public code as possible before using it to finally compete with Android. And if it allows us to get better overall Android experience (I've gave up on stock Android experience many years ago but some ROMs are great), it's a win-win.