Database Info

1.6GHz

:giggity: Adrynalyne test kernel
{
"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"
}
quadrant

Care to Share How?

This is cool but with it at 1.6 how long did the battery last >.>

And it begins! adrynalyne is a beast.
Sent from my ADR6400L using XDA App

You getting about 5 mins of battery life now?

That's teh sex!

Christ I wouldn't want the CPU that fast... 1.2Ghz would be my limit just because the battery wouldn't take too drastic of a hit. I mean the phone is already pretty well sound in the speed department

The real question (rather than being a smartass about it) is whether or not the custom kernel is simply overclocked... or if it is undervolted and overclocked.
It is very possible to obtain higher clock speeds at lower voltages on many CPUs. Therefore, there is no battery sacrifice when using the faster CPU clock speed!
Wasn't the G2 or MT4G overclocked to 1.6GHz and also undervolted to provide better battery life than the stock kernel?!

Well I did that just to show it works and is actually stable (ran it for 10 mins at that speed, no reboot). I just put it on there a couple minutes before that.

bmcclure937 said:
The real question (rather than being a smartass about it) is whether or not the custom kernel is simply overclocked... or if it is undervolted and overclocked.
It is very possible to obtain higher clock speeds at lower voltages on many CPUs. Therefore, there is no battery sacrifice when using the faster CPU clock speed!
Wasn't the G2 or MT4G overclocked to 1.6GHz and also undervolted to provide better battery life than the stock kernel?!
Click to expand...
Click to collapse
I honestly have no idea.

JayfromBK86 said:
Christ I wouldn't want the CPU that fast... 1.2Ghz would be my limit just because the battery wouldn't take too drastic of a hit. I mean the phone is already pretty well sound in the speed department
Click to expand...
Click to collapse
I had my OG droid OCd to 1.1ghz and had better battery life running Bugless beast and chevy's low voltage 1.2 kernel. Stock on the OG was 550 i think so i was doubling that speed, 1.6 once its played around with will probably not sacrifice your battery at all down the road.

I want one, I want one! Lol
Sent from my ADR6400L using XDA App

i want!!!!

hmm...~1700 on Adrynalyne's kernel for das BAMF 2.9 to 2300 OC'd. not bad

bmcclure937 said:
The real question (rather than being a smartass about it) is whether or not the custom kernel is simply overclocked... or if it is undervolted and overclocked.
It is very possible to obtain higher clock speeds at lower voltages on many CPUs. Therefore, there is no battery sacrifice when using the faster CPU clock speed!
Wasn't the G2 or MT4G overclocked to 1.6GHz and also undervolted to provide better battery life than the stock kernel?!
Click to expand...
Click to collapse
The D1's would run undervolted/overclocked with no problem. I ran mine @ 1.1ghz and undervolted.

magneticzero said:
You getting about 5 mins of battery life now?
Click to expand...
Click to collapse
Higher clock speeds =/= more battery usage

The UV stock clocked version of this kernel is hitting high 1800s to low 1900 in quadrant for me on a debloated but otherwise stock rom.

engagedtosmile said:
Higher clock speeds =/= more battery usage
Click to expand...
Click to collapse
not always. if it is a higher clock speed at a lower voltage it won't

nosympathy said:
not always. if it is a higher clock speed at a lower voltage it won't
Click to expand...
Click to collapse
That's what he was saying. "=/=" is "does not equal."
;-)

that's just silly without any extra qualifying statement.

Important Information About Overclocking - MUST READ

This is a message from a developer who is in a team who develops a kernel with a very large overclock. Do not take this is an idiot babbling, read this and take it to heart as this is very important.
I want to talk to you about overclocking our phone and how dangerous it can actually be. I love overclocking, and have overclocked my main computer, and I overclock my phone, but my overclock (as you can see from my signature) is very mild. A simple 800MHz overclock.
When we first got overclocking on our phone (thanks to Fugumod), we were around 800MHzish and it gave a nice boost. It got up to 1GHz and it gave another good boost. Over time, we have discovered the phone works at high speeds, now 1366 in Fugumod, and 1400 in G3MOD. Now if you look at these speeds and compare it to the original clock speed on our phone (667MHz, or you can look at the Spica which has the same CPU but with a larger transistor process: 800MHz), this is a 204% overclock on Fugumod and 209% on G3MOD.
Now let's put these percentages into perspective: on your desktop computer, a 200% overclock is normally only possible with serious cooling: water or liquid nitrogen, and we are attempting to do this in a PHONE with NO cooling, and NO ventilation. Furrthermore, it is kept in our pockets beside our thigh muscle: the largest muscle in our body and it emits a large amount of heat. These are not ideal conditions for a CPU to be kept in, especially when it is in a fragile state such as overclocking. We are lucky however because phones have clock governors which clock it back when it is idling to conserve power.
When you overclock the CPU, you must also overvolt it to keep the system stable while overclocked. However the downside is that if you overvolt your CPU, you will use more power, and also reduce the lifespan of our CPU. Let me show you how much more power is required to run the phone at 1.4GHz.
Now, as we don't know the exact power consumption of our CPU, I will assume the power consumption is 100mW. In overclocking a desktop computer, we use this algorithm:
Code:
OC Wattage = TDP * ( OC MHz / Stock MHz) * ( OC Vcore / Stock Vcore )^2
So that means 100 * (1400 / 667) * (1525 / 1200) ^ 2 = 338mW. That is over 3 times the power consumption of the CPU at stock speeds. That also in turn effects the lifespan of the CPU as the transistors are both having to work twice as hard (as the CPU clock is twice as high) and are drawing three times the power consumption, this means the CPU will last 6 times less at 1400MHz.
When we were starting out with overclocking our phones, we didn't have a lot of the nice new features we have discovered that boost performance but now that we do, these huge overclocks just aren't as necessary anymore.
TL;DR
Guys, our phone can go at 1.4GHz or 1.36GHz, yes. But is it a good idea to keep it at those sorts of speeds? No. The reason marcellusbe and the G3MOD team provide such HUGE overclocks are for rare occasions. When the phone is just doing nothing, we expect you to put it back to 667/800MHz, but when you are wanting to play Angry Birds or emulate Castlevania 4 or something, you put it up to 1400MHz, but put it back again once you are done. 24/7 usage at 1400MHz or 1366MHz is DESTROYING your CPU and your battery.
USE OVERCLOCKING WITH EXTREME CAUTION
Extra Information
Here is a graph to show the power consumption increase from running the CPU at higher overclocks and also the reduction from undervolting.
{
"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"
}

Even an i7 is rarely oced to 200% - its too much and can be dangerous

cdesai said:
Even an i7 is rarely oced to 200% - its too much and can be dangerous
Click to expand...
Click to collapse
Precisely my point.

Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...

dharamg3 said:
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
Click to expand...
Click to collapse
+1 For that too
Nice information. I always used to keep my phone to 1200 mhz. Damn should reduce it now

Thanks, excellent info.
Sent from my GT-I9000 using Tapatalk

I never try to go beyond 800Mhz
I think it is sufficient for daily use
(More than sufficient)

exactly.... i was going to post somthing like this
when u need that boost (like for ps1 emulator or hd games) us upto 1.3ghz
but otherwise just leave it at 800-900mhz...
u dont need crazy oc all the time!

Doesn't SetCPU (or any other app for that purpouse) do exactly that? If you set scaling and min/max freq. accordingly? What is the difference beetween that and setting in manually?

Gud info mate......
Governer should be Ondemand right ????

Hm, a guy called Kyrillos told me, that normal voltage at 667MHz is 1200mV. So, in newest g3mod, from 500MHz on, its higher, at 800MHz its already 0,1 volt above max in stock.
So how dangerous is it to let it allday at [email protected] ?

DaBigFreak said:
a guy called Kyrillos told me,
Click to expand...
Click to collapse
He s a recognized developer. A very good one infact. He was right by the way. Its only the faulty reading.
---------- Post added at 01:32 PM ---------- Previous post was at 12:54 PM ----------
Hillbeast excellent, excellent info. That s the precise reason I don t use high overclocked kernels. Maximum I goto is 800MHz.

raja4sure said:
Gud info mate......
Governer should be Ondemand right ????
Click to expand...
Click to collapse
Yes. I use it mostly. Other devs and experienced users here as well for what i've noticed. Or conservative which saves battery because it scales freq more gradually. http://www.setcpu.com/ - http://www.setcpu.com/#7
And profiles, especially the Temp and screen off. Prevents from overheating and exscessive battery discharge, respecitvelly.
DaBigFreak said:
So how dangerous is it to let it allday at [email protected] ?
Click to expand...
Click to collapse
Probably very. But overclocking in general shortens life span of electronic components, primarily because of increased heating. If that worries someone that it is probably best not to overclock at all.
I personally see no difference between manipulating cpu freq manually or by using some app to do it when necessary. If I'm wrong then please feel free to elaborate.

dharamg3 said:
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
Click to expand...
Click to collapse
I will update this thread and I hope it will actually get stickied as it's quite important information in my opinion and it could save some peoples phones.
mrvek said:
Doesn't SetCPU (or any other app for that purpouse) do exactly that? If you set scaling and min/max freq. accordingly? What is the difference beetween that and setting in manually?
Click to expand...
Click to collapse
SetCPU will obviously set the max and min settings, but in an ideal situation you will want to have a mild overclock (or none at all) if you are just using for phone for normal functions such as TXTing or browsing or something like that, but SetCPU can't detect when you are wanting a more intense operation such as a game, so you're best to adjust it when you are needing it and switch it back.
I keep a SetCPU widget on my home screen to do that.
DaBigFreak said:
Hm, a guy called Kyrillos told me, that normal voltage at 667MHz is 1200mV. So, in newest g3mod, from 500MHz on, its higher, at 800MHz its already 0,1 volt above max in stock.
So how dangerous is it to let it allday at [email protected] ?
Click to expand...
Click to collapse
The stock voltages for our phone at 667 is 1200mV, yes. At 1300mV you will notice a mild increase in consumption.
If we follow the same algorithm in the OP:
Code:
OC Wattage = TDP * ( OC MHz / Stock MHz) * ( OC Vcore / Stock Vcore )^2
We get (again, assuming the standard consumption is 100mA) 100 * (800 / 667) * (1300 / 1200) = 140mA. Yes, it's higher but not too much higher. If you UV it by 50mV @ 800MHz you'll go to 130 and at 1200mV it'll be 118mA.
Overclocks like this are still not 100% safe, but they are nowhere near as dangerous as a 300% power consumption increase.

This is the Information I was looking for past 2-3 weeks. Finally you posted it here.
Thanks hillbeast

Hey man. I really appreciate your effort to inform. I just would like to add something.
Overclock: in modern cpus power consumption increases almost linearly with clock. Let us say linearly to be safe. It means double clock double power (and so heat)
Voltage: when you increase the voltage the power increases approx quadratically (double voltage for times power). But also higher voltage means stronger signals in transistors and so higher stability.
Heating and lifetime: the heat decreases the lifetime of electronic components but not in a linear way. Please also note if a circuit does not die very soon (infantile mortality) it will last very long in normal conditions. So even if it was cut by half starting from the normal 10 years expected lifetime it would be anyway long for a phone.
So it is clear voltage is much more important than clock for power consumption. Decreasing the voltage you could have an overclocked cpu which consumes and hests up less than the stock one. Of course it is less likely to be stable.
Personal computer cpus needs cooling and are difficult to overclock because they become very unstable when overclocked so you have to increase voltage.
Finally to be clear I want to repeat your lesson.
DO NOT OVERCLOCK UNLESS YOU REALLY KNOW WHAT YOU ARE DOING. and don't complain with developers if your phone will break.
Sent from my GT-I5800 using XDA App

After reading this, I will never overclock more than 1GHz. Thanks

I agree extreme 200% overclocking is harmful to cpu and disagree with some of the points.
I don't think wattage and tdp formula are correct. If it is correct in reality battery should drain in 1/3rd of the stock time and should heat up immediately. we are just increasing the power supply in mv which is 1200 to 1500%. That means 25% power increase.
When the phone is in idle (no music, wifi, data ...) mode cpu/armcore is completely turned off. That means no frequency, no power supply and no heat. Other peripherals have separate clocks and they will keep running in idle mode. This is the difference between desktop and phone cpu.
frequency is 'no of times turning on and off transistors in a circuit per second'. In fact cpu's are designed to work at much more frequencies than stock. But stock frequency is decided by considering various operating conditions worldwide and $$. Personally i use 1020Mhz and phone operates like stock frequency.

I don't agree with one of the last statements:
hillbeast said:
So that means 100 * (1400 / 667) * (1525 / 1200) ^ 2 = 338mW. That is over 3 times the power consumption of the CPU at stock speeds. That also in turn effects the lifespan of the CPU as the transistors are both having to work twice as hard (as the CPU clock is twice as high) and are drawing three times the power consumption, this means the CPU will last 6 times less at 1400MHz.
Click to expand...
Click to collapse
Assuming you use setcpu, your phone spend most of the time in standby. if you use your phone a lot, it will be in standby 70% of the time.
Assuming that when your phone is not in standby the clock is automaticly set to 1400 (which is probably not, but we're doing worst case), your phone will be overclocked 30% of the time.
If your statement about battery drain is correct, the processor will use 160% more battery than usual. This, will not result in a huge battery drain, because actually, the processor is draining very little battery compared with things like display, wifi, 3g and so on.
If your statement about lifespan of the cpu is correct, the lifespan of the cpu is reduced to 75%. Considering that a cpu can last years and that you usually throw your phone away way before the cpu stops working, doesn't seem like a big deal to me.

That is true. Unless you run your phone 24/7 at max OC speed and phone heats up excessively there really should not be problems. That's why we have good apps and scaling governors that save the cpu and battery. In my case the phone spends most time at 400Mhz, then on 800, then 1400 then other freqs (based from setcpu report - info → time in state). Main profile beeing 400/1400, ondemand. And temp doesn't go over 31°C on daily use. What increases temp are mostly games but for that i use several setcpu profiles (in this point i disagree with hillbeast and the ability of setcpu to know my specific requirements. I know that it can't know what i need and when but if I set manually the requiered freq (max) to play a game the phone would heat up significatly (angry birds for about 30 mins gets me to 36°C - relatively high). And then i need profiles not to overheat the phone. And now when I already have profiles, why not let everything be automatic?).
Please don't get me wrong, I agree that OC-ing is quite risky and it should (must‼) be done with great caution and that is an implicit requirement.

[Q] voltage control tutorial?

Is there a tutorial (written or video) that shows how to use this? I've never overclocked or changed the voltage before and i dont wna just go in there n start messing with stuff when i have no clue what im doing. Ive looked around for maybe a begginers tut or like voltage control for dummies, but havent really found anything. Anyone know of one? Thanks.

It's really not very hard. The regular Voltage Control will not allow you to overvolt, so you will not run the risk of frying your processor. Don't go over 1400 mhz though. Bad magic after that.
Undervolting will not harm your phone, the most it will do is make it lock up. Just experiment with different voltages. Back in the day I used to run -75 mV across the board without many issues, but I don't really have a use for it anymore since I carry a spare battery. Don't be frustrated if your phone doesn't like even -25 mV though, because every processor is slightly different in their abilities to handle voltage and frequency changes out of spec.
Please note that PBJT kernel is already undervolted a good amount.
Sent from my SCH-I510 using xda premium

Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!

n1ghtwish said:
Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!
Click to expand...
Click to collapse
Can you please tell me what the actual voltage is? I found that with IMO 4.0 kernel, and with Tegrak Overclock Ultimate, I can clock the at 1.252 Ghz @ 1285mV and 1.3 Ghz @ 1330mV stably. However, I don't know what the actual stock voltage is or the PBJT voltage or IMO 4.0 voltage, etc.
I figure you could check the voltage at least with the free version of Tegrak.

{
"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"
}
Stable for days... Vr ..smartassv2.. 1200 max 100 min.. Eclipse with 1/15 pb&j
Sent from my SCH-I510 using XDA App

Phone is laggy
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb

dees_74 said:
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb
Click to expand...
Click to collapse
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
My phone was great when I flashed, but within about 12 hours, things were horrible. I have since flashed back to the stock fp1 kernel, and life is good. Unfortunately, I am not a person who 'leave well enough alone'. I'd like to enter the world of over/ under clocking and see if I can gain some additional performance.
Thanks in advance for any additional info/advice you can provide.
Sent from my Xoom using XDA

shrike1978 said:
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.
Click to expand...
Click to collapse
War Eagle!
I thought that was how it worked, but I will open voltage control from time to time and it will read that its currently at 400 or 800 MHz. Does the program not display properly?
edit: Playing around with it some more, if I change it to something else and then switch it to performance it goes right to 1000. Weird that it displays incorrectly when the program is opened.

[Q] Quick question about overclocking and battery

I have just one quick question about overclocking. If default speed of MSM8260 is 1.5GHz, and it`s just underclocked in stock sensation, then processor set for 1.5GHz "eats" battery faster than 1.2GHz or there is no difference? I understand that overclocked processor eats battery faster, but I`m just not sure in this case.

It probably eats battery a little quicker.

I think so but I just want to be sure is any1 really sure??
Sent from my HTC Sensation using XDA

it eats battery. trust me, i own an xe not so much though, but noticeable

Thanks so now it's clear but you're lucky enough to have bigger battery than my "usual" sensation
Sent from my HTC Sensation using XDA

gallardo5 said:
Thanks so now it's clear but you're lucky enough to have bigger battery than my "usual" sensation
Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse
Just get an anker if you want more power. I've heard they're really good. And cheap too
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA

washed ancedle
dexter93 said:
Just get an anker if you want more power. I've heard they're really good. And cheap too
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
Click to expand...
Click to collapse
Before you decide, check this: http://forum.xda-developers.com/showthread.php?t=1515181
The_Genius

But I heard a lot good things about Anker. I will think about getting one

there are different cpu frequency modes, overclocking just raises the highest frequency when on demand
Sent from my HTC Sensation Z710e using xda premium

using a 1.5ghz kernel will not eat your battery any faster than stock (1.2ghz) unless you are running games and benchmarking. the way a modern CPU works is that it throttles up to max speed when needed, most of the time it will probably be sitting at around 400mhz, a 1.5ghz kernel only raises the max amount which in some situations can actually increase your battery life since it will perform tasks quicker and go back to 400mhz after its done faster

norazi said:
using a 1.5ghz kernel will not eat your battery any faster than stock (1.2ghz) unless you are running games and benchmarking. the way a modern CPU works is that it throttles up to max speed when needed, most of the time it will probably be sitting at around 400mhz, a 1.5ghz kernel only raises the max amount which in some situations can actually increase your battery life since it will perform tasks quicker and go back to 400mhz after its done faster
Click to expand...
Click to collapse
+1
Gaming is not something I generally use my sensation for and since I've been running 'ondemand' at 1.5GHz max I've seen a noticeable improvement in battery life.

I have mine at 1782 MHz and battery is still fine.

I have mine up to 1.83ish, battery seems better, sounds odd but hear me out,
If the clock speed is higher the CPU won't need to wake the second core as often, as it can still handle the operations, so if it uses 10% more power from 1.5ghz to 1.8ghz, its better then using an extra 40% waking and running second core, but doing heaving operations will then of course run down quicker @ 1.8ghz then 1.5ghz.
So basically if you use your phone light to moderate use, e.g. because your at work so few texts, calls and a little gaming, then 1.8ghz max the battery will last longer, if you text all day and watch videos and a lot of gaming use 1.2/1.5ghz.
And an Anker 1900mah battery will help too
Test yourself with Sebastians Kernels and don't forget the thanks
Sent from my HTC Sensation using XDA Premium HD app,

norazi said:
using a 1.5ghz kernel will not eat your battery any faster than stock (1.2ghz) unless you are running games and benchmarking. the way a modern CPU works is that it throttles up to max speed when needed, most of the time it will probably be sitting at around 400mhz, a 1.5ghz kernel only raises the max amount which in some situations can actually increase your battery life since it will perform tasks quicker and go back to 400mhz after its done faster
Click to expand...
Click to collapse
Actually, the processor will never reach 1.5 GHz. It's only the theoretical throughput.
OllieArmageddon said:
I have mine up to 1.83ish, battery seems better, sounds odd but hear me out,
If the clock speed is higher the CPU won't need to wake the second core as often, as it can still handle the operations, so if it uses 10% more power from 1.5ghz to 1.8ghz, its better then using an extra 40% waking and running second core, but doing heaving operations will then of course run down quicker @ 1.8ghz then 1.5ghz.
Click to expand...
Click to collapse
and that is a false claim. Back your claim with facts.

ungraph said:
Actually, the processor will never reach 1.5 GHz. It's only the theoretical throughput.
and that is a false claim. Back your claim with facts.
Click to expand...
Click to collapse
65% after 11 hours on medium use
{
"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"
}
Sent from my HTC Sensation
ROM: ARHD 6.4.0
OVERCLOCK: 1.832Ghz
BATTERY: Anker 1900mAh
S-OFF: Yes (Revolutionary)
RECOVERY: 4ExT

ICS Overclocking Resources/Guides - Heat issues Kernel tests Post your experiences -

Here's a response from a PM i recieved about my Antutu benchmark scores. This is meant to be a reference to others who are working to squeeze optimal performance out of their captivates.
Hi, want to know what setting you do to reach more than 4000 points on antutu bench xD i just cant go more than 3800
Regards
Click to expand...
Click to collapse
Overclock at your own risk!
I am not responsible to any damage to your phone
I've had lots of experience over clocking desktops computers, I started when I was 14 years old or something. I am very happy to share my experiences here with my captivate.
Here's what I've been using to test the stability and speed of each incremental change: https://play.google.com/store/apps/...chMark&feature=nav_result#?t=W251bGwsMSwyLDNd
It's Antutu Benchmark.
Some may not like Antutu, and that's understandable, it's just the standard i have used to compile my testing results. if you have a better app to use suggest it!
The highest Antutu score i was able to achieve was 4044 when i was on 1.508 ghz. running Devil .86
Recomendations/Results:
I've been testing mostly stock settings between devil .86 and semaphore 1.2.5sc and devil keeps coming out on top with it's scores. not trying to start a war, but devil is just faster. don't get me wrong i love semaphore.
I am using Slim ICS 4.1, it's been the most stable ROM for me so far, if somebody can post their results with a different ROM and kernels then i gladly support it!
Slim: http://forum.xda-developers.com/showthread.php?t=1517486
Tests between Semaphore 1.2.5.sc and Devil .86
I had both semaphore and Devil running live OC of 116% and after each test devil kept winning by about 50-80 points.
I recommend the Devil Kernel by DerTeufel1980, DerTeufel1980 is very helpful and supportive, he also turns out updates like a machine!
The devil kernel supports increasing frequency as well as live OC. It also has so many other cool features that make it fast(like GPU overclocking). This is why I recommend this kernel for Overclocking speed and stability.
His kernel is here: http://forum.xda-developers.com/showthread.php?t=1642460 Sometimes he posts a downloadable release in the middle of a page so you usually have to search for it.
Advice/Settings
Overclocking to high stable frequencies, and having the least apps active is the key to getting the highest overclocking scores with Antutu.
To get scores over 4000 I use this set up:
My settings, SIO, Conservative governor, Frequency at the 1300mhz step, live OC at 116%(this yielded 1.508ghz). I had UKSM on(whether on or off didn't seem to make a difference during my tests), i had the GPU overclocked to 250mhz. I was using the XL mem version (391mb ram).
I had intended on running more tests on the big mem version but the constant reboots got tiresome, if anybody wants to take this up I'll gladly support it.
Crashes: Crashes are inevitable when testing. sometimes you get lucky and only the app crashes, most of the time though you will get a frozen screen or a few seconds followed by a reboot. depending on your kernel some may reset your settings. Use NS tools and save a setting that you know is stable and save your test settings so you can start from where you left off.
Voltages: the key to stability!
BE VERY CAREFUL WHEN YOU ADJUST YOUR VOLTAGES! too much is harmful to your chip!! Heat and overvolting is harmful!
these are my voltages:
Arm voltages
1400mhz it's 1.475
1300mhz its 1.450
Int Voltages
1400mhz it's 1.25
1300 it's 1.225.
The rest is stock. If anybody has found stable underclocking for the lower frequencies please post them here.
Live OC:
Something strange i noticed was that whenever i would do a odd numbered live OC i would get major instability... 116% was much more stable than 115%. weird huh? also i am pretty much unable to get a stable live OC of more than 116 regardless of the frequency step. Each phone will have it's own stability limit for Live OC. Some phones can go all the way up to 130%, but that's rare.
the key is to keep finessing it and carefully and incrementally change things till you find a nice sweet stable spot, other phones can achieve more live OC.
My favorite Fast Stable Safe setting:
My phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.
Some may balk at my use of the conservative governor, I Love it actually, CPU spy reports that the conservative governor barely ever uses the highest step for regular usage. Which is great because you don't need the highes step to be running all the time as most actions don't require it, the less high voltage you send to the chip the better. It also helps with battery life.
HEAT!!!!
Warnings about heat. voltage increases mean more latent heat. your phone is a closed system so the heat gets locked in easily... Warm is allright(not wonderful) any hotter than warm and you need to take steps to manage the heat. I've found two easy ways to deal with it, aside from putting it in my refrigerator lol
For stress testing I ussually have the battery cover off, one less thing to get hot.
One simple way to manage it when you feel the sd card slot warm is to press the SIM/Sd slot to your lips and blow air through the phone, this will help cool it down. another way to manage the heat is to do this
{
"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"
}
I borrowed a cooling fan from my gaming computer and set the phone up on it with the battery cover off. this really helped keep it cool.
Also, never leave your phone sitting in the sun on a hot day, I don't know why you would in the first place. But just don't.
Higher scores are achievable... just keep tweaking things.. I deleted all my user apps so nothing would run in the background and that did helps my scores a bit.
Also airplane mode prevents unwanted texts form interrupting testing. that way the phone can focus only on the task at hand
I bet wiping the SD card would improve read/write speeds incrementally...
If somebody wants to research this please post it here
Please read this before you post "results"
Please run at least 2 or 3 tests to sort of average the scores before you post about a result. This will help keep information clean of errors that can affect test results.
for example when i was doing a 1.392ghz test on Antutu, during the knights hacking thier swords scene a glitch happened and my frames per second shot up to 102 fps. It occurred for a few seconds but it was enough to offset the scores A LOT. I got a 4185 on 1.392ghz which doesn't seem possible. consequently I hold the #6 score listed for the captivate :laugh:
This is why I say get an average for the scores. with my 1.392ghz set up i tend to get scores ranging from low 3800's to high 3900's
Remember each phone is different!
Have fun tweaking!
Hope this helps!

Hi.
Thanks for sharing.
My undervolting values are:
100 Mhz = 800
200 Mhz = 850
400 Mhz = 950
800 Mhz = 1125
1000 Mhz = 1225
1200 Mhz = 1300
The attachment is a graph with my experiments to find a fast and stable configuration. The red line is my best so far.

BitteredBro said:
Hi.
Thanks for sharing.
My undervolting values are:
100 Mhz = 800
200 Mhz = 850
400 Mhz = 950
800 Mhz = 1125
1000 Mhz = 1225
1200 Mhz = 1300
The attachment is a graph with my experiments to find a fast and stable configuration. The red line is my best so far.
Click to expand...
Click to collapse
Excellent! i might have to try some of your undervolting! Did you do tests with a max voltage set to determine stability?
also what do you test it with?

What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app

melvinaury said:
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
My guess is that it's the ARM voltages, idk though.

My phone doesn't like speeds over 1.4 nor live OC over 20%. Those are my max settings without freezes or reboots.
For stability testing I use nbajam and blood and glory. Those games are very sensitive to changes in voltage and overclocking.
Sent from my SGH-I897 using xda premium

melvinaury said:
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Those are arm voltages.
I don't feel comfortable messing with Int voltages.

Anybody able to get a stable 1.6? I can't seem to get it stable...
Sent from my SGH-I897 using xda app-developers app

I think Icepack might work better!

bravomail said:
I think Icepack might work better!
Click to expand...
Click to collapse
Hahaha! Good idea!
Sent from my SGH-I897 using xda app-developers app

baconatorXVI said:
My favorite Fast Stable Safe setting:
My phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.
Some may balk at my use of the conservative governor, I Love it actually, CPU spy reports that the conservative governor barely ever uses the highest step for regular usage. Which is great because you don't need the highes step to be running all the time as most actions don't require it, the less high voltage you send to the chip the better. It also helps with battery life.
Click to expand...
Click to collapse
Great info, thanks. I had my phone running 1.5ghz (directly, no Live OC) all day long on Glitch kernel a while back... before I started flashing Devil. Right now on Devil I am trying out underclocking while using live OC, so I have the frequency set to 800 with a 110% Live OC so the CPU is at 880mhz. SmartassV2 and SIO. It is very responsive and I should try a higher Live OC I think.
I had trouble using the GPU OC feature... have you been using that at all? I think I remember someone mentioning they had GPU OC plus a Live OC on top of that... I would think that would be harmful to the GPU, right? I set the GPU back to 200mhz since I was getting more and more frequent FCs, freezes and reboots. Thanks for your posts and sharing your results.

They Drew First Blood said:
Great info, thanks. I had my phone running 1.5ghz (directly, no Live OC) all day long on Glitch kernel a while back... before I started flashing Devil. Right now on Devil I am trying out underclocking while using live OC, so I have the frequency set to 800 with a 110% Live OC so the CPU is at 880mhz. SmartassV2 and SIO. It is very responsive and I should try a higher Live OC I think.
I had trouble using the GPU OC feature... have you been using that at all? I think I remember someone mentioning they had GPU OC plus a Live OC on top of that... I would think that would be harmful to the GPU, right? I set the GPU back to 200mhz since I was getting more and more frequent FCs, freezes and reboots. Thanks for your posts and sharing your results.
Click to expand...
Click to collapse
No problem, your post on the devil kernel thread helped convince me to switch to SmartassV2. I'll probably bring a condensed version here for whoever else stumbles here.
I've only had one troubling experience with gpu overclock on. I was going for a high antutu score running something like 1.5ghz. Anyways, for whatever reason during one stage of the test, can't remember which, i got a strange green flashy line across the screen. it was very unsettling cause i thought it was a hardware issue that i would have to live with. it stayed there even though i stopped the test. turning the screen on and off didn't fix it either. thankfully rebooting fixed the issue.
The only other time i've seen visual artifacts like that is when I would overclock my graphics card on my desktop. so i assume it was a graphical processing error.
I can't say for sure if gpu overclocking AND live OC together cause problems. although I wouldn't be too disappointed if my cappy died, then i'd unfortunately have to upgrade to the Galaxy SIII

Dumb question, but how have you two over clocked the gpu? Is it possible to underclock while having the CPU overclocked? For my phone, the gpu always locks before the ram/proc. I can tell because the screen gets all fuzzy with lines which makes me reboot.
Sent from my SGH-I897 using Tapatalk 2

goob1284 said:
Dumb question, but how have you two over clocked the gpu? Is it possible to underclock while having the CPU overclocked? For my phone, the gpu always locks before the ram/proc. I can tell because the screen gets all fuzzy with lines which makes me reboot.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Well we are able to overclock our GPU's because the devil .79 and on kernel allows the choice between either 200mhz(stock) or 250mhz.
to underclock the gpu you would need to talk to a kernel maker.
Maybe you need to increase your voltages... don't increase them too much though. I'm not totally familiar with the architecture and design of each processing bit inside the captivate but from my knowledge of computers, more voltage makes it more stable.
this question should be asked to a kernel maker! i hope you find your solution.
are you past warranty? you're positive it's not a rom issue? did this happen while it was stock?

baconatorXVI said:
Well we are able to overclock our GPU's because the devil .79 and on kernel allows the choice between either 200mhz(stock) or 250mhz.
to underclock the gpu you would need to talk to a kernel maker.
Maybe you need to increase your voltages... don't increase them too much though. I'm not totally familiar with the architecture and design of each processing bit inside the captivate but from my knowledge of computers, more voltage makes it more stable.
this question should be asked to a kernel maker! i hope you find your solution.
are you past warranty? you're positive it's not a rom issue? did this happen while it was stock?
Click to expand...
Click to collapse
Overclocking GPU is an option, but it is disable as well as the 56/60 Hz switch.