Database Info

[Battery Showdown] Top captivate roms battle it out! Updated 3/31 w Phoenix results

Test # 1 Video Streaming Over WiFi
ROMS Tested So Far:
Continuum
Serendipity
Precision
Firefly
Cognition
Phoenix
Paragon
Twingerbread
Supernova
Darky's
di11igaf
Dragon
Andromeda
**DISCLAIMER**
Keep in mind that results will vary for each phone and just because I get a certain battery life using the rom's and kernel's listed below does not necessarily mean that you will.
Tired of constantly flashing to find great battery life only to realize the rom didn't meet your expectations; then this thread is for you. Over the next few weeks I will test every rom imaginable and post real world results that will include battery stats, linpack and quadrant results.
**This is not meant to put down any particular ROM. Without our great dev community my captivate would have been returned and thank you all for your hard work.**
[Goal]
To provide the captivate community with real world results from top roms in everyday usage where battery life is the key focal point, but performance is not affected. Hopefully this will help save you time from having to flash multiple ROMS.
[Roms]
*This list will continue to grow*
Stock 2.2 kept fcing so will test it on test 2 this evening 3/28
[Usage]
Each night I will run the exact same VERY LONG documentary using VLC stream and convert and current widget.
[Specs]
*Every rom will run "out of the box" meaning Kernel, Modem, Settings all default to how it was cooked*
° Default clockspeed 1000mhz (as suggested by a smart person listed below)
° 40% Brightness/Screen Timeout Turned Off
° 100% Charge each run (0mV to make ryude get a chubby)
° Auto Sync off
° GPS off
° Zeam launcher
° VLC Steam & Convert used w/ same long documentary used each time
° Phone is placed in exact same spot every test and is unplugged as soon as I hit play
Results So Far
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Test # 2 Web Browsing
Test # 2 Web Browsing on 3g
Roms Tested So Far:
Continuum
Serendipity
Precision
Stock 2.2
Firefly
Phoenix
Paragon
Currently Running:
Twingerbread
Upcoming:
Supernova
Darky's
di11igaf
Dragon
Andromeda
Juiced
Cognition
Goal:
In previous tests I tested on wifi using a vlc stream & convert. With this way of testing I'm hoping to get more realistic real-world results that you can use as a guideline to a roms overall battery performance . Keep in mind your results may vary.
Testing:
Every night I will set tab reload to 15 seconds and it will continuously reload XDA website until the phone dies. It will be placed in the same spot in my house every night and will be ran on phone data, thank god for the unlimited plan.
Applications I will be using:
- Dolphin Browser HD
- Reload tab plug-in
- Current widget
- My Settings
[Specs]
*Every rom will run "out of the box" meaning Kernel, Modem, Settings all default to how it was cooked*
° Default clockspeed 1000mhz
° 40% Brightness/Screen Timeout Turned Off
° 100% Charge each run
° Auto Sync and GPS On (To help give near real world results)
° 3g
° Zeam launcher
° Phone is placed in exact same spot every test and is unplugged as soon as I start Reload Tab Plug-in.
**Will be running all tests on 3g as some ROMs do not have HSPDA**
Results

Reserved for future use

Cool. Any chance you can add stock Froyo to the list as a reference point? It would be interesting to see how much custom rom's are improving over stock...

TheSopranos16 said:
Cool. Any chance you can add stock Froyo to the list as a reference point? It would be interesting to see how much custom rom's are improving over stock...
Click to expand...
Click to collapse
Great suggestion only thing is I won't be able to undervolt so numbers will not be accurate to this testing, but I might run the best two roms after I'm done testing at there defaults against stock froyo.

Since many users are set at the standard 1000, would you consider the testing at standard 1000 speed for a more accurate battery life any user can expect. Just a suggestion

Sounds like Precision should be included, with the black theme it easily gets great battery life.

diablo009 said:
Is this under-clocked? I am on the same ROM with speed at 1000 with no under-volting.
I get 1600+ scores on quadrant, and 14+ scores on linpack (tested out even now).
Click to expand...
Click to collapse
Yes I listed in the specs what they will all be running at. All are uc/uv to 600mhz.

I have been waiting for something like this but I assume that the devs would all be up in arms if someone rated their ROMs higher/lower.
If this thread will be allowed to continue, totally looking forward to the results.
And you should totally throw Precision into the mix as it seems like the de facto battery saving ROM as it skimps on a few services.

