The constant growth and acceptance of open source technologies in the digital world clearly shows that transparency, collaboration, and innovation are closely linked. Google plays a central role in the technological world and its influence on software, technologies, and hardware is enormous. Google's developments on Android and the influence of these developments on the AOSP (Android Open Source Project) play an essential role in a wide range of device types in our everyday lives, for example: Smartphones, tablets, televisions, cars, and more are just a few of the device types that run on AOSP.

A change in attitude toward open source is putting the future of open and user-friendly technologies at stake. In particular, the development of Android, one of the most widely used operating systems worldwide, needs to be revised in terms of its transparency and the involvement of the open source community.

Many users choose an Android system to avoid a closed ecosystem, trusting that Google will remain committed to open source and that developments will continue to find their way into the AOSP (Android Open Source Project). Google, as the developer of Android and “guardian” of the AOSP, must ensure that its development practices and company policy continue to support these principles.

A key concern is that Google should be required to integrate developments from the open source world into the AOSP no later than six weeks after the global launch of a new Android device and to restore the previous quarterly release cycle. In addition, a key demand is that changes due to vulnerabilities with a risk rating of CVSS > 7 be integrated into AOSP immediately, and changes with vulnerabilities with a medium impact within two weeks. This would ensure transparency, security, and data protection when using Android, and all innovations would be integrated into the Android Open Source Project (AOSP) in a timely manner.
 

Currently, custom ROM developers are faced with the challenge that Google no longer publishes Pixel sources into the AOSP. This forces developers to engage in reverse engineering, which means months of work per device and hinders the development of custom ROMs that, for example, extend the life of old devices or allow users to use an alternative system that places greater emphasis on privacy and security. Timely provision of sources would once again make it much easier to achieve broader hardware support significantly faster, reduce e-waste, strengthen fundamental and personal rights as well as the digital sovereignty of states and communities of states such as the EU, strengthen the innovative power of the open source community, and drastically reduce the dependence of open source projects and individuals on the decisions of a single tech company.

Furthermore, it is crucial to persuade OEMs such as Samsung and others not to lock their bootloaders and to get chipset manufacturers to make the necessary drivers available to the community. These measures would strengthen user freedoms and support the customization and personalization of devices. 

For this vision to become a reality, Google must use its strategic position to set a positive example and actively contribute to improving the open source ecosystem. Mandatory participation and co-creation can promote a fair and open environment that benefits everyone.
We call on Google to reform its practices and enable greater transparency and active participation in the further development of Android. This would not only help the open source community, but also underscore Google's role as a progressive company in the tech industry. Please support this petition to encourage Google to improve its open source support again. Every signature contributes to the realization of a transparent and open technological future.

More information on the increasing “closure” of AOSP: 
https://keepandroidopen.org/de/
https://c.org/QWS9hbkVCX

If Google does not comply, the demand to politicians is as follows:

~~~~~~~~~~~~~~~~~~~~~~~
Dear Sirs and Madams,
As a private user and user of /e/OS, LineageOS on old devices, and an employee in the IT industry, I know how important alternatives are. I am frustrated: Google is making Android (AOSP) increasingly closed—missing device trees since Android 16 and a focus on internal development that excludes the open source community and the public. Custom ROMs such as LineageOS, /e/OS, or GrapheneOS enable data protection and device longevity over many years, but without support from Google and hardware support from Qualcomm & Co., they fail. Europe needs digital sovereignty – not dependence on US corporations!

Our problem:

Google no longer publishes Google Pixel sources into AOSP: Custom ROM developers have to reverse engineer – several months of work per device. It is becoming increasingly difficult to create and use alternatives.

OEMs (Samsung, etc.) lock bootloaders; chipmakers do not release drivers.
– Consequence: Fewer updates, more e-waste, Google control over our data and smartphones.

Our clear demands:

1. DMA extension: Google must integrate device trees, kernel sources, and drivers into the AOSP no later than six weeks after the global launch of a new Android device and restore the previous quarterly release cycle. Changes to vulnerabilities with a risk rating of CVSS > 7 must be integrated into the AOSP immediately, and changes to vulnerabilities with a medium impact must be integrated within two weeks.
2. Manufacturers such as Qualcomm must provide bootloader unlocking and sources for at least 10 years or, after five years – or in the event of insolvency – make them available free of charge under an open source license and make them available to the community in a location that is easily accessible to the open source community. The background to this is to enable the community to continue development (e.g., maintaining drivers for Linux kernels, patching vulnerabilities). - EU penalties for violations by manufacturers.

3. FOSS fund: 0.5% of tech revenue (Google, etc.) into a fund for open source hardware (e.g., expand Prototype Fund, 20% public IT for FOSS).
4. Buy open source: Authorities prioritize sovereign ROMs (/e/OS) in procurement.

This strengthens jobs in Europe and open source positions, protects data privacy (e.g. GDPR), cyber resilience through open source, and reduces dependency. Open source is voluntary work and contributes to the common good – I beg you to recognize and support it! 
~~~~~~~~~~~~~~~~~~~~~~~

Why now? LineageOS already supports many devices and often serves as the basis for further developments; with support, there could be significantly more.  Sign up for a free, long-lasting and open Android/AOSP!