Ok..everybody knows about batterstatus and its amazing overclocking abilities. With this known, my question is, what is a good temperature range with the batterystatus temp monitor...are there certain temperatures that we need to become cautious with? ...I personally am at 260MHz and usually range anywhere from 32 to 80 degrees celsius.
Also, I personally am from Houston, TX...a VERY hot region. Could this also have an effect? What temperatures would be getting dangerous for the wing to be at?
Is it possible to fry a wing? lol =o
Thanx
Although our wings have a default speed of 400, under clocking too 260 would save you a lot of battery power in the long run.
Now if your talking the T-Mobile wing your in the wrong forum Try the Herald one I believe it is.
Now temperatures are trickey, this is a phone and has several different things to pay attention to. Theres not an active cooling system to dissipate the heat your creating. If you think about what temperatures most PC's start to have issues at and use that as a guage you should be okay. The materials and battery could start being affected if you take it too high.
I would personally get worried if it hit the 60c stage. However your best option is to look at what temperature it is with the stock speed on a hot day after some heavy usage to heat everything up. With that in mind then you can guage how high to overclock your phone.
Hello there,
I am having HUGE overheating problems. Last week I was having issues with random restarts and generally slow operating, but I realized that this is only when the temps are high. Ive seen my temps on my SetCPU widget get over 100 degrees Farenheit! Basically, I cannot use the phone at all when it is charging, and have to repeatedly put it in front of a fan or near an AC vent to keep using it throughout the day. I recently bought an extended battery. Could this be the issue?
Is this hardware or software related?
Any help is greatly appreciate, please let me know if I left out info
Eugene
Ok a hundred degrees for your phone isn't that bad.. But you need to make sure that you stop overclocking it when you charge it. Charging is the main thing that heat up that big ol battery on the back. Plus this combo with overclocking hurts. I have the same problem sometimes.
Hoped this helped a bit
sent from superfroyo dream
Slow the CPU down! You are using a community ROM that runs the CPU at 528 MHz. There is a REASON why the OEM runs the CPU slower than that!
And as for your huge battery... yes, that can make heat. Try with a NORMAL battery and see if the problem goes away.
on SetCpu I have been using the recommended settings, which I believe was 576Mhz maximum. Should I just not run SetCPU at all? (charging nor not)
Like lbcoder said. He knows what he's talking about. You can use setcpu still. But its meant to only run at those speeds only short bursts. So don't have it clocked at 576mhz all the time. You might want to cut it back to 528mhz anyways. But definitly the combo of the fat battery overclocked and charging will heat your phone up big time. I have the same problem as you sometimes. You just have to get used to switching cpu down in your settings. When your not using your phone and need speed.
sent from superfroyo dream
Lo N Slo said:
on SetCpu I have been using the recommended settings, which I believe was 576Mhz maximum. Should I just not run SetCPU at all? (charging nor not)
Click to expand...
Click to collapse
576? That's gotta tell you something about the program... the CPU's maximum is only 528!
Mine runs at 614mhz max... don't have any issues yet... the problem is that it may damage other electronic parts of the phone, not the cpu itself. anyway it isn't an expensive piece of hardware... it;s interesting to see how far it can go
So I am in fact running the 900mhz kernel right now, and the CM6 kernel on my Droid is running at around 1ghz with lowered voltages (hand tuned). I can't help but wonder, however, if doing so is safe for the future of the device? The manufacturer obviously knew what voltages and frequencies were most stable and safe for the longevity of the processor--and they likely spent a long time, with expert developers, working on getting the most speed and battery life out of the processor.
Who are we to suddenly decide that it can run faster and on lower voltages? No offense to the hard work put into the screamer kernel, as I am using it myself, but ever since the slow and painful decay of my Nvidia 8600GTS due to lowered voltages from the PSU over time, I've felt iffy about doing the same to devices that lack any cooling mechanisms.
So I'm curious: What risks do we incur by running an overclocked kernel? How can we detect the onset of long-term damage?
The main risk is damage to the CPU(electromigration if overvolting), but its hit or miss, depending on the quality of your particular chip. Undervolting can help minimize electromigration.
In general, overclocking will shorten the life of the unit - but by how much is difficult to say. I had a desktop PC that I ran overclocked for over 8 years with no problems and its still works today - a lesser chip might have been damaged in a year or less. If your CPU is marginal to begin with, it could fail in a short amount of time - days or weeks.
There really isn't any way to tell if its being damaged until its too late, but heat is a good indicator. If your unit feels excessively warm, then its life is probably being reduced - but it may be reduced from 20 years to 10, or from 10 years to 5 by which time the unit is obsolete anyway.
A close examination of the manufacturers data sheet would be in order to get a better idea of the life expectancy of the chip with the MTBF(Mean Time Before Failure) parameter in particular. Thats if this information is even available - some manufacturers do not publish it.
Like Jack - i have overclocked for years. I will say this. I have had Intel, Via, and AMD cpus, and not one has EVER failed from overclocking (and i took an AMD opteron from 1.8 to 2.8Ghz, for 3 years straight).
Honestly, the only real world risk you face, is if you run a CPU beyond its overclock limits. If your system (any system in general) is unstable, and you dont adjust it, you risk damage. Otherwise, you are fine.
vapor63 said:
So I am in fact running the 900mhz kernel right now, and the CM6 kernel on my Droid is running at around 1ghz with lowered voltages (hand tuned). I can't help but wonder, however, if doing so is safe for the future of the device? The manufacturer obviously knew what voltages and frequencies were most stable and safe for the longevity of the processor--and they likely spent a long time, with expert developers, working on getting the most speed and battery life out of the processor.
Who are we to suddenly decide that it can run faster and on lower voltages? No offense to the hard work put into the screamer kernel, as I am using it myself, but ever since the slow and painful decay of my Nvidia 8600GTS due to lowered voltages from the PSU over time, I've felt iffy about doing the same to devices that lack any cooling mechanisms.
So I'm curious: What risks do we incur by running an overclocked kernel? How can we detect the onset of long-term damage?
Click to expand...
Click to collapse
Overclocking itself wont shorten the life at all. The extra heat is what can cause damage but I don't think you'll be anywhere near the edge of the thermal envelope as these nooks just don't get very hot. Over-volting will also shorten the life some, but I can tell you based on experience as a semiconductor reliability engineer that if your cpu dies due to a minor over volt or heat from overclocking that it was going to die anyway. Electromigration will take many years. What will kill it is heat/cool cycles, and an overvolt and/or overclock will make it hotter and increase the temperature delta on a given heat/cool cycle. All of these chips go through Burn in, which is a high temperature overvolted test to weed out infant mortality chips, so they've already seen a much higher stress cycle than can be done to them via firmware when installed in a nook.
No offense, but who cares, lol. If it lasts 2 years I will be happy. I havent kept a cell phone longer since my first nokia brick phone. Besides, I'm sure by that time it will be sereverly outdated and in need of replacing anyway.
JackOnan said:
The main risk is damage to the CPU(electromigration if overvolting), but its hit or miss, depending on the quality of your particular chip. Undervolting can help minimize electromigration.
In general, overclocking will shorten the life of the unit - but by how much is difficult to say. I had a desktop PC that I ran overclocked for over 8 years with no problems and its still works today - a lesser chip might have been damaged in a year or less. If your CPU is marginal to begin with, it could fail in a short amount of time - days or weeks.
There really isn't any way to tell if its being damaged until its too late, but heat is a good indicator. If your unit feels excessively warm, then its life is probably being reduced - but it may be reduced from 20 years to 10, or from 10 years to 5 by which time the unit is obsolete anyway.
A close examination of the manufacturers data sheet would be in order to get a better idea of the life expectancy of the chip with the MTBF(Mean Time Before Failure) parameter in particular. Thats if this information is even available - some manufacturers do not publish it.
Click to expand...
Click to collapse
Extra heat is generally what kills ICs faster when overclocking, which is why if you don't/can't/aren't able to undervolt you need good cooling... no choice with the NC though as it's got to be undervolted to OC as we've no idea at all what the thermal budget of that package is, but I'd imagine that they're probably right on the edge to begin with even at 800MHz.
Some of my prior tablet I could feel warming up in the summer, harder to tell now with winter but my gTablet seems to get a bit warm at times when stressed...
From my experience in many years of CPU overclocking in computers, overclocking does not generally cause damage. Upping the voltage, and in turn the temperatures as well, can definitely damage the unit.
If you run into issues simply from overclocking they will likely just be instability, but no damage is likely to become from it. That is unless you are upping the voltage.
There are certainly many variables as well, and no two systems will be exactly the same.
As far as make sure that it is safe, I wouldn't push it to far, and if you do, it will not be stable. Saying the B&N chose the best or most stable frequency is somewhat silly. Just like we know full well that AMD and Intel have massive overclocking headroom as well.
Overclocking should be fine. I've been doing this on PCs since 1995/96 era. Never had one fail on me. As long as their is proper cooling or voltages are not too high, there is no issue. The key is to increase the CPU multiplier when you can, as opposed to voltage... but the tolerance of the hardware is pretty good.
No need to worry.
As for the manufacturers, they do the same thing. The buy a vanilla processor and depending on what they need on the market, the bump the speed. This allows them to buy one chip instead of ordering many types...
nootered said:
From my experience in many years of CPU overclocking in computers, overclocking does not generally cause damage. Upping the voltage, and in turn the temperatures as well, can definitely damage the unit.
If you run into issues simply from overclocking they will likely just be instability, but no damage is likely to become from it. That is unless you are upping the voltage.
There are certainly many variables as well, and no two systems will be exactly the same.
As far as make sure that it is safe, I wouldn't push it to far, and if you do, it will not be stable. Saying the B&N chose the best or most stable frequency is somewhat silly. Just like we know full well that AMD and Intel have massive overclocking headroom as well.
Click to expand...
Click to collapse
No. The 3621 was just left at AFAICT the "as sold" max clock for that particular SoC, which is probably as much a means of product differentiation was using the SGX530 was instead of the 540...
My guess would be that it can probably perform in the same range as the 3630, but additionally it might have had lower thermal specs listed which would also need to be accounted... but you're probably OCing usually doesn't harm anything, but if you're worried I'd keep an eye on the temp sensor every once in a while... (Used to OC my Palm IIIx all of the time, actually underclocked it as well when I was using it for reading...)
I see that the stable 1GHz and 1.1GHz kernels slightly overvolt(to 3630 values) so it would run a bit warmer... doesn't seem to be a problem for anyone yet, but I wonder if anyone's OCing one where it's actually even remotely something like warm ATM...
My Galaxy S just died on me after 8 months. Coincidentally, I had just overclocked it to run at 1.2GHz and unvervolted it at about -50mV across, just a week before it died.
Would this have killed the phone? It died when charging and not when in use. I also noticed that the temp was kinda warm as well (not sure if this is the normal raised temp during charging).
For that matter, I'm also not sure if it was the processor that died or some other component on the board. There is no signs of life at all......
I did notice even before rooting, the operating temperatures can go as high as about 58degC and the phone would shutdown at times at this range. (temp obtained using a system monitoring app)
What is the usual operating temps for phones? Or should i ask, what is the max operaing temps for phones? Did I get a lemon to begin with?
Thanks
bobzdar said:
Overclocking itself wont shorten the life at all. The extra heat is what can cause damage but I don't think you'll be anywhere near the edge of the thermal envelope as these nooks just don't get very hot. Over-volting will also shorten the life some, but I can tell you based on experience as a semiconductor reliability engineer that if your cpu dies due to a minor over volt or heat from overclocking that it was going to die anyway. Electromigration will take many years. What will kill it is heat/cool cycles, and an overvolt and/or overclock will make it hotter and increase the temperature delta on a given heat/cool cycle. All of these chips go through Burn in, which is a high temperature overvolted test to weed out infant mortality chips, so they've already seen a much higher stress cycle than can be done to them via firmware when installed in a nook.
Click to expand...
Click to collapse
The concern with OCs is mainly a heat issue, but even then as long as you stay within the thermal limits of the chip, you'll be fine. I remember once finding my moms K6-2 heat sink so clogged with dust that the fan was doing nothing. The system crashed from time to time, but once I cleaned it out, it ran just fine again. Not the best recent example, but I do know that the A8 is designed to hit faster clocks than 800, so running at 900-925 isn't a big issue. Also, unless you do nothing but games, your A8 isn't running at 900 most of the time--it just goes there when itneeds the power, then drops to 300 or 600 (which really saves battery). If you like, there is a few decent monitoring apps/Widgets you can run that show speed and temp. Most of the time, I don't think the A8 even reaches 40C, which is just a hot day in the summer where I live.
I had to check, but one such app is called Temp+CPU V2. Its free in the Market.
bobzdar said:
All of these chips go through Burn in, which is a high temperature overvolted test to weed out infant mortality chips, so they've already seen a much higher stress cycle than can be done to them via firmware when installed in a nook.
Click to expand...
Click to collapse
Thanks for bringing this up. The OMAP processor in the Nook was run through a Burnin temperature of over 120C (~250F). The only temp sensor we've got on the Nook is for the battery, so we should assume a 10C - 20C delta between the battery temp and the processor temp. Therefore, if you see a battery temp of 100C - 110C (>200F), your processor is about to experience catastrophic failure.
It's very likely that setup (late mode) timing violations will cause your Nook to lock up or decode instructions incorrectly (causing force closes) well before your processor takes heat damage. The unfortunate circumstance is when the Nook locks up while its unattended, leading to vicious overheating; this has happened to me once. When I returned to the Nook after a night's sleep, it was locked up, and upon rebooting, the battery temperature was 120F. At that temperature it's the battery's lifetime you worry about, not the processor.
higher power, shorter battery life, timing violation
The power consumed by the NC is proportional to volt squared times the frequency. By overclocking, with mostly likely an increase in voltage, you will have to charge the battery more often, hence shorter battery life. (The number of recharge cycles in a LiIon battery is fixed.)
Another unknown is the timing requirements of the NC. Chips need a setup and hold time. At 800Mhz, all timing constraints were met. May not be the case at 1ghz or 1.1 ghz.
Having said this, I do overclock my PC but I don't overclock the NC (I don't want to recharge every day.)
Hello,
I just flashed Cronos 1.2 last night, and after overclocking to 1GHz(62vsel), I noticed that my battery felm warm.
This morning the temperature had jumped up to 38C, but is presently at 34C. I used to run around 28C on CM7 and am wondering if these temps are normal? Should I downgrade my O/C to 900MHz?
Thanks in advance!
Sent from my Milestone using XDA Premium App
38C is definitely fine.
When i surf the web using 3G network, it is always 37C+
you can set a tempature profile using setCPU to lower the clock speed if temp. is high
You can edit /system/etc/init.d/10overclock using ROOT Explorer to change the speed to max 900Mhz. Also try to lower the vsel in the 10overclock file, it saves a lot of battery life
Right now, my overclock is set at 1GHz, with a 62 vsel. I have a stable overclock file from FroyoMod 2.6.0, that would save me a lot of battery life and it was clocked at 900MHz, just curious as to what are normal temperatures are, I'm used to sub-30C on normal browsing
I generally try to keep my battery from going any higher than 32 when browsing the 'net, but I did notice that on higher vsels it got hotter. I wouldn't call it dangerous, but remember that the more you're draining the battery, the faster it'll die. I don't mean lose its charge, I mean it just won't hold a charge any more. Lithium Ion batteries are rated for 500 charges, so if you need to charge the phone once a day, you'll be out of a battery in a year and a half.
If it reaches 40+ I would start to worry, though. The difference from 900 MHz at 52 vsel and 1 GHz at 62 vsel doesn't warrant using, in my opinion.
It looks like the spike to 38C was a random spike, because right now it is anywhere from 32-34C, so I think it might have just been one spike that made the phone get really hot!
I also think that the milestone is getting really hot. I think thats kind of annoying
Well right now I have mine at 29, sitting idle with EDGE turned on.
During the day time I've seen it going from 32 to 34.
With HSDPA and Wifi Tether turned on, I've seen it went up to 54.
That is my experience.. and yes 54 is HOT... usually I just turn off tether for a while, until the temp drops to 40+ before I re-tether.
I had my other phone touchscreen spoiled because of the prolonged heat. Bad experience..
Hi guys,
What is safe Tegra 3 temperature? I tried SetCPU stability test for 20 minutes at 1.6GHz and System Tuner Pro showed 72C. I'm correct, 80C is bad? I also suppose SetCPU stability test is more aggressive, than games or any other apps.
I user to run v10a firmware which often ran to 80° with no ill effects. I would be concerned if it rose any higher. The phone is built to shut down at 90° so I wouldn't worry too much, it can handle the heat
Sent from my smart frying pan (Tegra 3)
i had my device shut down twice while running werewolf with no skin throttle. i put the shutdown temp at 80 degs celsius. this happened after an hour of gaming. so yeah, it could probably run even more. i think default nvidia's shutdown temp is 120(!) degs celsius. not sure where i read it though.
I have throttle set to 75 and shutdown to 85. This is more than enough for me.
I wouldn't let my device go anywhere higher than 80C... It might be able to handle more than 80, but I'm not willing to risk it
Winudert said:
Hi guys,
What is safe Tegra 3 temperature? I tried SetCPU stability test for 20 minutes at 1.6GHz and System Tuner Pro showed 72C. I'm correct, 80C is bad? I also suppose SetCPU stability test is more aggressive, than games or any other apps.
Click to expand...
Click to collapse
I saw it from a kernel's changelog (don't remember the kernel's name), it said in the changelog "Tegra 3 default safe temperature : 85 C"
but I wouldn't recommend going above 80 C, it would reduce lifespan of your phone, not even mentioning the battery.Since battery is pretty close to tegra 3 chip, it gets effected by the heat chip generates
The main problem with high temperatures is not the chipset-temperature but the battery shouldn't get too hot. Li-batteries will be destroyed on high temperature. It's around 50 °C.
Did you hear about bloated or exploded phone batteries? This were cases of high temperatures.
blumenkasten said:
The main problem with high temperatures is not the chipset-temperature but the battery shouldn't get too hot. Li-batteries will be destroyed on high temperature. It's around 50 °C.
Did you hear about bloated or exploded phone batteries? This were cases of high temperatures.
Click to expand...
Click to collapse
Strange thing. Hot in the SoC area (top), not at all where battery is.
Winudert said:
Strange thing. Hot in the SoC area (top), not at all where battery is.
Click to expand...
Click to collapse
Because it is actually the SoC what gets hot. Look at temperatures in Trickster mod (or any similar app).
Better be careful, be careful burned out CPU
Mr.Fong said:
Better be careful, be careful burned out CPU
Click to expand...
Click to collapse
It's just one thing - Tegra 3 chip is awful. I watched a lot of review of Optimus 4X HD, but not in one was talked about awesome hot, sadly. Though Tegra 5 are looking very nice now with Kepler GPU, but I'm furious on nVidia and when I will buy phone next year, it not will be powered by nVidia chip. I'm crossing fingers on next gen Intel Atom SoC.