[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by huckl3b3rry

Now for a issue. I'm on the 1/16 release and I just had a reboot. I wasn't using the phone when it happened so I can't give you more more information on what was happening, etc. I grabbed the logs as soon as I had a chance: ====================== SYSTEM INFORMATION =================== Linux localhost 2. - Pastebin.com

If you had a reboot, unfortunately the only logs that are useful are last_kmsg...

GetLogs is awesome, but really only shows logs from that boot.

[huckl3b3rry]

Originally Posted by arrrghhh

If you had a reboot, unfortunately the long logs that are useful are last_kmsg...

GetLogs is awesome, but really only shows logs from that boot.

OK. Here is last_kmsg. I just had a second reboot when I plugged in USB to capture last_kmsg. First two reboots I've experienced (that I know of) since I loaded 1/16.

[arrrghhh]

Originally Posted by huckl3b3rry

OK. Here is last_kmsg. I just had a second reboot when I plugged in USB to capture last_kmsg. First two reboots I've experienced (that I know of) since I loaded 1/16.

Thanks. Lets hope ACL can make sense of it... definitely seems like something is awry, I don't ever remember this many resets.

I haven't tested the new build yet, I've been lost in HaRETland .

Edit - for anyone else having reboot issues, post as many logs as you can. I looked over huckl3b3rry's here, and it doesn't appear to have anything abnormal in it at all. It just stops...

[[ACL]]

Originally Posted by huckl3b3rry

OK. Here is last_kmsg. I just had a second reboot when I plugged in USB to capture last_kmsg. First two reboots I've experienced (that I know of) since I loaded 1/16.

This is going to be a tough one to catch. There is no errors in the log that stand out. Well there is this one but its no where near the end of your log.

[ 595.462371] pm_op(): platform_pm_suspend+0x0/0x58 returns -16
[ 595.462432] PM: Device alarm failed to suspend: error -16
[ 595.462463] PM: Some devices failed to suspend

When the kernel crashes, you get a kernel panic which doesnt reboot(just locks). Last_kmsg is key for this. But if the phone reboots, then last kmsg may not have anything useful since a9 may have crashed. When A9 crashes, we just reboot because we cant survive without it. A9 is the radio pretty much so we need to narrow this down and figure out if we can replicate this error.

[boggsie]

I need some advice on how to try and capture logs.

I experienced three spontaneous rebooted, today.

First event: Phone on desk, in sleep. SMS comes in, phone goes out of sleep, I hear my SMS announcement tone, pickup the phone as it rebooted.

Second event: Speaking on a call, in the midst of speaking, with the phone to my ear and the phone rebooted.

Third event: Incoming call while the phone is in my holster. I didn't recognize that taking the phone out of my holster has caused the phone to wake up. As it waking up, I press power (turning it off) and then power again, to turn it back on ... reboot.

So my question is: how should I go about trying to get logs for stuff like this?

Best regards,
-boggsie

Sent from my NookColor using Tapatalk

[arrrghhh]

Originally Posted by boggsie

I need some advice on how to try and capture logs.

I experienced three spontaneous rebooted, today.

First event: Phone on desk, in sleep. SMS comes in, phone goes out of sleep, I hear my SMS announcement tone, pickup the phone as it rebooted.

Second event: Speaking on a call, in the midst of speaking, with the phone to my ear and the phone rebooted.

Third event: Incoming call while the phone is in my holster. I didn't recognize that taking the phone out of my holster has caused the phone to wake up. As it waking up, I press power (turning it off) and then power again, to turn it back on ... reboot.

So my question is: how should I go about trying to get logs for stuff like this?

Best regards,
-boggsie

Sent from my NookColor using Tapatalk

As I stated above, the only way to get logs from a reboot are to pull last_kmsg. That's the only thing that will remain from a reboot...and it's not always available. Reboots are fun to troubleshoot.

[vzihome]

Just my 2 cents been on new build since 10pm last night, flashed it, put on charger and didn't touch it until 430am. Been messing with it through out whole day, no reboots, no lag, haven't oc'd (don't feel the need to runs like a champ.) No complaints so far...

Sent from my Touch Pro 2 using Tapatalk

[eurohunter]

Is the notification LED (green on sleep, orange when active) a tough issue to be fixed (too much work for such a small issue)? Or is it like that intentionally just for testing purposes?

[arrrghhh]

Originally Posted by eurohunter

Is the notification LED (green on sleep, orange when active) a tough issue to be fixed (too much work for such a small issue)? Or is it like that intentionally just for testing purposes?

Oh it's an easy fix... but it's for testing purposes. When sleep and everything related to sleep (pretty much everything...) is stable, userland notifications will be enabled a la XDAndroid HaRET builds.

[mbellot]

Two big bombs today.

First I couldn't capture because the phone was (I think) totally dead. It was plugged into a charger overnight, but it appears that something happened during the night to stop the phone from charging and then fully discharge the battery. Unfortunately the only way to get it doing anything again was a battery pull and then leave it on a charger for 20 minutes. battery pull killed last_kmsg for this one.

Second bomb was a total lockup when fully awake. last_kmsg attached, looks like something barfed big time near the end. Hopefully the log helps.