Database Info

OC/UV - What Are Your Results?

Just started playing around with UV/OCing tonight and am pretty happy so far with the results. I'm just currently looking at getting some extra battery life with UVing.
Just curious what everyone else has achieved.
And yes I know, and everyone else should know, that just because someone else was able to get a certain OC/UV doesn't mean you will. So is the game of OCing anything.
Please post the full details of what you have achieved and/or what you run as a daily driver.
In this format:
(My current results, so far)
1120Mhz @ -125
1000Mhz @ -125
900Mhz @ -125
800Mhz @ -125
600Mhz @ -125
400Mhz @ -125
200Mhz @ -125
100Mhz @ -125
Rom: Continuum v4
Kernel: Onix - 2.0.1 #7
(I'm curious what the lowest voltage has been attained at stock/1120 clock)

bnevets27 said:
Just started playing around with UV/OCing tonight and am pretty happy so far with the results. I'm just currently looking at getting some extra battery life with UVing.
Just curious what everyone else has achieved.
And yes I know, and everyone else should know, that just because someone else was able to get a certain OC/UV doesn't mean you will. So is the game of OCing anything.
Please post the full details of what you have achieved and/or what you run as a daily driver.
In this format:
(My current results, so far)
1120Mhz @ -125
1000Mhz @ -125
900Mhz @ -125
800Mhz @ -125
600Mhz @ -125
400Mhz @ -125
200Mhz @ -125
100Mhz @ -125
(I'm curious what the lowest voltage has been attained at stock/1120 clock)
Click to expand...
Click to collapse
I have mine oc. to compensate with battery drain I was undervolting also here is my specs:
1400- 0 Quadrant - 2258 Linpack - 20.1
1000- 50
800 - 100
400 -125
200 -125
100 -150

Here's what I got
1400 @ -25 Quadrant ~1900 Linpack ~19
1200 @ -50
1000 @ -50 Quadrant ~1600 Linpack ~14
800 @ -75
400 @ -75
200 @ -100
100 @ -100
EDIT: I use Voltage control app, some people seem to have issues with set CPU
______________________
Samsung Captivate
ROM: designgear's Cognition v4.2.2
Kernel: eXistZ's KB1 #7 beta

i envy you guys that can run stable at those numbers. my results are
1280 -50
1000 -25
800 -100
400 -100
200 -50
100 -50
with less over clock i can get much lower voltages across the board and without over clock i can go lower still.
having the actual voltage the same for 1000 and 1280 seems to help stability. my chip deosn't seem to like voltage fluctuations. also the difference between the upper and lower voltage seems to be a problem. my phone is stable at -100+ across the board if i dont over clock. for that reason i tend to test things by undervolting from the upper frequencies down, if i go from the low frequencies i will see instability with very little undervolt untill the upper frequencies are also undervolted.

CM7 03182011, Kernel du Jour v4.2
Just UV, with governor set to "conservative"
1000: -100
800: -100
600: -125
400: -125
200: -150
100: -150

Cognition 4.3
Voltage Control App
Stability Test
Neocore
Linpack
Mhz UV Temp. Linpack
1300 -50 (20c/42c) 17.8~
1000 -50
800 -75
400 -100
200 -100
100 -100

Serendipity 6.3
Paragon 6 kernel @ 1344mhz
Linpack = ~18.8
1344 - 0
1000 - 50
800 - 75
400 - 100
200 - 125
100 - 125

I'm liking your numbers... I wonder if having 100 and 200 enabled makes a big difference. Eliminating 1200 and going from 1000 to 4000 seems quite a bit snappier.

Idk. Paragon kernel defaults the states.
jgrnght said:
I'm liking your numbers... I wonder if having 100 and 200 enabled makes a big difference. Eliminating 1200 and going from 1000 to 4000 seems quite a bit snappier.
Click to expand...
Click to collapse

Interesting thread...would be great to see what people are using for different roms..

I can't get 1400 stable, even at stock voltage.... but at 1300 I can get down to -75:
1300 @ -75
1000 @ -100
800 @ -100
600 @ -100
400 @ -100
200 @ -100
100 @ -100
Last time I tried going down to -125 it wasn't stable, but that was on a different kernel... gonna give it a try when I get a chance.

CM7 and The Escapist's kernel with Noop scheduler and 1300mhz limit enabled
1300 -50
1200 -75
1000 -75
800 -100
600 -100
400 -125
200 -125
100 -125

Nice to see everyone posting their numbers.
I'm finding that the UV setting I have are causing the phone to lock up once and a while. I did pass 50 passes of stability test and 30min of neocore. So are those programs really that accurate at testing stability? Is there anything better out there?

Playing Cordy for a bit seems to effectively stress the system, as I can get it to lock quickly even when seeming stable in the synthetic tests.
Cordy spends almost 100% of the time in top frequency state from what I've seen, plus its pounding the GPU.

bnevets27 said:
Nice to see everyone posting their numbers.
I'm finding that the UV setting I have are causing the phone to lock up once and a while. I did pass 50 passes of stability test and 30min of neocore. So are those programs really that accurate at testing stability? Is there anything better out there?
Click to expand...
Click to collapse
I've found that stability test is only accurate on the Mhz it is testing at. What i did was lock my Mhz at 1400, then 1300, then 1200, 1120, 1000, lastly 800. I had to have 5 frequencies ticked to get 800 to even work. I did each level to find the max UV for each level... then used those numbers.
I found having 1000 being my 2nd highest frequency, makes for a much snappier interface. Right now I have 1300, 1000, 800, 400, 200, 100.
Although I was able to use stability test all the way down to 800, I really couldnt test the lower frequencies with it. I found 125 was stable on the lowest 3 while doing benchmarking, however when moving back and forth quickly through settings options, mainly the drop down menus, it would cause it to lock up. So I raised the lower number up to 100 and no longer got crashes in option menus.
Here are the numbers I've settled with and get the quickest overall feel with.
noop scheduler.
1300 -50
1000 -50
800 -75
400 -100
200 -100
100 -100
Cognition 4.3 btw.

Tryng to underclock now. Blah, such a pain!

noop scheduler.
1200 -100
1000 -100
800 -100
400 -100
200 -100
100 -100
On Phoenix Ultimate Special Edition with Onix 2.0.3 kernal

No one else wants to brag?
Anyone aware of (or maybe could make?) an app that can test at each frequency? It would be very helpful to be able to test UV settings for frequencies in the 100-800 range. So far it seems the only "test" is once the phone locks up while navigating thew menus, bump up the voltage to all of the frequencies bellow 800.
(Thanks jgrnght for the suggestion on how to test each frequency 800+)

bnevets27 said:
No one else wants to brag?
Anyone aware of (or maybe could make?) an app that can test at each frequency? It would be very helpful to be able to test UV settings for frequencies in the 100-800 range. So far it seems the only "test" is once the phone locks up while navigating thew menus, bump up the voltage to all of the frequencies bellow 800.
(Thanks jgrnght for the suggestion on how to test each frequency 800+)
Click to expand...
Click to collapse
lol...nothing can beat with hands on experience...you can download cpu spy from the market it will tell you how your cpu stays in every frequency/states you have. From that data you will know which fequency needs more undervolting or tweaks.

Has anyone noticed a definite increase in battery life as a result of undervolting? Common sense points to that it would (less voltage needed, less battery power needed to power it) but does it really translate into solid real life results?
I'm hoping that all this UV business doesn't just give me an extra 15 minutes or something and that it actually translates into an hour or 2.
I got on CM7 TheEscapist's kernel:
1000: -125
800: -125
600: -125
400: -125
200: -150
100: -150
Scheduler: noop
Governor: Conservative

[Q] SetCPU vs. Voltage Control, and what are some recommended settings?

My understanding is most people prefer Voltage Control, but SetCPU allows for specific under/overclocking profiles that can increase performance without killing battery life.
If someone could direct me to popular, trusted settings, I'd appreciate it. I'm not a heavy user or power user, so I'm looking for something that just works well. I don't care about benchmarks and things of that nature.
I'm sure this has been discussed, but I was unable to find posts that didn't concern user-specific issues.
Thanks,
Wyatt
EDIT: 53 views and no replies. I guess I'll experiment for myself. Wish me luck!

gnarlynewport said:
EDIT: 53 views and no replies. I guess I'll experiment for myself. Wish me luck!
Click to expand...
Click to collapse
That's really all it comes down too...experimenting and finding out what works best on YOUR phone with YOUR configuration...
GOOD LUCK!
ps... have been very stable with OC'd to 1.4
-25 down too 200
-100 on 100
bfq and conservative

I use VControl myself...i like the UI.
For Performance: 100-1.4GHZ (1.5 works too, but is WAY overvolted, and 1.6 is extremely unstable), -100mV from 100-1000 MHZ, -75 for 1.1-1.4GHZ.
For "Battery Life": (i really don't see a difference...) 100-800 MHZ (anything below 800 is painfully slow), -100mV across the board.
I leave schedulers and governors at their stock settings, the only time I change anything is to set the gov. to Performance on Performance for max Quadrant scores.

kvswim said:
I use VControl myself...i like the UI.
For Performance: 100-1.4GHZ (1.5 works too, but is WAY overvolted, and 1.6 is extremely unstable), -100mV from 100-1000 MHZ, -75 for 1.1-1.4GHZ.
For "Battery Life": (i really don't see a difference...) 100-800 MHZ (anything below 800 is painfully slow), -100mV across the board.
I leave schedulers and governors at their stock settings, the only time I change anything is to set the gov. to Performance on Performance for max Quadrant scores.
Click to expand...
Click to collapse
How many Mhz levels are you selecting? In my experience anything above 5 and it WILL NOT clock up to the higher settings. Maybe thats why you notice no difference in battery life?
For instance if you had say 100, 200, 400, 800, 1000 and 1400 you will reace 1000mhz only
if you had 100, 200, 400, 800, 1400 you would reach the 1400mhz. ive tried many combos and 5 or less was the max it would use (voltage control app, im sure setcpu would most likely be the same)

How many slots does the imnuts kernel support?
Sent from my SCH-I510 using Tapatalk

I started using SetCPU, and I think I prefer it.
Quick question, it seems like rebooting is unnecessary for the changes to take effect, is that true?
Overclocking definitely worked. I got 1853 @ 1200mhz in Quadrant, up from 1600.
Edit: now 2025 @ 1300mhz / 1300mhv
2nd Edit: Late last night, I was using a stability test in one of the apps, but I can't for the life of me remember which app or how I found it. Now I'm using StabilityTest from the market. What's a safe cpu temp for these phones? I'm getting 32 degrees under full load in an air conditioned environment.

gnarlynewport said:
I started using SetCPU, and I think I prefer it.
Quick question, it seems like rebooting is unnecessary for the changes to take effect, is that true?
Overclocking definitely worked. I got 1853 @ 1200mhz in Quadrant, up from 1600.
Edit: now 2025 @ 1300mhz / 1300mhv
2nd Edit: Late last night, I was using a stability test in one of the apps, but I can't for the life of me remember which app or how I found it. Now I'm using StabilityTest from the market. What's a safe cpu temp for these phones? I'm getting 32 degrees under full load in an air conditioned environment.
Click to expand...
Click to collapse
I just switched over to Setcpu as well. It seems to work better for me also. I can now select 6 levels instead of the 5 before in voltage control and I also noticed that the set on boot on voltage control did NOT work but it DOES work in setcpu!! Im happy!

Haven't tried Setcpu yet, but I preferred Pimp my CPU over VC when I was using Miui on the Fascinate.
Sent from my SCH-I510 using XDA App

Can we get some info on clocking/volting this phone?

I'm sure I'm not the only person but changing the clock speed/voltages is pretty damned confusing, voltages specifically. I never saw the point to overclocking(not yet at least, nothing really needs it) but lowering the voltages to save battery life is something I'm really into I just don't get how these voltages work at all.
Could someone post a quick walkthrough on it? I don't need your exact settings since I know it varies from person to person but a guide would be nice. I can change the clock speed, it's pretty simple and I used VControl to modify the speeds to 800mhz in both advanced & general but nothing else. Voltages scare me.

Just play around with it. The worst you can do is freeze the phone, nothing a hold of the power + volume up can't fix.
I recommend starting at -25 across the board and increasing slowly until you get a freeze so you can find the best balance between stability and battery savings for your phone.
Sent from my SCH-I510 using Tapatalk

As long as you don't OVERvolt your phone your hardware will be fine, although this isn't an issue since only VControl Extreme overvolts. Worst case scenario: your phone reboots because it doesn't like you taking away its power juice.
On stock clocks (100-1000 mhz) my phone can do -100 mV, anything above that -50. YMMV however, even "identical" processors have different tastes, ie one will take a beating while another is super fragile.
Sent from my Droid Charge running GummyCharged 2.0

How would this work?
800mhz -50v
600mhz -50v
400mhz -75v
200mhz -75v
Would that save more battery or should I reverse the voltages? I don't get how voltages work exactly, that was my main question

blarrick said:
How would this work?
800mhz -50v
600mhz -50v
400mhz -75v
200mhz -75v
Would that save more battery or should I reverse the voltages? I don't get how voltages work exactly, that was my main question
Click to expand...
Click to collapse
-75 means that it takes 75 mv off of the stock voltage setting. That should work, assuming your processor accepts that much under.
Sent from my Droid Charge running GummyCharged 2.0

kvswim said:
-75 means that it takes 75 mv off of the stock voltage setting. That should work, assuming your processor accepts that much under.
Sent from my Droid Charge running GummyCharged 2.0
Click to expand...
Click to collapse
Yeah everything is running fine, quadrant scores of 900 with ext4 begs to differ.. lol. Will overclocking drain more battery? I'd assume it would only affect battery when I'm using an intensive app like the browser that would actually utilize the higher CPU speed.

blarrick said:
Yeah everything is running fine, quadrant scores of 900 with ext4 begs to differ.. lol. Will overclocking drain more battery? I'd assume it would only affect battery when I'm using an intensive app like the browser that would actually utilize the higher CPU speed.
Click to expand...
Click to collapse
It'll stay at the lower settings until an app demands processing power. You will see a slight battery hit but a performance increase.
EDIT: I got 1224 @ 800 mhz.
EDIT: 2100 @1400 mhz. So you can see the performance changes drastically.
Sent from my Droid Charge running GummyCharged 2.0

When on froyo I run this
-25 1200
-50 1000
-50 800
-50 400
-75 200
-75 100

kejar31 said:
When on froyo I run this
-25 1200
-50 1000
-50 800
-50 400
-75 200
-75 100
Click to expand...
Click to collapse
Appreciate all the answers but this was what I really needed, I wasn't sure if I needed to increase or decrease the voltage as the clock speed changed.
Still, thanks to everyone for the information.

1300 - 0 conservative
1000-25
800 - 50
400 - 75
200 -100
100 - 125
Still experimenting. Next charge I will try another governor. Also might try dropping the voltage more on 400 and 800 steps.
Sent from my SCH-I510 using XDA App

PeterGunz said:
1300 - 0 conservative
1000-25
800 - 50
400 - 75
200 -100
100 - 125
Still experimenting. Next charge I will try another governor. Also might try dropping the voltage more on 400 and 800 steps.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
That's some mega voltage drops for 200-100mhz! I'm assuming that would just save some battery life when your phone is idle because I can't imagine any app only using 100mhz.

I am trying -75 mV across the board on stock voltages. No issues so far. Is there any reason to bump the higher speeds up in voltages? Ran a quadrant and I'm still scoring the same as before undervolting.

quantim0 said:
I am trying -75 mV across the board on stock voltages. No issues so far. Is there any reason to bump the higher speeds up in voltages? Ran a quadrant and I'm still scoring the same as before undervolting.
Click to expand...
Click to collapse
Voltages have nothing to do with performance. It's all about clockspeed.
Sent from my Droid Charge running GummyCharged 2.0

blarrick said:
That's some mega voltage drops for 200-100mhz! I'm assuming that would just save some battery life when your phone is idle because I can't imagine any app only using 100mhz.
Click to expand...
Click to collapse
I am not 100% sure, but I think the bottom steps are similar to PBJ. The only downside I used to get with UV the fascinate that low was that it would either not wake up from sleep sometimes, or calls and texts wouldn't come through unless/until the phone was woken up. Phone doesn't use much power when sleeping, but it is difficult to curb with 4G on.
This phone, in my experience thus far compared to the fascinate, can be OC'd way higher for me and be stable, and can also be undervolted across the board more successfully.
Governors I know nothing about, but have been doing some reading. Still not 100% what each one does. I usually don't OC, but it has been outstanding on this phone thus far.

I use noop and ondemand.
1400 -75
1200 -25
1000 -50
800 -50
400 -50
200 -75
100 -75

hazard209 said:
I use noop and ondemand.
1400 -75
1200 -25
1000 -50
800 -50
400 -50
200 -75
100 -75
Click to expand...
Click to collapse
I literally have no clue what noop/ondemand do, I just left it to ondemand.

hazard209 said:
I use noop and ondemand.
1400 -75
1200 -25
1000 -50
800 -50
400 -50
200 -75
100 -75
Click to expand...
Click to collapse
why didn't you use 1400 1200 1000 800 600 400 200? it looks prettier lol

blarrick said:
I literally have no clue what noop/ondemand do, I just left it to ondemand.
Click to expand...
Click to collapse
noop is the IO scheduler and ondemand is the governor. Imoseyon did some tweaking to ondemand, so that's why I use that versus other governors. I find that noop is more stable for me.
maurogg84 said:
why didn't you use 1400 1200 1000 800 600 400 200? it looks prettier lol
Click to expand...
Click to collapse
It's about stability and what the phone requires of it's resources. Lol. Not OCD perfection.

Can you change the IO scheduler on set CPU? I know you can on voltage control.
Sent from my SCH-I510 using XDA App

kejar31 said:
When on froyo I run this
-25 1200
-50 1000
-50 800
-50 400
-75 200
-75 100
Click to expand...
Click to collapse
^^this but I add the 1400 step at -25 as well... my phone doesn't like being undervolted past -25 on any step above 1000

[Q] Recommended undervolt settings (Clemsyn-blades)

I tried to search but was unsuccessful to find the information that I wanted.
Can someone tell me what are the recommended safe undervolt settings for the transformer?
I'm running prime 1.9 with clemsyn-blades 1.6a.
Thx
Sent from my Transformer TF101 using Tapatalk

steve.garon said:
I tried to search but was unsuccessful to find the information that I wanted.
Can someone tell me what are the recommended safe undervolt settings for the transformer?
I'm running prime 1.9 with clemsyn-blades 1.6a.
Thx
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.

Bjd223 said:
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Click to expand...
Click to collapse
Cool. I'll give this a try.
Sent from my Nexus S using Tapatalk

I get a stable undervolt at -50 on all cpu steps which is pretty good. This should save loads of battery.
Sent from my Nexus S using Tapatalk

steve.garon said:
I get a stable undervolt at -50 on all cpu steps which is pretty good. This should save loads of battery.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I started at the top and went down every stepping from 1624 to 1000 and found out the lowest stable frequency and then added 10 to be safe to each one. I am currently at
1624 (-70)
1592 (-80)
1544 (-180)
1472 (-80)
1424 (-160)
1336 (-185)
1232 (-185)
1000 (- 110) which is 990 mV
I then set every stepping under 1 GHz frequency that was above 990 mV to 990 mV as if it can run at 1 GHz at that voltage then any speed under that will run fine at that voltage also. I have some more stability testing to do but I think I got it pretty much nailed down for my device. I may go through all the sub 1 GHz frequencies but it does take some time to run a stress test under each stepping.
Also I have never had any sleep issues but that is something to look out for. I also wonder how temperature affects stability as I have never gotten it above 40c. The pad might benefit from a 1 or 2mm thermal pad squeezed between the CPU and the back bezel (if it will fit).
Does anyone know that tjunction max for a Tegra2? I have a profile set up in SetCPU that sets the CPU frequency at 1 GHz if the CPU gets above 42 because I saw something similar in the Clemsyn rom but don't really know when the CPU will start to throttle itself at or shut off.
I am trying to find stock voltages for different devices because it seems like some mfgs are undervolting to save battery on some tablets.

Bjd223 said:
I started at the top and went down every stepping from 1624 to 1000 and found out the lowest stable frequency and then added 10 to be safe to each one. I am currently at
1624 (-70)
1592 (-80)
1544 (-180)
1472 (-80)
1424 (-160)
1336 (-185)
1232 (-185)
1000 (- 110) which is 990 mV
I then set every stepping under 1 GHz frequency that was above 990 mV to 990 mV as if it can run at 1 GHz at that voltage then any speed under that will run fine at that voltage also. I have some more stability testing to do but I think I got it pretty much nailed down for my device. I may go through all the sub 1 GHz frequencies but it does take some time to run a stress test under each stepping.
Also I have never had any sleep issues but that is something to look out for. I also wonder how temperature affects stability as I have never gotten it above 40c. The pad might benefit from a 1 or 2mm thermal pad squeezed between the CPU and the back bezel (if it will fit).
Does anyone know that tjunction max for a Tegra2? I have a profile set up in SetCPU that sets the CPU frequency at 1 GHz if the CPU gets above 42 because I saw something similar in the Clemsyn rom but don't really know when the CPU will start to throttle itself at or shut off.
I am trying to find stock voltages for different devices because it seems like some mfgs are undervolting to save battery on some tablets.
Click to expand...
Click to collapse
-180 in some frequencies!! Thats just insane. I've got to try this.
FYI, you don't have to lower voltage for all upper 1ghz frequencies. If your running at 1544 for exemple. The cpu will never touch the frequencies between 1000 and 1544. After the 1000 its a direct step to whatever frequency your overclocking too. You can monitor this in setcpu.
I cannot undervolt as precise as you can. For some reason setcpu only let me do 25mv increment...
Sent from my Nexus S using Tapatalk

I have undervolted by -175 on all frequencies, obviously 216Mhz is locked but all seems pretty stable after some testing. No sleep death either so I'm going to carry on testing.

steve.garon said:
-180 in some frequencies!! Thats just insane. I've got to try this.
FYI, you don't have to lower voltage for all upper 1ghz frequencies. If your running at 1544 for exemple. The cpu will never touch the frequencies between 1000 and 1544. After the 1000 its a direct step to whatever frequency your overclocking too. You can monitor this in setcpu.
I cannot undervolt as precise as you can. For some reason setcpu only let me do 25mv increment...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
In SetCPU do not use the slider use the keyboard and type in the exact number you want.
I wanted to figure out every stepping in case I wanted to switch to a lower frequency but yeah most poeple don't have to do this.
The lowest stable I have gotten is -190 but feel like adding 10 padding will ensure stability.
I will probably do the sub 1 GHz frequencies today or tomorrow.

Bjd223 said:
In SetCPU do not use the slider use the keyboard and type in the exact number you want.
I wanted to figure out every stepping in case I wanted to switch to a lower frequency but yeah most poeple don't have to do this.
The lowest stable I have gotten is -190 but feel like adding 10 padding will ensure stability.
I will probably do the sub 1 GHz frequencies today or tomorrow.
Click to expand...
Click to collapse
I didnt even noticed I could use the keyboard...
I finally settled to -25 @216, -50 under 612 and -100 over 612. And everything is stable
Sent from my Nexus S using Tapatalk

I have tested each voltage. I am under the impression that 725 mV is the kernel minimum in the Clemsyn kernel so once I hit that I just set every frequency under that too 725. I will eventually go through and stress test every frequency @ 725 to make sure everything is a-okay but I am sure it is.
Here is my list incase anyone wants a place to start.
1680 MHz (-000) I can not overclock to this freuqency.
1624 MHz (-070) 1380 mV
1592 MHz (-080) 1345 mV
1544 MHz (-180) 1220 mV
1472 MHz (-080) 1220 mV
1424 MHz (-160) 1115 mV
1336 MHz (-185) 1065 mV
1232 MHz (-185) 990 mV
1000 MHz (-215) 885 mV
0912 MHz (-215) 835 mV
0816 MHz (-235) 790 mV
0760 MHz (-215) 760 mV
0608 MHz (-225) 725 mV
0456 MHz (-100) 725 mV
0312 MHz (-075) 725 mV
0216 MHz (-025) 725 mV
Clemsyn said the minimum mV in his kernel but I can't seem to find the thread, but I think it was 725. If I find out it is something lower I will go through the lower ones until I hit the minimum.
Also please note that everything above 1 GHz has +10 mV padding added to it above the lowest stable I could find. Everything below 1 GHz only has a +5 mV padding on it. So for example I actually hit a -240 w/o any issues @ 816 MHz.
I tested in +/-5 mV increments but if you wanted you could narrow it down even further.
EDIT: Also after some testing it looks like it does use frequencies between 1 GHz and your max. I have it set to 1644 and it does hit 1232 MHz occasionally.

Bjd223 said:
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Click to expand...
Click to collapse
Thanks for this mate. I followed your guide exactly and I'm using clems 16? Kernel completely stable at all frequencies including the undervolting!

Based on my testing you need ~ a +15 to +25 mV over stable CPU voltage to get stable 3D GPU.
I found that I could run hours of "Stress CPU" without any issues at a voltage but during stressful 3D games that are using CPU + GPU cores, at that same frequency, the machine would FC the app, reboot or lock. I have also noticed that the closer you are to the stable voltage different things will happen.
Far off - machine will usually reboot
Closer - machine will usually hard lock
Even closer - Apps will FC, widgets will act strange (like invert colors, black blocks for backgrounds, etc.)
So what I do now is I test with Dungeon Defenders at the main menu. Its seems that if you can last 1 hr at the Dungeon Defenders menu you are GTG. If you actually play the game then 1 stage is what I use to test.

Bjd223 said:
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Click to expand...
Click to collapse
I always wanted to learn more about the mV and CPU speed stuff. I always install rom, install kernel of the one I heard the better is and that's it. Never had touched the voltage measure in any of my android device. Yeah i know, so noob.
Thanks for this how to info, I think I will play around a bit later. Right now I'm struggling with my self on wish of the 3 roms available install and stay.

Had to remove undervolt this weekend since my camera wouldnt start anymore. I'll have to redo all the tests I was doing but test for camera too. The tablet would just freeze as soon as I opened the camera app
Sent from my Nexus S using Tapatalk

steve.garon said:
Had to remove undervolt this weekend since my camera wouldnt start anymore. I'll have to redo all the tests I was doing but test for camera too. The tablet would just freeze as soon as I opened the camera app
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
My camera does not work either. I just figured it was Clemsyns kernel not the OC. I don't know anything about cameras but maybe they use a lot of voltage so the voltage to the CPU dips.
I never used the camera personally, but I will test it some and see what additional mV you need over stable to get the camera working.
Also I noticed the more you undervolt (it seems to me) the harder it is to undock with an app open. usually instead of reloading they FC or lock the device so i just make sure to hit the home key before I undock then alt tab right back into the app.

Bjd223 said:
My camera does not work either. I just figured it was Clemsyns kernel not the OC. I don't know anything about cameras but maybe they use a lot of voltage so the voltage to the CPU dips.
I never used the camera personally, but I will test it some and see what additional mV you need over stable to get the camera working.
Also I noticed the more you undervolt (it seems to me) the harder it is to undock with an app open. usually instead of reloading they FC or lock the device so i just make sure to hit the home key before I undock then alt tab right back into the app.
Click to expand...
Click to collapse
My camera did not work at 912 MHz at stock voltage on 17b but now on 18 I can do my normal undervolt settings and the camera works fine.

[Q] [I9020a] Undervolting 100MHz frequency

Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 13 on a I9020a.
I'm playing around with undervolting the cpu and trying to find the minimum stable voltages. My procedure is to start the voltage as low as the voltage for the frequency step before it and then increase the voltage in 25mV steps until everything is stable. I am using SetCPU to adjust the voltages.
So far this has worked for every frequency step except for the 100MHz step. I can't seem to find the lowest voltage for 100MHz. For example, the 200MHz step will be unstable at 750mV but is stable at 775mV. The 100MHz step is never unstable no matter how low I set the voltage. I can even set it to 0mV (which I know is ridiculous) and it wont freeze.
Does anyone know why the phone doesn't become unstable at ridiculously low voltages for the 100MHz step? I see that the slider to adjust voltages in SetCPU only goes down to 600mV but I can manually type in lower voltage values. Is there some kind of hard-set voltage minimum for the cpu that even SetCPU can't bypass when setting the voltage? Is the phone violating the laws of physics?
Thanks in advance

What's your min frequency in setcpu?

Oh yeah, I should have posted that.
100MHz min
1000MHz max
lazy scaling

i heard that ...
force phone running in low mV MAY damage the CPU and other parts of it and destablize it...
=================================
i have seen some applications that would ignore your input value when it is not logical ...
for example like NS tools , one of them , i don't remember which exactly , perhaps it's live OC, for live OC, if you set value lower then 100 , it would automatically set back to 100 ... i think this may be same as your min frequency case...

nathanson666 said:
Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 13 on a I9020a.
I'm playing around with undervolting the cpu and trying to find the minimum stable voltages. My procedure is to start the voltage as low as the voltage for the frequency step before it and then increase the voltage in 25mV steps until everything is stable. I am using SetCPU to adjust the voltages.
So far this has worked for every frequency step except for the 100MHz step. I can't seem to find the lowest voltage for 100MHz. For example, the 200MHz step will be unstable at 750mV but is stable at 775mV. The 100MHz step is never unstable no matter how low I set the voltage. I can even set it to 0mV (which I know is ridiculous) and it wont freeze.
Does anyone know why the phone doesn't become unstable at ridiculously low voltages for the 100MHz step? I see that the slider to adjust voltages in SetCPU only goes down to 600mV but I can manually type in lower voltage values. Is there some kind of hard-set voltage minimum for the cpu that even SetCPU can't bypass when setting the voltage? Is the phone violating the laws of physics?
Thanks in advance
Click to expand...
Click to collapse
The method you are using is wrong. I did the same thing a few days ago, and changing the values like that won't work.
What I found out is that to easily find stable values, in SetCPU put your max as 200MHz and your min at 100MHz. Use ondemand. Keep 200MHz at stock volts and 100MHz try an undervolt.
Apply everything then slide the minimum frequency slider around a bit. I guarantee you 600mv will freeze. Do the same for each value, if testing 200MHz, use 400MHz as your max and 200MHz as your min, stock volts for 400MHz. Slide the minimum frequency left and right.
Sounds weird, but it works. Do this until you find a voltage for each frequency. Then put your frequency max and frequency min at the same value (IE 200MHz) and launch a game or a demanding app and play for a lil while, even if performance suck. Hope it doesn't freeze on you, but if it does, bump the voltage a bit.
If you want good starting values, here's the values I have found that work for me and are 100% stable. No force close over the last few days since I started using those:
100MHz 875mv (75mv under stock)
200MHz 875mv (75mv under stock)
400MHz 900mv (150mv under stock)
800MHz 1125mv (75mv under stock)
1000MHz 1225mv (25mv under stock)