• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

GNex Screen Power Consumption Study

MSUgEEk

Android Expert
For the past two weeks I have been conducting a pretty elementary study of the power consumption of the display on our GNexs. I will come back in this first post and lay out how I came up with these numbers and give some details on this experiment.

For those wanting numbers and graphs, skip to the second post.

For those wanting conclusions and tips, skip to the third post.

Conditions: I am running a Galaxy Nexus CDMA/LTE version with an extended 2100 mAh battery. I use my phone indoors the majority of the time, but do use it outdoors some, and did during this experiment. My phone is rooted, unlocked, and running AOKP Build 28. This was key in running this experiment as I will explain below in part two of the experiment.

For the first part of this experiment I set my screen brightness settings to manual at 100%. I used the battery stats collected by the system to calculate the screen usage isolated from all other battery usage of the phone and vice versa. I kept track of the phone isolated from the screen to make sure the readings were consistent and there was no duplicate battery stats in common with each other that would have affected the study. In the end, the phone consumption stats independent of the screen were very consistent, almost surprisingly so. You would expect the battery usage to vary a little due to difference in usage from day to day, and it did, but it wasn't very much. Numbers and graphs will illustrate that.

For the second part of the experiment, I utilized the ability to edit screen brightness levels, reset levels, light sensor filtering, etc contained in the build of AOKP I was running. I tweaked the brightness levels that corresponded with ambient indoor lighting levels to the absolute minimum and made the levels that corresponded with full sun outdoor lighting levels be max brightness. For the levels in between, I tweaked these to my satisfaction and am still tweaking them today. I wanted them to be at the absolute minimum that I could still easily read my phone. This took some time and effort, but worth it to me. Other than that, I repeated gathering readings like the first part.

If you want to know exactly how I took these readings, I'll be glad to discuss that later or come back and add it to this post with sample calculations and what not if necessary.

Not sure why, but inserting this table of the brightness settings forced a big gap in this post to appear on my screen, so I put it under the HIDE tag to keep things cleaner.

LowerUpperScreen
019910
20039920
40059925
60079930
80099940
1000124950
1250149960
1500199970
2000299980
3000399990
40005999100
60009999125
10000∞255

On to the results...(see post 2)
 
Screen at 100% Brightness
Battery consumed by screen: 11.20 mAh per minute
Battery consumed by phone: 1.87 mAh per minute
Optimized Auto Brightness
Battery consumed by screen: 7.92 mAh per minute
Battery consumed by phone: 1.95 mAh per minute

As you can see, there was very little difference in the battery consumed by the phone, meaning the screen battery usage is isolated from the phone by the android system by using the percentage used stats.

More importantly, you can see that there was a significant difference in the power used on a per minute basis between the optimized auto brightness and 100% power at all times. Keep in mind, this was an average of numbers throughout the day and that difference could have been even greater had I been able to use only indoor lighting levels at minimum screen brightness. Granted that was indoors 90% of the time, but it could have made a noticeable difference.

The average battery savings seen over this study was 29.29% from 100% brightness to the optimized auto brightness levels.

A second thing I noticed, which you'll see especially on the 100% brightness level graph, is that white backgrounds greatly affect screen power consumption and it is even more exaggerated when running 100% brightness. Black seemed to draw the least power, which souldn't come as a surprise to any of us.

attachment.php


attachment.php


attachment.php
 

Attachments

  • AverageComparison.jpg
    AverageComparison.jpg
    28.8 KB · Views: 525
  • 100ScreenBrightness.jpg
    100ScreenBrightness.jpg
    48 KB · Views: 462
  • optimizedbrightness.jpg
    optimizedbrightness.jpg
    55.7 KB · Views: 520
Tips to conserve battery in regards to screen usage:
1.) Use the lowest brightness you can while still being able to read the screen.
2.) If you have a ROM that supports it, definitely go in to the brightness level adjustments and tweak them to use low brightness settings. If you need help with that, I can help if you will post here or PM. The key is to getting the trigger ranges for the ambient lighting sensor set up for your conditions that you see in most any situation and then tweak the brightness levels to a minimum in each situation. This will allow you to use auto brightness instead of manually adjusting the brightness in different conditions.
3.) If your apps support it, use dark themes. If your ROM supports it or you have a choice of themes, also use any dark theme you can.

If you take this to the extreme, I would not be surprised to see people gain 30% or more of screen on time per charge. This could equate to 3-4 hours of time off charger, maybe more.
 
If anyone can show me how to put something into a table format on here I'll post up the screen levels I used.
 
Excellent work on this and thanks for posting it!

I generally used to keep my screen at 38% with AOKP b28 and earlier, but for some reason the brightness seems higher on AOKP b29 (AOSP 4.0.4 based). So now I'm running at 25% all the time unless I need it to be brighter outside, then I am generally fine with either 50% or 75%.

