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

Root Omap3 safe temperature range

B

biggdogg

Well-Known Member
CAN ANYONE TELL ME THE SAFE OPERATING TEMPERATURE RANGE FOR AN OVERCLOCKED DROID 1 OMAP3 processor. Ever since i switched to Chevys lv 1000mhz I keep setting off the computer temperature profile alarm in Set Cpu. I currently have it set to 250/900mhz on demand but when I download or run a computer intensive app it overheats. When I was on BBV04 I used Petes Kernel overclocked to 800mhz. I know all droids are different when it comes to kernels but there has to be a spec on safe range for the operating temperature of the processor and battery. Can anyone help me out?
 
According to the official specs on the droid's ARM cortex a8 processor, the operating temperature is 0C to 90C (194F) (standard applications), and -40c to 105C (extreme applications). The Droid's battery is rated at 60C (140F) so the battery will fry long before the CPU will. Bottom line is, we spend way too much time worrying about our CPU temps!
 
Thanks I appreciate the quick response. I can always change the specs on my Setcpu cpu temperature profile. The reason i was worrying is because the phone was so hot I could barely hold it! LOL, oh well, Im going to change kernels and see if that helps. Thanks again.
 
I have my SetCPU settings set to start downclocking as soon as it gets anywhere above 122 (50 C). If it runs for too long at or close to 140, (60C) then the heat will start heating the battery, and the phone will reboot. I ahve had it reboot a few times when trying to use Nav and listen to Pandora on an OC phone after Froyo came out - I learned quickly that I had to downclock it severely (to like around 600) and even then it was hit or miss - if it was in my dash in the card and the sun was heating it up, it overheated. I moved the dock so the phone sat out of the sunlight, and angled one of the middle car vents directly at it - that improved my performance significantly. no more massive over heating.

The CPU can take lots more punishment as mentioned above, but It still operates a lot better when below 140 (60C).
 
johnlgalt said:
I have my SetCPU settings set to start downclocking as soon as it gets anywhere above 122 (50 C). If it runs for too long at or close to 140, (60C) then the heat will start heating the battery, and the phone will reboot. I ahve had it reboot a few times when trying to use Nav and listen to Pandora on an OC phone after Froyo came out - I learned quickly that I had to downclock it severely (to like around 600) and even then it was hit or miss - if it was in my dash in the card and the sun was heating it up, it overheated. I moved the dock so the phone sat out of the sunlight, and angled one of the middle car vents directly at it - that improved my performance significantly. no more massive over heating.

The CPU can take lots more punishment as mentioned above, but It still operates a lot better when below 140 (60C).
Click to expand...

I have my Setcpu profiles set up and I have it set to downclock to 550 when the cpu temperature gets over 50 C, 122 F. I also have a battery profile set as well to drop the cpu to 550mhz when battery temp goes above. I have also had the phone reboot due to heat while in the car dock with the car charger plugged in running Pandora and Navigation.
 
I also use SetCPU to downgrade speeds when I get into the 120F range on the CPU.

this is one of the great aspects of SetCPU - you can protect your phones innards
 
I have had my phone go stupid on me a couple of times - particularly if several background apps are running.

I am currently using LFY 1.96 and the default 1000 MHz kernel as I really don't nee anything faster, an interactive scaling works wonders. My SetCPU profiles are still in pale though, to downclock on high temps as well as low batt power.

Now, if someone could figure out a way to write profiles based upon app being used, it would be perfect - I could force downclock whenever a particular app / combination of apps load(s) - and prevent all future errors.

But, yeah, SetCPU FTW.
 
johnlgalt said:
I have had my phone go stupid on me a couple of times - particularly if several background apps are running.

I am currently using LFY 1.96 and the default 1000 MHz kernel as I really don't nee anything faster, an interactive scaling works wonders. My SetCPU profiles are still in pale though, to downclock on high temps as well as low batt power.

Now, if someone could figure out a way to write profiles based upon app being used, it would be perfect - I could force downclock whenever a particular app / combination of apps load(s) - and prevent all future errors.

But, yeah, SetCPU FTW.
Click to expand...

Sounds like a great idea! As far as putting AC vents on the phone I personally wouldnt recommend cooling it down that quick, just opening the keyboard and letting room temperature air pass over it is probably safer.
 
Hi all. Sorry to crack open an older post but ...

One thing I've noticed about the responses here involve navigator and pandora.

I have my setCPU app to do the typical. Namely, down the processor to max 600 when temp is over 50 (celsius).

My problem is that I lose my connection to Pandora whenever this takes effect.

I'm on a Droid 2 and making use of battery saving mode. The screen doesn't go off (which would sever the data connection).

Any thoughts?
 
You must log in or register to reply here.
Back
Top Bottom