Related
I was curious about the max temperature for the CPU as I see many of these profiles setting up a reduction in OC if > 40. My problem is that I cannot maintain a temp below 40 with anything higher than 480 yet I see many people running 600-729. Could anyone shed some light on this for me.
skrumzy said:
I was curious about the max temperature for the CPU as I see many of these profiles setting up a reduction in OC if > 40. My problem is that I cannot maintain a temp below 40 with anything higher than 480 yet I see many people running 600-729. Could anyone shed some light on this for me.
Click to expand...
Click to collapse
The sustained max temperature you will see depends on what you are doing. Particularly if you have one or more radios going, you will experience high temperatures. For instance, streaming audio over the Mobile network or using tethering (WiFi tethering is the worst), it is trivial for the battery temperature to go above 50 C.
I saw 55 C once on my phone with a stock HTC 2.1 ROM (528 Mhz max) - I was streaming music, running a WiFi wardriving app, and also running the Nav app simultaneously on a 3 hr drive - in warm weather.
Unless someone on this board works as a thermal design engineer for HTC, it will be impossible for them to tell you what is too much - they would have to know what the thermal path from the processor to the battery is, and that's pretty much an impossible thing to guess at without pretty detailed calculations.
I set my temperature clamp profile to kick in at T > 50C; below that temperature, my phone runs at 768Mhz when it is fully charged. I would say that using the phone "normally" (as in extended internet browsing (reading, not video), texting, short phone calls), I rarely see my battery temperature above 40C.
bftb0
hello i got an optimus one...
ok ther is not a cpu temperature sensor.
but my battery report 2.3 °C .... is strange
ther is some app that correct read battery temperature on p500?
tnx
try Elixir
i have try
elixir report battery 2.5 °C
i have trai stock 2.2 , void and devoid rom and i have the same error...
is my battery fault?
Why do you want to know the battery's temperature ?
why not? are your battery temperature sensor working?
Not working here either
From what I've seen in the past month since I have this phone, nobody is able to get a correct reading of their battery temperature, no matter what application they used. The LG Optimus One always reports the temperature in the range of 2.x - 3.x degrees Celsius.
So, scoppyxda, your phone and battery are actually fine, don't worry. I hope this issue is fixed with the next Android version (2.3).
everythin reports it wrong except batteryminder..search for it in the market
I guess that the real temp is divided by a factor of 10. I say "i guess" because when i do something power hungry (like listening to streaming radio) the temp raises to 3.8 and the phone bak is quite hot.
I think it shows temp in deg. Fahrenhiet by default and app has to change it to deg. celcius.
Mik can fix this 5 mins if he spends time
I played with this a while today - I tried to multiply temp by 10 and voltage by 1000 in battery driver.
For voltage, it worked (see screenshot). When I tried to multiply temp by 10, apps showed it correctly, but android yelled that battery is overheated. So, android API gives wrong values to applications?
Make the api assume that it's normal ;p
Maybe the fahrenheit temp is actually the celsius temp.
And the celsius temp is the wrong temp.
I think it's...
Correct Values
While using myPhoneExplorer (usb connection) i get more realistic values. The monitor gives me figures in the range of 23-28 deg Celsius.
moses1202 said:
Maybe the fahrenheit temp is actually the celsius temp.
And the celsius temp is the wrong temp.
I think it's...
Click to expand...
Click to collapse
It isnt, battery driver returns value in celsius, fahrenheits are calculated from it by android.
I've posted the same question in the void forum (which is the ROM i'm currently using) it seems to be a problem with the model of the phone itself. So everyone will have the same results. I was told to just multiple the value by 10 to get the accurate degree.
I playing the game Japan Life while using AC charger, the temperature rised up to 61C. Do you know any problem will be affected to my phone?
Sent from my GT-I9100 using XDA App
61 °c! And you were able to still hold it! My phone is hard to touch at even just above 40 degree celcius
Sent from my GT-I9100 using XDA App
61c is insane....... you are lucky not to burn anything inside your s2.
What is the accepted max. temperature?
bala_gamer said:
61c is insane....... you are lucky not to burn anything inside your s2.
Click to expand...
Click to collapse
Well don't say that if you are not sure. 61°C is high, but no way you can say that as insane.
I was reading some articles about Cortex A9 CPU's and found this,
http://www.phytec.com/products/som/Cortex-A9/phyCORE-OMAP4430.html
So the TJ Max of the CPU is 85°C. But for safety you shouldn't let it go above 70-72°C.
But do remember one thing, that is the CPU temp I was talking about, not Battery temp as you mentioned. It's very common that Battery temp will get higher if CPU temp increases.
Regards.
ithehappy said:
Well don't say that if you are not sure. 61°C is high, but no way you can say that as insane.
I was reading some articles about Cortex A9 CPU's and found this,
http://www.phytec.com/products/som/Cortex-A9/phyCORE-OMAP4430.html
So the TJ Max of the CPU is 85°C. But for safety you shouldn't let it go above 70-72°C.
But do remember one thing, that is the CPU temp I was talking about, not Battery temp as you mentioned. It's very common that Battery temp will get higher if CPU temp increases.
Regards.
Click to expand...
Click to collapse
Yeah, people see battery temperature, but 61 degrees seems pretty high. My battery didn't pass 48 degrees, even when playing complex games. A high temperature will shorten battery lifetime and there has been one report on this forum about plastic inside SII melting down cause of heat, but no info about the temperature that melted it.
Sp1tfire said:
Yeah, people see battery temperature, but 61 degrees seems pretty high. My battery didn't pass 48 degrees, even when playing complex games. A high temperature will shorten battery lifetime and there has been one report on this forum about plastic inside SII melting down cause of heat, but no info about the temperature that melted it.
Click to expand...
Click to collapse
Well the battery & CPU, both temperatures are also depending on the ambient temp. It is also advised to mention the ambient temp along with battery temp.
Regards.
Normally mine operates at 42-46. Maybe it's because I live in a tropical country. Once it got to 53 degrees celsius. Got kinda worried, don't know whether to take it back or not. Is this normal?
Sent from my GT-I9100 using XDA Premium App
The HTC One M8 only has a battery temperature indicator (and from what I gather, these components aren't too reliable, but I digress.) I've recently reinstalled BOINC (the manager app for [email protected]) and it constantly starts and stops based on the default values for temperature. By default, it's set to stop computing when the battery reaches 40°C. This seems low to me. I'd like to increase the value so the app runs more often, but I also don't want to literally fry my phone.
What is the maximum temperature my battery can safely reach without damage? How accurate is the sensor in this model? (Gunmetal, if that makes any difference.)
Thanks very much.
The phone already has its own temperature monitoring, and will shutoff well before reaching temps that can cause permanent damage. A few folks have claimed that this isn't to be trusted. But with any temperature monitoring, its to be taken with a grain of salt, and in the end you have to trust something.
I'd agree that 40C is probably too low. I haven't seen any good figures for desired or undesired (too hot) operating temps for smartphones, but its been said (and reasonably so) that these are small computers, and the desired temps would be similar to a PC. And for PCs, while opinions will vary some, temps up to 60C or even 70C is acceptable. As you know, it depends on where you measure the temperature. And for smartphones in particular, while it may not cause immediate damage, having the batter temp consistently at higher temps will in the long run harm battery life. So I'd say limiting to maybe 50-55C is probably reasonable. There is some judgement involved here. But again, I'd say that is reasonable.
Attached is an image showing there is a CPU temp sensor on our phone. Stock kernel has an mpdecision setting to limit CPU and throttle or completely shut the phone down if temps get too dangerous. As for battery, 40℃ is a bit conservative. I live in Arizona and it gets upwards of 44℃ in the summer, so my phone would be in permanent limp mode during the summer.
redpoint73 said:
The phone already has its own temperature monitoring, and will shutoff well before reaching temps that can cause permanent damage. A few folks have claimed that this isn't to be trusted. But with any temperature monitoring, its to be taken with a grain of salt, and in the end you have to trust something.
I'd agree that 40C is probably too low. I haven't seen any good figures for desired or undesired (too hot) operating temps for smartphones, but its been said (and reasonably so) that these are small computers, and the desired temps would be similar to a PC. And for PCs, while opinions will vary some, temps up to 60C or even 70C is acceptable. As you know, it depends on where you measure the temperature. And for smartphones in particular, while it may not cause immediate damage, having the batter temp consistently at higher temps will in the long run harm battery life. So I'd say limiting to maybe 50-55C is probably reasonable. There is some judgement involved here. But again, I'd say that is reasonable.
Click to expand...
Click to collapse
Thanks much for your input. That's what I was hoping and expecting to hear. I've been conservatively playing around with settings, and I've limited the temperature threshold to 45C. This, combined with all the other very nice settings in BOINC, satisfies me. The funny thing is I probably have a better CPU in my phone than in my PC... I should cross-benchmark them somehow.
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