Hi, the following is the guide on local collection log operation, hope it is helpful.
1 Logs of the Terminal
EP682 logs are divided into AP logs, CP logs, TAPP logs, and special logs. The AP log refers to the application processor and the logs of the upper application, including the Android operating system, the SMS process, the voice process, and the process log of the soft video process. The CP log refers to the logs of the LTE processor and the upper-layer application, including the black box of the LTE module, the signaling process, and the status information. The TAPP log is a log of the AP side TAPP. The special log refers to several modes of the CP log, including the normal offline mode, the beta offline mode, and the online mode.
2 Local collection log operation guide
EP682 engineering model integrates a "one click log access" feature, you can extract AP, CP, TAPP log, the use of the following methods:
(1). input *#*#386#*#* at the dial interface, enter the engineering mode interface (note:enter the contact application,bring up the menu after press the middle button then dialer is visible; If there is no dialer, please press left soft key and middle key at the same time to display the dialer).
(2). select 1.LOG.
(3). Select "1. One-click log acquisition".
A progress bar and progress prompt will appear, showing the log currently being acquired. No other operations can be performed during this time. The "OK" button is grayed out and cannot be clicked.
After the success is obtained, there will be a prompt to “get a one-click log success”. Click the “OK” button and the log file will be saved in the /sdcard/onekeylog of the terminal.
Three files are generated in the directory, namely AP log (ap_log.7z), CP log (cp_log.7z), and TAPP log (tapp.7z). This file can be extracted to a PC using adb pull or MTP.
- adb pull method operation method (if device not found, you need to open the developer option switch and USB debugging in Settings -> Developer Options, if there is no developer option, you need to set the number -> about the phone, press the version number seven times )
i. The terminal uses a usb cable to connect to the computer;
ii. Install the terminal driver and adb tool (if not, please contact the maintenance staff);
iii. Enter adb pull /sdcard/onekeylog onekeylog/ at the command line (the operator specifies the path);
iv. After waiting for the command to complete, the log is in onekeylog/ (the operator specifies the path).
- MTP method operation method
i. The terminal uses a usb cable to connect to the computer;
ii. Select "Charge only" in the notification and enter the connection mode as "Device File Management (MTP)". If you do not have this option, please contact the administrator to open this permission.
iii. After selecting "Device File Management (MTP)", a portable device will appear on the PC on the PC. In the portable device, there will be a terminal (EP682), enter the terminal (EP682) -> internal storage (if the default storage location is changed to sdcard) , here is the SD card);
iv. Copy the onekeylog directory.
4. AP log Settings, open the log switch can grab the app, KMSG, ril, charging, dormancy and cshell log. AP private network log screen can be set for the AP log level.
NOTE
The following table lists all AP logs. The directory /data/android_logs is mandatory, and other directories are optional.
| Directory | Function |
| "/data/ anr " | Saves ANR logs. If the system has not experienced ANR errors, the directory will not be created. |
| "/data/android_logs" | Saves routine logs, including applog (application logs), rillog (protocol logs), kmsglog (kernel logs), charglog (charge logs), and wakeuplog (sleep logs) |
| "/data/rdr" | Saves the dying gasp. If the system restarts unexpectedly, the dying gasp stores the status information. |
| "/data/dontpanic" | Saves kernel panic logs. The directory saves the information when kernel panic occurs. |
| "/data/system/dropbox" | Saves the following logs. |
| Watchdog Logs | Exception information and other key information in the system when the watchdog restarts. |
| Java Crash logs | Logs recorded when Java program error occurs. |
| SystemServer Crash | Logs recorded when the Java program error information on the SystemServer. |
| WTF | Logs recorded when major errors occur in the application layer or the framework. |
| Lowmem | Logs recorded when the low memory error occurs in the system. |
| Strictmode | Logs recorded when exceptions occur due to unexpected network or file operations executed in the main thread. |
| "/data/recovery" | Records recovery logs, including operation logs during system upgrade and recovery. |
| "/data/hwzd_logs/cp_log/" | Records the modem logs of the public network. |
| "/data/ap-log/" | Records the logs of new modules added by Huawei. |
| "/data/cp-log" | Records the balong modem logs of the public network. |
| "/data/hifi-log/" | Records the HIFI logs on the modem side of the public network. |
| "/data/klog/" | Records logs about the kernel information. |
| "/data/memorydump/" | Saves the memory dump image file. |
| "/data/modemlog/" | Records the modem logs of a third party on the public network. |
| "/data/anr/" | Records log information when the application does not respond. |
| "/data/hisi_logs" | Records HiSilicon logs, including the DDR ram dump information. |
| "/data/dumplog" | Records the dump system information. |
| "/data/tombstones" | Records the call stack information of the Native program when kernel panic occurs. |
| "/data/MMI_Logs" | Record the result logs during the MMI (factory test) operation. |
Thanks!
