It's this feature unique to GoS?
I lost my device and had to get a replacement, however on my original I never bothered trying out stock pixel. As I'm trying it my password manager, 1password crashes anytime I try to auto fill but only gives option of app info and force close mo error log

    N3rdTek GrapheneOS adds most of the user-facing crash reporting features that are available in it. Users aren't informed of kernel, system_server or other systems crashes on the stock OS, and they don't have an easy way of getting the error logs.

      GrapheneOS
      Understandable and I get that, but what I'm referring to is when you experience an app that crashes you are presented with three options, app info, force close, and error log.
      I am inquiring if the error log is unique to GOS, since being on stock, I am unable to figure out how to generate any log report for any crash that I experienced

      GrapheneOS Users aren't informed of kernel, system_server or other systems crashes on the stock OS, and they don't have an easy way of getting the error logs.

      What would be the closest equivalent? Be it by a singular or even multiple apps/services to come even in the same ballpark to what GOS error logs provide after a crash?

      I think this is probably my #1 missed and arguably best feature of GOS as it's enabled me to troubleshoot on my own a whole range of issues and there's not been a single developer I've interacted with who requested anything additional other than what GOS Error logs provide.

      As it stands if I have a crash for anything at all for any reason, I just kind of have literally nothing to do to remedy prevent or fix it. I can produce a bug report but that seems so unbelievably generic, it's as though you're casting a fishing net to catch brine