Titan_M2 The release notes have been clarified:

add default-enabled toggle for automatic per-app exploit protection compatibility mode configuration

    • [deleted]

    • Edited

    Neoniq That entirely depends on if anything is discovered during the Alpha release that needs fixing and much time is needed to do so. Releases are tested by the developers and are then pushed out via the Alpha channel. The release is then pushed out via the Beta channel shortly afterwards. Finally, the release is then pushed out via the Stable channel after being tested by some users using the Beta channel.

    https://grapheneos.org/releases#about-the-releases

    Is it available on the stable channel already (I mean 2023100800) ? I can't follow your description entirely...

      GrapheneOS
      You have worked months to release the 14 version and now the saturday and sunday. Thank you for your engagement !

      • [deleted]

      androidin Read my response that's right before yours.

      Titan_M2 No, that toggle only applies to apps known to have memory corruption issues which are explicitly controlled by the toggle in code. Currently, it only applies to Google Camera as far as I know.

      Perhaps the toggle on the actual OS in Settings > Security might help to better understand how it works:

      "Allow automatically enabling "Exploit protection compatibility mode" for apps that are known to need it"

      I want to share that, compared to previous updates, apps optimisation after reboot is very very slow (is it normal?). Make sure you got plenty of battery before the update

      • v6ak replied to this.

        Pixel 6a
        UP1A.231005.007.2023100800

        Smooth sailing so far, no problems. Big thanks the the devs!

        willie_non Same experience with Pixel 6a. I think there is some subtle bug in GrapheneOS. In modern Android versions, the app optimization can happen before reboot, which reduces the downtime. For some unknown reason, on GrapheneOS, some apps need to be optimized (recompiled) after reboot. In my experience, it usually affects few apps, so it takes several minutes. With this release, it looks like all apps needed the optimisation during reboot, so it took much more time.

        tuxsudo

        I am also having issues with my work profile (on alpha 2023100800). Apps are not opening and a pop up says blocked by your IT Admin.

        I only use a work profile (shelter) for certain audio apps (Audible, Spotify, Apple Music) that I want isolated but I also want them to play in the background while I use my owner profile.

        Otherwise I use user profiles as they are better in every other way.

        So yea it might be from attempting to keep the behavior from android 13 work profile where you can actually stop apps, not just pause them. (Which I think is a really great feature to keep and hope it can stay).

        If the work profile is corrupted, it's not the end of the world for me as I don't, and wouldn't, keep anything sensitive there. Hopefully it can be fixed without data loss but no biggie really.

        Apart from that, not noticed any glaringly obvious issue so far with the android 14 alpha :)

          muhomorr

          No, I didn't actually use the initial experimental release of android 14. I went straight from 2023100300. I switched from stable channel to alpha to get 2023100800

          (I knew there could be a few bugs but was happy to try it out)

          By the way, current build is UP1A.231005.007.2023100800 on Pixel 6a :)