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
[–] 5 points 1 year ago* (1 child)

Idk man.

I love my OP12. But we're switching carriers to a Verizon MVNO which "won't work" with my OP12, so I bought a Pixel 8 Pro on sale last week and need to switch over.

I'm starting to wonder if that "it won't work" is bullshit tho...I've got a Verizon SIM in slot 2 and it works fine. Maybe I'd be missing out on 5G speeds? I got 5 bars on my tmo sim and my vz sim...but my Tmo got 1.1Gbps down, and my Vz sim only got 70Mbps.

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