Related
Hello I have run both the stock cm7 and cattleprods 4.3.1 with smartass
Even going as far as to use SetCPU profiles to reduce CPU to 245 min/Max on screen lock. Im able to squeeze 11-12 hours with decent usage
from what I unslderstand reading the lord UV kernal people are lacking hsupa which is something I rather like. And while im ok with 12hours usage if something unexpected it long dinner party after work, im SOL
Any help or tips would be great
Thanks
Drew
Sent from my Desire HD using XDA App
HSUPA seems to be hit or miss on the LorDmod kernel which is strange because it's based off the CM7 kernel by Kali-. I changed my APN and my HSUPA speeds came back, at least what's normal for me in my area (3.5mbps down/2mbps up).
I was pulling a little over 48 hours out of the -25mV undervolt BFQhs version before it needed a charge or it wouldn't last the next day. I'm currently running the Pinky Ultra Undervolt version and will see what kind of battery life I can pull out of it.
Wrong forum for this. It should be in general but the lordmod kernel probably isn't the hsupa killer it was probably the radio swap I did. I fixed it but it was a PITA!
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
HSUPA seems to be hit or miss on the LorDmod kernel which is strange because it's based off the CM7 kernel by Kali-. I changed my APN and my HSUPA speeds came back, at least what's normal for me in my area (3.5mbps down/2mbps up).
I was pulling a little over 48 hours out of the -25mV undervolt BFQhs version before it needed a charge or it wouldn't last the next day. I'm currently running the Pinky Ultra Undervolt version and will see what kind of battery life I can pull out of it.
Click to expand...
Click to collapse
Can I get a little assistance? I read throughout the your thread and the one u linked. There are about 15 different kernals and UV zips
Thanks. Im really interested in trying this out
Drew
Sent from my Desire HD using XDA App
Mustang302LX said:
Wrong forum for this. It should be in general but the lordmod kernel probably isn't the hsupa killer it was probably the radio swap I did. I fixed it but it was a PITA!
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
Click to expand...
Click to collapse
Sorry I couldent figure which forum would be most appropriate
anyone can move it if they are so inclined.
Drew
Sent from my Desire HD using XDA App
helushune said:
HSUPA seems to be hit or miss on the LorDmod kernel which is strange because it's based off the CM7 kernel by Kali-. I changed my APN and my HSUPA speeds came back, at least what's normal for me in my area (3.5mbps down/2mbps up).
I was pulling a little over 48 hours out of the -25mV undervolt BFQhs version before it needed a charge or it wouldn't last the next day. I'm currently running the Pinky Ultra Undervolt version and will see what kind of battery life I can pull out of it.
Click to expand...
Click to collapse
Do you just flash the lordmodV4.4.1-BFS-BFQ.zip file in recovery?
What do you do with lowervoltages-25.zip?
Thanks for the assistance this will be my first UV type kernel
Drew
drewdatrip said:
Do you just flash the lordmodV4.4.1-BFS-BFQ.zip file in recovery?
What do you do with lowervoltages-25.zip?
Thanks for the assistance this will be my first UV type kernel
Drew
Click to expand...
Click to collapse
Wipe Cache and load the 2 .zip files just like a ROM. Hopefully you won't lose HSUPA like I did (I still think it was the radio swap but I refuse to try this again as it was a pain to fix).
Sounds good. Ill report back with my findings regarding the HSUPA and overall batt improvements.
Thanks
Drew
drewdatrip said:
Sounds good. Ill report back with my findings regarding the HSUPA and overall batt improvements.
Thanks
Drew
Click to expand...
Click to collapse
I'll tell you the -50mV kernel mod froze the phone numerous times when opening an app to where I had to pull battery. The -25mV mod didn't help at all for my battery life. My phone drained same as always which is terrible but not great either.
drewdatrip said:
Can I get a little assistance? I read throughout the your thread and the one u linked. There are about 15 different kernals and UV zips
Thanks. Im really interested in trying this out
Drew
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I'd say go with BFQhs CFS or the V(R) I/O flavor (edit: scratch that, looks like he pulled the VIO one until tomorrow), they're supposed to be faster than the others. The non-undervolted kernel might give you fine battery life so there's a possibility you won't need to undervolt at all. Also, flashing an undervolt patch is optional.
Unlike Mustang, my phone responded extremely well to the -25mV but seemed to go back to typical drain when I switched over to -50mV. And it seems like it's enjoying the Pinky ultra undervolt so far. Like LorDmod says, try them out and see what works.
Flashing the kernel's simple,
Do a backup
Reboot in to recovery
Clear /cache
Clear Dalvik cache
Install kernel zip
Install undervolt zip (optional)
Reboot and enjoy
This is just my experience - during extensive testing for my APN modification thread I ran multiple versions of lordmod and never lost HSUPA speeds from the kernel itself. Any loss of speeds were due to other issues which were identified and corrected.
henrybravo said:
This is just my experience - during extensive testing for my APN modification thread I ran multiple versions of lordmod and never lost HSUPA speeds from the kernel itself. Any loss of speeds were due to other issues which were identified and corrected.
Click to expand...
Click to collapse
Yeah like I said I'm 99.9% sure it was the change in radio that did me in but it just so happened to be just before flashing the kernel and I didn't notice till the next day I lost HSUPA. I personally will stick with stock CM7 kernel just because I messed with my own head lol.
I just flashed the kernal last night with the -25. HSUPA is still intact. Ill report back on Bat life
Drew
helushune said:
Unlike Mustang, my phone responded extremely well to the -25mV but seemed to go back to typical drain when I switched over to -50mV. And it seems like it's enjoying the Pinky ultra undervolt so far. Like LorDmod says, try them out and see what works.
Click to expand...
Click to collapse
I have only tried -50mV with the latest LordMod which after 2 days is giving about same battery life as stock CM7 (about 20-24hr with moderate use). I cannot explain how -25mV gave you better battery life. I don't understand how much the other 2 version undervolts.
As a whole now tried OC/UV on both the Captivate and the Inspire, I have not noticed a significant difference in battery life with either of these phones. Also it seems like all the ROMs give me about the same battery life, and the whole thing about re-calibrate your battery if you don't flash with a full battery hasn't held up for me either. I can flash a new rom with 30% battery or 100% my battery drain remains unchanged.
gordec said:
I have only tried -50mV with the latest LordMod which after 2 days is giving about same battery life as stock CM7 (about 20-24hr with moderate use). I cannot explain how -25mV gave you better battery life. I don't understand how much the other 2 version undervolts.
As a whole now tried OC/UV on both the Captivate and the Inspire, I have not noticed a significant difference in battery life with either of these phones. Also it seems like all the ROMs give me about the same battery life, and the whole thing about re-calibrate your battery if you don't flash with a full battery hasn't held up for me either. I can flash a new rom with 30% battery or 100% my battery drain remains unchanged.
Click to expand...
Click to collapse
My experience mirrors yours. No matter where my battery is when I flash a ROM the drain remains the same. I've also done the whole wipe of battery stats and no difference either. It lasts me long enough as I charge it overnight anyways while I sleep so oh well I'm not too worried about it anymore really.
I recently removed the battery percent from the status bar. All I ended up doing was obsessing over it and had to see where it was all the time. So now I just use the gauge and feel better about the battery lol and not even focus on battery too much unless I'm away from my charger for an extended period of time.
I use lord mod 4.4 and I have hsupa. I never lost it.
Sent from my Inspire 4G using XDA Premium App
Mustang302LX said:
I'll tell you the -50mV kernel mod froze the phone numerous times when opening an app to where I had to pull battery. The -25mV mod didn't help at all for my battery life. My phone drained same as always which is terrible but not great either.
Click to expand...
Click to collapse
That is because your device can't handle it, every device handles it differently.
As an example, my device handles UUV fine, but when attempting to use PUV it boots, but with any random reboots and application FCs.
NikolaiT said:
That is because your device can't handle it, every device handles it differently.
As an example, my device handles UUV fine, but when attempting to use PUV it boots, but with any random reboots and application FCs.
Click to expand...
Click to collapse
Right which sucks cause I wanted to try the others lol. Oh well I guess.
Sent from my HTC Inspire 4G running CyanogenMod 7 using Tapatalk.
gordec said:
I have only tried -50mV with the latest LordMod which after 2 days is giving about same battery life as stock CM7 (about 20-24hr with moderate use). I cannot explain how -25mV gave you better battery life. I don't understand how much the other 2 version undervolts.
As a whole now tried OC/UV on both the Captivate and the Inspire, I have not noticed a significant difference in battery life with either of these phones. Also it seems like all the ROMs give me about the same battery life, and the whole thing about re-calibrate your battery if you don't flash with a full battery hasn't held up for me either. I can flash a new rom with 30% battery or 100% my battery drain remains unchanged.
Click to expand...
Click to collapse
Trust me, it makes absolutely no logical sense to me either. It seems to really like the PUV version as well so I'm not complaining.
For me, there is a noticeable difference between the stock kernel and undervolting. Stock CM7, my phone drains at around 3% per hour. Undervolted, it's slightly less than 1% per hour and possibly even better with PUV.
With the CFS BFQhs and -25 UV I got another hour and change. I feel like I used it the same maybe more. Im gonna try another one of his kernel and maybe the -50 or UUV see if NY device can hang with it.
Sent from my Desire HD using XDA App
For all of you evo 4g users. I decided to create this thread to share my experiences with Kernels, so that others may learn from it. This is going to be my journal, explaining what happens when I flash certain kernels. Battery life, stability, etc etc.
I am currently using CM 7.0.3.1 with Savage Zen 2.2.1 BFS SBC and AMAN RA to flash.
I've been using Savage zen for several months, the battery life is phenomenal, and works very well with my Extended SEDIO battery. I literally have no problems with SZ kernels. Not just because of the battery life, but because of it's stability.
I have just received news that the Savage Zen team may not be making any more updated kernels...this makes me extremely sad so I've decided to try other kernels out now. I am almost depressed...but life moves on.
So here is a list of AOSP kernals that I have SO FAR tried other then SZ :
Tiamat EVO 4.0.8 SBC
The stability is great, and of course it being SBC along with my extended battery, let's just say it doesn't drain My only problem with Tiamat, is it lets me overclock it past 1190, but when I try, my phone freezes. I have a problem with this because I'm always tinkering with set cpu, and it's only going to be a giant tease to me and I'm going to crash my phone trying to experiment. I don't want the option to overclock it that far, if my evo isn't going to remain stable.
Godmode Kernel
So far so good I flashed it, and removed dalvik cache/cache/battery cache, I love it. I miss SBC though. I'll post my experiences with this kernel after I've been running it for a few days and have charged it from 10% to full over night.
its "kernel" btw
An update!
I am now running Synergy mod RLS1+ Godmode.
I never thought I would enjoy the sense UI this much, it's so far the fastest rom that I've used, although I have yet to overclock it and it's running @ 998.
Am now attempting to install Aggressive synergy Godmode!
I will tell you how it goes
I apologize for never finishing this, life got so busy that I completely spaced it and forgot all about this. Mods you can delete it if possible thanks!
I am having terrible battery life. Before upgrading to CM7 I never noticed my battery life being bad. That said I have scoured the message boards trying every solution imaginable. I typically lose about 11% of battery every 90 minutes while the phone is in standby. This bad battery life started right when I installed CM7.
What I have tried:
-Installed System Panel and I don't have any rogue apps
-Factory data wipe, cache wipe, battery stats wipe (with and without), dalvik cache wipe -> then reinstall CM7.
-Battery has been bad on Alpha 1,2,6 & 7.
-Tried both suggestions on battery life in the CM7 Bible thread under Battery Issues section
-Upgraded to FAUX kernel Joe's RCU 0.2.0
-Changed CPU to max 1026 MHz.
I have waited 1-2 days before making each change and nothing has helped or hurt the battery.
I am very happy with CM7 with everything except the terrible battery life I am experiencing.
Use standard kernel without oc. It's really really good. Record us almost six days
sent from Sensation with awesome cm7!!!!
wixi909 said:
Use standard kernel without oc. It's really really good. Record us almost six days
sent from Sensation with awesome cm7!!!!
Click to expand...
Click to collapse
I am using Faux kernel with super undervolt. Battery life is still horrible comparing to other roms. maybe I will try using the stock kernel.
jcalifornia, are you also experiencing bad battery life with stock cm7 kernel?
Have you tried a stock kernel, maybe GPU freq is running higher than stock.
c19932 said:
jcalifornia, are you also experiencing bad battery life with stock cm7 kernel?
Click to expand...
Click to collapse
Yes, the bad battery life once I started using CM7. I used it for over 1 week.
tuner562 said:
Have you tried a stock kernel, maybe GPU freq is running higher than stock.
Click to expand...
Click to collapse
Yes, I tried the stock kernel for over 1 week and was experiencing bad battery life the entire time.
What was your battery voltage right before it went dead? I have a feeling that our phones (or just these HTC batteries) are cutting out long before they are truly dead. I notice mine drops out at 3.4v. The battery itself is usually protected from UV at 2.8v. I am waiting for my chichitec to die now so I can compare cutout voltage.
For the record, I was seeing 18-20 hours with CM7 and faux's kernels. 1.56Ghz
Since you have the issue on multiple ROMs/kernels, maybe your battery is bad/defective. Maybe T-mobile can send you a replacement under warranty? I'd call/chat with them to see. Worst they can say would be "no".
One other thing, you wouldn't happen to be using the performance governor?
jayyo said:
Since you have the issue on multiple ROMs/kernels, maybe your battery is bad/defective. Maybe T-mobile can send you a replacement under warranty? I'd call/chat with them to see. Worst they can say would be "no".
One other thing, you wouldn't happen to be using the performance governor?
Click to expand...
Click to collapse
I thought the battery may be bad too, but I was getting great battery life before I went to CM7. Last night I did a "superwipe" and that seems to have fixed the problem. I am down to 71% after 9 hours when before the wipe I would be at ~25%.
I guess you had something hanging around from a previous ROM somewhere. Good luck!
try tiamat kernel + VIpermod undervolting. It helped me a lot
c19932 said:
try tiamat kernel + VIpermod undervolting. It helped me a lot
Click to expand...
Click to collapse
I have been using Tiamat kernel and still getting bad battery life. I flashed Vipermod and when I run su -> vipermod from a terminal it says vipermod: not found.
jcalifornia said:
I have been using Tiamat kernel and still getting bad battery life. I flashed Vipermod and when I run su -> vipermod from a terminal it says vipermod: not found.
Click to expand...
Click to collapse
Yea Tiamat helps a bit but the bad battery life of CM7 is still inevitable I guess.
For Vipermod: (from viperboy's faq page)
Q. I can't find vipermod in /system/bin after flashing in recovery! Where is it?
A. Well, I need to know this! Please contact me via email or post about this in the correct device thread on XDA. Due to the differences in devices and the commands they use to mount /system you may encounter an issue. Here is a workaround:
Manually place vipermod in /system/bin
Use a terminal app and type:
su
chmod 0777 /system/bin/vipermod
vipermod
The script will then run. Please see my note in the previous question to make viperMOD easier to launch.
Click to expand...
Click to collapse
or you can just use root explorer: extract the vipermod file from the zip, place it into /system/bin, change the file's permission manually, and you are good to go
I have tried every radio and my battery life is still bad. If I recall correctly I was also getting bad battery life until the late August OTA and then my battery was great. I think I am going to have to switch back to the stock ROM because the battery life I am getting with CM7 won't cut it.
Try using the app battery calibrator. Or go in your recovery menu and chose advance(I think) and chose clear battery stats. But do this when your battery is full
Sent from my HTC Sensation 4G using XDA App
http://forum.xda-developers.com/showthread.php?t=1187698
Good calibration guide, many have found that the calibration app isn't the only factor in calibrating. All it does is remove a file that Android recreates every boot.
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Which ROM are you using?
Oops. Sorry. CM 7.1.0.1.
hadoob024 said:
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Click to expand...
Click to collapse
Faux has 2 kernel versions.... one that is PRE-Overclocked and PRE-Undervolted; and the other that is starts with stock speeds and voltages.
I've NEVER been able to get the pre-OC/UV'd kernels to work on any of the several phones I have went through. I get EXACTLY what you are getting now, just a black screen and unable to boot.
Download his "SV" rom. That is his kernel that starts off with stock settings. You'll get all the features and you can OC/UV manually.
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
You'll get all the features and you can OC/UV manually
Click to expand...
Click to collapse
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
hadoob024 said:
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Sent from my Calculator with Android.
jose makalolot said:
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Click to expand...
Click to collapse
Are you talking through Settings->Manage Applications->SetCPU?
hadoob024 said:
Are you talking through Settings->Manage Applications->SetCPU?
Click to expand...
Click to collapse
Yes.
Sent from my Calculator with Android.
jose makalolot said:
Yes.
Click to expand...
Click to collapse
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
hadoob024 said:
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
Click to expand...
Click to collapse
Never mind, mods please delete.
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
jamadio said:
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
Click to expand...
Click to collapse
Hmm.. Interesting. I'll keep an eye out for it. Today's my first full day with that combination of mod and kernel. Other than the weird battery charge amount readings, it seems to be stable with a better battery life than the CM kernel. Wish I could mess with the voltages too to try and eek out even more battery life. Oh well though.
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
jamadio said:
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
Click to expand...
Click to collapse
No kidding??? Nope. Hadn't heard about that. Will give that a shot late night tonight after I fully charge it when I get home. Thanks for the tip!
Any thoughts on this issue with SetCPU and not being able to access the "voltages" tab?
I went back and read over from the beginning of this thread to refresh myself. Two reasons come to mind:
1. It could be because I don't think Faux's SV kernel is optimized/set up to have it's voltages changed. On his OP, he won't even troubleshoot problems unless they're on the SV kernel. Hence, it makes sense not to give people the freedom to OC/UV it so they can't complain about problems they made for themselves.
2.It could also be SetCPU, I know other's have gone to Pimp My CPU (You can search it on XDA) because PMCPU was built from the ground up to OC and UV, but it's features outside of that are sparse. But eventually SetCPU caught up and is the No.1 for OC/UV.
Maybe giving Pimp My CPU a try wouldn't hurt, if it doesn't work than you know that the kernel won't allow it.
Cool. I guess I'll give this current combo a try and see if I even feel the need to mess with voltages. Got pretty good batter life today so far. Going to go home, charge the phone fully, wipe the battery stats and then resume testing.
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
hadoob024 said:
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
Click to expand...
Click to collapse
No problem. Yeah, that's what makes SetCPU so legit. I don't believe Pimp My CPU has that feature. Just establishing max, min, and their voltages. Could be wrong though.
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
hadoob024 said:
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
Click to expand...
Click to collapse
Any update?
I'm going to have to try later this evening or tomorrow. I forgot but when doing app updates, CW ROM Manager got updated. Anyway, I guess this update did something because when I tried rebooting into Recovery, it never did, it just rebooted normally into CM.
I finally launched CW ROM Manager, chose to "Reboot into Recovery", it then asked for su permissions (or something) and finally worked. Anyway, I rebooted like 4 or 5 times before I realized that this was the issue preventing me from rebooting into Recovery like I normally do. That put enough of a drain on the battery where I didn't want to wipe the battery stats <sigh>
And of COURSE I didn't bring my charger
Will try again this evening and post the results.
hi
sorry for being such a nooby mcnooby-pants
but i just want to know which combination of roms and kernels will give me a great battery life and at the same time i want to be able to overclock to 1.5 GHz
i looked through the forums and i did all the basic stuff like
undervolting
setting profiles in setcpu
and removing all the bloatware from the phone
but everyone has a different combination and im really confused as to which combination to use
right now im using eaglesblood 2.3.7 with the dragon kernel and its really not working very well
so any and all help will be appreciated
thank you
Slomo5793 said:
hi
sorry for being such a nooby mcnooby-pants
but i just want to know which combination of roms and kernels will give me a great battery life and at the same time i want to be able to overclock to 1.5 GHz
i looked through the forums and i did all the basic stuff like
undervolting
setting profiles in setcpu
and removing all the bloatware from the phone
but everyone has a different combination and im really confused as to which combination to use
right now im using eaglesblood 2.3.7 with the dragon kernel and its really not working very well
so any and all help will be appreciated
thank you
Click to expand...
Click to collapse
My opinion:
1. Jump on a stock-based ROM with stock kernel and UC (underclock to 900-800 Mhz, you would be surprised you notice very little change in performance). Most stock-based ROM users report back great battery life.
2. Jump on a CM7 Nightly 199 or higher (Reports of great battery life, I can attest to this) with morfic or faux123's kernel (I prefer morfic's) which you can undervolt easily with Pimp My CPU (search XDA). I prefer it to SetCPU because the only profile I use is UC when the screen is off and with Tegra's DVFS CPU governor, it already does a good job of doing this. I also UC with this setup.
Delete Wi-Fi Calling (Kineto.apk) from your phone if you're not using it. I learned this from lotherius, it's always running in the background even when off and not in use. I was shocked to see the improvement.
I know it sounds stupid, but if you're in class or at work and don't need a barrage of updates on your phone, just turn off data. Most ROMs have a quick toggle setting to efficiently turn it on and off quickly and you'll be quite happy with how long it lasts. If you have to have data on or think it's moronic to have an Android phone that's not does not always have a data connection, battery drain is just the price that is payed.
woah.
Awesome answer
so do you think option 1 is better or 2?
does using cm decrease the battery efficiency?
if it does do you think the extra functionality in cm makes up for the batteryloss?
Thanks btw
Try miui 1.11.4 from whitehawkx with faux kernel cm-4.4
Sent from my LG-P999 using Tapatalk
Slomo5793 said:
woah.
Awesome answer
so do you think option 1 is better or 2?
does using cm decrease the battery efficiency?
if it does do you think the extra functionality in cm makes up for the batteryloss?
Thanks btw
Click to expand...
Click to collapse
Good question, and I think that is totally up to you.
For example, my father and I both own G2x's, he runs a modified stock ROM (xboarder's ROM) and I run CM7. Without a doubt he gets better battery life than me, but at the cost of not having the features I have.
That may be a rough way of putting it but yes, using CM7 with all it's awesome features come with the price of not being as battery efficient.
The real question is if being less "battery efficient" actually means it's a bad thing. In my case it doesn't matter to me at all. Using the quick panel toggles in CM7, I only turn on data when I need it and I easily pull 15+ hours a charge because of it, assuming moderate usage.
Consider lotherius's tsugi rom, currently in version beta 3. It is my daily driver, stable, faster than 2.3.3 based roms, and excellent battery life. He has included a 2G toggle app that can automatically switch to 2g radio when screen is off to save lots of juice.
Sent from my LG-P999 using xda premium