[HTC Inspire 4G] existz:
To put an end to all this , without a logcat log there is nothing I can do to fix the problem (granted sometimes an issue is self explanatory, but most of the time its not).. Its like taking your car to the mechanic and only saying "My car doesn't work", and then leaving. Debug logs (logcat, dmesg..etc) are very useful for when I'm trying to figure out the cause for an issue..As I've seen some say that they are not developers..etc so they don't have to do it...There's a ton of apps in the market that will do this for you, and I've also got instructions posted when clicking the "Issues" tab on the GoogleCode site (and remember, the GoogleCode site is actually the main site for this rom, this thread is just a place to talk development for this rom, so all issues etc should be posted there anyways.

Its very simple to get a log of the issue, just have adb installed on your PC (this is very simple to do, and there's a guide on the AOSP website to install the sdk...then all you have to do is run "adb logcat" then copy and paste.. very simple. I usually don't throw this out, but since its becoming a task to report an issue,.. I do this for free and in my spare time (I actually spend way more time than I should on this) I don't ask for anything in return, but all I ask of you (the end user) is to post a proper bug report with logs so I can fix the issue for YOU. I don't do this for the money, or whatever it may be, I would be fine with just posting my source on github and calling it a day, I don't get anything extra out of posting releases here on xda.. So please, always include a debug log of the issue, most of the time this will help get the bug fixed quicker...instead of me trying to take "my phone reboots" and trying 100000 different things to try and duplicate the issue , and then having to dig through gigabytes (yes, gigabytes, about 7-8gb) worth of text/code to try and find the problem...when a logcat log would tell me its something in the browser, or wifi, or whatever it may be.

With reboots/lockups I know its tricky to get a log since the log clears on reboot...but the way around this is to find something that will reproduce the issue, hook up to PC and run "adb logcat" , then you can see the log in real time, then reproduce the issue...your log will still be in the terminal even after the phone reboots... But my point is, if I can spend the amount of time that I do on this rom, posting a logcat log of an issue isn't much to ask...especially when I'm fixing the bug for you...

And another thing that is very helpful is say there's an issue on my rom but not on LordClockans, the best thing for me is to have a log of the issue from my rom and then one from LCs...that way I can compare the 2.. This was what helped me figure out the Temple Run issue awhile back...by comparing the 2 I could see what was erroring out on mine, and then what it should have been on LCs..And then the issue was fixed in literally 5min...instead of days/weeks digging through countless things that probably wouldn't have ended up fixing it anyways (which is just a waste of my personal time, or time that could be spend on something else and also delays getting a new release out)...So always include a log if it works on another rom/kernel so I can compare the 2.. And also if you narrow it down to the kernel causing the issue, please include a dmesg log along with the logcat log.

/end of topic