Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

川普在美国宾州巴特勒的一次演讲中遇刺_20240714川普在美国宾州巴特勒的一次演讲中遇刺_20240714
0

Mountain View, CA – Google is reportedly planning a significant shift in its Android development strategy, moving all Android OS component development entirely in-house, according to a report by Android Authority. The move is aimed at streamlining the development process and boosting overall efficiency.

Currently, while certain Android components, such as the Bluetooth protocol stack, are still developed publicly within the Android Open Source Project (AOSP), core operating system frameworks and other crucial parts have long been developed internally at Google. This internal version of Android contains significantly more code than the publicly available AOSP branch, leading to a persistent lag between the two. The disparity is particularly noticeable between the AOSP code and Google’s latest Android 16 beta.

While Google has implemented a trunk-based development model to try and bridge this gap, code synchronization remains a complex challenge. This disconnect means Google spends considerable time merging patches between the AOSP and internal branches. Due to the structural differences in the codebases, these merges often result in conflicts.

The Android Authority report cites an example of an accessibility settings list for a screen magnification feature for the navigation bar and keyboard. The differing list lengths between the AOSP and internal branches prevented a direct merge of the patch. While such issues can be resolved individually, the sheer volume of these conflicts significantly hinders development speed.

Faced with these numerous code synchronization issues, Google has reportedly decided to abandon the current dual-track development model in favor of a fully internal development approach to simplify the process.

However, Google has emphasized that this shift does not mean Android is becoming a closed-source system. The company will continue to release the Android source code, synchronizing it with the public domain whenever a new version of Android is launched, such as the anticipated Android 16 later this year.

Furthermore, the Android Linux kernel branch, licensed under GPLv2, will remain open-source to comply with the licensing agreement.

According to the report, this change means that starting next week, all Android component development will be conducted internally at Google, with the corresponding source code only being released publicly when Google releases a new version. In effect, this represents a consolidation of existing practices, as many Android components already follow this strategy. Google is simply unifying the development workflow.

For the average Android user, this change is unlikely to have a direct impact. The focus remains on delivering a stable and feature-rich operating system.

Impact and Analysis

This move by Google signals a prioritization of development speed and efficiency. While the open-source nature of Android has fostered innovation and community contributions, the complexities of maintaining two separate codebases have clearly become a significant bottleneck.

By consolidating development internally, Google aims to:

  • Reduce code synchronization overhead: Eliminating the need to constantly merge patches between internal and AOSP branches.
  • Accelerate feature development: Streamlining the development process allows for faster iteration and deployment of new features.
  • Improve code quality: Focusing development efforts on a single codebase can lead to more consistent and robust code.

While the shift may raise concerns about the future of community involvement in Android development, Google’s commitment to releasing source code and maintaining the open-source nature of the Linux kernel branch should alleviate some of these concerns. The long-term impact on the Android ecosystem remains to be seen, but the move underscores Google’s dedication to improving the efficiency and performance of its flagship mobile operating system.

References:


>>> Read more <<<

Views: 0

0

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注