Database Develop

Battery Life considerably shorter [CM7] OC 1.1Ghz

Hi
So I have a rooted Nook Color with CM7 Nightly Build 41 and Dalingrin's OC Kernel running at 1.1Ghz max / 800Mhz min. I have not disabled Cell Standby and i use Launcher Pro. My Nook's battery life seems to be less than 5 hours while i have seen other people get 10+ hours in the same situation. I have been using it considerably but i would think that my battery life would be greater.
One thing to note is that i did NOT fully charge the nook before using it like it said. Would this be the cause of such a low battery life? If so are the batteries replaceable?
Thanks
Moriarty

B_Moriarty said:
Hi
So I have a rooted Nook Color with CM7 Nightly Build 41 and Dalingrin's OC Kernel running at 1.1Ghz max / 800Mhz min. I have not disabled Cell Standby and i use Launcher Pro. My Nook's battery life seems to be less than 5 hours while i have seen other people get 10+ hours in the same situation. I have been using it considerably but i would think that my battery life would be greater.
One thing to note is that i did NOT fully charge the nook before using it like it said. Would this be the cause of such a low battery life? If so are the batteries replaceable?
Thanks
Moriarty
Click to expand...
Click to collapse
And what are you doing for those 5 hours? Games?

B_Moriarty said:
Hi
So I have a rooted Nook Color with CM7 Nightly Build 41 and Dalingrin's OC Kernel running at 1.1Ghz max / 800Mhz min. I have not disabled Cell Standby and i use Launcher Pro. My Nook's battery life seems to be less than 5 hours while i have seen other people get 10+ hours in the same situation. I have been using it considerably but i would think that my battery life would be greater.
One thing to note is that i did NOT fully charge the nook before using it like it said. Would this be the cause of such a low battery life? If so are the batteries replaceable?
Thanks
Moriarty
Click to expand...
Click to collapse
its because you have 800mhz min, set it to like 300

Well thats including standby but i have been running emulators for N64 and NES etcetera, But it seems like even without running games the battery drains rather quickly
Heres my Battery Statistics:
Display: 57%
Phone Idle: 9%
Cell Standby: 8% (Yes i know this can be disabled)
Android OS: 7%
Market: 5%
Dolphin Browser HD: 4%
Bluetooth: 3%
Wi-Fi: 3%
Cordy: 3%

Will setting it to 300 affect any performance negatively? Whats the benefits of having a higher min?

B_Moriarty said:
Will setting it to 300 affect any performance negatively? Whats the benefits of having a higher min?
Click to expand...
Click to collapse
it will not make the performance worse. setting it to 300 means that when the nook is doing nothing it will be at 300mhz which uses less power and battery.

EverythingNook said:
it will not make the performance worse. setting it to 300 means that when the nook is doing nothing it will be at 300mhz which uses less power and battery.
Click to expand...
Click to collapse
^this, instead of idling at 300, with your settings you are running at 800 all the time, thus your battery life is terrible. also set governor to interactive. if you have it at performance it would be running your nook at 1.1 all the time.

I think the default governor on Dalingrin's kernel is set to ondemand. Is interactive batter with battery life?

d00med said:
I think the default governor on Dalingrin's kernel is set to ondemand. Is interactive batter with battery life?
Click to expand...
Click to collapse
Conservative is better with battery life. Dal recommends interactive, since when the screen sleeps it drops to the min cpu setting and can go up to max if necessary. If you want a little more power he recommends setting interactive min to 600 although this will hurt battery life some. He never recommends performance as that keeps cpu running at max only.
There is a new testing 4/24 OC with max of 1300 for most and 1200 if 1300 does not work for your nook. He say that this has little effect over 1100 as the majority of battery life is determined by the display. I am using 4/23 OC at 1300 max, 300 min, governor interactive. The 4/24 OC kernel has the additional 1200 setting plus other improvements. I will probably upgrade to it.

