yashsingh1/xdaforums huggingface dataset:
[Epic 4G Android Development] 1greek4u:
If there's a 400mhz gap between say, 200, 600, and 1000, the phone will always run at the higher speed if it needs it, when it might need less. So basically your phone will run at 600mhz when it could be running at 400, or it will run at 1000 when it could be only at 800 instead.

The processor runs through the steps instantaneously, basically having it on the lowest steps (with the lowest voltage) as often as possible will increase battery. I dunno maybe someone with more know-how can chime in for us.
[Epic 4G Android Development] JohnCorleone:
I just can't get any success with Voltage Control. I am watching these posts with great interest because SETCPU at 1400/200 on demand works perfect with no lock ups but everything I try with VC freezes. SetCPU uses only 5 steps according to CPU Spy:1400,800,400,200, and 100. I get 60% at 100 with constant use. I will try the same steps with VC and some undervolting and report back with results.
[Epic 4G Android Development] mideastbeast:
Are you running ViperRom Synergy? I'm on that ROM and was having the same issues with VC. These are the states I'm using on VC now that seem the most stable and giving me the best benchmark scores. Leaving 1400 out seems to help me a lot. I realize the undervolt is conservative but it seems to be the most stable. Any other Synergy users feel free to chime in as this is just a work in progress.

States:

100

200-25mV

400

600-25mV

800

1000-25mV

1300
[Epic 4G Android Development] JohnCorleone:
I am on Synergy. I think my trouble may be undervolting the lower steps. I am going to try the same 5 steps but only undervolt the 1400 at -50 or -75. I just tried -100 on 1400 no other undervolting and it froze. :(
[Epic 4G Android Development] mideastbeast:
I just got rid of 100 and am using 200 as the low now. Rodderick says that 100 isn't even enabled without going into terminal emulator (see post # 1070 on this thread). Try using 1300 as max. Not using 1400 should help a lot. My scores are great with 1300 as the max.
[Epic 4G Android Development] JohnCorleone:
What gets me is how much time CPU Spy shows me spending at 100 and Deep Sleep on SetCPU set at 1400/200. I get as good or better battery than I was with previus kernel at 1200/200. I mean how am I getting so much time at 100 if my minimum is 200? Strange but I can't complain about that. Even if I set my max at 1300 on Voltage Control and undervolt -25, it locks up. Also it stays at higher level as SetCPU does at "performance" so it is kind of working against me. This is like a riddle I can't solve yet but it is definately fun trying to solve it.
[Epic 4G Android Development] jbadboy2007:
2 things if setcpu is installed it will freeze with screen off so un install it. Realistically we should not be able to uv below 75-100mv so you might wanna try very conservative approach to this. The right way to do this is to look at your fav rom on github and look for the kernel voltages there as a template. I was trying to look for the mv for andromeda kernel from 2.1 but had no luck on finding it.
[Epic 4G Android Development] makipsee:
heres what i have for my settings its been stable for the day

1400 -25mV

1300 -50mV

1200 -100mV

1120 -100mV

1000 -100mV

800 -100mV

600 -75mV

i wasnt able 2 do the lower ones yet
[Epic 4G Android Development] JohnCorleone:
I understand and respect your opinion but I have been using Vision and Genocide kernels at 1400 with SetCPU for days now and haven't had a single freeze with screen off. I haven't fared as well with Voltage Control but I will continue to try any setup that people have success with so please all, continue posting your successful setups. Thanks
[Epic 4G Android Development] bryanfritz1:
I just wanna throw this out there. I was running vison for a couple of days ran good, then last night and this morning quite a bit of random slugishness. As I was wanting to try this, i loaded it up set all frequency included 100mhz and no undervolt. Battery life looks to be better than the bonsai 3.01 kernel without undervolt. So very little undervolt will most likely go along way. Just my two cents

sent from "The Other Woman"
[Epic 4G Android Development] Custodian:
John I recommend that you uninstall setcpu and set vc back to stock voltages...then reset the timers in cpu spy run some tests then look at what voltages are being used by your phone and start your tweaking from there forward.

My phone uses

1000

800

600

200

At stock voltages...so what I did was tweaked the uv on those voltages until stable...then you can start with the overclock testing
[Epic 4G Android Development] yogi2010:
yeah, I'm trying to see what kind of battery life I can get out of this. going for a solid everyday setup with awesome battery life, with a little speed thrown on top. just made a nandroid after running stable, and now pushing each voltage down 25 more:

1200 -50

1000 -100

800 -100

400 -100

200 -125

100 -125

will report back later. so far so good, managed to type this :)
[Epic 4G Android Development] JohnCorleone:
Appreciate the insight. Its been driving me nuts that I seem like the only one unable to take advantage of some undervolting
[Epic 4G Android Development] yogi2010:
does anyone know if there is a way to auto-enable the command that lets the cpu's min. go down to 100? or do you just have to type it into Terminal Emulator at every bootup?

