What do people get per charge?
Sent from my Nexus 5 using Tapatalk
I ususally get 1h 30min screen on time in whole day (around 15 hours).
EDIT: wifi and 3G turned on all the time, all sync enabled, on CM11 unofficial, variant 2
EDIT: @Adam77Root gonna try your settings
Mine's around 2h 30mins on normal usage, uptime is 13-14 hours. I charge in the evening, have the phone turned off at night. 2G data for about 5 hours (my 3G plan is over), Wi-Fi for 3-4 hours. I have all location services and all permissions from Google Play Services and mostly all from Search disabled. On latest Omni 4.4.2 with iodak v9.95, 51 MHz - 1.5 GHz, max screen off 475MHz, sio, interactive, multicore saving 1, max GPU 416MHz, SmartDimmer on, Dynamic fsync off, 3D scaling on, CPUQuiet balanced, max cores 4, LP undervolted 10mV, MP 50mV, my variant is 0. This is pretty decent in my opinion.
See my missus gets like 2h at most. So i see that's actually quite average. I thought it was pretty poo. Lol
Sent from my Nexus 5 using Tapatalk
I get about 3,5h of on screen time, a lot of internet on 3G/WiFi - that's what eats the most of the battery during the day.
Depends...it's crazy how some apps drain way more than others...
15 minutes of clash of c. drains as much as 1hr on yt.....
Battery saving apps have so many wakelocks they are usekess...
Automate it pro for total management
650 max screen off
1400 max cpu cap
520gpu
3g & wifi off when screen off
Forced sync every 60min
No gps unless travelling (automatic travel mode)
20-30 minutes bt per day with music stream
Only gmail as syncing app (no fb, watsapp etc...)
Greenified anything greenifiable (i am pretty sure that for my usage this app is useless)
2uccw widgets (with everything, mails, call, messages, location and weather)
nova as launcher
Onscreen time: On average little over 3hrs gaming, browsing and calls
Total running time before charge: 14hrs daily runtime
Artisto said:
I get about 3,5h of on screen time, a lot of internet on 3G/WiFi - that's what eats the most of the battery during the day.
Click to expand...
Click to collapse
Rudjgaard said:
Depends...it's crazy how some apps drain way more than others...
15 minutes of clash of c. drains as much as 1hr on yt.....
Battery saving apps have so many wakelocks they are usekess...
Automate it pro for total management
650 max screen off
1400 max cpu cap
520gpu
3g & wifi off when screen off
Forced sync every 60min
No gps unless travelling (automatic travel mode)
20-30 minutes bt per day with music stream
Only gmail as syncing app (no fb, watsapp etc...)
Greenified anything greenifiable (i am pretty sure that for my usage this app is useless)
2uccw widgets (with everything, mails, call, messages, location and weather)
nova as launcher
Onscreen time: On average little over 3hrs gaming, browsing and calls
Total running time before charge: 14hrs daily runtime
Click to expand...
Click to collapse
Bloody ell. 3h+! My missus would love that! Lol. What set up do you use?
Sent from my Nexus 5 using Tapatalk
Ben36 said:
Bloody ell. 3h+! My missus would love that! Lol. What set up do you use?
Click to expand...
Click to collapse
I've described it in other topic, so I'll just post a link - http://forum.xda-developers.com/showpost.php?p=52463422&postcount=242 ;]
And recently I usually keep my screen at minimum 25% of brightness - to admire how perfect it is - and it doesn't shorten battery life that much.
4h31mins is my best, but honestly, I can easily reach 3h45 mins with a normal usage (browsing the net, some youtube, forums like xda, some calls, SMS, whatsapp) I use iodak kernel with some custom settings regarding uV and uC (really smooth experience, anyway)
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Best stats i've seen so far..
Bloody ell, i think I might have to stick my missus on beanstalk! Lol
Sent from my Nexus 5 using Tapatalk
Hid3away said:
Best stats i've seen so far..
Click to expand...
Click to collapse
peppethustra said:
4h31mins is my best, but honestly, I can easily reach 3h45 mins with a normal usage (browsing the net, some youtube, forums like xda, some calls, SMS, whatsapp) I use iodak kernel with some custom settings regarding uV and uC (really smooth experience, anyway)
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that's nice can you please post which Rom, Kernal, settings those stats beat my best stats.
Sent from my LG-P880 using XDA Premium 4 mobile app
sPEADy said:
Wow that's nice can you please post which Rom, Kernal, settings those stats beat my best stats.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My signature talks for me
If you want to see my configuration, go here: http://forum.xda-developers.com/showthread.php?p=51386687
Edit: oh, you have seen it yet, I can see your "thanks" on that post
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
peppethustra said:
My signature talks for me
If you want to see my configuration, go here: http://forum.xda-developers.com/showthread.php?p=51386687
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will try , Is this your actually config?
KERNEL: iodak 9.95
ROM: Beanstalk 4.4.2
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=370 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-30 mV all frequencies, MPU uV=-75 mV all frequencies
GOOD: this configuration improve battery life, without decreasing overall smoothness - suggested to the users who don't mainly use the phone for hard gaming and want to find a compromise between battery durability and overall performance
BAD: some little lags, here and there, randomly happen - I suggest to apply underclock, before changing cpu freq voltage, because this configuration is good for 1300 Mhz undercloked device, but it may cause system freezes on some cpu variants, if you set cpu clock up to 1600-1700 Mhz (tested)
Regards
peppethustra said:
My signature talks for me
If you want to see my configuration, go here: http://forum.xda-developers.com/showthread.php?p=51386687
Edit: oh, you have seen it yet, I can see your "thanks" on that post
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Beanstalk is way too heavy a Rom, it's not optimised in the way it should be, battery isn't as good as it could be and it lags..
Those stats (Over5Hours On-Screen Time) Was using CarbonRom and iodak 9.95 with stock settings, 75% brightness, and WiFi on most of the day, and H+ for when WiFi was off..
but carbonRom is not on xda (Users banned) Just google it..
tiflao said:
I will try , Is this your actually config?
KERNEL: iodak 9.95
ROM: Beanstalk 4.4.2
SETTINGS: Governor=interactive, Scheduler=Sio, CPU max speed undercloked to 1300 Mhz, CPU max screen off frequency=370 Mhz, Multicore Power Saving=1 ,CPUquiet=balanced, LP Core uV=-30 mV all frequencies, MPU uV=-75 mV all frequencies
GOOD: this configuration improve battery life, without decreasing overall smoothness - suggested to the users who don't mainly use the phone for hard gaming and want to find a compromise between battery durability and overall performance
BAD: some little lags, here and there, randomly happen - I suggest to apply underclock, before changing cpu freq voltage, because this configuration is good for 1300 Mhz undercloked device, but it may cause system freezes on some cpu variants, if you set cpu clock up to 1600-1700 Mhz (tested)
Regards
Click to expand...
Click to collapse
I'm trying iodak v10beta right now, but yes, it was my last configuration on v9.95 only one week ago, and it's my own configuration yet, with a little more undervolt, considering that v10beta voltage
is a little higher than v9.95
Hid3away said:
Beanstalk is way too heavy a Rom, it's not optimised in the way it should be, battery isn't as good as it could be and it lags..
Those stats (Over5Hours On-Screen Time) Was using CarbonRom and iodak 9.95 with stock settings, 75% brightness, and WiFi on most of the day, and H+ for when WiFi was off..
but carbonRom is not on xda (Users banned) Just google it..
Click to expand...
Click to collapse
Everyone chooses his own ROM depending by his needs, and for me Beanstalk it's very good, independently by what you say My battery is not so bad as you say it should be with the "heavy" and "not optimized" Beanstalk, I think, considering both screen on time and overall phone usage time.
Sent from my LG-P880 - Beanstalk 4.4.2 - Iodak 9.95 kernel - using XDA Premium 4 mobile app
Setup:
Beanstalk 4.4.4007 , iodak v10 , CPU running at stock clock (1500Mhz)
both Wifi and Data were on for entire discharge cycle (though Wifi only actually connected for 30 minutes).
brightness mostly set to lowest level.
Result:
~2.5 hours web surfing, whatsapp, facebook, Gmail, Google+, etc., and very few calls
Total 2.5 hours on-screen time, and only 13 hours operation overall.
Phone purchased ~3 months ago. I was hoping to get at least the 4 hours web-browsing mentioned in this gsmarena article :crying:
Could having both Data and Wifi on be the explanation for the 1.5 hours less?
Edit:
Code:
[email protected]:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/tegra_cpu_variant
tegra_variant is 3, CPU is strong uhuuuu! :)
wi-fi on, only 2g, all google bull**** off
pure screen on time, on low brightness (around 30%) i get 3.30h.
daily usage wi-fi- always on, 2g, no sync etc...
screen time around 2h and 7-8h overall.
If im not carefull with this phone, it cant even last a normal workday
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.
This guide is for people who don't know much about changing kernel settings, etc. Experienced members should leave now.
All flaming will be ignored.
Please, for anyone who will complain that there's no point in disabling everything that makes your smartphone smart, please leave now.
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will. Everyone's phones are different. And how we use them is different too. This is just a thread containing guidelines to help you get the most battery.
Please note that performance may be affected.
Your ROM shouldn't matter too much. But I personally use AXI0M.
Kernel: This matters a lot. I personally use Air Kernel #10, the O2 version. This yields the best battery for me. If you use a different kernel, please don't complain that this guide doesn't have the desired results.
--------------- --------------- --------------- ---------------
All of these settings are optional but will help a lot.
Sync - off.
Screen brightness - 50% or less.
Wifi - on. 3g uses more battery.
NFC - off.
Use 2g networks only - on.
Auto rotate - off.
--------------- --------------- --------------- ---------------
--------------- --------------- --------------- ---------------
These settings, again are optional, but highly recommended. Please don't complain about this guide if you don't use these settings.
Governor: Wheatley
Minimum frequency: 286Mhz
Maximum Frequency: 1.118Ghz
GPU Maximum frequency: 400
Hotplug control/Maximum online CPUs - 2, minimum online CPUs - 1.
Undervolt: This is up to you. Find what is stable for your device. I don't undervolt at all.
All other settings should be left as default.
--------------- --------------- --------------- ---------------
That's it. Give it 2-3 charging cycles or a few days for the settings to settle. And then you should get optimum battery results with minimum effects on your performance.
Sent from my Nexus 4 using xda app-developers app
okmijnlp said:
This guide is for people who don't know much about changing kernel settings, etc. Experienced members should leave now.
All flaming will be ignored.
Please, for anyone who will complain that there's no point in disabling everything that makes your smartphone smart, please leave now.
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will. Everyone's phones are different. And how we use them is different too. This is just a thread containing guidelines to help you get the most battery.
Please note that performance may be affected.
Your ROM shouldn't matter too much. But I personally use AXI0M.
Kernel: This matters a lot. I personally use Air Kernel #10, the O2 version. This yields the best battery for me. If you use a different kernel, please don't complain that this guide doesn't have the desired results.
--------------- --------------- --------------- ---------------
All of these settings are optional but will help a lot.
Sync - off.
Screen brightness - 50% or less.
Wifi - on. 3g uses more battery.
NFC - off.
Use 2g networks only - on.
Auto rotate - off.
--------------- --------------- --------------- ---------------
--------------- --------------- --------------- ---------------
These settings, again are optional, but highly recommended. Please don't complain about this guide if you don't use these settings.
Governor: Wheatley
Minimum frequency: 286Mhz
Maximum Frequency: 1.118Ghz
GPU Maximum frequency: 400
Hotplug control/Maximum online CPUs - 2, minimum online CPUs - 1.
Undervolt: This is up to you. Find what is stable for your device. I don't undervolt at all.
All other settings should be left as default.
--------------- --------------- --------------- ---------------
That's it. Give it 2-3 charging cycles or a few days for the settings to settle. And then you should get optimum battery results with minimum effects on your performance.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What app do you use to achieve these settings?
Sent from my Nexus 4 using xda premium
adamski123 said:
What app do you use to achieve these settings?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Trickster mod, the free version .
Sent from my Nexus 4 using xda app-developers app
okmijnlp said:
Trickster mod, the free version .
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Basically you are downgrading the performance of the Phone by under-clocking the CPU.
What would be more beneficial is to find a way where we don't have to sacrifice the performance of the phone for Battery life.
Stock rom and faux stock enhanced kernel gives me the best performance and Battery life.
It also helps to hibernate the rouge apps that are constantly waking the phone during deep sleep by using Greeninfy app.
Thanks
okmijnlp said:
(GUIDE) Get 6 hours screen on time.
Click to expand...
Click to collapse
okmijnlp said:
NOTE: Just because I hit 6 hours screen time on average, doesn't guarantee you will.
Click to expand...
Click to collapse
In any case, here's some general guidelines:
- Undervolting, Underclocking, and disabling cores make the device use less power
- Lowering brightness makes the device use less power
- Turning off wireless signals makes the device use less power
- Using lesser signals (2G Cellular, 2.4GHz WiFi) makes the device use less power
- Having higher signal strength makes the device use less processing power, and thus, use less power
Most of that is just common knowledge though, maybe aside from the lesser signals thing. I don't really see anything in this guide as anything significant. It's basically saying "restrict your device's processing power for more battery", which is pretty much true for... anything.
Edit: As for the kernel, I can't think of any significant difference this would make either. Still uses the same drivers and same Linux kernel base, and most kernels have the same optimizations. Only things I can think of that would make a difference is if it came pre-UV'd or implemented a longer WiFi scan interval.
Edit: Somehow I failed to read the very first sentence (or skimmed over it completely, idk)... I should've just left
I never understood the cripple and downgrade your phone for battery thing but whatever floats your boat I guess.
Sent from my Nexus 10
**** yeah, disable two cores and get better battery life. Using airplane mode helps even more
Wow this is awesome! Will try it out
Sent from my GT-N7000 using Tapatalk 2
I can get 4.5 to 5.5 hours of screen on time (browsing, whatsapp, hangouts, some gaming) using auto-brightness, WiFi throughout, and a good signal zone without crippling the phone so such an extent. Getting 6 hours of screen on time is great....but if it isn't doing anything when you're not using it....not sure why you need a smartphone.
Actually, I found the that the phone is still pretty snappy when you turn off two of the cores...I don't think you have to lower all the way to 1.118, maybe 1.3 or 1.25 should be sufficient enough plus some undervolting. Screen brightness more than anything is the biggest factor though IMHO. Hope you guys get some good results.
Brightness alone makes up for almost everyone's battery issues.
-Sent from Marino's Nexus 7-
Honestly do not see the point in disabling everything that makes a smart phone.. well smart.. but I guess it's a good guide for people that just want their phone to last.
can anyone tell me what they are using to test out how stable the phone is when undervolting? What guide lines are there, what is a good indicator that the amount you under volt still leaves stability?
Meh, I've gotten almost 9 hours of screentime. Wifi on all day(no data), GPU: 487, matr1x kernel.
http://forum.xda-developers.com/attachment.php?attachmentid=1906921&d=1366769307
Can't seem to post the image url, so click that link for the screenshot.
Thats the wrong image... I'll post the one with 9 hours when I have time.
desertflame said:
Meh, I've gotten almost 9 hours of screentime. Wifi on all day(no data), GPU: 487, matr1x kernel.
http://forum.xda-developers.com/attachment.php?attachmentid=1906921&d=1366769307
Can't seem to post the image url, so click that link for the screenshot.
Thats the wrong image... I'll post the one with 9 hours when I have time.
Click to expand...
Click to collapse
What were you doing with the phone? Leaving it on a static screen with 10 minutes screen timeout time? Lol.
Just get the Caffeine app and leave your screen on all night while you sleep. Getting high screen on times is easy!
Sent from my Nexus 4 using Tapatalk 2
I personally leave network off, WiFi off, auto brightness
384MHz min, 1.512GHz max, intellidemand, disable mpdecision, 400MHz GPU ondemand, -100mV to all frequencies, and greenify EVERY single app so I don't get a wake lock. I can last over 2 days without charging and getting at least 4 hours of screen. But I mainly just text on my phone and listen to music. No games or much else
Sent from my Nexus 4 using xda app-developers app
Well using airkernelv8.......284mhz-1512mhz....everything one WiFi,2g,facebook,twitter,g+ etc..
Enviado desde mi Nexus 4 usando Tapatalk 2
Airplane mode+low brightness +no wifi+underclocked proc...8hrs plua sot guaranteed :thumbup:
Sent from my Nexus 4 using xda premium
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.