B_Moriarty said:
Well thats including standby but i have been running emulators for N64 and NES etcetera, But it seems like even without running games the battery drains rather quickly
Heres my Battery Statistics:
Display: 57%
Phone Idle: 9%
Cell Standby: 8% (Yes i know this can be disabled)
Android OS: 7%
Market: 5%
Dolphin Browser HD: 4%
Bluetooth: 3%
Wi-Fi: 3%
Cordy: 3%
Click to expand...
Click to collapse
erm... how do you disable cell standby?
edit: nevermind, i found it

bradputt said:
erm... how do you disable cell standby?
edit: nevermind, i found it
Click to expand...
Click to collapse
You don't. It's pointless and just causes other problems, such as your volume keys won't work..

So how is battery life with the latest stable or nightly build?
I'm going to take the plunge and install CM7 tonight coming from an autonootered Nook running 1.1.
I've read that the devs have found a fix, just wondering if they have filtered into the newest builds.

GSUBass05 said:
So how is battery life with the latest stable or nightly build?
I'm going to take the plunge and install CM7 tonight coming from an autonootered Nook running 1.1.
I've read that the devs have found a fix, just wondering if they have filtered into the newest builds.
Click to expand...
Click to collapse
I've been getting verily bad batter life with my Nook (7.03 stable) and SetCPU at 1200/1300Mhz with interactive. I've played with it for 2.5 hrs and it has dropped 30%. Mind you, I watched one 30 min tv show, played two games for maybe 20-30 minutes, and browsed online and taptalk the rest of the time. Display settings are very low at 20%.

You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App

ramiss said:
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I am using the OC kernal and then setting it with SetCPU. AM I suppose to set the OC through CyanogenMod settings instead?
Sent from my Atrix 4G using Tapatalk Pro

ramiss said:
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
So, how would you set your low value (i.e. at 300) without SetCPU? I don't recall the default CM7 settings having this option (just the high OC).

crea78 said:
I've been getting verily bad batter life with my Nook (7.03 stable) and SetCPU at 1200/1300Mhz with interactive. I've played with it for 2.5 hrs and it has dropped 30%. Mind you, I watched one 30 min tv show, played two games for maybe 20-30 minutes, and browsed online and taptalk the rest of the time. Display settings are very low at 20%.
Click to expand...
Click to collapse
Only had battery drain 2% from 12:30 to 7 am. I am really liking this build.

dohturdima said:
So, how would you set your low value (i.e. at 300) without SetCPU? I don't recall the default CM7 settings having this option (just the high OC).
Click to expand...
Click to collapse
CM7 allows you to set Min/Max CPU Frequency as well as governor from within its own menus.
Settings -> CyanogenMod settings -> Performance -> CPU settings.

GSUBass05 said:
So how is battery life with the latest stable or nightly build?
I'm going to take the plunge and install CM7 tonight coming from an autonootered Nook running 1.1.
I've read that the devs have found a fix, just wondering if they have filtered into the newest builds.
Click to expand...
Click to collapse
The fix isn't in the stable or any of the nightlies yet. The most recent nightlies have a different fix, which prevents the speaker from running constantly, so the battery life will be better than it used to be, but nowhere near as good as you would get with real deep sleep.
The real deep-sleep fix is in the CM7.1-RC0-beta3.1 build. Its still a beta, and a few people have had some glitches, but it is running fine for me. And my nook now has the kind of battery life it had on rooted stock (before being unable to prevent an auto-update nudged me to CM7).

ramiss said:
You aren't supposed to run SetCPU with CM7. Use the built in OC function and/or install an OC kernel.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
you can run setcpu actually. the thing you can't do is run profiles on pre-beta kernels with setcpu.
set your minimum to 300mhz no matter what you use.. anything else is overkill that will result in battery kill..
in addition phone, mms, and telephoney apks have been proven repeatedly to have no impact on battery.
occasionally after flashing a new rom, recalibrateing your battery stats will do wonders.. ie. charge to 100% go into CW and reset battery stats, let it drain to below 10% then charge back to 100%. This is true of most Android devices.
The new beta build and kernels have improved battery a ton, they say these fixes will be incorporated to nightlys then stable CM7 eventually.

Galaxy Note Battery Life

