You can check whether the information in/proc/kmsg is related to the system log. Why is it handled like this? The size of the circular buffer is limited and the kernel may write to it at any time, so this is normal. After each read, the contents of the circular buffer are considered to have been processed (that is, become invalid content), so you read it again It is normal to be empty. Every time you read a file, kmsg is actually a circular buffer inside the kernel. The tool dmesg or the daemon klogd is usually used to retrieve these messages. You can also use the system call syslog to retrieve these messages. Only one process with super user rights can read this file at any time. For example, adb shell dumpsys meminfo system is to view the memory information of the system process.Īdb shell cat/proc/kmsg> kmsg.txt, check the msm_kgsl field after openingĭescription: Used to retrieve kernel messages generated by printk. O adb shell dumpsys is about the system service. O dumpstate is the system state information, which is relatively complete, including the current memory information of the phone, cpu information, logcat cache, kernel cache, and so on. It contains dmesg, dumpstate and dumpsys. O bugreport (command adb bugreport>bugreport.log). (For QXDM LOG capture method, please refer to the basic instructions and functions of QPST and QXDM) This is not much to talk about, the content is rich, radio frequency, telephone, Internet.Any solution provided by Qualcomm, this can be caught.

Of course, it is not necessary to mention it if it is not a Qualcomm chip. Tcpdump is very useful, you can use this to capture all TCP/IP protocol related, adb shell tcpdump -s 10000 -w/sdcard/capture.pcap, such as capture the UA profile when downloading mms, and when the browser is online, Use proxy's APN download, streaming related content includes UA profile, etc.įinally, QXDM of the Qualcomm platform, whether it is Android or not, as long as you use a Qualcomm chip, you will be familiar with it.

Qxdm online course