Battery testing with CM6 RC0 - Hero CDMA General

Ok guys well in case anyone hasn't heard there is an RC of cm6 for our heroes. i've been running it for a couple of days and with collin_ph's battery tweak ive seen noticeable battery improvement, but that led me to wonder.. how much could i squeeze out of a stock battery? as such i will be still using my phone as regular i have JIT and compcache enabled with surface dithering shut off. collin claims he got 65 hours i am going to try and break that by doing one simple thing
http://www.gadgetvenue.com/google-nexus-red-screen-doubles-battery-life-07053707/
already ive tested it for a while and it is a little harsher on the eyes but ill manage (for science!!) but the odd thing is is it slows down the way the phone handles (by a good bit mind you). im going to be doing this via Cyanogenmod settings and the render output. i understand that most people wont be interested in having their phones only display red but there would be no innovation if people didnt tinker
i will update this post as it goes on and when it finally dies
final level was 29 hours and 48 mins
alright guys here is another pic, minimal usage since yesterday

Nvm...
10characteristiccharacters

I was under the impression that this would only extend battery life if our screens were of a different sort.

Until now, never have I felt physically ill from a screenshot.

yes oled screens would benifit the most from this but i wanted to see what effect it would have for our phones.. currently at over 17 hours and 47 battery life

Alrite well let's hope for the best and keep us updated

updated the main post, over 24 hours now

Related

Lower Batter Life due Increased Google Latitude Update Frequency

Since a few test revisions ago I've been checking logcat to see what's going on in the background and to try and optimize battery life by checking out what's turning on/off while on standby.
Earlier in the testing phase (t2?), I noticed that Latitude would update very slowly if ever, and I was hoping it'd be fixed at some point. As I flashed each newer test revision i'd run logcat and see what's going on, and at some point everything was working well. The NetworkLocationProvider service would come on sparingly, but enough that it would make Latitude useful. Now that i've flashed to the stable rev, I ran logcat again to try and figure out why my battery life had seemingly gotten worse only to see the NetworkLocationProvider server running with a much higher frequency then before, running once every 5 minutes or so.
By disabling Latitude, this stops happening so i'm relatively sure it's not any other application I have installed. I tried entirely removing maps and reinstalling it, i've tried running fix_permissions, i'm just confused as to why the update frequency is so erratic between image revisions and if there was anyway to adjust it.
please post this into cyanogen issue tracker
yeh i dont like having alot of stuff on my phone even though they have introduced apps2sd.... i mean ive only got like 5 3rd party apps and system apps. i usually can squeeze somewhere around 12hrs on a full charge from it dying to 0% if anyone has a better battery life on a overclocked rom higher then 570mhz, let me know
bosna110 said:
yeh i dont like having alot of stuff on my phone even though they have introduced apps2sd.... i mean ive only got like 5 3rd party apps and system apps. i usually can squeeze somewhere around 12hrs on a full charge from it dying to 0% if anyone has a better battery life on a overclocked rom higher then 570mhz, let me know
Click to expand...
Click to collapse
who likes to squeeze battery life out of their phone?
htcclay's superfast 1.3.3 is teh best for battery life, hands down. (speed too :0)
Reading this thread on my G1 resulted in lower battery life
-------------------------------------
Sent via the XDA Tapatalk App
I've noticed that with JIT enabled, I have 10x a better battery life than without JIT.
Life without JIT: 7 hours
Life with JIT: 12 hours
smackdown85146 said:
I've noticed that with JIT enabled, I have 10x a better battery life than without JIT.
Life without JIT: 7 hours
Life with JIT: 12 hours
Click to expand...
Click to collapse
This must be that "New Math" I hear everyone talking about...
7x10 =12?
nice math dude.....
Mod edit.: not dev related, moved to general

[Discussion] Ava V10 battery life - Phone Specs

