What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
akaine2001 said:
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
Thank Samsung for breaking ondemand on every sgs phone.
Sent from my SCH-I500 using XDA App
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
akaine2001 said:
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
Click to expand...
Click to collapse
You are doing something wrong. Conservative is not choppy on my device and the CPU will always ramp up faster than a human being can judge the response time.
Sent from my SCH-I500 using XDA App
My phone makes it the entire day with heavy use, this means about 20 - 10 min phone calls one or two lasting 30 min, texting my wife all day at work, checking emails, and angry birds for at least 1 hour a day i love that game but I suck at it lol. Something that I found is that the phone will last almost an hour of being on the phone after it hits 0%. In my pocket it lasted 4 hours at 0% the day before yesterday. I thought maybe this is on purpose so you have more then enough time to make it to a charger. When I first downloaded angry birds I played it for three hours straight with the screen at full brightness (i always keep it at full brightness, looks prettier that way) I know it was three hourse because it was while i was waiting at the hospital I got there a little before 7 and wasnt called until 10. Overall I am very pleased with the battery life of this phone not so much with other aspects but battery life and lag never came into my mind as a complaint for this phone, except with all the stock touchwiz stuff.
As adrynalyne said, CPU's scaling changes faster than human's perception. It's your phone or setting that's having an issue.
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
I meant "reliable" not trailer.
I get about 5 hours of screen time with little voice calls on wifi.
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge, having even made it to 44 hours on a very rare occasion and that's without setcpu profiles even set.
Wtf... my phone is brand spanking new and I get about 4ish hours of screen time on a full charge, with the lowest brightness + screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on.... wtf. This is running on conservative or interactive the whole time..... wtf!!! With wifi on and 0 extra screens or Widgets using launcher pro without animations... wtf!!!
Sent from my SCH-I500 using XDA App
+1... stock battery indicator is not accurate. Get the accurate battery mod.
soba49 said:
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
Terror_1 said:
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge...
Click to expand...
Click to collapse
That's because you don't use your phone.
Go play NFS for 3 hours and get back to us.
MoShiBa said:
...screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on...conservative or interactive the whole time...
Click to expand...
Click to collapse
What's the screen filter app? Conservative and interactive? That's SetCPU?
I wouldn't worry about these guys coming in here saying they're getting 2 days of use either. They're not using the phone anywhere near as much as you. I've had 3 of these things and know 2 guys with them. They all got the same battery life. You don't see anyone posting any screenshots, do you?
Me and my gfs fascinate gets about same battery life in our apt and hers is still DI01 and i'm on DJ05... she has jts 11/16 kernel and i have the 12/21 voodoo5 and we get about the same battery life... dependent on how much we use the phone. .... so just use your phone, and charge it as necessary... its better for the type of battery we use anyways in our phones... **************************************************************************************closed.**************************************************************************************
Related
ok i was under the impression that cynanogen mod autmatically over clocks the cpu to 528mhz. But someone told me it doesn't. Does it? and if i use setcpu will affect the stability?
Your not really Oc'ing because the CPU was made to run at a max of 528 and 384 is the stock(Offical OTAs) to save battery life. It will only go that high when needed, you dont drive at a 100MPH just to do it, you do that when no one else is around. It will reach that high under heavy load not if your dialing on just swiping on home.
ace is right from what ive been told and read. the cpu is underclocked so its not hitting its full potential.
also no cyanogen does not do this automatically. this is best done by the user anyway as they can get a prefered setup then on their phone as this does consume battery life.
Ok i downloaded setcpu but i dont see a big difference i selected 528 as max and the max stock as minumum and put set on boot and i rebooted. I dont know why im typing in upper case, im on my g1
to be honest i never really noticed too much of a difference myself.
I've been using SetCPU now for about 48 hours and am very impressed with it. See my sig for current system setup. As far as SetCPU settings: on-demand throttling, 528 MHz max, 245 Mhz min, no profile settings, scaling up setting 75%, and both "set on boot" options checked. The SetCPU settings definitely make the phone snappier compared to the normal CyanogenMod settings.
is there a difference between on demand governor or performance? whitch one is faster?
nahanee20 said:
is there a difference between on demand governor or performance? whitch one is faster?
Click to expand...
Click to collapse
http://www.pokedev.com/setcpu
On demand will scale CPU speed between the minimum and maximum settings, and performance runs it at maximum constantly.
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
BoomBoomPOW said:
Current CM rom fluctuates from 256Mhz/min to 528Mhz/max on demand. I suggest you leave it alone since it's an exceptional setup. Unless you prefer a constant max and have your battery die in 6 hours give or take.
Click to expand...
Click to collapse
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
TeeJay3800 said:
It's not that exceptional, nor does modifying that setup drain your battery much faster. My G1 is much faster after using SetCPU to change the settings. My battery drain in standby is unchanged (because I'm using the same minimum setting as CM), and it is significantly faster under heavy usage. There's really no downside to it, so to assume that the default CM setup is optimal is a little short sighted in my opinion. Don't be offended...just my 2 cents.
Click to expand...
Click to collapse
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
The main thing that SetCPU does that CM does not is adjust the threshold at which the CPU begins to scale up. I have mine set to 50% which is far lower than CM's setting, and I believe that is the main reason my phone is so much faster.
Also, SetCPU does not stay running in the background. A script runs at boot to apply your settings, but the app doesn't actually run unless you start it yourself.
CM's default up threshold is at 40, so I have no clue where you got the idea that is far higher. Also, it does not affect speed. It's the percent cpu usage before going up a speed step. So actually the higher the threshold, the longer it stays on current/lower speed.
SetCpu does stay running in the background. Open your app drawer, open Dev Tools, Running Processes, and you will see SetCpu (com.mhuang.overclocking) running.
Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
Well pal, all I can tell you is my phone is a LOT faster after using SetCPU to adjust settings. I don't mean only marginally, I mean significantly. In fact I can't overstate how much more snappy the phone is. If you can explain why that might be, I'd love to hear it.
EDIT: That process is not running.
It boils down to user experience. If it feels cold, then it must be cold. Am I right? But these are all perceptions manufactured by our brain. That is why we have crazy people. I'm not calling you crazy, but crazy people see things that are not there. Perception is the word of the day.
I guess we'll have to agree to disagree. I could measure the before and after difference with a stopwatch, meaning it genuinely is faster. In my opinion, it is entirely possible that SetCPU allows for faster performance than CM does by default. Unfortunately, that is impossible for me to prove via an internet forum. Anyway, it was fun debating with you.
BoomBoomPOW said:
What you just stated is the exact performance the coded frequency default on CM does. On demand is the key word. When you go standby/sleep, frequencies goes minimum. When under heavy usage, frequencies goes maximum. So how is that short sighted? When everything you stated that SetCpu does better, is the exact thing that the default CM setup does. Plus having SetCpu process run constantly in background is a main factor that eats up RAM. While the default CM setup does not. The only benefit I see with SetCpu are the profiles.
Click to expand...
Click to collapse
I've been rooted and running SetCPU for a while but just recently switched to CM. I had CM running with SetCPU until today when I decided to remove SetCPU to see how CM does on it's own. My phone seems exactly the same from what I can tell... if not a tad faster. BUT I really liked the ability to have SetCPU clock the CPU waaaay down when the battery gets below a certain %. I had it set to run at 245max/128min when the battery dropped below 30%... yes it was sluggish but it would stretch that 30% for many hours if I needed it to.
Does CM do anything like this or have a provision somewhere for setting cpu speed based on battery level? I don't like having stuff installed if I don't need to, but missing this feature may have me reinstalling SetCPU.
Hey guys any of you running set cpu? i have a profile set so that when i turn the screen off it drops the cpu down to 250mhz. I'm having a issue where sometimes it dosen't wake back up. Anyone else had this happen?
I noticed this Tuesday. They don't play nice together...yet. setcpu needs info about the hummingbird cpu in order for it to work. Setcpu's dev will most likely have an update for this soon. For now, i'd uninstall it and keep an eye out on the program for an update.
sweet glad to know that its not just me.
I had this same problem with the Overclock Widget for the same purpose (shut down CPU while screen sleeps)... After removing Overclock... I have yet to have a blank screen situation.
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
madocs said:
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
Click to expand...
Click to collapse
Scratch that - this morning the EPIC didn't wake. Battery out, back in, screen off, didn't wake.
Uninstalled SetCpu, all is back to normal (except for the crap battery life of course).
Emailed the SetCpu dev, he thinks it is related to the kernel. I'll try out a custom ROM/kernel as soon as one is ready to see if it resolves the issue.
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Chalup said:
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Click to expand...
Click to collapse
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
vavaud said:
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
Click to expand...
Click to collapse
How long have you had it in use? I was cool for a day, then it wouldn't wake up.
From the dev: "The scaling is the issue, I think. Ondemand crashes the Galaxy S, but conservative doesn't seem to."
I'm ready to hit some customs, battery life just isn't good enough so far.
2.0t03speed said:
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
Click to expand...
Click to collapse
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I was using conservative on set cpu when i got the lockup
Sent from my Epic 4G
I have been using setCPU and ATK since 9/2 with no problems so far. I have it set on conservative and 200 when screen is off. I been getting around 10-12 hours with moderate uses. With little use today I am at 9 hours with 50% battery left.
madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I ended up at with over 15 hours logged and ~15-20% battery remaining last night. Good enough for me. Bluetooth/GPS/Wifi on all day, 4G off, screen turned down, ATK.
No Problem with CPU Set at 200
I kept having the same issue until I changed the lower limit to 200 and used Conservative setting.
Now, no problem at all!
I think I tend to agree with you.... I tried running the phoenix kernel on my epic, and the phone would not wake up (was told it was because phoenix defaults to 100/1000) and was told to use setcpu.. tried it... wow... what a disappointment.. setcpu kept giving me way different readings everytime I ran it.... not nice at all....
I've since tried this again, this time, placing setcpu.txt on my /sdcard will see if this helps..... so far, so good......
I have a screen off profile set for 400mhz max 200mhz min with conservative governor. My main profile is 1200mhz max and 200mhz min. This is with the mixup kernel and I never have any lock up issues
Sent from my Emotionless Beast of an Epic using the XDA App
i have my min at 200 for all of my profiles. My screen max is 400 and it keeps my phone from waking up. It's set to conservative. I'm also using it with juice defender, so i'm not sure if that's the culprit or what. Does anyone else have any suggestions on settings for screen off?
can someone help me with set cpu profiles. I think I set it correctly, but battery life not what i'm expecting. i'm running ACS newest rom. I have it set to ondemand 100-1000 as the base. then I have a profile for screen off that specifies 100-200 conservative. so shouldn't it basically just be sitting at 100-200 most of the time since the screen is usually off? when I check it seems to be using 1000 an aweful lot which is weird for something that isn't using that unless the screen is on.
Those settings look right to me. I bumped my idle up to 400 though incase any background services need it. If its too underclocked it will stress the battery even harder if a service needs more from my understanding. Try calibrating your battery and downloading juice defender. I caught some flack in the ACS thread for these two things but after 7 idle hours last night I only lost 6%. Having the screen on is the biggest drain but there may also be other factors at play in your case.
Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!
http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.
063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.
Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...
Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.
I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.
dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.
I have been tweaking my G2 ever since I got it and it seems I found a pretty good configuration that gives me awesome battery life of 30 hours on medium light use and stock battery. Now I wonder if I can make it any better.
Ill post my configuration and hope that other will do the same to see if we can squeeze more battery life out of our phones!
CONFIG
SetCPU
screen on - 1000 Max, 122 Min, conservative
screen off - 245 Max, 122 Min, conservative
JuiceDefender/Setting Profiles
wifi on at home and work only
data off when wifi on
data off when screen off, toggle on for 1m every 30m
Home screen
three widgets
beautiful widets @ 4 hr refresh
genie widget @ 4 hr refresh
agenda widget
System
MIUI rom 1.7.22 www.miui.us
streamline5 kernel http://forum.androidspin.com/showthread.php/6555-Streamline5-Nightly-CM7-Test-Kernel-2.6.35.13
darkyy's memory boost script http://forum.xda-developers.com/showthread.php?t=998976
radio 26.0.03.26 with rmk's ril matcher http://forum.xda-developers.com/showthread.php?t=1021463
USAGE - medium light
< 10 calls approx 20 min total
< 50 text
< 15 emails
30 min navigation
45 min slacker radio
15-30 min gaming
30 min genie widget + browser on news
SCREEN - @28 HRS
If you can get more, post a screen, your config and usage. Sense hibernate doesnt count!
Pershoots kernel is the ultimate secret. And not to OC past 1.2 cause there is no noticeable difference once you go past that point.
Sent from my HTC Vision using XDA Premium App
For me it's called rmk40's virtuous g-lite v1.0.2. lol I regularly get 2~ish days without any special tweaking.
xsteven77x is right too, pershoot's kernel is by far the most efficient and nothing above 1.2 Ghz as the voltage requirements increase a lot i believe.
the secret to great battery life: don't use your phone.
xsteven77x said:
Pershoots kernel is the ultimate secret. And not to OC past 1.2 cause there is no noticeable difference once you go past that point.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
If you are using pershoot's kernal, what governer are you setting it to to max battery life? On demand?
Thanks
ill give pershoot a try
crevis24 said:
If you are using pershoot's kernal, what governer are you setting it to to max battery life? On demand?
Thanks
Click to expand...
Click to collapse
His only has on demand, performance, and user space (which I don't even know what that one does). I leave it on demand because performance keeps the CPU ramped up too often for good battery life with no noticeable improvement in actual performance lol.
Sent from my HTC Vision using XDA Premium App
Pershoot impressions @250min 1010max:
1) The ondemand has obviously been tweaked by pershoot to be VERY favourable to the 250mhz. This unfortunately makes the phone just very slight make a stutter step before ramping up to do a CPU intensive task.
2) The kernel is great when the phone is not regularily used, but seems to draw more power than Streamline5 when something is actually running but not requiring full CPU time as Streamline does provide other governors.
3) The kernel seems to take its time going into "deep sleep" 1 2 day uptime and only 17 hours of deep sleep.
Will continue the testing but seem like if you use the phone in a "medium light" usage, Streamline seems to be the better choice.
UPDATE: I am sitting at 64% @ 9h with pershoot...
im using a power sucking rom, virtuous unity. i just set my phone up so it will at least last a day with a little bit of battery left over. Here are my settings
Wake min: 245mhz Wake max: 1516mhz Governer:Ondemand
Sleep min: 245mhz sleep max: 356mhz Governer: conservative
also use juice defender with advanced settings and a auto memory killer with system tweaks for optimal battery life. i get about 12 to 13 hours.
evilcuber said:
im using a power sucking rom, virtuous unity. i just set my phone up so it will at least last a day with a little bit of battery left over. Here are my settings
Wake min: 245mhz Wake max: 1516mhz Governer:Ondemand
Sleep min: 245mhz sleep max: 356mhz Governer: conservative
also use juice defender with advanced settings and a auto memory killer with system tweaks for optimal battery life. i get about 12 to 13 hours.
Click to expand...
Click to collapse
i noticed you are with rogers as i am too, try "3g only" i had similar setup on a sense rom before and can get a few more hours out of it
i remember with sense i was getting 18 hours max. with the same usage outlined in op
lalalandrus said:
i noticed you are with rogers as i am too, try "3g only" i had similar setup on a sense rom before and can get a few more hours out of it
i remember with sense i was getting 18 hours max. with the same usage outlined in op
Click to expand...
Click to collapse
How do you set 3g only? If i set gsm only in settings, i only get edge networks
Sent from my HTC Vision using XDA App
evilcuber said:
How do you set 3g only? If i set gsm only in settings, i only get edge networks
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
in sense roms, two ways, gsm = 2g that explains why you only get 2g. 3g is wcdma
1) dailer -> *#*#4636#*#* -> phone info -> scroll to btm -> WCDMA ONLY -> reboot
2) menu-> settings -> mobile network settings -> network type selection -> 3g only
seems like i found another way to squeeze more battery life out, i extracted the virtuous rom's o/c daemon and uninstalled setcpu. will report with more data but so far everything is working better than setcpu (might be placebo effect)
I update the new radio 26.10.04.12
http://forum.xda-developers.com/showthread.php?t=970809
and matched rils
http://forum.xda-developers.com/showpost.php?p=16489050&postcount=807
and extracted from virtuous unity the performance tweak script for memory from /system/etc/init.d/10-virtuous_performance and the virtuous_oc from /system/xbin
went back to streamline 5 and install daemon tweaker
http://forum.xda-developers.com/showpost.php?p=16015003&postcount=43194
RESULT = 40 hours of battery! (same usage as first post of not more)
I don't know what's wrong with my battery...
I use CyanogenMod 7.1.0 RC1 with cpu OnDemand 245-1209 MhZ, just a few widgets (tajm, battstatt, desktop visualizer), no wlan and average usage. With this setup some people reported they got a battery life of 16-18 hours. I have to charge after 8 hours...with a brand new stock battery :/
lalalandrus said:
USAGE - medium light
< 10 calls approx 20 min total
< 50 text
< 15 emails
30 min navigation
45 min slacker radio
15-30 min gaming
30 min genie widget + browser on news
SCREEN - @28 HRS
Click to expand...
Click to collapse
In your screenshot, "Display" shows as only 1%. In my experience, unless you never actually turn on the screen, the display will tend to be the biggest power consumer. What brightness level do you have it set to? Can you please tap on "Display" and post a screenshot of that? I want to see how long your screen has been on during those 28 hours.
Even at the dimmest setting, an idle CPU @ 245 MHz, and in airplane mode, my phone draws 90 mA. About 60 mA of that is the display and G sensor. At full brightness, the phone draws a total of 220 mA, or 190 mA for the display.
On a stock 1300 mAh battery, 16% remaining is 208 mAh, meaning 1092 mAh has been consumed. 1% of that is about 11 mAh. At minimum brightness, that will run the display for 11 minutes (11 mAh / 60 mA = 0.183 h). At maximum brightness, only 3.5 minutes.
It looks like you had the display on for at least 90 minutes (only nav, gaming, browser), which means your display is only drawing about 7.3 mA, which I do not believe is possible, given the LCD panel in the DZ. That works out to only 27 mW (at 3.7 volts), which is roughly one-tenth the power draw of similar displays where I could find the specs.
So are you just leaving the screen turned off the whole time?
Longest time off charger for me is 2 days and 7 hours. My secret? MIUI with 1800mAh battery. 'Nuff said.
How long battery life do the people with those giant 3600mah batterys have? Just wonderin
Sent from my HTC Vision using XDA App
Pershoot sounds intresting.
How can I backup my current kernel just in case? NAND backup?
taob said:
In your screenshot, "Display" shows as only 1%. In my experience, unless you never actually turn on the screen, the display will tend to be the biggest power consumer. What brightness level do you have it set to? Can you please tap on "Display" and post a screenshot of that? I want to see how long your screen has been on during those 28 hours.
So are you just leaving the screen turned off the whole time?
Click to expand...
Click to collapse
most battery life brags come from people who dont really use their phones...
ill see if i can get actual screen on time. The point is not to brag rather to find the best config when people actually use their phones. That said 16 hours i was sleeping...