Enhanced said:
I have been waiting for something like this but I assume that the devs would all be up in arms if someone rated their ROMs higher/lower.
If this thread will be allowed to continue, totally looking forward to the results.
And you should totally throw Precision into the mix as it seems like the de facto battery saving ROM as it skimps on a few services.
Click to expand...
Click to collapse
Personally, if I was a dev and saw that my rom wasn't too good, I would try to make something better. So who knows how it turns out. A little competition wont hurt anyone, and hopefully have better roms! Btw, good idea with this
Sent from my SGH-I897 using XDA App

Just finished di11i on to paragon. The theme on di11i is very nice too almost a carbon fiber look.

add Torch 1.5
Also try Torch 1.5. So far been outstanding in battery department.

I know this doesn't help as far as battery life, but just for a reference as far as stock 2.2:
1. Linpack - around the 14 mflops (sometime in the 13 range, sometimes in the 14)
2. Quadrant - 1050 or so
3. Nenamark1 - 51 fps (not sure if anyone uses that one much, but thought I would throw it in as I had it available lol)
I would estimate the battery life if I didn't use the phone at all (just left it sitting in standby) would be at 60hours plus, as I get up to around 40 with light usage on 2.2 with battery to spare (haven't run it dead yet to be honest on 2.2) Still a little early though as the phone hasn't been drained and recharged full thus far.
I just checked my phone, and I have had it on for over eight hours, and I am at 92% battery left. I have hardly used the phone today (just a few texts is all), but going on that I should get around 80 hours on a single charge if I just leave it sitting there.

Great idea. I'm a huge continuum fan
Sent from my GT-I9000 using XDA App

good info to know...thanks alot!

This sounds like quite an undertaking. Good luck with the project. I'm looking forward to the comparisons. Thank you for your hard work to benefit Captivate owners out there.
Sent from my SGH-I897 using XDA Premium App

Charge drain charge drain lol gonna get online now and buy a new battery just incase i destroy this one.

LOcation matters
I am using JuicePlotter to monitor my battery usage closely. From what I see, different locations give dramatically different battery life. At home my battery drops 1% per hour. At work 20 miles away it drops 2% on captivate modems but 4-5% on i9000 modems. So the signal strength, cell tower type make big difference.
I have tried multiple Cog ROMs and Paragons ROMs, currently on Twingerbread 3.2. The best ROM in terms of battery life is cog 3.2 for me.

Yea but most people throughout the day are on the move and all I'm trying to achieve are results based on that. The constant will be the kernel in this test that way any thing I log can be directly attributed to the rom/modem. This by no means is the end all, but it will give the community a great idea of where each rom sits.

Interesting kernel choice. I've heard Suckerpunch lauded, but that ignores the fact that most of these roms flash with a different kernel by default. Is it a better test to run them all with the same kernel, or with the one they chose?
I dunno. Might be interesting to test and formally see how much kernel choice affects things.

[Q] voltage control tutorial?

Is there a tutorial (written or video) that shows how to use this? I've never overclocked or changed the voltage before and i dont wna just go in there n start messing with stuff when i have no clue what im doing. Ive looked around for maybe a begginers tut or like voltage control for dummies, but havent really found anything. Anyone know of one? Thanks.

It's really not very hard. The regular Voltage Control will not allow you to overvolt, so you will not run the risk of frying your processor. Don't go over 1400 mhz though. Bad magic after that.
Undervolting will not harm your phone, the most it will do is make it lock up. Just experiment with different voltages. Back in the day I used to run -75 mV across the board without many issues, but I don't really have a use for it anymore since I carry a spare battery. Don't be frustrated if your phone doesn't like even -25 mV though, because every processor is slightly different in their abilities to handle voltage and frequency changes out of spec.
Please note that PBJT kernel is already undervolted a good amount.
Sent from my SCH-I510 using xda premium

Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!

n1ghtwish said:
Here's my setup - no lag, no hiccups or freezing!!
1300mhz (max) -75mV
1200mhz -75mV
1000mhz -75mV
800 down to 100mhz -50mV
Hope this helps!
Click to expand...
Click to collapse
Can you please tell me what the actual voltage is? I found that with IMO 4.0 kernel, and with Tegrak Overclock Ultimate, I can clock the at 1.252 Ghz @ 1285mV and 1.3 Ghz @ 1330mV stably. However, I don't know what the actual stock voltage is or the PBJT voltage or IMO 4.0 voltage, etc.
I figure you could check the voltage at least with the free version of Tegrak.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stable for days... Vr ..smartassv2.. 1200 max 100 min.. Eclipse with 1/15 pb&j
Sent from my SCH-I510 using XDA App

Phone is laggy
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb

dees_74 said:
I am also new to the voltage and clock adjustments. I am finding that my phone is SUPER slow now. I used another forum member's numbers that were supposed to offer a good balance of performance and battery life. I know that every phone is a little different, but I don't want to start messing around and screw stuff up
My setup is:
1300-1400 -0
1000-1200 -50
800-900 -75
100-700 -75
I am running PBJ 415 with FP1 on Tweaked 2.0.
Please be gentle, I am a newb
Click to expand...
Click to collapse
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.

BleedsOrangeandBlue said:
Was your phone slow when you first flashed the new kernel? imnuts' kernels tend to slow down over time on my phone and I've had better luck with stock. Some people never seem to have issues.
Personally, I run the stock kernel which can't be overclocked. I do have the minimum clock speed set to 400 and the governor (which I think makes the biggest difference) set to performance. i/o scheduler is noop, but I've heard that it doesn't make a huge difference either way.
The only issues I have with speed are RAM related. I typically reboot my phone first thing in the morning just to get it going.
And battery life has maybe suffered some, but its hard for me to tell. I get horrible reception downtown, so when I need my phone I toggle data off to keep it from dying. When I'm home, I keep it on since I'm close to a charger. There's too many variables in my day to know (or even remember at this point) whether its had a significant impact.
Click to expand...
Click to collapse
My phone was great when I flashed, but within about 12 hours, things were horrible. I have since flashed back to the stock fp1 kernel, and life is good. Unfortunately, I am not a person who 'leave well enough alone'. I'd like to enter the world of over/ under clocking and see if I can gain some additional performance.
Thanks in advance for any additional info/advice you can provide.
Sent from my Xoom using XDA

shrike1978 said:
FYI, if you have the governor set to performance, then the minimum doesn't matter. That governor runs the CPU at max constantly. Great for performance, but hideous for battery life. The only time it will ever ramp down is when it goes into deep sleep, otherwise, it's running at 1GHz.
Click to expand...
Click to collapse
War Eagle!
I thought that was how it worked, but I will open voltage control from time to time and it will read that its currently at 400 or 800 MHz. Does the program not display properly?
edit: Playing around with it some more, if I change it to something else and then switch it to performance it goes right to 1000. Weird that it displays incorrectly when the program is opened.

[GUIDE] Undervolting, The Right Way