First off, this might be a topic for the general forum, but since is pertains directly to development, i thought i would put it here... Mods.. please move if you feel this is inappropriate.
There seems to be some HUGE differences with Ava v10 and battery life and i wanted to try and narrow down what the differences are to see what is up!
What i am curious about and would like you to post is the following:
Hardware Version
Screen
Kernel you are using
battery life / Usage
If we are seeing a pattern here then we should be able to determine the problem and hopefully yield some good data for devs to use. If it is still very random.. then its got to be an app that is causing the issues.
I will start
Hardware 003
Epson
Stock Kernel
8 - 9 hours MAX on moderate - use (lots of texting, some calls, and a little web browsing) Was getting WAY better on v9 before 3.30 update (v9a)
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
It seems only hardware version 0004 is mostly unaffected by the new frame software and I know the only difference is camera hardware but that may be it
Sent from my EVO at the edge of hell
Hardware: 003
Screen: not sure how to tell I am a newbie
stock kernel that comes with AVA V10
Right now I am home and not on the road working so my useage is lighter but I did go to bed last night with >50% life remaining and the phone had been off charger >15 hours
4-5 calls none were more than 5 min long
a little texting, couple emails (with polling every 30 min from 8-8), FB and Twitter updating at a regular interval (about every 30 min)
Bluetooth on for around 2 hrs, wifi on most of the day as I was at home using my home network so it was connected and not scanning.
Went to mall for about an hour and that has notoriously bad Sprint signal inside most places.
I ran the following:
hardware 002
Novatek screen
kernel: HTC 10, HTC 11, HTC 17, Kings #10 & #11 (both variants), Netarchy 4.1.9.1 & 4.2.1 beta (havs, no havs, bfs, cfs, smartass)
Some web browsing, facebook, texts, maybe 10-20 min of calls per day if that.
I'd get MAX 6-8 hours from fully charged to completely dead.
Went back to MIUI 11.19 and am consistently getting 15+ hours with moderate to heavy use.
If I try and run any ROM with the 3.30 file system, my battery totally sucks no matter which kernel I use.
Evo hardware version: 003
Screen Type: unknown (don't know how to tell)
3.30-ROMs tested: Ava V10, EViO 2
Kernels: various, in text
When I first switched to the first 3.30-based ROM, I noticed a big reduction in battery life. I tried another and ran into the same thing.
After one day on Ava V10, on a recommendation I tried the EViO 2 v1.6, along with the "netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS)" kernel, and with extremely light usage (1 short call, and few texts) after 19-hours I was showing an 89% charge. With this kernel the phone slept very well. The problem was that with that same kernel, even moderate usage sucked the battery very quickly.
So, based on things that I read I switched to the "netarchy-toastmod-4.2.1-bfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting)". Using this combo, sitting on my desk with zero usage for 11-hours it was displaying 89% charge, so sleeping did not appear to be as efficient. However through the day, normal usage (moderate) seemed to provide a bit more time per charge. It did not appear to be a drastic difference.
On another recommendation, I then tried the netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal kernel. Overnight, no usage, after 9-hours I was again at 89% charge. Normal usage netted slightly worse time than the netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS) kernel provided.
Behavioral observation: The 4.2.1 No HAVS kernel produced slightly higher Quadrant scores than the 4.1.9.1 kernel did, but overall in normal operation, the phone was more sluggish and draggy on the 4.2.1 kernel, while being snappier and feeling faster overall using the 4.1.9.1 kernel.
Also, please note that the best battery time I ever got on any 3.30-based ROM pales in comparison to my experience earlier in the year with DC3.5 and an older Toastmod DC-compatible kernel. Once, after almost 21-hours off the charger, light usage throughout the night and at the very end of a 3+ hour phone call, I got the charge warning that I was at 15%. I don't know why I changed.
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
bender1077 said:
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
Click to expand...
Click to collapse
what was your "awake" time with this? This will be the tell.
When i ran ava 10 i got like 10 hours max. Alot of the 3.30 roms sucked my battery life. Fresh 3.3 rom gave me best battery life and i upgraded to his 3.4 and my bat sucked. Now im running airbourne rc4 and i think im getting the best battery I've ever had and its 3.30 based. It does have the sense launcher removed but all other sense is still there that could be the problem.
Novatek and 003
I decided to reload v10 and only restore a few essential apps and see where i was at. i did this, and had a full charge late last night.
This was with ALL settings defaulted to what is in v10 and no setcpu. The ONLY thing that i changed was the autokiller settings to "optimum"
It has now been 14.5 hours since i unplugged it (7 was me sleeping)
and "awake time" has only been 2.5 hours
It has been a pretty light day for usage - couple phone calls, mostly texts and emails and i am at 50%
This is MUCH better, but i really have not used my phone like i normally do. And this is with only a few apps installed.
frettfreak said:
what was your "awake" time with this? This will be the tell.
Click to expand...
Click to collapse
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
bender1077 said:
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
Click to expand...
Click to collapse
huh.. thats pretty good! lol... hmm..
a little off topic......how do you tell who made the screen on your EVO?
skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
nYdGeo said:
...
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Click to expand...
Click to collapse
So dont remember where I got this from (someone in another topic), but it completely confirms everything that we have been talking about...
NO 3.30 rom is made for hardware 001-003 period.. directly from sprint.
http://community.sprint.com/baw/com.../blog/2010/11/05/htc-evo-maintenance-releases
so the problem now is devs are either going to have to split their roms in to 2 branches (one for pre-004 hardware and one for 004 hardware) OR... sprint need to come out with a unified release. SO... hopefully devs will read this and make changes accordingly

