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 ?

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.

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.

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.

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

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.

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.

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.

Oneplus gang, how we feelin?

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.

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.

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.

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.

You must be ignoring the Motorola bloat that makes it's performance beyond subpar somehow

Now more than ever we need more work on PostmarketOS, Mobian, Gnome Mobile etc...

Bummer that it's still so hard to find a somewhat modern, affordable phone that is Linux compatible