Related
Hello everyone, I lately have been getting horrible battery life!! I keep brightness on lowest setting, use wifi when possible, turn down haptic feedback all the way etc. do my best to save battery!
So my epic is Rooted with CWM3, and the latest frozen syndicate rom installed. Is it because my phone is rooted and the syndicate rom drains it more? is that why i have bad battery life? Does having your phone rooted drain battery life?
I ordered a Seidio 3300mah battery and got it yesterday in mail. Put in phone, then charged rest of night about it. Im using it today and am still receiving poor battery life, my friend who has epic ordered a cheap hong kong battery and is getting better battery life? I read something about conditioning your battery and draining it to 0% then charge fully to 100%? How does this work please explain?
Can someone just please help me use my new battery to its potential and help me out here?
Draining your battery for battery calibration is unecessary... there are a few threads regarding it...
Sent from my SPH-D700 using XDA App
so what should i do to improve battery life?
Rooting and custom ROMs reduce battery usage. You need to supply more details. Are you overclocking...that burns up battery usage. Have you tried Spare Parts to see what is using your battery? Has 3G been out in your area and the phone is searching for a data signal?
kennyglass123 said:
Rooting and custom ROMs reduce battery usage. You need to supply more details. Are you overclocking...that burns up battery usage. Have you tried Spare Parts to see what is using your battery? Has 3G been out in your area and the phone is searching for a data signal?
Click to expand...
Click to collapse
im not overclocking. spare parts? 4g is off- not in my area. 3g is on. what should i do. should i use my phone reguarly till it drains 0, then fully charge? i read something about wiping battery stats, shud i do tht? and i also read tht ec05 is horrible on battery life. should i go back to eb13 possibly or wht? and recommended roms?
try this thread:
Calibrate Battery thread - This is how you do it!
http://forum.xda-developers.com/showthread.php?t=884684&highlight=battery+stats
I used "The Powered Off Charge way" method and it did seem to make a difference.
Hope that helps, good luck
iModMM said:
im not overclocking. spare parts? 4g is off- not in my area. 3g is on. what should i do. should i use my phone reguarly till it drains 0, then fully charge? i read something about wiping battery stats, shud i do tht? and i also read tht ec05 is horrible on battery life. should i go back to eb13 possibly or wht? and recommended roms?
Click to expand...
Click to collapse
I have noticed no difference in DK28, EB13 or EC05 in my battery life. Do the calibration suggested in the post above. As for ROMs it is about personal choice. I have been with Bonsai for awhile now. I hear the ACS ROMs are very stable. Syndicate Frozen is good, Midnight is good. Read the OPs, learn what they remove and improve and see if that is what you are looking for.
Running SRF 1.1, with a custom theme, brightness at lowest setting, haptic feedback all the way up, because I need to know if someone is calling, I regularly get 30+ hours per charge. The two Chinese knockoffs I have get about 26 or so hours per charge.
I have recently seen a drop in my battery, spare parts on a couple of occasions should my phone would not sleep. Sometimes a reboot would fix this, but reflashed just to be safe.
After the reflash I was still getting bad battery life but spare parts showed no issues, so I started doing the airplane toggle again and that seems to of fixed it.
socos25 said:
Running SRF 1.1, with a custom theme, brightness at lowest setting, haptic feedback all the way up, because I need to know if someone is calling, I regularly get 30+ hours per charge. The two Chinese knockoffs I have get about 26 or so hours per charge.
I have recently seen a drop in my battery, spare parts on a couple of occasions should my phone would not sleep. Sometimes a reboot would fix this, but reflashed just to be safe.
After the reflash I was still getting bad battery life but spare parts showed no issues, so I started doing the airplane toggle again and that seems to of fixed it.
Click to expand...
Click to collapse
whats spare parts?
Spare parts is a free program available in the market place. It shows you more detailed statistics on what is using your battery juice.
Undervolting maybe. But I got stablilty issues. ymmv anyway.
My advice is
1. Set max clock to 800mhz and min to 200mhz. The CPU is volted -75 over 1ghz and 200 is volted the same as 100mhz. I use the Conservative governer but Ondemand works well too.
2. Get a good custom rom/kernel. CM7 and Frankenstein got the best through all my testing.
3. Brightness at lowest, turn off "Notify me when Wifi networks are available", Turn off syncing for contacts, the two GPS options, etc.
4. Take out as many applications as possible(Personal preference. I think it makes a difference) But I mean stuff you don't use. I take out Bluetooth, GPS, DRM, SNS, and most stock applications. If you're using Handcent you don't need stock SMS and vice versa.
5. If you're on 2.2 and lower I recommend a program like JuiceDefender to turn off 3G when your screen is off. The latest update on the free version removed the option to filter applications using data while the screen is off.
6.Enable Airplane mode on boot up. Then turn it off and use normally. TWS
7. Definitly calibrate your battery.
8. *Insert unreasonable battery tip here*
Oh and spare parts can be installed directly from the market. It's a program that allows monitering and for changing animation speeds and such. I don't use it for anything. You should also be able to go into settings -> about phone -> battery usage and see most of what spare parts would.
is tht one thread the one guy posted to calibrate the battery? will it work?
iModMM said:
is tht one thread the one guy posted to calibrate the battery? will it work?
Click to expand...
Click to collapse
Especially with a new 3300mAh battery! I recommend the top two as the third didn't work for me.
Juice defender on aggressive mode and setcpu on conservative mode increases my battery life when on standby quite a bit.
Don't drain your battery to zero it destroys our batteries. Don't use juice defender. If there is no reason that you need background data on like when you are sleeping turn it off but some say that's cheating but their idiots. That will dramatically improve your battery alone. Do the airplane shutdown every once in awhile some that's cosmetic but don't believe everything that is told to you. Only keep apps installed that you regularly use. Use spare parts to see if any app is causing significant drain. I'm a battery life guru.... ;-)
Sent from my SPH-D700 using XDA App
This guide is not meant to be as a whole and is not meant to be followed from beginning to end. There are several recommendations based on my own experience, some of them will give you big battery savings, some of them minor ones; I tried to recopile every config that helps to save battery, but every config is not suitable for everyone. (I´ll point it at the beginning of every section in bold blue).
You'll need a Rooted Galaxy Nexus, with a custom ROM and a custom Kernel.
The custom ROM will give you the ability to make a deep configuration of the device in terms of options. I'm actually using Liquidsmooth v1.25, but AOKP, CM9 and SlimICS have the same options (if not more) than my actual.
Some custom Kernels will give you the ability to change the CPU frequency and voltage, kernels are the main reason of some drainings or fantastic battery life, choose wise.
The normal Galaxy Nexus battery life is about 4 hours screen time. If you are not achieving this, the main reasons could be:
1. Some apps are draining your battery due to a continuous use (no deep sleep or continuous wake ups).
2. Screen too bright.
3. Bad kernels with draining problems.
4. Weak signal connections.
This guide is wrote by me, a simple user that is sharing his own experience of the last 4 and a half months with the device. Some statements may be wrong. I'll appreciate any positive recommendations in order to improve the guide and help the rest of the community to achieve the best battery life the device can give us.
I'm using actually Liquidsmooth v1.25 and PopcornKernel, in a GSM GNex with standrad battery (1700mAh), and I'm getting this results:
{
"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"
}
SCREEN
Due to the big screen, this is one of the elements of the device that affects in a major way to the battery live. (Great Savings)
It has been checked that black themes have a great impact on the battery due to the fact that one black pixel does not consume any battery.
Some apps have a black theme option on them, if you choose it you will save some battery.
On the other hand the brightness is the other part in the screen that has a big impact on the battery. In a logic way, less the brightness more the battery life. (Greatest Savings)
Now the latest ROM's have a new amazing feature, we can change the interval the sensor works to achieve the ambient light, reduce the brightness minimum value (that's by defect way too high in low light conditions), and customize your prefered light levels (that are too way too high in default configuration).
By reducing the sample interval sensor a bit and reducing the minimum value a lot we can achieved abetter battery life in a great manner.
Also adjusting the light sensor levels to a more reliable one's that are by far lower than the default one's we'll achieved a more optimize system that consumes less battery.
Note: This are my actual, after 2 weeks of adjust, values but I'm still working on them, they are no 100% reliable.
CPU
The CPU is a great beast. In terms of battery is well adjusted, by as always, we can achieve a personal optimized system (this is Android, yeah!) that will balance performance and battery life. (Great Savings Underclock and Undervolt combo).
A very good speed and fluidness can be achieved with a very good optimized and well balanced performance-battery friendly system.. and yes, with the last advances in kernels and ROMs, we can have a perfectly smooth system with a top speed of 1000Mhz.
In the other hand Undervolt will help us to achieve a cooler system with some battery gain. With Undervolt we´ll limit the max. value of the Voltage for the specified frequency, if we have a kernel with Smartflex, this one we´ll allow lower voltages depending on the power need of the CPU.
Two important things:
1. It has been tested that the 700Mhz frequency is prefereable over the 300Mhz one, due to the drops on frequency signal of the phone.
2. Undervolt values are not the same for everyone, it can oscillate depending on the individual CPU. When I UV I always test my system with an Stability Test app.
Connections
GNex is a phone...also.. well, it's a super computer with phone capabilities. Due to the "always connected" philosophy the optimal baseband will save a lot of battery. An optimal Baseband and Radio (region optimized) will require less power and time to connect to the antennas and will have better connection always (less power irradiated). (Medium savings).
The Radio should be updated and region optimized, there's a magnificent post made by josteink that explains all the details concerning the Radios with links to every one available.(GSM)
[Radio] (GSM) Galaxy Nexus I9250 Baseband dumps collection & discussion
European Radio Recommended: XXKK6 (XXLA2 is giving too high "Phone Idle", resulting in drain problems)
For the CDMA version there is another magnificent post by ready5 with a compilation of every RADIO for the CDMA version of the GNex.
(CDMA) [RADIOS/HYBRIDS]*UPDATED* 4.0.4 FULL 2/6/2012 PLUS FRIED RADIO Halp!
In the GSM version on the other part the 3G, HSPDA consumes great great great battery juice. If you are not in WIFI and are not using the data connection, a great way to save battery life is changing from HSPDA or 3G to 2G networks (this is really noticeable if you travel a lot by car or train, cause you are continuing connecting a reconnecting from different radio antennas).
There's some ROMs as Liquidsmooth that allows when you are not on WIFI and after an specified delay, to change to 2G automatically (or low consuming) networks when you have the screen off. This is a great way to save battery when you are not at home, reducing the standby drain of the phone outdoors.
.
The automatic 2G when sleep is a main function of Juice defender. Thanks to a1exus for recommendation.
In the CDMA version the LTE consumes also great great great battery juice. If you are not in WIFI and are not using the data connection, a great way to save battery life is changing from LTE to 4G networks (this is really noticeable if you travel a lot by car or train, cause you are continuing connecting a reconnecting from different radio antennas).
Thanks to thenickisme for this!
WIFI
Wifi has a crazy history on the GNex. After talking and talking, posting and posting, it has been tested that WIFI always on while sleep is the best way to achieve a longer battery life. (Medium savings).
Also the new ROM's have amazing feature that change the WIFI interval (we normally stay at the same WIFI always), increasing the value will save batterty life reducing the continues scans that produce the WIFI Always ON requirement.
Services and Apps
The best thing of Android is that we can configure anything, one of the best and underestimated feature is the Freeze or Service Uninstall. We did it before in Windows and we can do it now. Through the Apps section in Preferences or the mythic Titanium Backup we can disable or uninstall an internal function of the systems that is normally used, giving more resources to the system and in some cases, saving some battery. (Low to Minimum Savings).
There are some ICS functions that no everyone uses. For example, I don't use any Bluetooth, NFC, Google Voice, Google Search or Speech function of the system, freezing or uninstalling them will optimize our system giving some battery juice.
Note: This is a dangerous thing if you don't understand what you're doing. Make always a Nandroid before Freezing or Uninstalling an essential function, just to be cautious.
According to the Apps we have to take in account the Background Syncing or Sync Interval, most of the time the apps don't need to be synced every 5 minutes, like weather, if we make longer updates we'll achieve a good saving battery related. (Great Savings if many apps with many connections).
Widgets, 5 homescreens full of widgets updating in real time could be detrimental to the battery live, take care when adding widgets and as said in the previous paragraph, change every widget preferences to update in longer times than usually they have by default. (Great Savings if many apps with many connections).
Bad Apps are the one's that not allow our device to deep sleep or wake up continuously our GNex. There are several on the market, Readability for example is a new one that wake up continuously our device attempting to download new articles, on the other part, some time ago Widgetlocker had some problems not letting deep sleep the GNexus (don't know now). (Great Savings if there is an apps giving deep sleep or wake ups problems).
Pointing on this, the best way to know if any app is not behaving well in the system is through 2 apps:
- BetterBatteryStats, that will look for any wake up of the device while sleep.
- CPU Spy, that will tell us if the device is deep sleeping ok or not.
Other things
There are other things that will help us in a great or minor manner to save battery life.
Sync Data usage (Google services like contacts, bookmarks, etc..) consumes battery, if you limit this usage, you´ll gain some juice. The new ROM's in the Powersaver tag will allow you to limit this sync usage. (Low Savings).
The Dial Pad Touch Tones and Vibration affects battery also (yepp it's true, and in a great way!), disabling this features will give you some extra battery juice. (Low to Medium Savings with combo sound plus vibration).
The Google Location services and Backup&Reset Data consumes great battery also, limiting this services will gave you some extra juice. (Medium Savings).
The last little thing that will help you save batt life will be the Automatic Date&Time option, disabling it will give you some extra juice also. (Lowest Savings, practical minimum).
Live Wallpapers, they are very nice but will drain your battery quickly. Static Wallpapers are preferred, and if posible, dark ones. (Medium to Great Savings).
Experimental
This are new tweaks that normally appear in new/advanced kernels, his use according to battery save is still not really tested or can have a detrimental on the physical conditions of the device/battery. Use them with caution or if you really know what you are doing.
[MOD][KERNEL]Battery Life eXtender (BLX), this is a tweak created by the popular Ezekeel and in his owns words: "Older types of rechargable batteries exhibited a 'memory effect' which made it neccessary to completely charge/discharge the battery when using to prevent degradation of the capacity. Modern Lithium-Ion batteries like in the Nexus S do not show this problem and thus it is not necessary to use the battery in complete (dis)charge cycles. In fact on the contrary, it is commonly accepted that both very low and very high charge states accelerate the degradation of the battery capacity (that is why you should store Li-Ion batteries at around 40% charge).
While a low charge state can be simply avoided by charging the device more often, the battery in the Nexus S by default is charged to around 95% capacity and I could not find any app or tweak to stop the charging at a lower capacity. Thus the only way was to use the manual override and pull the cable which is annoying since one had to monitor the charge state." (Unknown Savings).
Galaxy Nexus is charged by default to the 96% of this capacity, with this new tweak you can gain this 4% (don't know for sure if you can get the 101%) of battery life, in 4 hours screen time, more or less 10 minutes, but it can be detrimental on the long way to the battery physical life.
You can found this tweak in the last nightly of Franco's Kernel, and can be activated via his own app.
You can find more information in Ezekeel post here at XDA.
[MOD][KERNEL]Undervolt of IVA and CORE Voltage, new patches let undervolt the IVA (hardware media decoder) and CORE (GPU Voltage), I'vce been playing with this all the day and I've managed to undervolt a 15-20% de original frequencies. (Unknown Savings).
I understand that with this we are limiting the maximum voltage they can use, letting them to use lower ones according to GPU load. I'm not sure at this (GPU uses smartflex also ¿?) but with a descent of 20% on the voltage could result in longer battery life while playing games or seeing movies.
I'll try further undervolts, but this are my actuals on a stable system.
You can play with this voltages via the last nightly of Franco's Kernel, and via his own app.
Take care playing with this, could result in system instabilities, reboots, freezes, etc.
Links of interest
- BetterBatteryStats, A high battery drain is often a limiting factor for a great user experience.
With BetterBatteryStats you can analyse the behavior of your phone, find applications causing the phone to drain battery while it is supposed to be asleep and measure the effect of corrective action.
- CPU Spy, This is a simple app to display the time the CPU spends in each frequency state. This can be a useful tool in diagnosing battery problems or tweaking your over-clock settings.
It also displays the current kernel information.
- StabilityTest, StabilityTest is a stress-testing tool for android devices with error reporting.
StabilityTest is a CPU, GPU, RAM/memory stress-testing tool for your device, whether stock and unrooted (limited functionality) or rooted and overclocked with SetCPU, SetVsel or similar tools.
Extended Battery
At the end, the best way to extend the battery life is with an Extended Battery, they are not very expensive and only increase a little bit the thickness of the device. They can be bought at several places through the typical places as Ebay, Expansys or Amazon.
Important: Take in account that the CDMA and GSM versions have different batteries and they are not compatible, normally the GSM one is longer and black and the CDMA is wider and blue.
Borrowed from Buddy Revell
Calibration
Once a month we´ll have to calibrate our battery so that the information to be shown on screen is accurate and true. The steps are as follows.
1. Charge the Nexus until the indicator shows us is 100%.
2. Disconnect it and let it discharge until it turns off by herself.
3. Then load up fully charged. Note that this state is reached after one hour approx. since it shows that is already loaded.
Note: There are several apps in the Market that help calibrate the battery, although I have heard that in ICS Google has changed the file location does. Log of our battery so many of them may not work well if they are not updated.
great post especially for a new gnex user. will look through these options thoroughly.
Very nice. Thank you! Took a few suggestions.
Looks like I've got some work to do =D
Sent from my Galaxy Nexus using XDA
edited out
Cool story bro! Lots of good tweaks to maximize battery.
Sent from my Galaxy Nexus using xda premium
What rom is that? You should state that ...
Awesome. Those custom backlight levels are going to save a good amount of battery. I tried using a filter, but it made using the phone in sunlight impossible.
It's working inside well and based on what I see from the custom levels, it should have no issues once I take it outside.
As for the underclocking, comparing iOS and Android isn't fair. iOS has an advantage with its closed ecosystem. I personally overclock the GNex to achieve the same snappiness I had on my iPhone 4S. Sure the underclocking will save battery, but I might as well be using an older phone if I'm going to underclock.
When it comes down to it, everyone's battery is >50% screen consumption. Your custom levels are going to tremendously increase battery life.
gogol said:
What rom is that? You should state that ...
Click to expand...
Click to collapse
It's in my signature, Liquidsmooth v1.25.
myrdog said:
Awesome. Those custom backlight levels are going to save a good amount of battery. I tried using a filter, but it made using the phone in sunlight impossible.
It's working inside well and based on what I see from the custom levels, it should have no issues once I take it outside.
As for the underclocking, comparing iOS and Android isn't fair. iOS has an advantage with its closed ecosystem. I personally overclock the GNex to achieve the same snappiness I had on my iPhone 4S. Sure the underclocking will save battery, but I might as well be using an older phone if I'm going to underclock.
When it comes down to it, everyone's battery is >50% screen consumption. Your custom levels are going to tremendously increase battery life.
Click to expand...
Click to collapse
Thanks
With the iPhone comparison I just tried to emphasize that sometimes underclocking results in the same snappiest system, but yes, is a little unfair though (but I can assure that with the latest Kernels and ROMs that have been released, I have a totally fast and smooth system with only 1000Mhz).
Well done good job
Good guide. Rather than seeing multiple thread's about awful battery life its nice to see people talk about how to maximize their battery life
Sent from my Galaxy Nexus using xda premium
Good guide—thanks for taking the time to make it—but along with it’s very good parts, it has quite a few inaccuracies, is misleading in some places, doesn’t fully explain the ramification of making many of the changes that are proposed and makes questionable changes for very little gain. Amongst other things, my major issues with it are:
You wrongly assume a device that does not get four hours of screen time is not optimized—this would be incorrect as one can get four hours of screen time with the stock ROM and default configuration.
The stock ROM does not allow you to customize the backlight and CPU—so you should point this out.
It’s condescending to the iPhone (while the GN might be better in many ways, patronizing another device has no place in a “guide”).
BinkXDA said:
Good guide—thanks for taking the time to make it—but along with it’s very good parts, it has quite a few inaccuracies, is misleading in some places, doesn’t fully explain the ramification of making many of the changes that are proposed and makes questionable changes for very little gain. Amongst other things, my major issues with it are:
You wrongly assume a device that does not get four hours of screen time is not optimized—this would be incorrect as one can get four hours of screen time with the stock ROM and default configuration.
The stock ROM does not allow you to customize the backlight and CPU—so you should point this out.
It’s condescending to the iPhone (while the GN might be better in many ways, patronizing another device has no place in a “guide”).
Click to expand...
Click to collapse
Thanks, but the guide tried to be a compilation of many procedures that would give you a longer batt life. Some of the recommendations give you maybe 4-5% more autonomy, some of them 0,5%, don't know because I'm not an engineer and don't have the tools and time to measure the actual rate of discharge of the device, I'm only a user that took some time in share his personal experience in the last 4 and a half months with the device.
1. It was a way of talking, did not tried to assume anything because was not thinking in anithing out of the people that are not having more that 3 hours batt time, was a simple way of selling something (a well/bad introduction depending on the eyes or mentality of the reader)
2. We are at XDA and this is a developer device, I asume a minimal technological base, I was assuming this. But I point this out because I also think that will help some people.
3. Tried to emphasize that while the over sold as an ultra-quick device is only 1Ghz Dual-Core, the GNex can be as fast and reliable as the iPhone 4S with the same speed, and also saving batt (and in addition you have 450 more Megaherzs if you want to use them.. if you root). It’s not condescending cause if I would have liked to buy an iPhone I would bought one as the 99% of the people here.
I am a simple user, as everyone here, trying to help people as people has helped me developing great ROMs and Kernels I like positive and concrete recommendations over vague and negative ones.
hey op,
SrTapir said:
If we take in account that the Mega-Ultra-Cool-Fashion-Posh and "Ultra Quick" iPhone 4S has a only Dual Core 1Ghz processor, we can assume that with the same speed we can achieved a very good optimized and well balanced performance-battery friendly system.. and yes, with the last advances in kernels and ROMs, we can have a perfectly smooth system with a top speed of 1000Mhz.
Click to expand...
Click to collapse
i think the iphone is clocked at 800mhz even it has 1ghz
king23adrianc said:
hey op,
i think the iphone is clocked at 800mhz even it has 1ghz
Click to expand...
Click to collapse
Ups!
SrTapir said:
Ups!
Click to expand...
Click to collapse
First of all thanks to all the people for your comments!
I've updated the first post with your recommendations, and added a couple little things.
SrTapir said:
First of all thanks to all the people for your comments!
I've updated the first post with your recommendations, and added a couple little things.
Click to expand...
Click to collapse
The Calibration section is a little confusing. It only takes 1 hour to go from 0% to 100%?
Also, do you know anything about calibration with ROMs that only allow you to charge to 99%?
myrdog said:
The Calibration section is a little confusing. It only takes 1 hour to go from 0% to 100%?
Also, do you know anything about calibration with ROMs that only allow you to charge to 99%?
Click to expand...
Click to collapse
No, it takes 1 hour after the GNex indicates is fully charged. I'll try to change it in order to clarify.
No, sorry, maybe you can "delete battery logs" via recovery. (I never did it, and don't know if can be detrimental).
Rule 1: If you haven't taken these steps, you haven't done a thing in the way of actually optimizing your battery life, and please do not complain that your battery is bad if you haven't at least done steps 1 and 2!
Step 1: Use BetterBatteryStats: http://forum.xda-developers.com/showthread.php?t=1179809
This will diagnose battery drain issues. If you have apps that are sucking battery in the background, this will show it. Google the ones that have high partial wakelock, and usually you will get a diagnosis. It is also sometimes very easy to figure out what is sucking battery just by looking at the application that is holding wakelocks or having many alarm wakeups.
Step 2: Sync settings, make sure that all of them are either at push or as high as you're personally willing to allow between sync checkups. Any sync settings that happen too often will trash battery life.
Step 3: Radio based drain is a very big part of battery life! As such, if you do not need constant sync, you can turn off mobile data on your own when you do not need it, or go to the Mobile Network settings and disable always on mobile data. This can greatly increase battery life, but at the expense of sync not working when mobile data is off.
Step 4: Display brightness can greatly affect the power drain of the battery! You can either manually control the brightness, download Lux autobrightness to make your own autobrightness settings, or flash a custom autobrightness setting in the ROM in order to achieve this. It also can have the side effect of making the display of the right brightness when in the sun and in the dark, so it is always at ideal brightness to preserve battery.
Step 5: Make sure that the battery is calibrated. This is not very complicated. Download currentwidget from the market, put it on a homescreen. Charge the device until currentwidget indicates 0 mA charge. Use the phone until the phone shuts off. You might want to then go to hboot and drain the battery until it shuts off again, and then do a full charge again. Only do this once every 2-3 months, because this is bad for the battery.
Step 6: Adblocking! One big cause of battery drain and unnecessary network usage is downloading ads. If rooted, use Adaway and Adblock to block ads from ever being downloaded, and use Adaway's adware feature to detect and remove apps with adware!
Step 7: A radical step is to use Core Control or something similar to either underclock, undervolt, or just shut off cores. Undervolting is always highly suggested, as it will help reduce heat and give the phone a longer lifetime, but underclocking and shutting off cores will reduce performance!
Step 8: Custom ROMs and kernel experimentation might yield just a bit more in the way of battery life, and also give much more customization and features.
After this, you have likely topped out all that can be reasonably done to extend battery life. If you find that your battery drain is still poor, perhaps you have a defective battery, or maybe even a defective device (Highly unlikely, but who knows...). It is also possible that you simply have a use case that is much more than the phone can accomplish, in which case you can either use a battery case, or an external battery to charge the phone on the go.
Hunt3r.j2 said:
Step 5: Make sure that the battery is calibrated. This is not very complicated. Download currentwidget from the market, put it on a homescreen. Charge the device until currentwidget indicates 0 mA charge. Use the phone until the phone shuts off. You might want to then go to hboot and drain the battery until it shuts off again, and then do a full charge again. Only do this once every 2-3 months, because this is bad for the battery..
Click to expand...
Click to collapse
Weird, I've tried this many times, and can't get the indicator show exactly 0 mA...
the lowest for me around 3-5 mA... :|
what do you mean by undervolt because i dont understand..what are the consequences ?
nemer12 said:
what do you mean by undervolt because i dont understand..what are the consequences ?
Click to expand...
Click to collapse
if too much undervolting the phone freezes/ reboot ....so the best value for undervolting is between 50 and 100mv ....in some cases undervolting increases battery life and makes the phone cooler but not much ...
Under volting is when you tell the battery to provide a little less power than usual.
Which is why the battery life usually increases, as less battery is being used than previously.
But as stated, too much can cause the battery to not provide ENOUGH power, therefor crashes and cannot boot properly etc.
One-X-master said:
if too much undervolting the phone freezes/ reboot ....so the best value for undervolting is between 50 and 100mv ....in some cases undervolting increases battery life and makes the phone cooler but not much ...
Click to expand...
Click to collapse
Pretty much, I would say. Drastic increase of battery in games: phone won't get hot => battery will last longer without overheating and, what is much more important, it will stay healthier in long run.
Even on wall charger while playing, my HOX won't overheat with - 100mv UV.
This is the main feature I miss on JB Sense without custom kernels
Sent from my HTC One X using xda app-developers app
THANK YOU
MysteryE said:
Weird, I've tried this many times, and can't get the indicator show exactly 0 mA...
the lowest for me around 3-5 mA... :|
Click to expand...
Click to collapse
Same here. On both my old HTC Sensation, and my HOX. Never saw the mA reach 0. Even after leaving on the charger for a couple of days.
DarkManHaze said:
Same here. On both my old HTC Sensation, and my HOX. Never saw the mA reach 0. Even after leaving on the charger for a couple of days.
Click to expand...
Click to collapse
The problem is, the phone cannot get the same amount of energy, it consume (in fact, it is the millisecond, where the phone is fully charged, than it discharges for some minutes, than it will be charged again for three minutes and so on periodically). So, what I mean, you will almost never see 0 ma on one X or other modern phones. You can only see that, if device can disable battery while it is fully charge and use wall charger like a main supply. And the last device with such behavior was Huawei s7 back to 2010
So, 3-5ma is pretty ok.
Sent from my HTC One X using xda app-developers app
Android 4.2.1
CyanogenMod 10.1 Snapshot M1 (21/1/13)
Franco Kernel R364
I'm trying to maximize my battery time.
(Power mode BeastlyBattery 192MHz~1036MHz, Governor: Lazy, IO Scheduler: deadline, Screen of Max Frew: 384MHz)
I want to UV my CPU (and maybe IVA and GPU also, does it helps too?) to save some battery.
Should I just decrease the voltage a bit, use stability test app and keep going till there will be errors,
or I can just decrease like someone else on the web and then keep going..?
Can it do something to the device? (because Its just undervoltage..)
For how long I need to run the stability test?
I saw this topic:
http://forum.xda-developers.com/showthread.php?t=1599025
and he says:
"1. It has been tested that the 700Mhz frequency is prefereable over the 300Mhz one, due to the drops on frequency signal of the phone."
Anyone tested this?
Does UV degrades preformance?
What is SmartFlex?
Anything else I need to know about that?
Im gonna make this one quick, so my apologies if I don't address your questions directly.
Prior to my Galaxy Nexus, I had a T-Mobile SGSII. I too had the belief that undervolting/clocking would improve my battery life substantially. It seemed to work but then I was only getting the results that I wanted to get, and thats because I went to extremes to lowering my screen brightness to minimum and using my phone a fraction of what I used to.
With the help of others and trial and error, my major conclusion is that undervolting/clocking, though normal headset use will not improve your battery life by a landslide. Android is so well optimized to save you as much battery as it can. Sure there are things here in there that interrupt that optimization such as bugs or kernel issues but that something even undervolting/clocking will not be able to solve.
If you do go into undervolting/clocking your device, please keep in mind that the most you will probably get out of it is maybe 45 minutes to 1hr extension, but thats not display time.
What you can do to improve your battery life is turn off whatever sync services you don't use, lower your screen brightness ( the display is the major battery hog in the GN and SAMOLED devices), use dark wallpapers and dark themes if apps support it, use wifi, disable 3G when not in use. The radio you use can also potentially affect your battery life and signal quality.
Those are just a few suggestions, the rest is up to you.
Good luck!
P.S. Kernels also add variation to the longevity of your battery life. It's been a very long time since I touched CM10 so I'm not gonna go and defame that ROM but do try something else that possibly offers better battery life. If MODs are a MUST for you, then you will be faced with a lower battery life compared to stock based ROM's. It won't be an extreme difference but the difference will be there. If I may suggest a ROM, try this one. I can honestly say I can get up to 3-4 hours of display time on it with about a 12 hour standby.
I read a lot on the web that it does help to battery time.. :S
anyone?
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
063_XOBX said:
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
Click to expand...
Click to collapse
And undervoltage?
Different overnor?
Undervolting will have minimal effect during actual use and a governor is based on specific user needs. One might save me battery while another works better for your usage. You need to actually mess with setting instead of just asking others what they use.
I need help with the kernel auditor to get better battery life, i have installed last cm nighties nad last NJ2 band, i read that if u change the kernel you can get better battery stats, the battery drop really fast, with low brightness and wi-fi off, just LTE data, without GPS. I use the app called "Root Booster" and the Calibrate Battery but it's the same. I need help with the kernels.
Sorry for the bad english, is not my native lenguage
B
My goto settings on this phone were interactive governor with the following tunables tweaked:
hispeed_freq = 918000
min_sample_time = 50000
timer_rate = 30000
Row I/O scheduler with 1024 kb read ahead.
Good battery life and not awful performance.
However, tweaking the kernel is unlikely to get you a miraculous change in battery life. Chances are if you're battery is draining super fast you have some rogue app or process keeping your phone from getting into deep sleep. You can troubleshoot that with better battery stats.
jason2678 said:
My goto settings on this phone were interactive governor with the following tunables tweaked:
hispeed_freq = 918000
min_sample_time = 50000
timer_rate = 30000
Row I/O scheduler with 1024 kb read ahead.
Good battery life and not awful performance.
However, tweaking the kernel is unlikely to get you a miraculous change in battery life. Chances are if you're battery is draining super fast you have some rogue app or process keeping your phone from getting into deep sleep. You can troubleshoot that with better battery stats.
Click to expand...
Click to collapse
Explain me more about "gettin into deep sleep"
Your phone's CPUs will scale up and down under load, but they will always run at some minimum frequency even under low load if they are "awake". I think it was around 300 MHz minimum on the i747.
In deep sleep the CPU powers off entirely, and your phone goes into a very low power draw mode. It is still listening for calls, texts, etc., but drawing much less power than if it was awake.
Your phone should be trying to get into deep sleep any time the screen is off, but wakelocks can prevent it. Not all wakelocks are bad. You don't want your phone switching into deep sleep if you're playing music or downloading files with the screen off; however, some wakelocks are unnecessary. Low priority apps syncing excessively or some app or process going rogue and holding a wakelock when it serves no purpose are not entirely uncommon. The kernel holds wakelocks and therefore sometimes catches the blame, but rarely is the kernel actually the culprit for excessive wakelocks. The kernel is typically just doing what the higher level software like the android system or apps are telling it to do.
One good indication the i747 was suffering from wakelocks was if it felt warm to the touch even after sitting with the screen off for an hour or two. This phone always heated some during use, but it should be room temp / cool to the touch after a long time idle. Since lollipop I don't find android's battery menu in settings to be all that useful. The better battery stats app I linked to in the post above is a great tool for investigating wakelocks. It will let you know what % of the time your phone is in deep sleep, and what is keeping it awake; a much more analytical approach than the "is it warm when it should be cool" method.
jason2678 said:
Your phone's CPUs will scale up and down under load, but they will always run at some minimum frequency even under low load if they are "awake". I think it was around 300 MHz minimum on the i747.
In deep sleep the CPU powers off entirely, and your phone goes into a very low power draw mode. It is still listening for calls, texts, etc., but drawing much less power than if it was awake.
Your phone should be trying to get into deep sleep any time the screen is off, but wakelocks can prevent it. Not all wakelocks are bad. You don't want your phone switching into deep sleep if you're playing music or downloading files with the screen off; however, some wakelocks are unnecessary. Low priority apps syncing excessively or some app or process going rogue and holding a wakelock when it serves no purpose are not entirely uncommon. The kernel holds wakelocks and therefore sometimes catches the blame, but rarely is the kernel actually the culprit for excessive wakelocks. The kernel is typically just doing what the higher level software like the android system or apps are telling it to do.
One good indication the i747 was suffering from wakelocks was if it felt warm to the touch even after sitting with the screen off for an hour or two. This phone always heated some during use, but it should be room temp / cool to the touch after a long time idle. Since lollipop I don't find android's battery menu in settings to be all that useful. The better battery stats app I linked to in the post above is a great tool for investigating wakelocks. It will let you know what % of the time your phone is in deep sleep, and what is keeping it awake; a much more analytical approach than the "is it warm when it should be cool" method.
Click to expand...
Click to collapse
Perfect answer, that give me a lot of info i dont know about it, thanks a lot dude i will use the app and check what is the problem here!