Database Develop

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.

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.

Any tweak that balances out active CPU cores?

Is it anyone that can share and care with me some kind of modifying / tweaks that shuts down how many CPU cores that is active at the same moment? My problem is that battery life is suffering thanks to the CPU is working at an high level even when using simple tasks like browsing the web thru the built in web browser.
Help me please..
Skickat från min C6603 via Tapatalk 2

Destroyedbeauty said:
Is it anyone that can share and care with me some kind of modifying / tweaks that shuts down how many CPU cores that is active at the same moment? My problem is that battery life is suffering thanks to the CPU is working at an high level even when using simple tasks like browsing the web thru the built in web browser.
Help me please..
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
Download system tuner or get this app: https://play.google.com/store/apps/details?id=com.teamkang.fauxclock
And then just look at your cores. 97% of the time there is just 1 core working (on my phone).
Faux's app is about the same as CPU Spy, but Faux123 Kernel Enhancement Pro can also tell/show you the amount of time that all 4 cores were being used. Which is really barely never. If it's different in your case then you could do some tweaks, but I really doubt that it will be different then my phone. In the end it also depends what you use your phone for of course.

Dsteppa said:
Download system tuner or get this app: https://play.google.com/store/apps/details?id=com.teamkang.fauxclock
And then just look at your cores. 97% of the time there is just 1 core working (on my phone).
Faux's app is about the same as CPU Spy, but Faux123 Kernel Enhancement Pro can also tell/show you the amount of time that all 4 cores were being used. Which is really barely never. If it's different in your case then you could do some tweaks, but I really doubt that it will be different then my phone. In the end it also depends what you use your phone for of course.
Click to expand...
Click to collapse
If 1 one core is used - why is my battery draining like crazy? I am greenifying every known battery eating app that is installed on my phone but even then, I got bad battery life on my Xperia Z it is two days old though..
Skickat från min C6603 via Tapatalk 2

Destroyedbeauty said:
If 1 one core is used - why is my battery draining like crazy? I am greenifying every known battery eating app that is installed on my phone but even then, I got bad battery life on my Xperia Z it is two days old though..
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
Yeah well... if anything... The least you should worry about are you cores.
Have you installed BBS/CPU Spy to see if your phone is going into sleep mode correctly?

Dsteppa said:
Yeah well... if anything... The least you should worry about are you cores.
Have you installed BBS/CPU Spy to see if your phone is going into sleep mode correctly?
Click to expand...
Click to collapse
My phone enter Deep sleep pretty quickly so it is nothing wrong with Deep sleep and sleep mode.
Maybe undervolting of stock kernel frequencies can help me with the fast battery drainage? I mean, my battery life is good but undervolting can make it better?

Turn off gps,google now,every vibration and unnecesary keyboard,dial sound.
The battery life will be better.
◇C6603

beni8978 said:
Turn off gps,google now,every vibration and unnecesary keyboard,dial sound.
The battery life will be better.
◇C6603
Click to expand...
Click to collapse
Already fixed.

Destroyedbeauty said:
My phone enter Deep sleep pretty quickly so it is nothing wrong with Deep sleep and sleep mode.
Maybe undervolting of stock kernel frequencies can help me with the fast battery drainage? I mean, my battery life is good but undervolting can make it better?
Click to expand...
Click to collapse
I guess UV helps to improve the battery life, but I don't know how much. The great thing of UV is that the phone also doesn't become too hot.

Destroyedbeauty said:
If 1 one core is used - why is my battery draining like crazy? I am greenifying every known battery eating app that is installed on my phone but even then, I got bad battery life on my Xperia Z it is two days old though..
Skickat från min C6603 via Tapatalk 2
Click to expand...
Click to collapse
Hey don't forget to let your phone settle down 2 days isn't enough. It needs around one week
Sent from my C6603 using xda premium

brightness is what taking the battery, I dont know what phone u came from but battery is pretty much a disappointment on this phone. I came from an S3 with a 7000mah battery, so yea it sucks.

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.

Undervolting vs Underclocking vs Hotplugging for battery life

Can anyone explain to me what is better?
I know that underclocking reduces cpu frequency, which means lower temperatures and also better battery, but performance is worse, so it takes longer to complete tasks...but if it takes longer to complete tasks, it means it will also have screen on for a longer time right?so it saves power from the cpu, but keeping the screen on for that extra time also means it will consume extra power right?
About undervolting, is it better to undervolt or to underclock when it comes to battery life?i know that with undervolting there is less heat produced because of the reduced voltages. From what i have read (i dont know if it is correct) the power consumption is given by this equation: P = f*c*(V^2) where f is frequency, c is capacitance and v is voltage. It makes sense that reducing voltage means less heat, but if i reduce CPU frequency it also produces less heat because it reduces power. Most of the time i read that underclock is better for battery because it uses less power, but like i said earlier, it takes longer to complete tasks and in result i have to keep the screen on for a longer time.
About hotplugging, i have seen some users with good battery life screenshots, and mentioning that they disabled hotplugging, because they said that turning cores on and off also wastes energy. So is it better to hotplug or not?
would really like to get some answers because i know nothing about this..I also know that i could test each setting and and see which is better, but i dont use my phone the same way everyday so its kind of hard to determine...

Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT

RASTAVIPER said:
Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT
Click to expand...
Click to collapse
nice to have some feedback from someone that tested=p. what about hotplugging? Today i disabled hotplugging and had always 4 cores on and it does not seem to be wasting more battery than with hotplugging enabled

These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4

n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
Also lot of discussion about Uv here
http://forum.xda-developers.com/showthread.php?t=2137034
Unleashed from Onda v957m on TDT

n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?

migueldbr said:
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?
Click to expand...
Click to collapse
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).

C4SCA said:
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).
Click to expand...
Click to collapse
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...

migueldbr said:
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...
Click to expand...
Click to collapse
Different things but on stock kernel touch boost is implemented on the hotplug and not the governor.
Any difference btw 4 cores online or hotplugging must minor, and have draw backs on heat wich affects the battery capacity.
Eventhough u can say that hotplugging may drain an amount of battery to plug and unplug cores, i would say its minor.
Talk to @simms22 , he is the "trinity kernel guy", four cores online is a must for him
sent from my diabetic Nexus 4 (too many KitKats).

From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app

Oxious119 said:
From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
no matter what you do , its still going to be a mediocre battery life , best leave it as it is because the way nexus 4 is designed its still going to be getting annoyingly warm on games

Well, from my own experience undervolting definetly reduced heat and made the battery last longer. Don't expect 2 hours more sot, though. Its most notably while the device is idle.
Sent from my Nexus 4 using XDA Free mobile app

nice man
very helpful...

Help pls..
Can any1 help me undervolting Unleashed kernel.. providing tips or the link ll be vry helpfull..