Just got my note I was wondering if people could share their tips on how to get great battery life on the note!
any tips (even the most basic) will help all us first time Android users
So share your tips, apps, settings, etc!
Sent from my GT-N7000 using XDA App

If you want to save max battery. Turn off 3G and only use 2G. Then lower brightness. Reduce frequency of app updates.
Those are the best tips. I keep brightness on auto. And I keep updates to once an hour for most things. It give me a solid day.
Sent from my Samsung Galaxy Note.

Thanks!
I downloaded setCPU and have it so that the processor goes down to 800mhz when the screen is off.
I am not sure if that is helping or not though.. still struggling with battery life.

Get JuiceDefender Ultimate. It helps to automatically turn off your Data Network and your wifi whenever your not using your phone, it reopens them periodically to check for any updates on ur apps. Smart app and it has saved me x2.3 of my battery life.

thanks!
Do you think juice defender ultimate is better than setCPU?

Disable fast dormancy. *#9900# and the select disable fast dormancy and then save.
Sent from my GT-N7000 using xda premium

Here are some tips for prelonging battery life:
1 - Don't use 100% screen brightness at all times - 50-60% is enough, only increase it when you need to then lower it again.
2 - If your planning to use the phone for long periods, 30 minutes or more constant use then once again use 25% or so brightness
3 - When browsing/surfing the net use the lowest possible brightness as this is the biggest battery killer. Unfortunately our AMOLED screens suck a lot of juice when displaying white...
4 - Try to keep most, if not all applications to manual updates only. Otherwise decrease the update frequency.
5 - Use an alternative launcher. I find for example using LauncherPro uses less resources/cpu/ram than the default touchwizz launcher. Therefore using less ram/cpu saves battery!
6 - If your gonna game for hours then I suggest 0% brightness!
7 - Last but least watch your apps. Some apps are poorly optimized/coded and can take up a lot of ram and cpu which then eats away at your battery!

In my case, disabling fast dormancy helps save some battery. Tough not to a big extent.

Use Screen Adjuster or Voodoo display filter to further lower screen brightness.
Install and use app that has a night mode. Eg, config opera mobile to use a user css to render white text on black background.

Hey,
Before you should know that android collects statistics on your battery in order to "learn" its behavior so within the first days of use you will see a constant improvement if you battery performance.
there are also a few apps that runs in background and has the annoying habit to drain your battery:
wifi sharing
wi-fi sharing manager
social hub
try to disable those apps using gemini app manager or titanium backup.

Thanks for the great tips. My battery lasted almost 19 hours ever since I did everything everyone has mentioned!
Sent from my GT-N7000 using XDA App

uneek14 said:
Thanks!
I downloaded setCPU and have it so that the processor goes down to 800mhz when the screen is off.
I am not sure if that is helping or not though.. still struggling with battery life.
Click to expand...
Click to collapse
Capping the max CPU speed does not help battery life.
Sent from my Transformer TF101

this will also help you understand battery life
http://batteryuniversity.com/

Gary13579 said:
Capping the max CPU speed does not help battery life.
Sent from my Transformer TF101
Click to expand...
Click to collapse
How so? I've heard some people on YouTube say they save battery this way..it was the only reason I downloaded setCPU...what are your thoughts?
Sent from my GT-N7000 using XDA App

When screen is off, the cpu frequency is reduced anyway. Thats the advantage of sleep.
Sent from my GT-N7000 using XDA App

bud.de said:
When screen is off, the cpu frequency is reduced anyway. Thats the advantage of sleep.
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
How much is it reduced to?

kanej2006 said:
How much is it reduced to?
Click to expand...
Click to collapse
Just enough to receive calls, sms, messages, etc. What was it, 200mhz?

