Some features iOS has that would be nice to see on GOS/AOSP:

  • paste permission
  • local network permission
  • ability to lock any app with biometrics
  • built-in E2EE backups
  • remove the wallpaper fingerprinting thing

I know some of these are planned I just wanted to put it all in one place so I can check them off as they get implemented. Lemme know if y’all can think of anything else

  1. https://github.com/GrapheneOS/os-issue-tracker/issues/2917
  2. https://github.com/GrapheneOS/os-issue-tracker/issues/4064
  3. No relevant issue (Will probably need to be added upstream to make it's way to GrapheneOS).
  4. No relevant issue (Though it is well known that Seedvault will be replaced. See A and B).
  5. https://github.com/GrapheneOS/os-issue-tracker/issues/1495

Personally, I would add factory reset protection to the list. The developers are hesitant to implement such a feature, which could result in users bricking their devices. However, I think that with the duress password feature, it would be a nice assurance that even after your phone has been reset, only you can use it and could conveniently verify ownership that way.

Upstate1618 wow that’s crazy, seems like there’s work to do on minimizing fingerprinting potential.

    fria Yup, it's insane.

    I think this needs to be a thing AOSP tackles rather than the GOS devs.

    Google, for example, have already started blocking apps from reading the values of some user-facing settings by restricting the settings behind private APIs. Additionally, In older API levels, apps used to be able to create unique string that persists after uninstallation and store it in external storage for fingerprinting. This has (mostly) been remedied already by Google with more modern API levels.

    It makes sense that the team has not started implementing many anti-fingerprinting measures as there are just too many known and unknown aspects. Fixing a small subset of them does not change the ability of the apps to fingerprint. It would make more sense for the GOS team to implement enhancements such such as making the Android ID per-app per-profile rather than just per-profile instead of tackling the entire fingerprinting issue.

    Overall, I don't think this is an issue that can easily be tackled by the GOS team alone. AOSP is a constantly changing environment so any changes the team makes can become a maintenance burden and AOSP can implement the same functionality later on anyway making the work the GOS team made redundant. As we have seen before as well, Google is already taking steps towards an anti-fingerprinting approach. I think the solution for this problem will just be to wait it out and see what Google does.

      duck1 enhancements such such as making the Android ID per-app per-profile rather than just per-profile

      This is close to how Android ID is already. Its per app signing certificate per profile. To have the same signing cert more or less apps would need to be from the same developer. In many cases a developer will use a different signing cert for each of their apps.

      Been that way in AOSP for some years now.

        Carlos-Anso Ah I see. What I meant was to prevent an app with the same signing cert in the same profile having the same Android ID after reinstallation then.