Hi,
I ran some basic tests with some benchmarks and also use ROM Toolbox to look at CPU min/max frequency.
I can confirm that running things like AnTuTU and Vellamo cause the device to heat up and cap CPU speed at about 1.5 GHz.
This means that unless your device is sitting in a freezer it will throttle when running all out.
There are some files that look to control this behavior in /system/etc/
thermal-engine.conf
thermal-engine-8974.conf
thermal-engine-8974-default.conf
and finally thermald.conf which is a brokent sym link.
Anyone ever play with these?
I'm sure a great kernel Dev will fix us up soon
tech_head said:
Hi,
I ran some basic tests with some benchmarks and also use ROM Toolbox to look at CPU min/max frequency.
I can confirm that running things like AnTuTU and Vellamo cause the device to heat up and cap CPU speed at about 1.5 GHz.
This means that unless your device is sitting in a freezer it will throttle when running all out.
There are some files that look to control this behavior in /system/etc/
thermal-engine.conf
thermal-engine-8974.conf
thermal-engine-8974-default.conf
and finally thermald.conf which is a brokent sym link.
Anyone ever play with these?
Click to expand...
Click to collapse
The only one you need to play with is thermal-engine-8974.conf. Two of the others are sym links (one broken) and the other seems to hold values for shutting the phone down due to high cpu temps (115 Celsius), although these values are also in thermal-engine-8974.conf with slightly different values. It seems there is a lot of different types of throttling involved on this phone by looking at this file.
Although I don't know all the details, it seems threshold is the temp in Celsius (multiplied by 10000 under batt_therm_monitor, multiplied by 1000 in all other places) that the throttling takes place. Thresholds_clr seems to be where that throttling stops when the temp cools. Some categories have multiple levels of throttling. CPU_LCD_management has 6.
Changing these two values does work. You have to reboot after any changes you make for them to take effect. I have increased the memory speed throttle and the individual cpu throttle temps by 5 degrees (5000) on both the thresholds and thresholds_clr. I have increased all other thresholds and thresholds_clr by 10 degrees. I did not mess with the shutdown temps.
I should also note that I did try disabling thermal throttling entirely via the hidden menu and the phone would shutdown due to overheat during any benchmarks (thank goodness!). So this is why I decided to tweak these settings, since disabling it entirely seems to be a bad idea. Benchmarks are slightly higher and no shutdowns. Phone does get noticeably hotter.
This is what my thermal-engine-8974.conf looks like after modifying:
sampling 5000
c_mode 3
[CPU_LCD_management]
algo_type monitor
sensor xo_therm_pu2
sampling 10000
thresholds 55000 57000 59000 61000 63000 65000
thresholds_clr 54000 55500 57500 59500 61500 63500
actions cpu+lcd cpu+lcd cpu+lcd cpu+lcd cpu+lcd cpu+lcd
action_info FFFFFFF+255 1958400+255 1574400+245 1497600+235 1497600+225 1267200+225
action_type 25000
[GPU_management]
algo_type monitor
sensor xo_therm_pu2
sampling 10000
thresholds 59000
thresholds_clr 53000
actions gpu
action_info 330000000
action_type 25000
[battery_monitor]
algo_type monitor
sensor xo_batt
sampling 10000
thresholds 57000 58000 59000 60000 61000
thresholds_clr 56000 57000 58000 59000 60000
actions battery battery battery battery battery
action_info 1024 768 512 410 307
[iusb_monitor]
algo_type monitor
sensor xo_batt
sampling 10000
thresholds 57000 60000
thresholds_clr 55000 57500
actions iusb iusb
action_info 1500 1000
[wlchg_monitor]
algo_type monitor
sensor xo_therm_pu2
sampling 10000
thresholds 62000
thresholds_clr 60000
actions wlchg
action_info 512
[batt_therm_monitor]
algo_type monitor
sensor batt_therm
sampling 10000
thresholds 660000
thresholds_clr 620000
actions lcd
action_info 93
[CPU0_MONITOR]
algo_type monitor
sensor cpu0
sampling 65
thresholds 120000
thresholds_clr 115000
actions shutdown
action_info 0
[CPU1_MONITOR]
algo_type monitor
sensor cpu1
sampling 65
thresholds 120000
thresholds_clr 115000
actions shutdown
action_info 0
[CPU2_MONITOR]
algo_type monitor
sensor cpu2
sampling 65
thresholds 120000
thresholds_clr 115000
actions shutdown
action_info 0
[CPU3_MONITOR]
algo_type monitor
sensor cpu3
sampling 65
thresholds 120000
thresholds_clr 115000
actions shutdown
action_info 0
[SS-CPU0]
algo_type ss
sampling 65
sensor cpu0
device cpu
set_point 90000
set_point_clr 60000
action_type 10000
[SS-CPU1]
algo_type ss
sampling 65
sensor cpu1
device cpu
set_point 90000
set_point_clr 60000
action_type 10000
[SS-CPU2]
algo_type ss
sampling 65
sensor cpu2
device cpu
set_point 90000
set_point_clr 60000
action_type 10000
[SS-CPU3]
algo_type ss
sampling 65
sensor cpu3
device cpu
set_point 90000
set_point_clr 60000
action_type 10000
[SS-POPMEM]
algo_type ss
sampling 65
sensor pop_mem
device cpu
set_point 85000
set_point_clr 60000
time_constant 16
action_type 20000
I figured it out, but thanks.
I tweaked mine a bit different but it still works like yours does.
No throttling during benchmarks.
tech_head said:
I figured it out, but thanks.
I tweaked mine a bit different but it still works like yours does.
No throttling during benchmarks.
Click to expand...
Click to collapse
I've made a mod that tweaks the throttling you can check it out here
http://forum.xda-developers.com/lg-g3/development/thermal-mod-t2907363
Hello guys , i recently rooted my phone successfully! I really didnt like how lg operated this phone , simple games was micro lagging , not as smooth as adreno 530 was marketed. When i set the cpu on ondemand governor and disabling thermal core control all games became smooth as butter , really love it this way. I am playing my games with base optimisation so it downscales the resolution but my device didn't warm up at all, so i decided to mess with thermal throttling settings....
Here is what i found after searching with Solid Explorer , go to ROOT>SYSTEM>ETC>thermal-engine-8996.conf
Thats the log for the thermal control:
sampling 5000
c_mode_ap 0
c_mode_pmic 11
[KRYO_SS]
algo_type ss
sensor vts
sampling 5000
device cpu_voltage
set_point 42000
set_point_clr 40500
[SS-CPUS-ALL]
algo_type ss
sensor VIRTUAL-CPUS
sampling 10
device cpu_voltage
set_point 85000
set_point_clr 65000
[SS-GPU]
algo_type ss
sensor gpu
sampling 250
device gpu
set_point 85000
set_point_clr 65000
[SS-POPMEM]
algo_type ss
sensor pop_mem
sampling 10
device cluster1
set_point 85000
set_point_clr 65000
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 40000 41500 43000 44500
thresholds_clr 39000 40500 42000 43500
actions gpu gpu gpu gpu
action_info 510000000 315000000 214000000 133000000
[CHG_MONITOR]
algo_type monitor
sensor skin_pmic
sampling 5000
thresholds 42000 45000 48000 50000
thresholds_clr 38500 42500 45500 48500
actions chg_ibat chg_ibat chg_ibat chg_ibat
action_info 3100 1000 600 300
[PA_MONITOR]
algo_type monitor
sensor pa_therm0
sampling 5000
thresholds 45000
thresholds_clr 42500
actions chg_ibat
action_info 1000
[LCD_ON_MONITOR]
algo_type monitor
sensor lcd-brightness
sampling 5000
thresholds 1
thresholds_clr 0
actions chg_ibat
action_info 1000
[DAYLIGHT_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 42500
thresholds_clr 38000
actions daylight
action_info 1
And did change GPU_MONITOR like that:
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 41000 44500 50000 54500
thresholds_clr 39000 41500 45000 50500
actions gpu gpu gpu gpu
action_info 624000000 560000000 510000000 401000000
After studding a bit and making way too much testings on my phone , i could make it , mod will be soon available i am still testing it to make sure its stable as rock!
Take a look at the thumbnails below
I just Deleted the whole file and scored 144170!!! Everything was increased a bit , i am going to test it more and update the thread! 2nd 3D scrore also was improved a bit (1000 points, throttled less) , it just might work with default settings now ,at least i hope...
*** Dont delete the file , device won't throttle , i was playing real racing 3 cpu hit 80C (thats not good) and gpy 67c (not bad at all) so i am going back to edit the log!!!
Thanks for the information and that you shared this. I will perhaps include in my Custom Kernel.
Gesendet von meinem LG-H850 mit Tapatalk
thehacker911 said:
Thanks for the information and that you shared this. I will perhaps include in my Custom Kernel.
Gesendet von meinem LG-H850 mit Tapatalk
Click to expand...
Click to collapse
Thats why i shared it , i have been testing it all the day , by increasing the values on threshold (temps) and the last ones (mhz) i got a little more perf but you can't get more than that , even if you delete both gpu tables still throttling occurs during benchmarks. In order to delay more the GPU throttling temp you need to increase throttling values of the CPU and that makes also the phone hotter but things like performance doesnt go with low temps....
leonman44 said:
I just Deleted the whole file and scored 144170!!! Everything was increased a bit , i am going to test it more and update the thread! 2nd 3D scrore also was improved a bit (1000 points, throttled less) , it just might work with default settings now ,at least i hope...
*** Dont delete the file , device won't throttle , i was playing real racing 3 cpu hit 80C (thats not good) and gpy 67c (not bad at all) so i am going back to edit the log!!!
Click to expand...
Click to collapse
I've noticed I get the screen brightness all the way up and it starts dimming when it gets kinda hot. If I erase the file will my screen brightness stay bright?
Still_living714 said:
I've noticed I get the screen brightness all the way up and it starts dimming when it gets kinda hot. If I erase the file will my screen brightness stay bright?
Click to expand...
Click to collapse
Sorry for the late answer , if your phone warms up just stock dont delete the whole file , just delete the "lcd on" and "daylight" columns. That should do the trick! :good:
leonman44 said:
Sorry for the late answer , if your phone warms up just stock dont delete the whole file , just delete the "lcd on" and "daylight" columns. That should do the trick! :good:
Click to expand...
Click to collapse
Haha thanks but I'm on the s7 edge now
leonman44 said:
Hello guys , i recently rooted my phone successfully! I really didnt like how lg operated this phone , simple games was micro lagging , not as smooth as adreno 530 was marketed. When i set the cpu on ondemand governor and disabling thermal core control all games became smooth as butter , really love it this way. I am playing my games with base optimisation so it downscales the resolution but my device didn't warm up at all, so i decided to mess with thermal throttling settings....
Here is what i found after searching with Solid Explorer , go to ROOT>SYSTEM>ETC>thermal-engine-8996.conf
Thats the log for the thermal control:
sampling 5000
c_mode_ap 0
c_mode_pmic 11
[KRYO_SS]
algo_type ss
sensor vts
sampling 5000
device cpu_voltage
set_point 42000
set_point_clr 40500
[SS-CPUS-ALL]
algo_type ss
sensor VIRTUAL-CPUS
sampling 10
device cpu_voltage
set_point 85000
set_point_clr 65000
[SS-GPU]
algo_type ss
sensor gpu
sampling 250
device gpu
set_point 85000
set_point_clr 65000
[SS-POPMEM]
algo_type ss
sensor pop_mem
sampling 10
device cluster1
set_point 85000
set_point_clr 65000
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 40000 41500 43000 44500
thresholds_clr 39000 40500 42000 43500
actions gpu gpu gpu gpu
action_info 510000000 315000000 214000000 133000000
[CHG_MONITOR]
algo_type monitor
sensor skin_pmic
sampling 5000
thresholds 42000 45000 48000 50000
thresholds_clr 38500 42500 45500 48500
actions chg_ibat chg_ibat chg_ibat chg_ibat
action_info 3100 1000 600 300
[PA_MONITOR]
algo_type monitor
sensor pa_therm0
sampling 5000
thresholds 45000
thresholds_clr 42500
actions chg_ibat
action_info 1000
[LCD_ON_MONITOR]
algo_type monitor
sensor lcd-brightness
sampling 5000
thresholds 1
thresholds_clr 0
actions chg_ibat
action_info 1000
[DAYLIGHT_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 42500
thresholds_clr 38000
actions daylight
action_info 1
And did change GPU_MONITOR like that:
[GPU_MONITOR]
algo_type monitor
sensor vts
sampling 5000
thresholds 41000 44500 50000 54500
thresholds_clr 39000 41500 45000 50500
actions gpu gpu gpu gpu
action_info 624000000 560000000 510000000 401000000
After studding a bit and making way too much testings on my phone , i could make it , mod will be soon available i am still testing it to make sure its stable as rock!
Take a look at the thumbnails below
Click to expand...
Click to collapse
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
Which thermal is best for gaming like pubg. Gives zero frame drops even phone heats up.
I'm using miui rom
shantorock said:
Which thermal is best for gaming like pubg. Gives zero frame drops even phone heats up.
I'm using miui rom
Click to expand...
Click to collapse
here you go https://drive.google.com/file/d/10OLkt9nR-z5hCvd4bVeRmbCQjwTPy8Fd/view?usp=drivesdk
Does anyone know of the same file's for a custom rom?
Please explain exactly what these thermals are doing
For example, here is a 4 core thermal
[BATTERY_CHARGING_CTL]
algo_type monitor
sampling 5000
sensor battery
thresholds 39000000 40000000 43000000 46000000 55000000
thresholds_clr 37000000 38000000 41000000 44000000 50000000
actions battery battery battery battery battery
action_info 0 1 2 3 4
When I took a look at these kernels, there is little to no information in English. Usually thermals are editable across a broad range of non Xiaomi Phones.