[LG Optimus 2x] tonyp:
sudden reboot reports

Well no, it's not needed. But then the post itself isn't needed either :cyclops:

But okay, we need to track that down. It's actually quite strange, most people don't have hot reboots.

I had my last hot reboot more than a month ago :confused:

I do want to help those of you who got hot reboots though, but in order to do so we need to get some more information :)

So let's start from the beginning.

First of all: When you have a real hot reboot you won't see the LG (bootloader) logo, it will go straight to the bootanimation.

This is a strong indication that it's not a kernel but a ROM failure.

If you do see the bootloader then it's more like a cold reboot and could indicate a kernel failure.

Either way, you need to attach a last_kmsg thus I can make sure if there are some kernel related failures.

But we need logs of what happens on the ROM as well.

If you read my "how to get useful logs" thread you'll know that the logcat only contains data after the reboot, thus it's useless.

So I need the ones of you who get reboots to do one of the following:

have your phone connected to your computer and do a continuous logcat:

adb logcat -v time > logcat.log

Install aLogrec or CatLog from the market and

record

the logcat to your sdcard.

Actually everyone who is having reboot problems should do this right away. But be aware that this will result in a higher battery drain, so only do it to get proper sudden reboot reports.

If you know a better logcat recording app please post about it, those are the two I found via a quick search.

Now wait until you get another sudden reboot and hand me the log.

Again: I do

not

need a logcat you obtained AFTER the hot reboot.

I need a logcat you started recording BEFORE the hot reboot.

In the future I'd like (hot) reboots to get reported within a better format:

[B]Reboot report[/B]
PA version: PA build number
Kernel version: kernel version
time (approx): HH:mm (local time of your phone)
LG logo was displayed before the bootanimation: Y/N
UV: Y/N
OC: Y/N (if Y: cpu clock)
Full wipe before coming to PA: Y/N (dirty flashes of updates are okay).
last_kmsg attached: Y/N
recorded logcat attached: Y/N (if Y: type - adb/aLogrec/CatLog)
additional information: what where you doing etc.

Note that you are not allowed to report any bug whatsoever if you OCed > 1200 or UVed.

Set it back to default and wait for the errors to happen again.

Example:

[B]Reboot report[/B]
PA version: 11
Kernel version: kk 116
time (approx): 23:35
LG logo was displayed before the bootanimation: Y
UV: N
OC: Y (1200)
Full wipe before coming to PA: Y
last_kmsg attached: Y
recorded logcat attached: Y (adb)
additional information: I was running a benchmark when the phone rebooted

Some further notes:

I will ignore reports of sudden reboots which do not contain those information in the future!

Same goes for logcats which are hosted at OCH's where I need to enter captchas or stuff like that (you can't be serious!!).

Use your Dropbox, xda attachments or at least http://pastebin.com/ or http://paste.ubuntu.com/

(make sure to choose a high expiration date, sometimes it take me a couple days until I check the log)

I don't have any issues. If you do then I expect you to put some effort into your error report.

I'm helping you for free in my free time and am not a support help desk you can abuse.

There have been a couple reports in here where I didn't like the demanding tone - remember that I am doing you a personal favor if I look into your personal bugs or logs, I am in no way obligated to help anyone.

And I don't care about threats to move to another ROM, go ahead.

But this only applies to 10% of the reports I get, if you're wondering if I'm referring to you then I probably didn't :) Overall I'm very happy about the friendly posts we all exchange here!