Develop Bugs

overclocking dhd

I have recently rooted my dhd and currently running CM7. Using the cpu setting within the performance menu I am wondering what peoples thoughts are on a noticeable but safe increase of cpu speed. its set as 1017MHz which i believe is default. I am told I can run anything up to 1500 safely. can anyone confirm this and also tell me what kind of result (performance and battery life) i should expect.
thanks

Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz

hmohammed43 said:
Well, I use Android Revolution HD (a sense rom, meaning heavy UI!) and i overclock to about 1.3GHz. In terms of battery life when it's awake, it seems a drain a teeny bit more readily, but I've never had a freeze on sense (quite rare)
On stock it underclocks to let the processor max at around 400MHz when the screens off, so that helps to really save a lot of battery on standby. On CM, I'd expect it'd feel more or less the same in terms of performance after you hit 1.2/1.3GHz
Click to expand...
Click to collapse
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers

rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers

darude0306 said:
The CPU is managed by the ROM itself. You can tweak it yourself by using setCPU (or similar), but I can advise you not to. Can't help you with the governors buddy, since I dunno what it is
Cheers
Click to expand...
Click to collapse
nice one dude

I'm running cm7 and I'm overclocked to 1.5 ghz. It's been totally fine for months.
Sent from my Motorola Startac running Atari 2600 software!

rhodri11 said:
thanks for the reply mate. going to try out revolution HD soon i think. have you overclocked using a third party app or is there one built into that rom?
also im a little confused by the governors. 'on demand' is the default governor. Does that mean it will only use the max selected cpu speed when necessary? would you recommend using a difference setting?
cheers
Click to expand...
Click to collapse
Lucky you picked a linuxhead!
The system itself has a daemon (background process built into the system) that handles overclocking. It's all explained on the page and also on this thread:
http://forum.xda-developers.com/showpost.php?p=14638641&postcount=34279
You can use another app (like SetCPU) but the daemon usually handles screen off's quicker. The governors basically determine how the processor frequency is changed. I'll explain the common ones:
Performance - Runs at highest speed, so if you have a range of 200 to 1.3G, it'll stay at 1.3G all the time, not usually the best
Ondemand - The universal default for phone overclocking, it only changes the speed up after a certain percentage of the CPU is used, and it switches on the fly, so if the CPU is used too much at 400MHz, it'll ramp it up to maybe 600 or 800, and if it's still overused, it'll put it up to maybe 1 or 1.2G
Conservative - This is like ondemand, except it makes the changes more gradual. It can give noticable lags in the foreground at times, so this is mainly used when the phone is asleep (screen off)
Smartass - This governor is like ondemand, except it'll less readily switch frequencies to higher values when it detects the screen off. This isn't really used because the overclocking daemons take into account the phone being awake or not
Basically, there isn't really a need to change governors, only really frequencies if anything. The thread, however, does tell you how to change governors.

Im using latest LeeDroid GB 3.2.1 and to be honest with the work he's done with the Kernal (3.1.8BFS) I have found that the ROM is a lot MORE responsive without me overclocking the CPU.
Im not really sure how it all works, but I guess doing this on different ROMS has its own different out comes.

overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?

toby_lerone said:
overclocking has me confused too, is there really that much of a benefit in it? how much will i gain from it?
Click to expand...
Click to collapse
There is a benefit when you use certain apps, or even sense itself. For example, I've never had sense ui freeze, or go slow. The under clocking helps to improve the rubbish battery life when your phone is asleep.
In terms of measuring the gain, I have no idea. Really, I'd think you could use a process heavy app, or benchmarking app and see.
There's also loads of guides on overclocking to help out! (that's how I got the hang of it! )
Sent from my Desire HD using XDA Premium App

For the need on OC, it depends on the kind of apps u're using. If u're happy w a non OC DHD, its totally up to u.
But for the UC, it works as a terrific battery saver, mich better/effective than other battery saver soln on market

The safe range depends on the DHD as the manufacturing changed even though same part, i'm OC 1.5GHz "On Demand" profile and under clock 245MHz on screen off "Power Save" profile.
Getting approx a day usage on Lee 2.1.

(Q)I have a og evo and cant overclock it 1.2ghz.

I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium

Each Evo is different. Some of them can't handle that high overclock, or can't be undervolted very low. Each one is different, each has its limits.
I don't understand the big deal with overclocking. It burns your battery faster. I personally underclock, with little to no lag and is good enough for my casual gaming needs

Mine doesn't like a clock much at all. I can get about 1.1 before it starts locking up but even then it hangs a lot. I honestly don't see a difference from 1.0 to 1.2. Get a decent rom, good kernel and try out the v6 script an I almost guarantee you will like that better.

beaumontcali48 said:
I have a og evo I want to know why when I overclock to 1.2ghz it freezes my phone why does it do that ?
Sent from my Nocturnal 4G using xda premium
Click to expand...
Click to collapse
Well for us to be able to help you, you would need to provide us with more details on how you are trying to accomplish this.

I use no frils cpu but have also tried setcpu and viperMOD I know that's the best way to overclock but is very confusing. Have any step by step instructions to of to 1.2 I know having higher voltages helps as well.
Sent from my Nocturnal 4G using xda premium
Sent from my Nocturnal 4G using xda premium

Overclocking is overrated. If you need to overclock for every day usage, then something is wrong - at least in my opinion. Resource intensive gaming is different, but you shouldn't need to overclock for browsing, texting, casual games, etc.
Try out the V6 Supercharger script. I'm not currently using it, but have in the past and it seemed to make my phone more snappy. A lot of people swear by it and it's a great script, definitely worth a shot. There are other things you can do to speed up your phone without overclocking. I'd try other options first since overclocking will chew through your battery. Increase the dalvik vm heap size, there are plenty of free apps on the market to help with this task. Uninstall apps you don't use, I'll bet that you never use some of the apps on your phone. Back them up with Titanium Backup and you can restore them if you ever need them again.
In case you didn't already know, the Evo can't overclock past 1.2, I'm not 100% sure why - it has something to do with the processor.
Supersonic Evo 4G | MIUI | Tapatalk

I never oc over 1075 and only when plugged in if i play a game I need to oc.for I just activate my charging profile and plug up and play 1.2 ghz is a good chance of doing serious.damage as these older scorpion processors get very very hot at that clock speed so they lock up to try and protect themselves from heat damage or they shut down the phone 1075 is as high as you should need to go for any games the evo can handle on the subpar gpu
Sent from my Classic-EViLizED-ToMAToFiED-EVo4g-

beaumontcali48 said:
...also tried setcpu and viperMOD I know that's the best way to overclock.
..
Click to expand...
Click to collapse
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!

shift
Get a shift. Mine runs fine at 1.9. But usually run it art 254-1200 on demand.

{ParanoiA} said:
I'm pretty sure viperMOD is more for undervolting than overclocking, which are not suppose to be combined together. I am running vipermod with max voltages - 50. Other nite was playing snes9x and was getting some lag with a game so I bumped max CPU up to 1.2. Phone went into a bootloop and had to superwipe and reflash everything. Don't know if its b/c vipermod + 1.2 CPU or just bumping up CPU. Didn't try it again.
Support TrevE!!
Click to expand...
Click to collapse
You can overclock and undervolt together just fine. You just need to ensure that every frequency has a high enough voltage to run the processor at that step. My Evo is overclocked and undervolted just fine, although IIRC I can only push it up to 1.1 GHz . My tablet is 1ghz to 1.6ghz and is undervolted as well, though.

merge rls 2.0, iron monkey, Droid overclock because of the profiles options. I set up four profiles including one for temp. sometimes i'm underclocking and sometimes overclocking but only up to 1.19 to prevent freeze and boot loops. Only downside is right at open Droid overclock needs su permission but that is my choice since profile changes at open.
Very snappy afterwards.
Sent from my PC36100 using XDA Premium App

When I had the 4G, I was never able to go above 1118, or somewhere around that. It would have freezing issues.
On my evo shift, I was able to do 1.7 gHz (compared to stock 800 mhz) ok. 1.6 pretty reliabily, and I could run 1.5 all day long. Some guys could do 1.9. It just depends on the phone.

Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium

tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Shoot the brutha a link
TrevE Supporter!