I had a couple freeze-ups on the setup I posted above, so backing off some of the undervolting, lol.
[Epic 4G Android Development] thomasskull666:
Custodian's suggestion is exactly what I would say also, everybody should be able to undervolt so it must be a glitch in your setup. Using setcpu and VC together can cause undesirable results if used incorrectly (Rodderik put this in the OP as well), so try without setcpu for a while and see if that helps at all. I'd be interested to hear your results!
[Epic 4G Android Development] thomasskull666:
May I ask why? 100mhz min has been known to cause issues with the phone waking from sleep, which is why it is enabled as the default min on most kernels for the Epic.
[Epic 4G Android Development] yogi2010:
yeah, I've read about that being an issue for some people, but I've never once had my phone not wake up! I've always run my phone at min. 100 whenever possible, and even on kernels that do actually settle down at 100, I've never once had that problem. now, trying to go above 1200 is another story for me lol, but 100 min. seems to work great on my phone, and hopefully saves some extra battery over 200 even if they run at same voltage.
[Epic 4G Android Development] thomasskull666:
Interesting, you're a lucky guy! With Voltage Control, make sure 100mhz is enabled and set your max freq. to whatever you want it to be at boot. Press menu, apply the changes and save them to set at boot. This should work, let me know if it doesn't and I'll come up with a different solution!
[Epic 4G Android Development] yogi2010:
haha yeah, I am lucky that way..... but I know there are some others too. on this kernel, even when I enable 100mhz, setcpu will usually show the kernel only going down to 200, and cpu spy will show 100 as an unused cpu state..... until I type in the command that Rodd listed on page 107. only thing is, rebooting seems to undo it. I believe Rodd said that he has it set up somehow for 200 to be the default lower limit, so I'm guessing it would need to be written into the code itself?

thanks for your help!
[Epic 4G Android Development] jbadboy2007:
Has anyone tried different schedulers yet? Any opinions on what they do specifically. And is cfq a valid option?
[Epic 4G Android Development] dchawk81:
My Quadrant is 1284. Is that in the realm of good or did I fark something up?
[Epic 4G Android Development] jbadboy2007:
You borked something? Badly!!
[Epic 4G Android Development] dchawk81:
Well it performs okay...ie no lag or anything.

Not sure how people are getting 2000 as I just read in previous posts.
[Epic 4G Android Development] jbadboy2007:
I was getting 1500 with max of 800mhz uv'ed
[Epic 4G Android Development] dchawk81:
I'm at a loss then.

Probably going to go back to .5
[Epic 4G Android Development] churro7:
safe to use 1.0 on srf 1.02?
[Epic 4G Android Development] makipsee:
the only way to make it set the min at boot is if u create the S_volt_scheduler file and drop it in the /etc/ini.d/ folder as it says in the OP and just set the other lines as u need to
[Epic 4G Android Development] Custodian:
I believe theres alot of confusion going on.

You folks should really create a check list for yourself when it comes to flashing roms and kernels. That way, when a problem occurs you'll know the cause or atleast have an ideal.

When flashing a kernal, make sure you have a complete backup of your current system. Boot into recovery, goto advanced options, and wipe the dalvik cache twice. Then install your desired kernal for testing.

Now, you have your desired kernal loaded and ready for testing. As the OP aswell as other DEVs have stated over and over, SetCpu is a great app but it does have quite a few short commings. UNINSTALL SETCPU!! Now download and install Voltage Control(rodd posted a link in the OP), and download CPU Spy(its freeware, awsome tool aswell!! You can download. It off the market, and rodd also posted a link to it in the OP).

Now, restart your phone to insure you're back at stock voltage with no additional tweaks added. When your phone boots up compeletly, spend about 2mins browsing, and running tests. Once your done, open CPU Spy and check out the frequencies that are being used by your phone on stock voltage. (My personal stats were 1000, 800, 600, 200).

Now that you have the numbers, (refer back to the OP on how to use voltage control.) But I will add this, once you understand the basic functions of voltage control, open the states tab and only select those few voltages that were being used by your phone in CPUspy. Now apply those settings for now. Still at stock settings, now we begin undervolting those same exact stock voltages until stable.

