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.
kami@lemmy.dbzer0.com 3 weeks ago
one less reason to buy a Pixel, well done Google!
metaphortune@lemmy.world 3 weeks ago
I don’t have any actual research, but I wouldn’t be surprised if the Pixel itself doesn’t really make money at all. One of those “get people hardcore into the Google ecosystem to get their money/data” things.
ocassionallyaduck@lemmy.world 3 weeks ago
The absolutely criminal dark patterns that they pull on people via Google photos auto backup is insane.
Just in my own orbit 2 of my friends wives, my parents, and my in-laws all wound up paying Google because they thought they had to or lose all their photos. We helped most of them disconnect the autobackup (that they didn’t even know was activated) and move it to offline safely. But that was the most downright evil shit Google has ever done and literally a fire in me for manipulating the elderly and less tech savvy so blatantly.
cryptix@discuss.tchncs.de 3 weeks ago
How badly would this affect graphine os?