tommy0823 said:
Actually overclocking and undervolting is counter-productive. What you should do, is read carhaulers and ropodopes guide over at vaelepak. Its give some good useful info about how to set up a good aosp rom. I'm underclocked, undervolted, and still getting 1400+ benchmarks. Check it out bro. You'll love the results.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101

Yea shot me the link too bro.
Sent from my PC36100 using xda premium

First let me say I don't use viper mod or any voltage controlling mod.
On sense 3.0 roms such as mikg I over clock to 1152 and set the minimum to 384 and its smooth as butter. No problem and battery lasts all day.
On aosp however such as decks (I'm on it now) I underclock to 499 and leave the min at 254. Smooth as always and battery lasts forever.
Anything past 1152 is going to cause problems (at least in my experience) also the rom/kernel can effect how much you can overclock.
Sent from my PC36100 using xda premium

Gary13579 said:
What? Overclocking and undervolting are two completely different things, and they aren't mutually exclusive. Unless you can provide a good reason as to why it's counter productive to do both, I don't buy that at all. Just checked my phone, my overclock requires an extra 25 mV for all three steps I've overclocked. 25mV isnt much, and it certainly isn't going to kill my battery that much faster.
Besides, the only time the CPU is going to be entering these high power modes is when it needs to do work, and it's better to do work as fast as possible to go back to sleep. Would you rather wake up, do a mundane task for 5 minutes, then go back to sleep or wake up, do a task at 2x the speed while only consuming 30-50% more energy, then going back to sleep after only 2.5 minutes?
HUGI is real.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Its counter productive because it is giving less to something that needs more. (Don't take this post as me trying to be a ****. Just voicing how someone explained it to me a while ago)
Think of this as cars.
Lets say you have a nice fancy v8 mustang. Stock, everything is well, balanced.
If you start adding parts and get it pushing out 1000 horsepower (overclock) your most likely gonna need more feul (voltage) or at least stock amount flowing into the engine just to keep it running.
Now lets say you got that same 1000 horsepower gas destroying mustang and you start to lower the amount of gas flowing into the engine (undervolt (done in vipermod)) cylinders (CPU) wont get enough gas, it wont work, and your stuck going no where.
So if that made sense (did to me) then you can see why they are counter productive. Unless your using vipermod to overvolt (which idk if you can since I don't use it) then you can disregard this whole post
Sent from my PC36100 using xda premium

Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101

Gary13579 said:
Your car analogy is completely irrelevant. You can look up the exact voltages that the CPU runs on at every frequency, *even when overclocking*. Overclocking an Evo 1ghz to 1.2ghz takes maybe a 5% bump in voltage, and that 5% extra power is only going to be used *when the CPU is running at max speed* (which is only when there is a lot of work to do), and even then, it's *still better to let the CPU run at max speed with a tiny bit more power consumption than to cap the CPU at a slower speed and make it work for even longer*. Intel calls it HUGI, Hurry Up and Get Idle.
I know what I'm talking about, and I wish people would stop trying to argue with me based off of second hand speculation. I do this for a living, after all. There is absolutely nothing wrong with overclocking and undervolting, and it's the best way to get the most battery life *and* performance out of your phone, period.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Hmm, *interesting*. I believe the best answer to the OP was covered rather well earlier. It's all about your rom/kernel/hardware combination. With all the variables to consider as relevant, your best bet is to experiment and find what works for your device. Don't check set on boot untill you are confident the set-up is stable. Higher is not always better with overclocking. My device runs blazingly well underclocked @768max. Gets insanely great battery @499max. However my quadrants are better @ 1036 than at 1190.
Great thing about android is you can experiment and learn through trial and error.
Sent from my PC36100 using xda premium

ROM Benchmark Scores

I got bored tonight and tested a few of the popular and recent ROM's for this phone. Below is the method of testing and the results.
I took these steps for -every- ROM tested.
Plugged phone in via USB to my computer and left it plugged in.
Factory reset using clockwork
format /system as well (i've seen a few rom's suggest this)
Installed ROM
Booted into ROM and let sit for 5 minutes without touching it
Stepped through the initial setup without setting up a google account (if applicable to the ROM)
Reboot
Let sit for 1 min
Installed AnTuTu Benchmark v2.6 from sdcard.
Ran AnTuTu Benchmark using default settings and selecting /sdcard/external_sd as the sdcard
This is NOT ment to imply one ROM is better than another. It's only intention is to share datapoints. Some of the ROM's are beta as well, so their final release may be different.
My intention is to show how ROMs perform based on the AnTuTu benchmark. I wish to use a ROM that is quick and efficient. Others may appreciate more eye-candy at the cost of performance. To each his own. So I hope some find this data useful.
Android Zombie v4.0 (7272)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Foxstar beta v1.0 (5689)
Revenge Of Macnut (5778)
Tuesday|Medieval|Midnight| (7136)
DARKSIDE:IGITAL::WARFARE v2.1 (5771)
Dewizzed-V2.5.2 (7045)
And just for kicks, here's my phone, running normally, fully loaded.
* Long time lurker, first time poster since I figured this may be a way to contribute to the forum.
* Also not here to promote any ROM. I'm unaffilliated.

Thanks!
Sent from my SGH-T989 using xda premium

Uh you know foxstar is the only one you ran at stock speeds? The rest are at 1700. Might want to re run that one.
Also you would have to run each test three to five times to get any sort of meaningful results bc the scores will fluctuate.
Sent from my SGH-T989 using XDA App

About the clock speeds, I did that on purpose. The purpose was to show the performance of the ROM as the creators intended.
Do you think running it multiple times will make a huge difference? I figured so long as I did the same steps for all ROMs it should reflect a decent standard.
Sent from my SGH-T989 using XDA App

matthewdavis said:
About the clock speeds, I did that on purpose. The purpose was to show the performance of the ROM as the creators intended.
Do you think running it multiple times will make a huge difference? I figured so long as I did the same steps for all ROMs it should reflect a decent standard.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
You did that on purpose? Interesting. You might want to put in bold the speeds you are running each test on. Seemed like a mistake if you ask me. All of those other roms do not come with default cpu max at 1700MHz.
Also, yes running them multiple times will make a HUGE difference. I have done it when bench marking graphics cards, cpu overclocks and with my phone. Try it....you will be very surprised.

G1ForFun said:
You did that on purpose? Interesting. You might want to put in bold the speeds you are running each test on. Seemed like a mistake if you ask me. All of those other roms do not come with default cpu max at 1700MHz.
Also, yes running them multiple times will make a HUGE difference. I have done it when bench marking graphics cards, cpu overclocks and with my phone. Try it....you will be very surprised.
Click to expand...
Click to collapse
Echoing this, Even if it's defaulted to a lower clock speed, you can't leave it that to provide an accurate data set. You also need a large spread, run hem 5 or 10 times and average them.
Even if benchmarks are a little silly in my book, still some interesting data.

G1ForFun said:
Uh you know foxstar is the only one you ran at stock speeds? The rest are at 1700. Might want to re run that one.
Also you would have to run each test three to five times to get any sort of meaningful results bc the scores will fluctuate.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Not true. Darkside Warfare was run at 1350.

IMO I think it's pointless unless you clock them at the same speed I mean you have digital warfare under clocked at 1.3 -_- might also want to mention which kernel each 1 is using and at the end of the day it's not about how each 1 scores but how it does in real life use I remember when I used the jugs kernel clocked at 1.89 I believe it scores over 8k easy but would lag on scrolling and other things but faux kernel would score a little over 7k and would run like butter clocked at 1.7. Now I'm using digital warfare with the kernel it comes with and I think it run incredible with speed, smoothness, and battery with good scores
Sent from my SGH-T989 using Tapatalk

mavblues said:
Not true. Darkside Warfare was run at 1350.
Click to expand...
Click to collapse
Mistake...
I was checking the screens from xda app. Your right.
Regardless...the roms should all be ran at one uniform speed for the best comparison.
Sent from my SGH-T989 using XDA App

avarize said:
Echoing this, Even if it's defaulted to a lower clock speed, you can't leave it that to provide an accurate data set. You also need a large spread, run hem 5 or 10 times and average them.
Even if benchmarks are a little silly in my book, still some interesting data.
Click to expand...
Click to collapse
This is true, however with an asterisk. Running them subsequently will 100% boost scores, mostly because of CPU stepping. Continually running them keeps them clocked at full speeds more often, especially in the beginning.
Also, same clocks please? Use setCPU or something to ensure it. Stock clocks would be appreciated.
Also, run Vellamo benchmark too please. Linpack too lol. And NOT quadrant.
That said, Darkside is the best performer here so far.

2hvy4grvty said:
Also, run Vellamo benchmark too please. Linpack too lol. And NOT quadrant.
Click to expand...
Click to collapse
Sorry, that's not going to happen. While I'm still debating how I feel about stock vs a standard clock speeds, I can tell you that I'm not willing to try different benchmarking tools. I feel AnTuTu is modern enough. And I agree with the quadrant comment.

Why not? What else tests browsing performance as thoroughly?
Can we at least agree that despite all the little games and gadgets this phone runs, almost everyone primarily uses the phone to browse the Internet? Antutu does none of that.

Not to defend myself or anything but...
a) for the 10000th time benchmarks are useless
b) benchmarks are useless
c) you ran them after different clock speeds.
d) benchmarks are better for Kernel tests, not rom tests.
e) Australia.

For clarity, the goal wasn't to try to get the highest score. It was to try to put all ROM's (and their included kernels) at the same baseline and see how they perform relative to one another. Not trying to put one over another.
Finding the right ROM can sometimes be a daunting task. Many offer roughly the same features, but just have different appearance. When people don't care about how the ROM looks (with all the different launchers and mods that can be changed after the fact), knowing how it performs out of the box may be the deciding factor.
I know clock speeds are different. Some ROMs opt for lower clock speeds to get better better life. So I thought it would be good to know how that effects its performance.
With that said, would this be useful? Would anyone appreciate seeing how one ROM performs relative to the others?

But what I don't get is you claim that the goal of the thread was to put all ROMs at the same baseline. That didn't happen. Just pointing that out.
matthewdavis said:
For clarity, the goal wasn't to try to get the highest score. It was to try to put all ROM's (and their included kernels) at the same baseline and see how they perform relative to one another. Not trying to put one over another.
Finding the right ROM can sometimes be a daunting task. Many offer roughly the same features, but just have different appearance. When people don't care about how the ROM looks (with all the different launchers and mods that can be changed after the fact), knowing how it performs out of the box may be the deciding factor.
I know clock speeds are different. Some ROMs opt for lower clock speeds to get better better life. So I thought it would be good to know how that effects its performance.
With that said, would this be useful? Would anyone appreciate seeing how one ROM performs relative to the others?
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App

