Charge your phone FAST with this trick... - Motorola Droid X2

Don't know if anyone else has played with it, but if i need a FAST charge and i can afford to do it, i use setcpu to turn the max CPU as low as it will go, which is 216mhz and let the phone charge.
I am using Battery Circle on the stock moto ROM with as much blur removed as i can, and if i let it sit with this CPU speed forced, i will see it go from 20-80% in as little as an HOUR...
restarting the phone with the battery bug can get me even higher, maybe upper 80% on the battery.
Try it, it really works! I have played with a profile that sets it as soon as the charger is plugged in to around 400mhz but the phone i find lags and it is hard to use, so i just plug, launch the setcpu app and crank down to 216hz
when i am done i unlock the phone, and put the speed back to where ever i need it to be.

Wouldn't powering down the phone while charging achieve the same results?
I've had a lot of problems with cranking the cpu speed down to the minimum -- a lot of laggy performance and some lockups that required a battery yank. In fact I use setcpu to force the minimum speed on my phone to 456 MHz to avoid any such problems.

iCurmudgeon said:
Wouldn't powering down the phone while charging achieve the same results?
I've had a lot of problems with cranking the cpu speed down to the minimum -- a lot of laggy performance and some lockups that required a battery yank. In fact I use setcpu to force the minimum speed on my phone to 456 MHz to avoid any such problems.
Click to expand...
Click to collapse
It really depends on a few things.
Your launcher, what the phone is trying to do while idle, etc.
Example, i find that if i have a lockscreen pattern that needs to be drawn i will have to be patient with it.
and obviously powering down the phone works.
It also makes it so your calls go straight to voicemail and you miss all sms messages.
I use my phone for business and i cannot have that problem, so long as i use fast reboot to "wipe" things out once in a while nothing bothers me putting the speed down.
You can charge lower, around 500mhz.. it also helps.
I think it has to do with the voltage being used to power the CPU being very low that helps it charge so much faster.

Related

Lets try to narrow down the Overheat issue.

