Better perfomance on b378 nougat p9 with less throttling cpu for rooted device - Huawei P9 Guides, News, & Discussion

Hello i just rooted my p9 eva-L09c432b378 and i found a way to make a less agressive throttling cpu due to higher temperature.
First you need heve a rooted device,and a root file explorer.
Open root explorer and get r/w permission to edit a file:
The path of the file to edit is:/sys/devices/virtual/thermal/thermal_zone0
Go to this folder and find file name:
trip_point_0_temp
Normally the value of this file is 55000 mean that after 55°C cpu will throttle hard to lower frequency and specially games will start lag!
I put the value at 65000 mean no throttle under 65°C
With that i could chain antutu bench more times without lower score
Warning this modification must be done at each time you restart your phone coz the value will be reseted at 55000!
So if people is able to make a script with auto change this value with an init.d script on boot you can tell me coz i don't know how to do that!
FEEDBACK ARE WELCOME

moomoon03 said:
...
So if people is able to make a script with auto change this value with an init.d script on boot you can tell me coz i don't know how to do that!
Click to expand...
Click to collapse
The attached file placed in your init.d folder with the correct permissions will do the job :good:
Once downloaded, remove .txt from the file name, it doesn't need that extension but i couldn't upload it without it
Peace

Hmm... nice finding. Does it give any major boost in eg VR applications that are most demanding right now? I mean real visible boost in performance, not only benchmarks numbers. Right now I didnt root my P9 because Im happy with it as it is, but if it would give some kick in terms of GPU/CPU speed, I might actually root it again...

I'm not sure you would see any major boost in most applications,and i would also be wary of consistently raising the temp threshhold by nearly 20% for extended periods of time...A burnt out CPU will almost certainly give no real boost in performance...

I had some cpu tweaks on my older xperias that also mess with throttling, and on some VR applications difference was not big but visible, from 5 to 9fps, sound really small, but in VR where you actually need stable 60fps to get proper experience(and less motion sickness, because low fps is actually main reason for that) every fps is important. So if in VR sesion that take from 10 to 30min if it would give me additional 5-10fps I would consider it as a good result.
True that more heat on such small component is not good, but I think 65C is not that "big", I actually once time checked temp of my xperia z3 without a back cover using Infrared thermometer from work and in heavy game running, cpu area had almost 72C -_- with cover it dropped to 63C, so metal back cover of P9 should keep it cool for that 30min of fun with VR

chris5s said:
The attached file placed in your init.d folder with the correct permissions will do the job :good:
Once downloaded, remove .txt from the file name, it doesn't need that extension but i couldn't upload it without it
Peace
Click to expand...
Click to collapse
Hello thx for the . Txt u did i'll try it!
Other thing about temp, it's the temp of the cpu so 65 is not really high coz i know lot of cpu could reach sometime 80 to 90 degrees and if you look on the folder, you have another file with second security given to 80°C Cpu

Just a warning, its perfectly fine to set the throttling to start after 65 degrees but I wouldnt advise you go any higher for those people thinking "I want to squeeze more out so lets change it to 75 degrees".
Just remember that there is some downsides to running hotter CPU/Phone, higher battery drain and reduced lifespan of the phone/components are some of them. Just keep this in mind, there is a reason why Huawei set it to 55 degrees however like many of you, I like to get the most out of my phone and things like shortening the lifespan of the components or a slight battery drain does not bother me.

Related

128MB and cache performance

for anyone who has upgraded to 128MB device, I've been doing a little research into putting all that extra RAM to good use and imroving the preformace of the Universal.
Had a little more time to sit down and test the pagepool think properly. Don't actually think that changing it made any difference and we're probably better off with having none (And it shouldn't really make much difference when I think about it)
Have tried both "Beast & Leos" and Ivans latest. There are a couple of things which make a big difference. First up is increasing the Glyph cache. The optimum value I found was around 65536.
The second thing that seemed to make the most difference was the File system Filter Cache. I set this at 16384.
I've set the File system cache to 8192. Though not sure of the benefit yet. There may be a link between the performance and the highresources cab but still investigating this.
With these settings at reset I get around 68Mb of RAM free. Not much free if your still on 64MB RAM!
The difference to system performance is marked though. One of the best examples is loading up the windows folder which usually has a noticable lag is "almost" instaneous. The TCPMP benchmark I got with the tweaked settings was 322% playback speed and 2.5Mbit/sec transfer rate. For this test setup this is by far the best performance obtained on any ROM I've tested.
PS Am also using the performance tool to OC to 624Mhz Dynamically.
WizP said:
There are a couple of things which make a big difference. First up is increasing the Glyph cache. The optimum value I found was around 65536.
Click to expand...
Click to collapse
How about the value 131072 (decimal) or 20000 (hex)?
How would that change your test keeping everything else the same?
WizP said:
PS Am also using the performance tool to OC to 624Mhz Dynamically.
Click to expand...
Click to collapse
How is the effect on the battery?
Best regards,
KOR!
King of Rapture™ said:
How about the value 131072 (decimal) or 20000 (hex)?
How would that change your test keeping everything else the same?
How is the effect on the battery?
Best regards,
KOR!
Click to expand...
Click to collapse
Seemed to make things slightly slower at 131072, but am curious to see how other fair!
As for the battery if anything the battery life is slightly better. - I'm not running processor intensive applications all the time to while the Universal is "snoozing" its should be sitting around 300Mhz.
Does anyone know exactly how this app works? I am curious as the other tools I've use i.e. Pocket Hack Master always show the processor speed in TCPMP but this little app doesn't. however adjusting the speed does appear to change the playback percentage!
hi WizP,
you are absolutely right! the processor does slow down to 300Mhz when no app is running.
i'm using Battery Status today plug-in by Chi-Tai DANG (freeware, found here at xda-dev) to display CPU speed & it does shows 300Mhz when CPU is idle.
the performance tool really works, although i don't overclock beyond 520Mhz. i use the performance tool more for battery saving than for it's overclocking facility.

[How To]Modify HTC One's Thermal Files For Your Own Need

Sorry for poor English
It is well-known that HTC encrypted their thermal config file, thermald.conf, to prevent users from modifying. Since 4.2.2, it throttles both gpu and cpu when battery reached 40C. It is not a good idea, since it cannot satisfy both those who want coolness and those who want extreme performance. As a result, users and devs have to use a custom thermal solution.
It is a good solution to have a 3rd party thermal management, but I believe there are people who want to use stock kernels or to use powersaver function. So I am here to start a thread about how to write a thermal config file for our own needs.
Requirements
1. a computer with adb and related drivers properly installed
2. your phones rooted
3. wp_mod.ko installed properly or using custom kernel
Step 1:
Find more information about temperature sensors
1. enable usb debug
2. connect your phone to the computer
3.1. input the following
Code:
adb pull /proc/last_kmsg
you can find adb.exe in sdk:http://developer.android.com/sdk/index.html
4. open the file, and search "sensor"
3.2. input the following
Code:
adb shell
cat /sys/devices/virtual/thermald/thermald_zone*/temp
* is the number of sensor you wanna checkout. it ranges from 0 to 11
the number displayed is the current temperature on this sensor
The following is the info I analysed, some of which may be incorrect
Code:
thermal_zone0: enabled, related to cpu
thermal_zone1: enabled, related to cpu
thermal_zone2: disabled, probably related to motherboard
thermal_zone3: disabled, related to cpu
thermal_zone4: disabled, probably related to motherboard
thermal_zone5: disabled, probably related to motherboard
thermal_zone6: disabled, probably related to motherboard
thermal_zone7: enabled, related to cpu
thermal_zone8: enabled, related to cpu
thermal_zone9: enabled, related to cpu
thermal_zone10: disabled, related to cpu
thermal_zone11:disabled, unknown
Step 2
create a txt file on your computer, rename it "thermald.conf"
Step 3
open the "thermald.conf" file you just created
Step 4
Write the first line:
Code:
sampling 5000
the number indicates the time interval of the system to scan the temperature, but I doubt whether it has any function now. Also I suggest to leave it unchanged.
Step 5
Define the sensor you want to use and configure its thresholds
Code:
[tsens_tz_sensor2]
sampling 1500
thresholds 54 57 64 70 75
thresholds_clr 51 54 57 64 70
actions gpu+cpu gpu+cpu cpu cpu cpu
action_info 400000000+1728000 320000000+1134000 1026000 918000 702000
Code:
[tsens_tz_sensor2]
the number after the word "sensor" means the sensor you want to use and config
Code:
sampling 1500
time interval of scanning, strongly recommended to leave it unchanged
Code:
thresholds 54 57 64 70 75
As it says, these are the thresholds that trigure actions
For example, the number 57 means that if the temperature of this sensor is over 57C, gpu will be throttled to 320mhz and cpu will be throttled to 1134mhz
Code:
thresholds_clr 51 54 57 64 70
These are the thresholds that make system to do the former action
For example, the number 54 means that if the temperature of this sensor is under 54C, gpu will be set to 400mhz and cpu will be set to 1728mhz
NOTE: it is strongly recommended to match the (n+1)th thresholds_clr to the nth thresholds, except threshold that trigures shutdown action
Code:
actions
These are the actions you want to take, like throttling cpu, gpu and even brightness.
If you want to take multiple actions, just use "+" to connect
For example, if you want to throttle both cpu and gpu
just type
actions cpu+gpu
If you does not want to take any action, just type: none
*actions:
Code:
cpu
gpu
lcd
battery
none
Code:
action_info
These define the values of actions defined earlier.
For example,
Code:
actions cpu+gpu
action_info 1134000+320000000
means to throttle cpu to 1134mhz and 320mhz
NOTE: The sequence of action info should EXACTLY MATCH the sequence of actions
For example, if you type
"cpu+gpu" in actions line
you can only type first, the cpu frequency you want to set, second, the gpu frequency you want to set
you CANNOT type it like this:
Code:
actions cpu+gpu
action_info 320000000+1134000
It can confuse the system when it decides to throttle
cpu frequency table:
Code:
384000 486000 594000 702000 810000 918000 1026000 1134000 1242000 1350000 1458000 1566000 1674000 1728000
gpu frequency table:
Code:
400000000 320000000 200000000
lcd
any value below 255. 255 means not to lower the brightness
battery
Code:
+1
+2
I don't know what these values mean, but it is for sure to be able to lower temperature
none
Code:
0
Step 5
save it and put it in your system
put the thermald.conf file in the folder where your adb.exe is placed
adb:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p35 /system
adb push thermald.conf /system/etc/
adb shell chmod 644 /system/etc/thermald.conf
or use recovery to flash
I will post scripts in attachments
Sample
Code:
sampling 5000
[tsens_tz_sensor0]
sampling 1500
thresholds 34
thresholds_clr 32
actions none
action_info 0
[tsens_tz_sensor7]
sampling 1500
thresholds 34 36 45 48 57 66 75 95
thresholds_clr 32 34 36 45 48 57 66 90
actions cpu+gpu cpu+gpu cpu+gpu cpu+gpu cpu+gpu cpu+gpu cpu+gpu cpu+gpu+shutdown
action_info 1728000+320000000 1134000+320000000 1026000+200000000 918000+200000000 702000+200000000 486000+200000000 384000+200000000 384000+200000000+5000
[tsens_tz_sensor8]
sampling 1500
thresholds 34 95
thresholds_clr 32 90
actions none shutdown
action_info 0 5000
[tsens_tz_sensor9]
sampling 1500
thresholds 34 95
thresholds_clr 32 90
actions none shutdown
action_info 0 5000
[tsens_tz_sensor10]
sampling 1500
thresholds 34 95
thresholds_clr 32 90
actions none shutdown
action_info 0 5000
Update
10/12/2013 replaced thermald_boot to prevent pnpmgr from changing config files [email protected]
Downloads
I've modified some thermald files for those who do not want to modify it by their own.
Stock thermald config file from htc:
cpu throttles when reaching 57C. both cpu and gpu throttles when battery temp reaches 40C
View attachment stock_thermal.zip
Stock no gpu:
cpu throttles when reaching 57C, no gpu throttling
View attachment stock_no_gpu.zip
Cool Version:
cpu throttles at 46C, no gpu throttling
View attachment cool.zip
Extra Cool
cpu throttles at 40C, no gpu throttling
View attachment extra_cool.zip
Ultra Cool
cpu throttles at 36C, gpu is limited at 320mhz
View attachment ultra_cool.zip
Performance
cpu will not throttle until 76C, no gpu throttling
View attachment performance.zip
NOTE: without changes of voltages/drivers/kernels, less heat means less performance. cpu performance is noticeably influenced if cpu freq is lower than 1134mhz. if gpu is at 200mhz you will feel laggy in everything.
Hopefully you guys will enjoy this
This is excellent work! where have you been 6 months ago :laugh:
but now we can finally use stock kernel without the risk of disabling throttling completely
I didnt understand one thing, after we create the text file, shouldnt we encrypt it again?
hamdir said:
This is excellent work! where have you been 6 months ago :laugh:
but now we can finally use stock kernel without the risk of disabling throttling completely
I didnt understand one thing, after we create the text file, shouldnt we encrypt it again?
Click to expand...
Click to collapse
One is so hot that I didn't get this phone before May...I would have been very happy if I have had this phone 6 months ago
4.1.2's default thermald file worked fine, but 4.2.2's one annoyed. I was waiting for some devs to decrypt the config file but no one seems to care about that. Since One is a qualcomm device, custom thermald file should work if the right language is used. It works indeed. I am now using Bulletproof with cool version, very cool indeed, and with the full function of powersaver, since I do not need to disable the thermald daemon anymore
no need to re-encrypt. no one knows how and why htc encrypt those things. It works fine without encryption, just as one can flash a decrypted ruu zip file.
jerrylzy said:
One is so hot that I didn't get this phone before May...I would have been very happy if I have had this phone 6 months ago
4.1.2's default thermald file worked fine, but 4.2.2's one annoyed. I was waiting for some devs to decrypt the config file but no one seems to care about that. Since One is a qualcomm device, custom thermald file should work if the right language is used. It works indeed. I am now using Bulletproof with cool version, very cool indeed, and with the full function of powersaver, since I do not need to disable the thermald daemon anymore
no need to re-encrypt. no one knows how and why htc encrypt those things. It works fine without encryption, just as one can flash a decrypted ruu zip file.
Click to expand...
Click to collapse
Ah although i attempted to use the SGS4 themrald on 4.1.2 and it didnt really work, so i guess like you said the proper wording is important
excellent, did you try these on the 3.17 kernel ?
so we only wp_mod.ko in case we push from ADB right? flashing from recovery shouldnt need this
hamdir said:
Ah although i attempted to use the SGS4 themrald on 4.1.2 and it didnt really work, so i guess like you said the proper wording is important
excellent, did you try these on the 3.17 kernel ?
Click to expand...
Click to collapse
First, sensors may be different on the 9505. Second, 9505's thermald is different. It uses soft-link to thermald-8064ab.conf, and its values are obsolete, from which I think samsung does poorly on system optimization. since it uses soft links, one's thermald binary may not support that kind of configuration.
It works very well on all stock kernels. I used 3.17 kernel for a long time, for it does not give me purple/pink issue in low light(I have no problem in 4,2,2, it should be the drivers' fault)
Yes you don't need wp_mod.ko if you use recovery to flash thermald.conf.
jerrylzy said:
First, sensors may be different on the 9505. Second, 9505's thermald is different. It uses soft-link to thermald-8064ab.conf, and its values are obsolete, from which I think samsung does poorly on system optimization. since it uses soft links, one's thermald binary may not support that kind of configuration.
It works very well on all stock kernels. I used 3.17 kernel for a long time, for it does not give me purple/pink issue in low light(I have no problem in 4,2,2, it should be the drivers' fault)
Yes you don't need wp_mod.ko if you use recovery to flash thermald.conf.
Click to expand...
Click to collapse
hold on 3.17 solves the tint issue?
I will post details about your find in my information threads, thanks a lot, this is gold
there is only problem! now i have to rewrite my entire Gaming OP
hamdir said:
hold on 3.17 solves the tint issue?
I will post details about your find in my information threads, thanks a lot, this is gold
there is only problem! now i have to rewrite my entire Gaming OP
Click to expand...
Click to collapse
Sorry for the inconvenience
No, as I said, I have no problem under stock 4.2.2 & 3.09 & 3.17, I only have purple/red issue when I am using 3.17 custom kernel with camera hack. Some users reported that the issue is ameliorated but not fully solved in stock 3.17 system
@jerrylzy you think there is an easy hack for stock kernel to OC the GPU into 450mhz?
hamdir said:
@jerrylzy you think there is an easy hack for stock kernel to OC the GPU into 450mhz?
Click to expand...
Click to collapse
Really? Theoritically, we cannot oc anything without compiling a modified kernel source...
jerrylzy said:
Really? Theoritically, we cannot oc anything without compiling a modified kernel source...
Click to expand...
Click to collapse
well I was just asking if there is a way
anyway listen this might be wrong but I really feel you should fix your patch zip files, by duplicating the txt thermald.conf as thermald_boot.conf as well, I feel I'm getting better performance this way out of stock kernel
I used to have weird stalls in games, all fixed after I also replaced thermald_boot, still I'm not sure but there is no harm in doing this
@jerrylzy i don't think the thermald_boot is related to the stalls i've been feeling
I think the stock no gpu 57c arrives sooner than I accepted so when the threshold is hit and it throttles down a full 500mhz on the CPU we get noticeable drop in CPU hungry games like Asphalt 8 (although no where near as noticeable as the GPU throttle)
I think we should cook a thermald which gradually scales down the CPU, something between the stock no gpu and performance, but it scales down in steps instead of a sharp 500mhz drop
one more thing i noticed, while the threshold is 57 for stock no GPU, i feel its actually threshold_clr 54 which is actually being used but I can't confirm since the CPU temps drop down so fast between switching out of game to a CPU monitor app
for now the solution is your performance zip file, but i noticed you are probing a lot more Sensors in the performance patch unlike the other files, can you elaborate?
hamdir said:
@jerrylzy i don't think the thermald_boot is related to the stalls i've been feeling
I think the stock no gpu 57c arrives sooner than I accepted so when the threshold is hit and it throttles down a full 500mhz on the CPU we get noticeable drop in CPU hungry games like Asphalt 8 (although no where near as noticeable as the GPU throttle)
I think we should cook a thermald which gradually scales down the CPU, something between the stock no gpu and performance, but it scales down in steps instead of a sharp 500mhz drop
one more thing i noticed, while the threshold is 57 for stock no GPU, i feel its actually threshold_clr 54 which is actually being used but I can't confirm since the CPU temps drop down so fast between switching out of game to a CPU monitor app
for now the solution is your performance zip file, but i noticed you are probing a lot more Sensors in the performance patch unlike the other files, can you elaborate?
Click to expand...
Click to collapse
In the new "stock no gpu" patch I added a step of 1566mhz between 1728mhz and 1134mhz. Also the reason why I added a lot more sensors for performance path is that I added a lot more sensors to prevent the cpu from too hot, which is harmful to both the cpu and the battery. Actually, it should not be as hot as that. I personally used stability test to check the thermald patch. with quad core 1.7g running more than 5 minutes, the temperature of my cpu never went higher than 65C. I am on PVS 4 bin.
jerrylzy said:
In the new "stock no gpu" patch I added a step of 1566mhz between 1728mhz and 1134mhz. Also the reason why I added a lot more sensors for performance path is that I added a lot more sensors to prevent the cpu from too hot, which is harmful to both the cpu and the battery. Actually, it should not be as hot as that. I personally used stability test to check the thermald patch. with quad core 1.7g running more than 5 minutes, the temperature of my cpu never went higher than 65C. I am on PVS 4 bin.
Click to expand...
Click to collapse
ok great, I was sure this is why you added those sensors good work, so performance patch is pretty safe I assume? i also have the same bin
I checked the new stock_no_gpu good work mate :good:
but i think i will go with performance

[GUIDE] Advanced Interactive Governor Script - Battery Life

Remember to have the screen turned ON while you apply the script!!!
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
One of them in particular was extremely good battery wise but i felt some lagginess here and there (talkin about HawkTail 1.2)
So i decided to make a script myself and share it with you, the idea behind it is to force the CPU to scale better with loads and making the Big cores in use more frequently by tuning some of the kernel parameters.
Plus we will have the GPU idling @ 180MhZ instead of 300MhZ (like in the Nexus 5x) and a switch to noop scheduler.
Performance wise and taking in example the latest stable ROM from Xiaomi.eu (8.0.5) we will have a decrease of about 5k point in Antutu (I'll attach two screenshots, the 71K was the result without tweaking, plus just by switching back to CFQ scheduler you'll get 2K points back but NOOP is more battery friendly)
So here you go, this is my script TAO.
Using it is pretty simple and you have a couple of options: [ROOT IS NEEDED]
Since it's a script, if your rom have INIT.D folder support, you can just move the file under /etc/Init.d and reboot the device. The script will make a log file under /sdcard/TAO.log that you can check if anything went wrong.
The second option, if your rom doesn't have Init.d folder support, just use Kernel Auditor and a text editor.
Open the downloaded file in a text editor, select all and copy the text.
Then open Kernel Auditor, and in the menu look for init.d, enable the "Emulate Init.d" and then click the "+" symbol. It will ask to add a name (let's set it to TAO for coherence), then OK. It will open a new window where we have to paste all the text previously copied, save it by pressing the icon on the top right. Now we can just reboot the device or click the newly created item and select execute.
Third option is to run it manually from terminal.
Plus, i'll add my Thermal-engine-8992.conf that you guys can use to change the thermal throttling values. Download it and replace it in /system/etc/ , set it with permission 644 and reboot.
This modded thermal will move up the limits, long story short, your device will continue to perform even if it gets hot.
Enjoy! & report back for feedback
Remember to have the screen turned ON while you apply the script!!!
P.S.
Files are zipped, extract them!!!
UPDATE
Minor update - use_sched_load set to 0 for both cores
Correction made for the log file
UPDATE 0.7
Since @solis_f is having some problem with the big cores, and this could be a common problem to many others too i've decided to add something in the script that will force the big core online so you should not have any more problem executing the script. Let me know
UPDATE 0.8 - Experimental
Updated Target_loads for both Little and Big cores.
Little core min freq. to 384 MhZ.
Input boost @ 787 MhZ instead of 600 MhZ.
hispeed_load disabled for both cores.
Updated values for UpMigrate.
Enabled core_ctl for big cluster:
With this update, you'll have your big cores Offline most of the time, but they will comes online when needed.
Yours perfd (/data/system/perfd/default_values) with this version have to look like this:
Code:
ihf;787200
iahd;38000
ighl;200
itl;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
gpu_default_pwrlvl;5
sst;33
smil;20
sminr;3
sitl;65
sum;66
sdm;54
cbmf;1525
cbhdr;90
cbhip;16
ihf0;787200
iahd0;38000
itl0;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
imst0;0
ighl0;200
imf0;0
itr0;30000
its0;-1
iiib0;1
intb0;0
ibd0;0
ihf4;1248000
iahd4;38000
itl4;53 768000:64 864000:72 960000:79 1248000:99
imst4;0
ighl4;200
imf4;20000
itr4;30000
its4;-1
iiib4;1
intb4;0
ibd4;0
P.P.S.
Over two hundred downloads, but not even half of you gives me feedback...
UPDATE 0.9
Sorry for the delay, many things to do IRL.
This version is what i'm using now, should be smoother then v0.8, hope you like it.
nice one, will try this
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
predragiPredrag said:
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
Click to expand...
Click to collapse
I did not, but degradation of score is dictated by the thermal config. That's why i modded that too, and pushed the standard limits...
Let me show you with an example:
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type ss
sampling 250
sensor xo_therm_buf
device cluster1
set_point 43000
set_point_clr 37000
time_constant 0
device_max_limit 800000
This is taken from the original file, and it covers the big cluster... when it reach 43° celsius, the thermal throttling will limit the max frequency of the cluster to 800MhZ
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type monitor
sampling 5000
sensor quiet_therm
thresholds 46000 48000 50000
thresholds_clr 44000 46000 48000
actions cluster1 cluster1 cluster1
action_info 1632000 1248000 960000
This is the same part but modified by me, i've added more step... as you can see thermal throttling for big cluster will work once the big cluster reach 46° and it will cut the max frequency to 1632MhZ, then at 48° 1248MhZ and at 50° at 960MhZ
The hot-plug, that put the cores offline, on the original file for the big cluster is marked at 42° for core 4 and 45° for core 5.
On my config file both cores will be hot-plugged once they reach 52°.
TL;DR if you use my thermal-engine conf file, you will get more consistent score on several runs.
Nice to hear that will try this when I have more time to play with my phone and report back.
Great work and thanks for sharing this
GoldGanja said:
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
(...)
Enjoy! & report back for feedback
P.S.
Files are zipped, extract them!!!
Click to expand...
Click to collapse
Hi,
I can not apply root because of he problem between pokemon go and root, (I am playing pokemon go with my 8 years old son a father-son activity and he loves it)
I am using a dev miui rom and i did tune my thermal-engine and remove the input boost using the TWRP file manager to apply the files.
This rom does not have init.d folder could i call your script from init.qcom.post_boot.sh? if so, do you know how to?
best regards,
John
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
GoldGanja said:
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
thanx, my son does not talk about anything else...
About the chain load the TS rom does that with ts_power.sh file.
Code:
# ts power scripts permissions
chown -h system /system/etc/ts_power.sh
chown -h system /data/ts_power.sh
Code:
# Call ts_power.sh, if found
if [ -f /data/ts_power.sh ]; then
logi "Call /data/ts_power.sh set_profile $profile"
sh /data/ts_power.sh set_profile $profile
elif [ -f /system/etc/ts_power.sh ]; then
logi "Call /system/etc/ts_power.sh set_profile $profile"
sh /system/etc/ts_power.sh set_profile $profile
fi
I will try to see if it works using your script.
About systemless root, i don't want to be in the middle of the cat and mouse thing. Today google update and tomorrow there is another hide root.
I did replace the thermal engine using the twrp file manager. It works.
Nice share bro. Thermal engine + init.d script is good battery backup for mi4c.
Hello,
could you make patched files available and the place where they should be placed ?
I don't want to root my phone but I want to give your optimisation a try. It is possible with TWRP to replace the files in the file manager. More work but it can be done without root. Therefore however I will need the allready patched files....
A little more "complicated" even... might it not be possible using TWRP to flash these files ? I have no idea how that would work exactly but I can imagine it would be possible to create a flashable zip that replaces these files... It currently goes beyound my abbilities though unfortunatly but maybe someone can help with that.
Thanks for your share @GoldGanja , looks interesting.
But i think the thermal-engine.conf would cause more overheating as it is already (for me reduce overheating is the most important), but i like the way to reduce the clockspeed step by step. Maybe i will try it with lower values.
The modified governer looks great. I think this will help with heating too. But on this there aren´t laggings ?
Thank you! i hope this fix my battery drain and the heat, i'll report if i see changes
@nachtwacht
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
@Danny94
thermal-engine.conf per se will not increase or decrease over-heating, of course one could make a conf file to be more restrictive on the temps and brutally decrease the performance but i don't see the need of this because i don't have any over-heat problem within my device with the script i've made. A major cause of over-heating is the input-boost frequency that by default is set to 1248MhZ, while if you run my script it will be 600 MhZ. Farther i have no lags at all...give it a try and report back. More feedback I have about it, the better I can adjust some parameters.
@HYBRIDEMON
Thanks!
@GoldGanja
Yeah i will try tomorrow if i get some free time.
Wich Rom do you use ? I have at almost all roms overheating problems. After 10 min+ of 3d gaming i have ~55°c + (On my old phone Thl 5k i could play the same game hours, don´t get over 45 °c and no lagging or something - and yeah its not the best phone).
With your thermal config the device throttles later. So it will heat higher, until it shut down big core etc. As hotter it becomes as more difficult its to cooldown. Sure if you won´t reach 52°c would be perfect one. But maybe i will replace the values with lower, else it looks very good.
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
siba01 said:
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
Click to expand...
Click to collapse
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
GoldGanja said:
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
Click to expand...
Click to collapse
Maybe I was not clear or, more likely I do not completely understand which is a fact for sure
Let me clear up the first part, then hopefully in the end I will also better understand
Your script chances several files if I understand correctly ? scaling_min_freq for example is the first one you change in the script ?
Could we not update all the files that you change using TWRP ?
My guess is, (that's just me trying to understand better.....) that I think that using TWRP it is possible to change these files without root, but in reality it is not because the phone is not rooted ? Maybe because only the complete system can be changed and not single files ? (without root)
I do know that in the end, for me it is possible to root my phone, apply the settings, and then unroot it again.... which hopefully have my phone working like it never was rooted... it's just a risk I would like to avoid if in any way possible, therefore I am investigating and trying to get it all clear for me, sorry for that
GoldGanja said:
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
Click to expand...
Click to collapse
I'm using Resurrecction Remix.
Thanks for your answer.
Enviado desde mi Mi-4c mediante Tapatalk
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
solis_f said:
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Mi-4c using Tapatalk

(GUIDE) LG ARISTO (LGMS210) CHANGE CPU MAX FREQUENCY (1401MHz)

I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE BY IMPLEMENTING THIS MODIFICATION!!
IMPORTANT: THIS IS A RELATIVELY NEW TWEAK I HAVE IMPLEMENTED ON A DEVICE I DO NOT USE AS A DAILY DRIVER. I HAVE ONLY BEEN USING THIS ARISTO AS A TEST FOR 4 DAYS WITH THIS MOD IN PLACE (AT THE TIME OF THIS WRITING). I DO NOT KNOW HOW STABLE THIS IS, OR IF ANYTHING WILL RANDOMLY KNOCK OUT MY TWEAKS, BUT SO FAR SO GOOD. BUT . . . . ALWAYS REMEMBER, YOUR MILAGE MAY VARY!! PLEASE SHARE YOUR EXPERIENCE WITH THIS TWEAK SO WE CAN IMPROVE ON IT'S STABILITY!!
So here's the story . . . .
My girlfriend got a free LG Aristo from MetroPCS when she switched carriers, which was a damn good deal IMHO. After using it for a month or so, she's pretty happy with it, aside from the usual gripes that come with low-midrange devices. I repair phones and computers for a living so I wanted to tinker with it and see what, if anything, could be done to give it that little bit of extra 'oomph' in performance, battery life, etc. Since it's her only device I didn't wanna risk depriving her of her phone if anything went sideways, so I kept my eyes open for an Aristo to pop up, and the other day, one did! One of my clients texted me asking if I wanted to buy a broken Aristo for parts, and considering the only thing wrong with it is a cracked screen, I jumped on it.
So, now that I have the guinea pig Aristo to play with, I did a quick search to see what kind of dev community this device had here, and on XDA. I stumbled accross this post with a working TWRP v3 (BTW, mad props to messi2050 for the TWRP v3, no-verity-opt-encrypt script link, and tutorial! MANY THANKS!).
I was a little surprised that the Aristo has an easily unlockable bootloader, so I give credit to LG for giving folks the option to do what they want with THEIR device.
With the bootloader unlocked and TWRP installed, I went ahead and formatted the /data partition to disable encryption (AFTER MAKING A NANDROID OF CORSE!!). After rebooting back into TWRP, I transfered the no-verity-opt-encrypt script and Magisk v13.2 and flashed them (IN THAT ORDER).
Magisk was a must since my girl plays Super Mario Run, and a few other games/apps that check Safety Net, and I'm happy to report that with Magisk v13.2 installed, Safety Net passes without issue.
Now comes the issue of LG underclocking the Snapdragon 425. Looking at it from LG's perspective, I understand the logic behind this implementation; a lower max_freq is definitely gonna give you a bit of extra battery life, and since low-midrange devices like the Aristo are unlikely to be used for anything more than calling/SMS/MMS, web browsing, YouTube, and light gaming, they probably figured that that bit of extra performance wouldn't be missed by most people buying this device.
The Snapdragon 425 has a max CPU clock speed rated at 1.4GHz, however, the LG Aristo tops out at 1.25GHz (1.248GHz). Using flar2's EX Kernel Manager (I use ElementalX on ALL of my other devices, but his kernel manager app works with ANY kernel), I couldn't get the max-freq to stick at 1401MHz. Strangely, it would max out at either 1248MHz, or 1094MHz, and even setting it to apply on boot proved futile. Then, I noticed that the frequency range in CPU-Z was '960MHz - 1.25MHz', so then I headed for the source:
/sys/devices/system/cpu
In this folder you will see the following folders:
cpu0
cpu1
cpu2
cpu3
Interestingly enough, the max rated frequency of '1401000' is listed in the 'scaling_available_frequencies' file of each core, meaning that specific frequency can be controlled by the kernel (CPU governor) if directed via each core's 'cpuinfo_max_freq' file.
(NOTE: This guide will walk you through changing the max_freq only for cpu0, however, the method for cpu0 is identical for cpu1, cpu2, and cpu3, so just repeat the steps for each cpu core)
Step 1.) Open the folder 'cpu0' [/sys/devices/system/cpu/cpu0]
Step 2.) Inside the 'cpu0' folder, find the folder 'cpufreq' [/sys/devices/system/cpu/cpu0/cpufreq]
Step 3.) Inside the 'cpufreq' folder, find the file 'cpuinfo_max_freq' [/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq]
Step 4.) Open it with a text editor (I am using Solid File Explorer w/ Root add-on which has a built in text editor, but ES File Explorer, Root Explorer, etc. all have built in text editors)
Step 5.) Change the value from '1248000' to '1401000' (WITHOUT ' ' MARKS OF COURSE!!)
Step 6.) Save the file after making the changes.
Step 7.) Repeat the above steps for the remaining 3 A53 cores. If you need to follow the guide for each core, just change the 'cpu0' in STEP 1 to 'cpu1', then 'cpu2', etc.
Step 8.) After making the changes to each core and saving your edits, exit out of your file manager and reboot (Now, if you go back to look at your edit after saving the cpuinfo_max_freq, it will appear as if your edit did not stick, but trust me, it will stick when you reboot).
Step 9.) After rebooting, open your root file explorer and check the edits you made to each core's 'cpuinfo_max_freq' file. They should now all read '1401000'.
Step 10.) Open your preferred kernel editor/auditor app and change the max frequency to 1401MHz, and this time it will stick. If it does not stick, simply change your CPU governor to 'Performance', then set the max to 1401MHz and that should make it stick. After that, close your kernel tweaking app and open CPU-Z or some other app that shows the current CPU frequency and check that it's locked at 1401MHz. Once you see that it's locked at 1401MHz, go back into your kernel tweaking app and change the governor back to your desired setting (I'm using Interactive), then check to see that the CPU max frequency is still locked at 1401MHz.
Step 11.) DON'T FORGET TO SET YOUR KERNEL EDITOR/AUDITOR TO APPLY THE CHANGES ON BOOT!! For some reason, if you don't set on boot it will randomly change the max speed between 1094MHz and 1248MHz.
Step 12.) PROFIT!!
NOTES:
- Solid File Explorer automatically mounts /system -rw when you open it. I'm not sure about other root file explorers, so make sure you mount /system -rw or your edits will not save/stick
- This is a relatively new tweak, so if anyone can expand on what I've covered here, please do!!
It won't let me save the edited text
Nice work!!! Also looking at the LG. K20 as well as the LG Tp450(Stylo 3+). I am curious to see if LG intentionally underclocks all...or at least the only ones this poor bastard can afford...LoL
Doesn't seem to work for me. Max CPU frequency frozen at 960 MHz ?

