Database Develop

overclocking questions

ive been liking android so far and because overlocking is so simple ive been wanting to try it to hopefully squeeze a little more performance out of the vogue
i just have some questions
whats the highest safe/stable speed?
ive heard some have gone up to 550mhz and quite a few that are at about 500mhz just wanted to know the general consensus from vogue users
my next question is if i clocked up that high should i be worried about heat?
thanks

dude4 said:
i just have some questions whats the highest safe/stable speed? thanks
Click to expand...
Click to collapse
Every CPU is different so this can't be answered. Your's may not overclock 1mhz, it may overclock 100mhz. You just have to try.

Just in case you are interested.
The clock speed must be a multiple of 19.2 so the available speeds between 380 and 600MHz are:
384
400 (because it uses a different pll)
403.2
422.4
441.6
460.8
480
499.2
518.4
537.6
556.8
576
595.2
Other values will be rounded down to one of these.

dude4 said:
whats the highest safe/stable speed?
ive heard some have gone up to 550mhz and quite a few that are at about
Click to expand...
Click to collapse
Stable speed is ALWAYS device-dependent.
Some chips have minor defects (just a fact of manufacturing).
NEVER, EVER just shove it to 550Mhz. Best case your phone will crash. Worst case your phone will burn up.
General rule of overclocking:
1. Increase the clock speed 2-5%
2. Run an intensive app (there's a benchmarking app in the RogueTools trhead) to see if the phone crashes. Run it multiple times (or continuously) for a half hour with the phone plug in.
3a. If it doesn't crash, go back to step 1.
3b. If it crashes, go back 1 or 2 19.2 Mhz steps. This is your stable overclock frequency.
For the 2-5%, as mentioned above, just do every 20 Mhz. Set it to 420, 440, 460, 480, 500, etc.... I wouldn't go past 540.

Overclock or not?

A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.

ZeppeMan said:
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
Click to expand...
Click to collapse
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.

set to 1.13 ghz
then screen off to minimum 245mhz

josemedina1983 said:
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
Click to expand...
Click to collapse
So you underclocked it, what about the speed? It's not to laggy?

Nexus one can run reasonably smooth @ 600mhz and above. It might not open applications as fast as it will be @ 1GHz though.

i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App

shreyas1122 said:
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I didn't said I want an overclock. It's allready very fast on 1Ghz (compared to my old Hero ), just wanted to know your thoughts about overclocking the N1.

im overclocked at 1152 mhz and profiles set for 245 max with screen off. Overclocking is nice because i like the snappiness but most people cant tell the difference between 998 mhz and 1152. its not needed to overclock but i think profiles help alot. just my two cents

Ok thx, I will try 1150Mhz and see (if it's stable and) what batterylife does. I'm also going to try underclocking.
I have my N1 only for a couple of weeks now and I must say, this phone is awesome. It's VERY fast compared to my old Hero. I remember when I was installing apps on my Hero it became very slow and couldn't do anything untill installing was finished. With the N1 you still can do things while installing apps without lag. The responsiveness and smoothness is also a lot faster. I loved my Hero Because it never let me down, ok it was all a bit slower, but it was getting there. Now with the release of Gingerbread (custom ROM) it became to slow for me and that's why I sold my Hero and bought the N1. It was very difficult to find one, because of the EOL (end of life). But eventually I found one and i'm very happy with it. The N1 is allready more 1 year old, but it still competes with the best phones out there.

I generally run overclocked at 1075MHz, which gives a good balance between battery power usage and processor power. My understanding is that a different voltage scaling method is generally used above 1075MHz, so power consumption will increase above that point.

Didn't knew the voltage would increase above 1075Mhz, will keep that in mind

ZeppeMan said:
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
Click to expand...
Click to collapse
This is, of course, dependent upon how the kernel is constructed, but this is what I have generally found to be true.

Give us some feedback

I overclocked it too 1075Mhz when screen is on (screen off 245Mhz). Will give my thoughts in a day or 2.

Just report that my battery drain is almost the same as on stock settings. I think it drains a tiny bit faster on 1075Mhz, but nothing major. On the other hand, I don't feel it's faster on 1075Mhz then on stock speed. Only benchmarks give me performance increase.
I'm now on CM6.1.1 with stock kernel (cyanogen), I tried other kernels like Wilmonks kernel,.. Although it was more responsive, battery was going down even faster. I get best battery results with stock kernel.
Hard to choose
more speed = more battery drain
less speed = longer battery
I think I stay with the last option (less speed = longer battery), because Wildmonks kernel doesn't give me enough performance increase over the stock kernel on stock speed.

I have mine at 998mhz, but overclocked 1152 while plugged into power.
Either way, its so easy to play with the clock settings, i'd just have a play with a bunch of different settings if i were you.

liam.lah said:
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Click to expand...
Click to collapse
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One

ZeppeMan said:
wanted to know your thoughts about overclocking the N1.
Click to expand...
Click to collapse
well my thoughts: underclock!
so you can watch movies on it all night!
Sent from my Nexus One

shreyas1122 said:
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
Click to expand...
Click to collapse
You can use SetCPU to create profiles based on different circumstances.
Me, I have mine clocked to a max of 1075 and min of 245 with the screen on, 576 max / 128 min screen off, 998/128 charging (to reduce heat - overclocking while power is applied can make it silly hot), and a failsafe to clock down to 576/128 if the temperature gets over 50*C.
Fabulous app.

Correct me if I am wrong. When you use setcpu to "ondemand", the CPU speed can ramp up to max whenever necessary, otherwise the speed will tune down to min especially in standby mode. In that way, you can enjoy the advantages of overclocking and underclocking the CPU speed i.e. increasing performance when needed and saving power when not in use, right? When I loaded Rod's MIUI and Wildmonk's kernel, I can underclock down to 128Mhz and overclock up to 1.152Ghz. At the end of the day, I still have over 60% of power left after not so heavily use (some web browsing, checking email and listen some music). Overall, setcpu is a great app for me.

[Q] Nook color overclock.

Hello
I recently acquired a nook color and i am going to install cynogen mod 7.1 and google apps from clock work recovery method, but i want to overclcok to 1.2 or 1.3 ghz, i understand that cynogen mod has an overclock facility built in, the part i am not sure about is to reach 1.2 ghz or 1.3 ghz do i have to use dalingrin overclock kernel to achieve these speeds, or is it possible in cynogen mod 7.1 without the kernel.
Any info would be appreciated.
Regards
Mark

Dal's kernel has been included in there for a while now. If you use 7.1 stable to later nighlies you are definitely safe.

ok, thats great, thanks for the reply, appreciated.
Regards
Mark

It appears the GPU may run best at 1200, even thou the CPU can do up to 1300.

It certainly seems to be true that going past 1200 can slow down graphic intensive operations. I am guessing that's probably because the graphics processor has to run at a ratio of the CPU and going past 1200 ends up with a lower graphics frequency.
But depending on the type of applications used there can be benefit in going higher and most Nooks seem to be capable of 1350. This can be seen in two different benchmarks. Quadrant gives significantly higher scores at 1350 than 1200 whilst the graphically more intensive Nenamark is slower at 1350 then 1200.
I ended up using 1200 anyway as it feels fast and probably also helps with battery life.
Check the voltage settings as well as these can normally be lowered a bit to help again with battery life. I use the one's originally quoted by Dal and don't have any stability issues. ( 09.25 / 1.05 / 1.2 / 1.275 / 1.325)

I did a comparison of 1200 and 1350 MHz with the Sunspider JavaScript bench. 1350 is faster but frankly I have a hard time telling the difference between even stock clock and 1350 in actual practical usage.
The most obvious speed boost I've found is running 16bit color. Big difference in browser scrolling performance.

Is overclocking it fully safe?

GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
From the standpoint that breathing in a metropolitan area is not fully safe, no it is not.
I use the stepper built-in to 7.1 stable and have never given it a second thought.

Try nook color tweaks.
Sent from my [R3] BLURR3D DROID BIONIC using XDA App.

GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
I have run at 1200 / 1350 for the last 4 months and it has been stable and I have not seen any real detectable difference in battery performance or in how warm the device gets. The governor means that a lot of the time the Nook is running at lower clock speed anyway.
I don't recollect seeing any reports of damage on this forum to the Nook through over-clocking. Increasing voltages from the stock values on the other hand is probably not a good idea. There may possibly be longer term effects from overclocking but I'd guess the effect on lifetime is small enough that most people will have changed their device before it is significant.

GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
Being that Nooks CPU is underclocked by default. It is very safe.
---------------------------------
Sent from my LG Optimus V using Tapatalk

[Q] Undervolted

I've undervolted my device and right now I have
100mhz - 825 mah
200mhz - 825 mah
500mhz - 800 mah
for some reason the 500mhz setting is stable and if I undervolt 100mhz/200mhz even more, I crash.
If I set my minimum processor power to 500mhz would I consume less batter than if I were to use 100mhz/200mhz?

Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels

Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.

Maskell said:
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Click to expand...
Click to collapse
It's been my minimum even before posting this thread. I just started to wonder.
I've been on it for 10 hours now. I have 45% battery life left. Probably due to my 1700mhz being @ 1350mah right now.
I can assure you, it's VERY stable. It's so SMOOTH. Smoother than just having rocketrom and all that stuff. NO LAGS, NO SHUTDOWNS. ALL STABLE.
I can see better battery life, and CPU Spy says it used up 47% 1700mhz and 40% 500mhz. I think it's giving me better battery life.
It's evenly splitted up probably because I was using lulzactive governor.
but then again I didn't log my previous battery life without undervolting.
Some more insight would be nice.
SweCrow81 said:
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Click to expand...
Click to collapse
There are alot of risks. Minor chance that you will cause hardware damage to your phone but I'm saying VERY minor. Just don't be stupid with voltages, like just suddenly overdropping the voltages. Your processor might die.
It's scary as hell, it crashes alot while testing and all that ****.
Feels good when you get it stable though.
TL;DR
Very slight chance to damage your hardware; only if you're very daring.
It should increase your battery life by atleast 20% if you reach the peak of your processors limit.

Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help

clairenix said:
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
Click to expand...
Click to collapse
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest

kaos_king said:
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
Click to expand...
Click to collapse
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?

clairenix said:
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
Click to expand...
Click to collapse
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.

I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.

kaos_king said:
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
Click to expand...
Click to collapse
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
liutszho said:
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
Click to expand...
Click to collapse
It's basically the same with SetCPU aside from its voltages.
I do not know if it should be used with SetCPU with the note because from what I've researched. It's only a common practice with SGSII.

Tried setting 100 and 200 mhz to 825. Crashed my phone twice in one day using it, gonna revert back to 875

clairenix said:
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
Click to expand...
Click to collapse
Many thanks!
I will just experiment then, i didnt want to do that and then cause hw damage. I'll let you know how my processor gets on

Overclocking the Nexus 4 - Benchmark of application load time = BIG difference

A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.

please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings

so overclocking makes things faster.. really? who would have thunk. and you just found this out?

my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.

zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.

So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?

well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.

alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?

sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **

gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.

sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **

If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.

No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.

zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100

is there any kernel that can overclock with 4.3?

Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:

simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?

Check the Development sections.
This thread makes my head hurt.