Google has confirmed it isn't discontinuing AOSP, but it's making a change that makes it harder for devs to build Android for Pixel phones.

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.

  • @JasonDJ@lemmy.zipEnglish
    5•6 days ago

    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.