Database Develop

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

Nexus 4 SCREEN ON TIME *NEXUS 4 ONLY*

This will HOPEFULLY be the new and improved nexus 4 SCREEN ON TIME
(this is my first new post, i hope im doing it correctly :fingers-crossed:
i will be adding some rules and guidelines to this as well
****************************************************************RULES****************************************************************
- post screen on time and overall battery
- post kernel/rom used also frequencies/governors/voltages, etc
- ONLY NEXUS 4 SCREENSHOTS, ive seen other post with 6+ hours screen on which is nearly impossible in my opinion (unless u dont do anything but leave screen on and not do anything
- and please post any additional information you feel is needed to show what improved your screen on time, such as battery improving apps, or leaving data off, or just using wifi, etc ANYTHING YOU FEEL LIKE IT HELPED YOU, ADD IT IN YOUR POST
- this will aslo cut down a lot of questions from people constantly asking for kernel and rom combo.
so for example these screenshots ive attached
I use Franco Kernel 121 with Paranoid Android
I Leave data off ALWAYS when not using it, when i do have it on i have good reception for the most part.
I also used greenify, first time ever using it.
Undervolted via franco kernel 100 mV
normal daily apps are, appy geek, xda, and maybe some super hexagon here and there or some minor web browsing

Nice results.. but i cant do test..

Sent from my Nexus 4 using xda app-developers app

Paranoid android latest. Franco r121 -150mv interactive governor. And some minor tweaks in kernel settings
Sent from my Nexus 4 using xda premium

Battery %80 SOT 50mins,franco r121+stock awesome
Sent from my Nexus 4 using xda premium

I've had great battery life using:
- Stock 4.2.2
- franco's kernel r121
-- CPU limited to ~700Mhz when screen is off, no voltage changes, min cpu set to 300Mhz, max 1300Mhz)
- Greenify
- Wifi ON, GPS ON, NFC OFF
edit: I had to wait 5 minutes before I could edit the post so sorry if you viewed it while the pics were still missing

Is my phone special or something? I was getting 6+ hours of screen time on stock...
It's probably due to how I use it though (only texting/facebook/email/chat apps/flipboard/reddit...ie: no games/video)
Anyways I don't usually let it drain dry but I did for the purpose of seeing how long it would take (screenshots included). I'm running stock 4.2.2 with Matr1x 10.0 GPU-OC kernel with 75mV downvolt, CPU max at 1ghz and homebrew tuned interactive governor. The screen is almost always at 25%ish brightness unless I'm outside under direct sunlight when I need to max it (happened for about 20minutes durring this cycle) and also didn't have access to WiFi for most of this cycle so it was off for most of the time (plus a few other small tweaks).
2% remaining juice: 19:33:11 cycle with 13:11:31 of light use screen time

BrutalGreen said:
Is my phone special or something? I was getting 6+ hours of screen time on stock...
It's probably due to how I use it though (only texting/facebook/email/chat apps/flipboard/reddit...ie: no games/video)
Anyways I don't usually let it drain dry but I did for the purpose of seeing how long it would take (screenshots included). I'm running stock 4.2.2 with Matr1x 10.0 GPU-OC kernel with 75mV downvolt, CPU max at 1ghz and homebrew tuned interactive governor. The screen is almost always at 25%ish brightness unless I'm outside under direct sunlight when I need to max it (happened for about 20minutes durring this cycle) and also didn't have access to WiFi for most of this cycle so it was off for most of the time (plus a few other small tweaks).
2% remaining juice: 19:33:11 cycle with 13:11:31 of light use screen time
Click to expand...
Click to collapse
13hours screen on time......... i call BS! :laugh:

kurtyyyyyy said:
13hours screen on time......... i call BS! :laugh:
Click to expand...
Click to collapse
Either it's BS or somebody modded with twice the battery.

CrashTestDroid said:
Either it's BS or somebody modded with twice the battery.
Click to expand...
Click to collapse
Neither, the secret is in the governor and lack of WiFi/GPS use. Basically using the Matr1x kernel with the minimum clock at 192mhz (undervolted to 675mV) with a standard interactive governor with the only exception being the CPU is locked down to 2 cores and max clock of 540mhz (750mV) or single core at 1026mhz (875mV) depending on the number of threads, unless the GPU goes above 35% use for long enough at which point all 4 cores become accessible but limited at 1026mhz.
Yes it's not the smoothest experience but still very livable and on par with a Galaxy Nexus, games still run great (faster than stock due to lack of thermald and with the GPU OCed to 487mhz) but gaming/video does kill the battery several folds faster.
Basically with this setup the only real power drain is the screen itself as the internals use barely more than in screen off/deep sleep modes under what is "normal" use to me. Thus why the screen by itself accounts to 88% of the total drain. I recon I could probably get about 6-8 hours of back to back YouTube videos or Temple Run 2 on this governor but I can't say for certain as its very rare for me to game or even watch videos on my phone.

BrutalGreen said:
Neither, the secret is in the governor and lack of WiFi/GPS use. Basically using the Matr1x kernel with the minimum clock at 192mhz (undervolted to 675mV) with a standard interactive governor with the only exception being the CPU is locked down to 2 cores and max clock of 540mhz (750mV) or single core at 1026mhz (875mV) depending on the number of threads, unless the GPU goes above 35% use for long enough at which point all 4 cores become accessible but limited at 1026mhz.
Yes it's not the smoothest experience but still very livable and on par with a Galaxy Nexus, games still run great (faster than stock due to lack of thermald and with the GPU OCed to 487mhz) but gaming/video does kill the battery several folds faster.
Basically with this setup the only real power drain is the screen itself as the internals use barely more than in screen off/deep sleep modes under what is "normal" use to me. Thus why the screen by itself accounts to 88% of the total drain. I recon I could probably get about 6-8 hours of back to back YouTube videos or Temple Run 2 on this governor but I can't say for certain as its very rare for me to game or even watch videos on my phone.
Click to expand...
Click to collapse
Thanks for the explanation! I've tried undervolting on Samsung devices without success, they always crash, so I never bothered on the N4. UV on N4 now seems to work fine. When/if my N4 lasts for 2-3 days (a la Note II) it will be screenshot worthy.

Hmm something isn't sitting right with me. You see I've seen something similar happen within Android. The OS doesn't reset battery stats unless a complete charge(100%) is completed, if the user unplugs and does a partial charge their previous battery stats are sustained for the time being.
Now I'm not saying tc did this, but it's just a feeling of mine.
Sent from my Nexus 4 using xda app-developers app

Ace42 said:
Hmm something isn't sitting right with me. You see I've seen something similar happen within Android. The OS doesn't reset battery stats unless a complete charge(100%) is completed, if the user unplugs and does a partial charge their previous battery stats are sustained for the time being.
Now I'm not saying tc did this, but it's just a feeling of mine.
Click to expand...
Click to collapse
True but if that was the case the graph wouldn't be a constant downward slope and would go back up, also on the first screenshot you would see when it was charging at the bottom.

BrutalGreen said:
True but if that was the case the graph wouldn't be a constant downward slope and would go back up, also on the first screenshot you would see when it was charging at the bottom.
Click to expand...
Click to collapse
I mean the one worth 13hrs sot, it just sounds odd. Tc is okay because I've seen 6hrs, but 13 seems unnatural.
Sent from my Nexus 4 using xda app-developers app

CM10.1.0 stable & Franco kernel
Sent from my Nexus 4 using Tapatalk 4 Beta

Typical battery life for me. All stock.
Sent from my Nexus 4

This day was at work where i was travelling 4 hours on a train. Data was always on, put into flight mode in some areas where there was little to no signal which is represented on the graph. Used of national rail, facebook, instagram, pulse, evernote and majority of it was watching CSI on MX player.
Paranoid Android 3.99 with franco.kernel
50Mv underclock, using greenify, max cpu reduced to 1Ghz, using only 1 core as touch boost instead of default 2. Phone still performs and full CPU access available on high demand such as gaming.

BrutalGreen said:
Is my phone special or something? I was getting 6+ hours of screen time on stock...
It's probably due to how I use it though (only texting/facebook/email/chat apps/flipboard/reddit...ie: no games/video)
Anyways I don't usually let it drain dry but I did for the purpose of seeing how long it would take (screenshots included). I'm running stock 4.2.2 with Matr1x 10.0 GPU-OC kernel with 75mV downvolt, CPU max at 1ghz and homebrew tuned interactive governor. The screen is almost always at 25%ish brightness unless I'm outside under direct sunlight when I need to max it (happened for about 20minutes durring this cycle) and also didn't have access to WiFi for most of this cycle so it was off for most of the time (plus a few other small tweaks).
2% remaining juice: 19:33:11 cycle with 13:11:31 of light use screen time
Click to expand...
Click to collapse
This is definitely cheating. Those grapghs show clearly that you just let the phone with the screen on above half the time, without even touching it. On the half of the graph I can see you used that Reader app and then you let the phone alone again.

(GUIDE) Get 6 hours screen on time.

This guide is for people who don't know much about changing kernel settings, etc. Experienced members should leave now.
All flaming will be ignored.
Please, for anyone who will complain that there's no point in disabling everything that makes your smartphone smart, please leave now.
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will. Everyone's phones are different. And how we use them is different too. This is just a thread containing guidelines to help you get the most battery.
Please note that performance may be affected.
Your ROM shouldn't matter too much. But I personally use AXI0M.
Kernel: This matters a lot. I personally use Air Kernel #10, the O2 version. This yields the best battery for me. If you use a different kernel, please don't complain that this guide doesn't have the desired results.
--------------- --------------- --------------- ---------------
All of these settings are optional but will help a lot.
Sync - off.
Screen brightness - 50% or less.
Wifi - on. 3g uses more battery.
NFC - off.
Use 2g networks only - on.
Auto rotate - off.
--------------- --------------- --------------- ---------------
--------------- --------------- --------------- ---------------
These settings, again are optional, but highly recommended. Please don't complain about this guide if you don't use these settings.
Governor: Wheatley
Minimum frequency: 286Mhz
Maximum Frequency: 1.118Ghz
GPU Maximum frequency: 400
Hotplug control/Maximum online CPUs - 2, minimum online CPUs - 1.
Undervolt: This is up to you. Find what is stable for your device. I don't undervolt at all.
All other settings should be left as default.
--------------- --------------- --------------- ---------------
That's it. Give it 2-3 charging cycles or a few days for the settings to settle. And then you should get optimum battery results with minimum effects on your performance.
Sent from my Nexus 4 using xda app-developers app

okmijnlp said:
This guide is for people who don't know much about changing kernel settings, etc. Experienced members should leave now.
All flaming will be ignored.
Please, for anyone who will complain that there's no point in disabling everything that makes your smartphone smart, please leave now.
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will. Everyone's phones are different. And how we use them is different too. This is just a thread containing guidelines to help you get the most battery.
Please note that performance may be affected.
Your ROM shouldn't matter too much. But I personally use AXI0M.
Kernel: This matters a lot. I personally use Air Kernel #10, the O2 version. This yields the best battery for me. If you use a different kernel, please don't complain that this guide doesn't have the desired results.
--------------- --------------- --------------- ---------------
All of these settings are optional but will help a lot.
Sync - off.
Screen brightness - 50% or less.
Wifi - on. 3g uses more battery.
NFC - off.
Use 2g networks only - on.
Auto rotate - off.
--------------- --------------- --------------- ---------------
--------------- --------------- --------------- ---------------
These settings, again are optional, but highly recommended. Please don't complain about this guide if you don't use these settings.
Governor: Wheatley
Minimum frequency: 286Mhz
Maximum Frequency: 1.118Ghz
GPU Maximum frequency: 400
Hotplug control/Maximum online CPUs - 2, minimum online CPUs - 1.
Undervolt: This is up to you. Find what is stable for your device. I don't undervolt at all.
All other settings should be left as default.
--------------- --------------- --------------- ---------------
That's it. Give it 2-3 charging cycles or a few days for the settings to settle. And then you should get optimum battery results with minimum effects on your performance.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What app do you use to achieve these settings?
Sent from my Nexus 4 using xda premium

adamski123 said:
What app do you use to achieve these settings?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Trickster mod, the free version .
Sent from my Nexus 4 using xda app-developers app

okmijnlp said:
Trickster mod, the free version .
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Basically you are downgrading the performance of the Phone by under-clocking the CPU.
What would be more beneficial is to find a way where we don't have to sacrifice the performance of the phone for Battery life.
Stock rom and faux stock enhanced kernel gives me the best performance and Battery life.
It also helps to hibernate the rouge apps that are constantly waking the phone during deep sleep by using Greeninfy app.
Thanks

okmijnlp said:
(GUIDE) Get 6 hours screen on time.
Click to expand...
Click to collapse
okmijnlp said:
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will.
Click to expand...
Click to collapse
In any case, here's some general guidelines:
- Undervolting, Underclocking, and disabling cores make the device use less power
- Lowering brightness makes the device use less power
- Turning off wireless signals makes the device use less power
- Using lesser signals (2G Cellular, 2.4GHz WiFi) makes the device use less power
- Having higher signal strength makes the device use less processing power, and thus, use less power
Most of that is just common knowledge though, maybe aside from the lesser signals thing. I don't really see anything in this guide as anything significant. It's basically saying "restrict your device's processing power for more battery", which is pretty much true for... anything.
Edit: As for the kernel, I can't think of any significant difference this would make either. Still uses the same drivers and same Linux kernel base, and most kernels have the same optimizations. Only things I can think of that would make a difference is if it came pre-UV'd or implemented a longer WiFi scan interval.
Edit: Somehow I failed to read the very first sentence (or skimmed over it completely, idk)... I should've just left

I never understood the cripple and downgrade your phone for battery thing but whatever floats your boat I guess.
Sent from my Nexus 10

**** yeah, disable two cores and get better battery life. Using airplane mode helps even more

Wow this is awesome! Will try it out
Sent from my GT-N7000 using Tapatalk 2

I can get 4.5 to 5.5 hours of screen on time (browsing, whatsapp, hangouts, some gaming) using auto-brightness, WiFi throughout, and a good signal zone without crippling the phone so such an extent. Getting 6 hours of screen on time is great....but if it isn't doing anything when you're not using it....not sure why you need a smartphone.

Actually, I found the that the phone is still pretty snappy when you turn off two of the cores...I don't think you have to lower all the way to 1.118, maybe 1.3 or 1.25 should be sufficient enough plus some undervolting. Screen brightness more than anything is the biggest factor though IMHO. Hope you guys get some good results.

Brightness alone makes up for almost everyone's battery issues.
-Sent from Marino's Nexus 7-

Honestly do not see the point in disabling everything that makes a smart phone.. well smart.. but I guess it's a good guide for people that just want their phone to last.

can anyone tell me what they are using to test out how stable the phone is when undervolting? What guide lines are there, what is a good indicator that the amount you under volt still leaves stability?

Meh, I've gotten almost 9 hours of screentime. Wifi on all day(no data), GPU: 487, matr1x kernel.
http://forum.xda-developers.com/attachment.php?attachmentid=1906921&d=1366769307
Can't seem to post the image url, so click that link for the screenshot.
Thats the wrong image... I'll post the one with 9 hours when I have time.

desertflame said:
Meh, I've gotten almost 9 hours of screentime. Wifi on all day(no data), GPU: 487, matr1x kernel.
http://forum.xda-developers.com/attachment.php?attachmentid=1906921&d=1366769307
Can't seem to post the image url, so click that link for the screenshot.
Thats the wrong image... I'll post the one with 9 hours when I have time.
Click to expand...
Click to collapse
What were you doing with the phone? Leaving it on a static screen with 10 minutes screen timeout time? Lol.

Just get the Caffeine app and leave your screen on all night while you sleep. Getting high screen on times is easy!
Sent from my Nexus 4 using Tapatalk 2

I personally leave network off, WiFi off, auto brightness
384MHz min, 1.512GHz max, intellidemand, disable mpdecision, 400MHz GPU ondemand, -100mV to all frequencies, and greenify EVERY single app so I don't get a wake lock. I can last over 2 days without charging and getting at least 4 hours of screen. But I mainly just text on my phone and listen to music. No games or much else
Sent from my Nexus 4 using xda app-developers app

Well using airkernelv8.......284mhz-1512mhz....everything one WiFi,2g,facebook,twitter,g+ etc..
Enviado desde mi Nexus 4 usando Tapatalk 2

Airplane mode+low brightness +no wifi+underclocked proc...8hrs plua sot guaranteed :thumbup:
Sent from my Nexus 4 using xda premium

Question regarding total amount of active CPU cores..

I did some checking in the .sh files, inside the /system/etc folder, and found inside the set_governor.sh that the Z1 is pre-configured to keeping all 4 CPU cores online at the same time. For performance reasons it seems..
Should I delete every line that is related to total amount of online / active cores so the kernel can decide and take care about that by itself or should I echo 0 the amount of cores that I want to be in sleep / idle mode?
I am tweaking my brand new Z1 for even more battery life, that's why I am asking this question!

Destroyedbeauty said:
I did some checking in the .sh files, inside the /system/etc folder, and found inside the set_governor.sh that the Z1 is pre-configured to keeping all 4 CPU cores online at the same time. For performance reasons it seems..
Should I delete every line that is related to total amount of online / active cores so the kernel can decide and take care about that by itself or should I echo 0 the amount of cores that I want to be in sleep / idle mode?
I am tweaking my brand new Z1 for even more battery life, that's why I am asking this question!
Click to expand...
Click to collapse
All four cores are not online at the same time all the time. At idle, only 1 core is active at min frequency 300 mhz, the other cores come online when there is demand for them. Disabling cores has never helped improve battery life in my experience, merely causing slow downs and resulting in the CPU taking longer to complete processing, using up precious power before it's able to return to min frequency.
(My limited knowledge)

tomascus said:
All four cores are not online at the same time all the time. At idle, only 1 core is active at min frequency 300 mhz, the other cores come online when there is demand for them. Disabling cores has never helped improve battery life in my experience, merely causing slow downs and resulting in the CPU taking longer to complete processing, using up precious power before it's able to return to min frequency.
(My limited knowledge)
Click to expand...
Click to collapse
If this is the case - why does kernel modules like ECO-Mode exist that shuts down two cores and converts the phone into an DC one?
Sent from my C6903 using XDA Premium 4 mobile app

Destroyedbeauty said:
If this is the case - why does kernel modules like ECO-Mode exist that shuts down two cores and converts the phone into an DC one?
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Eco mode? Never heard of it. Don't know anything that makes the Xperia Z1 go dualcore mode, might want to show me a link?
Ps. Tried underclocking with fauxclock or trickstermod?
Sent from my C6903 using Tapatalk

Why would anyone want to lower speed or nr of cores active on a beast like this? Go buy an older phone if u want a slower one lol. It uses the power it needs to complete the tasks it is asked to do unless u got some crap laying in the background draining your battery that way.

McT1980 said:
Why would anyone want to lower speed or nr of cores active on a beast like this? Go buy an older phone if u want a slower one lol. It uses the power it needs to complete the tasks it is asked to do unless u got some crap laying in the background draining your battery that way.
Click to expand...
Click to collapse
This have nothing to do with get a slow device. This probably will help avoid battery drain and without a few test no body can said it will not work.

eclyptos said:
This have nothing to do with get a slow device. This probably will help avoid battery drain and without a few test no body can said it will not work.
Click to expand...
Click to collapse
What battery drain are you referring to? When people talk about battery drain they usually mean when screen is of and they usually got some crap running in the background. I can get 2-3 days of moderate usage running dooms kernel and that's not bad.

McT1980 said:
What battery drain are you referring to? When people talk about battery drain they usually mean when screen is of and they usually got some crap running in the background. I can get 2-3 days of moderate usage running dooms kernel and that's not bad.
Click to expand...
Click to collapse
Any core need energy, trying to switch them off when not needed can only improve battery standby. This is not the solution for the battery, this is one of many. We know that the crap running in background it's another reason and the screen too. Here we considering only the CPU.

eclyptos said:
Any core need energy, trying to switch them off when not needed can only improve battery standby. This is not the solution for the battery, this is one of many. We know that the crap running in background it's another reason and the screen too. Here we considering only the CPU.
Click to expand...
Click to collapse
Agreed, but it would surprise me if the phone runs at 4x300mhz when the screen is of. 1 core is enough and i've seen several posts saying that it runs with 1 when the screen is of. If it runs at 4 however,yeah you could save some juice by disabling cores.

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.