uneek14 said:
How so? I've heard some people on YouTube say they save battery this way..it was the only reason I downloaded setCPU...what are your thoughts?
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
YouTube is in no way a reliable source of information when it comes to technology. Unfortunately, neither are these forums, as witnessed by the masses of people that consistently state underclocking saves battery. I've posted about this several times before, and it seems no one ever listens or trusts me, so I'll try to lay it out as simple as I can. This effect is very well known by old school Linux nerds that would push their notebooks to get longer battery lives. Intel calls this effect HUGI -- Hurry Up and Get Idle. It essentially states that the faster a CPU runs, the more energy it consumes, but it *also* finishes it's work faster. Finishing work faster is important as it means that the CPU can go back to it's "Idle" state faster. The idle (or sleep) state uses virtually zero energy. Let me see if I can pull up the voltage table for a phone... here, found this for the Sprint Nexus S 4G and it looks to be accurate based off my memory of the CPU.
1000mhz - 1.25v
800mhz - 1.20v
400mhz - 1.05v
200mhz - 0.95v
100mhz - 0.95v
Now, let's say we have a task that takes 10 seconds to complete at 1000 MHz. 10 seconds times 1.25v is 12.5v (I know, I know, voltage doesn't work this way -- but it's a good enough approximation to demonstrate this effect (and it's to scale!) and I'm too tired to explain volt vs amp vs watt, it's 5am here). At 100 MHz, though, the *same exact task* would take 100 seconds! 100 seconds times 0.95v is, wow, 95v! By capping your CPU to 100 MHz (10% of max), you are effectively using (95/12.5=) 660% more energy to do the same task.
Now, there are scenarios where underclocking can help you, such as when your phones CPU is running at 100% 24/7 because of ****ty applications or leaked wakelocks. Although underclocking does appear to somewhat fix this, it's a complete ****ing hack and won't give you anywhere near the amount of battery life that you'd get by uninstalling the ****ty app and letting your phone go to sleep.
Make sense?
Sent from my Transformer TF101

Wow! Thanks! yeah it does make sense! I guess I should uninstall setCPU...I'm not sure what else its used for
thanks again
Sent from my GT-N7000 using XDA App

zkyevolved said:
Just enough to receive calls, sms, messages, etc. What was it, 200mhz?
Click to expand...
Click to collapse
That's great, a very efficient way to save battery...
So it's basically like a modern pc running a core i5/i7 that runs at 2.5GHz when idle or when no power is needed. However when power is needed the intel Turbo boost kicks in & increases clock speed to 4.2GHz or even higher depending on what the user set it to.
In my case my PC cpu idles at 3.4GHz & when gaming or video editing it boosts to 4.7GHZ which I've manually set it to.

Best mods (Root) for best battery life and phone speed?

I have basically every script/ mod right now done to my Revo and I use Antutu Battery saver running at level 3 (best battery saver level). I still dont feel like I get good battery life, even when not using the phone too much. I have my cpu set on rom Toolbox running 1900/ 255 on smoothass governor, which constantly switches at random. Does it switch because of my battery saver im thinking? Either way, Im trying to figure out if I should wipe my Revo and restart with just Blitz and Rom toolbox for better battery, with still good speeds. Any suggestions if I wipe clean? Or any suggestions on what to do right now? Thanks!

I'm guessing ur using gingervolt... I've had this same issue on my revolution... I've researched it and everything... I've found nothing
Sent from my VS910 4G using xda premium

Yes using gingervolt. Sorta stuck on what to do
Sent from my VS910 4G using XDA App

jmaxin07 said:
Yes using gingervolt. Sorta stuck on what to do
Sent from my VS910 4G using XDA App
Click to expand...
Click to collapse
I could be wrong but I'm guessing that setting 1.9gHz on the Max is just that, the Max. Not necessarily the "constant" CPU speed.
Sent from my Volted Ice Revo using Tapatalk.

Now this might not be the answer you were looking for, but I had found that even with multiple power-saving measure my battery-life was still terribly short. The best thing is to get an extended battery, the one for the Revo is beast in size and battery life. Also, since you didn't mention it, changing from LTE to CDMA is also good if you're not really needing your 4G speeds.