I thought about doing a test to check what the battery consumption was @ 25%, 50%, 75% and 100% to see if it scales linearly or what. Actually, with those 3 or 4 values, we should be able to extrapolate a power curve and estimate the usage at other % levels.

My problem is I'm not sure I can leave my phone alone for up to 4 hours that many times LOL and I'm also weary of screen burnin doing testing.

But this is awesome data/info, thanks again for posting!
 
I swapped out this:
[table]
[tr]
[td]Lower[/td]
[td]Upper[/td]
[td]Screen[/td]
[/tr]
[tr]
[td]0[/td]
[td]199[/td]
[td]10[/td]
[/tr]
[tr]
[td]200[/td]
[td]399[/td]
[td]20[/td]
[/tr]
[tr]
[td]400[/td]
[td]599[/td]
[td]25[/td]
[/tr]
[tr]
[td]600[/td]
[td]799[/td]
[td]30[/td]
[/tr]
[tr]
[td]800[/td]
[td]999[/td]
[td]40[/td]
[/tr]
[tr]
[td]1000[/td]
[td]1249[/td]
[td]50[/td]
[/tr]
[tr]
[td]1250[/td]
[td]1499[/td]
[td]60[/td]
[/tr]
[tr]
[td]1500[/td]
[td]1999[/td]
[td]70[/td]
[/tr]
[tr]
[td]2000[/td]
[td]2999[/td]
[td]80[/td]
[/tr]
[tr]
[td]3000[/td]
[td]3999[/td]
[td]90[/td]
[/tr]
[tr]
[td]4000[/td]
[td]5999[/td]
[td]100[/td]
[/tr]
[tr]
[td]6000[/td]
[td]9999[/td]
[td]125[/td]
[/tr]
[tr]
[td]10000[/td]
[td]∞[/td]
[td]255[/td]
[/tr]
[/table]

For this:[Hide]
[table][tr][td]Lower[/td][td]Upper[/td][td]Screen[/td][/tr][tr][td]0[/td][td]199[/td][td]10[/td][/tr][tr][td]200[/td][td]399[/td][td]20[/td][/tr][tr][td]400[/td][td]599[/td][td]25[/td][/tr][tr][td]600[/td][td]799[/td][td]30[/td][/tr][tr][td]800[/td][td]999[/td][td]40[/td][/tr][tr][td]1000[/td][td]1249[/td][td]50[/td][/tr][tr][td]1250[/td][td]1499[/td][td]60[/td][/tr][tr][td]1500[/td][td]1999[/td][td]70[/td][/tr][tr][td]2000[/td][td]2999[/td][td]80[/td][/tr][tr][td]3000[/td][td]3999[/td][td]90[/td][/tr][tr][td]4000[/td][td]5999[/td][td]100[/td][/tr][tr][td]6000[/td][td]9999[/td][td]125[/td][/tr][tr][td]10000[/td][td]∞[/td][td]255[/td][/tr][/table][/spoiler]
[/spoiler]

And that seems to have fixed the table :)
 
svt,
Xyro was able to get rid of the spacing problem with your table so can can get rid of the hide tags if you want. Looks like you need to not use hard returns when you put it together (which for me as a former programmer is a PITA, I like whitespace).
 
I thought about doing a test to check what the battery consumption was @ 25%, 50%, 75% and 100% to see if it scales linearly or what. Actually, with those 3 or 4 values, we should be able to extrapolate a power curve and estimate the usage at other % levels.

Good thought. That may be my next step in this process. Didn't really have a next step but I guess I do now! May see what I can do with that idea the next week or so.
 
svt,
Xyro was able to get rid of the spacing problem with your table so can can get rid of the hide tags if you want. Looks like you need to not use hard returns when you put it together (which for me as a former programmer is a PITA, I like whitespace).

Same for me :p I liked my code to be spaced and indented perfectly so I could read it and make sure all my statements and such were properly opened and closed.
 
I should have results of some kind regarding the 25%, 50%, 75% power consumption later today. I'm just going to do a quick and dirty study initially. If the numbers look good, I might leave it at that, if they look a little skewed, I'll try to go back and do a proper study collecting data over several days at each percentage.
 
Same for me :p I liked my code to be spaced and indented perfectly so I could read it and make sure all my statements and such were properly opened and closed.

It only took a few seconds of mashing the delete and then the end key alternatively to remove all the hard returns, so I'd stick to typing it out with the hard returns since it's easier.
 
It only took a few seconds of mashing the delete and then the end key alternatively to remove all the hard returns, so I'd stick to typing it out with the hard returns since it's easier.

Yeah, if I had realized that's what caused it, I would have fixed it, just didn't know. Will make a mental note of that for the future. Thanks again for the fix!
 
