SoulKeeper It's up to the clock app in that case, which would need to support direct boot to be able to use part of its functionality while the phone is in BFU state. It's not up to GrapheneOS, but rather the app itself.

As an example of this, GrapheneOS actually contributed direct boot support to Florisboard, which means it can be used to unlock the phone while in BFU state where it otherwise wouldn't.

''prevent adding guest user on lockscreen via adding new users on lockscreen is disabled (UI only appears on large screens such as the Pixel Tablet)''

This one is interesting. Not wanting to offend anyone, it is just an observation. Even if one tries to be as mindful in building secure systems, major flaws will always be present. Keep up the good work.

  • [deleted]

siabadaba Just checking, do you have a pin or pw set? If not, you need to create one before adding your fingerprints. These are a prerequisite to decrypt the profile/device from rest and as a fallback to fingerprints for when they fail.

    Does anybody have performance issues since the last week or so? My Pixel 7 has feels so sluggish out of nowhere. I already rebooted several times. I haven't changed anything substantial on the phone itself. I know this can literally be anything, but perhaps other people share the same issue which could verify my doubts regarding if this is caused by the updates.

      • [deleted]

      • Edited

      aerosola That's most likely not the case. We need to look for issues in your setup. Could you give more information?

      Could you also check which apps or processes use the most of your CPU resources and battery?

      One more thing to check is if your phone is overheating or not.

        [deleted] nothing out of the ordinary. I also observed my RAM is more aggressive than normal with killing background processes. Even just two apps open, will more often than normal kill the other app.

          • [deleted]

          aerosola How many user profiles do you have? Do you have Google Play Services installed?

          aerosola
          There have been recent threads about this issue but I don't think there have been any answers unfortunately.
          Seeing as its been reported to google probably not going be much anyone at gos can do .

            Skyway there really needs to be downgrade option for botched updates. My phone has almost unusable for 2 weeks now (jun 14 update) with launcher crashing all day and no one seems to care or experience it. If gos team cannot fix issues introduced by quarterly patches then those should be optional or downgradable to a different version with just kernel or quarterly rolled back. If i needed my phone in an emergency now i would be screwed becausd the launcher is crashing and i wouldnot be able to bring up app quickly tryibg to work around it while panick emergency. This should have never gone to production. Fingerprint issue too but mainly launcher for me. Launcher crashing all the time broke app switching completely.

            No one even acknowledged my log here and in previous update thread no one had idea lol gosrox

              gosrox Hi there, I'm sorry to hear you've been experiencing launcher crashes. The OS issue tracker on GitHub is the place where you should submit the bug report for the development team to look at: https://github.com/GrapheneOS/os-issue-tracker.

              In the meantime, is using a third-party launcher app a viable temporary workaround for you?

              gosrox

              The launcher crash bug seems to be an upstream AOSP problem, lots here have reported this problem, including me. It happens to me all the time since that recent update.

              Perhaps this can help - when the launcher crashes, I switch profiles, then switch back to he profile where the crash happened, and the launcher bug is gone (for now). It's obviously not a fix for the problem but it's been an acceptable workaround for me.

              hello
              I have a pixel 7 and since this release (2023062300) i have problem with location services with an app.
              It is a public transportation app with gps tracking for billing. (com.fairtiq.android, 7.0.1)
              I use grapheneos location services without wifi and bluethoot scanning and it worked. Since this release, the app stopped working, becaus it needs "high accuracy location". normal location access works, I see it in the permission log.
              I tried activation of wifi and bluethoot scanning, and also location acces for sandboxed google play. nothing worked.

              Has this something to do with following change: "ignore non-system packages for location indicator exemptions, getLocationBypassPackages(), Qualified Network Services, telephony data services, device provisioning and wlan/wwan wireless network services"?

              What can i try to get this app working? Tried app downgrade. All other gps app like maps and routing works...

              thanks

                • [deleted]

                Sounds to me like GPS is required. If so, when the location setting kicks in, set it to precise location. I had an issue yesterday with my smart watch, once the location was set, Bluetooth found the watch immediately.

                Skyway What fixed it for me was to go cold turkey. Turned phone off, and let it off for 20 minutes and then boot again instead of reboot or instant boot after shutdown.

                I don´t know what changed in this release that has this impact, but PayPal started finally to show notifications :)