• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help readings logs - randomly turning off Nexus 4

maleo77

Newbie
Hi,
I have a problem, i had android 4.3 and one day my nexus turned off. Now also randomly turns off. I thought it was an application, but I did the factory settings and I updated to version 5.0.1, but the problem is all the time.

I used logcat to see what turns off the phone, but I do not understand .. While debugging, I ran a few applications, wifi, mozilla, etc. and suddenly the phone turned off.

I put the logs, if anyone can help me out and tell me what is the reason for shutdown?

Thank you
 

Attachments

For troubleshooting reboots and the like, the /proc/last_kmsg log file can actually be more useful than a logcat. If you have a moment, try to pull that (adb pull /proc/last_kmsg) and share that here as well.

I'm about to run out to lunch, but I'll give both logs a read once I return.
 
Were you charging the device at the time?

I noticed this message shortly before the shutdown process started:
Code:
D/ThermalDaemon(  197): Sensor 'batt_therm' - alarm raised 7 at 79.0 degC

D/ThermalDaemon(  197): Sensor 'batt_therm' - alarm raised 6 at 79.0 degC

D/ThermalDaemon(  197): ACTION: BATTERY - Setting battery charging mitigation to 3

79*C is pretty toasty; it may have been shutting down to avoid thermal-related damage.

I did also see a LOT of errors spewed by an app with the package name "eu.livesport.LiveSport_cz.net".

You may want to try rebooting to safe mode for a bit to see if things are more stable with your apps temporarily disabled. If so, start working through to track down which app is causing the issues.
 
No, I did not load the battery at this time.

I have the same problem when I restored to factory settings - it was clear from the application. Then I turn off the phone or at night, where the temperature was low and there was no application because I made a system restore.

Now I am in safe mode and see if there are changes

safe mode = system after restoring the system?
 
safe mode = system after restoring the system?

Safe Mode basically just disables all third-party applications - so anything that you've installed. The core OS and Google apps will continue to function normally. It's a good troubleshooting step to confirm if a problem is caused by an app or the OS itself.

When you upgraded to 5.0, did you flash a factory image or install an OTA update?
 
I just clicked on 'Download', then 'upgrade', but this issue has already appeared on other versions - do you think that this software or hardware fault?
 
It's hard to say for sure at this point. If the problem continues in Safe Mode, it could very well be a hardware problem - or it could be a firmware issue.

It might not be a bad idea to flash the latest factory image for good measure (download it here, instructions here) so that you start from a known-good point. 4.3 -> 5.0 is a HUGE change, so it's possible that something got corrupted in the transition.
 
but this problem also was at the 4.3 so I was updating, thinking that this software fault
Yep, and it's entirely plausible that there was some piece of the software that was corrupted on 4.3, and that just persisted across the update. Flashing the factory image overwrites all the file systems, making sure that everything is as it should be. It's the fool-proof way to eliminate software/firmware problems. :)
 
i have a next problem... i made flash and when I run the phone, stop the welcome screen (flying dot) .. I waited an hour and nothing ..

I would do it again flush, but I can not detect the device (how USB enable debugging if you can not get to the phone?)
 
This is terrible! After flash etc..the problem is the same, it is also in safe mode - any idea?
So does that mean you got past your previous issue (being stuck at the welcome screen)?

I'm still a bit concerned by that 79C battery temperature reading that I saw in the logs...

In between crashes, could you try to install this battery temperature monitor and see what temperatures it sees?
 
The system is already ok, but the problem is still shut down.

At rest, CPU temperature ~35C, battery temperature ~39, and the phone also can turn off ...
 
I hate to say it, but you've eliminated just about all the variables that you can. It sounds like the problem must be some sort of hardware failure, and I'm afraid there's not really much that we can do about that. :(
 
Let me know if you upgrade to a new phone - I'm starting to feel the itch to upgrade from my N4, but I don't have a clue what would be next. I may try to stick it out for the NEXT Nexus in hope that it's a more reasonable size than the N6.
 
The Nextus(Can I trademark this?) is rumored to be from Huawei.

I think if I upgraded this year, it would be to a Motorola device of some sort. But I think I'll hang onto my N4 until it dies. No reason not to. I just dropped $$$ on a Nexus 9 this week, so I need to control myself.
 
Back
Top Bottom