My phone keeps randomly rebooting everyday. I think it's a voltage issue because it only happens under 50% but I need the location for where the last_kmsg is stored to confirm why exactly it's happening. It's supposed to be at /sys/fs/pstore/console-ramoops but ADB gives me a permission denied even on SHELL.
Related
So I have Cyan 5.0.6. I have trackball pro installed, no theme, and I've tried 3 kernels and wiped everytime. I've also started from scratch and did a full wipe of everything, wiped and formatted my sdcard, installed 5.0.6, and I still can't figure out these reboots. Can anyone at all take the time to check this log and see what might be causing it? I can reproduce it in time but it's different each occurance. One time i might open the widget dialog. Another when putting in the car dock.
I ran a logcat and caught it on a reboot at the very end. Any help and ideas is VERY greatly appreciated.
Thank you.
http://pastebin.com/mEhuHz4n
By any chance do you have a live wallpaper? I narrowed down my resets to the Nexus Live Wallpaper and it was only occurring if I tapped an empty spot on the screen by accident.
Nope no live wallpaper. Thanks for the thought though.
didn't notice any reboot in that log. (dont know how the lines are all joined into one insanely long line)
try getting the kernel messages:
adb shell cat /proc/kmsg
My CDMA Hero started rebooting randomly during the last week or so. I uninstalled all recently installed applications and the problem went away.
However ...
This has happened more than once, and it takes a lot of time to track down the offending app(s). I really want to know how to troubleshoot if this happens again.
If this were a Windows computer, I would go and get the minidump file and run it through windbg and it would suggest what module had caused the fault.
Is there anything like that for Hero crash / unexpected reboot? If not, what approach would you suggest for investigating these incidents?
Thanks,
Chris
Running DamageControl 2.08.1
Best thing i know to do is to run logcat with adb and try to recreate the problem.
Hard to repro...
Thanks, but the problem was so sporadic ... it would go hours, or even days, between reboots. Is it possible to use something like logcat to get the log files from *before* the current bootup?
im not that familiar with logcat, just search the string "Logcat Hero" on the Xda forums and you should be pointed in the right direction
Is there anything like /var/log/messages?
Thanks again. I went and looked at the logcat documentation and there are some options to get different kinds of output. However, I reset the phone (simulating a crash) and when that happened, the logs were cleared, so that there were no log entries visible via logcat that predated the shutdown.
Does anybody know where the actual log files are kept? There isn't a /var/log/messages or anything like that. Where do I find files equivalent to the "normal" Linux /var/log/messages?
Thanks,
Chris
Alright, I've been using Fresh Toast for about two weeks now and love every second of it..The phone is incredibly responsive and everything I could want in a Hero. But I've run into a few problems/questions.
1. What does the option "Fix apk UID mismatches" option do in recovery? I've searched and it seems the only explanation is "it does just that" but I don't know what that is or means..
2. More often I've noticed I've had the mobile network not responding and had to toggle the option off/on for things like internet to work, but after the toggle it works just fine. It hasn't really started to be annoying till recently. Is this a problem in 2.1? Or Fresh Toast?
3. Possibly in conjunction, my phone has restarted 3 times by itself today..just sitting on the table. What could be the reason for this? I haven't installed or changed anything for at least a week, and it just started happening. It can get to be annoying because it takes a few minutes to boot up and a little inconvenient..
From what I understand, the apps and stuff have ID's which the phone can confuse sometimes, causing force closes of stuff you think should work. Fixing the mismatches helps with the force close problem some have. This is based off of knowledge I have gained from using th search button, but I am not rude enough to tell you to do a search when I am already typng you a message.
The random rebooting sounds like a problem you might want to take to sprint...
and I personally have been having some issues with mobile network using regawMOD lately... I am not blaming it on the ROM, jsut letting you know that I am using a different 2.1 ROM than you... mobile network locks up, doesn't respond and I have to toggle airplane mode to make it work, or it's just murderously slow compared to other times, andall while in the same location: my computer.
the random rebooting may be your phone unable to handle high frequencies... use overclock widget, and bring it down a notch to 710 or 691, and try that. The uid mismatches, I think, is a linux thing... the uid of a file is its permissions, aka read, write, execute, etc., but don't ask me how they get messed up and need that (you root your phone through adb? remember typing chmod 755 blah blah? the chmod command changes uid's, and the 755 is telling it what permissions to give it, but I don't remember the breakdown of the number, still learning linux myself)
good day fellow razr i owners,
my razor i (91.2.26001.XT890.Retail.en.EU) is behaving very strangely since it got it back from support with a new mainboard. Sometimes it just freezes or crashes, and when I reset it, it's often bootlooping around the flashing M-Symbol with a little clicking sound everytime it starts over. I can get it to boot up if I keep resetting it, shutting it down, starting it again aso. I can get into fastboot and even then it's not certain that it boots up afterwards. I managed to get into recovery mode with a process log that started to overlap the lines of text. Sadly I can't manage to get that again for further troubleshooting.
The easiest thing would be to send it in, but I've already done that only to get it back with the comment "couldn't reproduce the problem, upgraded the firmware".
Since then I try to reproduce the crashes so that I can proof the defect even to a service team that starts it up, sees it works, shuts it down, flashing it and sending it back...
Crashes and/or Freezes can appear when I'm handling it or not. When I'm browsing with Chrome, using the camera, use Google Now, play Simpsons Springfield...
Sometimes background processes stop to react spamming me with messages like "the process com.google.process.gapps isn't answering" -> OK (translated from german)
Since these problems started after a motherboard change after a brick (downgrading from 4.1.2 to 4.0.4) I'm thinking it's a hardware problem.
I tried to create a logfile with adb shell dmesg > log but only got "klogctl: Operation not permitted"
It seems to start more reliable when not used for a while after a crash (cache clearing?) and it seems to crash more often when plugged in
factory reset seems to work for a while but after 2 days at most it keeps crashing/freezing again
I would love a fix for the phone, but I don't think there is much I can do when it's really a hardware problem so next best thing would be a way to get a error log, that I can send the support with my device as proof that there is a problem and all that obviously without voiding the warranty...
Thanks in advance for any help
Freeks
my L90 has randomly rebooted several times tonight.
I am on stock rom, not rooted. using T-mobile.
Does anyone know why it's doing this?
phone is not hot. Is it the sim card triggering reboots?
Is there an app to monitor reboots and error codes like Windows has ?
It could be the device itself but you never know until you find the cause. Does it occur after doing a specific action or is it truly random? As for apps I am unsure but adb logcat would show why it reboots. Which variant do you have?
ardentis said:
It could be the device itself but you never know until you find the cause. Does it occur after doing a specific action or is it truly random? As for apps I am unsure but adb logcat would show why it reboots. Which variant do you have?
Click to expand...
Click to collapse
can i use logcat to find why it rebooted yesterday? or does logcat have to be running in the background and catch the reboot in the act?
I installed catlog, and it is only showing the current log starting from the time I installed it.
i have the d415
it's random.
i caught the phone reboot once while running GPS Test.
Once while running camera. Camera was running and I set it on the table, lens facing down. Then it rebooted.
another time while it was plugged into my pc via usb. Screen was tapped off, and then I heard the reboot sound.
The odd thing is, I didn't hear the Windows usb disconnect ding dong sound when the phone rebooted as it usually does if I had manually rebooted.
I think it rebooted 4 times already.
For a while, I played with this phone without a sim card inside, and it never rebooted.
yesterday, I put a sim card in taken from my LG F6, and it rebooted randomly multiple times.
The L90 has a stupid t-mobile app service running, which my F6 didn't, and I can't kill it.
link626 said:
can i use logcat to find why it rebooted yesterday? or does logcat have to be running in the background and catch the reboot in the act?
I installed catlog, and it is only showing the current log starting from the time I installed it.
i have the d415
it's random.
i caught the phone reboot once while running GPS Test.
Once while running camera. Camera was running and I set it on the table, lens facing down. Then it rebooted.
another time while it was plugged into my pc via usb. Screen was tapped off, and then I heard the reboot sound.
The odd thing is, I didn't hear the Windows usb disconnect ding dong sound when the phone rebooted as it usually does if I had manually rebooted.
I think it rebooted 4 times already.
For a while, I played with this phone without a sim card inside, and it never rebooted.
yesterday, I put a sim card in taken from my LG F6, and it rebooted randomly multiple times.
The L90 has a stupid t-mobile app service running, which my F6 didn't, and I can't kill it.
Click to expand...
Click to collapse
You must catch the reboot in action with logcat and wait for it to reboot. You may want to talk to T-Mobile about the issue and they should replace it.