Hi, I noticed that my device reboots from time to time completely unattended. Quite possible that it is frequent - last time it happened around 3AM and I would have completely missed it if there weren't a few apps relying on adb tcpip function which of course stopped working after reboot.
Does anyone else see this?
Related
Has anyone else noticed problems with CM crashing on their Atrix HD? I have been running CM on mine since September and have noticed the same problems in both CM 10.2 (epinter) and CM 11 (official). I never noticed any problems with the stock software. I have identified at least two different types of crashes.
Type 1 typically happens overnight when plugged into a charger (though less so with more recent builds) or when the phone is idle in my pocket. There is no notice the phone has crashed though sometimes if it happens in my pocket the phone seems to warm up somewhat. When I pull out the phone and press the power button I get nothing at all. This requires holding down the power and volume buttons for an extended period to force the phone off and then restarting it.
Type 2 typically happens when on an active phone call, though it can happen other times when using the phone as well. This involves the phone crashing and immediately going into a reboot (red M on the display as soon as I pull the phone away from my head).
I also have a less serious issue where when I press the power button to turn on the screen it will occasionally display the lock screen but refuse to take any touch input. I can usually get things to work by pressing the power button a few more times to turn the screen off and on again.
Just yesterday I switched to the new unified builds and have not seen all of these happen yet but I have definitely seen a type 2 already. Just wondering if these problems are widespread as I don't see them discussed a lot and if there's anything I can do about them.
Nothing? Am I really the only one having these problems? For the record I have now seen both types of crashes on the unified build.
May be you can try to flash stock rom:silly:
Try flashing the latest Validus ROM. I have been using version 4.3, which is based on KOT49H and it's been very stable with no crashes.
Is there a crash log that I can capture and review after a crash?
BenFranske said:
Is there a crash log that I can capture and review after a crash?
Click to expand...
Click to collapse
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
kabaldan said:
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Click to expand...
Click to collapse
Great, I'll check those out the next time I have a crash. I am thinking there will almost certainly be some useful information for the second type of crash where the phone actually reboots itself. I am less optimistic that there will be any information when it simply locks up and I'm forced to reboot it by holding power and volume down buttons.
kabaldan said:
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
Click to expand...
Click to collapse
Thanks for the helpful information there too. My sister has forbidden me from wearing belt cases for at least the last 10 years but it's at least nice to understand what the problem is!
Crash Logs
Sorry it took me a while to get back to this. I've attached a few crash logs that I captured last month. I have updated the OS several times since then but I'm still experiencing both of the types of crashes I originally mentioned. Any assistance in interpreting the logs is appreciated!
Any ideas about what might be causing these crashes and reboots?
Am I really the only person with these issues? How can that be?
I've just experienced some major screen tearing on my Moto X. It's the first time it's happened. Every animation was tearing to some degree, most of all the notification tray. I rebooted the phone, and terrifyingly, it continued. Then, it just stopped about a minute later. I've no idea why or how it persisted across a reboot and then stopped. Now I keep picking up my phone and testing it every few minutes. Has anyone noticed this themselves, on either 5.0 or 5.1? What causes this type of thing to occur randomly and temporarily?
AbsorbingCertainty said:
I've just experienced some major screen tearing on my Moto X. It's the first time it's happened. Every animation was tearing to some degree, most of all the notification tray. I rebooted the phone, and terrifyingly, it continued. Then, it just stopped about a minute later. I've no idea why or how it persisted across a reboot and then stopped. Now I keep picking up my phone and testing it every few minutes. Has anyone noticed this themselves, on either 5.0 or 5.1? What causes this type of thing to occur randomly and temporarily?
Click to expand...
Click to collapse
Yeah I have the same problem. It seems to have started since I updated to 5.1. It's been a constant thing for me for a few months now and it just comes and goes. I have no idea why it happens. I'm assuming it's just the OS being glitchy. I know the nexus devices should be getting 5.2M betas soon. So hopefully 5.2M official release for moto x will fix the issues. (It will be quite a wait I assume. I hope not.)
I'm really stumped here. I haven't been able to find any solution to this issue through searching, so I figure I might as well post something about it.
For the past few months, I've been having an issue with my watch screen turning itself on then dimming after a few seconds. This seems to occur every few minutes or so even when theater mode is enabled and when always on screen and wrist gestures are disabled. This issue persists even after unpairing with my LG G4 and after a factory reset (on both the watch and phone). It should also be worth noting that I have recently rolled my phone back from the latest VZW Marshmallow OTA to a rooted 5.1 image in an attempt to resolve the aforementioned problem, but from what I can tell, it has only become worse.
From what I've been able to gather from battery/wakelock monitoring apps and bug reports is that the phone is regularly sending wake requests at semi-regular intervals. I have not installed any third-party wear apps and I've disabled pretty much every Google sync function but the problem persists.
I am at wits end here as to what I can do here. This coupled with my phone suddenly developing a severe wakelock problem has made me seriously consider switching to another manufacturer, and this time I may not exclude Apple as a choice.
Has anyone else experienced an issue like this that might have some insight as to what's going on?
Thanks!
PS: If needed, I can provide the full bug report along with a quick spreadsheet I made to organize the kernel wake source info found in the report.
I am now experiencing occasional freezes while in some apps and also when in the system settings. This just started with the Oct security update. Trying to move ahead in the app or back out does not work. Sometimes hitting the icon to show all open apps will work and I can close all. Other times i have to hit the start/shutdown button in the back briefly to unfreeze the phone. Anyone else experiencing this?
No issues for me... but I've used adb to debloat my device, which *could* be making a difference...
If you can repeat the steps that consistently result in a 'freeze', you could start a logcat prior and close after, it may point to what's causing the problem.
That's the problem. It is random.
I have a WW model still on version WW_16.0631.1910.64 (rooted). Currently having a few oddities and wondering if an update might help?
Some of the things I’m noticing:
System Ui randomly stops working.
Phone calls and text messages dont come through, I have to reconnect via toggling airplane mode every 30ish min to ensure they come through.
A recent reboot has me in a extremely slow and unusable state where I had to reboot again.
I see some posts about people updating to 10 and they had battery issues, is this something that everyone seems to experience? If I give updating a shot, how would I update and keep my root/data?