I think he means baseline as in the performance you get from untouched roms as the dev intended them to be. This is probably more useful for people that are scared to mess around with overclocking apps..
G1ForFun said:
But what I don't get is you claim that the goal of the thread was to put all ROMs at the same baseline. That didn't happen. Just pointing that out.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse

mixedguy said:
I think he means baseline as in the performance you get from untouched roms as the dev intended them to be. This is probably more useful for people that are scared to mess around with overclocking apps..
Click to expand...
Click to collapse
That is correct. The baseline as defined by the authors of the ROMs. If a ROM author decides to underclock it out of the box, I'm not going to modify that.

[Q] Which Kernel to use Galaxy S3

I am running CM10 M2 on my Samsung Galaxy S3 I747
Now my question is which kernel do i use because i would like to OC my phone but it has to have some speed and keeps some battery life.
I don't want to have a lot of speed with hardly to no battery life, i need a little speed plus good battery life if possible.
So if anyone has any suggestions please post

Leandre20 said:
I am running CM10 M2 on my Samsung Galaxy S3 I747
Now my question is which kernel do i use because i would like to OC my phone but it has to have some speed and keeps some battery life.
I don't want to have a lot of speed with hardly to no battery life, i need a little speed plus good battery life if possible.
So if anyone has any suggestions please post
Click to expand...
Click to collapse
You can try all that work with CM10. It's a preference thing. I'm using ktoonsez. You can OC and UC.
Sent from my SAMSUNG-SGH-I747 using xda premium

Im not saying there aren't any others as i have only used ktoonez's kernel, http://forum.xda-developers.com/showthread.php?t=1756776 simply because there is, IMHO, no need to. He has versions for each of the available android versions for the i747...obviously you would want to use the AOSP JB based kernel under CM10. Packaged along with the kernel is ktweaker which is an app that gives you control over the clock speeds, under volting, governors, schedulers, plus a bunch of other options. If you overclock your processor you are going to drain the battery faster, you can compensate for this by under volting the frequencies however pushing the CPU too hard can shorten the life expectancy and under volting too far will cause severe system instability. Im not sure how much experience you have with OC/UV'ing but its basically trial and error until to find the right balance of speed and stability that is right for you.Just be sure to read and follow his instructions carefully and dont mess with anything in ktweaker you aren't 100% sure what it does, and as always make a backup in your recovery before messing with system files.....happy OC'ing.

dntesinfrno said:
Im not saying there aren't any others as i have only used ktoonez's kernel, http://forum.xda-developers.com/showthread.php?t=1756776 simply because there is, IMHO, no need to. He has versions for each of the available android versions for the i747...obviously you would want to use the AOSP JB based kernel under CM10. Packaged along with the kernel is ktweaker which is an app that gives you control over the clock speeds, under volting, governors, schedulers, plus a bunch of other options. If you overclock your processor you are going to drain the battery faster, you can compensate for this by under volting the frequencies however pushing the CPU too hard can shorten the life expectancy and under volting too far will cause severe system instability. Im not sure how much experience you have with OC/UV'ing but its basically trial and error until to find the right balance of speed and stability that is right for you.Just be sure to read and follow his instructions carefully and dont mess with anything in ktweaker you aren't 100% sure what it does, and as always make a backup in your recovery before messing with system files.....happy OC'ing.
Click to expand...
Click to collapse
I'm still learning since it's the first one I tried.
Sent from my SAMSUNG-SGH-I747 using xda premium

There is a thread dedicated to ktweaker settings on the i747 HERE that would be a good place to start and get an idea of what you are doing. There are also several topics that discuss the different governors and schedulers, what the differences are, advantages/disadvantages to each etc. You can also search google for a plethora of information regarding OC/UV'ing, although most of it will pertain to desktop processors and video cards. While the voltages and frequencies will be significantly lower the same principles apply with mobile device chips.

Ktoon's KT747 2/8/13 Kernel vs Task650's 2/10/13 Kernel

What are your guys' opinions on the performance of these two kernels? From what I've gathered it seems like KToon's kernel is meant for overclocking, but then what would one use task's for?
Task's recent update to his kernel makes me want to try it because I've been using KToon's kernel with the ktoonservative governer and row scheduler UV'ed a little bit but unlocked to 2.1GHz and have been having some pretty bad battery life in mu opinion, do you think switching to task's kernel would be better on the battery?
Well what do you guys think?

Fun Fact for the day. Versus threads get shut down in no time here on XDA.
P.S- Why wouldn't you just try it first before making a thread about it? Kernels take about 3 seconds to flash. Also. No one can tell you that you will get better battery life on one or the other considering all of the variables. We are all in different locations, use different apps, have different settings, and we all use our devices differently. You need to try them both out and see which one works better for YOUR device.

Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.

berryman13 said:
Man why are ya giving me a hard time? You kicked me out of your thread, which I understood and respect, but then you come here and tell me the same thing you told me before and that my thread's gonna go to the bin in no time.
I'm just trying to find out what the DIFFERENCES between the kernels are, because it isn't very clear in reading the descriptions/OP's,
They wouldn't co-exist if they were exactly the same.
I'm not too interested in tweaking the hell out of my device nor do I care too much about overclocking...I just want a lot of screen time and the ability to play games and SMS with little lag.
I have tried out both kernels and didn't really notice much difference because I didn't really know what to look for.
Like, okay or example, it seems to me that your kernel is less for tweaking and isn't for overclocking (max 1.6GHz or something?) while KToons can go to 2.1.
Click to expand...
Click to collapse
I'm not giving you are hard time. I'm just telling you the facts here. If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Which no one can tell you one is better than the other for. Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.

I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.

gilo123 said:
I think they re two of the same.Task just doesnt want KT to know he borrowed his kernel...lol jk. But seriously,they're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.

task650 said:
If you're not into tweaking and messing with things then this is simple and really shouldn't make a difference to you which one you use other than battery life, less lag, ect... Flash one and don't touch the settings for it and use it how you normally would for a day or two. Then do the same for the other kernel. See which one gets you the best results. Its the only way to find out. Not quite sure why you're refusing to take my advice here. Its pretty straight forward.
There's kernel source in both threads that explain in DETAIL all the DIFFERENCES between the two. It literally only takes seconds to flash and see for yourself. This shouldn't be a big deal at all.
Click to expand...
Click to collapse
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
gilo123 said:
Ithey're pretty similar.KT seems better on the performance end but I never got the exceptional battery stats that ppl keep posting,IdK it may be something on my end. On the other hand, task's seemed better on my battery as I could not noticeably see my battery drain during use as I did on Kt's. Furthermore my phone does get hot really fast on task kernel,I'm guessing its cuz we use performance control and can't really play in the voltages as much.
Click to expand...
Click to collapse
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.

berryman13 said:
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Click to expand...
Click to collapse
He cannot answer this question honestly. He doesn't have your device. You're not understanding. He can have the best battery life possible on my kernel but if you use it, you could have the worst battery life possible. IT'S DEVICE DEPENDENT. Will you please just do yourself a favor and take 3 seconds, flash the kernel, and see. You say you've tried them both, but you are also asking about playing games and what not with them? You would know if you had tried them dude. Same goes for the governors & schedulers. You would also know that if you had actually tried them both. I need to ask you this. Why won't you just try them and see for yourself. Are you really the type of person to flash what people tell you to your expensive device?
Look dude. I'm only trying to help you here. I'm not quite sure why you wouldn't just take my advice here. I have quite a bit of experience with this stuff and I'm trying to help you get the best experience possible. But it seems as though you think that personal opinions of others are whats best for your device when in all reality they are not. Real life testing is what will prove to be best for your device. Trust me.

berryman13 said:
I have flashed both kernels. And I don't mean that I am not planning on doing ANY tweaking whatsoever, I just don't mean like messing with voltages adding or subtracting 25 at a time until my CPU crashes so I can find the under/overclock limit...that's the kind of tweaking I have no interest in trying. I'm not gonna look through he sources of both kernels, come on dude you know I'm not a dev and that level of detail is un-necessary.
Your kernel being capped at 1.6GHz probably is better on battery but I also have a sixaxis controller and like to game, does it affect 3D performance at all?
This is the kind of posts I'm looking for in this thread. Do you personally find task's kernel's performance to be any worse than KT's? Cause you said bettery life seemed better.
Also, are the same governers and I/O schedules available between both kernels? The only settings I'm used to using is ktoonservative and row, I wouldn't really know what to do in performance control to emulate what I've done in KTweaker.
Click to expand...
Click to collapse
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app

liltitiz said:
What You won't have on underwear kernel vs kt747: ktoonservative gov, vibration strength control, screen off max freq control, screen off gov control, fast charge, MHz range from 96 to 2106, undervolting capabilities and adjustments to governors and schedulers.
If you don't want to undervolt or tweak anything, I recommend you use underwear kernel. It is stable fast and oc to 1674mhz is alright for any gaming and it doesn't affect 3d performance.
If you wanna use ktoonservative governor then you will have no choice but to use kt747.
But anyway, what you really need is to try both and familiarize yourself with their features.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Comprehensive list. I like it. Now I gotta figure out which gov I'm gonna use when I flash the underwear kernel.
Thanks everybody for their input, if anyone else has anything to say then please go for it!
Wiping cache + dalvik and flashing underwear kernel then fixing permissions and rebooting and gonna take a look around performance control to see whats up.

task650 said:
Or all or any of that could be due to the apps your have on your device, the settings you choose, ect...
P.S- My phone has never gotten hot. Probably due to what I mentioned above.
Click to expand...
Click to collapse
Ohh Thnx man. While you're here any suggestions as to how I go about fixing/finding out which apps are responsible? Also,any combinations/settings you might recommend trying with your kernel,despite the phone dependent variables and what not. Thnx )

Running the underwear kernel today, changes frequencies min and max to the farthest it can go. Will report back with my results.
Sent from my SGH-I747 using xda app-developers app

Sorry man, but no need to report back here as it has already been stated that each User's experience will differ upon usage, apps, personal habits, planet alignment,... Boils down to a flash and see type thing.
Thread Closed
Here is some info on Governor and I/O schedulers. Obviously it isn't going to include Ktoonservative or ROW but you get the idea.