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.
Related
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.
So I know the Faux kernal has the governors built in to it, and it's meant for performance.
anyone have suggestions on how to make it as much energy efficient as possible? I don't run the clock speed at 1.5 or 1.7 i usually have it on 1.3-4. Also I undervolted 1 time -12
will undervolting save more battery, or not really, should I clock it down to 1.2 or maybe even 1 when im not using my phone a lot?
I don't want the stock kernel because it just seems weak and I like having the option of going to 1.5 or 7 when i want to. also faux's kernel has a lot of performance and battery saving things already.
and also will undervolting do anything bad? if i undervolt too much it'll bootloop im assuming because not enough power but does it cause unnecessary cpu usage to make up for less volts?
That's a good question... I don't know the answer...
However... I have my phone -50 mV across the board... It's very stable... No reboots and every game runs fine...
At one point I had it set at -75 and some games would hang to the point where I had to pull the battery... Not sure if it was from the tweak or if it was something else....
I have one question though... Sometimes I open system tuner... And my governor has switched itself back to on-demand... Is that by design as part of intellidemand... Or is the governor just not sticking?
Sent from my HTC PH39100 using Tapatalk 2
rignfool said:
I have one question though... Sometimes I open system tuner... And my governor has switched itself back to on-demand... Is that by design as part of intellidemand... Or is the governor just not sticking?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Not sticking. I don't really like System Tuner. I just use SetCPU instead.
Sent from my HTC Velocity 4G using XDA Premium App
I am using faux's kernel as well and my battery just went flat right now after around 14hrs of pounding the phone. I mean over 3hrs of phone calls, about 1.5hrs of music streaming over bluetooth, downloading and updating more than 20 apps over wifi, texting, facebook and web browsing over 4G and about 30mins of mx video player. I am at 1.5 with intellidemand. No other tweaks. My point is that the cpu and the kernel seem pretty optimized. I don't think that, other than underclocking, changing the kernel settings would improve battery life much more, probably at the cost of stability.
been on it for a few days and....
Not to sure about battery life yet myself. Im also new to this phone (Vivid). Had a hacked droid a few years ago until it was stolen. Still learning hax0ring and kerneling again. Over all I like faux's kernel and P'Gs rum float B4 ROM.
More later I Guess...
I usually end my day with anywhere between 40% and 60% left on the clock.
648/192 intellidemand, no UV. Typical use is heavy web browsing (at least 3h), XDA surfing (1h) and music (about 1-2h). Calls are occasional at best, as is app use (read: emulators, WWF, DrawSomething).
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.
A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.
please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings
so overclocking makes things faster.. really? who would have thunk. and you just found this out?
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?
well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **
If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.
No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.
zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100
is there any kernel that can overclock with 4.3?
Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:
simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?
Check the Development sections.
This thread makes my head hurt.
I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Set cpu is working for me, I have the paid version though. I put it on performance governor and it held 1 core wide open at 2265. I then changed it to ondemand and the core dropped to 300. There's also a conservative, interactive, user space and power save governors. Search governors for explanation of each governors settings/purpose.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
kitsinni said:
I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Click to expand...
Click to collapse
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
@rbiter said:
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
Click to expand...
Click to collapse
so this may be a dumb question, but is 300MHz the lowest clock speed it can reach? I just installed Better Battery Stats on my Nexus 7 (2012) and it can get down to 50MHz. Just looking to conserve more battery. Thanks!
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
That's not really an option for me. I often rock the phone with no case at all and like it in its 168g form. I already have 30-40 hour batterly life with 3-4 hrs of screen time. But I just noticed the lowest clock speed it 300Mhz and I think it can be lower!
Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
Yes! This is my solution. No worries when mpdecision gets stuck on 4.4.2 and stops sleeping cores, who cares?! Pry-Fi running continuously in War mode, booyah.