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
Related
Not sure if anyone else has this but after wiping and re-flashing my phone to correct a market issue it still exists.
Basically I only have 2 tabs in the market.
Just in
Top free
I seem to have lost my 'top paid' tab.
I KNOW it existed before but it seems to have dissappeared after ungrading my ROM.
It also makes my Market run PAINFULLY slow, it takes ages to conduct a search and when I select something to download it takes ages to bring up the 'permissons' screen.
Once it has brought that up and I select download it downloads in milliseconds, yet it does this for EVERY item I select.
I had this issue about 3 weeks ago for a week or so but when I nandroid restored it fixed itself.
Anyone have any idea what's going on?
a logcat would be helpful... had a similar problem once, my logcat showed a lot of socket exceptions... did a wipe and things were smooth again...
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
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging
This is one of the weirdest problems I've had. I'll try to be very specific. I'm running Android 6.0 on a Moto G 2014. I was just using my phone, on YouTube, when it decides to randomly reboot. Ok, just an error. Then I noticed that my phone's lockscreen never shows up anymore, and I can't pull down the quick settings. I thought it was just an error from the unexpected reboot it had, so I do a full reboot. No change. Okay, maybe clearing cache and dalvik will solve this. Cleared, reboot, Android is Upgrading, and no change. Okay, now I'm worried. So I restore a system backup from a month ago, reboot, and no change. I also tried uninstalling xposed framework, and no change. Now I don't know what else there is to do before factory resetting, because I really don't want to do that. By the way, here's all of the problems I've noticed since that reboot:
Can't pull down notifications.
Lockscreen will not show up at all.
Home button does not work at all, pressing it does nothing. I have to press back if I want to get to the homescreen.
"Developer options are not available for this user" error screen, even though I'm the only user
adb won't respond (probably for the reason above)
I get no notifications at all
I can't receive calls
Any tips or steps I should take to find this problem? Any help is appreciated.
Solved
Restoring System, Data, and Boot from early June took the problem away. But it bothers me that I'll never know what the problem was.
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater