• pHr34kY@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    6 hours ago

    Google has already started killing GrapheneOS by removing device trees from AOSP releases. Android 16 works fine, but for how long?

    I would imagine the first thing any custom ROM would do is bypass Google’s app restrictions.

    I wouldn’t be surprised if in 3 years I would need to pass hardware attestation to install a calculator app from the Play store.

    • tranquil_cassowary@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      GrapheneOS still intends to support all the supported devices until EOL. The sideloading change doesn’t affect them. It won’t apply to GrapheneOS. It only applies to certified OSes and GrapheneOS is not certified because it doesn’t license Google Mobile Services. As per the rip out of the device trees for Pixels, that just makes Pixels like other phones. GrapheneOS has been able to expand it’s automation to build that device support themselves. For new devices, making the support will take longer than it did in the past though, but they will still support those Pixels, as long as they meet the hardware requirements and still allow third-party OS support with all security features intact. Besides that GrapheneOS is actively talking with a major Android OEM right now in order to help them reach the security requirements for a subset of their future devices. They are very optimistic about tha