I was playing around with some .xml files and found power_profile.xml in framework-res.apk
My understanding system uses this file to guesstimate how much this or that used the battery.
So according to that file the most power consumption part of the phone is the radio, then screen and third is gps followed by active wifi.
This actually proves my previously observations that the traffic via radio (cellurar/wifi) is the battery killer and cpu running at lowest 192mhz vs 1500mhz is not that of a big difference.
Code:
<?xml version="1.0" encoding="utf-8"?>
<device name="Android">
<item name="none">0</item>
<item name="screen.on">74.5</item>
<item name="bluetooth.active">9.9</item>
<item name="bluetooth.on">9.7</item>
<item name="screen.full">232.8</item>
<item name="wifi.on">26.7</item>
<item name="wifi.active">99.5</item>
<item name="wifi.scan">66.9</item>
<item name="dsp.audio">0.1</item>
<item name="dsp.video">0.1</item>
<item name="radio.active">550.0</item>
<item name="radio.scanning">7.9</item>
<item name="gps.on">100.6</item>
<array name="radio.on">
<value>2.0</value>
<value>5.1</value>
</array>
<array name="cpu.speeds">
<value>192000</value>
<value>384000</value>
<value>432000</value>
<value>486000</value>
<value>540000</value>
<value>594000</value>
<value>648000</value>
<value>702000</value>
<value>756000</value>
<value>810000</value>
<value>864000</value>
<value>918000</value>
<value>972000</value>
<value>1026000</value>
<value>1080000</value>
<value>1134000</value>
<value>1188000</value>
<value>1242000</value>
<value>1296000</value>
<value>1350000</value>
<value>1404000</value>
<value>1458000</value>
<value>1512000</value>
</array>
<item name="cpu.idle">3.37</item>
<array name="cpu.active">
<value>407.8</value>
<value>420.0</value>
<value>426.9</value>
<value>432.5</value>
<value>438.4</value>
<value>442.5</value>
<value>448.0</value>
<value>457.3</value>
<value>466.4</value>
<value>473.9</value>
<value>484.5</value>
<value>494.7</value>
<value>505.8</value>
<value>515.6</value>
<value>524.9</value>
<value>534.3</value>
<value>544.1</value>
<value>552.4</value>
<value>566.8</value>
<value>581.1</value>
<value>595.8</value>
<value>603.0</value>
<value>608.8</value>
</array>
<item name="battery.capacity">1830</item>
</device>
This may be off topic, im not sure..still a bit tired from working till 3 AM lol, but do u guys all live in an area blanketed with LTE or not? The reason I ask this is because I think this is one of the primary reason for our phone draining battery really fast. I believe that when the phone is searching for an LTE connection and can't connect to one, it waste much more battery doing so than when it is actually connected to one.
I live in northern jersey, where most of the area is not covered by LTE yet. I work in NY however and most of the area is already under LTE coverage. I notice that I waste much more battery in NJ than when I am in NY at work. Im not saying that with LTE connected I am saving 20-30% more battery, but I can say that I see the percentage drop slower than when it's searching for one.
We really need to somehow be able to turn off LTE when we don't need it or not in range of it. I believe we can save more battery by turning it off, just like in Verizon's phones.
I live in an area of good LTE coverage speeds from 25 to 50 down and the battery still drains giving tops of 4.5 hours of heavy use. Although when the screen is off the baterry drains is less noticeable so the drain is somewhere between LTE and IPS screen.
Sent from my LG-P930 using xda premium
Well, considering this file is what I think it is, the radio scanning consumes 7.9 points, so yes, it would make sense if it drains additional battery.
wait, GPS on uses over 100 points??? Isnt dat kinda high?
is that the code that generates the details for 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"
}
aquariuz23 said:
wait, GPS on uses over 100 points??? Isnt dat kinda high?
Click to expand...
Click to collapse
By GPS on, I think it means, when the GPS is being used (when the icon appears in the top bar) not when the setting is enabled.
Related
{
"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 Oxygen 0.2.2 Beta Rom. Yesterday I recalibrate my battery, closed unnecessary programs, turn off wifi, 3g, gps and bluetooth. Morning I checked battery level and shocked battery leves was about %75. I checked if there any memory leaked program but I couldn't find something like that.
Display used battery percantage dramatically high?
What is the problem? Screen was turned off naturally.
'My Battery Kills Me' - sounds like the title of a cheap horror film - LOL
How long is 'overnight'? 8, 10 hours?
25% in that time sounds quite reasonable to me.
@cr1960 25% over 8 hr with wifi and 3g off is not normal and if you experience this i would check what is causing your drain.
@yapay Install current widget, place it on one of the home screens and set it up to wright to the log every 5 min. Then turn your phone in to flight mode overnight and the next day check the log, if you have more than 1 mA usage regularly during the night there is something using to much power. Install a monitoring app from the market and let it run during the night to find out what.
If it's mostly around 1 mA than your problem probably is gone after another charge.
Screen is very high for only 1.5h ish. Looks looks like you have high brightness settings and a lot of white/blue images being displayed.
------------------------------
- Sent via HTC Desire -
cr1960 said:
'My Battery Kills Me' - sounds like the title of a cheap horror film - LOL
How long is 'overnight'? 8, 10 hours?
25% in that time sounds quite reasonable to me.
Click to expand...
Click to collapse
overnight is about 7hr13m
TheGhost1233 said:
@cr1960 25% over 8 hr with wifi and 3g off is not normal and if you experience this i would check what is causing your drain.
@yapay Install current widget, place it on one of the home screens and set it up to wright to the log every 5 min. Then turn your phone in to flight mode overnight and the next day check the log, if you have more than 1 mA usage regularly during the night there is something using to much power. Install a monitoring app from the market and let it run during the night to find out what.
If it's mostly around 1 mA than your problem probably is gone after another charge.
Click to expand...
Click to collapse
I installed current widget. I will try this this night. Thank you very much for your suggestions.
th3 said:
Screen is very high for only 1.5h ish. Looks looks like you have high brightness settings and a lot of white/blue images being displayed.
------------------------------
- Sent via HTC Desire -
Click to expand...
Click to collapse
There is a misunderstood. I checked battery status after woke up and that was 60% display usage. After that I used phone during breakfast and later my battery was 18%.
Something is wrong...
I got massive battery drain done by display, no matter what rom using. Brightness set to minimum, no animations at all. And its really killing my nervs. Most biggest battery drain (drop-down) is from 100% - 85%, within an hour! (SLCD model)
EDIT: flashed other radio few days ago, recalibrate battery, nothing helps..
EDIT2: CPU is downclocked to 768 mhz max.
{
"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"
}
Like on every electronic device (with screens) the display is the most power-hungry component.
So the readings are OK - I have an AMOLED display and mine is always around 65-75%.
Battery life is excellent.
And BTW, it is not a huge battery drain, but only shows what ate most of your juice - and of course the display eats it most of the time.
I saw battery stats readings with only 15-20% battery usage... so i though this may be something wrong.
Yes, those were on Froyo ROMs, but were not accurate - in all 2.3 based ROMs (even official) the stats for the display are bigger.
Gusta_HR said:
I saw battery stats readings with only 15-20% battery usage... so i though this may be something wrong.
Click to expand...
Click to collapse
Or were the results of people barely using their phones sharing misinformation. Whomever has anything else on top of their list other than display, is barely using his device. Eod
erklat said:
Or were the results of people barely using their phones sharing misinformation. Whomever has anything else on top of their list other than display, is barely using his device. Eod
Click to expand...
Click to collapse
So true.
TouchPaled from Oxygen with Transparent XDA App
Gusta_HR said:
I got massive battery drain done by display, no matter what rom using. Brightness set to minimum, no animations at all. And its really killing my nervs. Most biggest battery drain (drop-down) is from 100% - 85%, within an hour! (SLCD model)
Click to expand...
Click to collapse
Do you think that display does not consume any power? Rethink!
If you keep the screen ON continuously then it consumes the battery a lot. Does not matter if it is AMOLED or SLCD. Keep the brightness low and timeouts short to get better battery life.
Screen consumes the most of power on a phone. In addition to mobile/WiFi Internet connection (during heavy traffic) and video encoding (camera), decoding (playing videos).
Watching films on a phone in a bright environment over a mobile connection would be a killer if you want to try
Phone calls drain the battery much less than screen. Same about listening musing while screen is switched off.
I've bought/installed BetterBatteryStats to help get a handle on an issue that I thought had to do with wifi activity, and noticed the biggest process identified in my case was "events/0".
Other users are having the same issue I've seen from other threads:
vikramjatt11 said:
rooting or not has NOTHING TO WITH THE ISSUES!!
- I have had a stock phone since the day it came out, and have "watchdog lite" installed, watchdog alerts me about 10-15 times a day that "suspend", "events/0", and "base system" in my phone are using over 50% CPU while the phone is sleeping...
Click to expand...
Click to collapse
Here's a thread on it (without any solid info) on the international GSII forum:
http://forum.xda-developers.com/showthread.php?t=1248844
What is "events/0"?
Also note a couple days worth of monitoring my battery relative to wifi:
(the SGSII thread mentions the correlation between the "events/0", sleep, wifi, and battery life also):
geolemon said:
Saturday was a bad one for me:
{
"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 had to plug it in around 8:30 as you can see.
My wifi was on all day and connected, since I didn't leave the house.
I've changed the wifi sleep setting today, so we'll see if that makes a change.
The only other thing I changed yesterday was from the stock wind weather live wallpaper to a koi Pond live wallpaper, good reviews and no mention of battery issues that I saw).
I'm suspecting the wifi but interested to hear any "eureka" discoveries.
Click to expand...
Click to collapse
Note on this chart where a gentle slope turns into a precipitous drop, corresponding exactly with the wifi being turned on in the bar below.
Then, a Monday (at work all day, with wifi sleep setting essentially leaving wifi off unless the screen is on).
During the week, I work fairly long hours... wifi off... Still 50% or 60% left at 8 or 9 pm, even better with the wifi sleep policy changed:
geolemon said:
UPDATE:
Note I changed my wifi sleep setting prior.
Today, great battery life...
... As long as my wifi wasn't on:
What's the deal?
Definitely a correlation between WiFi and battery drainage.
Just leaving work, thought I'd post this to show the effects of that wifi sleep setting.
But this is a problem!
Click to expand...
Click to collapse
BetterBatteryStats is showing "events/0" as the main consumer.
The above plots show some direct correlations to wifi-on time, to some significant battery drain - I think this seems significant.
Like many here I've been having battery drain issues since the day I purchased the Galaxy Nexus. I also purchased the extended battery since day one. I've been reading through every single forum on how to reduce the battery drain and none seems to have worked for me. I've tried switching to wifi, 3g only, no email push, no google+, etc and my phone at 100% battery would lose almost 30% within 2 hours idling. Then I was looking at the settings and I came across the Developer Options/Background process limit and limited my background process from Standard to At most limit to 1 process and my battery has improved tremendously. Prior to making the change the Android OS was using 80+ % on idle (Wifi or 3g didn't make a difference), now it's uses around 20 or less. On idle I'm seeing around 4% or less an hour vs 15% battery drain.
Please remember this may or may not solve YOUR battery drain, but it has definitely helped mine and I just wanted to share with the community on what else you can try.
I've had pretty good results with my battery. I think some of ya'll are either just playing around with it too much or have some energy-sucking apps out there.
{
"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"
}
Cheyse said:
I've had pretty good results with my battery. I think some of ya'll are either just playing around with it too much or have some energy-sucking apps out there.
Click to expand...
Click to collapse
Or that you don't have a connection to the data network.
Just say'n. (I do the same thing at night)
I had Wi-fi enabled for 12 hours, and the battery only dropped to around 85%. I have been on 4G for 5 hours now, and the battery is now down to 13%. I'm going to use a Wi-fi/3G combination tomorrow. Oh and I also have my phone rooted/underclocked to 900Mhz.
Cheyse said:
I've had pretty good results with my battery. I think some of ya'll are either just playing around with it too much or have some energy-sucking apps out there.
https://fbcdn-sphotos-a.akamaihd.net/hphotos-ak-ash4/397858_10100550605299635_27421897_51271764_409359273_n.jpg[IMG][/QUOTE]
Light use with very little screen time from the looks.
Click to expand...
Click to collapse
cvbcbcmv said:
Remember things in the dev section are there for a reason, this could cause other issues.
Click to expand...
Click to collapse
I've been using it for 3 days and have had no issues. Anyways its as easy as checking the standard limit if you ever wanted to revert back.
THE PROBLEM
For users on a Gingerbread TW rom: When you navigate through your Settings to the Battery section, you're presented with a little bar graph and plot. The first thing that you may notice is that after nearly 3 hours of usage, my display registers as only 2% of the drain. But by now, you're well aware that the screen most certainly is the largest drain on most computer devices, especially a touchscreen device. What you may see is something like the following:
{
"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"
}
So why don't these percentages make any sense? I can't tell you for sure, because I didn't make the decision, but I know where the problem lies. Your phone reports the battery level, as well as usage results, which are run through a calculator function to give you the above charts. Unfortunately, Samsung did not populate the calculator with accurate reading values and left the default useless ones in.
What I've done is to extrapolate the hardware values from our sister device, the Google Nexus S. The values work as mah drains against the 1500 mah stock battery.
Previously, the Wifi On, Wifi Active, and Wifi Scan profiles were all defaulted as .1 mah, whereas more accurate values are 4, 120, and 220 respectively. These make sense. Similarly, Screen On was .1 as compared to 49. The result is the following:
The results are immediate and expected. With the phone being on only 6 minutes with the screen on nearly the entire time, one would expect the primary battery usage to be the display.
THE SOLUTION
There is no simple universal CWM flash-able, but I offer you two solutions.
You can flash either of my roms or one of my FC09 themes which incorporate this fix.
OR you can open your favorite rom/theme, and inject the attached file into the framework-res.apk under res/xml.
DISCLAIMER
Please note, these are, and will always be, based on experimental test values. The only way to truly know where your phone is losing power is to physically test the various innards of your device personally. These values should simply give you a MUCH more accurate representation.
ORIGINAL FILE
Code:
<?xml version="1.0" encoding="utf-8"?>
<device name="Android">
<item name="none">0</item>
<item name="screen.on">0.1</item>
<item name="bluetooth.active">0.1</item>
<item name="bluetooth.on">0.1</item>
<item name="screen.full">0.1</item>
<item name="wifi.on">0.1</item>
<item name="wifi.active">0.1</item>
<item name="wifi.scan">0.1</item>
<item name="dsp.audio">0.1</item>
<item name="dsp.video">0.1</item>
<item name="radio.active">1</item>
<item name="radio.scanning">0.5</item>
<item name="gps.on">1</item>
<array name="radio.on">
<value>0.2</value>
<value>0.1</value>
</array>
<array name="cpu.speeds">
<value>400000</value>
</array>
<item name="cpu.idle">0.1</item>
<array name="cpu.active">
<value>0.2</value>
</array>
<item name="battery.capacity">1000</item>
</device>
NEW FILE
Code:
<?xml version="1.0" encoding="utf-8"?>
<device name="Android">
<item name="none">0</item>
<item name="screen.on">49</item>
<item name="bluetooth.active">142</item>
<item name="bluetooth.on">.3</item>
<item name="screen.full">260</item>
<item name="wifi.on">4</item>
<item name="wifi.active">120</item>
<item name="wifi.scan">220</item>
<item name="dsp.audio">88</item>
<item name="dsp.video">88</item>
<item name="radio.active">185</item>
<item name="radio.scanning">88</item>
<item name="gps.on">50</item>
<array name="radio.on">
<value>3.4</value>
<value>3.4</value>
</array>
<array name="cpu.speeds">
<value>100000</value>
<value>200000</value>
<value>400000</value>
<value>800000</value>
<value>1000000</value>
</array>
<item name="cpu.idle">1.4</item>
<array name="cpu.active">
<value>55.4</value>
<value>82.1</value>
<value>113.7</value>
<value>205.4</value>
<value>259.0</value>
</array>
<item name="battery.capacity">1500</item>
</device>
PLEASE NOTE
The attached file in the first post is already compiled. Using 7zip you should be able to safely insert it into framework-res.apk without having to decompile. The code shown in this post is obviously after de-compiling the framework.
Thanks for posting this!
This issue has always annoyed me lol
Bluerai said:
Thanks for posting this!
This issue has always annoyed me lol
Click to expand...
Click to collapse
I have to believe that some dev brighter than me has come across this and left it behind for some reason! But it's so stupidly simple (kinda) that I can't believe we've never fixed it. Truth is, I stumbled across this file yesterday while making some other modifications.
And what if we use the ET4G 1800 mah battery, or another higher mah battery? How would using your rom/theme/xml file effect readings?
nikon120 said:
And what if we use the ET4G 1800 mah battery, or another higher mah battery? How would using your rom/theme/xml file effect readings?
Click to expand...
Click to collapse
It will have the same effect as you would see now when switching between different battery capacities. In general, it does not seem as though the battery size factors too heavily into the results, so long as the percentage is reading properly. The important factors were how all of the various functions and hardware drain in mah. You should see readings that still more accurately convey your power usage. That said, this isn't perfect no matter which battery you use, but its 1000 times better than what we've had.
Thanks RK. I may stick this in TPR 2.2b as a final Epic release unless there is another firmware update.
Sent from my PantechP4100 using xda premium
kennyglass123 said:
Thanks RK. I may stick this in TPR 2.2b as a final Epic release unless there is another firmware update.
Sent from my PantechP4100 using xda premium
Click to expand...
Click to collapse
That's pretty much where I'm at. Fixing teeny tiny things to fill the void the GS3 anticipation is leaving in me!
[Not abandoning my Epic. It's becoming my wifi phone/toy.]
Thats pretty neat but i never have had this issue wonder why im using AOKP i wonder if its a whole TW versus AOSP?
XxLostSoulxX said:
Thats pretty neat but i never have had this issue wonder why im using AOKP i wonder if its a whole TW versus AOSP?
Click to expand...
Click to collapse
This would only be for TouchWiz software, as I mentioned that this is Samsung's doing. Although it really has nothing to do with the software, it's simply an omission on their part in their Gingerbread releases. AOKP is a source-built rom, and ICS-based at that.
RandomKing said:
[Not abandoning my Epic. It's becoming my wifi phone/toy.]
Click to expand...
Click to collapse
[off topic] I'm still wondering what I'll do with mine.. Not worth ditching for like $60.. But I'm not sure why I'd use it as a wifi toy when I'll have the SGS3.. [/off topic]
This is awesome thanks! That has always bothered me! Rooting tmorrow, restorin my backup and pushing that file in! Thanks Random!!!
Bluerai said:
[off topic] I'm still wondering what I'll do with mine.. Not worth ditching for like $60.. But I'm not sure why I'd use it as a wifi toy when I'll have the SGS3.. [/off topic]
Click to expand...
Click to collapse
Eh, I'm thinking it will phase out my iTouch as an mp3 player. Plus it has a keyboard which makes certain tasks easier. And eventually I'll give it to my kid as a toy, AFTER we've taught him how not to throw things... assuming it still works by then haha. Also, backup phone.
flastnoles11 said:
This is awesome thanks! That has always bothered me! Rooting tmorrow, restorin my backup and pushing that file in! Thanks Random!!!
Click to expand...
Click to collapse
You're welcome.