[HOW-TO-DEBUG DEFY]

1.) Pre Requirements:  	

	- Fully working adb enviroment (Windows or Linux)
       	- ADB enabled on Defy
	- Defy conneted via USB and terminal/command line with adb shell

2.) Try to nail down the problem:

	There are most likely two problems; those which are reproduceable and those which are not.
	The first one are easy; type cat /proc/kmsg
	This will get you some sort of livestream of the current kernel log.
	Now make the steps to force the problem (reboot/freeze/something else)
	and save this kernel log. Post it either in the forum or send me a PM.

	The random issues are harder to debug.
	This needs more time since you have to "play around" untill you can reproduce
	the problem.

	By the way dmesg will give you the current kmsg at a certain moment of time (like a snapshot).
	With kmsg you can actually see what the kernel is doing while you are doing stuff.

3.) When do i have to use dmesg/kmsg and logcat?

	It's simple; all kernel related stuff is in dmesg/kmsg.
	Everything App/OS related is in logcat. In most cases a kmsg-log is enough
	and logcat not even needed (because it contains no useful information)
	
	However, you can post both, just open another terminal and type logcat
	and you'll get another some sort of livestream.

4.) How can i save those logs?

	First of all, don't try to get logs on your device. Use a terminal
	on your computer. 
	For Linux; 
		./adb shell
	For Windows;
		adb shell

	Thats enough. If you have the sdk installed, you might want to go to ~installdir/platform-tools/
	If you really want to get logs on your device, use logcat > /sdcard/logcat.txt or dmesg > /sdcard/dmesg.txt

5.) I can't even boot, how should i provide logs?

	If you can't boot up its likely that you want to plugin USB right after it tries
	to boot up (after the led) and fire cat /proc/kmsg
	It's a bit tricky, don't give up if it doesn't work for you on the first time.

6.) Where can i post my logs?
	
	Anywhere! However, one of the best places is http://pastie.org

7.) Activate more logs - Kmemleak;
	
	Memory Leaks can happen and they will have a impact on your device. Keep this in mind.
	If you want to help finding those little bastards, you need to enable the kernel memory
	leak detector (if not already activated).
	
		CONFIG_DEBUG_KMEMLEAK=y
		CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=1200

	When booted up, you need to mount the debugfs;

		mount -t debugfs nodev /sys/kernel/debug/
		cat /sys/kernel/debug/kmemleak

	The second command will print you all available memory leaks. Save this file somewhere and send it to
	your favorite developer. They'll love you for that.


8.) I use a 3.0 Kernel, can i post better logs?

	Yes! I enabled the ram console support for 3.0 Kernel which helps debugging.
	Whenever you encountered a random reboot, just fire cat /proc/last_kmsg
	This gives you the last dmesg-output until your crash/reboot/freeze/whatever happened.