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.

  • Ulrich@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    Google is slowly closing access to everything. It’s a boiled frog situation. All the red flags are there. We’re fucked.

    • Tundra@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      keep the faith - we are not fucked, we just need to move to different systems entirely.

    • yeehaw@lemmy.ca
      cake
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      Uhg then what? Samsung’s got too much of their own shit data harvesting crap on top of the Google stuff. All other phones basically have shit cameras. Time to go to iPhone? Seems they’re all the same at this point 😜

        • AmbiguousProps@lemmy.today
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          Graphene is centered around security. I’ve heard bad things about Fairphone in that regard - the Graphene team even talks about them in the replies on that thread.

          • Ulrich@feddit.org
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            2 months ago

            Respectfully to the Graphene team, they say that about literally every other OS.

          • Barbarian@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            arrow-down
            1
            ·
            edit-2
            2 months ago

            Read their comment and I’m left scratching my head. Their role in security with the straight android phone (not the /e/OS version) is simply pushing security patches as/when they get them from the Android team, as they’re using straight Android. Security is handled by Google for Android, not them. When it comes to /e/OS, no idea how good/bad it is, but apparently Graphene has some beef with Murena (the people who make it), at least according to their comment.

            Not at all knowledgable about mobile kernels and drivers to comment on the rest of it. I do know Fairphone 5 uses an unusual CPU normally used for SoC as that was the only CPU that was both good enough to run Android reasonably while simultaneously providing very long-term driver updates (they’re aiming for a minimum of 8 years of updates).

        • 6nk06@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          2 months ago

          The FairPhone is expensive and I’m not sure it can run Android Auto properly. If I can’t run my own OS anymore, Android will be an ugly alternative to the iPhone and I’d have to go back to iOS, it’s absolutely stupid from Google to do this.

          • neo2478@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            Fairphone is not expensive. All the other phone are too cheap due to slave like labor both in the raw materials and production of the phones. Fairphone pays every one along the production chain fairly.