jmaxin07 said:
I have basically every script/ mod right now done to my Revo and I use Antutu Battery saver running at level 3 (best battery saver level). I still dont feel like I get good battery life, even when not using the phone too much. I have my cpu set on rom Toolbox running 1900/ 255 on smoothass governor, which constantly switches at random. Does it switch because of my battery saver im thinking? Either way, Im trying to figure out if I should wipe my Revo and restart with just Blitz and Rom toolbox for better battery, with still good speeds. Any suggestions if I wipe clean? Or any suggestions on what to do right now? Thanks!
Click to expand...
Click to collapse
Your battery life is probably not too good because of the 1900 mhz setting... I use set CPU and you can use different profiles (including screen off, charging, battery threshold below a certain percent, etc.). This helps, but I don't get great battery life without a program like JuiceDefender. The problem there is, though, that it slows my phone down to the point of it taking a minute to get working, and by that time I have already done what I need to do... sort of sucks.

Fallen224 said:
Now this might not be the answer you were looking for, but I had found that even with multiple power-saving measure my battery-life was still terribly short. The best thing is to get an extended battery, the one for the Revo is beast in size and battery life. Also, since you didn't mention it, changing from LTE to CDMA is also good if you're not really needing your 4G speeds.
Click to expand...
Click to collapse
I got the extended battery too and it is a world of difference. I can run all day and night without killing my battery. Even with moderate to heavy use, I can run through a whole day with no charger (and be comfortable). I just got mine through verizon for 24.99 the other week. I may have overpaid, but I don't trust amazon or ebay too much with some things.

samwelborn said:
Your battery life is probably not too good because of the 1900 mhz setting... I use set CPU and you can use different profiles (including screen off, charging, battery threshold below a certain percent, etc.). This helps, but I don't get great battery life without a program like JuiceDefender. The problem there is, though, that it slows my phone down to the point of it taking a minute to get working, and by that time I have already done what I need to do... sort of sucks.
Click to expand...
Click to collapse
I have an extended battery and I stay overclocked at 1.9gHz all day long. I don't use apps like juice defender or anything and I'm seeing 15-18 hours with moderate/heavy use.
Sent from my Volted Ice Revo using Tapatalk.

I use 5 different battery programs to monitor my battery and save my battery, but for some reason my battery drains in an hour.
The thing I see on here the most: monitoring programs, 4g connections, flashing left and right. People need to go to YouTube, and watch the video on how Android phones work. They are constantly learning what apps you use or don't use, they are learning how best to operate for your needs. When you flash a ROM or tweaks, it has to relearn. Sure track your battery for a day or two, see what programs are doing what and when, but then get rid of the extra crap, your phones don't need it. If you want extra battery life, get the bigger battery, you all knew coming to a smart phone that battery life sucks. Stop using app killers, and monitoring programs, they run in the background. Turn off auto run programs so one program doesn't start another.
Sent from my VS910 4G using xda premium

Has anyone measured the battery current? I would think if you are trying all these different setups and use scenarios the actual current draw is what you need to know.

markapowell said:
I use 5 different battery programs to monitor my battery and save my battery, but for some reason my battery drains in an hour.
The thing I see on here the most: monitoring programs, 4g connections, flashing left and right. People need to go to YouTube, and watch the video on how Android phones work. They are constantly learning what apps you use or don't use, they are learning how best to operate for your needs. When you flash a ROM or tweaks, it has to relearn. Sure track your battery for a day or two, see what programs are doing what and when, but then get rid of the extra crap, your phones don't need it. If you want extra battery life, get the bigger battery, you all knew coming to a smart phone that battery life sucks. Stop using app killers, and monitoring programs, they run in the background. Turn off auto run programs so one program doesn't start another.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
+1
the more programs running the more drain. Widgets are convenient but can be real power hogs. Simple and streamlined is the way to go for me. You can have an awesome looking / running phone by being selective with apps and avoiding redundancies. If i have an issue, i dl the program/s i want to troubleshoot with and when im done i uninstall. No need to use resources that could be used elsewhere. You can always dl the app again or save its apk to the external sd or a laptop or both (thats what i did). Ofc, it will have a new learning curve but settles in a couple days, for me anyway.
Sent from my VS910 4G using XDA App

Sucky battery life

I want to know if my phone is just reading the charge level wrong or if something is wrong. I am running Slim ICS newest version, I also have an extended 3500mAh battery. I am only getting about 8-10 hours of battery life. I am always on my phone and I am wondering if that's why its draining so much. Any suggestions would be appreciated.
Sent from my SGH-I897 using XDA

