The launch of Android 16 was marked by the problem of many users and developers when he checked that Google excluded two key resources for the development of personalized ROMs. In particular, the company did not publish hardware repositories or pixel devices. This made many suspect that the version Open Android source (AOSP) Not very stopped. Now, after several days of uncertainty, Google spoke about this.
Based on the context, the problems began to arise after the launch of Android 16, when the developers noticed that the source code, which accompanied this version for the Android open source project, did not have two key Pixel equipment repositors. While the rest of the resources were available that Google Do not turn on the devices so many and other resources of your pixel, This is a great inconvenience for many developers.
In particular, those who create personalized Roms Android They cannot develop system updates usuallyResearchers can also experience difficulties with the search for vulnerabilities or safety problems in the system. However, the most worried that this restriction seems to be a little step at the end of Android AOSP.
Android will continue to remain open source, although with “but”
Schong Chau, Vice President of Android, did not accept the answer to the problems for users. In the publication in his profile X (Twitter), the executive director confirmed that The Android open source version “will not disappear.” In addition, already addressing the developers, he said that the company will still be committed to AOSP updates.
We see some assumptions that AOSP is stopping. To clarify, AOSP will not disappear. AOSP was built on the basis of an open platform for the implementation of devices, processing suppliers and architectures of instructions.
Chau too He talked about the disappearance of Pixel repositoriesThis field makes it clear that it was a deliberate movement and that in the future the Android version with open source will have a “reference goal”. This will be more flexible and independent of Google Hardware.
AOSP needs a reference goal, which is flexible, customizable and affordable, independent of which -libs of specific equipment, including Google. For many years, the developers built a karakatitsa (accessible in GitHub as a reference device for AOSP) and GSI -goals from the source code. We continue to make them available for testing and development goals.
Although it is very inconvenient for many developers, Android Mobile users They will not notice big changesThey can continue to enjoy the setting and many options offered by the Google operating system.
Source: Hiper Textual
I’m Ben Stock, a highly experienced and passionate journalist with a career in the news industry spanning more than 10 years. I specialize in writing content for websites, including researching and interviewing sources to produce engaging articles. My current role is as an author at Gadget Onus, where I mainly cover the mobile section.
