• Sonalder@lemmy.ml
      link
      fedilink
      arrow-up
      7
      ·
      2 days ago

      That is a misleading claim right here, don’t blindly trust everything you read online. The core team of the project explained it very well why it’s not as dramatic as people made it seems too. It’s not an ideal position and Google is definitely going in a direction that doesn’t not benefit AOSP but no Android16 is comming to GrapheneOS and future version also should.

          • FooBarrington@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            2 days ago

            Did they explicitly say anywhere that future versions should be coming as well? I only see them mentioning Android 16, and devices still being “supported”, but that could also mean improvements in Android 16.

            • Sonalder@lemmy.ml
              link
              fedilink
              arrow-up
              3
              ·
              2 days ago

              GrapheneOS will continue supporting the current devices we support until their end-of-life dates. We’ll also add support for new Pixels as long as they meet our requirements. We’ve tried to make that clear, but recent posts about changes to AOSP have been widely misrepresented. Prior to Android 16, Pixels had first class support in the Android Open Source Project as the official reference devices. This was never one of our requirements and no other device provides it.

              From my understanding yes but maybe not in this thread

      • Sonalder@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        These projects suffer from the same issues with how Google share new Android versions. This is not a solution. Also if you have a Pixel I would personnaly use a secure locked bootloader OS rather than an unsecure unlocked bootloader. I tend to privilege /e/OS on Fairphone and LineageOS on phone that have already dropped support.