So I'm not sure if this 4th G2x I received is a total beast or SetCPU is just f'ing with me, but I'm cruising at -200mV on top of the already undervolted Faux CM7 kernel.
The phone has absolutely no problems and it just keeps going.
Here's my setup:
1000Mhz Max 950 mV Current 925 mV (-25 mV)
800Mhz Max 850 mV Current 750 mV (-100 mV)
500Mhz Max 800 mV Current 650 mV (-150 mV)
400Mhz Max 770 mV Current 570 mV (-200 mV)
PS: Real men type it out
Edit: Poll added!
GideonX said:
So I'm not sure if this 4th G2x I received is a total beast or SetCPU is just f'ing with me, but I'm cruising at -200mV on top of the already undervolted Faux CM7 kernel.
The phone has absolutely no problems and it just keeps going.
Here's my setup:
1000Mhz Max 950 mV Current 925 mV (-25 mV)
800Mhz Max 850 mV Current 750 mV (-100 mV)
500Mhz Max 800 mV Current 650 mV (-150 mV)
400Mhz Max 770 mV Current 570 mV (-200 mV)
PS: Real men type it out
Click to expand...
Click to collapse
i really wonder sometimes if its really UVing with values so high x_X 216 running at 350mV x_X
{
"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 read in another thread by one of the developers (Faux?) that 770 mV is the lowest allowed voltage due to hardware restrictions and that any settings below that do nothing.
GideonX said:
So I'm not sure if this 4th G2x I received is a total beast or SetCPU is just f'ing with me, but I'm cruising at -200mV on top of the already undervolted Faux CM7 kernel.
The phone has absolutely no problems and it just keeps going.
Here's my setup:
1000Mhz Max 950 mV Current 925 mV (-25 mV)
800Mhz Max 850 mV Current 750 mV (-100 mV)
500Mhz Max 800 mV Current 650 mV (-150 mV)
400Mhz Max 770 mV Current 570 mV (-200 mV)
PS: Real men type it out
Click to expand...
Click to collapse
sincest said:
i really wonder sometimes if its really UVing with values so high x_X 216 running at 350mV x_X
Click to expand...
Click to collapse
You guys have amazing chips
The reason for 770mv @ 389/400 MHz is the limitation of ~100mv per "frequency jump" according to Tegra2 documentation. With the FakeShmoo implementation of overclock, we have a total of 8 slots (frequencies) to play with. If I start the lowest frequency let say at 500mv, then the max voltage at the eighth slot can only be ~1200mv. With 1200mv we can OC to 1.2~1.3 GHz, beyond that then it becomes unstable. So in order to get more juice @ higher clocks, we have to start a higher voltage at the low to get more juice at the high end. Of course, naturally, the next question would be why not start with 1000mv to begin with then you can get 1700mv at eighth slot? If we started with more juice at the low end, it would kill the battery 2x or 3x faster. So the current voltage table you see from my kernels is a compromise between battery life and OC Hope this clears it up a bit.
faux123 said:
You guys have amazing chips
The reason for 770mv @ 389/400 MHz is the limitation of ~100mv per "frequency jump" according to Tegra2 documentation. With the FakeShmoo implementation of overclock, we have a total of 8 slots (frequencies) to play with. If I start the lowest frequency let say at 500mv, then the max voltage at the eighth slot can only be ~1200mv. With 1200mv we can OC to 1.2~1.3 GHz, beyond that then it becomes unstable. So in order to get more juice @ higher clocks, we have to start a higher voltage at the low to get more juice at the high end. Of course, naturally, the next question would be why not start with 1000mv to begin with then you can get 1700mv at eighth slot? If we started with more juice at the low end, it would kill the battery 2x or 3x faster. So the current voltage table you see from my kernels is a compromise between battery life and OC Hope this clears it up a bit.
Click to expand...
Click to collapse
So there really isn't a hardware limit in place on how low this chip can go?
Sent from my HTC Vision (G2x in disguise)
I'm really starting to wonder if setcpu is busting our chops or not I'm
-100mV on all frequencies starting at 594mhz down to 216mhz on morfics jrcu 6/21 kernel, that can't be right can it is there a way to find out for sure???
for frequency 500mhz or 400mhz I can as low as I want ... 10mVs.. even 0mV. so i dont tihnk its accurate
c19932 said:
for frequency 500mhz or 400mhz I can as low as I want ... 10mVs.. even 0mV. so i dont tihnk its accurate
Click to expand...
Click to collapse
do you have any more than 100mV between frequencies?
Black6spdZ said:
do you have any more than 100mV between frequencies?
Click to expand...
Click to collapse
yes I do. should I not exceed 100mV between each frequency level then? would you happen to know the exact biggest voltage difference allowed between each level?
on another note, if I just leave them at 10mV, will that mean the processor will automatically take the voltage down to the lowest possible, or will it just do nothing but run at stock voltage?
c19932 said:
for frequency 500mhz or 400mhz I can as low as I want ... 10mVs.. even 0mV. so i dont tihnk its accurate
Click to expand...
Click to collapse
Yes, it seems possible to make settings that are not logically possible.
It would be nice if either SetCPU (which I am currently using) or Pimp My CPU would display in either real time or histogram what voltages are actually being used in the same way as they show frequency. Although I suspect this may be impossible due to hardware or this would be already implemented.
Added a poll up top.
I made it so you can vote either above or below -50mV. I'm basing this off the OC/UV kernel from Faux123.
I also skipped everything between 1.0 to 1.5Ghz. I'm going to assume at that speed, UV'ing will be very low.
double post
i actually use 1216max and uv it minus 150 all together so fauxs -50 plus i uv it -100, and my phone still flys and battery life is niceeee, oh and for the min i use 389, -200 on top of fauxs -50 so -250 all together
I am OC/UV up to 1200MHz -75mV on all frequencies below the undervolting built into Trinity JRCU kernel. This is stable and further UV gives me trouble. Your assumption about UV at higher frequencies is appears to be incorrect.
The poll actually confuses me, undervolting > -50 could mean I am not undervolting at all since 0 is greater than -50.
Interesting, I can UV more on the lower Mhz than higher. For example, at 1.0Ghz -50mV is already pushing it. Anything higher and I'll notice FC and random closes on certain apps.
First time polling, I guess there's no edit feature to change up the wording. Sigh.
SetCPU doesn't error check so everyone reporting -150mV and greater probably is incorrect. Remember there is only 800mV allowable from the highest frequency and only 100mV allowable between frequencies. So.. take my phone for instance.. I started at the highest 1.5Ghz frequency and tested -25mV at a time until phone rebooted and then went back up 25mV. This just happens to be 1300mV stable for me. This means the lowest 389Mhz can have at the lowest 500mV "1300mV - 800mV". I set everything -50mV across the board and then focused on 503Mhz since no matter what 389Mhz can only be -100mV lower. I was able to get -75Mv "725mV" stable. Then I was able to run 389Mhz stable at -150mV or 620mV. In actuality it is running 625mV since that is 100mV less than the frequency above it... setting it any lower in SetCPU would STILL only be 625mV regardless.
Also, this poll will be useless for everything but the 1500Mhz frequency as we wouldn't know if the user started with the SV or UV kernel. We need multiple polls with the final voltage eg 1100Mhz @ 1000mV,975mV,950mV
Test with a charger plugged in, I've had reboots with a battery at <50% because it cannot supply the high current draw of 100% cpu usage.
My specific settings are as follows as -?? means nothing because different kernels have a different starting point.
1075 mV @ 1200 MHz
975 mV @ 1100 MHz
875 mV @ 1000 MHz
775 mV @ 594 MHz
675 mV @ 432 MHz
575 mV @ 216 MHz
This is solidly stable having run it for several days without any bad behavior although any further reduction of voltage at 1200 MHz causes significant problems.
Phone: G2X
ROM: CyanogenMod 7.1 RC1
Kernel: Trinity 15 jrcu 06212011
Other relevant: SetCPU
I've gotten even better results with the SV kernel. After testing each speed for stability at lower and lower voltages here are my results:
1408Mhz @ 1175mV
1216Mhz @ 1075mV
1100Mhz @ 975mV
1015Mhz @ 900mV
816Mhz @ 800mV
655Mhz @ 725mV
503Mhz @ 650mV
389Mhz @ 595mV
lose 100Mhz from the UV/OC kernel but I get better UV settings with the SV kernel
Black6spdZ said:
I've gotten even better results with the SV kernel. After testing each speed for stability at lower and lower voltages here are my results:
1408Mhz @ 1175mV
1216Mhz @ 1075mV
1100Mhz @ 975mV
1015Mhz @ 900mV
816Mhz @ 800mV
655Mhz @ 725mV
503Mhz @ 650mV
389Mhz @ 595mV
lose 100Mhz from the UV/OC kernel but I get better UV settings with the SV kernel
Click to expand...
Click to collapse
too bad the lowest my phone can go for 1015mhz and 816mhz are 940 and 840mv respectively
Black6spdZ said:
I've gotten even better results with the SV kernel. After testing each speed for stability at lower and lower voltages here are my results:
1408Mhz @ 1175mV
1216Mhz @ 1075mV
1100Mhz @ 975mV
1015Mhz @ 900mV
816Mhz @ 800mV
655Mhz @ 725mV
503Mhz @ 650mV
389Mhz @ 595mV
lose 100Mhz from the UV/OC kernel but I get better UV settings with the SV kernel
Click to expand...
Click to collapse
We seem to be hitting about the same spot, almost exactly, I can OC to 1400 or 1500 but choose not to push my phone to that extent. I live in a very hot area and don't want to tempt fate.
Related
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
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
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.
I've asked the mods to close my other thread.
What I'll do in this thread is to test kernels and see which will be the best and or the most reliable undervolting parameters.
I know that each CPU/GPU are different, it will be only a reference for what can be done. I'll run extensive tests, stress test and real life test on the Nexus 7 device 32GB.
I'll reserve a couple of post areas because i want it to be a permanant thread and i put my device at risk for you my firends anyway it is not really an issue lol
I'll do the testing like that : ( how i'll do it and conditions )
1. I'll write the kernel name and version i am using for the test
2. I'll post the screenshots of the settings and/or a raw text of the settings for the specific kernel.
3. Trickstermod will be used for tweaking
4. Quadrant test for people who live for it
The conditions for the undervolt pass the test are the following
1. Running glowball for 30 minutes without crashing
2. Running Stability test 2.5 for 30 minutes. ( RUNNING EACH OF THE TESTS FOR 30 MINUTES C-A-D CLASSIC/CPU+GPU/SCALING TEST ) all in userspace mode.
Those settings will be the lower voltage achievable for me. You can use it as a reference but I cannot guarantee it will work for your device.. What I can suggest is using the boot delay option from the trickstermod menu. If we see that some settings are reliable for a lot of people, it would be nice to have help from some coders to write an init.d script with those settings. or just sharing other experiences. This is not a thread where I have the ultimate knowledge, but a thread who everybody can share their experiences, settings and so on to achieve the ultimate goal of performance and very low power consuption and battery life.
Those test will be time consuming but it is ok.
I do not expect any form of donation for that
If it helped you a little bit, you can just hit the help button and it will be my payday =)
Thank you very much
PS : For people giving 1 Star to the thread before I ever post the first undervolting settings, well, I do not know what to say. For the others who already tried the differents settings I,ll post day to day, feel free to post comments and rate the thread. You can even rate it 1 star if you want because you tried it. But for people who gave negatives reviews even if i didn't post any settings, please get a life.
December 4th 2012 6:06PM 1st stable aggressive undervolting
December 4th 2012, 6:06PM
ROM: Scott's CleanRom 3.0
Kernel : 3.1.10-franco.Kernel [email protected] #30
Stability issues : No
CPU frequencies settings : [email protected] Mhz
Governor : On Demand
I/O scheduler : Deadline
Read Ahead buffer : 2048
GPU Max frequency : 526
CPUQuiet Power Management : balanced
VOLTAGE SETTINGS : MPU
1300 Mhz @ 975 mv
1200 Mhz @ 950 mv
1100 Mhz @ 925 mv
1000 Mhz @ 900 mv
900 Mhz @ 875 mv
800 Mhz @ 850 mv
700 Mhz @ 825 mv
600 Mhz @ 800 mv
500 Mhz @ 775 mv
400 Mhz @ 750 mv
300 Mhz @ 725 mv
200 Mhz @ 700 mv
100 Mhz @ 675 mv
Notes for this undervolting
CPU stable at 975 mv for 1300 Mhz. Tried 970 mv with -5 incremental for other frequencies but the device just crashed. reverted back +5mv for all frequencies and run a second test and it was 100% stable.
The stock CPU voltage settings is 1175mv for 1300 Mhz and so on by 5mv incremental. We are able to achieve performance and stability with a global undervoltage of 200 mv. Actually this is a lot. What happened with the battery life ? Almost 8 hours gain vs the stock settings. This is a lot considering there is no drop with performances.
Edit : Just made other extensive testing. Played deadzone, dead trigger and gta 3 without any glitches. They run smoothly without freezes. We could assume this config is quite stable.
Next step would be undervolting bus and memory while trying keeping those voltages for the cpu. Ill need help to achieve that because i am not a big coder.
Ongoing testing ( may not be stable ) Dec 5 2012
ROM: Scott's CleanRom 3.0
Kernel : 3.1.10-franco.Kernel [email protected] #30
VOLTAGE SETTINGS : MPU
1300 Mhz @ 975 mv
1200 Mhz @ 950 mv
1100 Mhz @ 925 mv
1000 Mhz @ 900 mv
900 Mhz @ 875 mv
800 Mhz @ 850 mv
700 Mhz @ 825 mv
600 Mhz @ 800 mv
500 Mhz @ 775 mv
400 Mhz @ 710 mv
300 Mhz @ 640 mv
200 Mhz @ 635 mv
100 Mhz @ 625 mv
With on-demand, the tablet crash.
With interactive and other governors other than on-demand, seems working fine. Needs more testing
Reserved 3
Reserved 3
http://forum.xda-developers.com/showthread.php?t=2009702
He uses my voltage settings as his new kernel base I think. I must verify with him.
Sparksco use 1600 mhz with a ultra low voltage of 1100 mV.
Expect great battery life with his Rom and kernel
Reserved 4
Reserved 4
Reserved 5
Reserved 5
Good job, keep it up Mr. jsmasterx :good:
jsmasterx said:
December 4th 2012, 6:06PM
ROM: Scott's CleanRom 3.0
Kernel : 3.1.10-franco.Kernel [email protected] #30
Stability issues : No
CPU frequencies settings : [email protected] Mhz
Governor : On Demand
I/O scheduler : Deadline
Read Ahead buffer : 2048
GPU Max frequency : 526
CPUQuiet Power Management : balanced
VOLTAGE SETTINGS : MPU
1300 Mhz @ 975 mv
1200 Mhz @ 950 mv
1100 Mhz @ 925 mv
1000 Mhz @ 900 mv
900 Mhz @ 875 mv
800 Mhz @ 850 mv
700 Mhz @ 825 mv
600 Mhz @ 800 mv
500 Mhz @ 775 mv
400 Mhz @ 750 mv
300 Mhz @ 725 mv
200 Mhz @ 700 mv
100 Mhz @ 675 mv
Notes for this undervolting
CPU stable at 975 mv for 1300 Mhz. Tried 970 mv with -5 incremental for other frequencies but the device just crashed. reverted back +5mv for all frequencies and run a second test and it was 100% stable.
The stock CPU voltage settings is 1175mv for 1300 Mhz and so on by 5mv incremental. We are able to achieve performance and stability with a global undervoltage of 200 mv. Actually this is a lot. What happened with the battery life ? Almost 8 hours gain vs the stock settings. This is a lot considering there is no drop with performances.
Edit : Just made other extensive testing. Played deadzone, dead trigger and gta 3 without any glitches. They run smoothly without freezes. We could assume this config is quite stable.
Next step would be undervolting bus and memory while trying keeping those voltages for the cpu. Ill need help to achieve that because i am not a big coder.
Click to expand...
Click to collapse
how is the performance is it good because i have a lot of lag when i pull down the notification bar
sharjackmission said:
how is the performance is it good because i have a lot of lag when i pull down the notification bar
Click to expand...
Click to collapse
Undervolting should not impact the performance of the CPU.
What you can do is taking a look at the numbers and raise voltage a little. But it might be a lot of reasons why it is laggy. Possibly the governor ?
Other people tried the same settings without issues. But raisong the voltage a little wont drain the battery a lot as the number I gave are agressively low.
Cheers
Running on these settings and everything running smoothly. Thanks for the thread.
Sent from my Nexus 7 using Tapatalk 2
Running stock 4.2.1 with MKernel A19 & TRINITY... These voltages seem to be alright.
I am also using interactive and the deadline scheduler.
All is smooth so far... I'll report back if I run into any trouble.
UPDATE - Had to revert. Started getting freezes and crashes.
Trinity kernel's stock voltages seem to play nicely... Anything less is glitchy.
monsieurtalbot said:
Running stock 4.2.1 with MKernel A19 & TRINITY... These voltages seem to be alright.
I am also using interactive and the deadline scheduler.
All is smooth so far... I'll report back if I run into any trouble.
UPDATE - Had to revert. Started getting freezes and crashes.
Trinity kernel's stock voltages seem to play nicely... Anything less is glitchy.
Click to expand...
Click to collapse
For underclocking aaggressively for now I only recommand Franco Kernel. All other kernels Causes stability problems with the same voltages.
Ill let you know soon with that developpement.
Can't wait for m kernel optimizations
krazeecracker said:
Can't wait for m kernel optimizations
Click to expand...
Click to collapse
As soon as they realease the next version I'll test it.
For now the only thing it does is freezing the tablet.
The best undervolting I was able to achieve for now was with Franco Kernel because of the way the kernel is setting up. M-kernel and other boost Bus and memory speed that causes crashes with agressive undervolting.
Doing so, the performance gain is minimal and the battery life truly suffer at the end.
You can get except a few more FPS in certain games but not really noticeable.
jsmasterx said:
As soon as they realease the next version I'll test it.
For now the only thing it does is freezing the tablet.
The best undervolting I was able to achieve for now was with Franco Kernel because of the way the kernel is setting up. M-kernel and other boost Bus and memory speed that causes crashes with agressive undervolting.
Doing so, the performance gain is minimal and the battery life truly suffer at the end.
You can get except a few more FPS in certain games but not really noticeable.
Click to expand...
Click to collapse
No rush man, your work is amazing.
jsmasterx said:
As soon as they realease the next version I'll test it.
For now the only thing it does is freezing the tablet.
The best undervolting I was able to achieve for now was with Franco Kernel because of the way the kernel is setting up. M-kernel and other boost Bus and memory speed that causes crashes with agressive undervolting.
Doing so, the performance gain is minimal and the battery life truly suffer at the end.
You can get except a few more FPS in certain games but not really noticeable.
Click to expand...
Click to collapse
100% of everything you said in that post is untrue. Please make sure the information you pull out of thin air is correct before stating them as fact.
Also voltage tolerance at a certain frequency is device dependent. Not kernel dependent. No amount of circumstantial evidence will change the laws of physics.
One more thing, your frequency table in the first post is wrong. The A9 G core DVFS table does not go below 480MHz. Franco's table is wrong and as a result so is yours.
This thread looks interesting. If you'd like you can test my kernel attached to THIS post as a flashable zip.
:beer:
sparksco said:
This thread looks interesting. If you'd like you can test my kernel attached to THIS post as a flashable zip.
:beer:
Click to expand...
Click to collapse
I will. What would you like me to do after ?
Sent from my Nexus 7 using xda app-developers app
Metallice said:
100% of everything you said in that post is untrue. Please make sure the information you pull out of thin air is correct before stating them as fact.
Also voltage tolerance at a certain frequency is device dependent. Not kernel dependent. No amount of circumstantial evidence will change the laws of physics.
One more thing, your frequency table in the first post is wrong. The A9 G core DVFS table does not go below 480MHz. Franco's table is wrong and as a result so is yours.
Click to expand...
Click to collapse
I did not attack your kernel whats so ever i dont know why you are taking it personal.
As far as i know franco`s table is accurate and the G core can go under 480 mhz. To make sure i what i advance is true i even pluged the N7 to a debug box. My friend who is an analyst programmer certified it also
Sent from my Nexus 7 using xda app-developers app
jsmasterx said:
I will. What would you like me to do after ?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Whatever the goal of this thread is I suppose. It's based on bricked kernel but I modified it a lot so it's not really much like it anymore. To some it up it overclocks to 1.6ghz and has quite a few governors. I'm testing smartassv2 right now but I have a feeling it's not good for battery. I haven't really tested many of the other governors but I've never had any of them lock up on me. Voltage control is also supported. No GPU overclocking though.
Sent from my Nexus 7 using Tapatalk 2
I have recently installed PimpMyROM for my tablet and have found this nice voltage setting feature.
Anyone have any good voltage values for longer lasting battery life without any cases of random reboots?
Best guaranteed to work is really not dialed into your specific tab and user habits.
Setcpu is an excellent app that can help you out with testing. It has a stress test future to make it easy to see if your Undervolt settings are stable.
Google Play claimed it isn't compatible for my tab so I grabbed it off Xda. It works fine. I gotta donate still... (and so should you if you get it here)
Btw: Setcpu has Undervolt settings built in too. You may want to freeze PMR while testing to be sure their settings are not conflicting.
Sent from my SGH-I997 using Xparent Red Tapatalk 2
But as for a starting place...
I have both my daughter's p6210 running smooth with these settings:
1200 MHz 1175 mV
1000 MHz 1050 mV
800 MHz 950 mV
500 MHz 925 mV
200 MHz 900 mV
The most intensive thing they do is play Survival Craft (for hours). Tabs were getting excessively hot before I Undervolted them. No crashes in days...
They're both on CM10.1
Sent from my SGH-I997 using Xparent Red Tapatalk 2
My voltages:
1400 MHz 1325mV
1200 MHz 1225mV
1000MHz 1175mV
800MHz 1150mV
500MHz 1050mV
200MHz 975mV
Its not much battery saver but rom is stable