Which ROM/kernel has the best battery life?
This is the most-asked and most obsessed over question on these forums BY FAR. So I created this thread in order to compile a comprehensive guide to ROM battery life, based on AWAKE TIME. Up Time means nothing in this competition because according to HTC, the Incredible has the ability to go 146hrs of standby time (aka. up time) ON THE STOCK BATTERY!!!
The premise is this, show off your best battery stats on your favorite ROM/kernel combo by posting in this format:
[Rom Name & version] ex. Virtuous 3.1
[Kernel Used] ex. Stock HTC v4
[Battery Used] ex. HTC 2150mah
[Up Time] ex. 14hrs
[Awake Time] ex. 5.5 hrs*** What this competition is really looking for.
[Screenshot of Battery Use] (only way i know how to verify actual time since unplugged)
Click to expand...
Click to collapse
Just in case people don't know this, if you plug in your phone, IT DOES NOT RESET YOUR UP TIME OR AWAKE TIME. So be aware of this. So far the only way i know to check this is by requiring a screenshot of the battery use page, and verify that the "Time since unplugged" matches the Up Time (within 5 mins is fine). If anyone can think of a better/more efficient way to check this, please let me know
I will compile the results in this OP to come up with the results and rank in order of AWAKE TIME. So show off your best battery day and let the ROM Battery War begin!
Relocate....
To General?
Nayners said:
To General?
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
scottylove said:
Which ROM/kernel has the best battery life?
This is the most-asked and most obsessed over question on these forums BY FAR. So I created this thread in order to compile a comprehensive guide to ROM battery life, based on AWAKE TIME. Up Time means nothing in this competition because according to HTC, the Incredible has the ability to go 146hrs of standby time (aka. up time) ON THE STOCK BATTERY!!!
The premise is this, show off your best battery stats on your favorite ROM/kernel combo by posting in this format:
[Screenshot of Battery Use] (only way i know how to verify actual time since unplugged)
Just in case people don't know this, if you plug in your phone, IT DOES NOT RESET YOUR UP TIME OR AWAKE TIME. So be aware of this. So far the only way i know to check this is by requiring a screenshot of the battery use page, and verify that the "Time since unplugged" matches the Up Time (within 5 mins is fine). If anyone can think of a better/more efficient way to check this, please let me know
I will compile the results in this OP to come up with the results and rank in order of AWAKE TIME. So show off your best battery day and let the ROM Battery War begin!
Click to expand...
Click to collapse
Ok, so I think this is an interesting question. It's valid as well. BUT, I must stop short of saying it's scientific and would produce meaningful results. It will not. I admire your enthusiasm and initiative, but a casual investigation of empirical results on this forum suggests strongly that no two people with the same combination of kernel/ROM are likely to get exactly the same results. One of the biggest factors, often ignored, is your baseline signal strength. CDMA phones are constantly in communication with the towers, and the strength of those signals impacts directly the duration of a battery cycle.
A more scientific study may go something like this: (and you would have to get everyone to support this unified protocol)
1. Charge you battery completely (be it bumped, not bumped, turned on, turned off, what have you...)
2. Turn the phone on (if it's off) and be sure it's in airplane mode. Now we've taken towers and radios out of the equation.
3. Using a task-killer, be sure all non-essential tasks are dead.
4. Ensure that background data and autosync are off. They may try to communicate at set intervals even in airplane mode (and eveyone has different intervals set)
5. Now, so that everyone doesn't have to wait around for three days as their battery slowly drains, you must begin a standardized battery drain protocol. I would suggest setting up a live wallpaper (one of the more intensive ones) and then setting the 'display timeout' to 'NEVER'. Just let it sit there and check the battery level at certain intervals. It doesn't matter what exactly the intervals are, just that they are recorded. Then, we could produce some graphs.
This would produce more meaninful results, but good luck at getting many people on board. Until then...just stick with the method of trying the combos out for yourselves. Don't waste time reading a bunch of other people's experiences that are completely irrelevant to you. And yes, I realize this is a potential thread killer. I'm just too passionate about science to let these things get very far
I dont believe AOSP roms show awake time, only up time.
Epicardium said:
Ok, so I think this is an interesting question. It's valid as well. BUT, I must stop short of saying it's scientific and would produce meaningful results. It will not. I admire your enthusiasm and initiative, but a casual investigation of empirical results on this forum suggests strongly that no two people with the same combination of kernel/ROM are likely to get exactly the same results. One of the biggest factors, often ignored, is your baseline signal strength. CDMA phones are constantly in communication with the towers, and the strength of those signals impacts directly the duration of a battery cycle.
A more scientific study may go something like this: (and you would have to get everyone to support this unified protocol)
1. Charge you battery completely (be it bumped, not bumped, turned on, turned off, what have you...)
2. Turn the phone on (if it's off) and be sure it's in airplane mode. Now we've taken towers and radios out of the equation.
3. Using a task-killer, be sure all non-essential tasks are dead.
4. Ensure that background data and autosync are off. They may try to communicate at set intervals even in airplane mode (and eveyone has different intervals set)
5. Now, so that everyone doesn't have to wait around for three days as their battery slowly drains, you must begin a standardized battery drain protocol. I would suggest setting up a live wallpaper (one of the more intensive ones) and then setting the 'display timeout' to 'NEVER'. Just let it sit there and check the battery level at certain intervals. It doesn't matter what exactly the intervals are, just that they are recorded. Then, we could produce some graphs.
This would produce more meaninful results, but good luck at getting many people on board. Until then...just stick with the method of trying the combos out for yourselves. Don't waste time reading a bunch of other people's experiences that are completely irrelevant to you. And yes, I realize this is a potential thread killer. I'm just too passionate about science to let these things get very far
Click to expand...
Click to collapse
I agree this is not a laboratory experiment with variables and controlled environments. I did not intend it to be this way, this is a statistical survey that would seek to find maximum and mean REPORTED battery times by respected members of this forum. Surveys and polls are used to predict presidential elections, determine product interest for advertisers, and for scientific research.
I appreciate your input but do not discredit valid research methods because it cannot be controlled. That is not the point!
lies, damn lies, and 'you know what'
scottylove said:
I agree this is not a laboratory experiment with variables and controlled environments. I did not intend it to be this way, this is a statistical survey that would seek to find maximum and mean REPORTED battery times by respected members of this forum. Surveys and polls are used to predict presidential elections, determine product interest for advertisers, and for scientific research.
I appreciate your input but do not discredit valid research methods because it cannot be controlled. That is not the point!
Click to expand...
Click to collapse
If this is an opinion poll, then so be it. But, I hope you're not insinuating that opinion polls are reliable; particularly political ones. Rather, I would say this kind of data collection is more likely to lead people astray, or confuse them all the more. And we all know what they say about damn lies, err, statistics...
No harm no foul. Carry on.
This should be posted in general.
Feather's already got this:
http://androidforums.com/incredible-roms/199848-rom-feather-v1-7-a.html
ToyTank said:
This should be posted in general.
Click to expand...
Click to collapse
Then report the thread and request that it be moved to General. I don't know if I was the only one reporting threads, but since I stopped a few weeks ago the Development forum has become a complete mess. If you (or anyone else) want to take up the mantle, feel free.
Epicardium said:
If this is an opinion poll, then so be it. But, I hope you're not insinuating that opinion polls are reliable; particularly political ones. Rather, I would say this kind of data collection is more likely to lead people astray, or confuse them all the more. And we all know what they say about damn lies, err, statistics...
No harm no foul. Carry on.
Click to expand...
Click to collapse
I'm not over serious about this thread, or statistics. Never did i say anywhere this would provide conclusive, anal, scientific facts. I just thought this could be kinda fun getting people trying to best each other in battery life and let the ROM fanboys go at each other, while it also might provide some interesting info to boot. Didn't know some people took this so serious!
I think everyone is being a wee bit to serious on this one... I will post screen shots this weekend, but in the past I have made it to 15hr 46min on one charge with moderate use... I will see if I can duplicate, but This very well can show people which Rom/Kernel combinations are best... or atleast worst think about it if you have a 6 hour difference average between two ROM/Kernel combos you would know which one to pick right? Give the guy a break it is a good poll to have!
This is a very real concern which has been plaguing the Dinc since the beginning. Im all for it if we can knock out as many variables as possible and make sure each phone tested has all the info available.
For example.
Rom
Kernel
Radio
Battery
OV or not
Maybe like do a different combination of the above each couple of day or week. Like in the thread title put [Now testing skyraider with kkbfs#5 9.01 radio].
Or ya know like whatever
kungfuturkey said:
I think everyone is being a wee bit to serious on this one... I will post screen shots this weekend, but in the past I have made it to 15hr 46min on one charge with moderate use... I will see if I can duplicate, but This very well can show people which Rom/Kernel combinations are best... or atleast worst think about it if you have a 6 hour difference average between two ROM/Kernel combos you would know which one to pick right? Give the guy a break it is a good poll to have!
Click to expand...
Click to collapse
EDIT: HA! as i was writing my post lanxcom above posted the same suggestion
I agree, give the guy a break.
My observation on battery is that it does play a huge role on what rom/kernel you have. That's a given.
The problem is that there is no standard on usage; moderate, heavy etc. means different things to different people.
Another problem is conditions and differences in process power from apps. Angry birds for example uses a lot of battery but some other games do not. Same goes for Skype that doesn't seem to die and always lurks in the background.
Finally, you are running into all sort of other situations such as different battery brands and mah, different types of amoled/lcd screens might be an issue, bump charging etc.
Well, you get the point. There are so many variables and unless you want an actual statistical analysis that is going to be as close to accurate as it will ever get, you will have to standardize the situations as much as possible.
A group of people willing to test rom/kernels on their phones and keeping the variables constant will be the ideal case i can think of.
I'm not trying to bash anyone, i'm trying to help. Cheers!
Here's what I got, all the device info's in my sig. Typical day for me, nothing special. I do have the Seidio 1750mAh battery and bump charged.
{
"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"
}
This is the best battery life I ever had, other issues made me switch though. I don't use that set up anymore, had to reboot every 24hrs or phone would crawl.
I am using 9.01 radio now, and I am seeing good battery life still.
Screenies are current setup. Very light use while hunting, but great uptime.
-HTC1500 Batt. External charger to 4.223v
-Adrynalyne experimental SS UV Kernel.
-Skyraider 3.3.1 Sense
-9.01 Radio
-No SetCPU
-Autobrightness
-GPS ON
-Wifi ON
-Sync ON
Sorry if post is sloppy, I haz need sleep.
This is my best battery life:
Consistant texting, a few phone calls. I think two pictures, 1:30-2:00 of angry birds and 1:30 or gameboid. They disappeared from battery stats after awhile.
I turned off 3g at night when I was sleeping, no Juice defender, no setcpu. Cyanogen 6.0.2 ril fix and King's CFS #2 (AOSP)
Related
Ive spent the last few days fiddling and testing stuff to increase battery life. Here is what i have learnt...
(Im running R2BA026)
Firstly, personally i do not want to lose any functionality/performance in order to gain battery life. I think that if you are going to spend the money to get a phone with awesome hardware it should be able to run at full whack.
This guide will not be useful to all, but hopefully it will be handy to those in my situation.
This is a guide for what i have found to be the best compromise between battery life and user experience, with the emphasis being on user experience.
My specific goals are:
- I do not want to lose any performance i.e cause any slowdown/choppiness.
- I am only looking for a 24h battery life as i can charge every night.
- I want to be able to use my phone without worrying about battery. Specifically I never want to think "i shouldnt do that it might run down my battery". I should be able to use all the features on my phone without questioning if i can afford to.
-=-
In my experience using a task killer resulted in only minimal gains to battery life but it meant that opening up apps could be a lot slower and apps could be choppy just after opening them.
Additionally the idea of setCPU is a good one however when coming out of sleep or opening an app it takes a little while to get back up to speed. This also causes choppiness. Personally I find lag/choppiness a real pet peeve, it irritates me alot, so I do not use setCPU either. It is true that with careful set up the lag can be minimised but then the battery life gains are also minimal, so I choose to keep full performance and dispense with setCPU. Bear in mind that the hardware platform is already very efficient and well optimised so a software solution will pretty much be a straight trade of performance for battery life.
-=-
With those two common options out of the way, what else can be done to save juice?
Well generally the biggest consumer of energy is the screen. The simplest option is just to turn it down to minimum brightness, but in my opinion that is not a good solution, its too nice a screen to have dimmed all the time. Thankfully the auto-brightness does a pretty good job of keeping the back light at a good level. It can be a bit disconcerting if you enable it when using full brightness as the drop can seem somewhat dramatic but don't let that put you off, give at 1/2 a day or so and you wont even notice.
Other easy but important things you can do are turning the screen timeout to minimum and always turning off the screen (power button) as soon as you are finished. They are tiny changes but really do make a big difference.
-=-
Onto wifi...
I think there may be a bug with the firmware because if I disable wifi I get a HUGE increase in battery life when Im at home. I have good 3g coverage here and a 3GB allowance so I only need to turn on wifi when Im browsing the web or market, seeing as it takes seconds with the widget this option suits me fine.
I suspect that when the phone is connected to wifi it doesn't sleep properly so drains very fast.
Only turning on wifi when i want it made by far the biggest difference to me, and as it doesn't affect my user experience in any appreciable way I am happy to do it.
I think its a good idea to mention app/widget updates and refreshes here, personally i have all my widgets and apps set to refresh only once a day, that suits me fine because I can refresh them all manually very easily if I want to to be absolutely up to date and I'm not a twitter or facebook addict Most of my widgets are news/article based so once a day is perfect.
-=-
GPS, again this is rather obvious, if you don't use it, turn it off. Personally i use latitude so I have it turned on all the time. Android seems very good about only using it when it is needed and the phone seems to get a fix very quickly so in reality it doesn't spend much of the day being active.
Same goes for bluetooth, although I don't use it so it stays off.
-=-
Nothing i have said here is particularly revelatory mostly common sense but I have always had battery issues often with the battery lasting ~12 hours before asking to be charged.
Updating to 026 made a big difference and following these rules means my battery drains on average 2-2.5% an hour under normal use.
Normal use for me:
-Wifi Off
-GPS on (With latitude widget)
-Gtalk always running
-3 news widgets + timescape
-frequent texting
-moderate calls
-frequent fiddling
The phone is very very snappy, everything apart from timescape opens as near to instant as makes no odds, the phone is a pleasure to use. My battery life has comfortably doubled without the use of any apps or any loss of performance.
Mission Accomplished
Thanks
Cheers for that. Very interesting .
I definitely agree about the task killer apps, the OS does a perfect job at running itself!
One question, Am i correct in presuming you have 3g always running? Network mode set to GSM/WCDMA preferred? Ive been afraid to do this as i have it in my head that 3g eats up my battery for fun! I'll have to try it out.
Thanks again!
I bought an extended battery for my X10 the sloping sides stop it looking like a brick. The G1 always looked like a brick with an extended battery but the X10 sloping sides do serve a purpose.
helliewm said:
I bought an extended battery for my X10 the sloping sides stop it looking like a brick. The G1 always looked like a brick with an extended battery but the X10 sloping sides do serve a purpose.
Click to expand...
Click to collapse
I prefer this:
{
"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"
}
bjohnny85 said:
Cheers for that. Very interesting .
I definitely agree about the task killer apps, the OS does a perfect job at running itself!
One question, Am i correct in presuming you have 3g always running? Network mode set to GSM/WCDMA preferred? Ive been afraid to do this as i have it in my head that 3g eats up my battery for fun! I'll have to try it out.
Thanks again!
Click to expand...
Click to collapse
Yep, thats correct With the 3g on it seems to stay in 2g when sleeping then switch to 3g when you wake it, you can see the change in the status bar about a second after waking. Pure speculation though ...
Well, let us know how you get on with 3g active all the time
helliewm said:
I bought an extended battery for my X10 the sloping sides stop it looking like a brick. The G1 always looked like a brick with an extended battery but the X10 sloping sides do serve a purpose.
Click to expand...
Click to collapse
I love how slim the x10 is, that combined with the fact that the 3rd party backs are ugly and can be poor fitting mean an extended battery isnt really an option for me, whatever suits though ^^
iead1 said:
I prefer this:
Click to expand...
Click to collapse
Nice one where i can get one.
Sent from my X10i using XDA App
I certainly plan on getting a pair of bluetooth headphones, will be interesting to see how they affect battery life...
TechGuru_x10 said:
Nice one where i can get one.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
It's from Sanyo. It's being released in Japan in October, but, I'm sure it will come out internationally as well.
James thanks u were helpful
Sent from my X10i using XDA App
Some additional tips based on my personal experience:
-Using a third-party task launcher helps too. Some may not agree, but it works for me.
-Use a third-party digital clock widget instead of the stock one. Again, YMMV.
-Use a third-party(AGAIN!) MP3 player instead of Mediascape. I'm using Meridian, and notice an increase in battery life when playing MP3s.
I like having some control so I run task killer but there's no auto-kill enabled and if I know the phone is just going to turn it back on in 5min, I don't bother killing those apps. Maybe I should just remove it altogether, but it seems convenient to be able to kill an app at will (I do it with windows sometimes).
mmsbludhound said:
-Use a third-party digital clock widget instead of the stock one. Again, YMMV.
...
Click to expand...
Click to collapse
I think the reason why you find that the stock one drains your battery is due to the "use network provided values" being checked in the date and time settings.
Interesting article. I am running 024 and my battery is life is poor. I managed to get seven hours use yesterday after a full charge. My usage throughout the day wasn't anything too crazy. Where I work I get only a standard signal (no 3G). I seem to get a better battery life.
Sent from my X10i using XDA App
I agree battery life is horrible. It makes me really miss my blackberry.
Even when battery life is low, charging it takes FOREVER, not to mention if you plug it in and play with it at the same time, it charges even slower.
My Blackberry Tour charged fully in what seemed like 45 mins from less than 10% batt life. I know they are different phones, but it just really sucks to me.
I'm debating going back to a blackberry now. The X10 and other android phones (and Iphone), are more toys than anything else.
/end rant.
hehe sorry
Thats odd, my phone charges pretty damn fast, just a few days ago i was pleasantly surprised that it charged from completely empty (id forgotten to charge it) to ~80% in less than an hour.
Ballfuzz said:
Even when battery life is low, charging it takes FOREVER, not to mention if you plug it in and play with it at the same time, it charges even slower.
Click to expand...
Click to collapse
Hmm, mine charges from <10% to 100% within 1 - 2 hours.
Make sure you are charging by AC, charging by USB does indeed take forever.
mmsbludhound said:
Hmm, mine charges from <10% to 100% within 1 - 2 hours.
Make sure you are charging by AC, charging by USB does indeed take forever.
Click to expand...
Click to collapse
Yeah I agree by USB takes forever.
JamesBarnes said:
Additionally the idea of setCPU is a good one however when coming out of sleep or opening an app it takes a little while to get back up to speed. This also causes choppiness. Personally I find lag/choppiness a real pet peeve, it irritates me alot, so I do not use setCPU either. It is true that with careful set up the lag can be minimised but then the battery life gains are also minimal, so I choose to keep full performance and dispense with setCPU. Bear in mind that the hardware platform is already very efficient and well optimised so a software solution will pretty much be a straight trade of performance for battery life.
Click to expand...
Click to collapse
Quite interesting for me, I decided to add some statistical experiment about it.
Under my situation and environment. (I won't go in detail, sorry about that)
With SetCPU were 2.32% per hour without any usage.
W/O SetCPU were 3.18% per hour without any usage.
or approximately 7% maximum saving per day time. (for me)
My SetCPU only effected sleep state.
Not a big deal but still significant different, but it could survive for whole day anyhow.
I'm more interested about Killing app. I might try after this as I see many argument about it.
Cebees said:
Quite interesting for me, I decided to add some statistical experiment about it.
Under my situation and environment. (I won't go in detail, sorry about that)
With SetCPU were 2.32% per hour without any usage.
W/O SetCPU were 3.18% per hour without any usage.
or approximately 7% maximum saving per day time. (for me)
My SetCPU only effected sleep state.
Not a big deal but still significant different, but it could survive for whole day anyhow.
I'm more interested about Killing app. I might try after this as I see many argument about it.
Click to expand...
Click to collapse
Ohh figures, good stuff! Always better to have some numbers to work with.
Do you not find that for a few seconds after waking up the phone gets choppy?
I would definitely be interested in seeing the stats with a task killer
Do you guys leave internet/gps on or something? I get 3 hours/percent on idle.
JamesBarnes said:
Ohh figures, good stuff! Always better to have some numbers to work with.
Do you not find that for a few seconds after waking up the phone gets choppy?
I would definitely be interested in seeing the stats with a task killer
Click to expand...
Click to collapse
Yup, with SetCPU for sleep state, it was 'choppy' for a few sec, mostly effect lock screen and screen switching.
I've seen lots of threads about what SBC does, why it's bad, yadda yadda... but the point of this one isn't about that. I understand what it is and I understand the risks, and I'd like some input from people that have still been using them.
The first time I used a nightly of CM7 I flashed a SZ kernel not knowing it was SBC. I was blown away at the battery life I was getting. Some fellow Android enthusiast coworkers were convinced that something was 'wrong' with my phone when it took about an hour to drop from 100% to 99% -- and after about 16 hours I was over 60% still. It wasn't until later on that I stumbled upon some "SBC is bad, mmkay" posts/threads and horror stories of melting batteries and ruined phones. I immediately stopped using the SBC kernel.
The only issue that I ran into was that apps would occasionally seem to "time out" -- including system stuff. For example I'd try going to "Settings" and the screen would just dim like it was about to load or change over, and nothing would happen. Or I'd open Wordfeud and it would just be a black screen, like it didn't want to load. Typically I had to force stop it and reload it, then it'd work. That drove me insane. I don't know if it was related to the SBC, might have just been the kernel vs the ROM. Any input about that is appreciated.
Anyway... who has been using SBC kernels without any issues? It seems to me like if you're just smart about it (i.e. not leaving the phone charging all day long) then you shouldn't have issues (even though of course the risk is still there). I'd imagine there's quite a few XDA'ers that use SBC kernels because of the incredible battery life. You're the ones that I want to hear from.
Ill throw my opinion on this one...
Ive been using them since day one...never once had an issue. I beat the hell out of my phone and get great battery life with the stock battery. Ive tested different setups & combos of background data syncing...to this day I have not found any negative effects on my phone/battery. I leave it on the charger for about 8 hours per night when I sleep...if I dont stream music for 8 hours straight, I get about 8-11 hours of life out of my phone before needing to charge.
Here is my current battery usage on a SBC kernel. Currently at 82%
{
"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"
}
I'm using savaged Zen on CM7 SBC and charge for 8 or so hours while I sleep. It reaches a full charge after 2 of those hours so the rest of the time it is just trickling. That is the only time I charge it and have never had an issue with SBC.
I've been using sbc kernels since the beginning. Never had an issue. I have the Sprint extended battery and get 2 days battery life with moderate usage. I play games, text, phone, internet and surf the market quite a bit. Right now my phone has been off the charger for 16 hours and I still have 60% battery left. It was sitting idle in my locker at work for 8 hours but other than that it has been pretty steady usage.
Sent from my PC36100 using XDA Premium App
First of all I'll say that I was a part of the people that believed that the SBC kernels should have a warning disclaimer back when that was going on.
Now that is out of the way...
I had received an extra brand new battery with my replaced Evo.
So I decided to start using the SBC kernel's because I figured that if the battery went...who cares... I have a brand new replacement.
I will stop now and say that I've done the HTC calibration talked about here:
http://forum.xda-developers.com/showthread.php?t=712990
I was using the SBC kernel for a good few months and although the battery life was better it started declining.
I, of course, re-calibrated the battery but that seems to not help either.
So, did the battery's life fail due to the SBC kernel?
Don't know.
Not going to make that claim.
Just chiming in.
Using a 3000 mAh I get a good 16 Hrs using the SBC more aggressive blah blah blah, and I am always on my phone streaming radio, web and texting.
mattykinsx said:
First of all I'll say that I was a part of the people that believed that the SBC kernels should have a warning disclaimer back when that was going on.
Now that is out of the way...
I had received an extra brand new battery with my replaced Evo.
So I decided to start using the SBC kernel's because I figured that if the battery went...who cares... I have a brand new replacement.
I will stop now and say that I've done the HTC calibration talked about here:
http://forum.xda-developers.com/showthread.php?t=712990
I was using the SBC kernel for a good few months and although the battery life was better it started declining.
I, of course, re-calibrated the battery but that seems to not help either.
So, did the battery's life fail due to the SBC kernel?
Don't know.
Not going to make that claim.
Just chiming in.
Click to expand...
Click to collapse
What battery doesnt start to decline?
No problems here.
aimbdd said:
Lucky you. What battery doesnt start to decline?
Click to expand...
Click to collapse
Of course but I'm talking about 10 to 12 hours and now 6 to 8...
Lol... another one of these?! I get a bazillion hours of battery life when my phone just stands there and does basically nothing too. Who doesn't? Get out of your caves people and call someone. I want to see those batteries then.
akarol said:
Get out of your caves people and call someone. I want to see those batteries then.
Click to expand...
Click to collapse
Huh?????
Cat
hes saying anyones phone can last a long time while not being used, this thread needs to go away
I think what he means is, what kind of battery life do you get when using your phone hard? I have tried SBC and Non-sbc, but have not really noticed any difference. I am either surfing the web or playing games CONSTANTLY on my phone during the day, due to the nature of my job. I literally log 6+ continuous hours of surfing per day and, for me, the sbc kernels do not make an appreciable difference. This is not meant as a criticism, it is simply an observation of real-world results on my phone. I get up at 4:30 every morning. Phone comes off charger at 4:50 every morning. By 10am, I am plugging my phone in, cause I am down to 15%...maybe 15 minutes earlier, maybe 15 minutes later, but right around 10am. The kernel I use makes no difference with this. With that said, the kernel I use makes a BIG difference in my ENJOYMENT of that time. My phone has been really happy with anything other than stock. SZ is a close second, but none are as good as htc 15 for me (specifically at issue are screen-tearing in webpages, and smoothness of scrolling. When I was trying out netarchy, I had constant fc's of the browser and had to stop. I am sure the problem is in my phone, but that doesn't make it any more usable. None of the king kernels work well for me, causing tones of fc's and random reboots). I am currently living with stock cm cause it is stable, and I am feeling too lazy to flash a kernel just for some screen-tearing. I know. Pathetically lazy.
iitreatedii said:
hes saying anyones phone can last a long time while not being used, this thread needs to go away
Click to expand...
Click to collapse
And if I turn my phone off I use practically no battery...?
At any rate, a comment like "this thread needs to go away" is EXACTLY why threads about this subject usually explode.
No one here has said anything ridiculous, just trying to discuss.
You're welcome to NOT be apart of a thread if you don't like it.
Go beg for thanks elsewhere.
tejasrichard said:
I think what he means is, what kind of battery life do you get when using your phone hard? I have tried SBC and Non-sbc, but have not really noticed any difference. I am either surfing the web or playing games CONSTANTLY on my phone during the day, due to the nature of my job. I literally log 6+ continuous hours of surfing per day and, for me, the sbc kernels do not make an appreciable difference. This is not meant as a criticism, it is simply an observation of real-world results on my phone. I get up at 4:30 every morning. Phone comes off charger at 4:50 every morning. By 10am, I am plugging my phone in, cause I am down to 15%...maybe 15 minutes earlier, maybe 15 minutes later, but right around 10am. The kernel I use makes no difference with this. With that said, the kernel I use makes a BIG difference in my ENJOYMENT of that time. My phone has been really happy with anything other than stock. SZ is a close second, but none are as good as htc 15 for me (specifically at issue are screen-tearing in webpages, and smoothness of scrolling. When I was trying out netarchy, I had constant fc's of the browser and had to stop. I am sure the problem is in my phone, but that doesn't make it any more usable. None of the king kernels work well for me, causing tones of fc's and random reboots). I am currently living with stock cm cause it is stable, and I am feeling too lazy to flash a kernel just for some screen-tearing. I know. Pathetically lazy.
Click to expand...
Click to collapse
All I'm saying is the overall capacity of the battery declined, and quicker than it should, after using the kernel.
I'm not saying that the kernel caused it.
All I'm saying is, that's what happened.
iitreatedii said:
this thread needs to go away
Click to expand...
Click to collapse
Or just you.
The purpose of this thread was to talk to people that have been using SBC kernals and haven't had issues.
I guess I'm not surprised at some of the dumbass comments that have been made. I don't even know why I wasted my time trying to start a discussion.
ive been using sbc kernels since the beginning too, other than the major glitch with them (fix is to not have plugged in while rebooting, or unplug then replug to reset charging) I am very satisfied and thank FSM that ms79723 made sbc for us
my stock battery still feels like its new, I don't notice any inconsistant drain patterns
I use my phone heavy, i can drain my stock battery in 4hrs and my chinese fake 3500 in 7hrs. constant surfing, downloading, texting, talking and tethering. I do it daily not rarely, my nand memory should be failing by now and I'm surprised my batteries have survived this long due to abuse nonsbc related.
the longest my phone went without a sbc kernel was an hour while testing cm stock kernel and I refuse to flash a non sbc kernel.
I will make it known when my battery dies from sbc, so far so good, knocks on wood
mattykinsx said:
And if I turn my phone off I use practically no battery...?
At any rate, a comment like "this thread needs to go away" is EXACTLY why threads about this subject usually explode.
No one here has said anything ridiculous, just trying to discuss.
You're welcome to NOT be apart of a thread if you don't like it.
Go beg for thanks elsewhere.
All I'm saying is the overall capacity of the battery declined, and quicker than it should, after using the kernel.
I'm not saying that the kernel caused it.
All I'm saying is, that's what happened.
Click to expand...
Click to collapse
I got that. Other than the first sentence, explaining what I took his comment to mean, my comment had nothing to do with yours.
lmao yeah about that, ill always be here, we dont need ANOTHER thread about the same thing over and over again, maybe ill go in the q and a and ask how to unroot, yeah ill go do that
iitreatedii said:
lmao yeah about that, ill always be here, we dont need ANOTHER thread about the same thing over and over again, maybe ill go in the q and a and ask how to unroot, yeah ill go do that
Click to expand...
Click to collapse
Well thank you Steve Jobs for telling us what we need.
I've been using them for a few months and didn't realize I used them incorrectly until a week ago. I normally got great battery life but I found out that I had to let it charge overnight. I never left my phone overnight while charging so I guess I didn't push the kernels to the max. What I would do is just let it charge past 100% for like an hour and then take it off. I only thought people with 3500 batteries should leave it overnight and boy was I wrong. Other day I left my phone overnight for the FIRST time and I really saw the difference; it's funny because the way I know it was working is the battery monitor widget was showing 12-14mA's all night(finally witnessed trickle charging). Man was I amazed lol. Sorry for the long cluttered rant I'm on my phone so I'm trying to keep this short.
~ d3rk
So I've played a bit of Sherlock Holmes over the last 2 days trying to monitor the AOS bug and how exactly it affects everybody.
First of all let's start with a graph:
{
"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"
}
First of all we can divide the whole time-line in 3 parts:
T1) From beginning to the second bar of phone usage
T2) From T1 to the infliction point
T3) From T2 to the end
In T1 I had the phone as such as I always had it for several days and nothing special to report there, AOS was taking up up to 3h of CPU time during that 9h period.
Between T1 and T2, I upgraded ROM from Cognition 1.20 to 1.30, and left home (You can see where Wifi is not on) and got back several hours later. Now this is the most important part as what I've noticed over times and times again, the AOS bug doesn't come up when there is no Wifi or Internet connectivity, fine and dandy as long as I'm not home (I also had no 3G for that period), as expected. AOS gains just 1-2 max. minutes per hour in terms of CPU time. At the middle of T2 I get back home, turn on Wifi and so on.
Now what blows me away is that AOS continues to just use little CPU time for about 7 hours at which I'm home. Everything works fine, I have not changed anything to grant any difference in usage.
Now sometime in the night I use check on the battery again, as I've done over time the whole day to keep an eye on the usage, and this time, AOS goes nuts as you can see in the drop in battery level after that "infliction" point. AOS was at a little over 4 hours and something at that point, and one hour later it was basically at 5 hours. I said **** it and went to bed.
After waking up and noticing my battery level dropped about 15%, I checked up on AOS and what do you know, it's at 7-8h CPU time now.
In the morning I chatted for a bit and some light browsing, I let it plugged in for a bit and that was it. At the end of the graph AOS is at 9 hours of CPU time.
To the point:
The Android OS drain is real and kicking, and it makes no sense what so ever. There is no correlation to the usage of the phone. I found no correlation to the applications I'm using. Apparently there's not even a correlation to if you have Wifi on or not, since it worked fine for me for a while.
And its effect on battery usage is also pretty much real: As you can see I marked the average drain curves over the 3 periods and you can see clearly the similarity in usage between when the AOS bug is alive and when not, a 26° curve vs. a 16° curve. So what it means that flat-line idle usage is increased 40% by this one bug only. [And before anybody tries to reply on the degree of the curves, it's only relative to my usage in the screen-shot and irrelevant for anybody else.]
I even plotted a curve over the whole time too see what it would have been if AOS usage were to be sane. Result: At the end I'd be somewhere around 60-55% instead of the 25% I am now. Of course what I did is not accurate at all but even if I'm as much as 10% off it's still a huge difference and you can see the point.
Some remaining remarks:
People say it does not matter that if your phone is idling or not being much in use, having a high AOS % is normal since it needs to sum up to 100% and that's why it happens. Get your head out of your asses and think for a moment. Firstly, of course does AOS % go down when you're heavily using the phone, because when you're actually using the phone you're using more power than AOS would ever be capable of draining when it's in Deep Sleep. Secondly, when idle and in Deep Sleep, nothing other than Phone Idle, Cell Standby, Wifi, and Android System (Under which everything that runs in the background is packed) should be using anything. A percentage is calculated from absolute values, and when it's high, its not for nothing.
As for what I'm actually running on the phone: Nothing other than Skype and Trillian, and I've already checked that those have no effect on AOS usage at all. I have no widgets other than the clock in the lock-screen. I removed all of the Samsung apps and most of the services. I have no push email or anything related running. I disabled all syncing. If I would go even more bare than now I'd be losing usability. I've tested this with a dozen different Kernels and ROMs and it's not related to any of those. (SpeedMod Kernel makes AOS not appear anymore because I believe it disables the monitoring capability of the system to actually record the usage, battery life does not change, but I've yet to do a extended test so don't take my word on it)
Well that's all for it now. I just wanted to do this rant since I felt like throwing the phone against the wall last night when it suddenly ate up 5% battery inside of an hour. So annoying when everything else in the phone is perfect.
First, that's a fantastic bit of predictive analysis you worked up. I'm guessing you do a lot of number crunching in your day job.
I posted the following in another battery life thread. I'll post it here too. Do you disagree with my theory about the lack of a common denominator pretty much guaranteeing there will be no common solution?
Consider this:
1) Every phone leaves the factory configured exactly the same way.
2) People connect to different carriers ranging from large/advanced to small/outdated.
3) People use different routers to connect to Wi-Fi and spend varying amounts of time connected.
4) People use stock ROM's and cooked ROM's
5) Some people use CPU tools, memory managers, task killers, battery monitors, and some don't.
6) People use different e-mail clients, e-mail providers, different sync settings and send/receive different volumes of e-mail.
7) People use social apps differently with different sync settings.
8) No two phones have the exact same set of apps loaded on them.
9) People use their phones differently with different amounts of talk time, display time-on, CPU usage, and downloading time.
10) People use different SD cards.
Now, with all of that said, you tell me how any discussion on this forum is going to come up with a single "Holy Grail" solution to better battery life? If there's no common problem how on earth can there be a common solution? If everyone on the forum was getting ****ty battery life I'd say there's a chance of a common issue. That's not the case. And the never ending circuitous conversations about battery life that take place are inane because there is no common base to build a meaningful discussion on.
Funny my AOS never had to go greater than 10%, checked with my neighbour too. we got the same phone on the same day.
BarryH_GEG said:
First, that's a fantastic bit of predictive analysis you worked up. I'm guessing you do a lot of number crunching in your day job.
I posted the following in another battery life thread. I'll post it here too. Do you disagree with my theory about the lack of a common denominator pretty much guaranteeing there will be no common solution?
..snip..
Now, with all of that said, you tell me how any discussion on this forum is going to come up with a single "Holy Grail" solution to better battery life? If there's no common problem how on earth can there be a common solution? If everyone on the forum was getting ****ty battery life I'd say there's a chance of a common issue. That's not the case. And the never ending circuitous conversations about battery life that take place are inane because there is no common base to build a meaningful discussion on.
Click to expand...
Click to collapse
Well I don't know the context of that post you wrote but you're diversifying the problem too much if you bring up all those points. My point and this thread is about the lone AOS eating up battery life and having such an impact. That's why I had almost nothing else running on the phone as to try to isolate it as much as possible and actually bringing up the common denominator.
For me half of those points don't even matter, and at the end of the day the most-common denominator is a) Gingerbread b) Samsung drivers. I'm pretty new to the Android ecosystem as I didn't have any before my SGS2, so I don't know that much about other phones but one buddy of mine has a Desire HD and has the same problem with high AOS usage, so that logically would mean it's a Gingerbread issue. I have not heard of it on anything running Froyo or earlier.
Fact is people who post on those threads about battery life and having AOS showing up at such a high percentage, yet accept it and even say it has amazing battery life are disillusioned as it could be even much better if this one thing alone were to disappear and go away. Anything else using up battery in your list is what I would call actual usage of battery life, as all those things listed have some kind of measurable effect in usability and bring something to the table, as opposed to this, and that's why we call it drain or waste of battery.
vaust said:
Funny my AOS never had to go greater than 10%, checked with my neighbour too. we got the same phone on the same day.
Click to expand...
Click to collapse
Exactly people like you is what blow my mind. What I've noticed that when not using Wifi or 3G (And after my testing I'm not so sure about 3G anymore) the AOS usage is very low, so maybe you're falling into that category of people?
Thanks to the first 2 posters for their analysis in particular the OP,i think most people who on here who have a GS2 share your frustration, i have noticed that the leaked 2.3.4 update which was said to solve the AOS problem has failed to do so, well not exactly the AOS has gone down slightly but is certainly still a big issue for lots of people.
Like the OP ive tried to do some tests and try out various things but im still as much in the dark about what really causes this excessive battery drain,i too run Cognition ROM but it appears every ROM whether it be stock or custom suffers from this AOS drainage, ive not come across many who haven't experienced some sort of excessive drain with AOS.
I am going to look into this Kernel that the OP mentioned and give it a go, nothing to lose, wasn't there a big thread on this forum relating to AOS too, hopefully someone will come up with a viable solution sooner rather than later so we can all have better battery life on our GS2.
vaust said:
Funny my AOS never had to go greater than 10%, checked with my neighbour too. we got the same phone on the same day.
Click to expand...
Click to collapse
same here mine is 4%, 12m OS time out of 10hrs battery
AndreiLux said:
Exactly people like you is what blow my mind. What I've noticed that when not using Wifi or 3G (And after my testing I'm not so sure about 3G anymore) the AOS usage is very low, so maybe you're falling into that category of people?
Click to expand...
Click to collapse
I'm another one of them, although I think in my case it may be because my usage of the phone is so high the Android OS is mostly hidden under the overwhelming weight of Display
Logi_Ca1 said:
I'm another one of them, although I think in my case it may be because my usage of the phone is so high the Android OS is mostly hidden under the overwhelming weight of Display
Click to expand...
Click to collapse
That's why we need to stop using % to compare it and actually share the CPU runtime of the package, so in that way we can actually compare apples to apples. And it would be helpful to know how you've been using your connectivity in relation to that, as again, I repeat myself, it doesn't seem to happen when not connected to anything.
Thank you for the anaylsis. My findings mirror your own. Android OS bug runs rampant on wifi. However, on 3G or HSDPA, it inflicts much less damage, so I keep the phone on 3G or nodata mode unless I want to download something big.
What's sad is, I have tried every kernel, every ROM here, including truly alternative things like Cyanogen nightlies. This bug is always there. So I think it lies in Samsung's drivers package, which is common on every kernel. Until Samsung rewrites the drivers, especially the WiFi driver, we'll never get rid of this.
Disgrace
The fact is AOS bug is there, all time, sometime it's very prominent and sometimes not, doesn't really matter if there is any connectivity or not. Versatile bug to a versatile OS I guess. Don't like it.
Regards.
This bug is getting really frustrating so I wouldn't mind ranting a bit about it.
This is my battery stats yesterday and the only thing I did was a couple of minutes of web browsing. (I'm using stock GB 2.3.3 KE7)
Not sure what to make of mine, i cant really tell if i have the bug or not
rocketpaul said:
http://i224.photobucket.com/albums/dd67/rocketpaul/SC20110726-191715.png
http://i224.photobucket.com/albums/dd67/rocketpaul/SC20110726-201005.png
http://i224.photobucket.com/albums/dd67/rocketpaul/SC20110726-201012.png
Not sure what to make of mine, i cant really tell if i have the bug or not
Click to expand...
Click to collapse
You don't. 12m over 10h30 and with Wifi on all the time is excellent...
Can you please share what you did to your ROM / versions and what settings you are using?
AndreiLux said:
You don't. 12m over 10h30 and with Wifi on all the time is excellent...
Can you please share what you did to your ROM / versions and what settings you are using?
Click to expand...
Click to collapse
Villain 2.1 (kg2 base), Ninphetamine-2.0.1 kernel, kg3 modem.
Well, from my testing Android OS bug is most likely related to wi-fi, at least on my phone. The whole story is this. Used my phone for about 3 weeks without ever connecting to a wi-fi network. Everything was fine Android OS never showed more than 7 % up to 10 %, phone being idle or in constant usage. Connected to the same wi-fi network for about 2 weeks Android OS stayed the same, nothing unusual. Finally arrived to my home place and connected my phone to my personal wi-fi router and fun began, Android OS started reaching even 50 % while being idle and up to 25 % when using the phone. So in my opinion it must be related to routers' brand/class. I gotta mention i had the same apps installed in my phone for the whole time, stock android 2.3.3, no root. That's my story. Believe it or not , it's up to you. It might be related to tons of other things, but that's my personal experience.
Sp1tfire said:
Well, from my testing Android OS bug is most likely related to wi-fi, at least on my phone. The whole story is this. Used my phone for about 3 weeks without ever connecting to a wi-fi network. Everything was fine Android OS never showed more than 7 % up to 10 %, phone being idle or in constant usage. Connected to the same wi-fi network for about 2 weeks Android OS stayed the same, nothing unusual. Finally arrived to my home place and connected my phone to my personal wi-fi router and fun began, Android OS started reaching even 50 % while being idle and up to 25 % when using the phone. So in my opinion it must be related to routers' brand/class. I gotta mention i had the same apps installed in my phone for the whole time, stock android 2.3.3, no root. That's my story. Believe it or not , it's up to you. It might be related to tons of other things, but that's my personal experience.
Click to expand...
Click to collapse
I just tried this via tethering my router via my laptop and using that as the access point via Connectify. Didn't change anything.
AndreiLux said:
I just tried this via tethering my router via my laptop and using that as the access point via Connectify. Didn't change anything.
Click to expand...
Click to collapse
Wish i knew what kind of router was used in the wi-fi connection that i connected to first time. Obviously Android OS went nuts after connecting to my personal router. Will try and see how the phone runs when i connect to the router at my office, cause it's a different brand. The only difference i can think of is on the first wi-fi network i was connecting 3-4 hours a day, while at home i'm always connected to my router, 12 hours a day average. Wonder if Android OS would decrease % if i use wi-fi connection less.
Even when it is the router - it could be fixed.
http://forum.xda-developers.com/showpost.php?p=15968355&postcount=1286
Sent from my GT-I9100 using Tapatalk
Great study. I would like to add that the Android OS process could be including anything non-app related. So if you have the market doing a background check to see if the apps are updated, then that could be showing under Android OS since the actual market app itself is not running. Same goes for your mail apps etc. I suspect that as long as there is background sync or notifications happening without the app in question running, then Android OS goes up.
Here is mine from last night before bed until now (10:19am). Running stock KG3 2.3.4 with CF-Root KG3 kernel. Don't mind the battery spikes and drops, I just cleared the battery stats last night.
Here's mine.
It was used heavily from 1 am to 3 am, with Dolphin HD and music playback. Then I was asleep from 3 am to 11 am, with the app "Sleep like a droid" on. It's an app that monitors your movement using the accelerometer to determine what phase of sleep you are in and thus the best time for the alarm to sound.
Wi-fi is on all the way.
Not sure if I suffer from the bug. AOS usage is little over 12%, although CPU time itself seems to be low.
ROM: Lite'ning 4.1
Kernel: Ninphetamine-2.0.2
Hope this helps!
Our smartphones have the highest battery capacity a smartphone has ever had (not including Galaxy Note which isn't really a smartphone anyway).
Unfortunately, people get mixed results with the battery.
In this thread, post your battery life results and personal usage. It could help people see the potential our battery actually has and could also help stop battery woes.
It will also be interesting to see the results from different ROM's and different kernels.
Here's what you post:
- Display time
- That battery graph thingy
- Battery mA statistics (install this app).
Posting screenshots of the above would be MUCH more helpful than just saying, 'Oh, my phone lasts 2 days with heavy usage.' Heavy usage is variable for each individual, so being specific would be much better.
Please also post your personal configurations, ie. brightness at x%, 3G on, Wi-Fi on xminutes, 'Tasker' profiles etc.
Hopefully, if people participate, we will be able to identify how people get great battery life and how some people get really bad battery life. Then we could compare personal configurations and see what settings/apps/tweaks affect battery - in a positive or negative way.
This should also clean the forums of the daily 'bad battery life' thread's in the forums.
I will keep some posts reserved for the future, where there could be battery tips as well as the highest display time and the lowest mA statistics.
Good luck!
Reserved for future use.
Reserved another just in case.
Reserved this to increase my post count
This is just a suggestion for future reference. It would probably be best to keep stats/results/tips separated by either "CM-based" or "Blur-based" ROMs.
I haven't turned on BMW yet so I will update this post once I get results.
live4nyy said:
This is just a suggestion for future reference. It would probably be best to keep stats/results/tips separated by either "CM-based" or "Blur-based" ROMs.
I haven't turned on BMW yet so I will update this post once I get results.
Click to expand...
Click to collapse
Good idea, I'll do that once this thread starts to develop a bit.
Well my battery hasn't been normal ever since I flashed but
Rom-Neutrino 2.2 (GT-S ADDON)
Kernal-Faux123's 024 1.3ghz
Brightness-always at minimum
3g-most of the time when I'm not home
Tasker-you see that little green guy in the top left...
WiFi-its on all day when I'm home (no data plan)
Btw the link to the mA stats didn't work.
{
"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"
}
Sent from my Neutrino'd out Atrix @ 1.3Ghz.
Battery life will vary by individual device hardware performance, individual battery performance, ROM, radio, kernel, apps installed and running/not running, how many times you reboot, how much data you use, wifi usage, bluetooth usage, etc., etc.
There is no way to compare everything which is a factor because there are too many factors. Every device is basically completely custom unless you take 2 or more completely identical stock devices and do some battery studies on those without changing anything. Even then you won't capture the differences in actual performance differences from hardware and battery performance which will vary across all the sample devices.
The best you are going to get is people just saying which ROM, radio, and kernel they use, and the up-time they get. In reality, this will be no different to any other battery life reporting done in many other threads. Comparing apples to oranges to pears. Better to just start a "who has the longest battery life" thread.
I believe this is more of an attempt for users to "compare notes", so to speak. It might help people understand why they are getting the battery life they are and maybe there might be people who can collaborate on which setups will meet their needs and obtain the type of battery life they want. At the very least, it could give users (with similar configurations) a place to see if they are actually experiencing any issues or if it is the norm with said configuration.
Also, this could be a step in consolidating a frequently discussed issue and in return reduce the number of new posts on the same subject.
CaelanT said:
Battery life will vary by individual device hardware performance, individual battery performance, ROM, radio, kernel, apps installed and running/not running, how many times you reboot, how much data you use, wifi usage, bluetooth usage, etc., etc.
There is no way to compare everything which is a factor because there are too many factors. Every device is basically completely custom unless you take 2 or more completely identical stock devices and do some battery studies on those without changing anything. Even then you won't capture the differences in actual performance differences from hardware and battery performance which will vary across all the sample devices.
The best you are going to get is people just saying which ROM, radio, and kernel they use, and the up-time they get. In reality, this will be no different to any other battery life reporting done in many other threads. Comparing apples to oranges to pears. Better to just start a "who has the longest battery life" thread.
Click to expand...
Click to collapse
I came from a Galaxy S (since in my country there are issues with Galaxy S2 signal), Atrix is really nice (this is my 2nd day on it), but about battery, the same rom but different kernel always do different results, last one on galaxy S gave me 2 days on battery with low to med use, but in Atrix world, in the few post I have read, I just noted that Atrix arent the same, looks like there are 3 versions of it (sorry if i am wrong, I am new into Atrix) ATT seems to be one and the 2 others tegrapart versions, do you think this also could make difference on the batt duration?
CaelanT said:
Battery life will vary by individual device hardware performance, individual battery performance, ROM, radio, kernel, apps installed and running/not running, how many times you reboot, how much data you use, wifi usage, bluetooth usage, etc., etc.
There is no way to compare everything which is a factor because there are too many factors. Every device is basically completely custom unless you take 2 or more completely identical stock devices and do some battery studies on those without changing anything. Even then you won't capture the differences in actual performance differences from hardware and battery performance which will vary across all the sample devices.
The best you are going to get is people just saying which ROM, radio, and kernel they use, and the up-time they get. In reality, this will be no different to any other battery life reporting done in many other threads. Comparing apples to oranges to pears. Better to just start a "who has the longest battery life" thread.
Click to expand...
Click to collapse
Yes every phone is different, but the battery's are exactly the same...
The fact that the hardware is a tiny bit different on each device will make negligible difference on battery life.
What will make the difference are personal preferences. This is why I'm requesting people to post their own one so that we could all get tips on how to decrease battery drain.
Anyways, let's kickstart things off. Here's mine - I'm losing 1%/hour on idle, with 3G on, brightness on auto and autosync on.
I only downloaded BMW yesterday, so I don't really know how it works. But something I noticed was that the mA keeps decreasing. Why?
And another thing, is the screenshot attached what you would refer to as 'good battery life?' I'm not complaining, but I'd like to see what mA people are normally getting while idling as well.
EDIT: Oh, and just in case... I'm running (custom) Neutrino GT ROM with Faux123's 024 1.3Ghz kernel.
I'm a new user to Motorola Atrix, only got it for a week. The first two charges were good (still had the stock rom-no root yet) afterwards I installed neutrino 2.2 and battery doesn't last long. My previous HTC Desire lasted idling for 14 hours and more at the same settings: HSDPA only with data, bluetooth on paired with bt headset and several apps with push notifications.
These are today's results:
Seems hopeless!
i flashed a cm7 image. i had a battery issue. i drained it, plugged it in, charged it to 100% per batterycalibration, and have had excellent battery life.
tia,
rotty022
rotty022 said:
i flashed a cm7 image. i had a battery issue. i drained it, plugged it in, charged it to 100% per batterycalibration, and have had excellent battery life.
tia,
rotty022
Click to expand...
Click to collapse
same here, under regular conditions (normal phone use, a few phone calls, a ton of texts and probably about 5 hours a day of streaming audio) i'm usually around 30% when i go to bed each night, that's 16 hours on battery
this is on cm7.2 kang (most recent version)
my battery life was pretty terrible until i did the trick above
harisled said:
I'm a new user to Motorola Atrix, only got it for a week. The first two charges were good (still had the stock rom-no root yet) afterwards I installed neutrino 2.2 and battery doesn't last long. My previous HTC Desire lasted idling for 14 hours and more at the same settings: HSDPA only with data, bluetooth on paired with bt headset and several apps with push notifications.
These are today's results:
Seems hopeless!
Click to expand...
Click to collapse
This is the 'bluesleep' bug in my ROM.
It will be fixed in the next update.
For now, move the files in the attached .zip to /system/xbin and set permission to 777. It will considerably improve your battery life.
Using 2.2 WE from notorious, getting about 4hrs on average of screen time... Pretty aggressive uv as well as uc to 912mhz.
A lot of Web browsing for a mmorpg, texting roughly 10-20 a day, around an hr of phone calls, sometimes less, screen is set to auto, 2gmail accounts updating via push and weather updating every 2 hrs.
I don't know what else to say except a little earlier in Neutrino's post someone said freezing via tibu the following apps (Bluetooth share, truepoint something or other, as well as sensor navigation and atrix settings) since doing the above, as well as my other personal settings and usages I'm looking at 5 to 6 hours screen time today... Here is a couple of screen shots of what I go to so far.
Also, using 77.36 radio and gps USA mod from notorious and the v6 script.
Sent from my Neutrino'd (M)Atrix 3.5G
That was on ICS mod browsing reddit, playing n64 emulator on auto brightness 1GHZ. Then I switched to SUPEROSR and now only get about 2-3 hours of screen time
Notorious544d said:
This is the 'bluesleep' bug in my ROM.
It will be fixed in the next update.
For now, move the files in the attached .zip to /system/xbin and set permission to 777. It will considerably improve your battery life.
Click to expand...
Click to collapse
Thanks for the reply and the help, I did that and left it from 100% overnight and after ~5 hours i got 55% same consumption.. (after I moved and changed permissions, I rebooted)
I was getting horrible battery life (less than 10 hours of use) from the day I got my Atrix, purchased second hand. After installing watchdog lite, I found that the suspend process was continually draining my battery. I encountered this issue on every CM7 based or Blur based rom, and was not able to find any solutions.
After recently upgrading to Joker's ICS rom, this issue is gone, and now after 10 hours of use still have a 56% charge on the battery.
Not sure if anyone else is having issues with the 'suspend' bug, but joker's rom has been a Godsend, can actually use my phone for a whole day now.
Alright I got one for you guys.
I recently flashed Neutrino GT and had the battery show 96% as max. I preceded to recalibrate the battery and got it back to showing 100% again for a few charges. Now somehow its reverted back to maxing out at 96%. I haven't flashed anything since I recalibrated. Thoughts?
So I was posting some info in another thread but I figured I would make my own thread for it. It seems like the power consumption at idle might be the cause for the "not as good as expected" battery life. For example my G3 will sit off the charger for 4 hours without being used and still be at 100%, the Turbo loses 6% in that time. The G3 has a 3000mAH Battery and I could easily get 24h of off the charger time on the G3. My question is what is killing the battery on the Turbo??? Its kinda hard to look over the battery stats when there is no root. Anyone have any input?
I think it's because of the wifi. I too have experienced crazy idle drain compared to my G2 and it's really making me regret getting this phone. It seems like they just slapped the kitkat ROM together and didn't really care to test it very well because Lollipop is coming out so soon.
It's definitely draining at idle more than usual or should be, I agree. I don't think it is WiFi related though, or at least not enough to be the main problem. I could be wrong of course. I have also not experience any WiFi or Bluetooth issues whatsoever and I use a Moto 360 all day, every day.
I am currently on my 4th charge cycle since acquiring the 64GB BN model. It's been powered on for 7h 32m and I'm sitting at 78% with 1hr 18m SoT. That's with heavy usage and taking quite a bit of pictures & video during this mornings product demo presentations at work.
Hardly anything for me personally to complain about. I'm sure they will optimize it. I'm almost certain than Android L 5.0 will make this phone a true beast.
Time will tell.
are you leaving gps or high accuracy location settings on?
I have the same issue as the OP. My G3 lost very little battery life when idling. I've attempted shutting down email accounts, turning off location and selectively removing apps in hopes of determining the cause of the drain...without success. This could be a deal breaker if we don't get some type of root exploit soon.
Well this sucks. I was going to get the Turbo but now I'm going to wait and see what happens with this drain issue. Maybe 5.0 will fix it.
I have been using the same settings that I did on my G3, Auto brightness, Location OFF and Auto Sync. Glad I'm not the only one noticing it too, I think its all in the build of Kit Kat they put on this phone, hopefully L comes out soon.
timjp692 said:
So I was posting some info in another thread but I figured I would make my own thread for it. It seems like the power consumption at idle might be the cause for the "not as good as expected" battery life. For example my G3 will sit off the charger for 4 hours without being used and still be at 100%, the Turbo loses 6% in that time. The G3 has a 3000mAH Battery and I could easily get 24h of off the charger time on the G3. My question is what is killing the battery on the Turbo??? Its kinda hard to look over the battery stats when there is no root. Anyone have any input?
Click to expand...
Click to collapse
How about you start by posting screenshots of your battery stats from System...Battery
I don't have any issues whatsoever.
Well once I figure out how to do that I will post it, but in the mean time what phone were you coming from? A few people have agreed in this post that the battery life is worse @ idle then the G3 so its not just me.
Edited
{
"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"
}
timjp692 said:
Well once I figure out how to do that I will post it, but in the mean time what phone were you coming from? A few people have agreed in this post that the battery life is worse @ idle then the G3 so its not just me.
Click to expand...
Click to collapse
Well G3 could be out of box, not trying to argue wanted to understand what your problem was. If you press the graph you'll see more details on what is using batteries (awake vs screen on, cell signal etc) and more in Android System if you go into that screen.
Overall what your getting .. 1-2% is not a big deal to me and beauty of the massive battery is you don't have to worry about but if really wanted to you could improve by turning off stuff you don't need or even automating it.
FWIW I'm coming from a GS3 with a tiny battery but even that phone lasted 5 days idling with the right setting for my use case (cell radio off / WiFi on). With Turbo just disabled some apps I didn't need and don't even think about it any more. I do have complaints about the Turbo but battery is definitely not one of them.
I'm interested in this as well. I bought my turbo yesterday evening and it had a pretty good charge (>80%) out of the box. I played with it for much of the evening and copied ~8gb of data to the phone via wifi. When I went to bed battery was at 60%, when I woke up it was 46%. I noticed that my third biggest battery use is command center, so I disabled auto-location in that app. I'm hoping to have better results on my first full charge.
Yeah I agree, but its literally the same settings I ran of my G3. I think I'm just gonna return it between the weak wifi and cell signal, and the camera it's just not worth it if the battery life isn't better then my G3
I've been posting in the other battery life thread... but to summarize, I'm going to be doing some thorough testing over the next 24/48 hours (currently ongoing).
I have already noticed significant improvements in my battery life. Has mentioned in the other thread. I'll be making a detailed post on Friday evening with my results.
I may also, from time to time post some of my progress, as I already have an understanding as to one of the issues involved with the so called "idle drain" everyone is referring to, and it is NOT WiFi.
Keep your eyes on that thread here.
Thanks, I'm pretty good with understanding wake locks, I just don't know where to start without root since most the stats in BB require it. I'm intrested to see what you come up with. I'm gonna wait till Saturday anyway to see if I still want to trade this in for the nexus.
timjp692 said:
I'm gonna wait till Saturday anyway to see if I still want to trade this in for the nexus.
Click to expand...
Click to collapse
Is there a hard date for the nexus?
---------- Post added at 08:38 AM ---------- Previous post was at 08:35 AM ----------
Andromjb said:
I've been posting in the other battery life thread... but to summarize, I'm going to be doing some thorough testing over the next 24/48 hours (currently ongoing).
I have already noticed significant improvements in my battery life. Has mentioned in the other thread. I'll be making a detailed post on Friday evening with my results.
I may also, from time to time post some of my progress, as I already have an understanding as to one of the issues involved with the so called "idle drain" everyone is referring to.
Keep your eyes on that thread here.
Click to expand...
Click to collapse
Very interested in what you come up with, thanks!
timjp692 said:
Thanks, I'm pretty good with understanding wake locks, I just don't know where to start without root since most the stats in BB require it. I'm intrested to see what you come up with. I'm gonna wait till Saturday anyway to see if I still want to trade this in for the nexus.
Click to expand...
Click to collapse
Well you are limited with what you can do but I already gave you a start in my post, maybe you missed it. The only insight you will have without root (for tools like Better Battery Stats) is looking into all the info you can get out of Settings..Battery. There you can see wake locks vs screen on time and other stats like cell signal / wifi status etc. Then you can also dive into your biggest usage, for you it looks like it is Android System. They will list system services that are classified here. For example, you'll see the moto features are part of this. If you don't want to dig you can wait for Andromjb's updates
Overall I wouldn't base your decision to return the Turbo based on the battery -- base it on your other problems it sounds like you're having with wifi signal etc. That sounds like reason enough for a return. If you're ok with the larger size of the Nexus 6 then to me it's a no brainer to go with that instead of Droid Turbo since they are almost identical in terms of hardware.
For those that are getting battery drain, did you disable all of the verizon apps? There are some 20+ apps that are constantly running in the background and will drain your battery(even after i did a factory reset, these apps were sending data despite me never having opened them). Disable those, restart, then see if things change over the next cycle. I got 2d9hr31m and 4hr23 min of SOT(minimal usage) and was at 13%; this was on the first charge.
Could this drain be due to some of the sensors used for notifications. Doesn't the turbo have the feature where you stick your hand over it and it shows the notifications? If this is the case, wouldn't those sensors have to stay on?
Yeah I have 27 apps disabled and it really didn't make a difference for me like it has in the past, their must be something killing the battery on this 30m of screen time and I'm at 79% shouldn't be happening.
timjp692 said:
Yeah I have 27 apps disabled and it really didn't make a difference for me like it has in the past, their must be something killing the battery on this 30m of screen time and I'm at 79% shouldn't be happening.
Click to expand...
Click to collapse
Thats actually really interesting. I haven't been experiencing anything like that. Perhaps try doing a factory reset then disabling them again. That's the only thing I did differently. Perhaps it's just a bad device? I'm already at 2hrs screen time, heavy downloading(off line apps), and have been on battery for 1d8hr- still at 45%. Is there anything in the battery stats? Wake locks perhaps?