PhilosoRaptor

After months without a random reboot, my phone did it twice consecutively today while I was trying to navigate while streaming music (Pandora) on the way from the airport this morning. It worked perfectly on the 1 hour drive there (also on the round trip going there the previous week), but while I was waiting for the guys I was picking up at the arrival gate, I was browsing the web and still streaming music and my phone just did a "soft" restart (where it doesn't show the Moto logo, just the boot animation). Slightly annoying.. at least it gets to the launcher pretty quick still.

Then, maybe 30 mins later on the trip back, it does it again while I'm driving back . This time when it got back to the home screen, it refused to pick up any sort of cell signal like it was in airplane mode, but all the other radios were on (BT and satellite). Toggling airplane mode had no affect on it. So I had to totally reboot my phone to get it to work again.

I think it may be heat related, when it came back up the first time, SetCPU read the CPU at 51°C/124°F and that was immediately after reboot, so it may have cooled down some during that. After the second reboot I brought the clock down to 800 MHz from 1.1 GHz and it was good for the rest of the trip (another hour).

But I was running the exact same load/apps on it the last trip and the ambient temp in the car was the same. So I wanted to see if there some system log/app that can tell me what process forced the phone to reboot or maybe what the CPU temp was when it crashed, to rule out software. Is there anything like this?

If not, does anyone know what the max temp the CPU can handle before it forces a reboot? I'm sure there's a threshold for this, just like there is for PCs (but usually they just throttle instead of shutting down), but I don't know what it is. I would think ~60°C would be way too damn hot for a CPU in a hand held device.

Thanks in advance for any help!

Lock-N-Load

yep 124 is pretty hot & many times I have seen reboots because of high temps. for sure it was a temp issue. those things are pretty cpu intensive.

If you look at some of the SetCPU topics you will see battery & cpu max temps - I have forgotten. but 124 is up there and by the time you saw 124, it had even cooled some I bet, so I bet it was higher when it forced a reboot.

SetCPU is great for this exact issue as you can set a profile by both battery and cpu temp to scale back speed if either hits a certain temp. Mine are set at 120. I also use the app TempMonitor to flash red temp readings in my status bar at 113 and above just to keep me aware.

to answer your ? I have never seen such an app & would not load it if it did exist as it would run all the time in the BG eating resources.

__________________
TABLET: Asus Transformer Prime - rooted

PHONE: D1 + Pete's FRG01B | JDLFG's 32.25 1.25 | Pete's Baseband C_01.43.01P | My metamorph battery mod | Droid X Bootanimation

Last edited by Lock-N-Load; October 29th, 2010 at 03:47 PM.

PhilosoRaptor

Wow, I totally forgot SetCPU did the thermal profiles. I'll have to set that up for the next trip I do, thanks for the reminder!

Yeah, I know a service/app like that would put a decent load on the CPU/RAM too, but I would only run it while it's charging in the car (when it's most likely to reboot while I'm navigating and streaming) anyways, so that wouldn't be an issue for me.

Thanks!