Related
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.
.
..
I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk
Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?
..
MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk
..
MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk
When I bought Xperia T, after a while, I started to be a little disappointed with performance, autobrightness, discharging when playing, etc.
After some digging deeper into this problem, I have found, that cpu is throttled by temperature. And not only the cpu.
A few minutes of playing game, cpu goes to 800MHz, display brightness goes to level 100 (max. is 255), wall charger current is reduced (even when connected, it is discharging), radio power is reduced, etc.
Change it yourself:
Example:
xo_therm 14 -1000 380 20 NOTIFY CAM_NORMAL cpu_perflevel:1728000 charge_current_limit:0 usb_current_limit:1 modem_level0 lcd_brightnesslevel:240
xo_therm 14 = sensor step
-1000 = -100,0°C
380 = 38,0°C
20 = don't know (maybe some kind of sample rate?)
NOTIFY CAM_NORMAL = obvious (camera)
cpu_perflevel:1728000 = cpu frequency
charge_current_limit:0 = obvious (0 is 1300mA I think, 1 is 1100mA, 2 is 900mA, etc.)
usb_current_limit:1 = obvious (has impact on charging too)
modem_level0 = power of modem
lcd_brightnesslevel:240 = obvious (0 - 255)
Set the highest temperatures, with low enough frequencies and charging current values, to let phone cool down.
"gpu_perflevel" can be used too and there are some other thermal sensors in sysmon.cfg, which are also responsible for thermal throttling.
Disclaimer:
Each device is different and I am not responsible, if your device burns with some values from here.
Both CPU cores always on:
Echo 1 in /sys/devices/system/cpu/cpu1/online and change permissions to 444. And if you want to prevent errors from log (and maybe some unwanted wake locks), rename /system/bin/mpdecision to something else or delete it.
what is temp at what cpu throttles (and other things)?
seems it is lower than other devices, something like 40C, i think my sgs3s was at 76C or similar.. not sure, will check later.
sgs3 was a very hot phone.
Sent from my Xperia T
You can see the temperatures in sysmon.cfg - xo_therm 400 500 = 40 - 50°C for example. Cpu temperature, not battery. There is no tool to monitor cpu temperature, but if you set your own frequencies, you can see with Cool Tool, how long it takes to the lowest frequency.
peetr_ said:
You can see the temperatures in sysmon.cfg - xo_therm 400 500 = 40 - 50°C for example. Cpu temperature, not battery. There is no tool to monitor cpu temperature, but if you set your own frequencies, you can see with Cool Tool, how long it takes to the lowest frequency.
Click to expand...
Click to collapse
thanks, will check. i am on cm10 and didn't notice throttling yet, but i will check now as it is ****ty if so.
Sent from my Xperia T
I have noticed the throttling but it doesn't affect the performance in my case, playing games and watching HD video are fine, just annoying when the screen suddenly does dim.
Sent from my LT30p using xda premium
@OP:
If you don't want throttling, uninstall Androids inbuilt Thermal monitor(No need to tell you the risk by doing that I guess).
Thanks for you valuable advice.
Don't think it would help as that file says 2nd core off values are hardcoded
Sent from my LT30p using Tapatalk 2
I think, that it works, because I tested it and I am using my own values.
Good thing I won't be playing games when my T will arrive
https://developer.qualcomm.com/mobile-development/development-devices/trepn-profiler
Stay Informed
Trepn Profiler is currently being redesigned. Sign up to be notified when Trepn Profiler is reintroduced.
Click to expand...
Click to collapse
Still? Damn how long do they take ? -.-
Here is the .apk of the old version. No idea how much works and what doesn't!
Hello,
Could it be some kind of default on your device ? or maybe the application ?
Cause I remember Qualcomm's communicating on their S4 being "cooler" than its opponents when under heavy load.
Can someone else confirm ?
What's strange is that the game you mention (Osmos HD, which I bought some time ago for my TF101) does not even use super high end 3D graphics etc etc ... maybe the perf drop could come much quicker with some cpu/gpu intensive apps.
If confirmed, it might even become a big "no go" on this phone for me.
Nickola
nickola said:
Hello,
Could it be some kind of default on your device ? or maybe the application ?
Cause I remember Qualcomm's communicating on their S4 being "cooler" than its opponents when under heavy load.
Can someone else confirm ?
What's strange is that the game you mention (Osmos HD, which I bought some time ago for my TF101) does not even use super high end 3D graphics etc etc ... maybe the perf drop could come much quicker with some cpu/gpu intensive apps.
If confirmed, it might even become a big "no go" on this phone for me.
Nickola
Click to expand...
Click to collapse
I've had this phone for a while now and I haven't had a bit of lag while playing any game I have. Everything seems fine except the sudden dimming of the screen when playing games. Don't let this put you off buying the phone, its a great phone
Edit: been playing Osmos HD for at least 25 minutes, I'm experiencing no such lag or performance issue. Only the dimming issue I seem to get.
Well, after some more investigation, I have found, that lags in Osmos HD are not caused by cpu throttling, but wifi disconnecting.
Playing the game is fine, but still, with default settings the temperature is going high and except the screen dimming, cpu goes to 800MHz, (1 core disabled on highest temperature), and phone is discharging even when connected to wall charger.
It seems to me, that the overheating is not caused that much by cpu, but gpu. It would be nice, if it could be tested somehow by lowering the frequency of gpu.
I wonder if the heating issues could be fixed with software patches. Given Sony's desire to incorporate playstation stuff, I find it hard to believe there is some sort of hardware issue.
Wish we could get some more samples to work with.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Just measured with my settings (in the room - about 23°C):
10 minutes of playing Osmos HD without charging = 62°C CPU temp
With one core running on 1350 MHz and LCD brightness value 150, it's not increasing anymore.
When charging, the temperature will go higher. I will test it too.
peetr_ said:
Just measured with my settings (in the room - about 23°C):
10 minutes of playing Osmos HD without charging = 62°C CPU temp
With one core running on 1350 MHz and LCD brightness value 150, it's not increasing anymore.
When charging, the temperature will go higher. I will test it too.
Click to expand...
Click to collapse
Have you tried treppn profiler?
Anandtech says a CPU core draws around 450-750mW while gpu goes 800-1200mW!
Seems like 400mhz is a hard Task for an 225.
If you are still on ics maybe try jellybean? Perhaps project butter may more efficiently handle the gpu.
Maybe even make a list of "stress test" for people to try and see what the various results are.
If all else fails try undervolting the gpu and cpu.
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Haldi4803 said:
Have you tried treppn profiler?
Anandtech says a CPU core draws around 450-750mW while gpu goes 800-1200mW!
Seems like 400mhz is a hard Task for an 225.
Click to expand...
Click to collapse
Yes, I tried trpn profiler provided by you, but there are limited options.
It looks like the GPU cannot handle this frequency.
Undervolting won't help anything, but lowering GPU frequency would help I guess. But this cannot be done without custom kernel, allowing this.
LegibleEel said:
I've had this phone for a while now and I haven't had a bit of lag while playing any game I have. Everything seems fine except the sudden dimming of the screen when playing games. Don't let this put you off buying the phone, its a great phone
Edit: been playing Osmos HD for at least 25 minutes, I'm experiencing no such lag or performance issue. Only the dimming issue I seem to get.
Click to expand...
Click to collapse
Same here. I've been playing Speedball 2 and GTA3 mainly but I have played a few others too and haven't experienced any lag and no performance issues observed at all.
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 ..
Is there anything I can do on a new galaxy note 4 to prevent the emmc issue happening in the first place?
There was some talk about preventing overheating?
ghostwheel said:
There was some talk about preventing overheating?
Click to expand...
Click to collapse
Do I need to lower the cpu ghz? Or run some kind of app or program?
Redrainz said:
Do I need to lower the cpu ghz? Or run some kind of app or program?
Click to expand...
Click to collapse
It might help to lower the CPU speed, but you need access to root and an app to tweak the values.
Avoid gaming which is very demanding on GPU and avoid gaming for long periods of time.
Search also in the Snapdragon forum a good kernel.
Also turn off the fast charging, this can heat too much the phone.
I created a script here. It works very good, it monitors the battery temperature AND all the CPU cores temperatures, and will automatically throttle the phone if temps are too high. You can even kill some apps if the temps are to high (not yet implemented).
The difference with Samsung DVFS or integrated temperature management of kernels is that this one monitors almost all CPU sensors and also the battery, all in complete combination, and it can be easily tweaked (rather than modding a kernel). No battery hog. You can enable USB fast charge, game, etc it will still prevent overheating.
Here is the solution to eMMC error
Hello everyone, I was pretty tired of the eMMC error, and I created a script that completely annihilate this error. This error is due to the phone heating up, and the fact that custom kernels (maybe even the original kernel) don't read the...
forum.xda-developers.com