574
AOSP isn't dead, but Google just landed a huge blow to custom ROM developers (www.androidauthority.com)
submitted 1 year ago by to c/technology@lemmy.world
98 comments fedilink hide all child comments
 

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
[–] 6 points 1 year ago (4 children)

as a panicked graphene enjoyer, does oneplus measure up as a decent alternative or no?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 10 points 1 year ago* (3 children)

    I use a Oneplus 7 pro and my rom maintainer still updates and I still get a new version once every two months or so. If you want to omit gapps, you are more than free to do so. (Crdroid)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago (2 children)

    You are selling me mr. Fudge. I still need to do a lotta research but you are def sellin me here

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 1 year ago* (1 child)

    The trap: He could stop builds for the OP7... tomorrow with zero warning.

    That leads to my main takeaway for custom roms. Pick the phone with the most topics and replies on XDA. The more popular and liked, the more supported you'll be.

    and never get attached to anything. Your phone miraculously has support, none are guaranteed it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •