Database Info

Overclocking, kernel and governors

Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.

OC 806 can damage your phone for ever manage carefully this
Sent from my LG-P500 using Tapatalk

And what are the safest levels? And best governors? Im actually using smartass min 480 max 729

Overclocking will not "damage your phone for ever." Some of the P500s are stable at higher clock speeds than others, which is typical of mobile CPUs (even the two cores of my Sensation's CPU are stable at different maximum clock speeds). IIRC, my Optimus T was only stable up to 729 MHz. If you try to overclock higher than your phone is capable of, then it will freeze or reboot. There really isn't a "safest" level; any clock speed that your phone is stable at is going to be perfectly safe. Run a stability test or benchmark app from the Play store to check stability. IIRC, another easy way to test stability on the P500 is to open a camera app. The camera tends to crash the phone when the CPU is clocked too high. If you manage to crash the phone by doing any of that, then I recommend dropping down to a lower clock speed. Otherwise, the phone is fine and you can test a higher clock speed. FWIW, I'm pretty sure that most P500s are stable up to 729 MHz, but many of them are not stable higher than that.
I personally like to use Interactive governor. I think I used Interactive with min 480 and max 729 on my Optimus T. Governors Explained

chalo99 said:
Hi, I have some questions with kernels, overcloak and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
1. I use smartass as governor (well on the jenkins build). It has a balanced battery and performance I think.
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
3. Well overclocking on android depends on the ability of the kernel to handle overclocking situations. Some kernel can handle overclocking very well that the noticable errors are up to a minimum level. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
5. Before, we use to have different kernel developers and different rom developers. as the the passed by and newer devices are being developed, some migrated to newer devices and abandoned the development for our beloved phone. Now I think only 1 developer is still developing (original development not just cuztomizing and stuffs it with design) androidmeda (check "jenkins armv6") and the kernel included in the rom is sufficient enough to handle overclocking (used it and set the freq to 320 - 710 at smartass). I also use sweetnsour's kernel before but i think he too abandoned the development)
5. k

engr_exxi said:
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
Click to expand...
Click to collapse
That isn't true. Processor manufacturing is inexact, so some processors end up with higher clock speed capability than others. As the maker of a device, you have to set the clock speed low enough that ALL of the processors in ALL of the devices function properly. Setting the clock speed conservatively means that most or all of the devices are actually capable of functioning at a higher clock speed, which in most cases -- and certainly in the case of the P500 -- is completely safe. And it is extremely naive of you to believe that every processor or computer you buy is running at the "best and safest" speed as tested by the manufacturer. CPUs are often significantly underclocked simply to allow manufacturers to differentiate pricing. The same thing is done with finished products, including smartphones. For example, my HTC Sensation has a Qualcomm MSM8260 clocked (originally) at 1200 MHz. The HTC Sensation XE has the exact same processor clocked at 1500 MHz.
3. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
Click to expand...
Click to collapse
Again, it is nonsense to say that overclocking this phone "is not really safe." You won't find one example anywhere of a person who has damaged this phone by overclocking it. These things don't get hot enough at any clock speed to damage the hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
Click to expand...
Click to collapse
4.a. Heat is probably the only legitimate concern with overclocking a smartphone, and that's exactly why there is no risk with the P500 -- it doesn't get anywhere near hot enough, at any clock speed, to cause any damage.
4.b. This shouldn't be a problem. If your phone is not setting clock speed on boot, then a crash/reboot will send your phone back to the original clock speed. Even if you make a mistake and change a clock speed that is being set on boot (which I actually did by accident just yesterday), you can boot directly into recovery and restore a backup.
4.c. Who cares? As I said before, if your system is unstable as a result of overclocking, then you should lower the clock speed. That isn't a problem.
4.d. *sigh*
But to each his own. If you don't want to go "yolo" with your antiquated $50 smartphone, then by all means, keep it at 600 MHz. Nevertheless, there is absolutely no way that you would damage it by overclocking, regardless of what you may believe.

Well, its overclocking and not overcloaking.
Small error, but make changes in the OP

rhar**** said:
Well, its overclocking and not overcloaking.
Small error, but make changes in the OP
Click to expand...
Click to collapse
I wrote it bad in the title, but in the middle of the post it was OK. Thanks anyway, ****ing spanish that you read it like you write it, or viceversa.

chalo99 said:
Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
The phone won't work above 729MHz. And the only risk i can thinknof is depleting battery life faster.

Im actually using interactive min 480 max 806.
That permit no lag and normal reactivity.
Obviously there is a battery drain than normal.
I've also use a seeder application.

[Q] Why my phone crashes after 1.3 ghz?

Hi
I have try many kernels(and ROMS) and my phone keep to be unstable-crash after oc over 1.3 ghz.
Do you know why?
Thank in avdance!

maybe beacuse is too much you cant do it just like that.you can oc max to 1.15-1.25 for a daily use

i managed to get my phone stable 24/7 @ 1.3ghz with a decent kernel (i think i'm currently using signed_shazo's_kernel but not sure anymore) and voltage control to set clock and a bit more voltage on the cpu @ 1.3ghz... your battery will suffer and phone gets hot with heavy usage but the performance gains are substantial)
hope this helps

Killing the whole LITTLE cluster, using just the two cores in big cluster

Can anybody tell me how to do it? I think most of the heat (implies battery drain) and downgrading performance comes from the 4 A53 cores in LITTLE cluster, so I want to shuts all of them (if possible) and use only the two big cores.

Yes with resurrection rom and the custom kernel.

It is the A57 cores that overheat. I am not sure adding that much load is a good idea.

From my experience, CM13 from ketut has better CPU task management and seems to lower temps and battery consumption on normal usage. Of course playing games will also heat the device but it in opinion provides better sustained performance.

OK, so it's not so possible with official ROM, eh? I can't make any core offline (it goes back online too fast that setting 444 permission afterwards with && is too late ) even though perfd has been stopped. I wonder who really controls the cores...

leledumbo said:
OK, so it's not so possible with official ROM, eh? I can't make any core offline (it goes back online too fast that setting 444 permission afterwards with && is too late ) even though perfd has been stopped. I wonder who really controls the cores...
Click to expand...
Click to collapse
official ROM kernel uses core_ctl hotplug, how to configure read here
http://forum.xda-developers.com/xperia-z5/general/root-required-performance-battery-t3376233

int0x19 said:
official ROM kernel uses core_ctl hotplug, how to configure read here
http://forum.xda-developers.com/xperia-z5/general/root-required-performance-battery-t3376233
Click to expand...
Click to collapse
Aaa... so those are the culprits... nice info

[Thermal engine] Overheating problems ?

Hi guys,
I'm not sure if the LG Flex 2 uses thermal-engine.conf to set its thermal values, throttling, etc.
or if it's set in the Kernel source.
But if the 1st is the case @androidexpert35 's currently developed thermal "engine" might be the solution:
[MOD][6.0+][ v1.7 ][THERMAL-TWEAK] SmarTemperatureX | The best balanced S810 Ever!
some settings might need adaptation for the Flex 2 but I'm sure,
after some careful tinkering the device should be able to stay cooler, sustain performance over longer time and might also offer higher performance than stock (even under Marshmallow).
Good luck

Yes our device uses thermal_engine_8994 but how can we flash it on MM without root?

Correct me if im wrong but this looks like simple init.d script so it could be easily run for example with http://forum.xda-developers.com/g-flex2/development/init-d-script-init-d-support-g-flex-2-t3399145
Obviously it need some editing because it's for different device.

But we still need root on marshmallow to run scripts unfortunately.For lollipop we already have tweaked thermal config file but on MM,while tge ui is super smooth,gaming performance is horrible because of throttling.

Pungasul said:
Yes our device uses thermal_engine_8994 but how can we flash it on MM without root?
Click to expand...
Click to collapse
you need root, otherwise you cannot do these kind of modifications
k3lcior said:
Correct me if im wrong but this looks like simple init.d script so it could be easily run for example with http://forum.xda-developers.com/g-flex2/development/init-d-script-init-d-support-g-flex-2-t3399145
Obviously it need some editing because it's for different device.
Click to expand...
Click to collapse
Pungasul said:
But we still need root on marshmallow to run scripts unfortunately.For lollipop we already have tweaked thermal config file but on MM,while tge ui is super smooth,gaming performance is horrible because of throttling.
Click to expand...
Click to collapse
That's not really a init script,
it's a modification file, system config,
so someone who knows internals should ideally grab it via
e.g.
adb pull
and inspect if there are any similarities that can be merged and then re-uploaded,
NEVER at all times run WITHOUT the thermal configuration,
otherwise the device might overheat or get damaged (there are some safety measures in the chip, etc. but still)

zacharias.maladroit said:
Hi guys,
I'm not sure if the LG Flex 2 uses thermal-engine.conf to set its thermal values, throttling, etc.
or if it's set in the Kernel source.
But if the 1st is the case @androidexpert35 's currently developed thermal "engine" might be the solution:
[MOD][6.0+][ v1.7 ][THERMAL-TWEAK] SmarTemperatureX | The best balanced S810 Ever!
some settings might need adaptation for the Flex 2 but I'm sure,
after some careful tinkering the device should be able to stay cooler, sustain performance over longer time and might also offer higher performance than stock (even under Marshmallow).
Good luck
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-flex2/general/thermal-throttling-hotplug-settings-t3106165
This was already implemented almost a year ago..
It is really the limit to configuring the file..
The thermal config here sets throttling to higher values so reduces lag overall..but unlike anyother sd810 phones ..g flex 2 gets hot really really quickly..
So for gamming with the config in the mentioned thread gets the device to heat up upto 50-55 C overall..(core heating can get up to 70-80 C)
Only option is to customize the kernel but sadly no bootloader unlock for more than a year...

adds08 said:
http://forum.xda-developers.com/g-flex2/general/thermal-throttling-hotplug-settings-t3106165
This was already implemented almost a year ago..
It is really the limit to configuring the file..
The thermal config here sets throttling to higher values so reduces lag overall..but unlike anyother sd810 phones ..g flex 2 gets hot really really quickly..
So for gamming with the config in the mentioned thread gets the device to heat up upto 50-55 C overall..(core heating can get up to 70-80 C)
Only option is to customize the kernel but sadly no bootloader unlock for more than a year...
Click to expand...
Click to collapse
If it already lags at default settings, something's really off (ROM or Kernel would need optimization)
actually the best with this hothead of a SoC would be to make it throttle earlier (http://forum.xda-developers.com/z5-compact/general/mod-t3250283)
and then there's also core_ctl (CORE_CTL_HELPER) which can be set up via e.g. Kernel Adiutor or Kernel Adiutor Mod,
but that's probably nothing new to you and the others in the mentioned thread
Thanks

[KERNEL][MIDO][OC][3.5GHZ CPU] XXX-KERNEL ULTIMATE GAMING KERNEL 2GHZ GPU

BEST GAMING KERNEL FOR MIDO
CPU OVERCLOCKED TO 3.5GHZ AND GPU TO 2GHZ FOR BEST GAMING PERFORMANCE
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY THIS KERNEL
Based on Wolf Kernel
Features
3.5ghz CPU
2ghz GPU
PUBG OPTIMIZATION ENGINE IN KERNEL
All features from Wolf Kernel
Kernel may throttle in hot climate so recommended that you also delete thermal-engine
Download: https://drive.google.com/file/d/1qFAkWOTk207kI8uFGzK9FHjZzjSAA6dA/view
XDA:DevDB Information
XXX-KERNEL, Kernel for the Xiaomi Redmi Note 4
Contributors
Curi0, emabertax, alek dev
Source Code: https://github.com/xCuri0/XXX-KERNEL/
Kernel Special Features:
Version Information
Status: Testing
Created 2019-07-01
Last Updated 2019-07-01

My mido won't boot up
Hi. Thanks For Do this Project. I Like To Use OC kernel. But i use this kernel on my device MIDO. and then bootloop. I hope you Will fix this kernel soon. Thanks
Sorry my bad english

"Kernel may throttle in hot climate so recommended that you also delete thermal-engine"
How delete this?

I am currently digging through some old threads and seeing this kernel just makes me a little bit sad In case you are wondering (no offense to the creator) this kernel is a soc killer. At what voltages you achieved this clock? It could be quite fun when making some extensions, connecting motherboard to a pc cpu cooler and then flashing this kernel. Removing thermal engine will make the cpu go >100C and for longer periods of time it'll degrade not only the cpu but also the ram (soldered on the cpu). Don't flash this unless you want to throw the phone out anyway.

Verity. said:
I am currently digging through some old threads and seeing this kernel just makes me a little bit sad In case you are wondering (no offense to the creator) this kernel is a soc killer. At what voltages you achieved this clock? It could be quite fun when making some extensions, connecting motherboard to a pc cpu cooler and then flashing this kernel. Removing thermal engine will make the cpu go >100C and for longer periods of time it'll degrade not only the cpu but also the ram (soldered on the cpu). Don't flash this unless you want to throw the phone out anyway.
Click to expand...
Click to collapse
Don't worry the numbers are fake, it works at 2.2ghz for cpu.You can't achieve these numbers even with liquid nitrogen.