What I have found to be safe for me, not saying it will be the same for everyone else, is to start off undervolting each enabled voltage @ -25 and stress testing to test stability. If all is well, Then I start undervolting the lowest voltage further, and test stability until my phone freezes. I do this for each voltage until stable. Once those stock voltages are all undervolted and I'm %120 sure my phone is stable(reboots well, wakes up well, play games,browse well, calls out, texting,receive calls whatever)

Then I apply to boot settings. Then and only then, do I start overclocking....and another adventure begins :)

Also, once you're satisfied, for battery testing purposes, check back with cpu spy to see which voltages your phone is using the most and the least during your daily usage, then go into voltage control and disable the less used voltages...make sure your two or three, depending on how many you have enabled most used voltages are still enabled though..then apply for now, put your phone to sleep for 2 mins, if it wakes up..run some tests to test stability for about 5mins...if it doesn't lock up...then reboot..if it reboots well...then maybe those settings are golden and now you can really test your battery ..I do apologize for the grammer... :p
[Epic 4G Android Development] dchawk81:
Why'd you quote me?
[Epic 4G Android Development] Custodian:
Will you marry me?
[Epic 4G Android Development] dchawk81:
Do you have a vagina?
[Epic 4G Android Development] diptenkrom:
Did anyone else have battery charging issues? I flashed v1.0 and did not much to it, battery showed low, so I plugged it in. It was not charging. I turned phone off, still no charge. Fortunately I have an external charger...

Reverted back to 0.5a for now. I only OC'd it to 1120 or whatever that setting was. And did not even start the undervolting.

BTW my quadrant was 1150 high out of 3 tests. I am on stock ec05 with just the kernel, and most of the stock apps removed.

Sent from stock EC05 OTW...
[Epic 4G Android Development] dchawk81:
Mine charges.
[Epic 4G Android Development] lballer69:
Wipe battery stats in recovery

sent from my 1.3ghz voodoo beast (super epic)
[Epic 4G Android Development] Custodian:
Wipe battery stats in recovery
[Epic 4G Android Development] Rodderik:
i want to personally thank each and every one of you for keeping this thread on topic and not flaming others while i was away...i am truly amazed so thank you :)

btw i'm back!
[Epic 4G Android Development] lballer69:
Reboot into recovery. Goto advanced settings. Wipe battery stats. Reboot phone. Done.[/QUOTE]

His phone won't charge at all so he can't calibrate it at the mment so a quick wipe might fix his problem

sent from my 1.3ghz voodoo beast (super epic)
[Epic 4G Android Development] jbadboy2007:
Rod in your next release could you make 100mhz on by default. Cuz it is easier to disable then enable.
[Epic 4G Android Development] Custodian:
Welcome back!
[Epic 4G Android Development] dchawk81:
You were gone?
[Epic 4G Android Development] yogi2010:
i personally would like this too, although i am gonna try making a voltage scheduler file as described..... just gotta get familiar with 'adb shell'.
[Epic 4G Android Development] Rodderik:
i updated the FAQ in the OP and threw together a script for those who want 100MHz min. i do not intend to set 100MHz as the minimum but this is a simple solution for those who want it.

Q. I have enabled 100MHz but I can not scale down to 100MHz. Why?

A. By default the kernel sets 200MHz minimum. In order to scale down to 100MHz you can flash this script to set 100MHz on boot http://teamviper.devphone.org/downloads/kernels/Genocide_set_min_100MHz.zip or add this line to /system/etc/init.d/S_volt_scheduler:

echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
[Epic 4G Android Development] burgerpimp07:
To be completely honest my phone runs as smooth as I need it to with 1000MHz max and I really don't care about benchmarks. I only want the best battery life. Running 200,400,600,800,1000 all undervolted -100. Stable so far after all benchmark tests, and waking from 5-10 min sleep periods.

Question though, a few people have hinted at the less frequency steps, the more battery savings. 200-1000 is 5 steps. Looking at cpu spy, the 600 step seems to be used the least, would unchecking 600MHz help battery life?
[Epic 4G Android Development] yogi2010:
we're having fun with this :) hope you had a nice time away.
[Epic 4G Android Development] Rodderik:
i guess i had fun...gutted a bathroom and closet and ripped up the flooring in preparation to redo all that down there...the rest of the land was under water so couldn't do much playing in the woods. :/
[Epic 4G Android Development] Rodderik:
got your email, thanks yogi2010 :D
[Epic 4G Android Development] JohnCorleone:
Ok, I appreciate the help here. So far so good. Even if I can only get -25 of undervolt it will be worth it. Now for some overclock fun! Thanks to everyone who has been posting recommendations. Keep the successful setups coming!
[Epic 4G Android Development] yogi2010:
ah cool, you're welcome. glad you sort of had fun, sounds like you're paving the way for a nice getaway cabin??

