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.

Kernels

been looking through a lot of kernels and Roms, anyone have any particular ones they prefer and why? bit of help on mix and match.
thanks

Stock, or stock voltage and overclocked.
The kernel handles voltages better than manual users do. The rest of the stuff is mostly fluff.

I'm running codename rom at the moment, overclocked to 1.3 ondemand, changed nothing else, didn't go near voltage settings, but mostly just run it stock

adrynalyne said:
Stock, or stock voltage and overclocked.
The kernel handles voltages better than manual users do. The rest of the stuff is mostly fluff.
Click to expand...
Click to collapse
So undervolting and hotplug aren't really beneficial for improving battery life?

I was running morfic's trinity kernel. you can find the thread here

[KERNELS][ICS][I9000] The ICS Kernel Benchmarking Project -Update: Devil

Goal of this little project is to dispel myths and hearsay and trying to assess the elusive performance of custom kernels for our beloved SGS I9000.
So far this has proven quite challenging as there is no single good benchmark on Android (yet):
a lot of people have been misled by ridiculous Quadrant scores: ridiculous because, with some small tweaks which do not affect real performance in any way, shape or form, it is possible to boost the Quadrant score by factor 3x.
You're free to believe that your SGS I9000 which scores 3000+ on Quadrant is faster than a SGS II, but then please leave this thread and move on.
some kernels may seem smooth with some games, and get high scores on some synthetic benchmark, yet the UI appears "laggy" and stutters a lot in comparison to other kernels which score lower on the same benchmark
some popular benchmarks give results with unacceptably low reproducibility, i.e. if you run them multiple times without changing a thing on your system, you get scores varying by 50% of more, in a completely random fashion
most popular benchmarks do not measure or take into account multitasking and CPU contention with other applications, yet on a typical usage one has background tasks such as the media scanner or synchronization which kick in often and unpredictably
So this will be mostly a work in progress, i'm testing several benchmarks and several kernels in multiple combinations, trying to analyze which benchmarks offer certain criteria which make them useful, namely:
Reproducibility of results: running the same tests multiple times, should result in a very small variance of the final score
Performance separation: benchmarks which are too "synthetic" and show only a dependency on clock speed are not useful to discriminate "fast" kernels from "slow" kernels
Performance representation: we all know when a kernel "looks" or "feels" fast or smooth. If a benchmarks shows you that a "laggy" kernel scores higher than a fast and responsive one, it's likely that the benchmark is not well designed
I'll work more on this thread explaining my (current) choice of tests and what they're good for.
But for now i'll just post a link to the summary table, and give a brief recommendation concerning popular ICS kernels; recommendation which i'll explain in the coming days.
Base ROM:
Slim ICS 2.8
(because is fast, smooth and has the least background stuff of all ICS ROMs which i tested)
Test Conditions:
Whenever possible, i tried to overclock the kernels to 1.2GHz which most / all phones should have no trouble achieving.
In case of Semaphore i had to use the bus / live overclock but it wasn't fully stable at 1.2GHz on my phone so i ran most of the tests at 1.14GHz.
Tested Kernels:
Stock Teamhacksung V17
Devil 1.1.6b BFS
Devil 1.1.6b CFS
Icy Glitch V14 b
Semaphore ICS 0.9.5b
Recommendation:
Devil 1.1.6b CFS, Icy Glitch V14b (with SmartassV2 and FIOPS), and Midnight ICS (with a tweaked Conservative) are trading blows for the fastest kernel.
At the time of testing, Midnight is slightly worse in terms of overclocking though, apparently due to different voltages, also it doesn't allow overclocking beyond 1.2GHz.
But what's interesting is that it achieves great performance while using a tweaked conservative governor.
Devil 1.1.6b BFS is good but obviously inferior to its CFS brother.
Semaphore has the lowest cache and memory latency in the multithreaded test, it also has impressive sd card read speed and in general appears super responsive, but it's a bit worse in 3D gaming and especially it lacks "true" overclocking, "live overclocking" changes the bus clock and is way more unstable, in fact on my phone i couldn't run it stable at 1.2GHz.
All kernels are significantly faster than the stock teamhacksung's kernel, so you have no excuses not to upgrade to one of the popular custom kernels!
ICS 4.0.4
Started testing Android ICS 4.0.4 kernels on Slim ICS 3.2.
All tested kernels are "huge mem" versions with 380+MB of available RAM, without breaking video playback or 720p recording.
Summary:
the stock kernel from Teamhacksung is now a very respectable performer, unless you plan to overclock probably you don't need to install one of the other kernels
Semaphore, Midnight and Devil are all very fast and smooth
Results table:
https://docs.google.com/spreadsheet/ccc?key=0AuBUEB4dGFSSdHIyN2VIeWU4QnhLOFpJejFPWDh5S1E

Res 1
One request for the kernel developers:
could you please post me what are your preferred / recommended settings in terms of Governor and I/O Scheduler?
Only one configuration per kernel please, as running these tests is rather time consuming.

Test Settings
So for anybody who wants to follow the same methodology as I used to test kernels, please pay attention that in some tests i didn't use stock settings, to try to improve the reproducibility of the results.
Before all test, i put the phone in flight mode, and disable all synch services.
Antutu: DB I/O and SD Write and Read have poor reproducibility. So i run these tests separately 5 times, and take the best scores.
RealPi: the number of iterations is increased by factor 10x i.e.: 100000 digits
MPAC: lots of customization here. Also be careful as it's not very stable and some settings will make it crash.
All tests: 8 threads (or 8 producer / consumer pairs)
CPU: 10000000 iterations, use case: integer (i'm considering to add logical too)
Memory: stock apart for nr of threads. Repeat the test 5 times and get best numbers
Cache: 40 iterations

Res 3
With this should be enough.

Judging from those results, CFS Devil looks really promising.

Semaphore live oc stability issues happen only on Slim ICS indeed. On ICSSGS I have perfect stability at 1.2 ghz. And performance is just great, paired with very good battery life.
GT-i9000 / ICSSGS 4.2 / Semaphore 0.9.0

A quick question: did you lock the max freq to eliminate the "governor" variable?
Because each kernel could have governor's tweaks that the other don't.
Based on what you posted here, the differences between Glitch and Devil is practically none.
I tested both and didn't feel any tangible difference, in the end, it comes down to the unique features of each kernel.

Overclocking bus vs adding an extra step aren't even slightly comparable. Maybe do tests not overclocked?
Also there is a new glitch build with 100% working bln.
Sent from my GT-I9000 using xda premium

+1 for tests without overclock. Majority of us, users do not overclock. Maybe a seperate test for overclocking could be nice , but comparisons should be done with stock speeds imho.
Thanks for the time and effort. We needed this.

Overclocking bus Vs adding an extra step isn't an apple to apple comparison, I agree.
However my goal was to use each kernel in the best possible way, and if some kernels have the possibility to use higher multipliers / extra frequency steps, that is an advantage for the user, compared to the kernels who only offer live overclock.
Don't get me wrong, i love Semaphore and i've been using it for a long time.
And i have no doubt that some users can get it stable with live overclock to 1.2GHz.
But that is the ceiling, while with other kernels even my phone can reach stable overclocks of 1.5GHz, and that is something to consider.
I chose as the basis for my tests an overclock of 1.2GHz because it's something which practically everybody can use, without massive battery drain, overheat or shortening the life of the device.
I'll try to add measurements at stock speeds for those who don't like to overclock.

cba1986 said:
A quick question: did you lock the max freq to eliminate the "governor" variable?
Because each kernel could have governor's tweaks that the other don't.
Click to expand...
Click to collapse
I didn't want to take the governor variable out.
Because, as you said, each kernel could use (and often does) governor tweaks which make the kernel "special" or different from the others, and that has to be taken into account in evaluating them.
Because nobody will use the phone locked at the maximum frequency.
So for me the governor and its tweaks is part of the user experience of a certain kernel, and a distinctive factor.
At the end, all kernels are coming from almost the same sources, so it's the little things which make the difference.

phzi said:
Also there is a new glitch build with 100% working bln.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
That's great!
This test i run is not the "be all end all", it was just a recommendation at the time of writing.

Pipperox said:
Overclocking bus Vs adding an extra step isn't an apple to apple comparison, I agree.
However my goal was to use each kernel in the best possible way, and if some kernels have the possibility to use higher multipliers / extra frequency steps, that is an advantage for the user, compared to the kernels who only offer live overclock.
Click to expand...
Click to collapse
Agreed but, then again, benchmarks should be done at original CPU clock IMHO.
Otherwise, results are distorted.

HiKsFiles said:
Agreed but, then again, benchmarks should be done at original CPU clock IMHO.
Otherwise, results are distorted.
Click to expand...
Click to collapse
agreed. Especially since stock team hacksung seems to be clocked at 1GHz
what's the point of the comparison? Really?
As expected, there is no noticeable difference between all 1.2 GHz kernels.
It's not as if there was a real difference between them anyway.

zorxd said:
agreed. Especially since stock team hacksung seems to be clocked at 1GHz
what's the point of the comparison? Really?
As expected, there is no noticeable difference between all 1.2 GHz kernels.
It's not as if there was a real difference between them anyway.
Click to expand...
Click to collapse
That's not quite true.
If you look closer, you'll see that Devil CFS has quite a distinct advantage over all others in 3D tests.
The point of the comparison between stock hacksung @1.0GHz and the others, who can overclock, is to show what kind of benefit you get from switching to kernels which are overclock friendly.
Especially considering that you can't assume that a 20% clock speed increase will bring a 20% performance speedup across the board.
At last, i'd say that you may have "expected" that the kernels tested at 1.2 GHz don't have such a difference in performance.
But expectations have to be verified.
I tried to answer the questions:
On Devil's kernel, is BFS really better than CFS?
The "popular belief" is that BFS is faster than CFS.
According to my tests, CFS results faster instead.
Another question may be, what kernel gives you the best gaming performance.
If you pay attention to the An3D Bench XL, you'll see that Semaphore 0.9.5b, even overclocked a 1.2GHz, is significantly slower than Devil.

If i recall correctly Semaphore Author claimed that some kernel developers overclock GPU, and he didn't. Idk anything about it, but i recall something about it.
Is it possible to overclock only GPU, without overclocking CPU??

zipgenius said:
so you should benchmark them without setting anything. Average users don't overclock and don't change governor or scheduler: they flash the new kernel and stop.
Click to expand...
Click to collapse
I completely agree on benchmarking every kernel at the same frequency (stock 1Ghz max) but I think there are two different options for further benchmarking:
1) Benchmark kernels configured as similar as possible regarding CPU governor, IO scheduler, readahead -> comparable results for all kernels.
2) Benchmark kernels with default settings (only makes sense if all compared kernels are optimized for similar purpose like performance, does not make sense if a kernel does *not* focus on max. performance and uses e.g. Conservative CPU governor as default setting.
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).