If early indications hold true, which they may not, the power curve on this thing ramps up very quickly. First run at 25% power only yeilded 1 hour and 37 minutes of screen on time drawing a tic over 10.2 mAh per minute. That's just 1 mAh per minute less than full power 100% brightness. I'll make another run with it tomorrow
 
If early indications hold true, which they may not, the power curve on this thing ramps up very quickly. First run at 25% power only yeilded 1 hour and 37 minutes of screen on time drawing a tic over 10.2 mAh per minute. That's just 1 mAh per minute less than full power 100% brightness. I'll make another run with it tomorrow

Hmm, that seems odd. If the difference is that little between 25% and 100%, I wouldn't expect 30% battery improvement with your tweaked auto levels. Definitely curious to see how the next run goes :)
 
Hmm, that seems odd. If the difference is that little between 25% and 100%, I wouldn't expect 30% battery improvement with your tweaked auto levels. Definitely curious to see how the next run goes :)


Keep in mind, the tweaked levels I have keep the screen at minimum brightness probably 90-95% of the time and it probably sees as much time at 100% power as it does at 25% power...actually it proabably gets more time at 100% power than it does at 25%, 50%, and 75% combined. I think we're going to find out that there isn't a lot of power savings if you increase you brightness much over minimum.

The biggest power saving methods you are going to find will be keep the screen at minimum brightness and absolutely no white backgrounds.
 
Into my second day of testing power level at 25% brightness and beginning to see that the power draw of the screen ramps up rapidly from 0%-25% and then levels off up to 100% with very minimal power increase to step up in brightness. Someone else can repeat this experiment and let me know how it goes, but from what I've seen, I will not go any further with this part of the experiment. I'm barely getting 1.5-1.75 hours screen on time at 25% power and could muster almost the same at 100% whereas I could easily see over 2 hours at minimal brightness.

If anyone else wants to give this a go and see what results they get, PM me and I'll give you step by step how to set it up and go about doing this. It doesn't require anything more than what you would do with your phone on a daily basis, so don't worry about screen burn in.
 
Not to spoil your findings but this is a real meaningful data set unless we know what you are running. For example, do you have any background services running like calendaring, push email (non-gmail or exchange) or skype? I get only 3 hours of battery life when I have all my services running - 7 IMAP email accounts polling every minute. This is with 10-15 minute screen time and no calls. My iPhone with the same 7 IMAP accounts plus an additional 4 calendars and skype running in the background, i get 12-14 hours. Big difference just based on what services are running. On the GNEX, Take out all emails except 3 accounts (1 gmail, 1 yahoo, 1 IMAP non-push), I can stretch between 7AM to 1PM day usage. If I cut off all synch service and just leave GMAIL running. I can go from 7AM to 4 PM.
 
Into my second day of testing power level at 25% brightness and beginning to see that the power draw of the screen ramps up rapidly from 0%-25% and then levels off up to 100% with very minimal power increase to step up in brightness. Someone else can repeat this experiment and let me know how it goes, but from what I've seen, I will not go any further with this part of the experiment. I'm barely getting 1.5-1.75 hours screen on time at 25% power and could muster almost the same at 100% whereas I could easily see over 2 hours at minimal brightness.

If anyone else wants to give this a go and see what results they get, PM me and I'll give you step by step how to set it up and go about doing this. It doesn't require anything more than what you would do with your phone on a daily basis, so don't worry about screen burn in.

What is on the screen when you are testing? If it's black or near black, it could explain the power draw being close 25% to 100%. I imagine if you set it to an all-white background the difference would be much more pronounced.
 
What is on the screen when you are testing? If it's black or near black, it could explain the power draw being close 25% to 100%. I imagine if you set it to an all-white background the difference would be much more pronounced.

These are all real-world usage situations. Not all black, not all white, not all of any one color. This is average power usage per minute throughout the day using the same apps every day for roughly the same amount of time. I know that when I use web browsing more one day the power usage will be higher that day and I expect it because web pages are mostly white. I do imagine if you siet it to all-white, the difference would be great, but that wasn't my purpose in the study.
 
Not to spoil your findings but this is a real meaningful data set unless we know what you are running. For example, do you have any background services running like calendaring, push email (non-gmail or exchange) or skype? I get only 3 hours of battery life when I have all my services running - 7 IMAP email accounts polling every minute. This is with 10-15 minute screen time and no calls. My iPhone with the same 7 IMAP accounts plus an additional 4 calendars and skype running in the background, i get 12-14 hours. Big difference just based on what services are running. On the GNEX, Take out all emails except 3 accounts (1 gmail, 1 yahoo, 1 IMAP non-push), I can stretch between 7AM to 1PM day usage. If I cut off all synch service and just leave GMAIL running. I can go from 7AM to 4 PM.


Please read everything before commenting. You either didn't read or didn't understand. I isolate all background processes and track that separately.
 
Back
Top Bottom