On the ANR, Application Not Responding, summary page for Android applications, there are multiple different terms. 

Here is how we define these terms in Embrace, starting from the top of the page.

  • ANR Summary; in Embrace, an ANR begins when the main thread is blocked for > 1 second
  • ANR Duration; how long the ANR lasted
  • ANR Interval; similar to ANR duration, the activity between the start and end time of an ANR
    • Within ANR intervals, we "sample", meaning that we start taking rapid snapshots of data when the ANR starts because we don't know what'll happen with the ANR. For example, will it recover?, how long will it be before it ends?, etc. 
  • ANR sample: tied to the "first sample", "ad-focused sample", and the "most representative sample" group by filters at the top of the page. 
    • First sample; the first piece of information collected when the ANR initially occurred. We typically find that grouping by the first sample provides the most helpful clues for debugging as it is the sample closest to the original source of the ANR.
    • Ad-focused sample; when selected, we analyze all the samples and use the one that occurs most frequently and also contains at least one frame with an ad SDK in the stack trace
    • Most representative sample; when selected, we analyze all the samples and use the one that occurs most frequently.
  • ANR-Free Sessions; sessions that do not contain an ANR
  • ANR-Free Users; users that do not experience an ANR during the time period selected
  • ANR Exit Percent - Calculates the percentage of sessions with an ANR exit.
  • ANR Exit User Percent - Calculates the ANR exit percentage per user.
  • ANR Session Percent - Calculates the percentage of sessions with ANR occurrences.
  • ANR User Percent - Calculates the percentage of users with ANR occurrences.


To learn more about ANRs and how to minimize work on the main thread, check out this article.