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.

  • TheGrandNagus@lemmy.worldEnglish
    0·
    3 days ago

    If you want to be a photographer, get a camera.

    🤦‍♀️

    Even professional photographers don’t have their cameras on them at all times, nor are they as convenient for just whipping out and taking a picture within 1.5s.

    Plus, cameras are expensive and they’re another thing to carry around (idk about you but I don’t have infinite pocket space) and they’re another thing to keep charged, whereas you have a phone with you at pretty much all times anyway, because they’re effectively required for modern society.

    You may as well be saying you don’t understand why phones can play music when you can get an MP3 player, that you don’t understand why they play videos because TVs exist, that you don’t understand why they have web browsers and plenty of apps, because PCs exist.

    I stick to my guns and I’m on the internet and computers to learn to educate myself, not to dick around with stupid shit.

    He said, on this Lemmy thread.

    And we have to be weary of open source

    Ah yes, that nefarious Open Source software. Tell me more about the evils of FOSS, Mr Balmer.