So I'm looking for info on how to actually diagnose random rebooting.
I've seen the posts that recommend factory reset and swapping battery and disabling apps one by one.
But that isn't diagnosing the problem. I'm interested in how to actually diagnose and figure out what is causing the reboot.
I figure there are some logs or such that I should be perusing and there must be some resource that helps you interpret them.
Can anyone point me in that direction?
So I thought I'd follow-up on this.
I never did find out how to diagnose it properly.
New batteries helped for a while.
But now I get the dreaded emmc read failed message.
So I've sent my note4 to samsung for repair.
Started this thread instead if you'd like to follow:
https://forum.xda-developers.com/note-4/help/motherboard-replacement-source-t3824556
Related
I've run across a problem that seems to come up fairly frequently and I've done some searching, maybe *link* would fix my problem? Not sure.
The problem then becomes the fact that I don't know exactly what is being done or where it is being done. Would anyone care to enlighten me?
I tried entering some stuff in the adb command prompt on my pc when my phone was hooked up but I'm never sure when things are actually taking correctly, nothing has helped fix it so far.
Wow, since I apparently can't link to another thread even on this board since I'm a new user you guys can't even see what I've found...
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
Hi everyone,
I have encountered a really annoying issue with my HTC One. It is a completely new replacement unit, and ever since I started using it I've had problems with the reception. In the beginning it only lost reception for a short while, and then regained it. Now however, the loss of reception is almost always followed by an immediate reboot, and after this reboot the phone often will not allow me to enter any pin at all. It will just show a "no reception" symbol in the status bar and subsequently reboot again after a minute or so. This boot loop continues until the phone actually allows me to input the pin again, after this the phone will work fine for awhile until this looping business starts anew.
I've actually tried a whole lot of different roms and radio versions in order to try to solve this issue, but to no avail. I've also used an RUU to reset my phones firmware from the very beginning, but the problem still remains. I've also tried to swap sim cards, no luck with that either.
I've tried to check the logs after these reboots, and the only things that seem to have anything to do with this are the lines: "failure to start external modem" and "MDM common shutdown".
Am I out of luck here? Is there anything I can do in order to try to fix this myself?
I'm afraid that if I hand it in for repairs the shop won't actually experience anything wrong with it, since this happens so randomly, and just send it back to me with a service fee.
Help is much appreciated!
Anyone? I've made a logcat log of the error tagged-messages that occurs right before a restart:
i.imgur.com/z5srdT3.jpg (I'm not allowed to post image-links since i don't have enough posts)
Bump.
So i posted this in the Unoffical Xposed Lollipop thread but i figured i'd make a new post since it isn't really related. Looking around i also can't really find similar issues to try to diagnose and solve myself unfortunately. Today after testing out GB on my S5Active and then removing it, since i found no real use other than slowing my system down i found myself with an interesting new Xposed log after, my phone ended up bugging out asking me to "Sign into a network" that i already had internet access through and been set up. It then restarted itself and sat in boot. Wouldn't finish so i pulled the battery and it started back up, checked the log and this issue started arising. I'm not even certain GravityBox is the culprit, but i got a damn good feeling considering how it's supposedly not TW compatible even though a bunch of TW users are posting about their successful experiences with it.
So, Since i lack an Nandroid backup because i had already lost everything previously including Nandroid in previous issues, would my best fix be reset and start from scratch for the third time? Or is there anything from the tombstone & log that would help figure out a solution rather than a fresh start.
Tombstone & Log attached
Edit: also it's on boot when this appears, doesn't really seem to effect anything. And only other thing I could see it maybe coming from is me editing my .xml for sd permissions, but I don't quite understand the code.
Xposed Framework crashing. You should contact the devs of framework for Samsung devices, or visit respective thread, to provide details.
Hi everyone so recently my bluetooth has been really unstable. It is extremely frustrating as it will stutter, stop, unpair, turn off and on and right now it won't let me turn it back on. This is preventing smooth music playback. I have done literally everything, clearing cache to factory resseting and to no avail nothing has worked and I'm at the end of the line with ideas and frustration. If anyone can help at all it would be much appreciated. I'm attaching an image of what it looks like when I try to turn bluetooth on and it won't turn on. It greys out and nothing happens, won't turn on, search for devices or anything.
That certainly sounds awful. The last thing I'd try is doing a reflash of your firmware, to see if that helps (maybe something got corrupted along the way, and this should solve that). If that doesn't work, then you might just have a hardware issue. If you're rooted, you could investigate further... I'd start by looking at the logs in the phone to see what's erroring out...
Yeah I have tried refreshing the firmware so I'm guessing it is a hardware issue... but it's happening with the pixel line of phones. But how would I check the logs? Thank you so much for your input!!! I really appreciate it
Refreshing the firmware (or factory reset) is different from reFLASHing the firmware... I just want to make sure you tried the reFLASH.
Wait, is the issue with the Pixel phones, or the Samsung (this forum is for Samsungs).
Also, is it possible that the bluetooth device could be the issue? Does the device work reliably with other phones? For example, my company had many issues with Toyota bluetooth on the company cars and Android phones... this was a few years ago. It's because Toyota didn't follow the standard properly. Other people had issues with Nissans. Again, these were older cars, but the point is that the device was the problem, not the phone...
No the device is fine it's just the phone, I know this because another device works fine with it and even with a car pairing or another BT speaker have the same issues.
Have definitely tried to reFLASH the firmware and I was just saying this problem also seems to be common on the pixel line as well.
Would you recommend to check system logs to see if it's a hardware issue?
Checking logs (like dmsg) is one place to look... to see if there are any warnings and errors in there. I don't have any specific guidance on how to do this or what to look for, but that's where I'd start. I don't know if you can find dmsg logs without root (I tinkered with that in my previous phone which was rooted, but I didn't use it much so I don't have much guidance to offer... you will likely need to read up on what these logs have, etc).