Originally Posted by chaozbr
Using stock batt, I think it was a sensor software fail, because I flashed a stock-ROM and put an OC kernel, OC'ed to 1300MHz and put a stability test to play, 5 min and it's at 55ºC using Myrt / System Tuner. I also think it was some type of bug, because my batt gets TOO hot in a very short time, less than 2 min, it goes from 34ºC to 40ºC.
Can you run StabilityTest with 1.4GHz and post a screenshot for us? Only to finish the issue
Ah, the ambient temperature here is low today, so wasn't because of ambient temps.
I'm currently working on a torture-tester, and at 1300Mhz@1100mV I reach 72° after just 100 seconds of testing when plugged in, 68° if unplugged.
As for the apps, they simply read a system-file ("sys/devices/system/cpu/cpu0/cpufreq/cpu_temp"). There is no translation or conversion going on there, what you see on the screen is what is in that file. It is supplied by the kernel, and I have no idea how accurate it is, if it's just a calculated temp or a real temp from a sensor. Maybe Vadonka has some insights into this. All modern phones (perhaps except for LGs) have temperature protections built in, they will usually throttle down CPUs, dim the screen, perhaps even shut off when things get too hot. I've yet to see that, so either our phone doesn't have it, or the CPU-temps are not reported correctly.
After testing some more I actually see signs of throttling. MFlops will cut exactly in half for a period, then after a while get back to the expected level. It seems to have little to no relation to the reported CPU-temp though. Will have to test a lot more to figure out what is going on, can easily be something else.
This was a bug in the specific kernel I was testing.