Related
I have a Thunderbolt running Das BAMF Remix 1.6.3 and Imo's 2.7.0 kernel (I have tried going between Batt Saver/Normal, and now I am on Extreme). I adjusted my brightness of my display to about 20% (instead of automatic), and when I am home I try to be on my Wi-Fi. For some reason, I am not getting a full day's charge out of my Thunderbolt (when I first got the extended battery, I was getting at least 32 hours). I read about people's batteries and I feel people with the stock battery are getting more/equal amount as I am with an extended battery. I tried running Normal setting on Imo's kernel at one point and I did not even last 12 hours, and I was on 3G doing only minimal texting. I tried Batt Saver, and the first day I used it, it was really good (about 10 hours and I was down to 75%, but until I got to 18% or so and then within 3 minutes it was dead, which was weird). But the following day it was not as good as it was, and it died again less than a day. I even tried the Das BAMF kernels and they have similar results. I am also trying to switch between InteractiveX/SmartAss/OndemandX, but I am not seeing too much of a difference (unless someone can give hints on which is supposed to lend to a longer lasting battery). Any advice would be appreciated! (And if you need more specs on my phone, let me know... I generally only text, I do not play games or do very intensive internet things).
I have found the best battery life on bamf stripped v1.1, I get better battery life on that than any other Rom I've tried including stripped v1.7 and all the other bamf versions. I'm running the 4.4.6 kernel, I haven't tried the batt saver kernel from Imoseyon yet. I get 2-3x's the battery life as stock and almost twice the battery life as any other bamf Rom
There are lots of things to consider about your battery life. If you look at your batter use on your phone does it show anything that might be suspiciously draining battery more than normal? If you're using Imo's kernel you can type "12" into the terminal when you are changing governors to see the stats of how long your phone is staying at different frequencies, does it show a high amount of time spent at the higher frequencies? How long does your phones display stay on for?
There are so many things that can drain the battery its ridiculous and randomly I will have severe drains at times that are only solved by a reboot.
eraursls1984, do you have an extended battery? How much battery life are you getting?
Beastclaw, battery use seems normal - nothing out of the ordinary or suspicious is really eating at my battery. As I said before, I am currently running InteractiveX and at Extreme mode, and these are my states at different frequencies:
245760: 2102206
368640: 409810
768000: 58113
1024000: 263351
1222400: 12737
1408000: 72575
1593600: 0
1766400: 0
1920000: 0
Seems that nothing is really running too much on high frequencies, mainly on the lower end. My phone display is supposed to stay on for, I believe, 2 minutes, but whenever I am doing using it, I always lock it.
I heard Autostarts was a good app that could help with battery life and performance (and I was warned to not change any system settings), but I am trying to see if maybe there is anything else I can do to figure out why my battery seems to not last as long as other batteries.
You can try using an app from the market called "CurrentWidget" It allows you to log how much power your phone is using at different intervals of time. My phone generally runs at 40-60mA when the screen is off and its not doing anything and between 400-600mA when the screen is on and I am running tasks. You can use the log to check to make sure your phone isnt drawing too much power in the down state. It even shows you the stats in a nifty little graph form
Aup808 said:
eraursls1984, do you have an extended battery? How much battery life are you getting?.
Click to expand...
Click to collapse
I have a stock battery and with normal use I get 12-14 hours compared to about 4 when I was completely stock. When I use my phone heavily, constant browsing, I get about 4 hours compared to less than 2 stock. I always have my brightness all the way up except for when I'm in bed because this screen is not bright at all compared to my old phones. Unless you just have to have sense (which to me makes no sense, lol) then I would recommend trying bamf stripped v1.1. I am also not overclocked, I noticed a little increase in performance but not enough to justify the loss of some battery life., however I was going to experiment with it again since I haven't tested the performance and battery life of stripped v1.1 overclocked.
I mean, I have BAMF Remix 1.6.3, which I guess has Sense elements since I do not have BAMF Stripped? I mean, I do not think I use any Sense features or anything like that, so I have no reason not to get BAMF Stripped if it helps increase performance/battery life. Yeah, on Remix 1.6.3 and Imo's kernel at Normal, I had 12 hours on my extended battery... Haha.
Bump - does anyone have Autostarts? Or any other program/app that will help with the battery life, or any other suggestions? I will test the CurrentWidget app tomorrow when I am actually up and using my phone and see if I get similar results or if I find another program is using up my memory... I also recently installed Advanced Task Killer today to help with this battery problem, but I heard mixed things about using it and how it can actually negatively impact the phone instead of helping.
Aup808 said:
Bump - does anyone have Autostarts? Or any other program/app that will help with the battery life, or any other suggestions? I will test the CurrentWidget app tomorrow when I am actually up and using my phone and see if I get similar results or if I find another program is using up my memory... I also recently installed Advanced Task Killer today to help with this battery problem, but I heard mixed things about using it and how it can actually negatively impact the phone instead of helping.
Click to expand...
Click to collapse
Before 2.2 they were useful on some phones if used right, but its not needed nor does it work on the thunderbolt. If its set to autokill then it will drain the battery faster by running and killing apps, then the phone using juice to reopen the apps that were killed. If you root you can use autokiller (not a task killer) to set parameters for ram memory but I haven't found it to be necessary on the t-bolt, it was needed on my old droid X to keep it from lagging. I would suggest uninstalling the task killer.
Took your advice and uninstalled the task killer - thanks! Anyone else have any other suggestions or advice about my battery problem?
Autostarts is definitely worth $1. If you are familiar with Windows, it's kinda like msconfig for android. It prevents nonessential apps from starting in the background and wasting battery & network bandwidth. If you want to do everything you possibly can to minimize resource hogging, you should get Autostarts.
I downloaded Autostarts - I hate to be asking this sort of question but I am sort of cautious when changing these sorts of settings (because I heard a person who had to boot into recovery because he shut off system applications by accident), which programs should/shouldn't I turn off? I am a little confused how to use this program - did it automatically shut off some programs, because as I look through I see some programs are crossed off in a green line... Any help would be appreciated! Thanks!
Bump - can anyone help me with Autostarts? Any help would be appreciated! Thanks!
Sent from my ADR6400L using XDA App
Sigh, Autostarts isn't a "task killer"
I stay away from any proccess that's needed to run in the background. Things in yellow, leave alone. IMO pandora has no business running in the background at start up. If there's no valid reason, I kill it.
Tossed from my Tunabowl
I realize Autostarts isn't a task killer (it cannot kill a task if it never opens up, hehe). Thanks for your advice though! The more I was looking at it last night, the more I was understanding, but you just reassured what I was assuming. Hopefully this helps my battery a bit... Or I figure what else makes my extended battery drain faster than others.
Even with Autostarts, my battery life has not improved that much... I have been experimenting a bit with different governors and settings, but now I am back with the extreme Imo kernel and on InteractiveX. Does anyone have any other suggestions? Any help would be appreciated!
I was having trouble with my battery also. I've been lucky with Gingeritis but still the battery was killing me. This may not be an option but the extended battery is amazing. I got the case to go with it and I'm not disapointed. This OS with heavy use also and display at 50% and all animations enabled. Also running 4g all day!
Sent from my ADR6400L using XDA Premium App
The problem is, I DO have the extended battery and now seeing some of the battery life that others are getting (a lot say 30+ hours, I am barely pushing my phone and I am getting less than 20 at a time).
BAMF 3 RC2, imo 3.3.4, 245/1593, LTE Only mode, auto brightness, twitter sync every 15 minutes, facebook every hour, gmail push, weather every hour, 4 hours of music streaming, another couple of playing, a lot of twitter and facebook, and doing a bunch of other things with the phone, and I rebooted about 3 times. I think I could hit 50+ hours if i didn't OC or reboot.
Oh yeah, I have the extended battery
g00s3y, which governor are you using?
i'm on the same kernel, but using gingerremix w/ a std battery. the phone drains 40% overnight with it being on wifi. (that's with just gmail pushing and gtalk on).
Anyone use this (or the custom ones) built into the Note?
Are they effective or is Juice Defender a better choice?
Regards,
Stu.
i rooted mine and dropped the clock a little under 1ghz using set cpu and i get two days of light use. a day and a half heavy use. i didnt notice a performance difference either.
Just Rooted mine and have seen battery life definitely decrease.
I am going to drop the clock and hopefully get a little better battery life.....
I was wondering if any of you people could be kind enough to give me some more battery tips for my new SGS3.
I'm getting around 4-5% / hour battery drain on standby. I have 2 GMail accounts on sync.
Here's what I've done:
-> Removed Kik Messenger because it was commandeering an outrageous amount of Wakelock Time (about 5-11% of Wakelock Time in 4-7 hours).
-> Installed Omega v5.0 (latest).
-> Still on Stock Kernel
-> Changed my WiFi Policy to "Only when Plugged in"
Turn off automatic synchronizatikn for fcbk email or other accounts.
Sent from my GT-I9300 using XDA
Totòòò said:
Turn off automatic synchronizatikn for fcbk email or other accounts.
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
What does Facebook sync anyway? I always thought it was just once to get the contact pictures. I will disable it now
I've been using Foxhound and Siyah kernel, super combo. I can honestly say it's the best performance/battery life on any android device I've used, 6+ hours of screen on consistently - wifi/gps on, 3gmails autosyncing, autobrightness, 1hr>calls, 50+texts, light browsing, redditt, Google Music... Battery life is so subjective though depending on your apps, usage, cell signal, etc.
Experiment! All things being equal, in my experience its the kernels that make the biggest difference in significant battery life improvements, with the exception of stock roms vs. AOSP/AOKP, battery life doesn't differ very much minus bloatware in the various roms. And if you're a flashaholic like me you'll actually have to wait a few charge cycles to get an accurate representation of battery performance for your phone.
kchino said:
I've been using Foxhound and Siyah kernel, super combo. I can honestly say it's the best performance/battery life on any android device I've used, 6+ hours of screen on consistently - wifi/gps on, 3gmails autosyncing, autobrightness, 1hr>calls, 50+texts, light browsing, redditt, Google Music... Battery life is so subjective though depending on your apps, usage, cell signal, etc.
Experiment! All things being equal, in my experience its the kernels that make the biggest difference in significant battery life improvements, with the exception of stock roms vs. AOSP/AOKP, battery life doesn't differ very much minus bloatware in the various roms. And if you're a flashaholic like me you'll actually have to wait a few charge cycles to get an accurate representation of battery performance for your phone.
Click to expand...
Click to collapse
Thanks for the big post! ^v^. I am going to flash the SiyahKernel. But after turning Facebook Sync and the Wifi Policy (which I found out about today).
My battery is at 93% at 2h 01m 05s (also my battery goes down to 99% as soon as I take it off the charger). So thats 6% in 2 hours which is 3% / hour ! Getting there ^^
Apparently going to 99% immediatelly after the charger is normal for Samsung devices. So I wouldn't count that as reduction.
I dont use aftermarket kernels and roms, I have disabled a few stock programs I do not use and get a very decent battery with the 2x battery saver. I had already ordered a secondary battery which is on its way actually as well, so ill be covered from there on
sent with SGS3
Annie the Eagle said:
Thanks for the big post! ^v^. I am going to flash the SiyahKernel. But after turning Facebook Sync and the Wifi Policy (which I found out about today).
My battery is at 93% at 2h 01m 05s (also my battery goes down to 99% as soon as I take it off the charger). So thats 6% in 2 hours which is 3% / hour ! Getting there ^^
Click to expand...
Click to collapse
99% right off the charger is a feature .
Undervolting is an option as well.
kchino said:
99% right off the charger is a feature .
Undervolting is an option as well.
Click to expand...
Click to collapse
Oh my! Great feature! Do you know of a guide on how to do that, or is that just a fancy term for "underclocking" ^v^
As I am still on stock kernel I am obviously still on stock speeds but I'm going to flash SiyahKernel after I finish uploading photos of my A77
Annie the Eagle said:
Oh my! Great feature! Do you know of a guide on how to do that, or is that just a fancy term for "underclocking" ^v^
As I am still on stock kernel I am obviously still on stock speeds but I'm going to flash SiyahKernel after I finish uploading photos of my A77
Click to expand...
Click to collapse
I don't think there are any OC/UV guides in the SGS3 forums but you could search XDA to acquaint yourself, there many writeups on the subject. Make sure have ADB and are familiar with it before so you can recover if necessary from any mishaps. Every processor has a different tolerance to OC/UV so there isn't a tried and true method of implementing it you just have to use trial and error.
I won't get in to it too much but undervolting and underclocking are related but different. Undervolting effectively ask the processor to run with less power from the battery at a specific clock speed or frequency. Underclocking would be reducing the overall frequency of the processor depending on the load. They can be used independently or together.
kchino said:
I don't think there are any OC/UV guides in the SGS3 forums but you could search XDA to acquaint yourself, there many writeups on the subject. Make sure have ADB and are familiar with it before so you can recover if necessary from any mishaps. Every processor has a different tolerance to OC/UV so there isn't a tried and true method of implementing it you just have to use trial and error.
I won't get in to it too much but undervolting and underclocking are related but different. Undervolting effectively ask the processor to run with less power from the battery at a specific clock speed or frequency. Underclocking would be reducing the overall frequency of the processor depending on the load. They can be used independently or together.
Click to expand...
Click to collapse
Ah thanks a-lot. Would creating a profile to limit the CPU to 300 MHz MAX during screen off save battery also?
I have SetCPU installed and have flashed to SiyahKernel now but haven't fiddled with it yet.
Annie the Eagle said:
Ah thanks a-lot. Would creating a profile to limit the CPU to 300 MHz MAX during screen off save battery also?
I have SetCPU installed and have flashed to SiyahKernel now but haven't fiddled with it yet.
Click to expand...
Click to collapse
Download extweaks from the market instead to configure Siyah. Extweaks hasn't been optimized for the SGS3 yet but it works better than SetCPU with Siyah, it also has descriptions of what each setting does.
If you aren't a gamer you could even toggle two of the cores off, definitely will increase your battery without much if any performance hit in real usage.
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
I'm pretty new to the rooting scene and having a smartphone in general, so I don't know much about what's considered "good" battery life. I'm running Nil's sense 4.0 with Snuzzo's 1.2 kernel, lazy governor with SIO. My max voltage is at 1188 and my min is at 384 (I have no idea if those are the best voltages for this phone to promote longevity; they just seemed like good values so I chose them). What do you think of this battery life I got today?
Sent from my ADR6425LVW using xda app-developers app
2.5 hours of screen on time ? on a standard battery? yeah i'd say thats good
Oh, yeah, standard. I'd appreciate any input that could further increase it, if possible.
Kelton Rivas said:
I'm pretty new to the rooting scene and having a smartphone in general, so I don't know much about what's considered "good" battery life. I'm running Nil's sense 4.0 with Snuzzo's 1.2 kernel, lazy governor with SIO. My max voltage is at 1188 and my min is at 384 (I have no idea if those are the best voltages for this phone to promote longevity; they just seemed like good values so I chose them). What do you think of this battery life I got today?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I think you mean clockspeed, not voltage.
Kelton Rivas said:
Oh, yeah, standard. I'd appreciate any input that could further increase it, if possible.
Click to expand...
Click to collapse
There are two main power draws in the Rezound, neither of which you can "fix" assuming everything else is working properly.
The screen - it's power use is clearly the highest, 2.5 hours of screen time is pretty much the best you will get with a standard battery, the only way to improve it is to reduce the brightness.
The radios - it's power use is strictly governed by the signal strength received, the better the signal the lower the power use, the worse the signal the higher the power use.
There are lots of things you can do improve the battery use, none of them will make a significant difference for the screen or radio battery usage.
The Rezound is a high-end phone, it's screen and radios are impeccable... the problem is the cost is battery life. The best way to increase the battery life is to go to an extended battery.
yeah, honestly the only way to get longer battery life is to have screen on less. i mean 2.5 hours/almost 3 hrs on a standard battery is about the tops your gonna get
I used to have Neo's Adrenaline 2.0 Rom, and was getting on average 13 hours of average usage per day. I would text a bunch, Listen to music ~4 hours, and browse Reddit for another hour. I have YET to find another rom that can produce such impressive results. AOSP SCARFS down my battery life like no other. With the same usage, I get about ~8/9 hours of usage. Although Neo's Linaro roms do seem less laggy.
im_high_tech said:
I used to have Neo's Adrenaline 2.0 Rom, and was getting on average 13 hours of average usage per day. I would text a bunch, Listen to music ~4 hours, and browse Reddit for another hour. I have YET to find another rom that can produce such impressive results. AOSP SCARFS down my battery life like no other. With the same usage, I get about ~8/9 hours of usage. Although Neo's Linaro roms do seem less laggy.
Click to expand...
Click to collapse
ineff deus. I modded a lot. removed nearly everything sense. tweaked build.prop a bit. kept apps frozen until needed. kept foreground apps low and prevented many from starting based on choice. I get nearly 7 straight hours on extended battery. close to 5 or more depending usage on standard