What do you mean by always on your phone? If your screen on time is 8-10 hours, that would explain the drain lol. You may just want to test it with different ROM/kernel combinations
Sent from my CM9 ICS i897 Captivate

korockinout13 said:
What do you mean by always on your phone? If your screen on time is 8-10 hours, that would explain the drain lol. You may just want to test it with different ROM/kernel combinations
Sent from my CM9 ICS i897 Captivate
Click to expand...
Click to collapse
Well my screen isn't always on but I mean I use it a bunch like I text a crap load and stuff
Sent from my SGH-I897 using XDA

Take a look at what you have running on your phone - widgets that grab updates, live wallpapers, and any other thing that runs in the background will add to your battery drain. It's pretty much an even tradeoff - the more you ask the phone to do, the faster the battery will go down. Just take a look at what you have running and decide what needs to be running and what can be taken away.

jmtheiss said:
Take a look at what you have running on your phone - widgets that grab updates, live wallpapers, and any other thing that runs in the background will add to your battery drain. It's pretty much an even tradeoff - the more you ask the phone to do, the faster the battery will go down. Just take a look at what you have running and decide what needs to be running and what can be taken away.
Click to expand...
Click to collapse
I have one widget and a program called quicker I constantly kill things with my task manager
Sent from my SGH-I897 using XDA

Do you do much gaming or web browsing on the phone? Both of those can be pretty heavy battery drains.
If not, and you're only getting 8-10 hours per charge with normal use (mostly calls, texts, some small amount of apps), then you may want to look at overclocking/undervolting to fine tune how your phone uses power.

jmtheiss said:
Do you do much gaming or web browsing on the phone? Both of those can be pretty heavy battery drains.
If not, and you're only getting 8-10 hours per charge with normal use (mostly calls, texts, some small amount of apps), then you may want to look at overclocking/undervolting to fine tune how your phone uses power.
Click to expand...
Click to collapse
I do some web browsing but nothing that would drain my battery this much, if you could help Me configure overclocking and undervolting that would be great I am running glitch kernel v14 b6
Sent from my SGH-I897 using XDA

Whoops
Posting in the wrong section. Whoops. I cant even delete my post now

The OC/UV setup is something you'll just have to play around with, as each phone handles them differently.
My suggestion (and I can't say I'm even remotely an expert on this) would be to leave the UV alone at first and try pushing the OC setting up and see how high your phone will run and still be stable, then back off by 1 level (giving you a buffer). Your phone can handle the higher level, but a difference of 100 MHz isn't going to be a massive boost and it runs the chip a little easier.
Once you've done that, then take a single notch of voltage off of all levels. See if that's stable, then repeat and see which settings are ones your phone will handle.

patrick8996 said:
I have one widget and a program called quicker I constantly kill things with my task manager
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
Hmm... Killing things isn't very good on battery life since it forces those services to restart again, eating up CPU and holding wake lock. Killing tasks is frowned upon in general and won't help battery life unless you are killing rogue CPU hogging apps.
You could try underclocking with glitch to the 800 MHz step, and setting live OC to something around 115%. It should perform well depending on the ROM, and yield better battery life than pure overclocking. You can also experiment with undervolting from there. Keep in mind that these things only affect battery life when the CPU is running, so basically when the screen is on. It won't save you power in deep sleep.
Sent from my CM9 ICS i897 Captivate

Battery life and CPU

Although this might seem as a question. It really isnt.
What kind of battery life do you get on the First? Screenshots would be nice, but what is like the max time and min time you got and what kind of setting do you use, voltage, clock speed, usage etc.
Also has anyone been using the MSM-DCVS (dynamic clock and voltage scaling) CPU Governer? And if yes then have you gotten better battery life? I will do a test tomorrow and see how it goes.
My best stats.
Well before i got into cpu governors, by default the phone uses on-demand and i could max out 14 hours with variable usage. screen on maybe 50% of the time the phone was on and minimal gaming. texting. I dont have data so that didnt take any battery (i hear 4g and 3g take away lots of juice, is that true?).

