[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
- Thread starter Stryke_the_Orc
- Start date
-
- Tags
- how-to logcat troubleshooting
I've got new error when commenting out that line
java.lang.IllegalArgumentException: SlidingChallengeLayout must be measured with an exact size
Hi guys, since a few weeks I have been getting crashes whenever I launch either CM Applock or ES File Explorer. I have tried a lot of things, I use xposed so i reflashed my rom without it and still it crashes, I tried using different kernel still it crashes, tried different SuperSU still same. My device is Redmi note 3 Pro and I use a custom rom Resurrection Remix 5.7.4 marshmallow. I reflashed three time but the issue still comes up. Note that the apps are fine when I flash it, but after I install all my apps, either directly through playstore or Titanium Backup, the crashes start. I have the logcat here, i started the logcat then clicked CM Applock then it crashed and then i stopped the logcat. Thanks.
pastebin (dot) com (/) awDC4KV9
pastebin (dot) com (/) awDC4KV9
Last edited:
You'll need to flash back to something that worked.If your ROM didn't flash and you can't use adb, that's your only recourse.
I would try to find older versions of those apps (before the crashes started). It sounds like something changed in them that your ROM doesn't support or know how to handle.
Was the original error preventing you from booting, or causing any actual problems? I've gotten so entrenched in building before that I have found errors that honestly meant nothing and wasted time trying to fix. Ultimately, it ended up looking like bits of test code, or abandoned methods that were never removed.
Sir now i retry this all and now problem file create 199kb and stoped. Make problem file 2 or 3 mb to boot my rom but stopped in 199kb plz help me sir
Last edited:
Unfortunately, I can't help you if you're unable to grab any logs. You'd need to be able to capture the boot process to see where it's failing.
Try flashing a ROM that works, allow and, and then try this ROM again. See if you're able to capture any logs during the boot.
hi @Stryke_the_Orc
Can you help me with this LOGCAT ?
https://haste.blamealexcruz.com/dPQX2xC3VK.vbs
When i trying to booting Android Oreo fot Wileyfox Storm, Getting bootloop issue " stuck at bootanimation" ...
Can you help me with this LOGCAT ?
https://haste.blamealexcruz.com/dPQX2xC3VK.vbs
When i trying to booting Android Oreo fot Wileyfox Storm, Getting bootloop issue " stuck at bootanimation" ...
Last edited:
Hello @Stryke_the_Orc ,
I get following logcat message when I try to edit any photo on my Note 5, using note 8 ROM.
can you please help me to understand related file on my phone for this message ?
Thanks in advance !
I get following logcat message when I try to edit any photo on my Note 5, using note 8 ROM.
can you please help me to understand related file on my phone for this message ?
Thanks in advance !
Last edited:
@Stryke_the_Orc
Sir I have compiled the Du for my device and it stuck at boot-animation and I have grab the logs but I don't know what I need to do to fix it. Please help me to understand them what I need to fix them.
https://gist.github.com/avirk/5f8577004c6e5eadbec1dfe2ae36776a
Sir I have compiled the Du for my device and it stuck at boot-animation and I have grab the logs but I don't know what I need to do to fix it. Please help me to understand them what I need to fix them.
https://gist.github.com/avirk/5f8577004c6e5eadbec1dfe2ae36776a
Wondering if someone can see if there is anything obvious in the logs as to why U11 dual SIM is crashing calls. Were still in alpha so it may be something else but I have no idea on these things. I can see a Java error re a null in the telephone app but not sure if that's the issue. Calls work fine on single sim. Any assistance would be appreciated
You need to take logs at the time of occurring of error, other logs won't help in solving the bug.
I am opening the catlog app, its start capturing logs, then open that app, paytm then phone rebooted, these are collected if u found any thing then tell pls
What ROM you're using and which version, have you installed Xposed and any other mods?
J7 15, On8 v2 port, xposed not installed, many mods installed but can u say pls this error occurs from which then i remove that?
The logs are too lengthy anyway I tried to look at the last lines of logs (as mostly error will be recorded at last before booting) but didn't seem to find any error apart from touch inputs and tz data errors. Will this random reboot happening with paytm only or with other apps too? Try reverting recently done changes also uninstall and reinstall paytm.
Similar threads
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:
- I can't keep up with all the requests.
- 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.
- If you post your logs here, any member may look at it and help you solve them.
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 LogcatNavigate 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"
Windows
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 here93Reading 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.
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.
I hope that this has been a good learning experience and will help you to understand any issues you are facing.
:victory:70Bootloops 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 site49Apps and Reference
Apps for grabbing Logcats
Please be sure to thank the developers of these fantastic tools for their time and efforts!