Interesting thread... I never used devil's CFS version, always BFS. Will try CFS out now.
@Mialwe Where can we get your ics kernel?

mialwe said:
I completely agree on benchmarking every kernel at the same frequency (stock 1Ghz max) but I think there are two different options for further benchmarking:
1) Benchmark kernels configured as similar as possible regarding CPU governor, IO scheduler, readahead -> comparable results for all kernels.
2) Benchmark kernels with default settings (only makes sense if all compared kernels are optimized for similar purpose like performance, does not make sense if a kernel does *not* focus on max. performance and uses e.g. Conservative CPU governor as default setting.
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Click to expand...
Click to collapse
Sorry guys, i understand your logic but i do not fully agree with it.
I'm not comparing overclocked kernels with heavy tweaking of voltages and special settings with which they only work.
I did the "poor man"'s overclock, setting to 1.2GHz using NSTools, a setting where 95% of phones should have no problem working.
I think that if some kernels offer you this possibility while others do not, it is fair to use this "advantage" that they have over the other kernels.
Because a lot of users will have the possibility to do the same as i do, without esoteric knowledge and with just a couple of clicks in the menus.
That being said, "due to popular demand" i will also try to retest those kernels at 1.0GHz as soon as i get a bit of time.
BUT in my recommendations, i will also consider the overclocking capabilities.
@mialwe: sure, i'll give a run to your kernel as well!

mialwe said:
@Pipperox: Would it be possible to check my Mindnight-ICS dev version with your benchmark suite? I'd be really interested in the results as you use the same setup for all kernels (1.2Ghz would not be a problem, does not use LiveOC but old school 1/1.128/1.2Ghz OC).
Click to expand...
Click to collapse
Dude, sorry but i don't seem to find your ICS kernel anywhere.. can you provide a link?

[Q] SetCPU - Extra Info?

Hi there, thinking about getting SetCPU - I have some questions before I do because I hear it can be dangerous?
- I've heard it can brick your phone?
- What if you set it too high?
- Do you personally have to monitor it?
- What are the benefits?
- Use alot of battery?
- Is it really worth using?
- Is it optimized for different phones - example the One X?
Thanks guys!

JDBurnie said:
Hi there, thinking about getting SetCPU - I have some questions before I do because I hear it can be dangerous?
- I've heard it can brick your phone?
- What if you set it too high?
- Do you personally have to monitor it?
- What are the benefits?
- Use alot of battery?
- Is it really worth using?
- Is it optimized for different phones - example the One X?
Thanks guys!
Click to expand...
Click to collapse
Hi, i have read that SetCPU cannot view all the cores i have read alot saying that System Tuner works fine you might want to try that.
I used to use SetCPU on my sensation and never hand any issues with it i did not monitor the app at all
Benefits allows overclocking if available in kernel
it can be overclocked and cause some issues such as overheating but if set correctly will be fine doesnt use much battery if any
and no i dont think you can brick your phone
if you set it too high i believe i had to reflash rom nothing major
BTW this is based on my own knowledge and usage
Hope this helps

Thanks man

JDBurnie said:
Thanks man
Click to expand...
Click to collapse
How much battery life can you save using setCPU?

lamenramen said:
How much battery life can you save using setCPU?
Click to expand...
Click to collapse
None in theory, if the CPU is slower it takes longer to go from
idle - process - idle
Faster speeds allow it to get it over and done with faster and get back to idle.
Of course it will at times stop the CPU going higher than it needs too which could save battery.
Under volting will save more batter then underclocking ever will.
Sent from my HTC One X using xda premium

SetCPU can not see Tegra 3 yet
Use System Tuner and its free

hamdir said:
SetCPU can not see Tegra 3 yet
Use System Tuner and its free
Click to expand...
Click to collapse
Thanks. I have system tuner, but what do I need to do in order to improve battery life?
I have set the governor to powersave. Is there anything else? How would I undervolt using this app?

lamenramen said:
Thanks. I have system tuner, but what do I need to do in order to improve battery life?
I have set the governor to powersave. Is there anything else? How would I undervolt using this app?
Click to expand...
Click to collapse
undervolting requires your phones kernel to support it, currently on these forums there is only one that does but i haven't tested it, sticking firm to the "stock kernel is best" and will do untill the kernels have more time to mature.
you could limit your max speed to 1 GHz, if you are rooted you can use Core control to turn off cores and run your phone as a dual core.

treebill said:
undervolting requires your phones kernel to support it, currently on these forums there is only one that does but i haven't tested it, sticking firm to the "stock kernel is best" and will do untill the kernels have more time to mature.
you could limit your max speed to 1 GHz, if you are rooted you can use Core control to turn off cores and run your phone as a dual core.
Click to expand...
Click to collapse
Not to be lazy, but would running the phone as dual core and limiting it to 1 ghz result in a perceptible battery savings? I'm trying to get a feel for how much I should expect custom ROMs to make my One X perform up to par. Thus far, I've installed two custom ROMs and felt like the improvements were all safely in the minor category.
I did install cyanogenmod 7 on a phone last year wow, that resulted in major benefits.

lamenramen said:
Not to be lazy, but would running the phone as dual core and limiting it to 1 ghz result in a perceptible battery savings? I'm trying to get a feel for how much I should expect custom ROMs to make my One X perform up to par. Thus far, I've installed two custom ROMs and felt like the improvements were all safely in the minor category.
I did install cyanogenmod 7 on a phone last year wow, that resulted in major benefits.
Click to expand...
Click to collapse
Running on 2 cores stops the phone from using and 2 cores uses less power then 4, playing games and using all cores is over kill 2 cores will run the game without lag use less power and make less heat.
You'll maybe get 10% from doing that but I haven't tested.
Really the only time any of this saves battery is during demanding programs, tegrea has a super low power companion core, for all your power saving needs.
Sent from my HTC One X using xda premium

I tried conservative governor while downloading sd files for Nova3 gave execllent results
I strongly advice not to undervolt tegra3
t3 is not like any other chip and UV or OC should not be attempted
OC because the chip is already at the max of its thermals
UV for the same reason n might end up with problems like flicker
changing governors and UC should be enough

[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.