Battery Life Testing - Kernel + Rom Combo's

Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
SCREENSHOT 2: This is CM7 Nightly build 27# with Netarchy's latest 1.2.1 kernel and although i didnt use the screen once of charge for a few minutes as you can see once the screen was off battery life barely decreased and was over a long period of time.
If anyone wants me to test specific combos please let me know.
I'm actually looking forward to reading your results.
Sent from my Nexus S using XDA App
Yep, this would actually be pretty useful. Good luck and good work!
i'm a sucker for these types of tests, always love doing them and seeing the results. post soon!
I like others will be keeping an interested eye on your findings.
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
I'm interested too.
Can u try modaco r10 with Netarchy 1.2.1 kernel.
bratfink said:
Iv always considered battery life a very important factor in my purchasing of a phone and was one of the big reasons i moved from my Desire HD to the Nexus S (amongst many others). However having been on the android scene for a while im used to tinkering with kernels and roms etc and due to the new battery graph in gingerbread im now able to make direct comparisons rom by rom and kernel by kernel to see how they all differ. This is all shown + explained below.
First id like to explain my method;
I install the rom and kernel with the same apps I always use and charge the phone fully until i am about to go to sleep. I then unplug the phone and leave it in the exactly the same place on my desk with exactly the same settings (sync intervals etc) and i kill all apps before i leave it just to make sure the test is fair.
In the morning i then take a screen shot of the battery life over the period of usually 8 hours and will upload this for you to see. I then look at the over-night battery drain as a comparison on how good battery life is on specific roms and kernels.
Justification - Many of you may be thinking who cares about standby battery life? I care about the battery when im using it!?
Well although that's valid there are many reasons i have taken this approach;
1. It is completely fair i.e. no individual differences such as 'im a heavy user' but we all have different definitions of a 'heavy user'. This is eliminated by the fact the phone is not used and thus the same every time (no individual differences)
2. If a phone has severe battery drain during sleep general knowledge should dictate that battery drain should increase when the screen is on, cpu is working and your syncing your facebook wall, thus a direct correlation with sleep battery drain and usage drain should be apparent.
Therefore i have decided over the next few days/weeks etc i will upload on a regular basis a screenshot of the battery drain over night, along with the battery use details and screen on time etc etc. In addition to the rom and kernel info and i hope that over time this proves to be a very useful thread.
I have been doing this over the last few days on a less strict system and there have been some VERY interesting results which i will upload over the next few days.
(Just a final note iv never really done anything like this on xda before so if its a stupid idea then please tell me now so i dont waste my time doing it, however if people are really interested please let me know and il make sure i do my best!!)
Thanks for reading my extremely long post!
Bratfink
SCREENSHOT 1: This was using modacos custom rom r10 and the kernel that comes with it, i had quite a short sleep (about 6 hours) but the curve pretty much shows what the point im trying to make is. The battery life is great!!
If anyone wants me to test specific combos please let me know.
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App
I'd be interested in seeing CM7, just whatever nightly build you manage to catch.
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
gogol said:
I don't think that result will give you precise result.
I found that statistic is wrong sometimes.
It is better to measure using "play video loop".
So, find a movie, set to the same brightness and play in loop?
Click to expand...
Click to collapse
Unfortunately that will not give you how well the rom does while it is idle.
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Fuse8499 said:
I'm really looking forward to your results. My only issue with this phone is the battery life is terrible. I ordered an extended battery off Ebay 3 weeks ago and have yet to receive it. Never ordering anything from Hong Kong again!
Click to expand...
Click to collapse
What were you using before that you consider this phone to have bad battery life? By far this phone has the best battery life of any Android device I've owned. If you want bad battery life, get an Evo. That is horrific battery life.
bratfink said:
Uploading pictures of modaco r10 with it's own original kernel today. Its an interesting result!
Sent from my Nexus S using XDA App
Uploaded to OP
Click to expand...
Click to collapse
I am looking forward to the rest of these, however just a quick question. What was your battery use like in that situation with the stock ROM? Just for reference, because I'm thinking I might switch to modaco soon. Thanks!
More soon
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Interesting find
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
bratfink said:
I found out something today that may interest may of you. I was messing around with the sleep profiles on SetCpu with netarchys kernel and i found that its better to leave the range from 100-800 than 100-400 or less. This i believe is because when the phone is asleep and carries out a process it will be forced to clock to the maximum of 400mhz and then stay at that speed for 10 seconds, instead of say going up to 800mhz for 1-2 seconds to complete the same process. So a tip to you would be set your profile to 100-800mhz conservative and see what you get!
Click to expand...
Click to collapse
This kinda enforces the point that SetCPU is useless for the NS unless you really want to overclock...
Any battery saving tactics used buy lowering screen off profiles are counteracted by the system process;( So i think in the context of battery life you are probably better to not use SetCPU
JD
bratfink said:
Iv got a few more screenies but it seems i may have to end this thread prematurely. Its the SNS or 2.3 but idle battery usage for me is pretty much identical no matter what the kernel or rom (il upload a CM7 + Netarchy 1.2.1 shot top op). This was unexpected on my behalf because with my DHD kernels and roms had a big impact on idle battery consumption. I have noticed however that without a full wipe when changing some kernels such as with M r10 idle battery life can increase drastically. I will continue for the next few days and if i dont see any big changes i may move method to a video loop or something of the sort.
Click to expand...
Click to collapse
I would definitely move to a video loop or some other 'heavy use' task because when you think about it, not too much can really be changed when almost no power is being used in the first place.
You could also just mention your general feeling for the battery life of each rom, because quite often that is what I go by as my usage varies depending on a range of things (school day or weekend etc) .
Sent from my Nexus S using XDA App
Could you please test modaco r10 with Netarchy's latest 1.2.1 kernel ?
I would love to see the difference between modaco's default kernel vs netarchy's kernel.
On CM nightly 13, I just went 11 hours and I'm at 90%. That's 1/2% an hour. Not bad. That is with stock kernel.
Sent from my Nexus S using Tapatalk

Appropriate steps to a better battery life?

Hi everyone! Long time XDA reader and I've had my Evo rooted for months. Now I have been dealing with its "poor" battery life for a long time and not really thinking much of it till I finally decided that rooting has to have some advantage for this. I average about 6-7 hours then my phone dies...
After doing a little research I read some people getting 15-20+ hours out of their phone with heavy use...I was amazed...I decided to try to get better battery life on my phone and this is what I am trying right now. I just want to make sure I am on the right path with it and that I am not doing anything seriously wrong.
-I am trying Cynogens ROMs - CM7 I tried for a day and that gave me about 7 hours of battery life...still no real improvments. I am trying Cynogens 7 Nightly 12 now to see if that works.
-I am trying different Kernels. Been getting them on the HTC EVO kernels page. Right now I am using stock HTC one.
-Should I try different radios too? Where can I go to find different radios if so.
-What order should I be installing radios/kernels/roms?
-I have donated and am using Set CPU now also and have the screen off cpu power really low.
-Am I on the right path trying out different ROMS/ Kernels/ Radios to optimize my battery life? Is there anything else I can be trying?
turn off gps when not need
data when not needed
Check out my sig for my full walk-through on battery life (I don't want to repost it here lol).
But you seem to be doing everything okay. My only hesitation would be to say make sure you're giving Kernels adequate time to settle into your phone. Unless something is HORRIBLY wrong with them, you shouldn't switch/judge them until at least two days in
Radios should not make a difference in your battery life.
Also, be aware that CM is NOT optimized for battery life. There are a couple of ROMs that will give you unheard of battery life if you would like though (Myn's comes to mind). It's a trade off though. CM is hands down the fastest ROM you'll run...but in my experiences is in the lower tier of battery.
Hope that helps
also when the newest version of ultimate Juice is released that will help you i have the closed beta and im glad to have it back and running
@Cheesy: I turn off all those things If I turn off "data" that turns off Exchange push right? I really need that on all the time >_<
@Green: Really? Myns is good on battery life? I tried that before and was dieing with battery. (Was getting my average 6-7 hours) I had that one for about 2 weeks. Do you think it was my Kernels that were bad then? Isn't Myns warm 2 pt sense based? The one I used was...I had thought sense UI drained battery more than CM for example that is just plain stock android gingerbread?
@Cheesy again: Ultimate Juice? Is that an app on the mkt place? How much did it help you? I'm willing to donate and pay for apps to support the devs if they really make a noticeable difference.
Another thing..when you install a ROM does it automatically install a Kernel too? Or are those 2 separate?
syypher said:
@Cheesy: I turn off all those things If I turn off "data" that turns off Exchange push right? I really need that on all the time >_<
@Green: Really? Myns is good on battery life? I tried that before and was dieing with battery. (Was getting my average 6-7 hours) I had that one for about 2 weeks. Do you think it was my Kernels that were bad then? Isn't Myns warm 2 pt sense based? The one I used was...I had thought sense UI drained battery more than CM for example that is just plain stock android gingerbread?
@Cheesy again: Ultimate Juice? Is that an app on the mkt place? How much did it help you? I'm willing to donate and pay for apps to support the devs if they really make a noticeable difference.
Click to expand...
Click to collapse
with UJ i get 18-19 or more on a full charge with phone being used 80% of the day .
with out i was changing out batteries after 9 hours or so ( i normally work 12 - 13 hours a day )
yes its in the market but gingerbread support is not public yet ( closed beta )
also check in spareparts for any wakelocks you might be having
for a sense rom myns are great so are Ava's,caulkins and Miks
Hmm Thanks Cheesy. I'll take a look at that.
So if I flash a ROM that is not Gingerbread...I can use that app. But Gingerbread is anything 2.0+ right?
I'll try out those ROMs too and different kernels...test them for 2-3 days.
Whats wake lock? I'll download that spare parts thing and see if I can figure it out.
I just recently started seeing great battery life with my rooted Evo. I flashed MikFroYo 4.5 with a stock htc kernal.
I use juice defender and that's it. I've been getting just over a day per charge for the past two weeks.
I wouldn't say that's with heavy use as a good 6-7 hours of that time are accounted for when I'm asleep. I do about 30-50 texts a day. About 10 minutes of calls and I check facebook and twitter all the time. My data use varies depending on the day but I do use youtube and pandora pretty regularly as well.
just make sure background data is disabled. accounts and sync>background data. I have no issues with battery life on stock sprint evo.
of course it is a 3500mah battery
My wife and I just bought two EVOs a week and a half ago, and I quickly became interested in improving the battery life on the phone. My first attempts were rooting my phone and installing OverClock Widget, and using minimal settings when the screen was off. With that change alone, and comparing to my wife's phone from a full overnight charge, my phone was able to make it 14-16 hours with moderate use. My wife's phone would die after 8-9 hours of moderate use. Granted, there's obviously going to be a difference between my moderate use and hers, but even testing with screens off and letting them idle for an hour, there was a definitive difference in battery consumption between our phones.
I went one step further and installed CM7 Nightly 12 just yesterday... already I'm noticing even further improvement in battery life, but the majority of those savings are when my phone is idle. Overnight, my battery only drained 7%, whereas my wife's drained much more than that. My battery has been at 39% for the past 3 hours at idle, so I imagine that with my version of "standard usage", I would be able to possibly get higher than 16 hours of usage per charge (can't wait until I do the full calculation testing tomorrow!).
Here are some observations I've had in all of this:
1) Check out Greenfieldan's list of battery tips and tricks. Some of these are very simple and actually had a significant impact on both my phone and my wife's phone (especially shutting off data and disabling auto-synch). I'm new to the forums, but this is one of the first things I checked out. This is a great place to start.
2) Battery consumption is obviously affected by how frequently you use your phone, and what you are doing with it. I say this because it's easy to read threads about what techniques work and see mixed results, but I don't see alot of people really admitting how much or how little they use their phones. I'd say I'm a more conservative user of my phone, but I still have my texting, browsing, and even occasional streaming, GPS using and general fiddling. So in other words, your mileage may vary with any given technique.
3) This is my personal opinion, but think about when you ideally want to be charging your phone, and try and anticipate usage around it. It sounds strange, but I've come to my own conclusion that an optimal charge for me (not necessarily possible, but optimal) will give either 12 or 36 hours of usage time. This is because I like to charge my phone overnight, so if I get 18 hours of battery life, I'm unfortunately wasting 4-6 of them. If I get 24 hours of usage, then that means that by the next morning, I need to charge again. So I plan ahead and charge at night, and use through the day. This was particularly useful when I first started with the phone and was getting a max of 8-9 hours. I'd know when to unplug, and how well it would get me through the day.
Anyway, at this point I'm rambling, but since it is still very fresh in my mind I wanted to share my thoughts. Hopefully this helps.
(Btw, apologies for the huge post!!)
syypher said:
So if I flash a ROM that is not Gingerbread...I can use that app. But Gingerbread is anything 2.0+ right?
Click to expand...
Click to collapse
Gingerbread is Android v2.3. Froyo is v2.2.
syypher said:
@Cheesy: I turn off all those things If I turn off "data" that turns off Exchange push right? I really need that on all the time >_<
@Green: Really? Myns is good on battery life? I tried that before and was dieing with battery. (Was getting my average 6-7 hours) I had that one for about 2 weeks. Do you think it was my Kernels that were bad then? Isn't Myns warm 2 pt sense based? The one I used was...I had thought sense UI drained battery more than CM for example that is just plain stock android gingerbread?
@Cheesy again: Ultimate Juice? Is that an app on the mkt place? How much did it help you? I'm willing to donate and pay for apps to support the devs if they really make a noticeable difference.
Another thing..when you install a ROM does it automatically install a Kernel too? Or are those 2 separate?
Click to expand...
Click to collapse
Sorry it took me so long to reply.
Anyhow, from my testing on mine and three other phones Myn's Warm TwoPointTwo has the best battery life (although some of them were right on par with it). Specifically his RLS 3 and RLS 4. Did you try Warm Z? Because the battery life on that ROM is no where NEAR his 2.2 ROM.
Also, Sense CAN be a major drain on battery. If you make it so it's not syncing all the time/doing the random shenanigans it defaults to I'd argue it's better than AOSP (based on my experience with both).
Yes, your Kernel might have been an issue. Do you know which one you were using? HAVS? CFS? BFS? Etc.
Just for my phone comparison, CM7 (which I am running now) requires me to charge my phone at least once a day. Myn's Warm TwoPointTwo was every other day/every day and a half.
syypher said:
@Cheesy: I turn off all those things If I turn off "data" that turns off Exchange push right? I really need that on all the time.
Click to expand...
Click to collapse
You can set juice defender to turn on data to sync at set intervals; anywhere from 15min to every couple of hours. If you can stand to wait 15 minutes for that email then I would recommend it. I personally like not being interrupted every time I get an email.
Also, make sure your kernel and setCPU aren't trying to both control the same thing. I really like using a kernel with HAVS so I avoid apps that also try to modulate my CPU.
I've tried warm 2.2 and really like it. Although I think I'm getting slightly better battery with Azrael X 4.0 with netarchy 4.3.1-cfs-havs-nosbc and ultimate juice controlling only my data and WiFi connections.
Also,the 3500mah battery is worth every penny if you don't mind the extra thickness.
i owe setcpu and screen off seting for my battery life
I read Greenfieldan's step on the forum here about a week ago, and jsut the HTC Method of battery calibration alone changed my battery life completely.
I also dumped Advanced Task Killer.
In another thread, I rad that CM is the worst drain on a battery and I personally think the guy that wrote that is sadly mistaken. Even with all the steps taken in Greenfieldan's guide, Sense based ROMs are battery killers. They are the worst, by far, and I average battery drain at about 15-20% pr hour, even with screen off.
The #2 killer, is having your screen on. Waiting for that next text to come in with the screen on is not worth it, so turn it off when you're not using it.
With the setup in my sig, and moderate to heavy use, in 12 hours, I only drop about 25% with a Sedio 3500maH battery.
With Sense, like I said, quick battery death.
I'm using CM7 - Nightly 12 right now + Stock Kernel...I also have set cpu to change cpu usage when screen is off.
This combo was my first combo I started trying (2 days ago when I posted this) to test for increased battery life. I followed what some of you guys suggested and let it "work into my phone." Instead of giving up after 1 day of test.
Results! Just yesterday I had my phone on for 14 hours and it was at 18%! That is a HUGE improvement. Right now it is at 65% and I've had it on for about 5 hours. That's really long compared to what it was before! Before I tried changing the ROM, kernel and using Set CPU I would be at the red right now or around 15%.
Thanks you guys for all the suggestions! Any further advice would be greatly appreciated! (Only sad thing is that my GPS doesn't work with CM7 - Nightly 12 >_<...) Other than that I love it!

[Q] kernel for GB retail?

hi guys im a newbie about android. yesterday i have updated my phone with motorola update gingebread for ms2 retail (italian).
I wish to know if is there a kernel for improve battery duration, i`ve searched around and on this forum but have found nothing.
thx!
edit: around i`ve read that i can improve my battery life installing setcpu or milestone overclock and setting up some profiles with cpu and monitor differents frequences.
anyone tried it? is this helping battery life and are these app compatible with new stock gingerbread 2.3.4 for ms2 retail?
any advice guys? im still searching around, can someone address me to on the right way(aany guide or thread talking about this).
I have never had any battery issues and still don't. Still rockin' at about 23 hours non stop with WiFi and 3G on and brightness set to automatic.
I actually realized I didn't even undervolt yet, so I guess battery performance might be improved.
hi dude, thx for ur reply.
do u use a custom rom? or different battery?
as i told i use a ms2 unbranded with stock rom, now updated battery seems going better now than when i was on froyo but still low hard arriving in the night if i use wifi
The only kernels we can get on ms2 are the stock ones thanks to the locked boot loader. If you downlooad milestone2toolbox from one of the threads in the android development forum (pretty sure miui has it on first page), it has a pretty nice over/underclock feature. And custom roms will help you battery life somewhat, however if you are like me and can't put your phone down, and are on it all the time, you'll still only get like 4 - 6 hours battery life .
Once and once only, I squeezed out 24 hours, I was very proud. Granted that I was bored out of my brain, but still managed about 15 minutes of gaming, a couple calls and about a dozen sms, 1/2 hour browsing xda, another half on android market.
And I don't know about other people's experience with it, but Juice defender seemed to have actually DECREASED my battery life - quite significantly I might add. A friend at work tried it too and unistalled that same day from the amount of drain he got :/. I suspect perhaps its more useful on eclair, but with gingerbread (and maybe froyo) it is redundant.
Moral of the story - underclocking is your friend for battery life. I'm underclocked to 800 mhz and barely notice any performance loss - even when playing NOVA hd
Sent from my A953 using xda premium
hey dude thx for ur reply!
ok ill try tool box. yeah i think same on juice defender.
well i`ve not calibrated my battery and dont know if it helps, but my battery life especially when use wifi is very low!btw ive noticed that the over 60% of consume of the battery juice is about screen. I was thinking of underclock gpu too when i dont use games etc... is that possible on milestone 2? i`ve found nothing around about that
I didn't know phones could have gpu clocked? Unless you were just speculating
Yeah the screen is a bit of a power hog, but just remember that it has back lights lighting it the whole time your using it, so that's the reason it drains so much. So either setting screen brightness to low or automatic is a plus. Obviously low is best but its pretty hard to see . Autosync/gps will push apps like facebook into the lead too.
I'd recomend one of those recharable portable batteries that has a usb out port, they are so handy in a pinch it's a bit of a decent investment too since you can just plug whatever usb cable you have to charge any device really
Oh and using your phone's internet is a crazy, crazy drain to the battery!
Sent from my A953 using xda premium

Categories

Resources