Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Tutorial: How to properly post a bug

OP Indirect

27th February 2012, 08:58 PM   |  #1  
OP Recognized Contributor
Flag Florida
Thanks Meter: 2,960
 
2,323 posts
Join Date:Joined: Mar 2011
Donate to Me
More
Alright guys, I was on an irc channel when I considered posting this since it's rather important. There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".

Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.

This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})


Section 1: Logcat
This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.

How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!

Section 2: Dmesg

This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right.
How to get a dmesg:
This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!

Section 3: last_kmsg
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
 cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
 adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.

Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.

I'm glad to have written this and devs, feel free to link to this guide as a "bug reporting FAQ"
The Following 87 Users Say Thank You to Indirect For This Useful Post: [ View ]
27th February 2012, 09:12 PM   |  #2  
shabbypenguin's Avatar
Recognized Developer
Thanks Meter: 5,112
 
4,656 posts
Join Date:Joined: May 2010
Donate to Me
More
HALP! I BRICKD MY FONE!!1!

I JAILBROKED IT LAST NIGHT AND NOW I NO GET SIGNEL!! PLASE HALP!!!1


but on a more serious note, good tut
The Following 4 Users Say Thank You to shabbypenguin For This Useful Post: [ View ]
17th April 2012, 06:14 PM   |  #3  
Spiralzz's Avatar
Senior Member
Flag Islamabad
Thanks Meter: 332
 
1,166 posts
Join Date:Joined: Aug 2011
More
Thanks dude!!! I was looking for some kind of guide. Only thing I still don't understand is when are we supposed to give dmesg and when do we give the logcat? I understand the last_kmsg is for kernel panics and random reboots, but the rest two are still ambiguous to me... Could you please explain the other two in a simpler way with an easy example for each?... Sorry.. I'm a noob... but am trying to learn these things..
Last edited by Spiralzz; 17th April 2012 at 06:18 PM.
8th August 2012, 12:53 PM   |  #4  
Senior Member
Thanks Meter: 64
 
333 posts
Join Date:Joined: Dec 2011
There also is this app called 'Bootlog Uptime' that tries to auto-detect a crash and subsequently exports the log to sdcard.
9th August 2012, 11:25 AM   |  #5  
anshumandash's Avatar
Senior Member
Thanks Meter: 463
 
1,435 posts
Join Date:Joined: Mar 2011
Donate to Me
More
When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?
The Following User Says Thank You to anshumandash For This Useful Post: [ View ]
9th August 2012, 12:40 PM   |  #6  
OP Recognized Contributor
Flag Florida
Thanks Meter: 2,960
 
2,323 posts
Join Date:Joined: Mar 2011
Donate to Me
More
If you're in boot loader mode, that's not adb.

Sent from my Full Android on Crespo4G using xda premium
9th August 2012, 03:59 PM   |  #7  
Spiralzz's Avatar
Senior Member
Flag Islamabad
Thanks Meter: 332
 
1,166 posts
Join Date:Joined: Aug 2011
More
Quote:
Originally Posted by anshumandash

When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?

You need to boot into the ROM, then grab the logs.

Sent from my GT-I9100 using xda app-developers app
4th February 2013, 06:11 PM   |  #8  
DowntownJeffBrown's Avatar
Senior Member
Flag Porter Indiana (Chicagoland)
Thanks Meter: 3,371
 
15,882 posts
Join Date:Joined: Oct 2012
More
Re: Tutorial: How to properly post a bug
Thank you for this

Sent from my Nexus 4 using Xparent BlueTapatalk 2
25th March 2013, 07:05 PM   |  #9  
fatpanda0's Avatar
Senior Member
Thanks Meter: 106
 
284 posts
Join Date:Joined: Nov 2012
Donate to Me
More
Can someone help me please.

I am from the HTC One S (Ville C2) community. I am testing a new kernel by one of the devs who doesnt have the phone. Now after installing the new kernel the phone is on bootloop. I need to extract the last_kmsg. the only way I can get out of the boot loop to do anything is by pressing the power button and simulate battery out. This it seems erases the last_kmsg cuz when I enter recovery to get it. It either says no such file or sometimes ends up showing me the recovery kernels last_kmsg. I am at a total loss as to how I the last_kmsg file.

There is also no way to install a working boot image as the kernel uses a zip to install files on the phone so we must use recovery to restore to previous state. This leads to the original condition. I tried looking for a solution but cant find it anywhere.
13th April 2013, 10:24 AM   |  #10  
Member
Thanks Meter: 7
 
61 posts
Join Date:Joined: Nov 2012
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"

And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?

Thanks!

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes