[EVO 4G General] lehalter:
I was surprised by how long the batter lasted when I switched to Ava’s ROM, but I wanted to run some tests and see how I can get the best results. If you have questions let me know, but I will continue to edit this as I go. I am running these tests for at least two days under a certain setting before I move on to the next one. On Day 8 I will/did switch back to using SetCPU to compare the weekends. Ava, you screwed my batter tests by updating from version 8 to 9, but that’s ok :). If you want me to run a specific test, let me know. I plan to do King’s 6, 10, and 11.

*I just realized today (10-20-2010) that my Facebook has been refreshing every hour automatically. Since it has been doing this every day, I am going to keep that setting throughout the rest of the tests.

SetCPU set to 245/245 Ondemand with screen off for all of these unless stated otherwise. This test was started 10-9-2010.

Day 1 - Stock kernel - Weekend day - 16.5 hours with 31% left. I didn’t use the music player at all. I did a bunch of texting , web browsing, Facebooking, and some calling.

Day 2 - Stock kernel - Weekend day - 16 hours with 30% battery left. I didn’t use the music player at all. I did a bunch of texting , web browsing, Facebooking, and some calling.

Day 3 - Stock kernel - Work day - 14 hours of usage with 8% battery left. I used the music player for at least 6 hours. I did a bunch of texting, web browsing, Facebooking and only a few calls.

Day 4 - Stock kernel - Work day - 14.5 hours of usage with 6% battery left. I used the music player for at least 6 hours. I did a bunch of texting, web browsing, Facebooking, I only had one phone call.

Day 5 - Stock kernel - Work day - No SetCPU - 15. 5 hours of usage with 9% battery left. I used the music player for at least 5 hours, felt a little less than most days. Normal amount of texting, web browsing, Facebooking, but I had a few phone calls. I was very surprised that I had better battery without using SetCPU. I am testing it again day 5. Interesting note: the battery seems to drain slower while playing music than when I am using SetCPU. I have no idea why this would be.

Day 6 - Stock kernel - Work day - No SetCPU - 15 hours of usage with 7% battery left. I used the music player for a lot more than day 5, at least an hour more. Day 5 and 6 are surprising because I was not using SetCPU.

Day 7 - King’s #10 CFS - Work day - No SetCPU - Test got cancelled. Something happened with my market and it would not let my phone sleep.

Day 8(10-16-2010) - King's #10 CFS - Weekend day - 12 hours of usage with 20% left. Normal usage without any music. The huge variance here is that I let my niece use my Swype keyboard for almost an hour just messing around with the screen on. I was actually surprised that the battery lasted that long to be honest with you.

Day 9 - King's #10 CFS - Weekend day - 13 hours and 45 minutes of usage with 38% left! I am really shocked about this because I used my phone a bunch today. On top of normal usage, my girlfriend's internet stopped working so I started my wireless tether and let her use that for 20 minutes or so. I wish I could continue this test, but the real testing will be done during my work day using my music player.

Day 10 - King's #10 CFS - Work day - 16 hours and 10 minutes with 20% left...wow. This was with pretty heavy usage in terms of music AND my market was not working at all today, it stayed on for 30 minutes before it finally failed a couple of my downloads. This gave me a pretty good indication of what I can expect. Tomorrow I am going to run it without SetCPU

Day 11(10-19-2010) - King's #10 CFS - No SetCPU - Work day - 11.5 hours with 7% left. I have no idea why the battery drained this much. I maybe used the music player an hour more than I normally do, everything else was the same. This is kind of mind boggling.

Day 12 - King's #10 CFS - No SetCPU - Work day - 15 hours and 46 minutes with 20% left. The only thing I did different today compared to yesterday was completely remove SetCPU. I had it set to not allow yesterday, but maybe it was still working? Normal usage all the way around. Great battery life today. Day 13 will be with King's #11.

Day 13 - King's #11 CFS - No SetCPU - Work day - 15 hours and 32 minutes with 21% left. Normal usage. #11 seems to make the screens transition a little bit quicker and things seem snappier. The one thing I noticed about the idle battery life for this kernel is that it barely drains. I was in a meeting for two hours today and it went from 73% as I walked in to 72% at the end. I turned the screen on a couple times to check the time. Overall, the battery life doesn't seem to different between 10 and 11. I will test these settings again tomorrow. I am looking forward to the weekend because I am going out on Bartlett lake and I want to see how it works with less reception.

Day 14 - King's #11 CFS - Work day - 13.5 hours with 5% left. I had my screen on for a solid 90 minutes straight. Other than that, usage was normal.

Day 15 - King's #11 CFS - Weekend day - 15 hours 11 minutes with 2% left. I don't know why the usage is so bad here, things were normal today.

Day 16(10-24-2010) - King's #11 CFS - No SetCPU - Weekend day - 12 hours and 17 minutes with 57% left. This is pretty awesome. I am trying these settings again tomorrow at work.

Day 17 - King's #11 CFS - No SetCPU - Week day but not at work - 13 hours and 45 minutes with 30% left. I had to take the day off. I made a bunch of phone calls, no music, but normal texting and Facebooking.

Day 18 - King's #11 CFS - No SetCPU - Work day - 16 hours and 20 minutes with 18% left. I only used my music player for 5 hours today, so it was less than most work days, but the battery life is still pretty impressive. Normal usage otherwise.

Day 19 - King's #11 CFS - No SetCPU - Work day - 14 hours with 8% left. I had very heavy usage today, web browsing, Facebook, but only 4 hours or so of music player.

Day 20 - King's #11 CFS - No SetCPU - Work day - 14 hours and 35 minutes with 12% left. Normal usage, except I did some GPS. This kernel seems to be pretty awesome, I think I am going to stop this test and only edit it when I make some other changes.