Okay. So just did a quick test with msm-dcvs.
Basically for 5 minutes I tested each governed doing the same stuff.
Msm-dcvs utilizes deep sleep ALOT more. Almost 8 times more than on demand. And doesn't really use anything in between. So it goes from deep sleep to minimum 300mhz to get it going and then jumps to the max of 1.4ghz and if the screen is on it uses 700mhz.
So using deep sleep it saves batter.
On demand on the other hand tends to use 300mhz instead of deep sleep. It also jumps around a lot between all the various clock speeds using just about anything it can. So i guess on demand will get worse battery life but I will report my findings in a few hours seeing bow battery life goes with dcvs.
Sent from my HTC first using XDA Premium 4 mobile app

Just a quick update. On demand is crap. Performance is really good and dcvs is performance just more intelligent
Sent from my HTC first using XDA Premium 4 mobile app

My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick

abrahammmmmmm_ said:
My battery life is crap. I've tried to adjust clock speed & voltage but I don't believe JMZ's latest kernel supports it and I'm never able to get any governors besides stock to stick
Click to expand...
Click to collapse
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
Use performance. It has a really fast "rave-to-idle" speed. This means that the phone will finish tasks faster and go to idle/deep sleep. So it should save you batter. Unless you don't mind lag and use msm-dcvs which is performance just it takes time to ramp up the speed.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What app do you use for this? All the ones I've tried don't make any custom settings stick

abrahammmmmmm_ said:
What app do you use for this? All the ones I've tried don't make any custom settings stick
Click to expand...
Click to collapse
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
CPU master by antutu. I've always used it. Best one there is
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?

It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.

G00fY2 said:
It's important for battery life, that the phone goes into deep sleep while screen is off. Use this app to test whether thats the case: BetterBatteryStats
Also you can see which process "wakes up" the phone while it should sleep.
My First normaly runs about 2 days without charging. So battery is pretty good!
PS: I'm using deodexed rom with stock kernel.
Click to expand...
Click to collapse
Wow that's great battery life.
I'm yet to test dcvs in my first and see how long that lasts me. I have Wi-Fi on all day. So I can get up to 14 hours max.
Sent from my HTC first using XDA Premium 4 mobile app

abrahammmmmmm_ said:
Alright I'll try the app. BTW I'm pretty sure 918mhz isn't the stock minimum... Must explain my horrible battery. What do you have yours on?
Edit: so far so good. I'm feeling some better battery life even tho it might just be a placebo effect I know that the CPU will have less strain & rest more now that the minimum is at 384. And few more questions, what do you have set for your I/O scheduler and also did you configure the voltage?
Click to expand...
Click to collapse
No I have yet to figure out io bit tinkering with voltage isn't a good idea since the battery is specifically set to a voltage the phone needs.
Sent from my HTC first using XDA Premium 4 mobile app

Okay I have some new findings. Idk about the custom kernel...bit with stock you only get 3 I/o schedulers. Noop, deadline, and cfq. Noop is first come first serve. Deadline reorders the task sequence and does what it thinks should come first...good for like gaming. And cfq. Which evenly distributes the power amongst all tasks. If you are using cfq make sure you kill unused tasks all the time. If you use a lot of things on your phone and multitask a lot use deadline. Noop is pointless unless you don't use your phone for anything. And cfq is just an alternative to deadline. So I/o won help much.
Then in CPU master. Go to advanced. And press "disable perflock". It will explain what it does. Hit set on boot. And reset you clock settings. Now we shall see what we get.
Sent from my HTC first using XDA Premium 4 mobile app

Okay guys. I used deadline to see if that would change anything. With the same dcvs setting with deadline I got 15% batter down in 2 hours. That's pretty good. That's 7.5% an hour.
And this is with screen on and wifi on about 70% of the time.
Sent from my HTC first using XDA Premium 4 mobile app

