Related
This is probably a stupid question but I'll ask it anyway. I've noticed my phone draining lately (or maybe it's not, I'm not quite sure what the battery life used to be xD), and I recently overclocked my phone to 1.25 GHz (my profile on SetCPU is ondemand), does overclocking affect the battery that much?
I run Froyo (rooted with wifi fix and the 1.25 GHz kernal)
I'm using an ultra low voltage kernal at 1ghz and haven't noticed a difference, if anything it seems like it's better.
I guess it probably largely depends on what kernal.
I've been overclocked for 4+ months. The first month before I rooted, I was getting around 16-18 hours on a full charge at the stock 550 speed. After I rooted, a lot depended on the rom (lesser so) and the kernel (more so). I think the best performance I got was on ChevyNo1's SS rom (2.1) with one of his kernels ... 40+ hours overclocked conservatively at 800. My first shot some time back with CyanogenMod got me 3 hours with the early Bekit kernels but the past several versions up through 5.0.8 I was getting about 30 hours clocked at 800 with a jdlfg kernel. Now on Froyo I'm getting close to 30 hours again conservatively at 800-1000 ... which on a 2.2. rom is more like 1200+ since its faster.
So, in short, my battery life has significantly improved while running faster than stock. But no 2 Droids are identical in terms of how a rom and/or kernel perform. With 2.1 roms my Droid seems to like jdlfg's kernels, while on 2.2 the P3droid kernels do good. But that's what I found out via a lot of trial and error, not anyone's post saying "You must try ______'s kernel (or rom) as its da bomb!"
I would like to include that the post above by "cvhovey" provides some valuable information that might interest you and suggest anyone untreated in this thread to read that post.
Using an application like SetCPU you can throttle down the processor speed when the screen is off, this reducing heat and gaining better battery life. This doesn't mean you will get better battery life if you use your phone all day and never turn the screen off. But is totally worth it because u feel like I'm getting awesome battery life, plus an amazingly fast phone because SetCPU will overall me to my personal preference of 1100mhz on demand.
The answer to your actual question depends on how well you set up your phone preferences according to what benefits you the most, and what method of adjusting processor speed. I only mentioned one here, there are mire ways than just an APK.
Sent from my Droid using XDA App
PetRiLJoe said:
Using an application like SetCPU ...
Click to expand...
Click to collapse
1+ on that. But how one uses SetCPU can also make big differences, such as which governor is selected. SetCPU at 400-1250 with the Performance governor will essentially run at its highest speed all of the time (if I'm correct), whereas with the Conservative governor will ramp up from 400 to 1250 at a slower pace, or at a faster face with Ondemand.
This thread can give you some helpful tips: Battery Saving Techniques - Theories in Test
Alright, thank you for your help ^^
i used SetCPU and my phone had continuously reboots...
I just had to uninstall it..
Were you using profiles in any way? A specific ROM? I've had similar a experience with certain ROMs (specifically UltimateDroid).
Best guess is that it just didn't play nice with the modded kernel.
Sent from my Droid using XDA App
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
ZeppeMan said:
A few weeks ago when I still had my HTC Hero it was overclocked to 672Mhz (standard = 528Mhz). It gave me a little boost in performance on Froyo, also the batterylife wasn't decreased too much.
But with our N1 running on 1Ghz, will it give much difference when clocked to 1113/1152Mhz? And what about batterylife?
If SetCPU is used what are your settings then? Mine is currently running on stock speed, no SetCPU.
Click to expand...
Click to collapse
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
set to 1.13 ghz
then screen off to minimum 245mhz
josemedina1983 said:
I have my nexus one rooted and flashed to MIUI Rom and clock @ 690mhz I get way better battery power. Before I would only get 6hr to 8hr if lucky now I get from 9hr to 13hr depending how much I use it.
Click to expand...
Click to collapse
So you underclocked it, what about the speed? It's not to laggy?
Nexus one can run reasonably smooth @ 600mhz and above. It might not open applications as fast as it will be @ 1GHz though.
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
shreyas1122 said:
i think 1Ghz is enough for n1
why do u want an overclock?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I didn't said I want an overclock. It's allready very fast on 1Ghz (compared to my old Hero ), just wanted to know your thoughts about overclocking the N1.
im overclocked at 1152 mhz and profiles set for 245 max with screen off. Overclocking is nice because i like the snappiness but most people cant tell the difference between 998 mhz and 1152. its not needed to overclock but i think profiles help alot. just my two cents
Ok thx, I will try 1150Mhz and see (if it's stable and) what batterylife does. I'm also going to try underclocking.
I have my N1 only for a couple of weeks now and I must say, this phone is awesome. It's VERY fast compared to my old Hero. I remember when I was installing apps on my Hero it became very slow and couldn't do anything untill installing was finished. With the N1 you still can do things while installing apps without lag. The responsiveness and smoothness is also a lot faster. I loved my Hero Because it never let me down, ok it was all a bit slower, but it was getting there. Now with the release of Gingerbread (custom ROM) it became to slow for me and that's why I sold my Hero and bought the N1. It was very difficult to find one, because of the EOL (end of life). But eventually I found one and i'm very happy with it. The N1 is allready more 1 year old, but it still competes with the best phones out there.
I generally run overclocked at 1075MHz, which gives a good balance between battery power usage and processor power. My understanding is that a different voltage scaling method is generally used above 1075MHz, so power consumption will increase above that point.
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
ZeppeMan said:
Didn't knew the voltage would increase above 1075Mhz, will keep that in mind
Click to expand...
Click to collapse
This is, of course, dependent upon how the kernel is constructed, but this is what I have generally found to be true.
Give us some feedback
I overclocked it too 1075Mhz when screen is on (screen off 245Mhz). Will give my thoughts in a day or 2.
Just report that my battery drain is almost the same as on stock settings. I think it drains a tiny bit faster on 1075Mhz, but nothing major. On the other hand, I don't feel it's faster on 1075Mhz then on stock speed. Only benchmarks give me performance increase.
I'm now on CM6.1.1 with stock kernel (cyanogen), I tried other kernels like Wilmonks kernel,.. Although it was more responsive, battery was going down even faster. I get best battery results with stock kernel.
Hard to choose
more speed = more battery drain
less speed = longer battery
I think I stay with the last option (less speed = longer battery), because Wildmonks kernel doesn't give me enough performance increase over the stock kernel on stock speed.
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Either way, its so easy to play with the clock settings, i'd just have a play with a bunch of different settings if i were you.
liam.lah said:
I have mine at 998mhz, but overclocked 1152 while plugged into power.
Click to expand...
Click to collapse
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
ZeppeMan said:
wanted to know your thoughts about overclocking the N1.
Click to expand...
Click to collapse
well my thoughts: underclock!
so you can watch movies on it all night!
Sent from my Nexus One
shreyas1122 said:
I'd love a how-to fire that..
mind sharing the app?
Sent from my Nexus One
Click to expand...
Click to collapse
You can use SetCPU to create profiles based on different circumstances.
Me, I have mine clocked to a max of 1075 and min of 245 with the screen on, 576 max / 128 min screen off, 998/128 charging (to reduce heat - overclocking while power is applied can make it silly hot), and a failsafe to clock down to 576/128 if the temperature gets over 50*C.
Fabulous app.
Correct me if I am wrong. When you use setcpu to "ondemand", the CPU speed can ramp up to max whenever necessary, otherwise the speed will tune down to min especially in standby mode. In that way, you can enjoy the advantages of overclocking and underclocking the CPU speed i.e. increasing performance when needed and saving power when not in use, right? When I loaded Rod's MIUI and Wildmonk's kernel, I can underclock down to 128Mhz and overclock up to 1.152Ghz. At the end of the day, I still have over 60% of power left after not so heavily use (some web browsing, checking email and listen some music). Overall, setcpu is a great app for me.
Welcome to the Thrillz kernel for LG Thrill 4G (may be compatible for O3D).
Standard disclaimer: You bork, your phone. I take no liability. K?
Includes OC to 1.2 native (no modules) and 100 MHz frequency.
cifs.ko module built in.
Conservative governor enabled.
init.d support native.
More to come.
V2 update includes:
Insecure boot
persistent root shell in adb
Removed 100 MHz frequency (caused more issues than it was worth)
Trying a 200 MHz frequency.
V3 includes:
Lock 200mhz when sleep (was set at 300, swapped due to removal of 300)
---Working on other improvements, may be a week or two due to cleanup of code and removal of non-4430 chaff---
V4
Updated frequencies (300, 600, 800, 1000, 1300)
Lower cpu voltages.
#Note, seems screen is eating more battery than CPU. Will investigate.#
Plan for V5
More governors, possible UV compatible with Xan's Voltage Control app.
If you have suggestions, ideas, please give me them.
I do plan on more governors (maybe smartass, interactive, ect....) more io schedulers (bfq, ect...) and anything else that comes my way.
Special thanks to those who have gone before me and helped my learn what I have: gtg465x, LinuxBozo, and Entropy512 for everything that I've learned from them in the Infuse 4G forums, Excaliburinhand for encouraging me to start my own kernel, CallMeAria, Urabewe, tylerwagler and gtg465x again for what they've done here before me... and to you for choosing this kernel (I know... Video game cheezy, but it's true. )
Git is below, it is under the wagler kernel git as it was what I forked and am pushing to. I decided it's time to get started with this.
And please remember, thanks button is good as is fueling my insanity. If you look at my Infusion kernels, I do recognize my "Insanity Crew." (and if you want to be kept in obscurity, I respect that as well. )
Good job man, everyday this forum gets better.
...fighting ninjas at night. Talking about this and that.
Work pretty good on o3d l'll check battry life let u know later
Sent from my LG-P925 using XDA App
Thanks! Keep the comments and suggestions coming! (hoping for p920h/p925 GB leak and official GB source for p920, but I'm fully supporting this in the mean time. Forward ho!)
So far this is best kernel for my rom (v10kv4) so far I got best mobile speed 1.6up 5down i never got this speed any rom or kernal before best speed i had before 1.5. &4 from thriller
Sent from my LG-P925 using XDA App
I hate to report that my battery life did not impress me at first but after charging it seems to be doing better. But i was losing about 15% every 3 hrs in idle. No wifi data or anything.
Sent from my LG Thrill 4G...
Good to see you guys pushin' the kernel movement forward, and sharing your work.
Good deal on getting that built in overclocking going as well. I've been running the kernel for the past day. I did notice an issue, though. Maybe it's just my phone... But the 300mhz OPP, is not being utilized.
I've attached some screenshots.
I was planning to mention that, will try to fix. (100-300 bug) on battery life, what governor are you running? I've found better life on conservative or on demand.
my battery life is decent not the best try to calibrating battery will give you a decent battery life
bedwa said:
I was planning to mention that, will try to fix. (100-300 bug) on battery life, what governor are you running? I've found better life on conservative or on demand.
Click to expand...
Click to collapse
Usually I'm in hotplug or performance... My device has no service, so it doesn't see "normal use" like most. Most of the time it just sits and sleeps.
So, what I did yesterday, really because I wanted to see if you guys squashed the random reboots I've notice in my own playing with LG's kernel source... Had a fully charged phone, flashed your kernel, ran a few benchmarks, still had over 90%, and just let it sit in hotplug. got back to checking it out maybe 12 hours later, noticed the drain, checked setcpu, and that explained it for me. My phone normally would be 80% to 90% in 300mhz... But I don't think 100mhz is able to accomplish most tasks, so it's always popping out, even when it should be idle sleeping.
One thing for me is wireless tethering.. The device needs to be able to accomplish this in the background, and 300mhz even on a DroidX is able to accomplish this. 100mhz is a no go, though.
If you find it real difficult to get 300mhz functioning with 100mhz, I'd say chop the 100mhz out for now, and give us a bump, or atleast put out a 'high voltage' 1388000 mV(TI's kernel 3.0 number) top slot version of the kernel... The overclock module still works with your kernel, BTW... So, in combination with the voltage bump, those that are real speed freaks can push toward that 1300mhz mark with stability.
P.S. No random reboots, so that gets a big thumbs up!!!
I'm going to try and keep to 5 freqs, going to see if 200 works. If not 300 will be low end. Wanting to see if 1.4 or 1.5 is possible with proper voltage. (we should reach sgs II performance benches at that level. )
bedwa said:
I'm going to try and keep to 5 freqs, going to see if 200 works. If not 300 will be low end. Wanting to see if 1.4 or 1.5 is possible with proper voltage. (we should reach sgs II performance benches at that level. )
Click to expand...
Click to collapse
hehehe twould be pretty nice to rub in the face of the acclaimed best device..
Running new Kernel now, so far seems to be running smooth, max 1200, min 600 on Performance governor
Trekfan422991 said:
hehehe twould be pretty nice to rub in the face of the acclaimed best device..
Click to expand...
Click to collapse
It would be nice but I have yet to see my Thrill out perform my STOCK SGS2 yet with any kind of tweaking.
I only hope it can be done.
sent from my Stock Samsung Galaxy S II
I think I got an issue. Starts to lagg when typing/texting. Maybe its the governor I used. I tried with both concervative and ondemand. Also hotplig too. Conservative had the least amount of lag but still noticeable. The other 2 were way too laggy. Unusable.
I believe that's due to the 100 MHz freq. I rebuilt later night without it and while I am typing this there is no lag for me. Re-uploading V2.
Anyone flashed this can comment on battery life and any issues?
Haven't had it long enough for battery use, but it made slim doomed speedier.
Sent from my LG-P925 using xda premium
Flashed it. So far no lag. Battery life kinda iffy. But it's a brand new battery. I'll clear the stats and see how battery life is then.
No issues, phone feels really fast, more batt drain though. I like it.
Sent from my LG-P925 using XDA App
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.
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.