Edit:
From what I have gathered from those that have provided info.
Around 120*F is normal for heavy use, around 105-110* for medium use, 100-105* for light use. This is with cell data enabled, wifi lowers temps 5-10*, also temps are for extended use scenarios. (over 10-15 min)
Heavy use= 3D game or graphically intensive 2D game, streaming videos especially HD
Medium use= basic games web surfing sites with lots of images or some flash content
Light use= sending SMS, basic fooling with settings or other basic functions, streaming music with the screen off
I think we need to get a bit more scientific about testing this overheating issue out. I need help from a large group of people. I need those who think they have overheat issues and those who do not for the info to be useful.
First off... I believe these temps are just the battery, not the CPU. I think the CPU is running relatively cool as the rest of the phone does not heat up, or it seems what heat is felt is coming from the battery only.
This would explain why people claim that the extended battery does not have this issue. As batteries with higher mAh ratings are able to handle the higher power demands with less heat.
We need to do comparison tests using the same apps across tests and the same use times as well. Also no over or under-clocking and using the same CPU governor. (and between everyone participating where possible)
I have Minecraft and Sleepy Jack, they both produce similar temps after 15 minutes of play time. (around 117-120*F) I do not know if it gets any hotter with longer use because I rarely play longer than that at a time. I am at about the same temp after only 10 minutes so maybe that is the highest it gets.
I know for certain that enabling WiFi has a big impact on the temps. My fiance's phone would only get about 95*F, (according to the SetCPU widget) but when LTE is enabled it would get to 115*F. Mine hits 105* on WiFi.
I want to do at least two tests.
Lets use the following steps to test:
-For all testing the test time will be 15 minutes of play time.
-Lets all use Minecraft since there is a free version and I know the app causes the phone to work hard.
-No over or under-clocking
-On Demand governor
Test 1) Airplane mode enabled
Test 2) 3G enabled (not everyone lives in a LTE area, if you do, data from LTE enabled would be useful as well)
Now some optional tests. I did some rudimentary testing and there seemed to be an impact on temps.
Optional 3) Using interactive governor or Lag free governor
Optional 4) Use a different kernel... If you are on stock switch to ziggy's and vice versa. (this may be the most promising test as since switching to ziggy's I have had a few lockups where the old Android logo pops up on the screen and I need to do a battery pull to fix it. This happens to the fiance's device as well)
If you do these tests, please post the results, and what ROM and kernel you are using. I will keep track of the results and update as appropriate.
Lets see if we can find some consistent data and narrow this heat issue down.
Edit:
Running Ziggy's kernel I hit 108*F kept playing and shortly after the phone did the odd crash I mentioned.
Nice, had the same idea to do one of these over the weekend - you just beat me to it
I've done alot of research/ testing heat wise, and the pseudo-scientific conclusion that i've come to is that in a room temperature environment something like 75-85F idle & 110-115F netflix is normal for this gen of phones (Rezound, Galaxy Nexus, Galaxy S II, etc) - Give or take another 5F if you're using 4G. Seems like some devices are luckier than others & stay slightly cooler, but i'd gauge that they aren't the typical use case. IMO, (along side battery) data is a huge reason we've seen some of the face melting temperatures people have been reporting.
One thing I think would really help this thread is to set an easy to follow format for posting results. For example, here's a few tests I've done:
### Phone Info ###
ROM - Stock
Kernal - Stock
CPU Speed - Default (1.5)
Battery Type - Standard
Case - Generic TPU
## Test 1 ##
Charging - No
Data - 4G (4 bars)
App - Field Runners
Test Duration - 15 min
Start battery temp - 85 F
End battery temp - 112 F
Total Battery Drain - 20%
## Test 2 ##
Charging - No
Data - 4G (4 bars)
App - YouTube
Test Duration - 20 min
Start battery temp - 85 F
End battery temp - 104 F
Total Battery Drain - 16%
## Test 3 ##
Charging - No
Data - 4G (4 bars)
App - Onlive
Test Duration - 30 min
Start battery temp - 85 F
End battery temp - 125 F
Total Battery Drain - 40%
Hope this helps, i'd really like to see people participate - this information will be helpful for pretty much everyone in the Android community with a current gen phone.
Stock rom
Extended battery
Charging - yes
App - shine runner
Duration - 20 min
Start temp - 96F
End temp - 115F
3g, 3bars
This extended battery will get just as hot as the stock, just takes a little longer.
Edit-not quite as hot as the stock, but pretty toasty.
if it's the battery, then isn't the only parameter we need to test is current draw from the battery? no matter what radios/apps are enabled/disabled. It's bottom line is, the more we're drawing off the battery the hotter it's getting? I'd have to bring a pro in here on how Li-ion works in this form factor and why it gets hot, or what corners the battery manufacturer cut to make it possible!
The only time my battery gets hot is when I am in a weak signal area and the phone is searching for the 3G-4G signal. During daily use in a good signal area it never heats up.
My phone (and wife's also) heats up most notably during charging, especially when the battery is around 99% and going 100%. Usually the temp goes to ~ 45C (115F). In some rare cases, it was too hot to touch (dunno the exact temp). But some other times it would stay cool at all time.
Wife's first phone went into bootloop and her current phone is a new replacement. I kind of believe the overheating was the main cause of the bootloop problem.
thatsricci said:
if it's the battery, then isn't the only parameter we need to test is current draw from the battery? no matter what radios/apps are enabled/disabled. It's bottom line is, the more we're drawing off the battery the hotter it's getting? I'd have to bring a pro in here on how Li-ion works in this form factor and why it gets hot, or what corners the battery manufacturer cut to make it possible!
Click to expand...
Click to collapse
It's more than just the battery. Also: feel free to post a test - the more data we get from everyone, the better.
One important variable missing: ambient temp.
I was just playing words with friends for ten minutes:
Ambient temp: 67, Screen brightness: 50%,
4g: ON
wifi: OFF
my temp went to 105F, it's NEVER gone to 105F when playing before... and I play it every evening. It was hooked to the USB charger at the time, and when I felt it getting so hot, I looked at battery monitor and my net charge was negative, so it was using more than it was charging off the usb...
maybe something in some of those apps triggers something that causes the temp to rise? a loop? something?
thatsricci said:
I was just playing words with friends for ten minutes:
Ambient temp: 67, Screen brightness: 50%,
4g: ON
wifi: OFF
my temp went to 105F, it's NEVER gone to 105F when playing before... and I play it every evening. It was hooked to the USB charger at the time, and when I felt it getting so hot, I looked at battery monitor and my net charge was negative, so it was using more than it was charging off the usb...
maybe something in some of those apps triggers something that causes the temp to rise? a loop? something?
Click to expand...
Click to collapse
I noticed any time I charge with USB and use my phone it gets hot
Sent from my HTC Rezound
dustintheweb;21090574
One thing I think would really help this thread is to set an easy to follow format for posting results. For example said:
Good layout... and I think you are right about 115-120 degrees is normal for heavy use with apps that really stress the CPU or radio.
thatsricci said:
if it's the battery, then isn't the only parameter we need to test is current draw from the battery? no matter what radios/apps are enabled/disabled. It's bottom line is, the more we're drawing off the battery the hotter it's getting? I'd have to bring a pro in here on how Li-ion works in this form factor and why it gets hot, or what corners the battery manufacturer cut to make it possible!
Click to expand...
Click to collapse
A pro huh... good thing I'm here.
Ok I'm not a "pro" as it were, but i know a thing or too.
Its not going to be simply the battery, but I think it is a big culprit, and most of these devices only provide battery temps, not CPU or internal temps, this limits our overall knowledge of what is going on internally. The battery getting hot causes the device to heat up as well so a bad battery that overheats can cause the device to overheat.
All batteries will convert some energy draw into heat. This is caused by the internal resistance of the battery. Li Ion batteries have fairly low internal resistance compared to other types, but battery design an affect power output handling. Pulling more power than the battery can handle or near its limit and you get more heat than normal. The heat to output ratio stops being proportional and becomes exponential. So that means the real kicker is the actual amp draw on the battery. How much power the battery can handle is related to both the capacity of the battery and the manufacturing process/ design of the battery construction. I bet the new devices are straining the battery more than the current design can handle. There are better battery manufacture processes for better power handling, but that increases the cost of the battery.
(BTW battery is a misnomer for these, they are cells, specifically one 3.7/8V Li Ion cell. The difference is that batteries are made up of 2 or more cells. This goes for AAA, AA, C and D cells as well. Car batteries for example are made of six 2V cells, 6V lantern batteries are made of four 1.5V cells and 9V batteries are six 1.5V cells)
This is one reason I want to do a test with airplane mode on. This helps lower the power draw and allows us to get a better overall device temp, this helps us know if there is an issue with the CPU getting excessively hot vs just the battery being stressed to hard.
Kane5581 said:
One important variable missing: ambient temp.
Click to expand...
Click to collapse
I assumed most testing would be done at room temps of 68-72 degrees. If anyone tests in temps that are much higher or lower, then that would throw off the measurements.
I switched back to stock kernel, going to check for lockups and issues like I had before.
Click to expand...
Click to collapse
nev310 said:
I noticed any time I charge with USB and use my phone it gets hot
Sent from my HTC Rezound
Click to expand...
Click to collapse
Charging always causes heat. You are forcing power into a small space.
Charging via USB should only get the battery a little warm to the touch. 95* or so at most.
Charging with AC should get it a few degrees higher. I would think over 100* is odd.
as you reach 100% is when the heat should spike to the max temps I mentioned, before that it should just be warmish.
I will check mine to see how it behaves, but all my R/C batteries behave that way.
Replacing the kernel with stock lowered my temps quite a bit. I was around 110-115 degrees after 30 minutes or so. This was with LTE enabled.
Nobody else have anything?
noticed most of my heating issues when 4g was on (even when idling on 4g). Leaving in wifi and 3g keep the stock battery cool...on the extended I never really notice the heat, even on 4g.
I realize that you're trying to keep things as similar as possible, but I had an issue today listening to the broncos game in the NFL app while charging. It got so hot it boot looped. After getting it back up and running I started monitoring battery temps and even with the screen off and just listening to the game, it would get extremely hot. Btw, I have 4G 4 bars. A couple of times I ran to the freezer and put the phone in it for a couple minutes to cool it down as the temps got above 117°F.
From here, I thought it might be the CPU, so I set the maximum setting to 384 in antutu and then let the phone sit there with the screen off just as before listening to the game and still charging. Same thing, phone got extremely hot, 115°F. Although, what I find strange, is I can watch Netflix while charging and even tho it gets warm, it never gets above 115°F and never goes into the boot loop issue. Same exact location, charger, ambient temps, signal, the works. So I'm wondering if an app is just poorly written and causes some sort of excessive use of the radio.
On another note, I had a rezound battery in my thunderbolt and never had any issues what so ever with heat.
Sent from my ADR6425LVW using Tapatalk
What temperatures are you people expecting to see just out of curiousity? I mean if we run 3d intensive apps, videos, extreme web browsing we're going to see high temps since we are stressing the devices. We do have to remember these are compact devices and they are limited to what type of heatsinks/cooling they can add. From the multiple posts form this thread and others like it, we can see the majority of our devices run at same temps while under load. If it hasn't already been done maybe we should contact HTC and see what they say? Just a thought.
zetsumeikuro said:
What temperatures are you people expecting to see just out of curiousity? I mean if we run 3d intensive apps, videos, extreme web browsing we're going to see high temps since we are stressing the devices. We do have to remember these are compact devices and they are limited to what type of heatsinks/cooling they can add. From the multiple posts form this thread and others like it, we can see the majority of our devices run at same temps while under load. If it hasn't already been done maybe we should contact HTC and see what they say? Just a thought.
Click to expand...
Click to collapse
I am trying to find the norms and what is too hot.
I am thinking 115 is normal for heavy use. But we need to be sure, if someone says they only hit 100 under similar conditions as someone that hits 120. it may be that 120 is a problem temp and that 100 is normal. It may also be that the person only hitting 100 is just lucky.
tbot said:
I realize that you're trying to keep things as similar as possible, but I had an issue today listening to the broncos game in the NFL app while charging. It got so hot it boot looped. After getting it back up and running I started monitoring battery temps and even with the screen off and just listening to the game, it would get extremely hot. Btw, I have 4G 4 bars. A couple of times I ran to the freezer and put the phone in it for a couple minutes to cool it down as the temps got above 117°F.
From here, I thought it might be the CPU, so I set the maximum setting to 384 in antutu and then let the phone sit there with the screen off just as before listening to the game and still charging. Same thing, phone got extremely hot, 115°F. Although, what I find strange, is I can watch Netflix while charging and even tho it gets warm, it never gets above 115°F and never goes into the boot loop issue. Same exact location, charger, ambient temps, signal, the works. So I'm wondering if an app is just poorly written and causes some sort of excessive use of the radio.
On another note, I had a rezound battery in my thunderbolt and never had any issues what so ever with heat.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Go play an app that is heavy in 3D, lets see what temps you get. If you go much over 120 it may be an issue.
Running Gun Bros for about 20 minutes gets me up to about 105°F. Right now after the phone had been sitting for 5ish hours doing nothing its at 98°F.
Sent from my ADR6425LVW using Tapatalk
I think it is Ziggy's kernel I have never got 125f when tethering for 30min or playing GTA for 30 min. I am going to try another kernel.

Question about the governor/cpu frequency scaling

I've just done some undervolting and governor changes on my phone... (faux 012 kernel), build.prop added ro.ril.disable.power.collapse=0, pm.sleep_mode=1
On Powersave (where the CPU frequency is locked at the lowest 192mhz, I was able to hit 9mAh(reported by Battery Monitor Widget with HTC Sensation current detection option enabled) on idle with data on, sync on
Reported by the phone's built in stats:
30 min screen-on time, 1 hour phone on time, >12 hours deep sleep, my battery was just above 50%
of course, with frequency at 192mhz, there was major noticeable lag... one time, there was too much stuff running on the phone when it rang, and it couldn't work fast enough for me to answer the phone in time before bouncing to voicemail
lowest noted current usage before change - after change
deep sleep: 20mA | 9mA
screen on idle: 100mA | 60mA
9 hours usage before hitting 50% | >12 hours usage before hitting 50%
I've looked/used at the other available governors....
the interactive is next "power saving" efficient... clocks up from 192mhz somewhat slowly after some use, and goes back to 192mhz
the conservative is next... clocks up very fast from 192mhz use, slowly goes back to 192mhz
the ondemand clocks up faster and goes down slower
all of them clock up from 192mhz when the usage barely passes 50%
anyways... is there a way to customize my own needs? I want the phone on 192mhz until the CPU goes over 90% for 1s, then clocks up slowly... when a phone call comes in, i want it to use as much as it needs... etc
Maybe it's just me, but this phone is pretty fast/stable without missing with out volting
Sent from my HTC_Amaze_4G using xda app-developers app
Spastic909 said:
Maybe it's just me, but this phone is pretty fast/stable without missing with out volting
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I just want to be able to maximize battery life when I need(eg when I'm going out and I know I won't be near a phone charger for more than 20 hours, and still need the use of GPS/camera etc)
paperWastage said:
I've just done some undervolting and governor changes on my phone... (faux 012 kernel), build.prop added ro.ril.disable.power.collapse=0, pm.sleep_mode=1
On Powersave (where the CPU frequency is locked at the lowest 192mhz, I was able to hit 9mAh(reported by Battery Monitor Widget with HTC Sensation current detection option enabled) on idle with data on, sync on
Reported by the phone's built in stats:
30 min screen-on time, 1 hour phone on time, >12 hours deep sleep, my battery was just above 50%
of course, with frequency at 192mhz, there was major noticeable lag... one time, there was too much stuff running on the phone when it rang, and it couldn't work fast enough for me to answer the phone in time before bouncing to voicemail
lowest noted current usage before change - after change
deep sleep: 20mA | 9mA
screen on idle: 100mA | 60mA
9 hours usage before hitting 50% | >12 hours usage before hitting 50%
I've looked/used at the other available governors....
the interactive is next "power saving" efficient... clocks up from 192mhz somewhat slowly after some use, and goes back to 192mhz
the conservative is next... clocks up very fast from 192mhz use, slowly goes back to 192mhz
the ondemand clocks up faster and goes down slower
all of them clock up from 192mhz when the usage barely passes 50%
anyways... is there a way to customize my own needs? I want the phone on 192mhz until the CPU goes over 90% for 1s, then clocks up slowly... when a phone call comes in, i want it to use as much as it needs... etc
Click to expand...
Click to collapse
There are several other things you can do which may be more effective than what you are trying to do- or even more effective WITH what you are trying to do.
First, don't lower the minimum clock speed, 384 is the minimum that HTC chose, probably for multiple reasons. As long as your phone is going into deep sleep, it doesn't use ANY processor, and on any governor EXCEPT battery saver, it is VERY rarely idling at the minimum speed.
Next, look at the init.post_boot.sh and init.qcom.post_boot.sh files(you may have one, or you may have both, faux added the second one in later builds) in the system/etc folder, that sets many of the kernel settings. Do some research into how changing the line for "down_differential"(which is 5 stock, 1 increases battery A LOT, but increases lag a bit too), , "up_threshold"(stock is 90, setting to 95 increases battery, but takes longer to get to full clock speed), "sampling_down_factor"(stock is 4, you can lower to 1 for increased battery life, and slightly more lag), "sampling_rate"(latest faux changes to 30000, setting to 50000 means it checks whether to increase/decrease cpu speed less often, and gives better battery life).. changing those values will have much bigger impact on battery life, while adding a little bit of lag at most if you change them quite a bit. Also, look to see if you have a line that says "echo 1 > /sys/devices/system/cpu/cpu1/online", if you do, change it to a 0, 1 forces the second core on ALL the time instead of letting ICS decide when to turn it on.
Next, look at thermald.conf in the same folder, some of the biggest differences in battery life between roms is because of that file- faux replaces it with his later kernels, but I'm not sure if it is to increase battery life, or increase performance. His is definitely different than any rom I have seen, and people report much improved battery, and that file is likely why.
Doing all of these things with system files rather than with a 3rd party CPU app means the phone will deep sleep more, and be more responsive, because there is no app constantly running in the background trying to make changes on the fly. Also, you can find "battery saver" scripts that can be put into the above files that have their own tweaks you can make if you are determined to use that governor- but battery saver tries to constantly stay at the minimum speed possible(if you read it in some places, it simply stays at minimum speed PERIOD), and will have the most extreme lag, with a questionable amount of increased battery life compared to a tweaked on_demand governor.
And last, before undervolting, try decreasing the max speed of the core.. you can lower it by 1-2 steps and notice NO difference in speeds, yet get far better gains than undervolting, without creating instability. The volts that HTC chose are probably the very minimum that works well for all of our phones, as undervolting by 12.5 may work fine on my phone, but may introduce random reboots or worse on yours- once you undervolt you simply can't troubleshoot any issue on your phone, because the UV could be the cause instead of anything else..
There is more than that you can do also, like making sure that your screen-on and your actual usage numbers are almost EXACTLY the same- get an app like betterbatterystats(available free on XDA) to see what partial-wakelocks are keeping your phone from deep-sleep.. the higher the % of deep sleep, the less you have to worry about ANYTHING to do with the CPU, since the CPU isn't being used at all..
paperWastage said:
I just want to be able to maximize battery life when I need(eg when I'm going out and I know I won't be near a phone charger for more than 20 hours, and still need the use of GPS/camera etc)
Click to expand...
Click to collapse
If you do everything I said above to maximize battery on the on_demand governor, you can use a CPU app to change to battery saver governor when you know you won't be near a charger, and you just want basic functionality(no games, browser, etc), and DONT set on boot.. that way on reboot it defaults to normal governor.
I tweaked all the things I said above and get at LEAST 16+ hours with 3+ hours of screen on, and will get over 24 hours if I underclock to around 1.2ghz.. battery saver isn't even needed if you set everything else right.
Or you can buy 2 1900mah ankers and an external charger for 29.99 and free shipping on amazon, and simply carry the spare charged battery, and never care again.. much simpler fix if you ask me.
thanks for the tips Silentbtdeadly. I'll look at them this weekend
I am already using the Anker 1900mAh battery, with the latest faux kernel and energy stock ICS rom...
I get maybe 15 hours from 100% to 10% with ~1-2 hours of usage
From looking at BetterBatteryStats, it looks like the phone is falling into deep sleep properly with no obvious problems with wakelocks/alarms...
If I left my phone unplugged overnight with data on and autosync, it levels out.... lost 9% over 6 hours
I think I just have 2 main problems:
Drain from 100%->80% is fast after unplug... I think it takes 30 minutes to get to 90% and another 60 minutes to get to 80%. BBS shows phone in deep sleep, Battery Monitor Widget shows mA usage ~50mAh with -2%/hour, but the %-left slopes down a lot, since i did lose 20% in 90 minutes
when I turn on the phone and use it for <1 minute and put it back to sleep... Battery Monitor Widget shows a sharp drop in %-left even though BBS shows falling into deep sleep
I guess my problem might be the battery-monitoring hardware/firmware... I just received the Digital Timer, will try Bump Charging to see if I can get 16-20 hours with 3 hours of usage
paperWastage said:
thanks for the tips Silentbtdeadly. I'll look at them this weekend
I am already using the Anker 1900mAh battery, with the latest faux kernel and energy stock ICS rom...
I get maybe 15 hours from 100% to 10% with ~1-2 hours of usage
From looking at BetterBatteryStats, it looks like the phone is falling into deep sleep properly with no obvious problems with wakelocks/alarms...
If I left my phone unplugged overnight with data on and autosync, it levels out.... lost 9% over 6 hours
I think I just have 2 main problems:
Drain from 100%->80% is fast after unplug... I think it takes 30 minutes to get to 90% and another 60 minutes to get to 80%. BBS shows phone in deep sleep, Battery Monitor Widget shows mA usage ~50mAh with -2%/hour, but the %-left slopes down a lot, since i did lose 20% in 90 minutes
when I turn on the phone and use it for <1 minute and put it back to sleep... Battery Monitor Widget shows a sharp drop in %-left even though BBS shows falling into deep sleep
I guess my problem might be the battery-monitoring hardware/firmware... I just received the Digital Timer, will try Bump Charging to see if I can get 16-20 hours with 3 hours of usage
Click to expand...
Click to collapse
Careful with battery monitor widget, the way it polls the battery creates its own drain.. there is another widget called currentwidget that can actually log how much energy is being used by an app, it too can drain a lot, but it could show you if a certain app is using an absurd amount of power.. I have more info for it in the battery saver section of the bible in my signature.
I think about 16 hours with 2-4 hours of screen on is the most that can be gotten without seriously degrading the performance. If you set the governor options like I said in the last post and under clock a little, you will get a little lag on minor things, but the phone is still quite usable, and 24 hours is totally doable at those settings with 3-4 hours screen on.
Do realize the anker batteries aren't perfect, I bought two at once.. one gives me much more battery life than the other does even tho they were bought together, so that could be a factor too. I try to maximize battery life, but I'll carry a spare charged battery so I don't worry too much, it is the best solution thus far.
Sent from my HTC_Amaze_4G using xda app-developers app

What are your SetCPU settings?

What are your SetCPU settings on the Amaze? What do you consider optimal/suggest?
I pretty much need everyone's input before underclocking to preserve battery, cuz whenever I set it up, it lags my phone like crazy and my battery takes long to charge and still goes down pretty much the same speed. Using SpeedROM 6.5.
Instead of underclocking, you can simply undervolt instead, maintaining your current performance while reducing battery use.
sent from a galaxy you'll never see.
I think use 1.2Ghz is ok for me.It's also fast, but for me, I seldom play games
Mystery? said:
What are your SetCPU settings on the Amaze? What do you consider optimal/suggest?
I pretty much need everyone's input before underclocking to preserve battery, cuz whenever I set it up, it lags my phone like crazy and my battery takes long to charge and still goes down pretty much the same speed. Using SpeedROM 6.5.
Click to expand...
Click to collapse
3rd party cpu apps aren't even needed, you can control more just by changing a few things in a few system files. I gave pretty good details here http://forum.xda-developers.com/showpost.php?p=30298629&postcount=4
You CAN undervolt, but if you have any issues, it could be undervolt related.. system tuner is better for undervolt, I actually don't like setcpu anymore at all.
If you ARE determined to use setcpu, don't use the profiles part- like cpu speed on screen off, etc.. it hurts more than it helps.
But not using a cpu app means you don't have yet ANOTHER app running on the phone constantly, eating ram, slowing things down.. my 2 cents.

[Mega-Guide][14/01/14] Get a (Battery) Life! Every possible way to save your battery.

Links pointing to androidbatterylife.com are DOWN FOR GOOD!
Android Battery Life, a pretty successful website has been made in order to help android users achieve better battery life while still using many functions and apps. All of these guides are available, with screenshots, at www.androidbatterylife.com
It's my 2000th post here on xda, and I wanna make it special
PORTAL! http://www.xda-developers.com/android/battery-saving-mega-guide-celebrating-users-2000th-post/
A lot of users are thinking that everything mentioned should be applied. You don't have to apply all of them, just apply what you think works for you. This is more of an index of guides, if you will.
Yes, this is in the Android Q&A, Help & Troubleshooting because of the word "Troubleshooting"... I'm shooting your "Low battery life" trouble in the face.
So let's begin:
The guide is split into 3 parts: Easy, Medium, and Advanced.
First up is... you guessed it..
Easy​
Screen / Display LINK
If you go to Settings>Battery, you’ll clearly see that “Screen” has the biggest bar of about 40-60%. The bigger the bar (and the number), the bigger the battery drain. We’ll try to lower that bar as much as we can.
Brightness
First of all, to reduce the battery drain caused by the display, click on the Screen button, then click display (it’s the same as going to Settings>Display), then click on brightness, untick Auto-Brightness if it’s ticked and lower the brightness to minimum.
Explanation: A brighter screen means the screen is emitting more light, which consumes more battery. So lowering the brightness makes the screen use less battery juice.
Wallpaper
Second thing to do to reduce the “Screen” battery consumption is having a Static Wallpaper, and not a Live Wallpaper. So go to Settings>Display and click Wallpaper, and pick any wallpaper you want except the wallpapers from the Live Wallpapers list.
Explanation: Live Wallpapers use the CPU (and possibly the GPU) to make the image move. So the phone is using the CPU to process these images, which means more battery sucking, and we don’t want that.
Sleep
Again, go to Settings>Display, and click Sleep (aka screen timeout) and set that to something less than 1 minute. I personally use 30 seconds and it’s good enough for day-to-day use.
Explanation: The more time the screen is on, the higher is the battery usage, because the screen won’t be using the battery when it’s off…
Framework Animation
Fourth thing to do is disable the Framework Animations. Framework Animations are the animations you see when you switch from an app to another app, or when you press home, or back, or recent apps buttons. To turn those off go to Settings>Developer options (if you don’t see that, then go to About Phone and press the Build Number button 8 times, then go back), scroll down to drawing section, and set Window animation scale, Transition animation scale, and Animator duration scale to “Animation off”.
Explanation: Framework Animations use the GPU (and possibly the CPU) to draw the frames of the animations, so by turning them off, you’re pulling some load off of the GPU and CPU to make the battery life better.
Widgets
Believe it or not, widgets can greatly affect battery life, it's because they update themselves regularly. This can wake up the phone a lot of times. So the best way to prevent this is to remove all the widgets on the homescreen.... and maybe keep the ones that don't update themselves much.
Remember, everything that’s shown on-screen that isn't app related is registered as “Screen” in the battery window. So to lower that, you have to compromise every little thing that’s shown on the screen.
Click to expand...
Click to collapse
Google Services LINK
One major issue you may face with Google Services is the location battery drain. This was born in Android 4.2.2 and can be easily fixed by just unticking a button.
Problem
The real problem is, in one word, Location.
Google Services such as Gmail, Now, Maps, and Google+ constantly polls your location using your wifi (if you're connected) or your cell network. And every time Google Services poll your location, your battery gets affected. So what's the solution to that?
Solution
Further research by Galaxo60 proved that going to Settings - Location Settings (or Location on android 4.4), and unticking WiFi & mobile network location (or setting the Mode to Device Only) prevents Google Services from polling your location, thus preventing the battery drain
So disable the WiFi & mobile network location option, and actually tick and turn on GPS satellites. (It's just like setting the Mode to Device only on KitKat)
But why do that? Why should I turn on GPS?
Picture taken using Android 4.4 KitKat
Explanation
Google Services don't use your GPS to poll your location, so your GPS actually stays offline most of the time; and the reason you should enable GPS is to "Let apps that have asked your permission use your location information".
Click to expand...
Click to collapse
Go Dark LINK
Some devices have AMOLED or SAMOLED (Super-AMOLED) screens, like the Samsung Galaxy SII and the Motorola Moto X. The following method is helpful for these kind of devices.
You may check what's your screen type to see if it's AMOLED or not. If it's not, this method won't help you achieve better battery life, but may help your eyes
What's AMOLED?
AMOLED is a screen type designed to get the highest contrast a screen can get to. Black pixels turn themselves off, unlike the IPS screens that always require a backlight. So AMOLED has less battery consumption than most screen types.
What to do?
Try turning everything as dark as you can. So make the wallpaper have as much black areas as possible, and use dark apps. The best way to convert most apps to dark apps is downloading Team Black Out Updater. From that app, download the apps you want to make them darker and install them. Some apps require having root because you have to flash them via recovery.
This consumes less power
This consumes more power
Explanation
By turning most things dark/black, more pixels in the AMOLED screen will turn off, thus lowering the power consumption caused by the screen.
Remember, this is only for AMOLED screens, IPS/LCD screens will still consume the same power from the battery.
Click to expand...
Click to collapse
Turn Off Auto-Sync LINK
Auto-Sync constantly checks the data on the phone and the data on the cloud, and adds the missing files. In other words, Auto-Sync = wasted battery.
Turn off Auto-Sync
Go to settings, scroll down to you google account, tap it and tap on your gmail. Then uncheck all the items on the list.
This is wrong. Now untick them!
Explanation
Auto-Sync consumes a lot of data and battery. By unchecking the items, Auto-Sync will turn off, and thus saving battery AND data!
Click to expand...
Click to collapse
Turn Off NFC LINK
NFC is wireless, and wireless consumes battery. So turning off NFC will make the battery life slightly better.
NFC off when not needed
If you don't use NFC, go to settings > more > and turn it off. Android beam will grey out because it needs NFC, we don't need that either.
Explanation
NFC consumes a lot of battery if you keep your screen on most of the time. So by turning it off, we're improving battery life while the screen is on.
Click to expand...
Click to collapse
NO Task managers/Hibernators LINK
Yes... I know... Weird right? Don't be misguided, and understand what's happening inside android before doing anything.
Uninstall / Disable Task Managers / Killers / Hibernators
If you have any Task killer, or Task manager apps installed, either disable them if you can, or uninstall them.
Explanation
Android learns the way you use it. It knows which apps you like best and pre-opens them and puts them in RAM so that they get opened faster. Android keeps a log of how much time you've been spending on an app.
By using a Task killer, you're breaking this log, thus preventing Android from learning how you use it. The results?
Android will be loading every app you open from scratch.
Android will get slower.
Android will be wasting battery.
So uninstall those "battery killers" and let Android do the work instead.
Click to expand...
Click to collapse
Use ART LINK
Yes... ART... Not art, but ART... It's an Android 4.4 KitKat specific thing...
What is ART?
ART is a runtime replacement of the Dalvik runtime. It's the way the phone handles apps. Dalvik used to install apps fast, and conserve some space after the installation, but it compiles the app as soon as you open it, and runs it on a Virtual Machine (if it's not a native app).
ART pre-compiles the app on installation, which takes up a little bit (teeny tiny) more space, but makes apps faster to open, and over all performance better.
Switch to ART
Go to settings, developer options, and tap on select runtime, then use ART and reboot. It'll take some time to finish booting the first time it's running ART, but when it's done optimizing apps it'll be worth the wait.
Explanation
ART demands less CPU power to process things over time. It pre-compiles apps just once so that when you open an app, the CPU won't work as much to compile the app just-in-time (JIT). So, less CPU work, less battery consumption, more battery juice, and more performance!
Click to expand...
Click to collapse
Pick the correct charger LINK
I can't put direct links to chargers, so go HERE to the relevant page and see the chargers from there.
Is a fast charger better? or is it the slow one?
Use the Right Charger
A slow charger relaxes the battery, making it last longer when it fully charges. So, for a better battery life, use a slow charger at night when you're sleeping, or when you don't need to charge it quickly.
I recommend using this charger*: it's small, looks good, and it's slow with a 1A power output... Perfect for what we want.
If you're in a hurry, and your phone's battery has little juice left, you may want to charge it pretty quickly. In this situation, you won't care about the relaxation of the battery, so you should use a fast charger.
Something like this charger* should help a lot in achieving what you need. It also has a second slot it you have to charge another device. Use the A slot to charge faster with its 2.4A power.
You can also use a car charger if your phone's battery suddenly dies while you're not home.
This car charger* is perfect because it's fast enough to revive your phone and gives you enough juice to save the day.
So be wise and use the right charger for the right situation, so that you can achieve the best battery life possible.
Click to expand...
Click to collapse
Have a Spare Battery / Power Bank LINK
Sometimes, your battery will die, whatever you do...
Have a Spare Battery
In that case, if you have a phone with removable battery like any current Samsung device, equipping another spare battery could be very useful. If your battery is almost dead, just turn off the phone, open it up, and put your spare battery in. Voila, insta-charge
Have a Battery Bank
One great gadget to own with your phone is a backup power bank. This portable power bank (see link of the page HERE) is awesome because it's universal, and has a 13000 mAh capacity which can charge your phone about 5 times!
So if you don't want to scratch your head to do tweaks, you can use spare batteries or power banks to save the day
Click to expand...
Click to collapse
Know How to Use Android LINK
It's all about how you use it...
We see a lot of users that use Android the wrong way. We see people setting their screen timeout to 30 minutes because "whenever I want to chat, the screen keeps turning off". We also see a lot of users, even devs and power users, constantly pressing the back button to go home.
Know How to Use Android
If you have the screen problem where whenever you want to interact with the screen, it turns off, don't turn the screen timeout up. Turn it down, so that the screen turns off sooner, and saves battery.
And to go home, there's a button for that for a reason! Use it! Pressing back over and over again closes the app, and clears it from your device's RAM. When you re-open the app, it will open from scratch, so your phone will be slower, and will consume more battery since it's using more CPU power.
So use the home button, try to keep as much apps in RAM as possible, stop "clearing all" apps from RAM, and save battery!
Explanation
RAM, either full or empty, consumes the same amount of electricity, unlike RAM in computers.
The CPU copies data from storage to RAM and then runs the app. If the app is already in RAM, the CPU won't reopen it, it'll directly use it.
So making the RAM full of opened apps helps the CPU. The phone becomes faster, and the need of electricity running through the CPU to open the app is now nonexistent.
Also, Android keeps a log of how you use your phone and pre-opens the apps you need. If you constantly kill and clear out apps, you're breaking that log. So when clearing apps, you're not letting Android learn the way you use it. This results in a slower experience, and more battery drain.
Click to expand...
Click to collapse
Deactivate Auto-Rotate LINK
Auto Rotation isn't always needed... right?
Disable Auto Rotation
Go to Settings, Display, Rotation, and turn off Auto-rotate.
Explanation
Auto-rotate uses the phone's G-Sensor to see how you're holding the phone. By turning off Auto Rotation, you're using less hardware, thus using less battery
Click to expand...
Click to collapse
Turn on Airplane Mode LINK
When in low signal places, it's a hassle trying to find that precious signal...
Turn on Airplane Mode
Whenever you feel that the mobile signal is getting too low, turn on airplane mode if you don't need to call someone. Go to settings, More, and check Airplane mode to turn it on.
Explanation
The phone wants you to stay connected to a cell tower whenever possible. On low signal places, the phone will try harder to find a tower to connect to, and that drain a lot of battery. So turning on Airplane Mode makes your phone rest and not search for any tower, thus saving battery.
Click to expand...
Click to collapse
Use a Light Theme for LCD Screens LINK
AMOLED will consume less battery on the dark theme, LCD isn't affected by that...
Use a Light Theme for LCD
Using a lighter theme with more white in it helps your eyes, because you can lower the brightness even more and still see the screen just fine.
Explanation
The lower the brightness, the better the battery life. So a lighter theme is what we want, so we can reduce the brightness and still see everything.
Click to expand...
Click to collapse
Charge You Battery Correctly LINK
It's called a battery cycle, not a quarter of it
Charge it correctly
Don't let your battery go down to 0%, charge it while it's about 50%.
Explanation
No matter what charger you're using (either a slow or a fast one), the battery is greatly affected by the frequency of the charges. Our phones have different batteries than past devices had, so battery life cycles are a bit different as we used to think.
More info here: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Click to expand...
Click to collapse
Use Widgets with Manual Refresh LINK
Widgets update themselves a lot... but there's a solution for that.
Use Manual Refreshed Widgets
Check every widget you have, and see whether you can set it to refresh whenever you click on it, or do something to refresh it.
Explanation
Auto-refreshing widgets make the phone wake up a lot and do some processing which can use the battery. By making them manual, you are controlling the frequency of the refreshes, and you are forbidding the widgets to refresh while the phone is asleep.
Click to expand...
Click to collapse
Do Not Rely On Battery Discharge Rate LINK
Look! Left it overnight and only lost 2%! This is about 0.25%/hr!
WRONG!
The battery acts like a capacitor (not exactly like it, but very similar to it), so whenever its charge is changed, the discharge / charge rate will change with it.
So, if you leave your phone overnight at 100%, you'll get a rate of x%/hr. If you leave it at 50%, you'll get a rate of y%/hr where x and y are very different.
It's only a matter of experimenting where is the sweet spot of battery percentage that you should have when keeping it overnight.
Click to expand...
Click to collapse
Do Not Wipe Battery Stats LINK
Some people do that a lot... but why?
What's Battery Stats?
Battery stats is basically a file in Android that stores the battery history. The longer the battery stats is, the more accurate the battery percentage reading is.
Why not wipe it?
Wiping battery stats is like tinkering with the fuel gauge in your car: you won't get more gas if you glue the gauge's needle at Full.
The problem is that wiping battery stats will give you wrong readings. Users thought that wiping it will make the battery "hold the charge better". This is wrong because doing so will break Android's battery reading, and that's why it will show you a higher percentage for a longer time.
Click to expand...
Click to collapse
Do Not Buy Cheap Batteries LINK
Wow! A 2500 mAh battery for my Galaxy Ace! And the same size of the original!
The problem here is that some users order a battery with a higher mAh value for a very low price. They get their 2500 mAh battery and put it in the phone. The device would last a lot longer now before its battery dies.
Now let's not forget why they ordered such a battery. It's most probably because their old battery is just exhausted and isn't lasting much. So no matter what battery they get, they'll notice a big difference in battery life.
Usually these cheap batteries are advertised as 2500 mAh, while they're actually a lot less.
So if you want to replace your old battery, try getting an original one.
Click to expand...
Click to collapse
Thanks to all of you who gave me more ideas on how to achieve better battery life
Medium​
Undervolt LINK
The CPU is the biggest battery consumer, and it needs voltage from the battery. If we decrease that, we'll gain some battery life.
Undervolt your CPU
Assuming you have TricksterMOD, launch it and go to the specific window. Scroll down to CPU Voltages, then click Profile, and save the Profile as Default.
Now hit the minus/plus button right above where it now says "Default". When the window pops up, hit the minus button JUST ONCE. Every time you hit the minus button you undervolt by 12500 mV, and we'll call that a "step"; so undervolt by one step.
Hit the check mark button to apply.
Explanation
Every time you undervolt by a step, the CPU will demand less and less from the battery to run. This improves the battery by just a bit. It's mainly to avoid temperature throttling, but it also improves battery.
Click to expand...
Click to collapse
Increasing SD card Read-Ahead Value LINK
Whether or not you have an SD card, this helps...
Increase readahead Value
Go to TricksterMOD, swipe to general, and click Read Ahead Buffer Size under the I/O Control section. Set it to 3072 (Value is in KB, so it's 3MB)
Explanation
The bigger the read-ahead buffer is, the better the SDcard can predict what command would come next. It prepares itself to do a command before it's even issued. This gives you better performance, and a potential increase of battery life because generating 3MB is nothing compared to the performance benefit.
Check out this Spreadsheet from broodplank.net for more info on the benefits of read-ahead.
Click to expand...
Click to collapse
Advanced​
Underclocking LINK
One major battery drainer is the CPU, so if you don't really use the phone much, and you don't care about games, you should probably consider underclocking it to get that precious juice back.
Requirements
You must be rooted and have a kernel that supports overclocking. You may find out how to root by doing a little online research because every device has its own rooting method (for example, I wrote a fully detailed guide on how to root your Nexus 4).
CPU Underclocking
Warning: Underclocking the CPU too much could result in an SOD (Sleep Of Death) which makes the phone sleep and not turn on without pulling the battery.
First of all, we need a controller, or a daemon to control the CPU's clock speeds. So go ahead and download TricksterMOD from the Play store, we'll be using that to underclock the CPU.
Now enter it and grant su permissions, swipe from left to right and select the general menu, scroll down to CPU frequency control and tick frequency lock, then click on the number next to the min button, and choose the smallest number in the list.
Then, click on the number next to the max button and choose something a little less than you CPU's stock frequency... on a Nexus 4, the stock frequency is 1.5 GHz (or 1512000) so I picked 1.2 GHz (or 1242000).
Now swipe down to CPU Governor Control and click the button next to the Governor Button, and select conservative. If you don't have conservative in the list, pick ondemand. Now hit the check mark button at the top of the app to apply the settings.
Explanation
We are lowering the CPU's clock speed which makes it a little slower, but consumes much less battery. We are also changing the way the frequencies are handled: with the conservative governor, the CPU will prefer staying at lower frequencies.
MP Decision
We're not done yet, swipe again from left to right and click specific, then look for MP Decision. If it's there, turn it off, if not then it's probably already off. Hit the check mark to apply the settings.
Explanation
MP Decision sees how you use the phone, and clocks the CPU relatively (if you're just chatting, it'll underclock. If you're playing games, it'll clock it to normal). We don't want that since we want to force underclock the CPU, so we turn this off to prevent it from playing with our settings.
GPU Underclocking
On that same screen, scroll down to GPU max frequency, and lower that just one step below the default clockspeed (400 MHz being the stock frequency on the Nexus 4, so let's set that to 320 MHz). Don't forget to hit the check mark button to apply the changes you've made.
Explanation
The GPU draws almost everything you see on the screen, so it's always active. Lowering its frequency has a big positive impact on battery life, which is what we want.
So that's basically it for the underclocking part, have fun playing with different governors and frequencies to get that precious Performance/Battery life point.
Click to expand...
Click to collapse
Detecting Wakelocks VS Installing Battery Saving Apps LINK
The most cliche thing to do when your battery doesn't last a day is install a battery saver app. However, I don't do it myself. I prefer detecting wakelocks in order to reduce battery consumption.
What is a Wakelock?
A wakelock is the moment where you turn the screen off, but the CPU stays awake doing something. It is the phenomenon when the CPU isn't asleep when the screen is off and it shouldn't be doing anything. Wakelocks usually drain battery because the CPU is kept awake and working while it should be resting.
Detecting a Wakelock
To detect a wakelock, install Wakelock Detector. Charge your phone, then unplug it and leave it with the screen turned off for about an hour or two. Then open the app and check the list of wakelocks.
The bigger the red bar on the top, the longer the wakelocks are. The top app is the number 1 culprit, and should be removed. If the top app is Google Services, it's probably the Location issue. If it's another app, check if there are syncing issues, and try making the sync interval a little longer, or turn off its notifications.
Explanation
We're trying to minimize the wakelocks caused by some apps to prevent the phone from being awakened. By doing that, we let the phone go to deep sleep faster, and longer. So, more battery life for us!
Another way to detect wakelocks (a little more pro)
Download and install betterbatterystats. It's basically a more pro version of Wakelock Detector. It also needs root for some functionality to work, but it gives you a more in-depth info about the wakelocks, CPU states, and network usage.
msm_hsic_host is the 3G... not to worry about that
So that's it for the wakelocks! Keep testing with different app configurations to achieve the best deep sleep mode for your phone, and get the most out of your battery.
Click to expand...
Click to collapse
Undervolt Even More! LINK
Undervolting once is fine. Undervolting twice is better. But undervolting a million times isn't good... So let's undervolt as much as we can.
Download Stability Test, run it, and hit the Scaling Stability Test button (root will be needed). Wait about 8 to 10 minutes while it's doing the process. If it doesn't crash, stop it by pressing the back button. Your phone is stable, you can undervolt even more.
So go to TricksterMOD and undervolt another step (remember to save a profile indicating how many steps you've undervolted). Then test again using stability test....
Keep doing that until something bad happens like the app crashing, or Android itself rebooting. When it does crash, "overvolt" back one step. At this point your CPU is running good while on the lowest voltage.
Explanation
Every time we undervolt by a step, we test the stability of the CPU so it doesn't crash. When it crashes, we overvolt back to the last voltage set that was stable, so that we get the lowest voltages our CPU can handle without going crazy, and thus, getting that slight push of the battery life.
Click to expand...
Click to collapse
Tweak Kernel Governors / Schedulers / KSM LINK
These tweaks only apply to certain kernels, since not all kernels allow you to modify these settings.
Governor, Schedulers, and KSM Tweaks
If you have a kernel tweaking app like tricksterMOD or faux clock, you are 90% free of all trouble of tweaking kernel governors.
First, find a kernel that has a specific and optimized governor. Turn off MPDecision if the kernel has an alternative (anything like "Intelli-Plug" will do). Now let's tweak!
We cannot cover the options for every kernel and every governor in the universe since each one has its own options and settings.
I am currently using faux kernel on my device. This kernel has intellidemand as the optimized governor. The aim of the kernel dev was to replace MPDecision with something better.
The links below provide some info about that kernel. These settings include tweaking the governor, schedulers and the KSM:
http://forum.xda-developers.com/nex...ernel-ver-031-mako-kk-4-4-uv-otg-cpu-t2008222 (the second post shows the recommended settings for faux kernel)
https://plus.google.com/+PaulReioux/posts/WFcjPqMEZgJ
Have fun tweaking!
Click to expand...
Click to collapse
Great guide, and great usage of your 2000th post! I've featured this on the XDA Portal
Great post!
I like using Screebl to prevent screen turning off and on unnecessarily. And use One Power Guard by onexuan. It really lessens the drain over night. I use Condi to automatically disable mobile data when connected to wifi at home as well.
very great guide! Just note something for people with HTC Sense. If you use the weather clock with current sensor, setting the location to GPS only will disable the location service (even if it's seems on, the widget will say it's off since it doesn't want to use the GPS). Because of that, you loose that feature if you do that.
Um, there's a problem with this guide. Instead of underclocking, overclock the processor. The faster the processor, the faster it gets jobs done, the faster it can go to sleep. These reduces long wakelocks and in general improves battery life.
I used to think the same way, but thinking that way is false.
What about Greenify?
idk about you, but greenify is useful.
EDIT: And for the fast charge/slow charge, do you have any proof?
Beatsleigher said:
Um, there's a problem with this guide. Instead of underclocking, overclock the processor. The faster the processor, the faster it gets jobs done, the faster it can go to sleep. These reduces long wakelocks and in general battery life.
I used to think the same way, but thinking that way is false.
Click to expand...
Click to collapse
So you're saying that it's better not to underclock and just use default values?
Hmm kind of skeptical about the home button thing. I usually back out of an app to prevent it from running in the background and consuming battery. Can anyone comment on this?
fredrick1213 said:
Hmm kind of skeptical about the home button thing. I usually back out of an app to prevent it from running in the background and consuming battery. Can anyone comment on this?
Click to expand...
Click to collapse
the fact that the app opens from scratch again makes the CPU work more and thus using more battery
if it's kept in the RAM, it'll stay paused, it won't use the CPU and makes your phone faster sincr it resumes the app, thus making your battery usage less.
Sent from my Nexus 4
Riro Zizo said:
the fact that the app opens from scratch again makes the CPU work more and thus using more battery
if it's kept in the RAM, it'll stay paused, it won't use the CPU and makes your phone faster sincr it resumes the app, thus making your battery usage less.
Sent from my Nexus 4
Click to expand...
Click to collapse
So if using Greenify, which automatically hibernates apps and greatly increases my battery life btw, will it make pressing the home button useless?
Beatsleigher said:
Um, there's a problem with this guide. Instead of underclocking, overclock the processor. The faster the processor, the faster it gets jobs done, the faster it can go to sleep. These reduces long wakelocks and in general improves battery life.
I used to think the same way, but thinking that way is false.
Click to expand...
Click to collapse
you have a point if the user is a heavy user. But for normal users, the CPU won't be doing much; so underclocking it won't affect time, but it greatly improves battery life.
steakhutzeee said:
What about Greenify?
Click to expand...
Click to collapse
pham818 said:
idk about you, but greenify is useful.
EDIT: And for the fast charge/slow charge, do you have any proof?
Click to expand...
Click to collapse
greenify freezes the app if you're not using it, so the phone will start it from scratch... it's a good app if you use it on apps that you barely use, but don't greenify the apps that you use frequently, it will badly affect your battery life.
as for the fast/slow charge, I have no proof since this is what i usually have as a personal experience, but i find out that my battery lasts longer when i charge it slower...
Sent from my Nexus 4
fredrick1213 said:
So if using Greenify, which automatically hibernates apps and greatly increases my battery life btw, will it make pressing the home button useless?
Click to expand...
Click to collapse
if for example you greenify whatsapp, and you press home while you were inside whatsapp... yes... it's useless...
but try building the habit of pressing it, the back button kills the apps, we don't want that
Sent from my Nexus 4
i always clear all my apps before i put the phone to sleep.
i'll try to not clear apps anymore, and see how that works.
thanks
pham818 said:
i always clear all my apps before i put the phone to sleep.
i'll try to not clear apps anymore, and see how that works.
thanks
Click to expand...
Click to collapse
ah, you see, here's where it does make the good difference, keep doing that because you won't use the apps for about 8 hours, so it's better if they're closed.
i just posted this because i see people constantly closong the apps that they always use, but if you're not using the apps much (like when sleeping) it's better to kill them
Sent from my Nexus 4
Great post, love all of the tips. Keep up the good work. I hope to see 2000 more posts to come.
aguilar8788 said:
Great post, love all of the tips. Keep up the good work. I hope to see 2000 more posts to come.
Click to expand...
Click to collapse
oh you will, trust me
every 1k posts I'll make something very special.
my 1000th post was releasing 2 very annoying apps that the portal newswriters denied them for being too annoying
Sent from my Nexus 4
First of all thanks! battery life is a never ending issue in any smartphone using the no animations, less widgets and device only location... hope it'll prove useful
I got a question... I use go power master which has a "screen off optimization" and i noticed that my battery barely drains itself while the phone is idle... it's not what you count as a task killer right?

*TRICK* The Proper Way To Obtain Peak Battery Life!

So I have been testing the LG Optimus G E970 AT&T for quite some time now.
What I found is stock, non-stock, custom kernel, stock kernel, custom rom is it doesn't matter what choice is made, Battery life sucks. Wouldn't you guys much prefer a couple days compared to a half a day?
The absolute best way to obtain good performance at least acceptable performance and get days and days of battery life is simple. Primarily it has to be Cyanogenmod 10.2.0 Official Stable Release on stock kernel.
Cyanogenmod 10.2.0 by stock though gets about 15 hours as stock does. Though there is a couple cool things to do to get insane battery life. First is proper calibration by draining to absolutely dead. In terms of Android auto-shutdown, then boot up to recovery screen or bootloader. Let it sit on the bootloader until it's dead as a door nail. Prepare for a device which may not turn on with or without power period. It would appear bricked/ dead, however its far from that. This is a force calibrate procedure and if it doesn't power on or respond to power after that it's clear the battery is heavily damaged from improper charging. I had to remove the nano screws on bottom, and nano screws holding the battery ribbon connector. Which I left the screws out for easy quick battery access in the future. I had to disconnect the battery ribbon, then plug in power and watch it start up to lightning bolt charging mode. I then unplugged and plugged in the battery ribbon. This time it started charging from absolute 0%. I charged it from absolute 0% to 100% without stop. It will then be properly calibrated and will stay that way as long as you charge appropriately when it dies or gets below 5%.
You must leave developer options disabled as well as it'll force interactive as governor. Range by stock 384-1512mhz. You will need two apps one is DS Battery Saver and set it to Slumberer, and in options settings deepsleep uncheck check background data and battery triggers to ignore. This alone will force 24-36 hours with full 1.5ghz performance but will lose 25% per hour heavy use as normal.
Next step will be download MULTICORE CPU CONTROL FREE. Set Core 1,2,3 to always disabled and set Core 0 to max 702Mhz via custom profile select profile save.
The difference between running on a single core at 702mhz vs all 4 at 1512mhz is a delay in milliseconds.
1512mhz on all cores give less than 100ms delay of response and gives horrible battery life while in heavy use. It will lose a couple percent per minute while in use.
702mhz on one core gives roughly 750-1750ms delay response. That means it is 17.5 times slower though the battery life is insane! Even my mind runs fast and I can deal with that delay no problem, even with how picky I am about snappyness.
Now on every boot you pretty much need to go to the profile edit and re-save if you set auto apply on boot up it'll still ignore it. So edit profile save on each boot and check time spent in states to make sure only core 0 is active 100% of the time and at 702mhz max.
So far I have achieved 1% loss per hour while in heavy use. Which should in theory approach and exceed 99 hours on battery without charge. However realistically it'll achieve now more than a day and could last closer to a week when idle!!!
Anyway Good Luck Guys!
whoa what? can you tell me your findings thus far?
optimisandroid said:
whoa what? can you tell me your findings thus far?
Click to expand...
Click to collapse
The CPU Profile disabling cores does improve battery life but I just got sick of messing with the app. Developers should create an AROMA Kernel installer to do just this without toying with it every boot.
So far though I'm getting no less than 48 hours out of it now... Not bad but I'm gonna buy a new phone anyway the in call volume is horrible and clarity of both ends is horrendous.
So I'm gonna buy a Galaxy Note 1 or 2 probably one because it's less than $100. Note 2 is like $125 but I'll be okay with a dual core for $90 and 5.3" Screen. It's also the Mass Storage will be way better. The E970 hates my SD card it doesn't like it not one bit plus the Storage Configuration on E970 is straight up stupid.

Categories

Resources