Well since I love getting into technical results with this Rezound since I got it, I'm pretty much really late to the game with this phone. My Thunderbolt took a crap on me during deployment and I've been spending the last 2-3 weeks working on it here and there to make it the best battery life for my OWN personal usage.
People may say *Oh dur turn on 4G* I know 4G eats battery, but where I'm at, I get very very spotty signal, Most I use is 3G sending MMS. I keep data off all day since I just text.
Since I get spotty signal, obvious answer is my phone will use more battery for itself. I'm am well aware of this. I have most of the stuff memorized I have done to this phone, rom wise, build.prop, Kernel Tweaker etc. So if you have any questions about what I've done just ask me. It's hard enough to search through a ton of threads and get VERY VERY vague answers. Seems like it's been like this since I jumped on the HTC Inc back in the day
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did take these with my camera because screenshot didn't wanna work properly with me so I just grabbed my camera and shot the pics off. If anyone wants me to post my usuage from yesterday via battery_stats I can.
EclipticRez 5.2.1
Funky v2.3, S2W disabled.
The best results I've found in regards to battery life is with using Kernel Tuner and giving each processor core a different governor (cpu0 Badass, cpu1 Conservative) and underclocking and tweaking some settings in MPdecision. Also, turn off auto-brightness. Take it to around 35-40% and just leave it there.
I also leave LTE on at all times, but I also use WiFi wherever available.
Granted, I don't have my extended battery (yet - just ordered one earlier in the week), but I finished yesterday with 17 hours and 2 hours and a few minutes of screen on time. That's just with the standard 1620 mAh battery.
liqwidzero said:
The best results I've found in regards to battery life is with using Kernel Tuner and giving each processor core a different governor (cpu0 Badass, cpu1 Conservative) and underclocking and tweaking some settings in MPdecision. Also, turn off auto-brightness. Take it to around 35-40% and just leave it there.
I also leave LTE on at all times, but I also use WiFi wherever available.
Granted, I don't have my extended battery (yet - just ordered one earlier in the week), but I finished yesterday with 17 hours and 2 hours and a few minutes of screen on time. That's just with the standard 1620 mAh battery.
Click to expand...
Click to collapse
Well I will defiantly try that out, I was also using auto the whole day since I was constantly inside/outside when the sun was blaring.
What are your current MPDecisions in Kernel Tweaker?
Also in Kernel Tweaker, does it not sometimes load your settings for the CPU? I heard it was kernel related and not ROM related. Sometimes my CPU0 would stay at 1080MHz where I set it at but CPU1 would reset to 1.5Ghz
savagebunny said:
What are your current MPDecisions in Kernel Tweaker?
Also in Kernel Tweaker, does it not sometimes load your settings for the CPU? I heard it was kernel related and not ROM related. Sometimes my CPU0 would stay at 1080MHz where I set it at but CPU1 would reset to 1.5Ghz
Click to expand...
Click to collapse
Mine jumps back up to 1.5 on CPU1 as well, but that's a non-issue. Set it to Conservative. Make sure that the minimum is set at 384 MHz for each core. Otherwise it will just start jumping around (at least, that's what happens to me). I don't know if it's exactly kernel related, though. I was able to run Funky 2.4 on a Sense 4 ROM (Newt's OneXxX 6.0.2, I think) and cpu1 stick, though.
MPdecision:
Service Start Delay: 10000 ms
Pause: 10000 ms
Threshold Up - Load: 40 ms
Threshold Up - Time: 450 ms
Threshold Down - Load: 5 ms
Threshold Down -Time: 250 ms
Idle Frequency: 192
liqwidzero said:
Mine jumps back up to 1.5 on CPU1 as well, but that's a non-issue. Set it to Conservative. Make sure that the minimum is set at 384 MHz for each core. Otherwise it will just start jumping around (at least, that's what happens to me).
MPdecision:
Service Start Delay: 10000 ms
Pause: 10000 ms
Threshold Up - Load: 40 ms
Threshold Up - Time: 450 ms
Threshold Down - Load: 5 ms
Threshold Down -Time: 250 ms
Idle Frequency: 192
Click to expand...
Click to collapse
Thanks. Ya that's what I just set it too. I was using dancedance on both cores when I posted up the screen shots. Will see how it goes for the most of the day. Yesterday I sent out almost 300 texts maybe or more so that was a majority of screen time with 3 different people to say the least.
Oh and another anomaly I can't quite figure out. Some days my phone only pulls less than -100mA and then only ~-20mA on average in screen off sleep. Now today instead of doing the same thing yesterday, todays average has been more near ~ -280mA+ with screen off sleep
I have changed nothing on the phone. Did a restart, no change. Shut phone down completely, pull battery and reboot and still the same result. And even when people ask me what my wakelocks are, I post them and then no one knows what they are nor can I find documentation on the software itself.
did u tried to check it with gsam battery to see what drain or what waking up the phone ?
Try uninstalling some memory intensive apps and reinstall them. Sometimes restored files, for me, just need to be reinstalled.
Also, I just received my extended battery and I'll see how far I can go with it.
How has your phone been doing since the new settings?
Sent from my ADR6425LVW using xda app-developers app
Related
Has anyone played with the profiles for this app to get optimal performance and better battery. Life of so post your results and share your profiles thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other than that it is always set to 816/216.
I usually get about 5 hours screen time and about 20 hours standby. Email and Calender sync at 1 hr, with a custom power profile that turns data off after 15 minutes between 3a-9a. I'm happy with it
Girgizzlemuf said:
Other than that it is always set to 816/216.
I usually get about 5 hours screen time and about 20 hours standby. Email and Calender sync at 1 hr, with a custom power profile that turns data off after 15 minutes between 3a-9a. I'm happy with it
Click to expand...
Click to collapse
Your profiles are similar to what I use, although I don't have one for charging/charging A/C
Also, you run 816/216 rest of the time? Aren't you short-changing your phone's capabilities a bit though ... ? I find the biggest different is having screen-off profile.
crippenx said:
Your profiles are similar to what I use, although I don't have one for charging/charging A/C
Also, you run 816/216 rest of the time? Aren't you short-changing your phone's capabilities a bit though ... ? I find the biggest different is having screen-off profile.
Click to expand...
Click to collapse
Not really. I change it to 1000/216 if it's spectral souls, gun bros or a benchmark. Angry birds plays on my fuze (lol) so i don't change it there. I have noticed little to no difference running 1000/216 on launcher screens, pictures, data rates or anything versus 816/216. If i bump it down to the 700 range then things get laggy, but as it sits 816 runs everything almost flawlessly.
Girgizzlemuf said:
Not really. I change it to 1000/216 if it's spectral souls, gun bros or a benchmark. Angry birds plays on my fuze (lol) so i don't change it there. I have noticed little to no difference running 1000/216 on launcher screens, pictures, data rates or anything versus 816/216. If i bump it down to the 700 range then things get laggy, but as it sits 816 runs everything almost flawlessly.
Click to expand...
Click to collapse
Good to know, thanks! I'll try that, maybe squeeze out a little more battery life than I am now What are you averaging? I can go about 1.5 days with good usage as it stands
Strange, I can't have more than 15 hours if moderate usage...
I have similar profiles to the screenshot posted above, but I don't have one for when powered. The main profile on mine is 1000 max ~400 min. I've found that keeping the min ~400 makes the device always snappy without sacking much battery life.
I also use JuiceDefender to manage my data syncing. I leave the blur battery profile at high performance.
crippenx said:
Good to know, thanks! I'll try that, maybe squeeze out a little more battery life than I am now What are you averaging? I can go about 1.5 days with good usage as it stands
Click to expand...
Click to collapse
Depends on the day. If its a day off, i get ~30 hours with ~6 hours screen time from 100%-10%. Most days though i don't notice much, I drive around a lot listening to pandora in my car dock so its constantly being charged
If I can tear myself away from pandora for a day i'll repost something more meaningful.
On a side note, I notice with circle battery widget I usually get the slowest drain between 80% and 40%, not sure if anyone else has noticed this.
Small update to what I said earlier..
With my profiles, and all the crap running in the background this is what i got now from 100%-31%
1d3h11m since unplug
1d0h25m idle time
3h04m display
0h45m spectral souls (!)
Would go further but I am gonna be away from a charger all day tomorrow
i get the same battery life with setcpu and a display off profile than with no setcpu at all. my guess is that the battery saved gets wasted on setcpu itself.
I have the phone on from 7:30am to 12 midnight with no calls and 1 hour display time and i have just 40% less. No wifi at anytime.
Apps i only have gmail, no other email accounts, twitter at 15 minutes and whatsapp
franciscojavierleon said:
i get the same battery life with setcpu and a display off profile than with no setcpu at all. my guess is that the battery saved gets wasted on setcpu itself.
I have the phone on from 7:30am to 12 midnight with no calls and 1 hour display time and i have just 40% less. No wifi at anytime.
Apps i only have gmail, no other email accounts, twitter at 15 minutes and whatsapp
Click to expand...
Click to collapse
You got something else wrong. SetCPU will definitely not drain the life it saves. you must have a beast app running in the back somewhere...
also, what kernel/rom are you running?
dean_fx said:
You got something else wrong. SetCPU will definitely not drain the life it saves. you must have a beast app running in the back somewhere...
also, what kernel/rom are you running?
Click to expand...
Click to collapse
lol what??
what kernel? since when there its custom kernels :rolleyes
i get like 12 hours in my normal day i guess its to few :s but streaming music over BT like 4 hours and surfing web forums tweetdeck. not impressed battery for my usage :S
perhaps seems better than my N1. and seems when i enable data it drain more faster like 5% per hour screen off, and no data like 1% or 2
zen kun said:
lol what??
what kernel? since when there its custom kernels :rolleyes
i get like 12 hours in my normal day i guess its to few :s but streaming music over BT like 4 hours and surfing web forums tweetdeck. not impressed battery for my usage :S
perhaps seems better than my N1. and seems when i enable data it drain more faster like 5% per hour screen off, and no data like 1% or 2
Click to expand...
Click to collapse
Yes, my question was pretty straight forward...what kernel are you running. From your response I see your English may be the issue here.
Anyway, reason I ask is because some kernels such as BFS kernels don't really play nice with my phone nor battery. So maybe the issue is with the kernel being used.
"::rollseyes::"
dean_fx said:
Yes, my question was pretty straight forward...what kernel are you running. From your response I see your English may be the issue here.
Anyway, reason I ask is because some kernels such as BFS kernels don't really play nice with my phone nor battery. So maybe the issue is with the kernel being used.
"::rollseyes::"
Click to expand...
Click to collapse
Bootloader is signed on the phone. No custom kernels.
We currently have 4 options on att and like... one on bell i believe. Mine is stock motorola 4.1.57 with gladiatrix2 pseudo-rom
I did forget to mention that i'd sent like 40 text messages and replied to a half dozen emails.
dean_fx said:
Yes, my question was pretty straight forward...what kernel are you running. From your response I see your English may be the issue here.
Anyway, reason I ask is because some kernels such as BFS kernels don't really play nice with my phone nor battery. So maybe the issue is with the kernel being used.
"::rollseyes::"
Click to expand...
Click to collapse
/sigh. XDA, a wealth of information, but a lack of patience and reading comprehension.
Anyway, I feel like the Atrix does better than the Evo with battery life. I might try fiddling with SetCPU, so thanks for the info.
HTC Desire with stock Froyo ROM
I've been using SetCPU 2.1.1a recently and have noticed no difference in battery life. Is SetCPU a placebo as far as battery life is concerned?
My settings:
Charging = Max. 998 / Min. 998
Screen Off = Max. 245 / Min. 245
Battery < 101% = Max. 998 / Min. 245
Battery < 25% = Max. 499 / Min. 245
If I "Disable Perflock" SetCPU says "Success: Perflock appears to be disabled".
Some say it increases their battery life, are they imagining it? I'm not interested in over clocking. I'd be very willing to buy it, if it increased my battery life. Thanks
Why are people using Setcpu to try to save battery life?
The whole point of Tegra 2 is ultra low voltage operation when the system is inactive..
Its absolutely counter-productive to use setcpu to try to already do what the chipset itself is made to do and not half as effectively.
seven2099 said:
Why are people using Setcpu to try to save battery life?
Click to expand...
Click to collapse
Because plenty of people say it helps. Hence my question. I'm guessing you pessimistic?
seven2099 said:
The whole point of Tegra 2 is ultra low voltage operation when the system is inactive..
Click to expand...
Click to collapse
The Tegra 2 is only in certain Android devices.
bradavon said:
Because plenty of people say it helps. Hence my question. I'm guessing you pessimistic?
The Tegra 2 is only in certain Android devices.
Click to expand...
Click to collapse
it may only be in certain ones, but it DEFINITELY in the atrix....which is this section in which you're posting...
raybond25 said:
it may only be in certain ones, but it DEFINITELY in the atrix....which is this section in which you're posting...
Click to expand...
Click to collapse
This thread is covering more than the Atrix. I didn't want to start yet another thread about this, when there are already plenty. Besides the main SetCPU thread (with the download links) is in the HTC Dream section and that phone's ancient.
If someone can answer my questions please.
During regular use I am at 816 Max and 216 Min. When charging I use 1000 Max and 1000 Min. Screen off 216 Max and 216 Min. Battery life is alright, from 100% to 80% it decreases rapidly but from 79 to around 5% it is phenomenal. My phone will last around 12 hours of heavy use. I send a lot of texts 150+ a day and check facebook mobile about 5 times an hour.
Don't tell me to calibrate my battery, i've done it probably 100 times.
The objective of this thread is simply to see what other SetCPU profiles other people might be using.
from higher priority to lower...
Screen Off: 456-216
Charging: 608-216
Battery<10%: 456-216
Battery<30%: 608-216
Keeping 1000-1000 while charging is bad idea.
ideally power consumption should be none while charging so that battery can charge faster. I would suggest you to switch to the lower frequency while charging.
also, the 'Screen off' profile takes over if screen is off during charging thus giving you best of both world in case if you want to use fone while charging...(just set priority highest on screen off'
also, i have set battery = power saving mode settings.... through custom mode and also added peak off hours when i generally sleep
this lasts me more than 30hours on general usage and a day if i game and play music alot.
Brightness is set to auto all the times. although my usage environment never requires it to be above 40%
madnav said:
from higher priority to lower...
Screen Off: 456-216
Charging: 608-216
Battery<10%: 456-216
Battery<30%: 608-216
Keeping 1000-1000 while charging is bad idea.
ideally power consumption should be none while charging so that battery can charge faster. I would suggest you to switch to the lower frequency while charging.
also, the 'Screen off' profile takes over if screen is off during charging thus giving you best of both world in case if you want to use fone while charging...(just set priority highest on screen off'
also, i have set battery = power saving mode settings.... through custom mode and also added peak off hours when i generally sleep
this lasts me more than 30hours on general usage and a day if i game and play music alot.
Brightness is set to auto all the times. although my usage environment never requires it to be above 40%
Click to expand...
Click to collapse
Is this the way you have it ?im new to setcpu
Sent from my MB860 using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just use the 608 max, 216 min for screen off and then a 456 max, 216 min for hours that I regularly am sleeping.
Does anyone know why we can only use certain seemingly random numbers? I would like to get much more fine tuned than differences of only ~150... And why is 216 the only min?? That's too high!
yokozuna82 said:
Is this the way you have it ?im new to setcpu
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yes but 2nd last priority should be battery<10% (you have kept both at battery<30%)
My profile is that I uninstalled setcpu... I don't think it made any positive difference at all in battery life. I have switched to performance mode (phone charges at night) and I have been happy with the battery life. Other day 8 hour road trip with Slacker on for 6.5 hrs and screen locked on the whole time so I could flip around songs. Also exchange/email sync, news reader updates every two hours and some phone calls. I plugged in usb for maybe 3/4 hour to charge. At the end of day (took off charge at 6am and put back on charge at 1am) had 40% left. Biggest things for me to improve battery was get rid of running programs (setcpu/cache mate/etc) Also have the android task manager turn off some things when screen is dark and took email/exchange off push (sync every half hour)
Imho..
I've done a bunch of different things to my phone to achieve this. I owe most of this result to scripts I have developed, I've put a lot of research into these, as well as my build.prop (Google "0vermind build prop" for that), I am not even using the memory values of supercharger, etc. I will probably be posting my scripts soon and how I did this, but just wanted to give a heads up. Long live the best phone ever made! The Droid x2!
Here's some teasers:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice..looking forward to your work..
Now this is with what kind of use?
I can do regular texting, a little web search and marketplace downloads/updates and have around 19 hours and be around 20% with just the normal tweaks. (Probably 40% usage, 60% idle). I set the data saver to trigger at 11 PM (even though I always use it until late into the next morning) but by the time data saver is off (8 AM) the phone probably dropped 10-15% if I rarely used it. I'm wondering if this is at all any good since my idle is around 85% at all times so it looks like you trimmed that down.
This being my first smartphone, I think the actual standbye time is great but usage time is awful.
*edit: Just checked and running 2 Hours on battery and dropped 10% so I have no clue whats going on. I've noticed this phones battery is really random.
Elite49 said:
Now this is with what kind of use?
I can do regular texting, a little web search and marketplace downloads/updates and have around 19 hours and be around 20% with just the normal tweaks. (Probably 40% usage, 60% idle). I set the data saver to trigger at 11 PM (even though I always use it until late into the next morning) but by the time data saver is off (8 AM) the phone probably dropped 10-15% if I rarely used it. I'm wondering if this is at all any good since my idle is around 85% at all times so it looks like you trimmed that down.
This being my first smartphone, I think the actual standbye time is great but usage time is awful.
*edit: Just checked and running 2 Hours on battery and dropped 10% so I have no clue whats going on. I've noticed this phones battery is really random.
Click to expand...
Click to collapse
Mines been pretty consistent, and I've had wifi on most of the time, if you look at the screens. I don't text using standard texting app, I use Google Voice, which is said to use more battery cause it has to send a keep alive signal and it constantly redownloads messages.
That being said, I also have Trillian sitting in the background and have it on 24/7. It notifys me of texts, vms, calls from my business number, plus facebook. And I made a few calls, some short, some long. All that, 19 hours, and still 20% to spare. Heavy use still lasts pretty dang long.
And, if you look at my awake times, my phone never really goes into deep sleep when the screen is off, and it's suppose to, I think this is a software bug in Motorola's build of Gingerbread for x2. That's why I think I'm pretty impressed right now with this beast! Oh and Quadrant scores around 2900.
I have excellent battery life with my x2, the key to me was not using any of motoblur's social networking integration.. It consistantly runs and just gums everything up.. I use the facebook app and twitdeck when i want too, but dont let them update automatically (aka no unneeded connections to the web to download crap i can just manually update)..
Ever since then i get 2 full days out of battery usage if i need..
Since moving to Gingerbread I've been able to push the phone to almost 24hrs between charges, on very light usage days. This is with bg data services running (Sync on, corp email sync, Trillian, weather updates, etc...) If I'm using the phone for any significant portion of the day this drops considerably.
All I've done is frozen most of the Motorola/Verizon bloat.
The next opportunity I have to basically ignore my phone for 24hrs I will post screenshots to prove it.
That's with light usage though? I use my phone pretty heavily at times. Cause as you know from my signature, I run a business, lol.
I'm a heavy use phone user and I use my phone as my home phone. I've rooted and killed the motocrap with fire. I use setcpu to handle better CPU throttling and achieve 24+ hours on a single charge. I don't have any doubts the heavy battery use stems from the motocrap. I just cannot wait until CM7 or another minimalist rom becomes available with overclocking.
spr0k3t said:
I'm a heavy use phone user and I use my phone as my home phone. I've rooted and killed the motocrap with fire. I use setcpu to handle better CPU throttling and achieve 24+ hours on a single charge. I don't have any doubts the heavy battery use stems from the motocrap. I just cannot wait until CM7 or another minimalist rom becomes available with overclocking.
Click to expand...
Click to collapse
Do you happen to have any problems with setcpu actually making the processer stay within the range you set? It seems that no matter where I set the min/max it stays there for maybe half hour max then goes to whatever speed it wants to. The sliders don't change spots, the cpu just doesn't stay within the value set after a half hour. Can't future out why.
ashclepdia said:
Do you happen to have any problems with setcpu actually making the processer stay within the range you set? It seems that no matter where I set the min/max it stays there for maybe half hour max then goes to whatever speed it wants to. The sliders don't change spots, the cpu just doesn't stay within the value set after a half hour. Can't future out why.
Click to expand...
Click to collapse
Overclocking needs a CUSTOM KERNEL not a stock kernel. Locked BLoader = No Overclock.
SwiftLegend said:
Overclocking needs a CUSTOM KERNEL not a stock kernel. Locked BLoader = No Overclock.
Click to expand...
Click to collapse
I am not trying to overclock. I am trying to keep my speeds lower to help save battery which I have been told IS possible. I know I can't go faster than 1ghz but I thought I would be able to keep it from reaching that to save battery life. Am I wrong
Overmind,
Is this with the stock bh5x battery? I can get upwards of 10-14hours on mine with moderate use.
Sent from my DROID X2 using XDA App
ashclepdia said:
I am not trying to overclock. I am trying to keep my speeds lower to help save battery which I have been told IS possible. I know I can't go faster than 1ghz but I thought I would be able to keep it from reaching that to save battery life. Am I wrong
Click to expand...
Click to collapse
I'm not so sure that the stock kernel will allow for any tweaking of clock speeds. I think you have to have a custom kernel to implement any clock or scheduler changes.
Sent from my DROID X2 using XDA Premium App
garywojdan81 said:
I'm not so sure that the stock kernel will allow for any tweaking of clock speeds. I think you have to have a custom kernel to implement any clock or scheduler changes.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Just seems weird that it initially works but then after a while stops..
ashclepdia said:
Do you happen to have any problems with setcpu actually making the processer stay within the range you set? It seems that no matter where I set the min/max it stays there for maybe half hour max then goes to whatever speed it wants to. The sliders don't change spots, the cpu just doesn't stay within the value set after a half hour. Can't future out why.
Click to expand...
Click to collapse
Not sure about that one... I use profiles to handle the changes rather than forcing the speed ranges through the set sliders. The profiles seem to work better anyway, they react to active content rather than set-in-stone performance. One thing to note, the profiles are only available in the paid version (IIRC). Changing the profiles would be similar to handling the changes manually or through custom scripting routines. Right now, I'm going on 15+ hours with 70% of my battery left. I had the OG Droid running over five days on a single charge. What I do different from those saying 1 day max charge, I have no clue.
So ETA on script release?
spr0k3t said:
Not sure about that one... I use profiles to handle the changes rather than forcing the speed ranges through the set sliders. The profiles seem to work better anyway, they react to active content rather than set-in-stone performance. One thing to note, the profiles are only available in the paid version (IIRC). Changing the profiles would be similar to handling the changes manually or through custom scripting routines. Right now, I'm going on 15+ hours with 70% of my battery left. I had the OG Droid running over five days on a single charge. What I do different from those saying 1 day max charge, I have no clue.
Click to expand...
Click to collapse
I shall try profiles then. I do have paid version. Thanks for the tip.
I consistently get 20+ hours with a stock battery, no scripts of any kind, with moderate use and data always connected. All I've done to achieve this is de bloat the hell out of the system apps, set my screen brightness to minimum (the thing its so dang bright anyways, you can hardly tell once you get used to the minimum setting) my wifi is set to never disconnect (I pretty much have a wifi connection 95% of the time) that's about it. I use adwEX, plume for twitter (polls every 3 minutes) gmail, google voice for visual voicemail, moderate amount of widgets (clockr, fancy widget pro, system panel, power control, uk news), I'm even running a live wallpaper (vortex galaxy, set to 100% speed).
Sent from OH MY GOD IS THAT A SQUIRREL!
ashclepdia said:
I am not trying to overclock. I am trying to keep my speeds lower to help save battery which I have been told IS possible. I know I can't go faster than 1ghz but I thought I would be able to keep it from reaching that to save battery life. Am I wrong
Click to expand...
Click to collapse
You Can Underclock.
So here I am, finally hitting 50% 1d 5h 10m and a few seconds. I wonder what this would be like on the extended battery?
Hi guys, I just wanted to know what undervolt values you guys use, right now im getting semi decent battery life but in comparison to others battery life its terrible, I get about 3 hrs on screen time (screen brightness at 25%) and overall 14 hrs battery life (100 - 0%) with average amount of use (browsing the web, text messaging and whatsapping)
Whether I'm on blur (Darkside/Aura) or CM7, I'm using Faux's latest 1.0GHz kernel. Unless I'm gaming, I leave my CPU capped at 750MHz, with a profile for screen off with max 216MHz (priority 100). I've attached my Voltages. Be careful with the set at boot option. Make sure to do a nandroid backup before messing with any of this. Remember that the max difference between steps of voltage settings is +/- 100; if you break that, then the settings are automatically inert (this is a Tegra restriction). Not all silicon is created equal, so your best undervolting might be less (or more) than mine. Good luck!
-omni
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
omni_angel7 said:
Whether I'm on blur (Darkside/Aura) or CM7, I'm using Faux's latest 1.0GHz kernel. Unless I'm gaming, I leave my CPU capped at 750MHz, with a profile for screen off with max 216MHz (priority 100). I've attached my Voltages. Be careful with the set at boot option. Make sure to do a nandroid backup before messing with any of this. Remember that the max difference between steps of voltage settings is +/- 100; if you break that, then the settings are automatically inert (this is a Tegra restriction). Not all silicon is created equal, so your best undervolting might be less (or more) than mine. Good luck!
-omni
Click to expand...
Click to collapse
i read somewhere in these forums that the voltage values on either side cannot have step-wise differences greater than 100mV... if that is true, that would mean that your voltages from 216mHz to 608mHz are not functional. i dont have much personal experience with UV, so couldnt say first-hand one way or the other, but from what i've gathered here, that is my understanding.
i would suggest starting small (-25 on all clocks) and adjusting them upwards, one at a time. as long as you dont check "set on boot", you can do this until your phone reboots, and then just wind it down to where it was stable.
fischwrap said:
i read somewhere in these forums that the voltage values on either side cannot have step-wise differences greater than 100mV... if that is true, that would mean that your voltages from 216mHz to 608mHz are not functional. i dont have much personal experience with UV, so couldnt say first-hand one way or the other, but from what i've gathered here, that is my understanding.
i would suggest starting small (-25 on all clocks) and adjusting them upwards, one at a time. as long as you dont check "set on boot", you can do this until your phone reboots, and then just wind it down to where it was stable.
Click to expand...
Click to collapse
The 100mv max difference between frequencies is a built in Tegra limitation. It applies to the final mV values at each frequencey (i.e. left side). So as long as each step does not exceed 100 from the preceding one, you should be good to go. Fischwrap is correct, 216 to 608 are being ignored.
See these 2 posts from faux's thread, they get into some more detail:
July 13
July 24
*Edit* After re-reading the second link I posted I wanted to correct the above. Steps greater than 100 are not ignored, they are automatically adjusted to be within 100mV of the preceding step.
can i ask, how come your scaling drop down box has a option called powersave, and mine is greyed out and I can't select an "option"?
thanks
On CM7 (any build, but currently on weekly #2) with Faux's 1.0GHz stopgap kernel I can get up to 40 hours with light to heavy use using the following UV values:
I use Optimize Toolbox to prevent unwanted autostarts, have WiFi turned off 50% of the time, have data turned on all the time, and rarely play games or watch videos.
on cm7, weekly build #2, faux's 1.45 stop ext4 kernel.....loving cm7, and the atrix. with minimal use (work long days during the week, I'm a mechanic) getting roughly 3 days. Still doing some texting, phone calling, web browsing, email during occasional times. also using uv values of -100 for each
Sorry for deviating from the OP. I would like to maximise my phone's battery life too. For some strange reason, i cant load Faux's enhanced 1 Ghz kernel on any of the ROMs, be it CWM or the usual gingerbread ones. Overclocked and stock kernels work fine though. I have checked and then cross-checked every step required to flash a kernel. What might be the issue?
Being new to XDA, i cant post directly in the development section, else i would have asked the same in Faux's kernel thread. Sorry again!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is unfortunate, it is not even hot so I don't know what's up.
Sent from my LG-E970 using xda premium
There is the temp as says setCPU
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Tim4 said:
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Click to expand...
Click to collapse
I am unsure if this is just over caution on their part of if this is something we need to be worried about... honesty even yours at 39c is not that hot 102 F which for a computer is whatever... but I thought this chip was supposed to run cooler and everything being the new architecture.
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
gafalas said:
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
Click to expand...
Click to collapse
You are right on point. I have seen it drop (I believe to 1180) when running a bunch of benchmarks. The manufacturer sets the heat threshold at a very safe level. Kernel devs are usually able to safely bump that up another 10 to 15 degrees. I am one of the lucky ones that got the variant 3 of the international One X. Variant 3 was the strongest version and I ran all 4 cores at 1600 with 51 minimum. Faux usually figures out how to uncap and raise the throttle temperature... but he's on a N4. I am going to keep an eye on the kernel threads there and see how far they push things. Chainfire's "PerfMod" app is perfect to watch this while running different apps
Sent from my LG-E970 using Xparent ICS Tapatalk 2