Google is again engaging in anti-competative or in the United States, antitrust behaviour, which is against the law.
With this new action Google is getting rid of ALL competitors, where Android phones must run through Google (it's about 'forcing' the licencing of GMS (Google Mobile Services)), where they are not able to function under AOSP (Android Open Source Project), such as Lingeage OS and GraphenOS.
AOSP is a baseline operating system of Android which manufacturers (e.g Samsung, Motorola, Huawei, etc) use before they load up their hardware with their spyware bloated version of Android.
Lingeage and Graphene, are among a few custom open source Android operating systems called ROMs, that do not have highly invasive 'spyware' that Google and other phone manufaturers (e.g. Samsung) install on their phones, which can be a danger to people's lives where they require privacy or anonimity as a result of their job or for other reasons.
The tech and legal communites MUST take action against Google's latest 'illegal' practice.
Whether they will, is another story that time will tell.
See a Comparison of Android-based Operating Systems:
Most of these ROMs are privacy (and security) focused, where Google's actions are an attack on user's privacy and therefore security.
Google is deliberately killing off AOSP.
At the end of the day it's all about data collection by the giants Google and Apple, where the latest actions by Google are part of the global 'Nanny State' agenda where only duopoly powerhouses exist.
If you truly value your privacy, then Google products are not the ones that you will achieve privacy with.
See the following article by androidpolice.com of the following headline:
Google’s latest AOSP move spells doom for custom ROMs on Pixel phones
For years, Google used its Pixel phones as reference devices for AOSP
development. As part of this, the company also published the device
trees and driver binaries, ensuring that developers could compile a
fully working AOSP build of Android for Pixels. Custom ROM developers
also relied on the same device trees and driver binaries to ensure core
features worked properly in their ROMs.
This won't be the case going forward, though. While Google has already published the Android 16 source code, it won't be releasing the device trees and driver binaries for compatible Pixel phones. The Graphene OS team initially claimed that Google made this change as it planned to discontinue AOSP entirely.
However, Seang Chau, VP and GM of Android Platform, refuted such rumors and provided a clearer picture (via Android Authority).
He made it clear that Google is not doing away with AOSP. But going
forward, AOSP will use a reference target device "that is flexible,
configurable, and affordable — independent of any particular hardware,
including those from Google." And so, Google is switching from Pixels to
Cuttlefish — a virtual Android device— as the reference AOSP device.
Since it's a virtual platform, developers can run Cuttlefish remotely or
locally.
Custom ROM development for Pixel phones just got a lot more difficult
This move from Google will change the custom ROM development scene
for Pixel phones forever.
Unlike other Android devices, device trees and
binaries made it relatively easier for developers to build ROMs for
Pixel devices.
Without them, they would have to
reverse-engineer prebuilt binaries to find out the changes that Google
made — a challenging and time-consuming process. The lack of kernel
source code commit history from Google only adds to the complexity.
Think
of these device trees and binaries as the Android equivalent of drivers
on a Windows PC — they ensure the operating system can properly
communicate with the device's hardware.
Google's latest
changes to AOSP will have a major impact if you run LineageOS or another
custom ROM on your Pixel. That's a dwindling number, though, as custom
ROMs are no longer as popular as they once were. Still, it's a major
setback for leading custom ROM projects, like LineageOS and GrapheneOS.
See other related articles:
Comments from the above link: