Database Develop

Overclocking App available in the market!

Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.

just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz

Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.

well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together

At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.

speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting

@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)

I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?

Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked

andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?

andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands

ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry

I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...

ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)

damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?

Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth

wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.

A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...

damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar

well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.

[Q] CPU throttling on Revolution

Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.

hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
I honestly don't think anyone has been messing with the CPU until the CM ROM is released.

hadookee said:
Long time lurker, but 1st time poster.
I've noticed on my Revolution that the CPU always runs at 1ghz. I thought CPU throttling was a standard feature in android?
Anyhow I installed CPU tuner and I get much better standby battery life now (~2% drain/hr when not using phone vs. ~5% drain/hr on standby). The phone runs mostly at 124mhz w the screen off. My problem is my revolution reboots pretty frequently and sometimes even just completely shuts down w CPU tuner on. I still get reboots once in awhile w CPU tuner turned off, but much less frequently.
Anyone else having this problem? I also have green power running in the background to turn off the data connection w the screen off. Are you guys who use setCPU not getting reboots? If so I'll spend the $2 and give that a try.
Click to expand...
Click to collapse
As far as I've seen, the Revo's CPU does automatically speed scale to the necessary load.
If you're running lots of apps in the background, with the screen on Android will keep the cpu at full throttle to provide a smooth experience for you.
As soon as you turn off the screen, it will throttle it down as much as it can.
If the phone's rebooting on you, that's because whatever cpu tuner is doing may be keeping the cpu speed too low for the demand of the OS, then the watchdog kicks in when it thinks the cpu is stuck in a loop. (watchdog wants to be petted every 30 seconds, if the cpu misses that, the watchdog reboots the phone)

I use setcpu and have no reboot issues.
Sent from my VS910 4G using XDA App

throttle
I use android system info to show the CPU speed. It shows the % of time my revolution is running at each speed. W/o using a 3rd party app it always shows 100% at 1Ghz. W CPU tuner running it shows 50% at 122Mhz, 25% at 1Ghz, and 25% in between.
I don't think I'm running any apps thats sucking up a lot of CPU. I'm rooted w most of bloat removed.
Am I the only one not seeing any CPU throttle on stock?

i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.

Exactly Im much happier with my phone now. I had the same issue when I received a call but set up the profile as u did and have no problems at all
newkick said:
i'm not seeing any throttling on stock.
setcpu drastically improved battery life when the phone's off, and no reboot issues.
some issues initially with the phone not throttling back up quickly enough when i got a call, making me unable to answer the call, but played with the settings and made it so it automatically throttles back up to 1024 when i get a call, and now it's fine.
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App

I am using setCPU as well with no issues. I have mine set were the screen is off it goes to 124 and clocks back up to full 1GHz when it is on. Helps greatly improve my battery.

So what settings do you use? I get really bad lag when waking my Revo. Sometimes it will reboot after waking too.
Sent from my VS910 4G using XDA App

I don't know if this is a CPU throttling issue, or a general REVO issue, but I get horrible horrible lag sometimes trying to get any programs to respond. Like press the home key, or click send, or anything like that. I'm running Decrap 1.1, I don't know if I have too many processes running or what.

Interesting. The Thunderbolt has the same issue. Is it the same CPU in that phone?

Clocking problems

Hi,
first, I want to apologize for my bad english.
I have a problem with the clockingspeed of my HTC One.
I was impressed by how bad the battery life of the One is.
I found out, that the CPU is always clocking at 1,7Ghz, both values (Min AND Max) are set to 1.7 Ghz.
If I turn on the battery-safe option, it clocks at 1Ghz, but again on both values.
So, I have downloaded some CPU apps, which should let me change the clocking speed of the CPU.
Well, it works, but if I turn on "Set on boot", and reboot, the values are gone.
I thought, this would be caused by the stock ROM, so I have flashed the "InsertCoin" ROM, but no changes.
Has someone the same problem, or does someone has a solution for me?
regards.

The clock speed is dynamically controlled. When the phone is not in use, it should reduce the clock speed.
It sounds like you have an app that is preventing it from sleeping.
Install betterbatterystats and look for partial wakelocks. Feel free to leave a screenshot here.

Hi,
even if there is an app which would prevent my phone from clocking down, the MIN-value should be at 300/400mhz, and not be the same as the max-value ..
regards.

No idea..?

what hes saying is theres a rogue app mostly likely in the background thats pushing your phone that it thinks it should ramp up the speed of your phone. so even if you have it set to 384/1.7 the phone is detecting "oh **** *so and so* app is beastly bump the speed to max 1.7. bad analogy but you get the idea. i would start by wiping the phone install a brand new rom and DONT install anything just the mhz reader. then check. if your on a fully clean flash and still holding at max value all the time. then next is to check the CPU governor. it may have been set to performance at some point "accidentally" the performance governor forces the phone to hold at max speed. mostly only used for synthetic benchmarks.

Nope nope nope.
Nope.
I just had to S-Off my phone ..

[Q] CPU running at high clock most of the time

Updated section:
After clearing cache through recovery and doing a hard reset, the uAh has gone back to 3142000. Standby time seems good with the battery losing 7% overnight. It does charge quite quickly from 0-100 in about 2h. The previous heating issue remains with cpu monitors showing that the cpu jumps to high clock when I touch the screen. I don't see any change in which apps use the most battery with the screen taking up the most as before the problem started.
The heat appears to be what is draining the battery but I can't find any single app that causes it to ramp to max.
Pictures:
No-frills is set to stock settings to see how the phone handles the actions
2nd picture is when phone is idle
3rd picture is immediately after swiping through a few tabs and scrolling through some pages in the app which causes cpu clock and load to increase
Old sectionFor when battery uAh was low)
I've had this Z1 for about 11 months. I can only get around 2.5h on screen time with regular usage. The battery uAh was only 1848000 Recently it fell to the 1700s. Calibration appears to reduce the value further. The phone seems to heat up in about a minute or two no matter what app is running.
The phone is rooted on stock 4.4.2
I have tried updating to Lollipop before but received an error due to rooting, so I don't think anything changed.

bump

alantay11 said:
bump
Click to expand...
Click to collapse
sounds like it's time for you to replace your battery.

You may try to disable the "input boost frequency"
By default when you toch the screen, cpu frequency of two cores instantly jumps to around 1400 to preventing any lag but it seems to use more power and causing heat
I have disables this and since then I'm no longer have any heat issue and also the battery life is so much better now but you may exprience a little lag while scrolling on heavy web pages but thats all
Btw i'm on .157 and using Kernel Adiutor for cpu tweaks
You may disable this by the app mentioned above or by editing sys.somc.touch_perf_kick=1 from 1 to 0 in buid.prop or adding this line

Thermal Settings

I have noticed the Xiaomi Mix has some persistent software thermal throttling after a short period of time.
I ran the same test on a OnePlus 3T and noticed this throttling issue is not present.
It's possible the temps to start throttling are too low on the Mix.
Is there any way to modify or increase these throttle limits?
I know this has been done before but I cannot load the Thermal conf file in /system/ etc / thermal-engine.conf
Can we replace the file with something else ?
The OnePlus forum members released several versions of the file with different throttling temps. Can we use these files or make our own.
https://forums.oneplus.net/threads/oneplus2-how-to-fix-thermal-throttling.417108/

Did you ever get any further with this? My phone idles at ~35C. I read a review that said throttling begins at ~40C so I get throttled when I do virtually anything.
I've only had this thing 2 days and the performance has been worse than my old Nexus 6 because the cores keep getting capped very low. I was copying some backed up files over WiFi from my PC. It was lots of small files so it was running for 20 mins or so. When I was trying to do other stuff in the meantime it started to get really sluggish. I used to do exactly the same thing on my N6 and I could never tell that file copying was running in the background. I checked Kernel Auditor and it was showing temps ~50C and the cores were all being capped around 5-600MHz.
I've tried the stock ROM (stable and beta) and EPIC, and Lineage/RR. It seems to be a bit worse on the latter two (Antutu won't go above 100k, but it's like 140k on the MIUI ones) for some reason, but it's an issue on all of them.

gavin19 said:
Did you ever get any further with this? My phone idles at ~35C. I read a review that said throttling begins at ~40C so I get throttled when I do virtually anything.
I've only had this thing 2 days and the performance has been worse than my old Nexus 6 because the cores keep getting capped very low. I was copying some backed up files over WiFi from my PC. It was lots of small files so it was running for 20 mins or so. When I was trying to do other stuff in the meantime it started to get really sluggish. I used to do exactly the same thing on my N6 and I could never tell that file copying was running in the background. I checked Kernel Auditor and it was showing temps ~50C and the cores were all being capped around 5-600MHz.
I've tried the stock ROM (stable and beta) and EPIC, and Lineage/RR. It seems to be a bit worse on the latter two (Antutu won't go above 100k, but it's like 140k on the MIUI ones) for some reason, but it's an issue on all of them.
Click to expand...
Click to collapse
I have absolutely gotten further here I have managed to get throttling completely disabled actually.
The highest temp the CPU got to was 42 degrees Celsius after running Dolphin for 2 hours straight.
There is no need for thermal throttling on this device at all, hardware does a good enough job clearing the heat.
To stop the thermal throttling you need root access.
Use ES File Explorer from the play store and enable root access
Navigate to root and look for Folder system/etc and find file called thermal*******.*** ( I don't remember what it's called )
Cut this file from this location and paste it into another directory. I moved it to the sdcard for easy access. This way you can move it back if you do not like the results.
I have not experienced any overheating with this, also the battery doesn't drain like crazy. Performance is greatly improved with speed matching the Snapdragon 835 in a few scenarios.
Oh yeah restart the phone after you move the file so it can register the changes. Clock the cores appropriately with Kernal Auditor to make sure it can run at full blast when it needs to. On demand is way faster than interactive.

Cheers. I actually read the links you posted and renamed the conf file. After a reboot it was flying. The problem isn't so much the throttling, it's that mine idles at ~35C already, so it was getting capped when I did virtually anything. If I run Antutu 2-3 times in a row and check the temps in Kernel Auditor it can be in the low 60s. Using other temp apps (CPUTemp) it only shows about 45C tops.
It definitely does feel pretty damn warm since I don't use a case. but I'd love to know what the 'real' temp was. I tend to believe the lower one since I got the 45C warning when using EPIC and that's exactly what the app said. it was.
My Antutu scores increased substantially too. I was sometimes dipping down to 80-90k but I regularly get ~140k now, even 160k once. I know not to go by those scores but when I could never even get above 100k it was a concern.

gavin19 said:
Cheers. I actually read the links you posted and renamed the conf file. After a reboot it was flying. The problem isn't so much the throttling, it's that mine idles at ~35C already, so it was getting capped when I did virtually anything. If I run Antutu 2-3 times in a row and check the temps in Kernel Auditor it can be in the low 60s. Using other temp apps (CPUTemp) it only shows about 45C tops.
It definitely does feel pretty damn warm since I don't use a case. but I'd love to know what the 'real' temp was. I tend to believe the lower one since I got the 45C warning when using EPIC and that's exactly what the app said. it was.
My Antutu scores increased substantially too. I was sometimes dipping down to 80-90k but I regularly get ~140k now, even 160k once. I know not to go by those scores but when I could never even get above 100k it was a concern.
Click to expand...
Click to collapse
Yeah I'm thinking Xiaomi severely limits the thermal threshold to improve battery performance.
It's kinda all they care about in Japan for some reason.
Makes for some great performance improvements without the thermal settings being active.
This setting change is almost necessary of you need some heavy work done.
Glad you were able to get this changed.

i remove thermal_8896_blabla.conf...
Honestly device become too hot for me.... backplate change during my game (Battle Bay), very different sensation... reinstall immediatly *.conf... Finally i have decent perf and cold phone and very good battery life... no more...
My opinion !

lesscro said:
i remove thermal_8896_blabla.conf...
Honestly device become too hot for me.... backplate change during my game (Battle Bay), very different sensation... reinstall immediatly *.conf... Finally i have decent perf and cold phone and very good battery life... no more...
My opinion !
Click to expand...
Click to collapse
I think our best solution would be a modified .conf file that increases the thermal threshold as opposed to completely removing it.
Until this solution is available then this is our only choice.

i agree... i think with a ROM kitchen mayve this fil can be readable... anyway @ this point, we can only hope somebody dectypt this file to support various cool modification available over XDA...
Edit /
it seems HTC make same stuff... here it is a guideline ot example...
https://forum.xda-developers.com/showthread.php?t=2455596

lesscro said:
i remove thermal_8896_blabla.conf...
Honestly device become too hot for me.... backplate change during my game (Battle Bay), very different sensation... reinstall immediatly *.conf... Finally i have decent perf and cold phone and very good battery life... no more...
My opinion !
Click to expand...
Click to collapse
I had the same issue. I was getting 165k+ in Antutu but the phone would get uncomfortably warm when doing multiple passes, or gaming for extended periods.
In the Thermal section of Kernel Auditor, I enabled the Core Control and Temperature Throttle options and the phone still gets warm, but only as warm as you'd expect. I still get ~155k in Antutu consistently and the performance in general is still very smooth. I have the CPU governor set to ondemand, and the GPU governor to simple_ondemand. All other KA settings are default.
One other thing I always do is to reduce the Window Animation, Transition Animation and Animator duration scales to .5x (1x by default). It just makes the phone feel snappier in general. Settings > Additional settings > Developer options (MIUI-based).
I'm using the latest EPIC ROM. Using RR/LOS I couldn't replicate the same high Antutu scores consistently for some reason. I quite like MIUI after years of using CM and CM-like ROMS anyway.

already reduce animation x0.5... MIUI use a lot of this animation with complex and (very long calcul) then reduce this number make device seems much faster... anyway, u right...
A custom kernel for miui base... based on Dragon XIA exist in MI5 thread... only need to play a bit to make universal... with all source we can make somthing, but no have time to play with all tutorial available on XDA or Youtube...
Only way to make device much smoother and battery friendly or Perf/Warm destructor...