There's something odd with Snapdragon 625 on RN4 (according to me).
I have noticed that the maximum clock is half of the times coming down to 1.6GHz or less instead of 2.0GHz, especially when charging when the phone is warm (but temperature isn't high enough to trigger down clocking-- around 30-40 degree Celsius).
This also happens when the phone is not charging and I am doing some task like using apps or playing games when the phone's hardly heating up (afterall, SD 625 is known for its no heating issues).
It looks like whenever I am doing some task that doesn't involve much processing, the max clock comes down (but when I am performing some CPU intensive task such as installing an app, the max clock stays at 2GHz).
I am using interactive governor. PLEASE NOTE THAT I AM TALKING ABOUT THE MAXIMUM CPU CLOCK WHICH IS AFFECTED IN MY CASE. Using Kernel Adiutor to reset max freq. to 2GHz hardly works. It seems like the system ignores my clock settings. Even if i set the governor to performance, the max clock still keeps coming down and going up.
What's the deal with this processor?
Also, all the 8 cores are ALWAYS ON. There's no option for CPU hotplug in Kernel Adiutor.
Please someone shed some light over this.
CPU is thermal throttling not only when CPU is hot, but also when battery is hot. Also it is using a frequency which it needs, if it's using 1.6ghz it means it doesnt need more for whatever you have been doing.
k3lcior said:
CPU is thermal throttling not only when CPU is hot, but also when battery is hot. Also it is using a frequency which it needs, if it's using 1.6ghz it means it doesnt need more for whatever you have been doing.
Click to expand...
Click to collapse
It also happens when the phone is not warm/hot.
Please note that I'm not talking about the current frequency that is being used, I AM TALKING ABOUT THE MAX FREQ that is pulled down and up when I am working (even when just simply using the phone for little tasks which doesn't really heat the phone up).
While using any governor, the max freq should stick to what it is set to and the current freq varies. But here, the max freq is varying along with the current freq. Is this some feature or what?
If this is actually due to heating, is the management so bad that even 35-40 degree celsius makes the CPU throttle? Generally throttling happens at much higher temperatures.
This is 14nm SoC, it has much lower temperatures but also much lower max temp. (throttling start on lower temps)
You can't heat up this CPU to 60C or more like Snapdragon 8xx for example, because it will shut down.
k3lcior said:
This is 14nm SoC, it has much lower temperatures but also much lower max temp. (throttling start on lower temps)
You can't heat up this CPU to 60C or more like Snapdragon 8xx for example, because it will shut down.
Click to expand...
Click to collapse
LOL means I can't make good use of the 2GHz 8 core CPU for long because it'll heat up and simply throttle down. That's too stupid to have a powerful processor.
i am having heating issue. I found no thread discussing.. I am in Miui9 global beta version. Rooted withMagisk using redwolf twrp. My top part of screen heats in normal usage for 5 minute in wifi/data.I have checked the cpu temp( maximum 42) and battery tem( 36 to 38)..But the screen become hot..any work around? Is it a software or hardware issue? how to resolve it
Related
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
Hi Guys,
I am a noob here. I have never used a android phone before, not even a iPhone - so basically no smart phones.My first smart/android phone would be Nexus 4 which would be coming tomorrow.
I have been reading threads to understand andriod architecture and believe have understood to certain extent.
I have a question in clocking the CPUs and Voting.
As I understand, we have 3 states -Max, Min and Sleep for a single CPU core
Max - The frequency (clock speed) which CPU executes or maximum speed which CPU sends signals to its components and get the response back. This would be used when the system is on - which means when user is doing some process.. like texting, video chat, gaming (this case GPU is also involved) etc.
Min - This would be for background process when the user/phone is idle - that when screen is off (eq - gmail sync, facebook sync etc..)
Sleep - Screen off and no background process , the core will be in sleep.
And the battery level will be directly propotional to speed of CPU with respect to the volting.
Now lets say there is a single core processor in a phone which can clock upto 1.5GZ. and the stock kernel comes up with Max - 1.3GZ and MIN -0.5 GHZ.
Question is abt overclocking minimum frequency
1. why not overclock the Mn frequency to 1.3Ghz? because the backgroundprocess would be fast and phone/core will be sleeping after that,
which means process consumes more battery at that particular time but overall baterry should be efficient as there would be more sleeping time.
2. About volting, so far I have not seen min and max volting. So is there only one voltage/power drawn for max and min CPU speeds by CPU?
Please correct me if any of my statements is wrong.
Appreciate your help,
Thanks,
Franklin B.
Overclocking the minimum frequency to 1.3ghz would probably decrease your processor's life if you use your phone too much but I have been actually increasing my phone even 200mhz more than it was in stock ROMs, i've been using my device for more than 2 years and it still works perfectly. Finally, it all depends on how much your phone is good.
I also decreased the cpu min and max frequency when phone sleeps to 256 mhz which decreased a lot battery consumption.
Hope i helped !
Don't forget the THANKS button
1.you can but your battery life will be drastically reduced! There is a good amount of time after the screen is off and before the phone sleeps! So if over clock the min to 1.3Ghz, the processor will be running at 1.3Ghz till it goes to sleep! But if that's what you want you can do that!
2 . I'm not so sure about this topic either but I think the processor operates at a particular voltage and I could be wrong!
Sent from my GT-P3100 using Tapatalk 2
Thank you Guys
Franklin Bernard said:
1. why not overclock the Mn frequency to 1.3Ghz? because the backgroundprocess would be fast and phone/core will be sleeping after that,
which means process consumes more battery at that particular time but overall baterry should be efficient as there would be more sleeping time.
2. About volting, so far I have not seen min and max volting. So is there only one voltage/power drawn for max and min CPU speeds by CPU?
Click to expand...
Click to collapse
Hi, I received your PM. I agree with the guys about the heat issues, longevity, and battery life etc. The answer to your question #2 will help you better understand things.
In all kernels, there are frequency/voltage scaling tables. For every frequency step (clock speed) in the table, it corresponds to a specific voltage. It gets a bit more complicated than this of course, but that is the basic way things are setup in the kernel. The higher the frequency, the higher the voltage is required to be to keep the CPU (or GPU, bus, RAM etc.) stable at a given clock speed. The more voltage, the more current, and the more heat is generated. The longer you stay at higher clock speeds/voltages, the better the cooling system you need to have. Supply regulators are defined to feed the core and rail voltages so that the processor can live in a happy environment no matter what it is being asked to.
As far as power consumption, it's all about getting a unit of work done in a timely/efficient fashion using the least amount of power consumption. If the phone is sleeping, the word "timely" takes on a different meaning so then it is mostly concerned with power consumption and getting the background tasks completed effectively without having the phone experience the sleep of death (SOD). What you are talking about is the theory of "race to sleep" so that the work can be done quickly and the phone can go back to sleep where it uses the least amount of power (clocks actually turn off during deep sleep and cores are turned off). However, there is a happy medium to this theory and heat and battery consumption are the main enemies. Heat can also rob efficiency, more current is required when a circuit heats up. The more a phone wakes up to do syncs for email, apps, social networking, missed calls etc., that work can stack up throughout the day. The question comes down to how can the device get this work done using the least power and keep the device cool. On the N4, the lowest frequencies can use ~700-800mV per core while the highest frequencies can use ~1100mV. There is a drastic difference in the amount of heat generation between this range.
I think this should give you the general idea and maybe more that you wanted to know! Here are some links to check out if you are interested. Google and you will find many many more articles and research papers.
http://en.wikipedia.org/wiki/Voltage_and_frequency_scaling
http://atrak.usc.edu/~massoud/Talks/Pedram-dvfs-Taiwan05.pdf
Thanks a ton !!!
I was using Havoc OS with derp kernels for quite a long time, and used to play PUBG alot , so recently from past few weeks cpu temperature is reaching about 60°c (Maybe because of summer season) and then cpu starts to throttle.
Then I recently switched to Oxygen OS and when my temperature reaches 60°c something ,it doesn't throttle. (Maybe because oos uses different thermal profile)
So my questions are :
1. If it doesn't throttle above 60°c then could it harm my device?
2. What's the highest maximum temperature which wouldn't harm my device?
On Maximum 48-50 Degree Can Harm Your Device Chipset.
If You are on Latest OOS 25Build.
Then Install BuildProp Editor and Change The Value Stock Thermals False To True.
Reboot To Apply.
60 C Can Damage Your Device.
Smartphones Are Automatically Switch off When Reached to maximium Temperature 50-50.
Olystem said:
On Maximum 48-50 Degree Can Harm Your Device Chipset.
If You are on Latest OOS 25Build.
Then Install BuildProp Editor and Change The Value Stock Thermals False To True.
Reboot To Apply.
60 C Can Damage Your Device.
Smartphones Are Automatically Switch off When Reached to maximium Temperature 50-50.
Click to expand...
Click to collapse
I have changed my rom to Pixel Experience, & now the temperature is just between 45-55 while playing games, but most of the time temperature was around 50°c . I think the problem was because of kernel or rom. Don't know the exact reason.
-TheKoolAnie- said:
I have changed my rom to Pixel Experience, & now the temperature is just between 45-55 while playing games, but most of the time temperature was around 50°c . I think the problem was because of kernel or rom. Don't know the exact reason.
Click to expand...
Click to collapse
Flash Stock ROM Latest Version Then Check.
It's Not Normal.
Till Then Don't play the Games.
I also Facing same issue while playing games 44-46.
I think problem related to latest vendor.
Olystem said:
Flash Stock ROM Latest Version Then Check.
It's Not Normal.
Till Then Don't play the Games.
I also Facing same issue while playing games 44-46.
I think problem related to latest vendor.
Click to expand...
Click to collapse
I switched to miui , not doing any heavy or performance requiring task, still this temperature.
P.s: I have applied Gadgeshildz skin on my Poco,do u think this could be the reason?
-TheKoolAnie- said:
I switched to miui , not doing any heavy or performance requiring task, still this temperature.
P.s: I have applied Gadgeshildz skin on my Poco,do u think this could be the reason?
Click to expand...
Click to collapse
I didn't think the skin causing that issue.
Hello Bro This is CPU Temperature CPU Has a Limit to of 70-100 max .
This is Normal.
That is Thermal Profile.
If The Temperature Reach That Limit it Will Decrease The Performance.
Check Your Battery Temperature.
Check This.
This is mine.
In oxygen OS with Stock Kernel.
Olystem said:
Hello Bro This is CPU Temperature CPU Has a Limit to of 70-100 max .
This is Normal.
That is Thermal Profile.
If The Temperature Reach That Limit it Will Decrease The Performance.
Check Your Battery Temperature.
Click to expand...
Click to collapse
I didn't understand your point.
Why is it normal? Temperature is reaching above 55°c which isn't normal.
Btw when I play pubg, battery temperature reaches to 46°c but when I took screen shot temperature was 40°c.
If battery temperature Reached to 47-55 degree that's not normal.
Your SS Shows thermal profile temperature not the CPU temperature.
CPU and GPU are components inside your phone and they heat from 40 -80 degree Celsius pretty fast in every phone. They can handle upto
Olystem said:
CPU and GPU are components inside your phone and they heat from 40 -80 degree Celsius pretty fast in every phone. They can handle upto
Click to expand...
Click to collapse
As you can read in op ,I was talking about CPU temperature from starting. So when I play pubg and temperature reaches to 55°c so it's Safe? I got confused.
CPU and GPU are components inside your phone and they heat from 40 -80 degree Celsius pretty fast in every phone. They can handle upto
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
I am writing full post but when I post it.
Not showing full message.
Cpu temperature is Normal 40-80 degree.
Bro it's normal.
I am talking about battery temperature.
Working temps in heavy workloads (Games, YouTube, Split-screen/Dual screen, etc.) is around 60°c and it is quite normal but above 75°c thats when you expect damage to the system. According to other XDA Thread, https://www.xda-developers.com/processor-temperature-results-for-tens-of-socs-how-hot-is-your-chip/ Maximum Temperature recorded on a Qualcomm Device (It uses MSM8225Q Chipset) is 63.88°c
Expect Qualcomm that makes powerful and energy efficient SOCs even operating in high temperatures.
Darklouis said:
Working temps in heavy workloads (Games, YouTube, Split-screen/Dual screen, etc.) is around 60°c and it is quite normal but above 75°c thats when you expect damage to the system. According to other XDA Thread, https://www.xda-developers.com/processor-temperature-results-for-tens-of-socs-how-hot-is-your-chip/ Maximum Temperature recorded on a Qualcomm Device (It uses MSM8225Q Chipset) is 63.88°c
Expect Qualcomm that makes powerful and energy efficient SOCs even operating in high temperatures.
Click to expand...
Click to collapse
So that means i shouldn't worry about below 60°c cpu temperature while playing game in hot environmen ( around 40°c)
-TheKoolAnie- said:
So that means i shouldn't worry about below 60°c cpu temperature while playing game in hot environmen ( around 40°c)
Click to expand...
Click to collapse
Its fine. Just don't let it work around 70°c above.
Darklouis said:
Its fine. Just don't let it work around 70°c above.
Click to expand...
Click to collapse
If he uses the default thermal profile, he won't reach above 70, well it shouldn't as the phone will throttle. That's the whole idea of throttling, to lower the temperatures to protect the CPU or GPU from any damage. Also, even if you reach a higher temperature then 70, at one point, the phone will switch off in order to protect itself from any damage. Well, in most cases.
ekin_strops said:
If he uses the default thermal profile, he won't reach above 70, well it shouldn't as the phone will throttle. That's the whole idea of throttling, to lower the temperatures to protect the CPU or GPU from any damage. Also, even if you reach a higher temperature then 70, at one point, the phone will switch off in order to protect itself from any damage. Well, in most cases.
Click to expand...
Click to collapse
Btw every custom rom has its own throttling points for example :
Havoc os start to Throttle around 53°c
Whereas pixel experience throttles about 57_58°c
But in miui cpu temp reached above 60°c for few seconds still it doesn't throttle.
ekin_strops said:
If he uses the default thermal profile, he won't reach above 70, well it shouldn't as the phone will throttle. That's the whole idea of throttling, to lower the temperatures to protect the CPU or GPU from any damage. Also, even if you reach a higher temperature then 70, at one point, the phone will switch off in order to protect itself from any damage. Well, in most cases.
Click to expand...
Click to collapse
Poco doesn't have automatic shutdown when overheating, but just a overheating notification. (Like in S10+) But maybe in a certain temperature, Poco has a built-in safety switch to automatically shutdown the device to prevent possible damage
Darklouis said:
Poco doesn't have automatic shutdown when overheating, but just a overheating notification. (Like in S10+) But maybe in a certain temperature, Poco has a built-in safety switch to automatically shutdown the device to prevent possible damage
Click to expand...
Click to collapse
Even the old Redmi note 4 had that switch, so i'm pretty sure they have it in Poco too.
My temps used to hover around 32*c back then before the MIUI Global Beta 10 9.3.28 came out. I forgot which beta version I was in. I was all stock with no root. While gaming, my temps would go as much as 37*c but never more than it.
Right now, I've tried MIUI EU and Global Beta and most of the time, my normal temps are around 38*c.