[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!

What are you using this guide for?


  • Total voters
    971
Search This thread

akinis09

Senior Member
Jul 20, 2013
65
32
plz help me analyze this camera & wifi logcat error

I successfully ported miui ROM from leeco le2 to Coolpad cool1 after fixing many bugs but find it very difficult to fix both wifi & camera bug. Please I need someone to please help me analyze this logcat. Thanks in advance.
 

Attachments

  • alogcat.2017-04-17-11-59-55+0100.txt
    21.1 KB · Views: 23
  • alogcat.2017-04-17-12-14-06+0100.txt
    24.2 KB · Views: 24
Last edited:

jaklm

Member
Feb 13, 2016
33
5
After a lot of searching for a way to solve the problem the device is still stuck on the rom logo please help me fix it
i ported cm12.1 using cm11 as a base
thank you in advance
about the logcat how can i get it from TWRP?
 

Sam Nakamura

Retired Forum Moderator
After a lot of searching for a way to solve the problem the device is still stuck on the rom logo please help me fix it
i ported cm12.1 using cm11 as a base
thank you in advance
about the logcat how can i get it from TWRP?
It's not possible from twrp, you'll need a pc for that, you can easily Google which setup you'll need on the pc to get logs from bootloop...

Sent from my OnePlus 2 using XDA Labs
 

kos25k

Senior Member
Nov 15, 2012
3,195
444
hello and thanks for the app.I have the worst bug ever and I hope someone from here can help me.I have a moto x play stock rooted with xposed v87 arm sdk 23 with many mods.my problem is that they call me,they hear the call-beep sound but my phone does nothing!no ring,no wake up,no missed call notif. nothing but ghost call!it wakes up only if I manually open the screen and then rings.I have lost many important calls.yestersay I was lucky enough to catch a log with your app.I called from another phone to mine.it rung about 9 times (at this point,phone was dead-sleeping)then I opened the screen and it rang for a sec. and closed.the call was made to my phone at about 20:45.I asked in many forums but noone is willy to help me.so I ask here.any help from what is causing this,would be highly appreciated..thanks. https://www.dropbox.com/s/w6xrz84rk3u62aj/calldelay2045.txt?dl=0
 
Last edited:

jcmm11

Recognized Contributor
Feb 10, 2012
3,589
3,614
Google Pixel 4a 5G
hello and thanks for the app.I have the worst bug ever and I hope someone from here can help me.I have a moto x play stock rooted with xposed v87 arm sdk 23 with many mods.my problem is that they call me,they hear the call-beep sound but my phone does nothing!no ring,no wake up,no missed call notif. nothing but ghost call!it wakes up only if I manually open the screen and then rings.I have lost many important calls.yestersay I was lucky enough to catch a log with your app.I called from another phone to mine.it rung about 9 times (at this point,phone was dead-sleeping)then I opened the screen and it rang for a sec. and closed.the call was made to my phone at about 20:45.I asked in many forums but noone is willy to help me.so I ask here.any help from what is causing this,would be highly appreciated..thanks. https://www.dropbox.com/s/w6xrz84rk3u62aj/calldelay2045.txt?dl=0
Does it still happen if you remove exposed?
 
  • Like
Reactions: kos25k

kos25k

Senior Member
Nov 15, 2012
3,195
444
I havent tryied dude cause I have many xposed module's.today I noticed that with freezing root call blocker (but was inactive already) and uninstalling device id changer xposed module,my phone seems to ring normally.in the logcat I provided I saw about 20 times a specific same line which says : E/Xposed (8043): java.lang.NoSuchMethodError: com.android.internal.telephony.PhoneSubInfo#getDeviceId()#exact.as I saw this module was active but not set to ranfomize phone id etc..don't know really ehat happens...
 

Revantark

Senior Member
Apr 28, 2016
127
174
Hyderabad
i get this in adb when trying port. pls help



gps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:14.839 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:16.839 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:16.839 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:18.839 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:18.839 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:19.177 883 883 F libc : page record for 0xb6f8601c was not found (block_size=16)
05-20 16:35:20.839 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:20.840 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:22.840 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:22.840 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:24.245 892 892 F libc : page record for 0xb6f5301c was not found (block_size=16)
05-20 16:35:24.840 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:24.841 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:26.841 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:26.841 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:28.841 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:28.841 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:29.320 901 901 F libc : page record for 0xb6f0c01c was not found (block_size=16)
05-20 16:35:30.841 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:30.842 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:32.842 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:32.842 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:34.361 910 910 F libc : page record for 0xb6f5401c was not found (block_size=16)
05-20 16:35:34.842 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:34.842 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:36.842 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:36.843 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:38.843 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:38.843 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:39.410 919 919 F libc : page record for 0xb6f2001c was not found (block_size=16)
05-20 16:35:40.843 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:40.843 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:42.844 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:42.844 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:44.479 928 928 F libc : page record for 0xb6f5b01c was not found (block_size=16)
05-20 16:35:44.844 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:44.844 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:46.844 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:46.845 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:48.845 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:48.845 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:49.551 937 937 F libc : page record for 0xb6ef901c was not found (block_size=16)
05-20 16:35:50.845 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:50.845 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:52.846 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:52.846 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:53.603 946 946 F libc : page record for 0xb6ed001c was not found (block_size=16)
05-20 16:35:54.847 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:54.847 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:56.847 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:56.847 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:35:58.684 955 955 F libc : page record for 0xb6edc01c was not found (block_size=16)
05-20 16:35:58.847 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:35:58.848 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:00.848 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:00.848 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:02.848 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:02.848 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:03.738 964 964 F libc : page record for 0xb6f1f01c was not found (block_size=16)
05-20 16:36:04.848 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:04.849 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:06.849 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:06.849 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:08.798 973 973 F libc : page record for 0xb6eaf01c was not found (block_size=16)
05-20 16:36:08.849 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:08.849 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:10.850 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:10.850 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:12.850 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:12.853 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:13.869 982 982 F libc : page record for 0xb6f1c01c was not found (block_size=16)
05-20 16:36:14.853 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:14.853 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:16.854 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:16.854 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:18.854 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:18.854 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:18.912 991 991 F libc : page record for 0xb6ecd01c was not found (block_size=16)
05-20 16:36:20.854 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:20.854 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:22.855 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:22.855 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:23.972 1000 1000 F libc : page record for 0xb6f0601c was not found (block_size=16)
05-20 16:36:24.855 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:24.855 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:26.855 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:26.856 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:28.856 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:28.856 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:29.041 1009 1009 F libc : page record for 0xb6fab01c was not found (block_size=16)
05-20 16:36:30.856 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:30.856 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:32.857 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:32.857 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:34.098 1018 1018 F libc : page record for 0xb6f1f01c was not found (block_size=16)
05-20 16:36:34.857 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:34.857 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:36.857 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:36.858 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:38.858 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:38.858 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:39.143 1027 1027 F libc : page record for 0xb6fab01c was not found (block_size=16)
05-20 16:36:40.858 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:40.859 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:42.859 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:42.859 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:44.205 1036 1036 F libc : page record for 0xb6f1b01c was not found (block_size=16)
05-20 16:36:44.859 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:44.859 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:46.859 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:46.860 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:48.860 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:48.860 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:49.271 1045 1045 F libc : page record for 0xb6f7401c was not found (block_size=16)
05-20 16:36:50.860 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:50.860 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:52.860 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:52.861 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:54.315 1054 1054 F libc : page record for 0xb6eb101c was not found (block_size=16)
05-20 16:36:54.861 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:54.861 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:56.861 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:56.861 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:58.862 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:36:58.862 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:36:59.366 1063 1063 F libc : page record for 0xb6ef201c was not found (block_size=16)
05-20 16:37:00.862 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:00.862 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:02.863 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:02.863 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:04.453 1072 1072 F libc : page record for 0xb6f2801c was not found (block_size=16)
05-20 16:37:04.863 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:04.863 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:06.864 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:06.864 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:08.864 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:08.864 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:09.525 1081 1081 F libc : page record for 0xb6ee701c was not found (block_size=16)
05-20 16:37:10.864 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:10.865 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:12.865 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:12.865 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:14.555 1101 1101 F libc : page record for 0xb6f4201c was not found (block_size=16)
05-20 16:37:14.865 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:14.865 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:16.865 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:16.866 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:18.593 1112 1112 F libc : page record for 0xb6f8b01c was not found (block_size=16)
05-20 16:37:18.866 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:18.866 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:20.866 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:20.866 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:22.866 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:22.867 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:23.640 1121 1121 F libc : page record for 0xb6f1701c was not found (block_size=16)
05-20 16:37:24.867 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:24.867 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:26.867 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:26.867 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:28.699 1130 1130 F libc : page record for 0xb6fac01c was not found (block_size=16)
05-20 16:37:28.868 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:28.868 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:30.868 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:30.868 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:32.868 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:32.869 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:33.743 1139 1139 F libc : page record for 0xb6f7301c was not found (block_size=16)
05-20 16:37:34.869 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:34.869 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:36.869 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:36.870 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:38.798 1148 1148 F libc : page record for 0xb6f4e01c was not found (block_size=16)
05-20 16:37:38.870 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:38.870 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:40.870 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:40.870 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:42.870 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:42.871 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:43.860 1157 1157 F libc : page record for 0xb6ee601c was not found (block_size=16)
05-20 16:37:44.871 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:44.871 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:46.871 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:46.871 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:48.871 230 356 D agps : [agps] WARNING: [CP] cp2_fd_1_req_sim_num_timeout
05-20 16:37:48.872 230 332 D agps : [agps][n][CP] [MD_1] write sim_info_req
05-20 16:37:48.911 1166 1166 F libc : page record for 0xb6ec501c was not found (block_size=16)
 

Ashish.akc

Senior Member
Feb 9, 2013
426
72
28
Jaipur
Am using op3 with Freedom OS 2.10 CE build. My phone sometimes acts like it's dead. No response to buttons, touchscreen or the charger. I have to hold down the power button for a couple of seconds in order to forcefully reboot it.
Am not sue if the first log would have capured anything important as i don't remember if the app was running while the phone acted wired but am damn sure with the second one.
Update: i faced two of these hiccups back to back. Also my alarm did not rang because of this. Adding two more logs.
 

Attachments

  • alogcat.2017-06-07-23-48-12+0530.txt
    102.7 KB · Views: 7
  • alogcat.2017-06-08-23-09-05+0530.txt
    94.1 KB · Views: 8
  • alogcat.2017-06-09-04-49-33+0530.txt
    92 KB · Views: 7
  • alogcat.2017-06-09-05-09-01+0530.txt
    89.9 KB · Views: 9

ktmom

Retired Forum Moderator
Apr 22, 2015
5,176
3,387
Deep Space Station K7
Need help reading this logcat.and find fix. Stuck in bootanimation.
If you're still looking for help, you need to supply more information.

The "log file" is corrupt. It looks like a grab of a terminal window that is smaller than the line's length. The end of every line is truncated. Please read through the beginning of this thread and pipe the output of your a ADB log straight into a file.

Additionally, knowing your device, ROM, modifications (e.g. Root method, exposed ...) and what triggered the bootloop would hep -just updated ROM? Installed root? A theme? Something else?
 

foudroid

Senior Member
Sep 1, 2014
208
45
madagascar
If you're still looking for help, you need to supply more information.

The "log file" is corrupt. It looks like a grab of a terminal window that is smaller than the line's length. The end of every line is truncated. Please read through the beginning of this thread and pipe the output of your a ADB log straight into a file.

Additionally, knowing your device, ROM, modifications (e.g. Root method, exposed ...) and what triggered the bootloop would hep -just updated ROM? Installed root? A theme? Something else?
Yes ! I just copy and past the output of an adb terminal logcat. Can'export the log cause there is no key ">" in my keyboard and don't know how to do. Can't use the command "adb logcat >logcat.txt".
And about the rom : i'running CM12.1 mtk6753chips try to port xenonhd android 7.2.1 from other device which have same spec., dtuck in bootanimation with that log !
 

jcmm11

Recognized Contributor
Feb 10, 2012
3,589
3,614
Google Pixel 4a 5G
Yes ! I just copy and past the output of an adb terminal logcat. Can'export the log cause there is no key ">" in my keyboard and don't know how to do. Can't use the command "adb logcat >logcat.txt".
And about the rom : i'running CM12.1 mtk6753chips try to port xenonhd android 7.2.1 from other device which have same spec., dtuck in bootanimation with that log !
If you have the | key then try this
Code:
adb logcat | tee logcat.txt
That will write output to both terminal and file.
 

tobi/

Member
Jul 7, 2017
6
4
help !

hv been trying to port a samsung keyboard rest of the errors were easyto fix but unable to decipher this one.what file should i edit n where i can find it....lend some assistance thnk u

#logcat
07-07 14:33:31.923 11306 11465 I ActivityManager: Start proc com.sec.android.inputmethod for service com.sec.android.inputmethod/.SamsungKeypad: pid=12601 uid=1000 gids={41000, 3003, 3002, 3001, 1028, 1015, 1023, 1007, 1001, 2001, 1024}

07-07 14:33:32.033 12601 12601 E AndroidRuntime: Process: com.sec.android.inputmethod, PID: 12601

07-07 14:33:33.585 11306 11465 I ActivityManager: Process com.sec.android.inputmethod (pid 12601) (adj 0) has died.(11,134)

07-07 14:33:33.585 11306 11465 W ActivityManager: Scheduling restart of crashed service com.sec.android.inputmethod/.SamsungKeypad in 1000ms
 

foudroid

Senior Member
Sep 1, 2014
208
45
madagascar
Here is the correct logcat. Try to port xenonhd android 7.1.2 to my elephone p6000 pro.stuck in boot animation.please need help to find fix !!!!!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 246



    DUE TO REAL LIFE TIME CONSTRAINTS I AM UNABLE TO CONTINUE READING AND DIAGNOSING LOGS FOR MEMBERS. PLEASE USE THIS THREAD AS INTENDED, AS A STARTING POINT IN LEARNING TO READ THESE LOGS AND DIAGNOSE PROBLEMS YOURSELF. THANK YOU!




    The Basics

    I'm starting this thread in hopes of sharing some very useful information to all our new members and hopefully either teaching something new or being a good refresher for our experienced members. I've been asked before how to tell what errors are present in logcats, how I can understand all that mess, etc...

    Well, I'm going to try my best to explain all of it. In this way, you can get your own logs and try to fix the problems, or know exactly what is causing your problems to help out the developers so they aren't looking through thousands of lines of code for each persons issue.

    Help us help you!

    ATTENTION:
    Due to the recent feature in the portal, my thread has become increasingly popular, and as such I am getting a lot of requests for help. You may post your logs here, but please do so in either pastebin format, or use hide tags. Please DO NOT request help via pm. This is for a couple of reasons:
    1. I can't keep up with all the requests.
    2. Your logs may be solved by another member, I have requested that any willing RC's, RD's, Moderators, or members willing to help, to do so.
    3. If you post your logs here, any member may look at it and help you solve them.
    Thank you.


    To begin with, we'll need to have some understanding of adb. Check out this thread by @bigtoysrock and be sure to thank him!

    Logcats

    First, we'll need to know how to get a logcat. With the plethora of new users this has been the subject of many, many discussions. When asked to get a logcat, they don't know how.


    Tools and Requirements

    First of all, you'll absolutely NEED to have usb debugging enabled. To do this go to SETTINGS, navigate down to DEVELOPER OPTIONS and select it, if they are not on use the toggle in the top right corner and select USB DEBUGGING ( See attached screen shots )

    Secondly, you'll absolutely NEED to have the ANDROID SDK grab it here
    Install the SDK on the root of your computer. DO NOT change the SDK name to include any spaces as it will fail!

    Also be sure to grab your device specific drivers, if they aren't already installed. Some devices will install them automatically, while others require a simple google search.

    Now that you've got everything you need, lets grab a logcat!

    Update: 15 Second ADB installer for windows is an excellent alternative for the above instructions, and while you're there be sure to thank @Snoop05

    How to get a Logcat

    Windows
    Navigate to where you've installed the sdk. Once you've gotten into the sdk, you're going to look for "PLATFORM TOOLS" folder, inside hold shift + right click on any empty space, select "OPEN COMMAND WINDOW HERE"
    Connect your phone to your PC via usb cable, in the command window type "adb devices" without the quotes. If you've set everything up properly it should return an alpha-numeric value, this is your device ID. If not, you've missed a step or installed sdk in the wrong manner. Go back and double check your steps.

    Now that we know you're connected there are a few options, you can run the logcat in command window, or you can export it to a .txt file.

    To see the log in command window just type "adb logcat" (again no quotes) and the log will scroll through your screen. To stop scrolling so you can investigate hit ctrl + c

    To export to a .txt file (I personally prefer this method) type "adb logcat > logcat.txt". You can name the logcat anything you want, for example "adb logcat > MyError.txt" just be sure not to include spaces or special characters in the name of the file.



    MAC/Linux

    "Instructions:

    Install your device driver for using adb. Everything you need will you find here
    Download adb executable for your OS (Download: Windows | Linux | Mac). Paste it somewhere.
    Connect your android device.
    Verify if "Settings > Developer options > USB debugging" is checked, if not, simply check it.
    Open a command promt (windows) or terminal (linux / mac). How to do it: On Windows: windows + r > enter "cmd" (without quotes) > click enter | On Linux: You don't know how to open a terminal? LOL | On Mac: Type Terminal into Spotlight and open it
    CD to the directory where the adb executable is located. On Windows: Go to the directory where you downloaded the adb executable, Shift+Right Click and select "Open Console" (or similar) | On Linux / Mac: Rightclick in the directory and select "Open Terminal here" (or simply CD into the directory)
    Type in your cmd/terminal: adb devices to verify your device is properly connected.
    If your device is properly selected, type in adb logcat to show the mighty and magic logcat aka stacktrace.
    Reproduce your error (or whatever) on your device.
    Right after, paste the whole cmd / terminal window into a paste-service like http://pastebin.com/ and send it to us." - Quoted from Leandros here
    93
    Reading and understanding logcat output

    Reading a Logcat

    Ok, so now we have our log but what do we do with it?
    There are a few things that you need to know before you'll understand what is what.
    Preceding every line in a logcat is a class, you can learn about them here.
    These will look like this and I have placed the meaning next to each:
    Code:
    E/       Error - I would hope this is self explanatory
    F/       Fatal Error - Again pretty self explanatory
    I/        Information - This is pretty tricky, the information class shows what the system is doing, but it can also show you errors so read it carefully!
    D/      Dalvikvm - This class will show what the dalvik processes are doing, but can also show you where mistakes are
    W/     Warning - Warnings are basically errors, but less severe. Usually it will show you missing resources, conflicting or missing paths, etc...
    V/      Verbose - Basically everything the phone is doing
    S/      Silent - You will not see silent


    Ok so lets see some examples. Some of these will be more in-depth than others simply because there is more to it.

    Code:
    [COLOR="Red"]D/dalvikvm( 1853): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---[/COLOR]
    Here we see that the dalvik process has begun to optimize our system files.
    
    [COLOR="red"]D/dalvikvm( 2162): DexOpt: 'Lcom/sec/android/seccamera/SecCamera$OnMultiFrameShotEventListener;' has an earlier definition; blocking out[/COLOR]
    Here you can see that the Dalvik process has already defined the called method, and is skipping the optimization
    
    [COLOR="red"]I/PackageManager( 2130): /system/app/sCloudSyncBrowser.apk changed; collecting certs[/COLOR]
    The information class is showing that there has been a change made to this apk, and is verifying the signature.
    
    [COLOR="red"]W/ResourceType( 2130): Failure getting entry for 0x7f050020 (t=4 e=32) in package 0 (error -75)
    
    D/PhoneStatusBar( 2792): Added status bar view
    
    D/PhoneStatusBar( 2792): disable: < expand icons alerts ticker system_info back home recent clock >
    
    W/PackageManager( 2130): Failure retrieving xml 0x7f050020 in package com.maxmpz.audioplayer
    
    W/PackageManager( 2130): android.content.res.Resources$NotFoundException: Resource ID #0x7f050020
    
    W/PackageManager( 2130): at android.content.res.Resources.getValue(Resources.java:1339)
    
    W/PackageManager( 2130): at android.content.res.Resources.loadXmlResourceParser(Resources.java:2445)
    
    W/PackageManager( 2130): at android.content.res.Resources.getXml(Resources.java:1227)
    
    W/PackageManager( 2130): at android.app.ApplicationPackageManager.getXml(ApplicationPackageManager.java:1080)
    
    W/PackageManager( 2130): at android.content.pm.PackageItemInfo.loadXmlMetaData(PackageItemInfo.java:227)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.parseProviderInfoXml(AppWidgetServiceImpl.java:1264)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.addProviderLocked(AppWidgetServiceImpl.java:1162)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.loadAppWidgetList(AppWidgetServiceImpl.java:1148)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.ensureStateLoadedLocked(AppWidgetServiceImpl.java:391)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.systemReady(AppWidgetServiceImpl.java:211)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:156)
    
    W/PackageManager( 2130): at com.android.server.ServerThread$1.run(SystemServer.java:1882)
    
    W/PackageManager( 2130): at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:8250)
    
    W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$9$1.run(ActivityManagerService.java:8152)
    
    W/PackageManager( 2130): at android.os.Handler.handleCallback(Handler.java:615)
    
    W/PackageManager( 2130): at android.os.Handler.dispatchMessage(Handler.java:92)
    
    W/PackageManager( 2130): at android.os.Looper.loop(Looper.java:137)
    
    W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1563)
    
    W/ResourceType( 2130): Failure getting entry for 0x7f050021 (t=4 e=33) in package 0 (error -75)
    
    W/PackageManager( 2130): Failure retrieving xml 0x7f050021 in package com.maxmpz.audioplayer
    
    W/PackageManager( 2130): android.content.res.Resources$NotFoundException: Resource ID #0x7f050021
    
    W/PackageManager( 2130): at android.content.res.Resources.getValue(Resources.java:1339)
    
    W/PackageManager( 2130): at android.content.res.Resources.loadXmlResourceParser(Resources.java:2445)
    
    W/PackageManager( 2130): at android.content.res.Resources.getXml(Resources.java:1227)
    
    W/PackageManager( 2130): at android.app.ApplicationPackageManager.getXml(ApplicationPackageManager.java:1080)
    
    W/PackageManager( 2130): at android.content.pm.PackageItemInfo.loadXmlMetaData(PackageItemInfo.java:227)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.parseProviderInfoXml(AppWidgetServiceImpl.java:1264)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.addProviderLocked(AppWidgetServiceImpl.java:1162)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.loadAppWidgetList(AppWidgetServiceImpl.java:1148)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.ensureStateLoadedLocked(AppWidgetServiceImpl.java:391)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetServiceImpl.systemReady(AppWidgetServiceImpl.java:211)
    
    W/PackageManager( 2130): at com.android.server.AppWidgetService.systemReady(AppWidgetService.java:156)
    
    W/PackageManager( 2130): at com.android.server.ServerThread$1.run(SystemServer.java:1882)
    
    W/PackageManager( 2130): at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:8250)
    
    W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$9$1.run(ActivityManagerService.java:8152)
    
    W/PackageManager( 2130): at android.os.Handler.handleCallback(Handler.java:615)
    
    W/PackageManager( 2130): at android.os.Handler.dispatchMessage(Handler.java:92)
    
    W/PackageManager( 2130): at android.os.Looper.loop(Looper.java:137)
    
    W/PackageManager( 2130): at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1563)[/COLOR]
    Here is a great example of the warning class showing missing resources.
    
    [COLOR="red"]I/dalvikvm( 1853): Could not find method android.app.IActivityManager.resizeArrangedWindow, referenced from method android.app.ActivityManager.resizeArrangedWindow
    
    W/dalvikvm( 1853): VFY: unable to resolve interface method 3769: Landroid/app/IActivityManager;.resizeArrangedWindow (IILandroid/graphics/Rect;)Landroid/graphics/Rect;
    
    D/dalvikvm( 1853): VFY: replacing opcode 0x72 at 0x0004[/COLOR]
    A prime example of Information class showing an "error", these will usually be listed in information class if they don't have a great impact of the functionality of the device.
    
    [COLOR="red"]F/PackageManager( 2014): Unable to backup package manager settings,  current changes will be lost at reboot
    E/DropBoxManagerService(2014):  Can't write: system_server_wtf
    E/DropBoxManagerService(2014):  java.io.FileNotFoundException: /data/system/dropbox/drop21.tmp: open failed: EROFS (Read-only file system)
    E/DropBoxManagerService(2014):  at libcore.io.IoBridge.open(IoBridge.java:416)
    E/DropBoxManagerService(2014):  at java.io.FileOutputStream.(FileOutputStream.java:88)
    E/DropBoxManagerService(2014):  at java.io.FileOutputStream.(FileOutputStream.java:73)
    E/DropBoxManagerService(2014):  at com.android.server.DropBoxManagerService.add(DropBoxManagerService.java:208)
    E/DropBoxManagerService(2014):  at android.os.DropBoxManager.addText(DropBoxManager.java:272)
    E/DropBoxManagerService(2014):  at com.android.server.am.ActivityManagerService$13.run(ActivityManagerService.java:8281)
    E/DropBoxManagerService(2014):  at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:8288)
    E/DropBoxManagerService(2014):  at com.android.server.am.ActivityManagerService.handleApplicationWtf(ActivityManagerService.java:8099)
    E/DropBoxManagerService(2014):  at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:329)
    E/DropBoxManagerService(2014):  at android.util.Log$1.onTerribleFailure(Log.java:103)
    E/DropBoxManagerService(2014):  at android.util.Log.wtf(Log.java:278)
    E/DropBoxManagerService(2014):  at android.util.Log.wtf(Log.java:255)
    E/DropBoxManagerService(2014):  at com.android.server.pm.Settings.writeLPr(Settings.java:1115)
    E/DropBoxManagerService(2014):  at com.android.server.pm.PackageManagerService.unloadMediaPackages(PackageManagerService.java:9314)
    E/DropBoxManagerService(2014):  at com.android.server.pm.PackageManagerService.updateExternalMediaStatusInner(PackageManagerService.java:9128)
    E/DropBoxManagerService(2014):  at com.android.server.pm.PackageManagerService.access$3800(PackageManagerService.java:165)
    E/DropBoxManagerService(2014):  at com.android.server.pm.PackageManagerService$10.run(PackageManagerService.java:9017)
    E/DropBoxManagerService(2014):  at android.os.Handler.handleCallback(Handler.java:615)
    E/DropBoxManagerService(2014):  at android.os.Handler.dispatchMessage(Handler.java:92)
    E/DropBoxManagerService(2014):  at android.os.Looper.loop(Looper.java:137)
    E/DropBoxManagerService(2014):  at android.os.HandlerThread.run(HandlerThread.java:60)
    E/DropBoxManagerService(2014):  Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
    E/DropBoxManagerService(2014):  at libcore.io.Posix.open(Native Method)
    E/DropBoxManagerService(2014):  at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
    E/DropBoxManagerService(2014):  at libcore.io.IoBridge.open(IoBridge.java:400)
    E/DropBoxManagerService(2014):  ... 20 more[/COLOR]
    Here we have the Fatal and Error classes.

    Ok, so now we have seen some examples, lets learn to decipher them:highfive:

    The beautiful thing about these logs is that they tell you exactly what and where everything is, as long as you know what you're looking at.
    I'm only going to use the one line to show you how to read a log, as the format is exactly the same for any class.
    Code:
    E/DropBoxManagerService(2014):  at com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:8288)
    
    So here we have the printed error from logcat, the format used is as follows
    Class/Process/Location
    [b]Important! The log WILL NOT tell you what apk or jar the error occurs in, this is the hardest part of debugging![/b]
    
    In the above error we see
    Class = E/
    Process = DropBoxManagerService
    Location = com.android.server.am.ActivityManagerService.addErrorToDropBox(ActivityManagerService.java:8288) (Folder directory.File Name. Method)
    
    I know from all my digging that the specified path is in services.jar so once I have services.jar decompiled I'll follow the path laid out. (Decompile "apkname".odex for odexed roms and classes.dex for deodexed roms)
    These paths will always be located in the smali folder! For example I open my classes.dex folder after decompiling and see a smali folder, I'll open that and then I have options. The . after every word is a folder directory ( same as / in your computer directory )
    The specified path says com. so I'll open the com folder, next I'm directed to android, then server, then am folder.
    Now I should see a bunch of files and possibly some folders, [b]if there is no folder name that matches the next directory it is a file![/b]
    ActivityManagerService is a filename, so I'll open that file using NotePad++ and search for the specified method which is addErrorToDropBox.
    From here I can use another file to compare the lines to find my error, or I can know exactly where the error occured and report my problem to a helpful dev or member.

    I hope that this has been a good learning experience and will help you to understand any issues you are facing.
    :victory:
    70
    Bootloops and Filtering your logs

    Getting a Logcat during the dreaded Bootloop

    The only difference between grabbing a logcat while running and grabbing one during a bootloop is the program you're going to use. Instead of the standard adb bridge, we'll be using the adb monitor tool. You can find this tool under the "TOOLS" folder. Open the "Tools" folder, right click on any empty space and select "Open Command Window Here"
    Once the window is open, type "monitor" (without the quotes) and press enter. A whole new program will open listing the device ID and subfolders (your devices partitions)
    IMPORTANT! The device ID may not show up right away, THIS IS OK! I found that it took about three bootloop cycles to actually connect.
    Once you see the device ID, within a few seconds you should see the "system" partition listed underneath. Select it.
    Down in the bottom left corner select the "Logcat" tab. From here, you can grab the logcat in a txt format or just watch it scroll.
    I have taken screenshots of the process, and are available here

    There's a great guide here that goes a little more in depth and has updated information about the requirements for a log during bootloops.


    How to Filter your Logcat

    Lets say you want to find only the logs for a specific app or process, searching through thousands of lines can be a pain. Luckily, adb allows you to filter your logs based on application tags!
    Here's how:
    Code:
    adb logcat ActivityManager:I MyApp:D *:S

    This filter basically says "Show me only logs for ActivityManager at an Information or above level, and all logs for 'MyApp' with a priority level of Debug and higher" The *:S is important here, this makes all other tags Silent so that it ensures only the filtered tags are shown in your log.How's that for handy?


    Demesg (kernel) Logs

    For a demesg log you'll want to follow the same instructions as above to get into adb terminal.
    Once there, type adb devices to verify you're connected. Now you can pull a log by simply typing "adb shell dmesg > dmesg.txt" (without the quotatons" This will place the logs in the same folder that you launched terminal from (platform-tools)

    Also, for more detailed information and a few other useful commands check out this site
    49
    Apps and Reference

    Apps for grabbing Logcats


    Mobile Apps

    alogcat

    This app is great for seeing your logs, especially on older Android versions. The biggest issue I have with this app is that the share function doesn't work properly on jellybean. Yet...
    You can grab it here

    CatLog

    I personally have no experience with this app, but it's highly rated in Play Store and has an easy to use User Interface.
    Grab it here

    getlogs

    This is my favorite of these apps, I can use it to grab almost any log I want. Highly recommended for any developer, themer, or enthusiast!
    Simple, clean, effective. The way getting your logs should be:D
    Grab it here

    Logcat Reader

    Grab it here

    Logcat Extreme

    This one looks pretty cool, it has a "floating logcat" feature. Grab it here


    PC Applications

    A pretty neat logcat tool is AIOlog found here, contains versions for Windows, Linux and MacOS's by 32 and 64 bit systems.


    Here's a neat tool for you windows users, an AIO Logcat manager. Grab it, and view the orignal thread here

    Another for you windows users, Easy Logcat Maker is an executable GUI that looks pretty neat.

    Another cool logging tool is here created by the genius behind VTS!

    A new Windows tool by @FuzzyMeep Two, the aptly named Logcat Tool will parse your logcat to show you how many of each entry your logs contain, and then it organizes your logs into separate files based on the type of entry (Warning, Error, Verbose, etc...), and more! This could easily become my favorite desktop method of grabbing logs.
    Misc. Apps and Tools

    For those of you using linux there is a neat tool that color codes your logcat output to make it easier to read. You can find it here

    Not a logcat app, per se, but a pretty entertaining and live logcat boot animation courtesy of @Chainfire can be found here. Download it and see your device boot in real time!


    There are a lot more apps available than what I've covered here. These are simply the most widely known (possibly with the exception of getlogs) and widely used/recommended. If you find or make any more of these apps, please feel free to post the link here and share with the community!

    PLEASE NOTE THAT IT IS AGAINST XDA RULES TO LINK TO PAID APPS, SO DO NOT LINK TO PAID SERVICES OR THE POST WILL BE REPORTED AND LIKELY REMOVED

    Reference Links:
    Googles Logcat Help Pages
    How to get useful logs by tonyp
    Guide to logcats provided by Deadly
    Color Coding Your Logcat World


    Please be sure to thank the developers of these fantastic tools for their time and efforts!
    24
    For some reason every time I try to run a logcat I get this

    Sent from my SPH-L710 using xda premium