APP Log Analytics

1. First check whether the device is connected successfully via ADB devices

2. Crawl logs via adb logcat command

The Logcat log file-android log provides the ability to record and view system debug information, which is recorded from various software and buffer zones of some systems, and buffers can be viewed through Logcat and used

The Logcat has a large output and defines 4 log buffers:

Radio: Log of the output communication system

System: Log of the output system component

Events: Log of output events

Main: All Java Tiers (default)

Switch log output Adb logcat-b Radio Select the output of the radio buffer

3.ADB logcat-v Time (-V times in order to get log hours)

4. Log Analysis:

The log can be filtered by the package name.

Run the program in the foreground, view the app package name by command: adb shell Dumpsys | Findstr "Mfocusedactivity"

5. Crash problem occurred, search keyword Force finishing (look up the log: FATAL Exception-force finish)

6.ANR (Application not responding) application is unresponsive, and the system will pop up an unresponsive dialog box when the application is unable to process for a period of time.

Search data from top to bottom with ANR in filter data

ANR needs to commit the log file : Logcat (after use from ANR in +cpu) +trace.txt (last ANR information saved)

7. Multiple ANR: Direct the DATA_APP_ANR under Dropbox to the developer

Collect exception information (including ANR) over a period of time via Dropbox

/data/system/dropbox

Data_app is a third-party app

8.APP exception occurred

L First determine if it is a crash or a non-responsive ANR (based on the dialog box)

L ADB logcat Crawl log file If it is ANR take Dropbox under the Data_app_anr

L REPRODUCE the scene recurrence step to reproduce the environment

APP Log Analytics