[deleted] hmmm. I'm not sure what can be done then. Ultimately I was hoping to get some sort of useful crash log but they're all the same, including the one I caused on my phone.

I had the same result after the initial ANR popup. I could open another permission, one that had very few entries, and still get the popup. Not sure why that would happen, though.

You can try opening an issue in the OS issue tracker but I don't think they'll be able to do much about it since the logs aren't very helpful and it is likely an upstream bug.

16 days later
  • [deleted]

UP1A.231105.003.2023112900

type: ANR
osVersion: google/panther/panther:14/UP1A.231105.003/2023112900:user/release-keys
package: com.android.permissioncontroller:330000000
process: com.android.permissioncontroller

activity: com.android.permissioncontroller/.permission.ui.ManagePermissionsActivity
cause: ANR Input dispatching timed out (d9cb2cb com.android.permissioncontroller/com.android.permissioncontroller.permission.ui.ManagePermissionsActivity (server) is not responding. Waited 5003ms for FocusEvent(hasFocus=true))
info: ANR in com.android.permissioncontroller (com.android.permissioncontroller/.permission.ui.ManagePermissionsActivity)
PID: 25597
Reason: Input dispatching timed out (d9cb2cb com.android.permissioncontroller/com.android.permissioncontroller.permission.ui.ManagePermissionsActivity (server) is not responding. Waited 5003ms for FocusEvent(hasFocus=true))
Parent: com.android.permissioncontroller/.permission.ui.ManagePermissionsActivity
ErrorId: 9611356b-51d1-440d-9ca2-fc35876bf123
Frozen: false
Load: 3.12 / 2.89 / 2.72
----- Output from /proc/pressure/memory -----
some avg10=0.23 avg60=0.59 avg300=0.32 total=514689527
full avg10=0.19 avg60=0.45 avg300=0.23 total=342661954
----- End output from /proc/pressure/memory -----
----- Output from /proc/pressure/cpu -----
some avg10=13.02 avg60=9.78 avg300=7.62 total=16787525139
----- End output from /proc/pressure/cpu -----
----- Output from /proc/pressure/io -----
some avg10=0.04 avg60=0.16 avg300=0.12 total=712758588
full avg10=0.00 avg60=0.06 avg300=0.05 total=448909942
----- End output from /proc/pressure/io -----

CPU usage from 1697ms to -3959ms ago (2023-12-06 21:33:14.997 to 2023-12-06 21:33:20.653):
  96% 2412/system_server: 50% user + 46% kernel / faults: 31894 minor 78 major
  70% 25597/com.android.permissioncontroller: 37% user + 33% kernel / faults: 6505 minor 22 major
  22% 576/surfaceflinger: 15% user + 7.6% kernel / faults: 4425 minor
  8.8% 3679/net.ivpn.client: 4.2% user + 4.6% kernel / faults: 10227 minor 5155 major
  7.7% 1146/media.swcodec: 3% user + 4.7% kernel / faults: 12097 minor
  7.4% 2664/com.android.systemui: 3.7% user + 3.7% kernel / faults: 16916 minor 6 major
  5.1% 93/kswapd0: 0% user + 5.1% kernel
  5.1% 584/android.hardware.composer.hwc3-service.pixel: 2.8% user + 2.2% kernel
  4.5% 1057/media.extractor: 1.5% user + 3% kernel / faults: 6180 minor
  4% 26226/com.google.android.inputmethod.latin: 2.1% user + 1.9% kernel / faults: 9759 minor 2 major