btw, sorry to be a pain, but i think maybe the zip for the min. didn't work? still hangs at 200. or have i missed something?
[Epic 4G Android Development] burgerpimp07:
x2, flashed the 100MHz step minimum, did not work.
[Epic 4G Android Development] BThomas22x:
Lol that was just to show what it does ...my normal scaling is 200-1.2GHz (Now lol). Because i found that if you leave it on 100 and wake, your phone really bogs and a couple apps have issues.
[Epic 4G Android Development] yogi2010:
ahh yeah, I figured that was maybe for show :)

is it true tho about 1.0 max. and min. being the best battery saver thus far you think?
[Epic 4G Android Development] JudasD:
wow this kernel really feels snappy! even if you keep it at 1ghz, many of the laggy spots appear to be gone. This is very nice!!! Thank you to the OP!

To those with CWM issues; if you quick boot into recovery then it will be broken, however, if you do the button-mash method then all is fine.

JD
[Epic 4G Android Development] BThomas22x:
I Run Conservative, 200-1.2 and i have no issues. This might not be the preference for everyone, but it's fine on battery with me. It's gonna be different on every ROM though, so to give a particular setup might not be that helpful lol.
[Epic 4G Android Development] yogi2010:
yeah, I like that setting myself, but in the end we must all test for ourselves ;) thx BT
[Epic 4G Android Development] Rodderik:
just to clarify for some people....

do not use setcpu to set 1.0 min and 1.2 max! the lower frequencies down to 100mhz use far less power than the undervolted 1ghz.

For those who want the gains from 1.2Ghz i recommend

Max: 1200000 (1.2GHz)

Min: 100000 (100Mhz)

Scaling: conservative

and once you test it and feel comfortable that it is stable for you (which it should be) tick 'Set on Boot'

For those that just want to save battery and not use 1.2GHz i recommend

Max: 1000000 (1.0GHz)

Min: 100000 (100Mhz)

Scaling: conservative

and once you test it and feel comfortable that it is stable for you (which it should be) tick 'Set on Boot'

*this will make your phone run at the normal 1Ghz while still undervolted for a little bit better battery life

i haven't tested with the different governors to see if one of the others is any better than conservative (atleast until we tweak them in the source)

i hope that clears things up for some people
[Epic 4G Android Development] lilmikeyv:
Sweet, thanks for the clarification!
[Epic 4G Android Development] yogi2010:
+1, that says it all, Rodderik. 'thanks', from my phone, lol.
[Epic 4G Android Development] BopChie:
ymmv @100 for min... bogged down wake and some**** may lock the phone or fc

ifso go 200
[Epic 4G Android Development] theimpaler747:
Hmm.... none of that for me.
[Epic 4G Android Development] Rodderik:
i haven't had any lockups or issues yet using the phone normally (100mhz-1.2ghz)...and my son also played some graphic intensive games for the hour and a half i had to drive him home today and i locked it at 1ghz to test the undervolt stability...no problems at all

now to work on getting the source online for you guys
[Epic 4G Android Development] Paul627g:
I've been using it set at conservative 1000000 to 100000 for the undervolt and battery life is very impressive. Normally playing Angry Birds it would suck the stock battery dry in no time, so far with this setting I've gone about 8 hrs now played about an hour or so of Angry Birds with some net surfing and only down 28 % after 8 hrs... So much better improvement over the stock kernel.

Running TER 1.5 ROM.
[Epic 4G Android Development] Rodderik:
that's awesome...glad you're seeing such a good improvement!
[Epic 4G Android Development] lv2bll:
only lost 2% while my phone was on standby for an hour, so this really works well.

my screen off setttings are 100mhz-800mhz on "userspace".

just thought i'd share for you guys. Thanks rodderik for this kernel. Really is nice!

Can anyone else try powersave and let me know how it is.
[Epic 4G Android Development] musclehead84:
Anyone getting a bunch.of errors in cwm3? The kernel is awesome and I booted into recovery and when it opens I get alot of unknown paths. Is this normal for the kernel?

Sent from my Evo Killer!!!
[Epic 4G Android Development] heathmcabee:
Works as described, and you are excellently awesome for sharing!
[Epic 4G Android Development] theimpaler747:
I'm running fine booting into cwm

