AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Technology
91
Beiträge
64
Kommentatoren
0
Aufrufe
-
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.
one less reason to buy a Pixel, well done Google!
-
-
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 would be sad if Pixel phones were worth buying, instead of being far inferior to midrange Motorola devices in battery life and performance while costing well over twice as much.
-
-
This would be sad if Pixel phones were worth buying, instead of being far inferior to midrange Motorola devices in battery life and performance while costing well over twice as much.
Anything being less open is sad regardless of your opinion of the hardware.
-
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.
Sundar Pichai strikes again!
-
-
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.
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.
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.
-
-
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.
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.
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.
-
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.
AOSP can be fully abandoned and privately forked by Google without it technically being "dead," but that abandonment would effectively kill the project.
-
-
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.
So I bought a pixel device (an old one) for nothing ?
-
-
So I bought a pixel device (an old one) for nothing ?
Google is doing a good job of discouraging some of us from buying Pixel phones. But they don't care because the number of people installing Graphene etc. is relatively very low.
-
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.
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
-
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.
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.
It looks like they were already being "cool" before. Sucks I guess.
While Google is under no obligation to release device trees, provide driver binaries, or share the full kernel commit history (in fact, it’s one of the few device makers to do these things), it has done so for years. The company’s reason for doing so was because the Pixel was treated as a reference platform for AOSP, so developers needed an easy way to build for it.
-
The GrapheneOS team is very aware of their dependence on google. They are planning to either find an OEM for their own line of hardware or a brand whose phones support their requirements other than google. That being said, it will complicate work a lot, but for now it would be to early to jump to that conclusion.
Also, Google couldn't care less if <1% of buyers flash a custom ROM / OS on their phone, this is about tying the android ecosystem closer to google in general. Most other big phone manufacturers know this and are trying to come up with their own solution, like Huawei had to because of the ban when the orange man has been president the first time.
or a brand whose phones support their requirements other than google.
Wasn't Graphene's "selling point" for long being that nothing but Pixels can match their reqs? I don't see why any current band would want to make it easier for them, and I also don't see new brand significantly entering the market.
Graphene boiled themselves in their own frogpan.
-
or a brand whose phones support their requirements other than google.
Wasn't Graphene's "selling point" for long being that nothing but Pixels can match their reqs? I don't see why any current band would want to make it easier for them, and I also don't see new brand significantly entering the market.
Graphene boiled themselves in their own frogpan.
This is not a selling point but rather a unfortunate but comprehensible circumstance. Nexus and later Pixel phones have not been anything more than reference hardware without significant sales until the Pixel 6. Google has been a software company that has greatly benefited by android being an "open" platform you could contribute to and use their services on.
The App / Cloud ecosystem has gained a lot of competitors, so Google is doing their best to reverse this course of action by pulling more and more functionality out of AOSP into Play services and now into Cuttlefish. We can only wait and see how other phone manufacturers react to this.
-
one less reason to buy a Pixel, well done Google!
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.
-
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.
Unrelated: The top bar in this article indicating the article position is so fucking stupid. Guess what the scroll bar on the right hand side is for?
-
-
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.
-
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.
Oneplus gang, how we feelin?
-
-
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.
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.
-
This would be sad if Pixel phones were worth buying, instead of being far inferior to midrange Motorola devices in battery life and performance while costing well over twice as much.
You must be ignoring the Motorola bloat that makes it's performance beyond subpar somehow
-
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.
devil's avocado: this move has saved many people's cherished photos from disappearing by having them auto save. before Google photos I'd run into cases (I used to do home IT support) where people had years of family photos disappear because they didn't back them up properly. Having to communicate what happened was never fun.
is Google photos perfect? No, but it's a great solution for people who don't want to manage their data.
