Related
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
For you gamers out there
Finally I solved the thermal throttling problem in this lovely device.
BEWARE **YOUR PHONE WILL HEAT MORE**
first using your root explorer go to system/etc, you will find 3 files related to thermal throttling:
1. thermal-engine-8996-normal.conf
2. thermal-engine-8996-perf.conf
3. thermal-engine.conf
These files related to the configuration in the settings->power manager->power plan.
If you chose performance then your phone will use the perf.conf
If you chose Smart power-save your phone will use normal.conf
Edit:
After further investigation it seems that no matter what setting I choose the file that is active always the normal.conf.
perf.conf seems not affecting anything at all. Needs futher investigation.
That is the mechanic, now for the fun part:
Open the file you wish to edit using text editor.
The key is in these two sections
Code:
[SKIN_CPU_MONITOR]
#algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 59000 62000
thresholds_clr 56000 60000
actions cluster0+cluster1 cluster0+cluster1
action_info 1400000+1700000 1500000+1824000
override 5000
[SKIN_GPU_MONITOR]
#algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 41000 42000
thresholds_clr 39000 40000
actions gpu gpu
action_info 510000000 401800000
override 5000
As you can see the values above are a little bit different from yours, it's because I already change a bit.
The parts you should take consideration are thresholds, thresholds_clr, actions, and action_info.
Thresholds means in what temperature the device should throttle
Thresholds_clr means in what temperature the device will stop throttling
Actions mean which item to be throttled
Cluster0 = Little CPU
Cluster1 = Big CPU
GPU = GPU
so for example above
thresholds 59000
thresholds_clr 56000
actions cluster0+cluster1
action_info 1400000+1700000
Means it will start throttling at 59 celcius and stop throttling at56 celcius, the item to be throttled are little CPU which become 1400 mhz and big CPU which become 1700 mhz
You can add many parameters just by using spaces like example above.
Okay, hope it helps. If you confuse, just use my values above and unleash the 60fps beast. Muahahaha
Edit:
This is my current setting
Code:
[SKIN_CPU_MONITOR]
#algo_type monitor
sampling 1000
sensor tsens_tz_sensor11
thresholds 48000 50000
thresholds_clr 45000 49000
actions cluster0+cluster1 cluster0+cluster1
action_info 1500000+1824000 1400000+1700000
override 5000
Instead of emmc thermostat I use tsens_tz_sensor11 which is the temperature of the CPU core itself, I think it is better
Finally someone make magisk module for this (thanks nfsmw_gr), not yet tried it myself though
https://forum.xda-developers.com/showpost.php?p=76793058&postcount=14
I've already moved on to stock b01 oreo rom, now it is located in /system/vendor/etc/thermal-engine.conf
Here is my current config
Code:
[SKIN_CHG_LIMIT]
algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 39000 41000
thresholds_clr 38000 40000
actions battery battery
action_info 1 2
[SKIN_CPU_MONITOR_NORMAL]
algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 36000 39000 42000
thresholds_clr 35000 38000 41000
actions cluster0+cluster1 cluster0+cluster1 cluster0+cluster1
action_info 1500000+1824000 1400000+1700000 1300000+1438000
override 5000
[SKIN_GPU_MONITOR_NORMAL]
algo_type monitor
sampling 1000
sensor emmc_therm
thresholds 41000 42000
thresholds_clr 39000 40000
actions gpu gpu
action_info 510000000 401800000
override 5000
Thank you so much.
Is this valid for destroying the phone without voiding the warranty?
aLexzkter said:
Is this valid for destroying the phone without voiding the warranty?
Click to expand...
Click to collapse
Lol, I'm pretty sure there's a failsafe for temps
You'd probably want to also undervolt if you are removing thermal throttling to give yourself a little more headroom. Hellsgate kernel supports undervolting
Been doing similar for months and mentioned about it a few times in various places.
I don't think using the CPU temperature sensor is suitable for throttling as it peaks largely and fluctuates rapidly with corresponding load. The reason emmc_therm (quiet_therm in AOSP ROMs) is probably used for a suitable consistent reading. The related default temperature throttles need to be adjusted to reflect the changed sensor and it's nature. What will happen on your config is sudden throttling on CPU load that will unthrottle rapidly when load is decreased but the battery/device isn't likely any cooler.
Btw on AOSP I can't get any changes to stay after rebooting with disemmcwp system writable too. I'm guessing the kernel or something regenerates the defined values at startup. I found having the file modified through a Magisk module works however.
Sent from my Xperia Z3C using XDA Labs
I know this sounds super lazy but can this possibly be made into a magisk module for convenience for and for ease of enabling/disabling
dalebaxter01 said:
I know this sounds super lazy but can this possibly be made into a magisk module for convenience for and for ease of enabling/disabling
Click to expand...
Click to collapse
I would like this as well if it's not much hassle.
dalebaxter01 said:
I know this sounds super lazy but can this possibly be made into a magisk module for convenience for and for ease of enabling/disabling
Click to expand...
Click to collapse
put your changed file into this template https://forum.xda-developers.com/mi-5/how-to/how-to-disable-thermal-throttling-t3636574
Infy_AsiX said:
Been doing similar for months and mentioned about it a few times in various places.
I don't think using the CPU temperature sensor is suitable for throttling as it peaks largely and fluctuates rapidly with corresponding load. The reason emmc_therm (quiet_therm in AOSP ROMs) is probably used for a suitable consistent reading. The related default temperature throttles need to be adjusted to reflect the changed sensor and it's nature. What will happen on your config is sudden throttling on CPU load that will unthrottle rapidly when load is decreased but the battery/device isn't likely any cooler.
Btw on AOSP I can't get any changes to stay after rebooting with disemmcwp system writable too. I'm guessing the kernel or something regenerates the defined values at startup. I found having the file modified through a Magisk module works however.
Sent from my Xperia Z3C using XDA Labs
Click to expand...
Click to collapse
Yeah, this is also what I found. At first I just looked at which temp is the highest and use that sensor for the trigger. But then when I use cpu-z to observe the reading, I found that emmc_therm is the most consistent and not fluctuate drastically so much. Therefore I'm back using emmc_therm right now
Seeing this thread gives me flashback in the Android M days where a xposed module was needed to disable a system task killer that would kill my games if they used too much battery once I turn off screen _-_
Never again will I use my phone gaming while overheating message comes up.
It almost killed my phone, not turning on and charging. I had to disassemble the phone and remove the battery to make it charge again.
otaconremo said:
Never again will I use my phone gaming while overheating message comes up.
It almost killed my phone, not turning on and charging. I had to disassemble the phone and remove the battery to make it charge again.
Click to expand...
Click to collapse
You should always keep your eyes on the temp. My rule of thumb is under 55 degree is ok, above that is no no. If your games always reach above 55 then you should re-tweak your thermal config.
Use dev check pro to observe the temp, though it doesn't have widget for emmc_therm only the cpu therm, you can still see what's going on under the screen
Okay, so after reading through the comments I made a magisk module for myself to test, using the template from the Mi 5 thread.
I modified all 3 files to be sure it works (my device boots so yeah, try it and let me know).
Also made a copy of the modded files at /system/etc to cover all scenarios because in the ROM I run the files are located in /system/vendor/etc, not in /system/etc as in the OP .
It shouldn't affect anything I think.
Anyway without stalling you'll find the file attached at the bottom, as always you flash at your own risk, have a nice day!
(P.S. If this is ok I'll put it on my thread with my Jojoc mod.)
otaconremo said:
Never again will I use my phone gaming while overheating message comes up.
It almost killed my phone, not turning on and charging. I had to disassemble the phone and remove the battery to make it charge again.
Click to expand...
Click to collapse
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
iyancoolbgt said:
You should always keep your eyes on the temp. My rule of thumb is under 55 degree is ok, above that is no no. If your games always reach above 55 then you should re-tweak your thermal config.
Use dev check pro to observe the temp, though it doesn't have widget for emmc_therm only the cpu therm, you can still see what's going on under the screen
Click to expand...
Click to collapse
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
nfsmw_gr said:
Okay, so after reading through the comments I made a magisk module for myself to test, using the template from the Mi 5 thread.
I modified all 3 files to be sure it works (my device boots so yeah, try it and let me know).
Also made a copy of the modded files at /system/etc to cover all scenarios because in the ROM I run the files are located in /system/vendor/etc, not in /system/etc as in the OP .
It shouldn't affect anything I think.
Anyway without stalling you'll find the file attached at the bottom, as always you flash at your own risk, have a nice day!
(P.S. If this is ok I'll put it on my thread with my Jojoc mod.)
Click to expand...
Click to collapse
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Infy_AsiX said:
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Click to expand...
Click to collapse
Mind sharing your own config?
Infy_AsiX said:
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Click to expand...
Click to collapse
I believe my battery is too degraded already. That only happens when my batt is below 20% and I was still gaming. That's why I'm very careful already when I'm getting lowbat. Btw, I'm using stock chinese mf5 version. The overheating message is from the Mi-Assistant app (Power Manager).
nfsmw_gr said:
Mind sharing your own config?
Click to expand...
Click to collapse
I did awhile back but I guess it's a little scattered across posts. I was about to edit in another paragraph with more info but I'll put it here now instead. I'll consider cleaning up the new stuff to share, performance profiles is just a varied collection of performance levels.
I've setup various CPU GPU performance profiles to switch between using Tasker. From testing, the highest I'd go without a fan is 1600/1800 big and 1300 small. With a constant load at these frequencies the battery will still hit up to around 50degC, matching the much higher perf allowed with a fan.
Here's a tidbit to get y'all thinking about environmental impact on heat. Stock Daydream sets a Sustainable Performance mode that uses all cores at 1200MHz. In the Daydream Headset V1, the back of the phone actually has an air gap behind it because of raised nubs inside the headset. Yet with all this the battery can rather easily heat to over 55degC after a few dozen minutes. The headset v2 has a built in heatsink, with minor improvement apparently. Also on an off-topic note, that Sustained Performance mode gets stuck to on after using Daydream on stock N. Things no one notices unless you actually monitor
---------- Post added at 10:12 PM ---------- Previous post was at 10:09 PM ----------
otaconremo said:
I believe my battery is too degraded already. That only happens when my batt is below 20% and I was still gaming. That's why I'm very careful already when I'm getting lowbat. Btw, I'm using stock chinese mf5 version. The overheating message is from the Mi-Assistant app (Power Manager).
Click to expand...
Click to collapse
Yeah sounds like my guess about an undervolted degraded battery. Oh I had that frozen so never got that alert. I'd assume it occurs when battery is 55degC or so, that's when Daydream alerts too for example.
Infy_AsiX said:
No idea how you got that. I've never seen a overheating message on stock N or RR-O. I've gotten the device to overheat shutdown plenty of times after increasing the secondary CPU throttle (hasn't been described here) from 95degC to 105degC. Even on fan with enough load at maximum frequencies the CPU temp can spike to the presumedly 120degC Qualcomm shutdown (dropping one step on big cores is fine). This secondary throttle behaves differently by interrupting performance and unthrottling rapidly. Still boots fine after. I've yet to try if undervolting will allow that final big frequency step, on fan, increased to 105degC, no secondary throttle and no shutdowm.
I'd guess instead your battery voltage dropped too severely low being old degraded and too high a current draw, requiring a reset of the battery PCB or something.
55 isn't high at all for a CPU. You mean floating monitor overlay? It can select two custom temperatures to show on the dashboard and float monitor. The only real concern is battery temp. Other components are designed and rated to handle high temperatures. FWIW I've been running around 100degC CPU, keeping battery <50degC on fan with battery voltage limited to 3.85V for several months playing various high end games at maximum performance without notable ill effect. Well except that constant heat on the battery even at the safe low voltage will cause degradation, unavoidable cost for higher performance on a phone.
That location sounds like how it was when I tried AEX-O. Don't know if anything's changed there but no files could affect ROM thermal throttling on it then. The files there are different too, maybe generic Sd820 config or something, whereas RR-O uses the same sensors, values and config as stock N. I did also try the stock config modded to AEX but still no go. The only file with effect where it works is the -normal.conf.
Click to expand...
Click to collapse
Maybe I'm just too cautious But still, too much heat makes my hands really not comfortable.
I know we can customize which temperature to show, but no emmc_therm unfortunately. Reading your comment make me thinking, if the real concern is the battery temp, then why not using it as the trigger for the thermal config? It is listed as 'battery' in cpu-z list of thermal sensors. It means that we can use it right?
nfsmw_gr said:
Okay, so after reading through the comments I made a magisk module for myself to test, using the template from the Mi 5 thread.
I modified all 3 files to be sure it works (my device boots so yeah, try it and let me know).
Also made a copy of the modded files at /system/etc to cover all scenarios because in the ROM I run the files are located in /system/vendor/etc, not in /system/etc as in the OP .
It shouldn't affect anything I think.
Anyway without stalling you'll find the file attached at the bottom, as always you flash at your own risk, have a nice day!
(P.S. If this is ok I'll put it on my thread with my Jojoc mod.)
Click to expand...
Click to collapse
Thanks, that's so cool. I'll put it on the first post
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.
hi everyone
i was wondering if these temps are normal
i was playing Codm for 50mins on lowest graphic settings and highest fps
ambient 22C
no phone cover
(Not charging)
Cpu: 57C
Gpu: 52C
Battery: 39C
Absolutely fine.
amn1987 said:
Absolutely fine.
Click to expand...
Click to collapse
thanks.
what is the maximum temp cpu can reach safely?
because i live in a hot environment (30C+) and this test happened in my room
CPU should start throttling down once it hits 75-80C but depending upon the thermals used it can be tweaked up/down. Therm shutoff point should be ~90C.
For those of you using the modified thermal-engine-8996.conf files in this forum, I would recommend using these three specifications under the [KYRO_SS] area: (keep everything else the same)
set_point 49500
set_point_clr 45500
device_perf_floor 1324800
set_point determines a threshold for thermal throttling
set_point_clr determines when to stop thermal throttling
They don't equate exactly to the degrees in celsius for the CPU or battery, so I'm not sure exactly what the translation is. However, I found that this was a pretty good threshold to use to reduce the thermal throttling on the CPU.
By setting the device_perf_floor metric to a lower number, I could also make sure that thermal throttling DID happen when it was needed. This helped a lot to reduce the chances of my phone from overheating and shutting down during a hot summer day.
Hope this helps somebody! This really saved my phone.
this is the two i modified
p.s. do not go higher than 1824000... it went so hot my first Lgv20 screen got unglued from the case lol. now is working fine with my second lg v20 with below config
KRYO_SS]
algo_type ss
sensor skin_ap
sampling 5000
device cpu_voltage
set_point 40000
set_point_clr 38500
device_perf_floor 1824000
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 38000 39500 41000 42500
thresholds_clr 37000 38500 40000 41500
actions gpu gpu gpu gpu
action_info 642000000 560000000 510000000 401000000
paul999 said:
this is the two i modified
p.s. do not go higher than 1824000... it went so hot my first Lgv20 screen got unglued from the case lol. now is working fine with my second lg v20 with below config
KRYO_SS]
algo_type ss
sensor skin_ap
sampling 5000
device cpu_voltage
set_point 40000
set_point_clr 38500
device_perf_floor 1824000
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 38000 39500 41000 42500
thresholds_clr 37000 38500 40000 41500
actions gpu gpu gpu gpu
action_info 642000000 560000000 510000000 401000000
Click to expand...
Click to collapse
The difference betwen the two methods is that 1824000 is actually kind of a high frequency to be thermal throttling at. (especially during the hot summer days we've been having lately in my state, my phone would just continue heating up and shutting down) I find that modifying set_point and set_point_clr are actually better since it increases the temperature setting BEFORE it starts throttling, but still throttles when it really needs to. This is especially helpful when using extended life batteries like the 6700 mAh batteries or 8500 mAh batteries which tend to run hotter than the average 3200 mAh batteries.
What I've observed is that if the extended batteries go above 51 degrees celsius, it starts kind of a chain reaction of heat between the CPU and battery that eventually causes the phone to overheat. I targeted the set_point and set_point_clr settings to cause it to throttle around this time to still make the phone usable, just slower for a short time.
I found that 1324800 was a good frequency to actually bring the temperature back down. When I set it at higher frequencies, the temperature for the battery would still stay around 51 degrees celsius or higher which was too hot for my taste.
i think my phone can handle it since i replaced the cheap paste with a premium paste......anyway i will test your method out to see if theres improvement