Having issues with my phone crashing randomly, I recorded a logcat before the crash trying to get information but I have no idea how to read it. Maybe someone can help out.
Thanks
Describe "crash"
rootSU said:
Describe "crash"
Click to expand...
Click to collapse
Will be doing something and the phone will just shut off. Varies on what I'm doing...browsing chrome... Playing a game...etc. Then phone wont come back on unless I plug it in. The battery is never dead when it shuts off or when I plug it in and reboot it.
Have a look at last_kmsg log immediately after it happens. Logcat only really shows what android is doing not what kernel is doing.
too much
Code:
E/PowerHAL(753): touch_boost: failed to send: No such file or directory
messages, I know it;s not much of an issue and that the mpdecisions are trying to overwrite and thus failing, but try
1.Changing kernel
2.Reverting to stock
Related
Hi,
I have an issue with my Desire, it randomly reboots atleast once an hour
I have tried running a logcat, but heres the problem: When the phone has power connected it won't reboot.
So how to I catch the last entries in the log?
aLogcat wont work since it only save the log file every 15 minutes.
Anyone?
DISCLAIMER:
I am running CM7#36 and I know it has those issues, others have reported them. And I'm confident that it will be solved in a future release. But I would like to know anyway how or if I can get a logcat without power connected or what type of file that could be usefull.
I've looked around, but can't really find much information about this. When viewing logcat logs(via an app called aLogcat), every 5 to 10 seconds, i get the three errors listed below:
08-24 17:32:14.605 E/TrafficStats( 2906): Tx(pdpbr0) 72
08-24 17:32:14.608 E/TrafficStats( 2906): Rx(pdpbr0) 100
08-24 17:32:14.608 E/TrafficStats( 2906): dpram_stat: pending UL 0 (@4926) pending DL 0 (@5360)
For what it's worth, pid 2906 in the log above points to: com.android.phone
I am currently running on Humble 1.51, with CWM from 08-17(Orange, with restore capability). However, i've noticed this on previous versions of humble/cwm as well. I just did a factory EE4 install via Odin with .pit file, then installed an old humble (1.33) with the same results. I've tried removing the SD card completely, and it still pops up.
If I look at the network usage in Spare Parts, I see that 'Dialer' is always at the top. It sounds like it may be related, as there was a similar discussion in this thread.
Does anyone have ANY idea why the constant "E/TrafficStats" messages might be happening? If not, any idea what I can do to get more information on what is causing it?
I to noticed this and am very curious as to what it is?
I'm not sure what is causing it, unless it is some sort of hardware defect? It makes me feel better that it isn't just me though
Sent from my SCH-I510 using XDA Premium App
it's mainly debugging stuff from what i can tell, and it isn't breaking anything, just annoying when looking through logcats.
The thing is that not everybody gets those messages though. I've seen other charge users' logcats, and they aren't in there, at least not nearly as often. I've noticed that it does seem to be greatly diminished when the phone hasn't recently been used, but not consistently. For example, last night it ran from 11:30 to 2:30 without a single message. Then, it started occurring every 2 to 5 minutes. When the phone is being used though, it is consistently every 5 seconds.
The only way i've found to prevent it is to turn on airplane mode, then restart, as the numbers after pdpbr0 or pdpbr1 are like some sort of counter(they never go down, only up). Obviously, that isn't ideal.
If you have logcat look at the radio buffer instead, you will see messages that coincide in frequency with the trafficstats for "[GsmMultiDCT]NetPollStartTimer: posting again for netStatPollPeriod", with the same UID as the trafficstats.
imnuts, do you know of any tools/apps for me to investigate this further than just looking logs?
You could start decompiling framework .jar files and searching through the resulting smali output for TrafficStats to see what is creating the lines and potentially how to stop them.
Hi, So I have been fighting the dreaded random reboots for the last few weeks and despite factory resetting and loading a new ROM etc. I can't get to the bottom of it.
It only seems to happen when not connected to Wifi, when I am out and about and strangely most commonly when I am out jogging.
I was thinking it was something to do with the phone's radio's just because it doesn't happen when I'm using it or when it's connected to Wifi but this is just a noob speculating.
Anyway, I found some instructions on how to pull a LAST_KMSG file and I have attached it from the reboot that happened this morning. Problem is I have no clue what I am looking at so I'm hoping one of you clever people can tell me what it means.
Thanks for your time and help.
I've had my phone since March and never really had any problems with it. It would crash and restart every once in a while, but not too often.
Now, it crashes and restarts multiple times over the course of a day. I think it started happening after I updated my phone to build G930FXXS1BPJ1.
One day my problems were so bad that I couldn't do anything on my phone. It would lock up and restart every two to three minutes while I was using it. I was tired of that so I did a factory reset. My phone behaves a little better now but it still crashes many times a day. Even when it's in my pocket.
Is there any way I can trace the problem back to a specific app or firmware problem? I'm comfortable with using command line tools.
maybe try to gather logs just after crash? There could be some info of problems leading to reboot
Sounds good. How?
Steven Liekens said:
Sounds good. How?
Click to expand...
Click to collapse
adb logcat > d:\logs.txt
Click to expand...
Click to collapse
where d:\logs.txt is path to file you want to save as. Don't save on c:\ because it results in 'access denied'. To use adb you have to install ie. this
I restarted my phone and let logcat run until my phone crashed. Here is the log. I'm not sure what to look for.
https://gist.githubusercontent.com/...d0050685c37e2268224e8be70f1a51eb8c/logcat.txt
Hi all. I have Nokia 8.1 for a few months now. Updated to Android 10 immediately and it has been rock stable. Until today.
At about 11am I heard an incoming message notification but was busy and decided to look at it later.
At 11:55am I picked the phone but could not wake it up - tapping didn't work, fingerprint didn't work. Black screen. So I long-pressed the power button and it booted up.
It is working fine since but I'm somewhat concerned about the issue.
I collected a zip log file through "adb bugreport" command.
As I understand, it's tricky to find the cause after the reboot because all log files are generated fresh after boot. I looked in \FS\data\tombstones folders and found three records there, all complaining about the following issue:
Code:
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'FORTIFY: %n not allowed on Android'
But they are almost a month old and I don't remember anything weird happening at that time; except maybe some Android system update and manual reboot.
Is there any place in that log zip or somewhere else on the device (without root) where I could find some info about what happened right before the unexpected shutdown? Kernel panics? Crashes?
Hmm, nobody? Does it mean that everybody else is just ignoring random shutdowns and have never attempted to debug the problem?
AFAIK logcat output isn't persisted over reboot, and maybe that's one reason nobody replied to this thread. But you can always write log to a file every time your phone boots (via shell commands etc) and just check out that file once phone rebooted.
Regarding kernel log, /proc/last_kmsg or /sys/fs/pstore/console-ramoops might be helpful.