{
"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"
}
http://shayessays.com/2012/03/08/te...st-popular-roms-for-the-samsung-galaxy-nexus/
please leave a comment if you have anything to say!
Why not test all of them?
Nice...thanks. I take it you have the Verizon one? I prefer foxhound for battery.
Sent from my Galaxy Nexus
Some thoughts:
Given that the "Android OS" report in battery usage was apparently subject to a major, but simple, calculation bug until 4.0.4, I have doubts about its validity as a measure in this kind of test. Are all of these ROMs using the 4.0.3 code as base, or are some backporting pieces of 4.0.4? Furthermore, how would you know if any devs sticking to the 4.0.3 source haven't gone in and fixed the bug themselves once it became known? If I had to guess just by looking at this, Gummynex, Liquid, and Revolution have this bug patched, the others do not. The similarity within and between these two groups is just too striking.
Even putting that aside, I'm not sure I see the sense in measuring anything but total drain, assuming your methodology filters out any variance due to usage habits (screen on, apps running, signal strength). If the phone is left to sleep and nothing else is running, shouldn't all the drain show the nature of that ROM?
Also, perhaps you can elaborate more on why not keeping the time constant seemed like an okay concession, because when the total drain only varies by 1 or 2% over 6-7 hours, I'm not sure how almost a full hour's difference across tests can be considered insignificant.
For example, compare AOKP vs Redemption in your results, redemption ends up looking marginally better. AOKP reads 4% over 7 hours, or ~.57% per hour. Without actually crunching all the numbers, 20 minutes of variance looks like enough to be significantly signficant if all we get for sigfigs is 1% increments.
With all that in mind, my general impression is that most of these roms are roughly the same for battery. I don't know if there is a feasible option to either get a full mAh reading, or to have program log the exact time a certain % level is reached, but both would give much more valuable data, I think.
Also, one of my first thoughts after looking at this was what kernels are these roms all using? It would be nice to see it included; are the devs using the stock AOSP kernels, stock with a few of their own patches, bundling their favorite custom kernel, or even developing their ROM with a specific kernel in mind? I know that liquid is bundled with leankernel, for example. It begs questions: Is there a good kernel complimenting a well designed ROM? A great kernel making up for a crappy ROM? An extraordinary ROM that shines despite a buggy kernel? (All example for conjecture). Hard to say without kernel as a constant across tests.
To summarize, my main critiques of your methodology are:
-Don't see the merits of using Android OS drain vs the total drain.
-Would like to see a standard time used in tests, or if possible, measure the exact time required for x% of drain, or mAh remaining after x hours.
-Would like to see a larger test range to establish statistical significance.
-Would like to see kernel as a constant, since anyone can flash their own custom kernel, and packaging one in a ROM may be a good move, but doesn't say much about the rom itself.
Those are my thoughts on the methodology and the results presented, but I would also like to express that it's very refreshing to see someone actually going to lengths to compile thought-out data on battery life, instead of the dreaded "wow great battery life awesome ROM" posts that litter the ROM threads.
Edit: As far as a more precise reading goes, if you run better battery stats, Menu->More->History->Menu->View Serie gives quick access to a log that I think would be helpful here. I'm not sure what triggers the program to write to this log, but it's pretty well populated regardless. So you could decide you want to drain the battery to x%, and just read off the first time the log shows that level.
Related
Anyone know if battery life will improve at all with the new gingerbread update coming tomorrow? I'm just curious to see if they helped improve that at all, knowing that alot of people are currently running 2.3 already.
EggosEvo said:
Anyone know if battery life will improve at all with the new gingerbread update coming tomorrow? I'm just curious to see if they helped improve that at all, knowing that alot of people are currently running 2.3 already.
Click to expand...
Click to collapse
There probably won't be a big increase in battery life, but what this does mean is that there will be source for GB Sense kernels for the EVO. This is great because then kernel developers can start cooking better kernels that offer more battery savings.
I certainly hope so, but I wouldn't count on a major increase.
-viperboy- said:
There probably won't be a big increase in battery life, but what this does mean is that there will be source for GB Sense kernels for the EVO. This is great because then kernel developers can start cooking better kernels that offer more battery savings.
Click to expand...
Click to collapse
That is true my friend.
"oh ya"
{
"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 have an extended life battery on my EVO. It has always allowed me to use the EVO as much as I wanted as long as I charged it nightly. Since I installed Gingerbread, my phone will no longer make it all day. Gingerbread actually made my battery life much worse. I wish I had never installed it.
Well, every update I'm sure has some specific things that optimize the processes the phone runs and the task killers, so there's probably some minor improvements. I doubt you'll notice all that much though . If you're having issues with battery life hit up my sig lol
my moms evo had a problem with battery life. Some how it wasnt charging correctly. A battery pull for a few minutes fixed the issue.
Joey SR said:
my moms evo had a problem with battery life. Some how it wasnt charging correctly. A battery pull for a few minutes fixed the issue.
Click to expand...
Click to collapse
Had the same problem it would charge for some time but then stop charging..but its fine now
I've been running GB now for almost a week and I definitely have quite a bit worse batter life.
I installed a rooted gb rom last night and updated all the radios. Runs smoothly but my battery life has significantly gone down. Does anyone know if there is a known display issue with the update? See my screenshot of my battery stats.
Sent from my PC36100 using XDA Premium App
My display totally eats my battery on the new update. Very lame
We're comin from a pure power source.
Retraction to my previoius post in this thread
I found an email with a rather large attachment in my outbox that my phone was continually trying to send. When I deleted the email, my battery life returned to performance that was similar to the performance I had prior to the GB update. I believe the phone was continually trying to send the email and it was swamping my battery.
I know that one doesn't currently exist, but does anybody know if anyone's actually working on one? Given the age of the EVO 4G, I worry that developers no longer care enough to actually work on this, but it's something I desperately want. I haven't seen anybody talking about it in a while.
If nobody's working on one, I may start looking into how hard it'd be to develop my own (I have some comp-sci background, but being that it's limited, I know it'd be easier for someone else), or offer an incentive to some developers...
And before you say "AOSP!" I say "I love MikG!" I get fantastic battery life as it is, but it would be better if the battery was completely charged when I pull it off the charger. I'll switch to AOSP when ICS is stable on the EVO 4G (because we all know HTC is never going to push an ICS update for the EVO 4G, as sad as it is to say that).
MikG 2.60 w/Freedom kernel (less aggressive) and stock capacity battery:
{
"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"
}
(In a regular work day, I'll have 68% remaining after 10 hours, but that's because I have crappy reception in my office.)
Wouldn't get your hopes up man. SBC is really the main thing I wanted out of the GB sense kernel (along with HAVS and such) but none of the developers are really updating the kernels anymore. Lithid has done an amazing job with his Freedom kernel but he went to the iPhone I think and dropped development before implementing SBC.
I already get terrible battery life on Sense roms (due to a random bug causing extremely high display usage all the time that kills the battery, very frustrating) but maybe SBC will give me a few more hours enough to use it as a daily. Until them, I'm stuck using CM7 which I wasn't a big fan of before but after having to use it so long I have found ways to make it exactly how I want, along with giving me great battery life.
With ICS coming out, I doubt there'll be much more dev work on GB kernels
Swyped From The Hippest MIUI'd phone Using XDA Premium
HTC made the kernel not play nice with SBC the one SBC kernel that was out had lots of issues and was pulled. There was a code conflict in the core of the kernel source causing all kinds of failures with hardware, they went away after flashing a new kernel, but touch screen was whacked out audio bugged and there were lots of FC as the SBC code basically broke the kernel's functionality, so blame HTC not the devs it was like HTC intentionally built the kernel to block SBC. There are kernels out with AVS and I think one with HAVS but I'm not 100% sure on the HAVS since I've been working on AOSP the last few weeks and have taken a break from sense.
sent from my ics'd out EViL4G
Many valid points... thanks everyone for responding. I didn't realize that there were issues with HTC's kernel as it was (last I had heard, the newest GB kernel from HTC had a form of SBC built in, and after HTC released the code, it seemed as though nobody was working on the kernels anymore). I'll have to contemplate thoroughly on what to do... if the developers have looked into it, I doubt I'd be able to make progress where they were unable to do so.
ncfastls1, have you tried MikG at all? I know hardware varies, but it is without question the best performing Sense ROM I've had, in smoothness, functionality (Sense 2.1 + 3.0), and battery life. Using Freedom's more aggressively undervolting kernel gave me camera issues (phone would freeze and reboot), but as you can see from the pic in my first post, I've gotten some incredible battery life from MikG with the less aggressive kernel. I can also provide spreadsheets with my battery life every day that I've had it (I'm a statistician by profession, so I test everything I can collect data on just to make sure I'm getting the best performance from my phone). [Note: When I updated to 2.61, I simultaneously updated a bunch of apps, and my battery life fell off the Grand Canyon, so I restored to 2.60 and am trying to isolate the source of the drain by progressively updating apps before updating to 2.61.] CM7 is great - I have it on my Nook and am anxious to see CM9 - but I do have an affinity for Sense.
Thanks again, everyone!
P.S. I was also heartbroken to see that lithid went over to crApple. He had tried throwing together an SBC kernel (it's buried deep in his kernel thread), but since I didn't see a single person report about its functionality, I was reluctant to try it...
Lithid was working on it for a very long time. He has since gone to the iOS. Wish he wouldnt released his v 0.95 kernel though before he did.
I get 2+ days (max so far 3.5 days) with normal use and Tommy's classic paired with aggressive freedom.
Rxpert said:
I get 2+ days (max so far 3.5 days) with normal use and Tommy's classic paired with aggressive freedom.
Click to expand...
Click to collapse
Can you give more details on that, please? And, if possible, links to both.
Thanks
Hey All,
As per the N00B video, I'll try to keep this short.
So today was my first full day with the SGS3 (ATT). The battery life is ABYSMAL. I had it in airplane mode for about 8 hours (for reasons not important to the thread) and light usage (Facebook/internet) for 20 min. With another hour or so with all radios on and no usage. Add all that up, and I went from 100% to 1%. Unlike most others, my biggest usage was Android System....Not screen. I am un-rooted. I've downloaded no different apps then with my previous Android (OG ATRIX). I had/have Lightflow on both. That's the only thing I can think of that would cause this.
Any help is greatly appreciated. I downloaded BetterBattery, and will have it running after I charge up my phone.
And if this is discussed elsewhere, my bad. Maybe point me in the right direction?
Okay, it is my opinion, only having had my 474 for a little over a month that you have a rouge app.... delete lighrflow. After that, see how it goes.
I have been using the stock rom for the entire time (rooted the day i got it) and have tried 2 roms. Ive tried juiced defender and that didn't
really yield great results. I'm not considering using the stock ROM with kootz or whatever it's called kernel. Ive read that that combo
yields better results with regards to battery life.
I'll post in the next few days. Need to run it for thru 3 charges to see results.
Anyone else care to chime in??
I've run Ultimatum 1.3 and Kylan.... admittingly, not long enough to see if battery life improved....
Yes_Ima_N00B said:
Hey All,
As per the N00B video, I'll try to keep this short.
So today was my first full day with the SGS3 (ATT). The battery life is ABYSMAL. I had it in airplane mode for about 8 hours (for reasons not important to the thread) and light usage (Facebook/internet) for 20 min. With another hour or so with all radios on and no usage. Add all that up, and I went from 100% to 1%. Unlike most others, my biggest usage was Android System....Not screen. I am un-rooted. I've downloaded no different apps then with my previous Android (OG ATRIX). I had/have Lightflow on both. That's the only thing I can think of that would cause this.
Any help is greatly appreciated. I downloaded BetterBattery, and will have it running after I charge up my phone.
And if this is discussed elsewhere, my bad. Maybe point me in the right direction?
Click to expand...
Click to collapse
Use BetterBatteryStats and try to track down any wakelocks that are happening
Sent from my SAMSUNG-SGH-I747 using xda premium
As others mentioned, do the better battery stats and un install light flow. I believe that the developer acknowledged the battery drain for the S III.
{
"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"
}
Could be the gsiff-daemon bug. Try turning on Power Save and see if it helps. I normally get 15-17 hours per charge. That's with everything synching every 15 minutes, chrome browsing, Facebook checking, game playing, app downloading, and general reading.
Sent from my Marble White SAMSUNG SGH-I747 using xda-developers app
I noticed alot of people on the forums posting benchmarks after installing different ROM. I decided to download Quadrant just to see what I was pulling. I scored low in comparison to what I've seen, so I just completely wiped my phone back to stock (data wiped and then ODIN) and tried it, and pulled a 4678. Flashed CleanROM SE 1.2, and it went up to 4706. I've seen some people between 5k and 7k. A few videos I watched, people claiming to be completely stock were getting 5600+. Any clue what's wrong here? Is there anyone else out there that is stock that can benchmark and tell me what they get?
Thanks in Advance,
emoti0n
Read through the benchmark threads and you'll come to understand a few things:
- benchmarks are useless as an ongoing measurement. They merely show capability potential.
- your benchmarks will vary not only based on the rom and kernel, but what other apps you have running as services, what specific device configuration you have set at the time of running.
Does your phone perform amazingly doing what you want it to do? That's the only relevant and important measurement.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
spycedtx said:
Read through the benchmark threads and you'll come to understand a few things:
- benchmarks are useless as an ongoing measurement. They merely show capability potential.
- your benchmarks will vary not only based on the rom and kernel, but what other apps you have running as services, what specific device configuration you have set at the time of running.
Does your phone perform amazingly doing what you want it to do? That's the only relevant and important measurement.
-----
I would love to help you, but help yourself first: ask a better question
http://www.catb.org/~esr/faqs/smart-questions.html
Click to expand...
Click to collapse
Right. I understand what you're saying and that software environment can change the results, but two out-of-box state phones should score somewhat close to each other, yes or no? In comparison to what I've seen, my CPU is where I'm lacking. I also understand that I can OC and hit higher scores, but just comparing it to other phones that claim to out-of-box / stock - I'm scoring low in comparison.
Spy is probably right. But benchmarks should be somewhat similar
This is running DAGr8's AOKP Bullet build.
{
"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 GT-N7105 using Tapatalk 2
emoti0n said:
I noticed alot of people on the forums posting benchmarks after installing different ROM. I decided to download Quadrant just to see what I was pulling. I scored low in comparison to what I've seen, so I just completely wiped my phone back to stock (data wiped and then ODIN) and tried it, and pulled a 4678. Flashed CleanROM SE 1.2, and it went up to 4706. I've seen some people between 5k and 7k. A few videos I watched, people claiming to be completely stock were getting 5600+. Any clue what's wrong here? Is there anyone else out there that is stock that can benchmark and tell me what they get?
Thanks in Advance,
emoti0n
Click to expand...
Click to collapse
I've been following the saber kernal for a while and seen that some guys are running the saber kernel on clean rom OC'd. Not sure if that what your looking for but that would put you right up there along the 7k mark.
I don't try to squeeze out numbers on the quadrant thing but I have ran a few times just to see. I score right about 6900. Note 2, CleanRom 4.0.5 with the kernal from that rom and no other tweaks that I know of that would increase the score. I am not over clocked or anything. Seems fine to me
Sorry to bother you guys with that silly question. Total user error. I had power-saving mode on, and it didn't even occur to me. I pretty much turn it on first thing anytime I reset my phone, and do it without thinking anymore. However, after resetting back to pure stock one more time, without power-saving mode, I actually hit 7168. Basically, I was trying to see the difference myself of stock performance verses a different ROM / kernel. I would also like to see the battery life difference for myself.
Anyhow, thanks to everyone for their responses.
I've gotten some awesome battery life with AOKP mr1 build 6 and Lean kernel 6.3.1 lately. Just thought I would share incase anyone else is looking for awesome screen on time. This is with stock GSM gnex battery.
Also, anyone know why Google services is so high on the list. It never used to be a month ago and I don't do anything different. Anyone else's Google apps draining more lately?
{
"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 Galaxy Nexus
These kind of threads are discouraged. There are at least a couple dozen different combinations achievable and there is no reason for a thread for each. Just enjoy what you have.
Battery stats is always a relative statistic. You're just using less power from other areas.
Learn to search.
063_XOBX said:
These kind of threads are discouraged. There are at least a couple dozen different combinations achievable and there is no reason for a thread for each. Just enjoy what you have.
Battery stats is always a relative statistic. You're just using less power from other areas.
Learn to search.
Click to expand...
Click to collapse
Not sure why you feel the need to have a **** response when I am trying to share my findings with this rom/kernel combo. I have tried many different roms and kernels and haven't had battery life nearly this good and thought someone else might be interested too.
Learn to not be a ****.
Sent from my Galaxy Nexus
When I last visited XDA yesterday or the day before I was ranting about Android's battery life. This thread bragging about 3 hours screen on time is the perfect example! OP not trying to change the subject or take away from your battery pride, but.. This is a joke. The phone stayed on for three hours and this guy is so happy about it he started a new thread. Android has a BIG problem, or maybe the more accurate statement is the companies who manufacture Android devices do. Am I the only one who feels this way!? (growing more and more bitter about it each day that it goes ignored)
WiredPirate said:
When I last visited XDA yesterday or the day before I was ranting about Android's battery life. This thread bragging about 3 hours screen on time is the perfect example! OP not trying to change the subject or take away from your battery pride, but.. This is a joke. The phone stayed on for three hours and this guy is so happy about it he started a new thread. Android has a BIG problem, or maybe the more accurate statement is the companies who manufacture Android devices do. Am I the only one who feels this way!? (growing more and more bitter about it each day that it goes ignored)
Click to expand...
Click to collapse
Definitely one of my biggest gripes about Android is the battery life. I would really like to not charge my phone everyday. I don't like the bulk of extended battery and there seems to be no end in sight.
Sent from my Galaxy Nexus
I for one appreciate you reporting your battery life - probably didn't need its own thread (sharing the AOKP development thread would have been fine) but its good to give other users an idea of the kind of performance you're getting from your ROM/Kernel combo.
In regards to Android and battery life... Granted, its not like my Blackberry devices of 5 years ago, BUT, the devices are capable of much more. I charge my phone every night and sometimes even need a bump charge to make it through the day. Between my car charger and my office, I'm never in a pinch for some extra juice.
The way I look at it, if you want a car that puts out 500 horsepower, can't expect it to give you 40 MPG too.
Just my two cents.
gbarayah said:
The way I look at it, if you want a car that puts out 500 horsepower, can't expect it to give you 40 MPG too.
Just my two cents.
Click to expand...
Click to collapse
Sticking with the analogy.. The problem is most of the cars being manufactured, and all of the cars worth having, are 500 horsepower now. But very few offer a larger gas tank, which would not be hard to do.
We need batteries like that of galaxy note 2, which is 3100 mah in a slim form.
Cool story OP.
This mind of threads appear almost once a week. We all know battery life is not that good for GNex. To gain 30min more battery life by trying so hard simply is not worth it.
Get an extended battery, 6 hours screen on time, problem solved.
Sent from my Galaxy Nexus using xda app-developers app
OP since you live only 15 minutes or so away from me, and I am on Verizon, have you done any overclocking/underclocking? Undervolting? What apps are you using? Getting great screen on time can only get you so far depending on the apps you use.