It seems alot of people dont know the proper way to undervolt their phones, so I'm gonna try to help out! This is my first attempt at a guide, and i tend to ramble so just tell me if it makes no ****-for-sense
Undervolting is great, it allows us to change the voltage in our phones while we use it! this can really increase battery life and reduce heat in the phone. but if its not done right, it causes many more problems than it fixes.
When you are following this guide you WILL have issues! This is not a generic disclaimer, it is the TRUTH! the goal here is to find out where your phone stops working, and you cant do that without causing it to STOP WORKING.
once again: THIS WILL MAKE YOUR PHONE FREEZE, IT WILL HAVE AWFUL BATTERY LIFE, AND IT WILL MAKE BAD THINGS HAPPEN​
But after its all done it should work much better
To start off, too much or too little voltage in the phone causes any number of things including:
Reboots (Screen Off and Screen On)
Lagging
Phone Overheating (Hot to the touch)
Reduced Battery Life (this includes the phone using more power, as well as reducing the battery's ability to hold a charge)
'Strange' issues with things shutting off/not working (WIFI, Bluetooth, your favorite app, ect...)
Many other 'weird' things
If you are having any of the above issues, and you are using a custom kernel, they may be caused by inproper undervolting.
THIS CAN BE THE CASE EVEN IF YOU HAVE NOT DONE ANY UNDERVOLTING YOURSELF!!!
Most custom kernels have undervolting build into them, and even 'stock voltage' versions allow overclocking, and those frequencies have no 'safe' voltage associated with them.
How to Properly Undervolt your Phone:​
*this assumes you have no idea where to start, if you have some past experience, USE IT!!!*
First, Undervolting a phone the right way is not a quick job, like most things in life the more time you put into it the better your end result will be. For me i like to take an ENTIRE WEEK OR MORE to get all my settings down right. whenever you decide to do this, expect any and all of the issues i listed above to happen while you are trying to find the right settings.
Step 1: Starting Fresh​
Disable all overclocking, undervolting, AND PROFILES on the ROM, you need to get the stock speeds working before you try to push the phone to its limit.
This will be your baseline. Use the phone like you normally do, text, call, surf the web, even let it sit in your pocket for a while. Do this for as long as you need to to be sure that everything is stable.
If you have any issues during this stage. STOP! add +25mv to every frequency across the board and start over. Do this up to 3 times if necessary, if after you have added +75mv to your stock voltage and you are still having issues, it is most likely something else in the rom causing the issue (rogue app, wrong kernel version, phone was dropped in the toilet too many times...) try to fix that first, or just try to ignore the issue, its up to you.
Otherwise, if everything is stable, Continue to step 2!
Step 2: Start Lowering Voltages​
Lower all of the voltages by -25mv across the board. (If your phone needed any voltage added over stock to be stable, skip this step.)
This is where you begin testing the waters. Once again use the phone like normal, including some screen off time, as well as some CPU intensive tasks (playing music while websurfing, gaming, ect.)
If your phone is still stable after a good amount of time, then do it again. Your looking for the moment when things start to go wrong.
When you notice your first random reboot, or you start to feel the phone getting hot, or not responding STOP! you found the limit of your phone. Go back to the last working voltages you have and use them for step 3.
The more time you spend at this step the better your overall result will be! if you dont get any symptoms in an hour, they might show up later in the day, or overnight. Just take your time and have some patience.
Step 3: Lowering Voltages Independently​
Now that you have a stable working phone. you can start lowering voltages one by one!
Starting with the lowest frequency, lower the voltage by -25mv.
Run this for a while, until you feel it is stable. Then move to the next highest voltage and do the same.
*If you have any issues, undo ONLY that frequency!!! Write down that frequency somewhere. you are done with it! you know that frequency is stable, and you shouldn't need to touch it again!!!
Keep doing this till you get to your stock maximum frequency, then continue to step 4!
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
if at 1ghz, the phone is at 1000mv and at 1.2ghz the phone is at 1150mv. the higher one needs to be lowered (set 1.2ghz to 1125mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Step 4: OVERCLOCKING!​
At this point you should have a completely stable phone with no overclocking, grats! Now you get to start raising the frequency.
starting with the next highest frequency, set it to its stock voltage. if this is more than 100mv (125mv for Morfic's kernels) more than the previous frequency, set it to 100mv (125 for morfic) more than that.
run this until it is stable, and keep reducing it as much as you feel until you find instability. set it one step higher and move on to the next highest frequency.
if, after setting the voltage to 100mv (or 125mv) more than the last one, it is not stable, you need to raise the lower frequency's voltage up. sometimes this can cause a chain reaction that makes you raise 3, 4, or even all of the other frequencies up, if this happens you need to decide if that frequency is worth it to raise all the other frequencies to the next level.
If all is running good, proceed to step 5!
Step 5: The part where you hate me ​
(this step is optional, its just something i do to help with stability)
Now that you have a fully overclocked phone that is running as low of a frequency as it can safely, raise all of the voltages up by +25mv!
yes yes, i know, it sounds retarted to just undo that hard work and all that time you just put into finding the perfect voltages, but just hear me out.
Even if you spent a week on each step, did everything perfectly and tested everything you ever do on your phone and it is all completely stable. one day you are going to do something that will push the phone, which is running at its limit. so by adding 25mv to everything you are giving yourself some insurance. you may loose some battery life (i honestly don't ever notice a change with only 25mv) but when your phone alarm goes off in the morning to get you up for class, or you get that call you got that job you wanted, just be happy its not frozen on the table, or black screened in your pocket.
There you go! you should now have a stable phone with great battery life, and now you can stop bugging the devs about 'that strange reboot that is still there' or 'how every time you use his kernel you get black screens'
To Long; Didn't read Version:​
If your having issues with your phone and you think its related to UV, and your much too busy/lazy/cool to read the above, try this: (Results will most likely be worse...)
Set (all of) your lowest voltages to 775mv (or 750 if you think your phone can do it)
Set your 1ghz voltage around 1000mv (give or take 50-100mv)
Set the highest speed to no more than 100mv below its stock seting.
Set the rest of all the speeds below 1ghz on a line between it and the lowest, and after 1ghz on a line between it and the highest. ex(From Morfic's T15 Kernel):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Post any questions or feedback you have, ill try to answer it as best i can!

Truly a great guide. I agree mostly with the last part, my alarm stopped ringing two days in a row, so I added 25 mv across the board, and it works perfectly. Thank you on behalf of the community, everyone will appreciate this guide for sure.

Helped fix an overheating problem!
Sent from my LG-P999 using XDA

This is done using setcpu?
Sent from my LG-P999 using XDA

imoumni said:
This is done using setcpu?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Any CPU managing app. I use CPU Master but there's lots more options out there. I don't use SetCPU because it took nearly a year to update.
Sent from my amazing LG G2x running Bionix Reloaded v1.4

Klathmon said:
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
at 1ghz, the phone is at 1000mv if at 1.2ghz the phone is at 1200mv. the higher one needs to be lowered (set 1.2ghz to 1175mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Click to expand...
Click to collapse
First off, thanks for this guide. I do rely on my phone's alarm clock pretty regularly so I'll have to start setting another alarm clock while I do this. Also, consider posting this in Android General to reach a larger audience.
My only question: I understand what you're saying, but I think your example may be incorrect. 1200mV - 1000mV = 200mV difference, so you would need to change one or the other by 75 to 100mV, right?

This is done using setcpu?
Click to expand...
Click to collapse
It can be done with any app that works with this phone.
I use an app called "System Tuner Pro" because it allows you to add voltage from stock settings (my phone seems to like a minimum voltage of 775 vs the 750 that most kernels start with) and im not sure any more but i think its free...
r4d14n7 said:
My only question: I understand what you're saying, but I think your example may be incorrect. 1200mV - 1000mV = 200mV difference, so you would need to change one or the other by 75 to 100mV, right?
Click to expand...
Click to collapse
thanks, yeah thats what i meant to say
All Fixed

Klathmon said:
It can be done with any app that works with this phone.
I use an app called "System Tuner Pro" because it allows you to add voltage from stock settings (my phone seems to like a minimum voltage of 775 vs the 750 that most kernels start with) and im not sure any more but i think its free...
thanks, yeah thats what i meant to say
All Fixed
Click to expand...
Click to collapse
No problemo. Looks like System Tuner is free but the Pro version is $3.99. How is it on resources? That's the only thing that worries me about these jack-of-all-trades apps.

r4d14n7 said:
No problemo. Looks like System Tuner is free but the Pro version is $3.99. How is it on resources? That's the only thing that worries me about these jack-of-all-trades apps.
Click to expand...
Click to collapse
it keeps a service running all the time, but is very CPU friendly, and wont hog resources. So far it hasn't been a problem for me at all.
and just for full disclosure; the dev is a close friend of mine, so i may be a bit biased
EDIT: added a quick "help im lazy" version for people that dont want to put the time/effort into doing it the right way.
Sent from my LG-P999 using Tapatalk

thanks for this

Thank you, this was very helpful!

Thanks for taking the time to make a great post.
I just started to OC/UV my G2X. I will use this as a guide.
-Thanks again

a noob question, Whats the difference between an app (eg, setcpu, pimpmycpu etc etc) lowering the voltage for you and "one doing it via your guide"

cricketAC said:
a noob question, Whats the difference between an app (eg, setcpu, pimpmycpu etc etc) lowering the voltage for you and "one doing it via your guide"
Click to expand...
Click to collapse
not really sure what you mean, to the best of my knowledge, no programs out there automatically undervolt for you. you use those programs to reduce or increase the voltage in each frequency yourself.
Hope that helps

Klathmon said:
not really sure what you mean, to the best of my knowledge, no programs out there automatically undervolt for you. you use those programs to reduce or increase the voltage in each frequency yourself.
Hope that helps
Click to expand...
Click to collapse
sorry, my bad. I just flash faux kernel. I thought all frequencies worked at the same voltages (silly me!) lol. Thatswhy when i saw there were different voltages for every frequency, i thought this guide was about that. (i.e i thought faux already did it for us in his kernel). lol
If my phone is stable at the current voltages that came with faux kernel, should i still try lowering them?
How much of a battery life can i get if i lower them by -25mv?
Lets say, i flash another kernel in the future and then reflash any oc/uv later on. Do i have to do these steps again or just simply input the (uv)values which i get after doing it right now?

cricketAC said:
sorry, my bad. I just flash faux kernel. I thought all frequencies worked at the same voltages (silly me!) lol. Thatswhy when i saw there were different voltages for every frequency, i thought this guide was about that. (i.e i thought faux already did it for us in his kernel). lol
If my phone is stable at the current voltages that came with faux kernel, should i still try lowering them?
How much of a battery life can i get if i lower them by -25mv?
Lets say, i flash another kernel in the future and then reflash any oc/uv later on. Do i have to do these steps again or just simply input the (uv)values which i get after doing it right now?
Click to expand...
Click to collapse
its up to you. personally, i would follow the "if its not broken, dont fix it" rule. if your happy with the current battery life, and you like the stability, no need to change it. But if you really want to go for broke, and squeeze every last bit of battery life out of this phone, then by all means go for it (you can ALWAYS undo it all) although -25mv most likely wont make much of a difference.
and to the second question, as long as its the same kernel, the same values should be alright, but each kernel is different. (i can get -50mv more on faux123's kernels, but i get better battery life on Morfic's even with the higher voltage)

Since we all have the same phone couldn't we all use the exact same voltages? and are the ones pictured yours?

noxary said:
Since we all have the same phone couldn't we all use the exact same voltages? and are the ones pictured yours?
Click to expand...
Click to collapse
Voltage depends on the chip (CPU) you have - every chip is different. you need to try playing with it according to what your chip can endure.

Klathmon said:
its up to you. personally, i would follow the "if its not broken, dont fix it" rule. if your happy with the current battery life, and you like the stability, no need to change it. But if you really want to go for broke, and squeeze every last bit of battery life out of this phone, then by all means go for it (you can ALWAYS undo it all) although -25mv most likely wont make much of a difference.
and to the second question, as long as its the same kernel, the same values should be alright, but each kernel is different. (i can get -50mv more on faux123's kernels, but i get better battery life on Morfic's even with the higher voltage)
Click to expand...
Click to collapse
If I end up squeezing every bit of juice, wouldn't that make my charger life short?

This guide needs a sticky!
Thank you for taking the time to write this.

Advice on battery life, Beans 14/lean kernel

Hey guys, I'm new to this forum but not Android Central. Anyways, I just recently switched to jelly beans build 14 w/lean kernel. For some reason my battery life is just terrible. I'm just barely making it through an 8 hour workday, and that's not even using it that much. I was wondering if you guys had any tips for good battery life on this ROM/Kernel combo. I do have set cpu installed and running but I'm only Overclocked to 1.6 and undervolting by 50 mv. I also have a save battery life profile that drops it down to 1026 when the screen is off, it's charging, or battery is below 40%. Can you guys give me advice on settings to use to save battery life? I really like this ROM and kernel but I'm getting such terrible battery life. I think it's probably more user error than anything but maybe you guys could provide some tips.
Thanks in advance.
Nick
sent from my Galaxy S3 on beans 14 via tapatalk 2

How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
http://rootzwiki.com/topic/31329-ke...nimalistic-kernel/page__st__1410#entry1042976
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!

nicholi2789 said:
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
Click to expand...
Click to collapse
I actually have my voltages set to exactly what Imoseyon has listed for the nominal cpu. As far as my screen off, I honestly just picked a low number and since I don't see lag I keep it there haha in addition, I use interactive governor which scales up the cpu once the screen comes on so it balances out either way.
To check which cpu type you have, do this. Details on what the cpu differences are included in the link as well. Matching your cpu type and adjusting your voltages may help extend your battery life but some say it is marginal.
No, your radio actually stays the same unless you manually flash a different one. I should also ask, what else do you have enabled? For example, in Maps/Settings, do you have everything disabled except "Enable Location History"?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2

nicholi2789 said:
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Click to expand...
Click to collapse
Well it's under Location Settings but if you have Maps frozen until needed then it's an unnecessary step. You have done even more than I do or suggest haha I haven't frozen anything.
What would you say you're seeing as your average screen on time?
Sent from my SCH-I535 using xda app-developers app

Oh average screen on time is probably around 2.5 to 3 hours or so. Nothing crazy. I just wanna get my battery life back to before, where basically I could leave home fully charged and work a 10-12 hour day and come home with around 30% or so battery life. That's good enough for me.
So about these recommended voltages. I have the "fast" processor, should I just st the voltages for what he recommends? Are those recommended for bet battery life or best performance? I want to undervolt as much as possible without creating an unstable system or causing damage.
And can you help me understand the governor settings, my understanding is that "ondemand" activate both cores when needed, and interactivex is all the time? Is that roughly correct?
sent from my Galaxy S3 on beans 14 via tapatalk 2

Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!

nicholi2789 said:
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
Click to expand...
Click to collapse
Yea flashing kernels and roms is very addicting. Since you have a fast cpu, you can actually UV much lower than I can with my nominal cpu. You can set your voltages to match Imoseyon's table and you'll be fine or maybe try lower. I know from experience that I can't UV lower than 900 mv without my phone immediately locking up lol You can even hold off on setting voltages at boot if you want to get a feel for performance while UV'ed.
I can't really speak on OC vs. regular clock battery life, I keep mine OC'ed at 1.62 ghz so I'd notice minor drops in battery life compared to say 1.8 ghz. I don't even have much need for that since its fast enough to me as is. I haven't noticed too much of a hit on battery, I still range between 2.5-4 hours screen on pending if I'm on LTE or wifi during that charge.
Also, if you want to try your hand at really digging into kernel settings then you should also check out the the Team Kernelizer's thread for KT747 kernel. Personally, I use LeanKernel cuz it works really good for me so I applied some settings from there but not everything was applicable. This thread has some really knowledgeable people in it. Definitely give KT747 a look, or any other kernel for that matter, and see which ones you like the best.

Yeah i think i may have had a bad battery. I checked and I know my phone is deep sleeping, but since adjusting my voltages and settings last night it'd definetely improving. I have my voltages set to 25mv under what is recommended on that chart down to 1.4 the in the lower clock settings o have it exactly at the recommended settings. Seems to work okay. I have set on boot enabled but i also have the stock voltage settings on my SD Just in case of a boot loop.
sent from my Galaxy S3 on beans 14 via tapatalk 2

Does anyone have any suggestions? I really like this ROM and would prefer to keep it if possible but this battery life is terrible. Ant ideas on some measures I could take to try and improve it a bit?
I wiped cache partitions, davlik cache, and did factory reset before installing. I even do them twice just to be sure.
Would maybe wiping and re flashing the Rom help? I'm totally stumped here.
sent from my Galaxy S3 on beans 14 via tapatalk 2

I don't understand. I used cpu spy and i know phone is deep sleeping. I have set CPU to drop the clock speed when screens off.
Why the heck is it using so much battery? I'm dropping about 6-7% battery at idle. Somebody shed some insight.
sent from my Galaxy S3 on beans 14 via tapatalk 2

Recommendations for kernel/ROM with good battery life

Hi,
I switched from my Galaxy S2 to a Note 3, and I'm immediately running into serious issues with battery life. After switching to low-power mode and after reconfiguring my SetCPU, I get about 16 hours with screen off and Wifi on. So, time to switch ROMs, and looking through the forum, I am unable to find any kernel/ROM comparison based upon battery life. Therefor would like to hear recommendations.
Have been looking at the X-Note, but besides a remark to pick the X-kernel for battery life for the v8.0 version, I am unable to find any info for the v7 JB version.
Looking forward hearing your experience.

geoff2011 said:
Hi,
I switched from my Galaxy S2 to a Note 3, and I'm immediately running into serious issues with battery life. After switching to low-power mode and after reconfiguring my SetCPU, I get about 16 hours with screen off and Wifi on. So, time to switch ROMs, and looking through the forum, I am unable to find any kernel/ROM comparison based upon battery life. Therefor would like to hear recommendations.
Have been looking at the X-Note, but besides a remark to pick the X-kernel for battery life for the v8.0 version, I am unable to find any info for the v7 JB version.
Looking forward hearing your experience.
Click to expand...
Click to collapse
X-Note is a good choice, X-Note is one of the reasons why I bought a note 3(Since he was developing for note 2 first but went over to the note 3). Changing DPI is manditory for me. Default DPI is for my grandpa so he can read the screen without glasses -.-. Batterylife is quite good for me. Haven't reached 40% after a day yet.

Armazia said:
X-Note is a good choice, X-Note is one of the reasons why I bought a note 3(Since he was developing for note 2 first but went over to the note 3). Changing DPI is manditory for me. Default DPI is for my grandpa so he can read the screen without glasses -.-. Batterylife is quite good for me. Haven't reached 40% after a day yet.
Click to expand...
Click to collapse
Thank you for the info. May I ask which version you're using, the JB (7.0) or KitKat (8.0)? And, what is the X-Note Transformer compared to v7.0?
And, most important, which kernel are you suing?

Mate if you are getting 16 hrs of screen off time and no screen on time, it is not a Kernel/ROM problem, you have a rogue app installed which is causing your phone to be constantly awake and draining battery.
Definetly go for the 4.4 since it updates to KitKat which offers many benefits. There are also slight improvements in battery life.
As for the ROMs I've tested all Custom ROMs and honestly it's about preference. Check the additions they provide and decide what's best for you. I'm a battery nut and believe me none of the ROMs add any actual benefit to battery life over stock for 4.4.
Personally for me, since I love a lean install and don't like that much modifications I found Stock Samsung 4.4 works best for me. I just use ES file explorer to debloat it from all the apps I don't want and procede to installing the apps I use I've found that you can expect around 6.5 hours of on screen time with auto brightness +5 and no rogue apps (no apps that require constant gps syncying and what not) spread over from 1 to 3 days depending on how you use your phone. That is light web browsing, chatting and movie watching. Games will suck your battery dry like space fuel on the Note 3.
As for the Kernel on the 4.4 bootloader you don't have a lot of choices. Afaik the only ones available at the moment and CustomN3 and FlexKat engine. Considering you are asking for battery life I'm guessing you are more interested in power perserving than overclocking. I would go with FlexKat since it supports intelliplug and intellidemand gov. Actually I am testing it at the moment my self. I get 1k more points in AnTuTu using intelliplug and intellidemand compardd tl Stock Kernel. Seems pretty smooth and stable for now, haven't run in any issues but I've only been uskng it since last night. Battery usage for now is 35%, with 2.5 hours of screen time and over 16 hours of total since uplugged. Can't really compare to Stock Kernel yet but it doesn't seem like there will be any major difference.

I tried all roms actually, But nothing suited me. Till I jouned x-note. From x-note 7 I waited till 8, and installed it the same day it came. 8 is super stable, havent had problems(except for some apps which arent compatible with kitkat).

Thanks for the feedback, which I highly appreciate. I must admit being kind of a battery freak too, and I like a UI to be simple and practical. My golden rule is that whenever I carry the mobile in my pocket, I don't care about speed. Just keep them as low as possible in order to keep running stable.
When I look at what's draining the battery then at the top are Cell Standby 18%, Android OS (4.3) 18%, Device Idle 11% and my K-9 email app which stays active 11%. And these numbers are with low power mode activated, and with SetCPU setting minimum frequencies with screen off (the stock kernel doesn't allow for a voltage configuration). When staying with the same OS 4.3, I may be able to improve this by maximum 30%, in going from 1.2V to 800 or 850 mV in standby.
I'll give the X-Note 4.4 a try, and using the X-kernel may then also be beneficial. Will report on the result.
Thanks

Sweet Rom for the stock-look custom rom, battery life is great!

arkin56 said:
Sweet Rom for the stock-look custom rom, battery life is great!
Click to expand...
Click to collapse
That's a 2nd one on the list. Can you please be more specific about the battery life? How does it compare with what was mentioned for the X-Rom?

Armazia said:
I tried all roms actually, But nothing suited me. Till I jouned x-note. From x-note 7 I waited till 8, and installed it the same day it came. 8 is super stable, havent had problems(except for some apps which arent compatible with kitkat).
Click to expand...
Click to collapse
Wanted to do the flash and ran into a question. I downloaded the Poland KitKat official ROM, but the poor thing is only 3 MB and when I try to open it, both windows and winrar, I get the message "unknown format". Is it maybe only a patch that's applied to the 4.3? But then I should still be able to open it. Any advice?

geoff2011 said:
Wanted to do the flash and ran into a question. I downloaded the Poland KitKat official ROM, but the poor thing is only 3 MB and when I try to open it, both windows and winrar, I get the message "unknown format". Is it maybe only a patch that's applied to the 4.3? But then I should still be able to open it. Any advice?
Click to expand...
Click to collapse
Got it resolved. Only the MIRROR seems to give a reliable download.

Also try my battery saving tips here! Good Results!
JellyBean
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KitKat