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

Overheating..

DFRESH

Android Enthusiast
Dec 26, 2009
559
39
The Bay Area SF/Oak
I wake up at 3am to find my phone overheating!

it was at 130 degrees! What was the problem? well...I forgot to close an application!

So if you have the gumbo kernel ...make sure you don't run any applications and leave them open....

So if you ever have the same problem, turn off your phone and place it by an open window and let it cool off for a good 5-10 mins..
 
Google Maps ......

but in the past before the kernel, i had applications running in the background and never had an overheating problem.

The only thing I could think of was the kernel ....I could be wrong..

but my phone was overheating....got scared for a sec, thought it was gonna fry all the way..

I noticed the led light was flashing, green/orange ....touched it, the thing was hot..

opened it and the battery widget by curve fish said "overheating" ..

but i really do believe the kernel and certain apps can lead to overheating..
 
Upvote 0
I thought the point of the kernal was to kill apps that were running in the backround? Does your phone not sleep when charging? If you have setCPU to ondemand it should automatically drop down to the min. when your screen is off.

I didn't know that, looks like I'm going to switch to ondemand ...

Yeah, do you have setCPU running in ondemand?

It's always on performance...but I'm going to follow what durandetto just said..
 
Upvote 0
To provide a bit of explanation, as I understand it, Gumbo is supposed to be fast because he disabled HTC's own (closed source) cpu throttling, aside from the memory management stuff.

>>>Kernel built with debugging and HTC performance lock stripped for full wake ramp up support<<<

He did that with the assumption that users would use setcpu's ondemand dynamic throttling to provide battery protection or the alternative...

>>>It's a kernel driven CPU governor. You can install setcpu to enable it, or
echo "powersave" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
from a terminal app on the phone.
<<<

It may also be important to know that he suggests not using setcpu's OnBoot function, and run setcpu yourself after booting, as needed...

Here was his recommendation:
>>>
Example use:
Get to work, drop governor into powersave and put the phone in your pocket.
At lunch, you want to reply to messages, surf, whatever drop it back to ondemand.
If you want to play robodefense at lunch, drop it to performance.
When lunch is over, back to powersave and in your pocket.

<<<

I suspect you could get 2-3 days of sporatic use with this thing if you kicked it into powersave most of the time you aren't using it (this is what i would do if I forgot my charger in a hotel in the middle of a 4 day trip)

Instead of copying and pasting all of that, I should just have said: read the first post on XDA carefully, then read pages 8-12 starting here.



Actually, that warning should probably be in the first post of that whole fresh+gumbo+setcpu thread before people burn their phones up.
 
Upvote 0
Before I loaded the new kernel, my phone did get very hot. The circumstances were: loss of signal and background data still on. As soon as I turned the background data off, the phone cooled down. I have only had one occurrence of running warm with the new kernel. The phone wouldn't sleep. it was awake 100% of the time. After a restart, the phone has been outstanding. I couldn't be more pleased.
 
Upvote 0
To provide a bit of explanation, as I understand it, Gumbo is supposed to be fast because he disabled HTC's own (closed source) cpu throttling, aside from the memory management stuff.

>>>Kernel built with debugging and HTC performance lock stripped for full wake ramp up support<<<

He did that with the assumption that users would use setcpu's ondemand dynamic throttling to provide battery protection or the alternative...

>>>It's a kernel driven CPU governor. You can install setcpu to enable it, or
echo "powersave" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
from a terminal app on the phone.
<<<

It may also be important to know that he suggests not using setcpu's OnBoot function, and run setcpu yourself after booting, as needed...

Here was his recommendation:
>>>
Example use:
Get to work, drop governor into powersave and put the phone in your pocket.
At lunch, you want to reply to messages, surf, whatever drop it back to ondemand.
If you want to play robodefense at lunch, drop it to performance.
When lunch is over, back to powersave and in your pocket.

<<<

