I imagine this will be disabled in the EU, but it’s a concern nonetheless.

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

        Probably makes sense. They don’t want to be responsible for your phone exploding.

    • nesc@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      5
      ·
      2 days ago

      There were news recently that there won’t be grapheneos for newer models.

      • cron@feddit.org
        link
        fedilink
        English
        arrow-up
        8
        ·
        2 days ago

        Do you have a definitive source for this? All I found was speculation.

        • sunzu2@thebrainbin.org
          link
          fedilink
          arrow-up
          7
          ·
          2 days ago

          GrapheneOS team has extra work cut out for them but nothing that they can’t over come.

          But this is the beginning of the end IMHO

          Over next few years Sundar the creep will ensure they are ml viable

            • sunzu2@thebrainbin.org
              link
              fedilink
              arrow-up
              7
              ·
              2 days ago

              Android is open source but Google is starting to move certain things behind closed doors.

              This year they decide to no long provide “device trees” for pixel phones… Ie GrapheneOS will need to recerwse engineer android for each pixel devices where before this was provided.

              Extra work, hard work but it is doable.

    • frongt@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      4
      ·
      2 days ago

      Sure, in the same way that the fix for a smoke alarm going off is taking out the battery.