Okay this is my final say on how to get the most out of your battery life.
There are two set ups
1. Lag free/ smooth set up
Min 384mhz, Max 1080mhz
Governer: Performance
i/o Scheduler: Deadline
-This set up will save battery why? Because 1. You don not need your max 1.4 ghz to keep the phone running lag free, and in performance mode, the phone is LOCKED into 1.4ghz until you dim the screen and it goes into deep sleep. no inbetween. So clocking down will help save EVEN MORE battery. So unlike dcvs you will not have lag when you turn your screen on. It will jump from zero to 1ghz in a few milliseconds.
2. Inteligent
Min: 432mhz, Max 1.4ghz (default max. Dont over clock)
Governer: MSM-DCVS
i/o Scheduler: CFQ
-This set up will save battery, i go down about 1% every 6-20 minutes depending on usage. (6 being max usage and 20 meaning iddle). Once you turn the screen on your device will lag slightly and then will work just fine. This set up is good for those people who dont ALWAYS need max performance. Example: Reading an email doesnt require your phone to be locked at max frequency all the time so it will down clock the device. It simply takes time for it to rev the engine.
3. On Demand
Well this is simply absoule minimum to absolute maximum with NOOP as the i/o. This is the ultimate ondemand set up as it will do what you are currently doing first then do the rest while constantly changing clock speed.
Also...btw changing clock speed takes battery that is why performance saves batter not uses it. Its either deep sleep or max and thats it.
I will add screenshots to this soon once im done with all my tests.

Battery life today on msm-dcvs
I should be at 30% right now bit pretty good battery tight now
Sent from my HTC first using XDA Premium 4 mobile app

Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).

Hulo_ said:
Tried today MSM-DCVS scheduler on my stock rooted firmware. Don't like it. Lags a lot when screen on (and CPU at max 1.4Ghz). And i do not see any significant battery improvements, instead it seems that it takes longer time for phone to do background tasks like mail checking etc.
Concerning battery life - in general I receive 3-3.5 hours of screen time. And it can be 1 day to 3. It all depends on usage, but screen on time never goes above 4 hours.
In attached file - Stats for my phone while traveling from the U.S. to Russia. As you can see, delivery does not take very much time And in standby mode phone can last almost two weeks (with wi-fi and nfc on).
Click to expand...
Click to collapse
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!

russian392 said:
Personaly i dont have NFC or 4g on at any time. 1. i dont have data and 2. i dont use nfc cause the so called "modern world" is still stuc on stupid apple devices.
I noticed the following issues with managing the cpu
1. When setting cpu clock speed, after about 5 seconds after you left the app it changes the clock speed back to how it was
FIX: in cpu master (or the app of your choice) go to advanced and turn perflock off. then go to the cpu settings and set the speed you want. you must do that every time though cause of the htc kernel
2. MSM-DCVS lags.
FIX: set your minimum to 450-500 mhz
3. 4g drains batter (or so i hear)
FIX: idk yet but if someone could show me their battery life with 4g on and normal daily usage i could try to figure something out.
Hulo. Try this set up
Performance, 300mhz - 1080mhz, deadline
IDK my phone syncs things quite well and lag isnt a big issue for me, i can deal with it because my old phone overclocked is 700mhz so lag isnt anything new to me. So i just notch up the minimum to reduce it.
MSM-DCVS saves batter when screen is off and when screen is on but idle. playing games or actively using the screen will drain battery no matter what setting you use. This is made for people who are constantly on their phones.
Performance saves battery when screen is OFF period. When screen is on its at its max. this is best used for people who dont use their phones alot.
With dcvs i got an extra 7 hours of battery life. usually i get 11. But i hear with 4g on your battery dies in about 6 hours? is that true?!
Click to expand...
Click to collapse
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions

abrahammmmmmm_ said:
I'd just like to add that 4g actually consumes LESS battery than 2g/3g/3.5g only LTE tho. That's because it's more optimized and advanced I've read and experienced it in many occasions
Click to expand...
Click to collapse
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app

russian392 said:
Alright then. Interesting. My friend on his s3 gets 6 hours of battery with 4g.
Sent from my HTC first using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I should add that the optimized battery life for LTE is only true tho for new snapdragon CPU's including Apple's processors as well. I'm not aware of tegra or any exynos at the moment.