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 are viewing a single comment's thread
view the rest of the comments
[–] 8 points 1 year ago* (3 children)

I really want to give furios phone a shot. It's apparently close to supporting my carrier.

That and a sailfish phone. The community one though didn't support my carrier (think it's mainly EU specced only.)

What I find missing most of the time though is any esim support. Makes me wonder if the hardware one that you can program an esim on works.

  • source
  • parent
  • hideshow 3 child comments