1.Logcat logs(main, events, radio) 
2.Dmesg/kernel logs 
3.bugreport and “dumpstate" log 
adb shell bugreport > bugreport.txt 
adb shell dumpstate > dumpstate.log 
(this command will produce trace log about all process then u need adb pull /data/anr to collect the trace log) adb pull /d/binder/ . 
4.Trace file /data/anr 
5.adb pull /data/tombstones 
(All log file time must be consistent with issue occurred time, it needs to clear /data/anr & /data/tombstones after stability issue occur) 

1.Logcat logs 
2.Kernel logs: “ adb shell getevent” 实时事件log
open echo w > /proc/sysrq-trigger when capture dmesg and bugreport log as follows: 
adb root 
adb remount 
adb shell 
echo w > /proc/sysrq-trigger 
& then exit adb shell, then collect bugreport 
adb shell bugreport > bugreport.txt 
adb shell kmesg > kmesg.txt 没有kmesg
3.Key events log 
adb shell getevent -rtl /dev/input/event0 按键事件
4.bugreport and “dumpstate " log: 
adb shell bugreport > bugreport.txt 
adb shell dumpstate > dumpstate.log 
adb pull /d/binder/ . 
5.Dumpsys window log: 
adb shell dumpsys window > dump_window.txt 
6.Meminfo log: 
adb shell cat proc/meminfo > meminfo.txt 
7.Procrank log: 
adb shell procrank > procrank.txt 
8.Top log: 
adb shell top > top.txt 
9. Add below information: 
•Adb workable or not, ANR or not 
•CTP workable or not ->
 touch screen and observe 
the output of "adb shell getevent". 
•Display driver workable or not -> 
Use the screencast to see 
if the screen can be displayed 
•Power key/volume key work or not? 
Menu/back/home key work or not? 
10. It's better to trigger a ram dump 
Before test: 
adb root 
adb shell "echo 0x843 > /d/spmi/spmi-0/address" 
adb shell "echo 0x80 > /d/spmi/spmi-0/data" 
Then long press power key more than 10~30s 
could trigger a dump. 
If device is rebooted, it needs to set again. 

Main, events, radio, bugreport, sumpstate, Procrank, 
meminfo, top log 
1.Logcat logs(main, events, system, radio) 
2.Kernel logs 
3.bugreport and “dumpstate " log 
adb shell bugreport > bugreport.txt 
adb shell dumpstate > dumpstate.log 
then capture traces log : 
adb pull /data/anr , after about I min ,
 clear /data/anr and capture traces log once again 
adb pull /d/binder/ . 
5.Meminfo log: 
adb shell cat proc/meminfo >meminfo.txt 
6.Procrank log: 
adb shell procrank >procrank.txt 
7.Top log: 
adb shell top >top.txt 
4.Add below information: 
•Adb workable or not, ANR or not 
•CTP workable or not
 -> touch screen and observe the output of
 "adb shell getevent". 
•Display driver workable or not
 -> Use the screencast to see
 if the screen can be displayed 
•Power key/volume key work or not? 
Menu/back/home key work or not? 
5.It's better to trigger a ram dump 
Before test: 
adb root 
adb shell "echo 0x843 > /d/spmi/spmi-0/address" 
adb shell "echo 0x80 > /d/spmi/spmi-0/data" 
Then long press power key more than 10~30s
could trigger a dump. 
If device is rebooted, it needs to set again. 

1.Logcat logs(main, events, radio) 
2.Dmesg/kernel logs 
3.Trace file /data/anr 
4.adb pull /data/tombstones 
All log file time must be consistent 
with issue occurred time, it needs to clear /data/anr &

Wu_Being博客声明：本人博客欢迎转载，请标明博客原文和原链接！谢谢！
《Android系统各种稳定性问题所需要的log》： http://blog.csdn.net/u014134180/article/details/78122529

如果你看完这篇博文，觉得对你有帮助，并且愿意付赞助费，那么我会更有动力写下去。