Sent from a truly Epic phone and a transparent XDA app ;)
[Epic 4G Android Development] MeetFace:
You are probably on a rom that does not have redirector working correctly.

I'm assuming you tried to boot into cwm via quick boot or rom manager.

What happens when you three finger?
[Epic 4G Android Development] danasmith2816:
Thanks for clarifying and for the kernel. much faster for me on Epic Experience
[Epic 4G Android Development] strauss0829:
OMG im making a comeback ASAP
[Epic 4G Android Development] Rodderik:
do me a favor and check /system/etc/init.d/ for a file called S_set_min_100MHz and let me know if it is there...if it is then also post your S_volt_scheduler file from that same directory

on second thought...i think i know what i did...give me a few to post up a new one

ok uploaded a new one http://teamviper.devphone.org/downloads/kernels/Genocide_set_min_100MHz.zip

let me know if it doesn't work now
[Epic 4G Android Development] yogi2010:
yes i DO have the S_set_min file there. i also see my voltage scheduler file, but how can i post it from Root Explorer? i can view it as text, copy, edit, or send the file....

also, can we add the line to set the min. into the scheduler file, if we open the file in text editor in Root Explorer?
[Epic 4G Android Development] Rodderik:
i updated the S_set_min file...i forgot a line to tell it that it was a script but you can add the link in the S_volt_scheduler file that way ...either way will work
[Epic 4G Android Development] iSaint:
Hey Rodderik, Further down the line when CM7 is more stable do you think we'll see this kernel for it ?
[Epic 4G Android Development] yogi2010:
dang, still a no-go on the zip i believe. if i do add the line to set the min. into the scheduler file, does it matter where i add it?
[Epic 4G Android Development] Rodderik:
it is quite possible :)
[Epic 4G Android Development] JohnCorleone:
Rodderik, are you having any luck undervolting 1400? I just can't give up the CPU gain I got and go to a lower state
[Epic 4G Android Development] mikey80021:
CM7 + Genocide? That would be amazing!
[Epic 4G Android Development] Rodderik:
it doesn't matter where in that file you add the line but i would recommend right below where you set the max freq

and for the .zip to set min....that's why i always test stuff before releasing it...guess i should have before i spit out that zip...but i think i know what i did...ill fix it and verify it works in a few minutes
[Epic 4G Android Development] burgerpimp07:
i can confirm this
[Epic 4G Android Development] yogi2010:
ok cool. and no problem, we're happy to test :)
[Epic 4G Android Development] burgerpimp07:
Correct me if I'm wrong, but it seems that you can undervolt the lower frequencies more than the higher ones.

I was running 100mV undervolt across the board on 200,400,600,800,1000 with no issues. When I tried 125mV my phone froze after a few benchmarks.

Now I am running:

1000MHz - 100

800MHz - 100

600MHz - 100

400MHz - 125

200MHz - 125

100MHz - 125

with no issues or freezes, after waking from sleep, or benchmark testing. Will probably run this for a few days and see if its stable before undervolting some more.

*edit* added 100MHz step
[Epic 4G Android Development] JohnCorleone:
Ok, finally. 1400,800,600,400,200. No undervolt on 1400 or it freezes right up. Even scaling between each "state" My battery was still better with SetCPU "on demand" because 60% was at 200 but if everyone says its not safe, I will stay on VC. Oh, only -25 undervolt so far on 800,600,400
[Epic 4G Android Development] JohnCorleone:
Maybe I can crank up my lower state undervolting and stay away from 1400 and minimal at 200. If I go that high on low states, it freezes on shut down.
[Epic 4G Android Development] iSaint:
Sweet! Bro this phone will fly with CM7 @ 1.4 Gigawatt's :D
[Epic 4G Android Development] jbadboy2007:
You enabled the 100mhz state in vc right?
[Epic 4G Android Development] Rodderik:
ok i fixed the flashable script to set 100MHz as min on boot...it should work now so just download it again
[Epic 4G Android Development] burgerpimp07:
I can confirm that this works. You're the ****!
[Epic 4G Android Development] iSaint:
.... No he's the piss because he's #1
[Epic 4G Android Development] Rodderik:
haha...goofy people
[Epic 4G Android Development] diptenkrom:
Okay, now I have a problem. I reverted to 0.5a, and still can't charge my phone. Had to reroot, and then went to test charge and no charge indication still. Don't really want to have to start over, tried clearing batt stats, is there anythingelse I can try?

Phone works fine other than charging problem...

Sent from stock EC05 with Genocide 0.5a