cross-posted from: https://lemmy.world/post/31229844

As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it’s more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.

  • Lazycog@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    2 days ago

    Fair, but is your current phone truly made in your home country?

    Fairphone is arguably doing a lot of good for the consumers and (even if its not perfect) for the environment compared to other phone manufacturers. And most people in my country need a (smart)phone.

    I highly recommend the book “The Book of Hope” from Jane Goodall to truly understand “Don’t let perfect be the enemy of good” when it comes to climate action.

    Edit: added full title of the book

    • voracitude@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      2 days ago

      I run GrapheneOS. Stock Fairphone doesn’t fit my security requirements, but if I can put a hardened OS on it I’d consider it.

      • hash@lemmy.world
        cake
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 days ago

        Yeah. The linked Mastodon thread by GrapheneOS mentions them potentially making a phone themselves. I’d love if they partnered with fairphone to build it. Though it sounds like we’d need to accept a higher price than a standard fairphone.