[GUIDE] Disable S8 Exynos throttling (DVFS) the Easy Way

Introduction:
This will remove the performance throttling of our S8 when using it heavily (gaming, movie streaming, or any demanding stuff we do on our phone). Oh and benchmarks also. There has been numerous threads of disabling DVFS from previous Exynos phones such as Note and Galaxy S4 and so on...
Note: This tweak will not INCREASE your phone's performance as is, but to remove limiting factor such as heat when it comes to heavy usage of phone. Removing throttling could cause too much heat to your phone or worse.... could cause device and physical harm to you. Be cautious and be warned when using this. I'm not responsible for any damages that this tweak would do to you.
Verdict: Heat generated was acceptable, but this depends on every users with different setups/installed apps on their phone/usages.
Requirements:
1. Rooted Galaxy S8 Exynos (this could work probably in S8+/Note 8 Exynos variant????)
2. Kernel Adiuotor (preferred) or any tool that has Init.d support.
Steps:
1. Download Kernel Adiutor from Playstore.
2. Open the app and go to Menu > Tools > Init.d.
3. Toggle the Init.d to enable script at boot.
4. Click "+" button and name it anything you want then click ok.
5. The editor will open, now copy and paste this script in the editor.
#!/system/bin/sh
chmod 0000 /sys/devices/14ac0000.mali/dvfs
chmod 0000 /sys/devices/14ac0000.mali/dvfs_max_lock
chmod 0000 /sys/devices/14ac0000.mali/dvfs_min_lock
6. Then click save button.
Now you can click the script and execute it or reboot to check if the script has been executed.
To check if the script is executed you may use Root Explorer Paid version and go to this directory,
/sys/devices/14ac0000.mali/
and look for dvfs file, if you see that the permission is --- or blank, that means the script has been applied.
Let me know if this works for you all.
Benchmarks are nothing but tbh, it will show if throttling affects the result. I haven't captured the 1st result but I got 130kish when he devices was 50~60°C.
I run the script and quickly rerun Antutu again. See attached image below.
https://en.wikipedia.org/wiki/Thermal_runaway
Your choice.
Will this also work on my s9+. On my s8 it works like a charm.
How to remove if this one is applied?
Just reboot ur phone
This is like to remove rev. limiter. Engine gone to blowww.
It work s7
Tank you . Now it give a life on my divice . No down clock aft few min on gaming . Happy .
can I do this with adb as well? I just purchased the S10+ ( exynos ofc) and I dont want to root it, not because I cant but if want to sell it some buyers will not be interested without no google pay, netflix , samsung pay etc. If I can do this with a adb command I would really like to know.
I think this disables GPU Throttling only not CPU right?.. Does anyone knows a way to disable the CPU Throttling? Im running a custom kernel on S7 FLAT EXYNOS Overclocked to 2600MHZ but after 2 minutes frequency drops to 2394MHZ Due to cpu throttle.
Edit: I dont care about the battery i just want a gaming phone and i know the risks.
s8userhere said:
How to remove if this one is applied?
Click to expand...
Click to collapse
Reboot

Categories

Resources