Graphene OS has had just about enough of Google not doing more to make Android compatible with custom ROM projects.

TL;DR

  • Efforts like Graphene OS face increasing pressure from apps that refuse to run on non-standard Android.
  • The custom ROM project characterizes Google’s approach to device attestation as incomplete and flawed.
  • Graphene OS is prepared to take legal action if Google won’t let it pass Play Integrity checks.
  • conciselyverbose@sh.itjust.worksEnglish
    2·
    3 months ago

    The point is that you have to emulate a fuckton of low level access to even have a chance of anything working. Either you replace the actual hardware access with junk data, making none of the apps work, or you break the whole permissions structure, and your security is completely gone.

    All of those APIs were deprecated because it’s impossible to provide them in any way that resembles security.

    • gh0stcassette@lemmy.blahaj.zoneEnglish
      1·
      3 months ago

      I mean, as long as it’s in a pretty robust sandbox and it’s either firewalled or has no network access (if possible for the app in question), I would think security implications are minimal. Like, even if the version of Android inside the container is compromised, the app could only take over its own container, which is non-privileged and doesn’t have access to anything you didn’t explicitly give it (in terms of user data).

      • conciselyverbose@sh.itjust.worksEnglish
        1·
        3 months ago

        But almost every app is going to crash because they’re built on needing the information those APIs return.

        His example of not being able to control some wireless speaker? Supporting that app is going to be a mess, best case.

        • gh0stcassette@lemmy.blahaj.zoneEnglish
          1·
          3 months ago

          You’d need some sort of translation layer to allow older versions of the Android userland drivers in the container to talk to the modern Android userspace drivers. Or you could write new userspace drivers inside the container that interact directly with the hardware, but this would likely be expensive and insecure. Definitely doable tho, especially for a company as large as Google.

          Especially on Pixels, with the generic system image feature (allows for booting generic, non-device-specific android images), if the container is built with the same userland drivers as a generic system image, it might not even need any special effort/attention to run, though iirc GSIs are pretty recent, so you wouldn’t be able to run software for anything before like, Android 12 or 13 probably.