33% TOTAL: 15% user + 17% kernel + 0% iowait + 0.7% irq + 0.2% softirq
CPU usage from 16ms to 688ms later (2023-12-06 21:33:16.710 to 2023-12-06 21:33:17.381):
  214% 2412/system_server: 104% user + 109% kernel / faults: 16914 minor 55 major
    96% 2417/Signal Catcher: 54% user + 41% kernel
    44% 30914/AnrAuxiliaryTas: 10% user + 33% kernel
    36% 8434/binder:2412_15: 23% user + 13% kernel
    20% 3220/binder:2412_7: 7.8% user + 13% kernel
    13% 19674/binder:2412_20: 5.2% user + 7.8% kernel
  85% 25597/com.android.permissioncontroller: 37% user + 47% kernel / faults: 81 minor
    47% 25597/ssioncontroller: 13% user + 34% kernel
    27% 25908/RenderThread: 20% user + 6.8% kernel
    3.4% 25929/binder:25597_3: 3.4% user + 0% kernel
    3.4% 30831/mali-event-hand: 0% user + 3.4% kernel
  27% 576/surfaceflinger: 17% user + 10% kernel
    12% 576/surfaceflinger: 12% user + 0% kernel
    6.3% 2462/binder:576_5: 4.2% user + 2.1% kernel
    2.1% 672/TimerDispatch: 0% user + 2.1% kernel
    2.1% 676/app: 0% user + 2.1% kernel
    2.1% 678/RegionSampling: 0% user + 2.1% kernel
    2.1% 696/surfaceflinger: 0% user + 2.1% kernel
  8.5% 584/android.hardware.composer.hwc3-service.pixel: 4.2% user + 4.2% kernel
    6.4% 670/binder:584_4: 2.1% user + 4.2% kernel
  1.4% 12/rcu_preempt: 0% user + 1.4% kernel
  1.4% 49/rcuog/4: 0% user + 1.4% kernel
  1.5% 71/rcuop/7: 0% user + 1.5% kernel
  1.5% 335/decon0_kthread: 0% user + 1.5% kernel
  2% 525/sugov:0: 0% user + 2% kernel
  2.1% 669/mali_kbase_csf_: 0% user + 2.1% kernel
  2.3% 947/android.hardware.sensors-service.multihal: 0% user + 2.3% kernel
  3% 3679/net.ivpn.client: 3% user + 0% kernel
40% TOTAL: 20% user + 18% kernel + 0.9% irq + 0.3% softirq

    [deleted] 2023112900

    This would be the release on November 29th. You'll want to update to the most recent release. Right now, December 4th's is the most recent release in the stable channel.

    There's one that was announced today, but not even in the alpha channel yet. Hopefully one of these two releases fixes this issue.

      [deleted] okay. Still very strange since you're the only person that I've seen on here who has had this kind of ANR consistently.

      At this point I'm not sure what kind of suggestion I can give other than to either wait for an update to fix the issue, to just not use the privacy dashboard or ignore the crashes, or submit a bug report to the OS issue tracker. I'd expect a developer can give better advice than I have given.

      If you do decide to submit a report, then I'd suggest including a link to this thread so they can see what you've tried and all that.

        • [deleted]

        other8026
        Thanks for your kind answer
        Please note that during this discussion, I have rested my phone and the issue still happens. Update today.

        other8026 I also get this in the exact same way as OP. I've never bothered reporting it cuz I don't check the usage that often I know exactly what's in use, but every now and then I'll do a double check and I experience this every single time

          N3rdTek I can make it happen as well, but I need to scroll through lots of stuff to make it pop up. Just a guess here, but I'm thinking there's something about your and ZorroisonGOS1's history that's making it hang much faster than on my phone.

          It's likely an upstream issue, but since there doesn't seem to be a way to fix it, maybe it's best if you can get the log and open an issue on GitHub in the GrapheneOS Issue Tracker: https://github.com/GrapheneOS/os-issue-tracker/issues and they can track the issue there. You can link this post if you'd like so they can see the other logs and anything else they might find useful in this thread.

            11 days later

            other8026
            I'll try to trigger it and send what logs get generated.
            Also as a correction, I wouldn't say it triggers immediately, it's funny you say after some scrolling, iirc mine is also due to scrolling but I don't recall is it's fast scrolling or scrolling in general

              • [deleted]

              N3rdTek

              Now it appears both right away and when I scroll

              4 months later

              trefdcsaxyaewrgtvef Because it doesn't happen for everyone.

              What's happening is that we enable showing way more than stock OS, and depending on how many apps one has, it can hang. We are aware and may adjust what that screen shows in order to reduce noise and prevent it from crashing in cases like yours.