Tripartite problem analysis summary

I would question the three parties into the following categories:
1, Crash problem
such issues are often described as "flash back" may be the interface flash back, it could be the entire application flash back. This question we search keywords directly from the bugreport to "am_crash" and "Fatal" critical information can be found error message.
Crash Crash is also divided into upper and Native Crash.
Crash upper layer generally can be directly found in the java exception stack corresponding to a root cause abnormal; Native crash down can generally only be found in the native exception stack which is so abnormal library, following FIG.

2, ANR question:
ANR problem often described as "Application not responding", "application stuck", "Application stuck" and so on. For such problems, we can search from bugreport in "am_anr", "ANR IN" to quickly locate the cause of the ANR.
ANR appears common causes are:
Input event processing timeout (5S)
Service lifecycle process timeout (20S / 200S)
l broadcast reception process timeout (10s / 60s)
ContentProvider process timeout (20s)

if further analysis is required crawl trace information under data / trace, analyze main processes specific occurrence of the call stack waiting to find out the cause of the timeout.
3, system adaptation problems
adapting problem mainly refers to the UI display adapter and adapted version of Android.
UI adaptation problems common to notch screen is not fit, round screen is not fit, does not fit the full screen and other issues; issues of common systems adapted for permission abnormal, android is not adapted to the new features, customized property reading take abnormalities.
For such problems,