TL;DR
-
Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release.
-
The company says this is because it’s shifting its AOSP reference target from Pixel hardware to a virtual device called “Cuttlefish” to be more neutral.
-
While Google insists AOSP isn’t going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult.
This actually probably make sense, but they could still be cool and have pixel drivers be open source in a different repo if that was the only reason.
Yeah, just that this has shit to do with the stated reasons. Google hasn’t been an open source ally for quite some time now
Yup, the entire culture of Google has nearly changed. It used to be coder- and innovation-driven, and open-source was a natural thing to support. Make more money by growing the pie, creating markets with new tech.
Now it seems it’s middle managers and MBAs calling the shots, and their strategy is generic business zero-sum mindset - lock down, restrict, extract. They still see the PR value in open-source, but that’s it.
Just becoming 1990s Microsoft or 1980s IBM.
Just another example of enshittification from a publicly traded company. Nothing really new here.
Do you think it may be related to the monopoly issues they are currently facing?
Quite possibly, the GrapheneOS team seems to think so:
https://grapheneos.social/@GrapheneOS/114665449554083676
https://grapheneos.social/@GrapheneOS/114665441933500613
Would be great indeed, but “more neutral” in this case seems to mean vendor agnostic by abstracting the hardware away and have anything run on a closed source google container.
deleted by creator