Quote:
Originally Posted by arrrghhh
Hrm... interesting. I'm certainly no expert, but these logs show some serious issue. I just wish I knew what the issue was  .
Logcat seems to show that the CPU is pegged, and can't do anything. I also see where the kernel tanked, probably the reason for the SoD. Interesting that adb worked - I don't think this condition was created from poor signal.
Edit - I suck at following logs . What were you doing right before it started acting haywire? I see a bunch of stuff like a task killer running, twitdroid, some SMS messages...
No matter how you slice it, in your logcat there's a TON of "CPU pegged" messages, blocking stuff&things from happening . |
I was using the phone talking, got off and hit the power button which is remapped to hang up per F22's rootfs and startup.txt addition, have used it in the past and no issues. As far as sms messages, they may have been coming in along with twitdroid getting messages, I do have taskiller also. And I agree, there were tons of CPU pegged all thoughout it. I wasn't even pressing a ton of buttons on it trying to make it do a million things at once. Maybe I'll try removing taskiller and see if that improves it at all, although this isn't a regular occurrence.