I suspect you could get 2-3 days of sporatic use with this thing if you kicked it into powersave most of the time you aren't using it (this is what i would do if I forgot my charger in a hotel in the middle of a 4 day trip)

Instead of copying and pasting all of that, I should just have said: read the first post on XDA carefully, then read pages 8-12 starting here.



Actually, that warning should probably be in the first post of that whole fresh+gumbo+setcpu thread before people burn their phones up.

So you have to manually select different modes in setCPU? That makes a lot more sense, but confusing as well. I understood it as those modes were automatically selected by setCPU depending on what you were doing, I dont remember which mode I changed last but that probably explains why my battery was dead in about half a day.

I since deleted setCPU, and now my battery is better, but stil not a full day like I used to get. Plus the overheating. I will try reinstalling setCPU and messing with the different modes. I think ondemand might be the best overal choice for me since I use my phone throughout the day and never really have extended periods of time when I dont check it.

Thanks for the tip, rep point given.
 
Upvote 0
So you have to manually select different modes in setCPU? That makes a lot more sense, but confusing as well. I understood it as those modes were automatically selected by setCPU depending on what you were doing, I dont remember which mode I changed last but that probably explains why my battery was dead in about half a day.

I since deleted setCPU, and now my battery is better, but stil not a full day like I used to get. Plus the overheating. I will try reinstalling setCPU and messing with the different modes. I think ondemand might be the best overal choice for me since I use my phone throughout the day and never really have extended periods of time when I dont check it.

Thanks for the tip, rep point given.

From what I have read ondemand sets the cpu to your min. setting when the screen is off in stand by and to max when you are using it.
 
Upvote 0
So you have to manually select different modes in setCPU? That makes a lot more sense, but confusing as well. I understood it as those modes were automatically selected by setCPU depending on what you were doing, I dont remember which mode I changed last but that probably explains why my battery was dead in about half a day.

I since deleted setCPU, and now my battery is better, but stil not a full day like I used to get. Plus the overheating. I will try reinstalling setCPU and messing with the different modes. I think ondemand might be the best overal choice for me since I use my phone throughout the day and never really have extended periods of time when I dont check it.

Thanks for the tip, rep point given.
I had the same problem with setCPU, check out my last post in the setCPU vs. overclockwidget thread. Overclockwidget is waaaaay better on my battery.
 
Upvote 0
From what I have read ondemand sets the cpu to your min. setting when the screen is off in stand by and to max when you are using it.

Thats what I thought I read too, but I think what my problem was is that I thought the drop down menu settings all kicked in automatically depending on what you were doing. So I dont know which drop down item I had selected last.

I just failed to fully understand what it did and didnt do. Now I reinstalled it and changed it to ondemand at 480/160. I will see how that affects performance vs battery. I dont need super performance, but at least a little something to make all this tweaking worth it.

I had the same problem with setCPU, check out my last post in the setCPU vs. overclockwidget thread. Overclockwidget is waaaaay better on my battery.

I will check that out. Thanks for the tip.
 
Upvote 0
I wake up at 3am to find my phone overheating!

it was at 130 degrees! What was the problem? well...I forgot to close an application!

So if you have the gumbo kernel ...make sure you don't run any applications and leave them open....

So if you ever have the same problem, turn off your phone and place it by an open window and let it cool off for a good 5-10 mins..

try sand. I cant believe you didn't think of this already!?
 
Upvote 0
With WIFI tethering my Hero usually tops out at about 108 degrees after about 3 hours of tethering with it plugged to the wall, it usually only lasts about 2-3 hours if it is not plugged in. This is with Fresh 1.1, and Gumbo installed. I just installed setCPU, set to Ondemand 528/245 and have a full charge. I will post results in a couple of hours after some tethering.


EDIT: After 2 hours of steady tethering and phone calls while not plugged in i have been at about 95 degrees, and still at 50% battery life...so I would have to say setCPU defintley helps. Tomorrow I will try the same but while plugged into the wall.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones