Database Info

1.6GHz

:giggity: Adrynalyne test kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
quadrant

Care to Share How?

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

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

You getting about 5 mins of battery life now?

That's teh sex!

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

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

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

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

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

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

i want!!!!

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

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

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

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

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

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

that's just silly without any extra qualifying statement.

400Mhz at -200mV on top of -50mV?

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.

[Q]Galaxy Tap 7.7 Can OverClock?

Galaxy Tap 7.7 Can OverClock?
...and It can Overclock ..how to do it?

PJTONz said:
Galaxy Tap 7.7 Can OverClock?
...and It can Overclock ..how to do it?
Click to expand...
Click to collapse
Until someone develops a custom kernel for overclocking, then the answer is "no."
However, if/when this does happen, you can use a root app called SetCPU.

PJTONz said:
Galaxy Tap 7.7 Can OverClock?
...and It can Overclock ..how to do it?
Click to expand...
Click to collapse
hi!
You can overclock your tablet with the Tegrak application on the market... be careful not to forget to increase the voltage at the same time in the overclokage... mine is Overclocked a 1.6GHz

hella i use tegrak too, you have set 1600 for ever? You are not scared if higth frequency fries your cpu? and what about mali400? U set the gpu to 400mhz and leave it at 400 for ever?

not my processor is set "on demand" it between 200 and 1600mhz.... However, I do not overclock the GPU....
{
"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 just tried overclocking with Tegrak too.
However, when overclocking to say 1.5 or 1.6Ghz it causes lag, why?

have you ever tried Zeta ROM ?

hillzx said:
have you ever tried Zeta ROM ?
Click to expand...
Click to collapse
It's ok with zeta rom.......v4

I bought Tegrak overclock, too.
Using stock ICS 4.04, does anyone know the right voltage to get up to 1.6Ghz ?
I tried mine 1.6Ghz at 1.45v, but I think it resulted lower Antutu benchmark, I don't know why..

dlee064 said:
I bought Tegrak overclock, too.
Using stock ICS 4.04, does anyone know the right voltage to get up to 1.6Ghz ?
I tried mine 1.6Ghz at 1.45v, but I think it resulted lower Antutu benchmark, I don't know why..
Click to expand...
Click to collapse
The bester for 1,6ghz is 1,250 and it's Ok with 1.3v
My quadrand is 5300

micger21 said:
The bester for 1,6ghz is 1,250 and it's Ok with 1.3v
My quadrand is 5300
Click to expand...
Click to collapse
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ?
or is the default voltage setup already too high enough that can be reduced while staying stable?
is it okay if you share your stable voltage for each ghz list ?
thanks

dlee064 said:
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ?
or is the default voltage setup already too high enough that can be reduced while staying stable?
is it okay if you share your stable voltage for each ghz list ?
thanks
Click to expand...
Click to collapse
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ? yes
or is the default voltage setup already too high enough that can be reduced while staying stable? yes very stable, no issue
.........lowering processor voltage, the gain of battery can be observed, and the power is here!

micger21 said:
thanks, but wait, isn't the default 1.4Ghz set to 1.25v already ? yes
or is the default voltage setup already too high enough that can be reduced while staying stable? yes very stable, no issue
.........lowering processor voltage, the gain of battery can be observed, and the power is here!
View attachment 1308231
View attachment 1308232
View attachment 1308233
View attachment 1308234
Click to expand...
Click to collapse
Thanks a lot for your screenshots,, first two pics are the same btw

dlee064 said:
Thanks a lot for your screenshots,, first two pics are the same btw
Click to expand...
Click to collapse
!
Also, my battery temperature has dropped 4 to 5 degrees working with these settings ... These are personal settings ..... it is more than 15 days is up and it works perfectly on my tablet ....
gpu is at 400mhz with 1100mv for you information ....it's for that I have this score to nenamark2!
I tested too and its ok:
processor: 1.652 ghz for 1.3
1.600 ghz for 1.250v and 1.3v
1.552 ghz for 1.250
1500 ghz for 1.200
1400 ghz for 1.200......and i think your can 1.150v...no tested
......computing power as well as the benchmark machine improves significantly under voltage processor and not the other way .... I read on the internet that samsung would tend to increase the voltage of its processors ..... i do not know why
Before making my settings ... when I was surfing on wifi and the power was connected, the battery temperature ranged from 39 to 43 degree ... with these new parameters, the heating pad and earns much less 10 degrees less. now .... I'm a little less than 32 degree..... with much better performance!

micger21 said:
!
Also, my battery temperature has dropped 4 to 5 degrees working with these settings ... These are personal settings ..... it is more than 15 days is up and it works perfectly on my tablet ....
gpu is at 400mhz with 1100mv for you information ....it's for that I have this score to nenamark2!
I tested too and its ok:
processor: 1.652 ghz for 1.3
1.600 ghz for 1.250v and 1.3v
1.552 ghz for 1.250
1500 ghz for 1.200
1400 ghz for 1.200......and i think your can 1.150v...no tested
......computing power as well as the benchmark machine improves significantly under voltage processor and not the other way .... I read on the internet that samsung would tend to increase the voltage of its processors ..... i do not know why
Before making my settings ... when I was surfing on wifi and the power was connected, the battery temperature ranged from 39 to 43 degree ... with these new parameters, the heating pad and earns much less 10 degrees less. now .... I'm a little less than 32 degree..... with much better performance!
Click to expand...
Click to collapse
By the way, few questions,
Is there a way to set in Tegrak so that, I set 200Mhz or 500Mhz, and directly jump to 1.6Ghz+ ?
Maybe I'm a bit too analytic, using one of the Android system info, I use about ~10 to 20% of 800mhz/1000mhz/1400mhz, and I feel that those transitional process could make it 'sluggish' when processing demand is really required.
So perhaps, for a sake of 'smoothness' (but not using 'performance'-mode) I want to just use 200/500mhz and 1.6ghz+..
When CPU0 is set to 1.6ghz, the next lowest CPU1 is 1596mhz, (-4), and I can't change CPU2 and the rest..
Btw, I haven't treid 1.65, but I'll try it now and let you know

i noticed that sometimes my tab doesn't sleep. the minimum is just 200mhz causing my battery to drain faster than normal. and once it stayed 1.6 mhz. is it related to the OC kernel used? is there other kernels available for OC aside from EZYICS kernel?

[Q] Best undervolt values for this tablet?

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

Undervolting, what are your settings?

My battery is getting old and along with that its life length. So I decided to undervolt and found it stressful but fun (lol weird huh?).
I'm currently stress testing it using SetCPU's stress test, so far it has not crashed.
My undervolt settings:
100 MHz - 950
200 MHz - 950
300 MHz - 975 *
400 MHz - 1000
500 MHz - 1025 *
600 MHz - 1050 *
700 MHz - 1075 *
800 MHz - 1100
900 MHz - 1125 *
1000 MHz - 1150
1100 MHz - 1175 *
1200 MHz - 1200
* - I'm just assuming SetCPU sets this automatically since it skips some clock speeds.
However I set the voltages increment by 25, so far the stress test has not shown any crashes.
What are your settings?

I run about -75 I think across the board using AndroidTuner, no stress test, but seems stable.