Related
I was wondering what would be considered optimal settings for SetCpu. I amn running BaconBits and am not sure how I should do the settings.
Any help would be appreciated!
Thanks.
i have mine set at:
Profile 1 : 806 MHz max, 245MHz min, On Demand, priority 50
Profile 2 : 245 MHz max , 245MHz min, On Demand, for when the screen is off, priority 50
if i change the MHz, i change it higher on profile 1 for whatever i need it for then i just scale it back down to 806 when i am done...
Mines pretty much the same as the one above save for max clock speed being 1500Mhz.
Sent from my HTC Vision using XDA App
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
If you search google for an "overclocking 101" thread you should find a rather large ongoing break down of setcpu and the most efficient way to use it. I believe its on one of the droid forums, awesome info.
tazz9690 said:
I have my scaling set ondemand, have setcpu set at boot, with 1497 max and 245 min, with profiles for various states of the phone.
My profiles:
Screen off: 245 max, 245 min - Priority=100
Battery temp >104: 806 max, 245 min - Priority=90
Battery <10: 245 max, 245 min - Priority=80
Battery <20: 368 max, 245 min - Priority=70
Battery <30: 768 max, 245 min - Priority=60
Charging/Full: 1497 max, 245 min - Priority=50
I get well over a day of use, even with moderate-heavy usage, even with my overclocking on Evil's Sense ROM.
Click to expand...
Click to collapse
I just stole the rest of your settings, hope you dont mind!
WarBird87 said:
I just stole the rest of your settings, hope you dont mind!
Click to expand...
Click to collapse
By all means, have at it!
Main profile: 245 - 1017 on demand
Charging/Full: 1017 - 1017 performance 90 priority
Screen Off: 245 - 245 performance; mainly as this mode will bypass the need to poll/sample for CPU speeds, thus reduces some CPU load. 100 priority
Battery < 20%: 245 - 768 on demand 75 priority
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
WarBird87 said:
i decided to put the SetCPU widget on my homescreen last night so i could see if the profiles were actually changing as my battery ran lower... and my phone got reaaaalllly sluggish to the point where i would have to wait a few seconds for it to flip back and forth between screens... i deleted the widget thinking that might have caused it, but it was still laggy... so i unclicked on the profiles for battery and got it back to 806MHz and it was fine again...
im guessing that it supposed to slow down the phone when the CPU drops below 806MHz but i didnt think it would be that bad... anyone else experiance this?
Click to expand...
Click to collapse
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Speaking of powersave bias, could anyone tell me some optimal settings for the setCPU advanced tab? Don't mean to derail this thread, I've just never used that tab.
Sent from my T-Mobile G2 using XDA App
SeReaction said:
What are the profiles you are using? The ones you copied shouldn't have run into any conflicts... except when you're under 20% battery where the CPU is throttled under 368.
What is your powersave bias?
Click to expand...
Click to collapse
I believe i was right at 20% batt or right below,so that could have been the issue... I havent messed with anything on the advanced tab as i dont know much about it, the powersave bias is still set to 0
I have HTC heroc 200 alltel running fresh 2.40 rom firerat mtd 160 10. what should I set CPU to
Sent from my HERO200 using XDA App
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
j.books said:
does anyone else feel that their battery lasts longer without using setcpu at all? I mean I love what setcpu can do but in terms of power efficiency, even without overclocking, for some reason I feel like my battery last longer without it.... or am I just crazy?
Click to expand...
Click to collapse
I used to get about a whole day without setcpu. With setcpu, same amount of usage, I get well over a day and a half before having to charge it up.
I haven't been able to find any info on undervolting the Xoom, so have started this thread in the hope that some may find it beneficial.
What is undervolting?
It basically involves reducing the amount of electrical voltage running through the CPU. It does not affect the speed of the CPU at all, just the amount of power that it uses. The stock configuration of CPUs usually has a fairly high voltage, to cater for the fact that CPUs are not exactly identical.
Why undervolt?
Reduce power consumption, and therefore increase battery life.
Why not undervolt?
Can affect stability, and there is a small risk of damage to your device.
Disclaimer: Undervolting, like overclocking, does have the potential to damage your device. It's very rare, but not unheard of. I've never had a problem, but you may. Good luck, and don't blame me.
My config:
Model: MZ601 Xoom
Kernel: Tiamat Xoom v2.1.0
Undervolting software: SetCPU 2.2.4
My voltages before UV:
MHz mV
216 770
312 770
456 825
608 900
760 975
816 1000
912 1050
1000 1100
1200 1150
1408 1250
1504 1325
1600 1400
1704 1400
So after doing a bit of testing, I've found that I can lower my voltages noticeably throughout the range, reducing the amount of power my Xoom uses, and prolonging my battery.
My UV voltages:
MHz mV
216 770
312 770
456 775
608 825
760 875
816 925
912 975
1000 1000
1200 1075
1408 1125
1504 1175
1600 1250
1704 1325
Notes:
It is not possible to UV any less than 770 mV (with the kernel I'm using anyway).
Given that the mV for the 456 CPU frequency is so similar to 216, I set my minimum clock frequency to 456, which makes the device more responsive.
So, you may want to try these voltages, and see how they work for you.
To test: (Instructions for SetCPU)
Set your min & max speeds to the same frequency, for example 456.
Set the voltage of the 456 frequency to an amount lower that the current amount, for example 775. (It's generally best to adjust your voltage down only 25mv at a time.)
Perform a "Stress Test", for at least about 5 seconds.
If the device locks up or reboots, the mV is too low - try a higher mV.
Once you've found the optimal voltage for that frequency, move onto the next one, for example 608, then 760, etc.
If your device locks up or freezes during testing, you can force a reboot by holding down the Volume Up button, and the Power button.
The voltages I've used above may work for you, or you may have to increase them a little on your device. You may also get better voltages than me - if so, please post your results.
Battery test results
Performed some battery performance testing by doing the following steps:
1. Set the screen to not turn off, and brightness to 10% (screen needs to be on to keep the stress test running, and brightness low to minimise the battery drain of the screen, as that's not what we're testing).
2. Disabled all network connections (WiFi, Bluetooth, Data, GPS) to minimise battery drain by other factors.
3. Closed all other apps, and did not use the Xoom at all during the tests.
4. Charged Xoom to 100%.
5. Set CPU speed to 1504mhz using SetCPU (both min & max frequencies the same for accurate testing).
6. Unplugged the Xoom.
7. Ran "Stress Test" for 2 hours (give or take 20 seconds).
I performed the above steps for both stock voltage, and undervolted voltage. Results as follows:
1. For stock voltage (1325mV on Tiamit Tachi kernel), battery life went down to 62%.
2. For undervolted voltage (1175mV, which is nice & stable for me), battery life went down to 72%.
Findings:
I was expecting battery savings, but not quite this much.
Standard voltage (at 1504mhz) at this CPU load, drains at about 19% per hour.
UV voltage at this CPU load, drains at about 14% per hour.
Standard voltage at this CPU load, the Xoom would drain battery entirely after about 5.26 hours.
UV voltage at this CPU load, the Xoom would drain battery entirely after about 7.14 hours.
In addition to the battery savings, the Xoom was only slightly warm after the UV tests, but very warm after the standard voltage tests. (Standard voltage test was performed first.)
Note: For general usage (email, browsing, basic apps & widgets), the CPU is not as heavily used. But in situations where the CPU is heavily used (such as intensive games), these results show there is significant potential for battery savings.
super nice tips. Tq very much
126-608 -175
Others -150
This is my settings... no prob at all.
Would I use setcpu app or just use the Moray(in settings) or does it matter
rayhodge02 said:
Would I use setcpu app or just use the Moray(in settings) or does it matter
Click to expand...
Click to collapse
Not sure what the "Moray" is, but any tool capable of undervolting should be ok. I like and use SetCPU, but I've tried other tools on other devices in the past, and they did similar things.
nobody wants to share their result after trying?
Very good job, I try
Sent from my Xoom using xda premium
pls share ur best result
I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium
Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.
for me i just underclock my xoom to 912mhz. it is almost as fast as 1ghz. and i save battery alot.
Gregus59 said:
I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Try bumping up the voltages a little bit at a time, until you find a stable setting. The settings I listed are what are stable for my Xoom (even intensive 3D games), but CPUs vary. What I get, others may not, and others may get better than me.
musashiken said:
Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.
Click to expand...
Click to collapse
They're not 100%. The longer you stress test, the more likely the CPU is stable, but 10 seconds gives a general idea. If unstable, just do as you did, and increase by 25mv or so.
omnia1994 said:
126-608 -175
Others -150
This is my settings... no prob at all.
Click to expand...
Click to collapse
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?
do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?
baron von bubba said:
do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?
Click to expand...
Click to collapse
1. It depends what you're using the device for. Games, for example, can use a lot of CPU, so undervolting in this instance, will definitely use noticeably less battery.
2. If CPU voltage throughput didn't make any difference, we'd all just run our devices at 1700mhz all the time.
3. With undervolting, I can run my Xoom at the same voltage at 456mhz, as it run at 216mhz. This means I set my minimum frequency to 456 instead, and for the same minimum battery consumption, my device is noticeably smoother.
If you want to know how much extra time you will get from a fully charged battery, YOU do some tests.
lindsaytheflint said:
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?
Click to expand...
Click to collapse
Yes i m sure. Has been using these settings till now.. no prob at all. Using tiamat stock gpu kernal with moray rom
i agree that during low intensity operation the power savings are probably nearly negligible, but during CPU-intense usage it could save a bit.
I myself am not willing to leave my Xoom on full bore for a series of tests lasting 7-10 hours each just to quantify how much power undervolting can save under super extraordinary circumstances.
But even if the energy savings is an arguable benefit, the reduction in CPU temperature is not. That alone makes this worth doing, IMO.
Agree.. after setting it my xoom now has lower temp when playing it
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Jasonhunterx said:
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I just got Voltage Control (the free one)
but I don't get how to use it. Can you please guide me? Which Mhz is sleep profile? and what do you mean build prop tweaks?
Well its pretty simple open app click second tab the you will see sliders you slide them down slide it down 1 notch
Sent from my GT-I9000 using XDA App
But like which ones? I set the 100 to -25 and went to sleep and most 13% overnight.
Which other ones should I set there.sorry for the questions I just don't want to mess up my phone
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
So basically, I have to go through the voltages (-#'s) and see how low i can go without crashing?
}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
What would happen if you set it to 1000= -0 ??? Couldn't you just odin back to stock if the phone crashed?
}{Alienz}{ said:
Start with these
(Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
check this out
http://forum.xda-developers.com/showthread.php?t=829731
nbhnohome said:
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
Click to expand...
Click to collapse
I don't think I want to go THAT low, maybe it'll crash my phone or someting?
caldran said:
http://forum.xda-developers.com/showthread.php?t=829731
Click to expand...
Click to collapse
that thread doesn't help. I've seen it before, its just info.
I think people are answering the wrong question. Or I should say, giving answers to a different question.
To the OP: You're talking about Deep Sleep battery usage, right? There's no way to undervolt Deep Sleep. It's already using very minimal voltage. I believe what causes excessive Deep Sleep battery drain is the number of apps still running and using the CPU during Deep Sleep.
Undervolting will help a bit with battery drain during normal usage. For Deep Sleep, turn off your various apps' syncing ability, as well as freezing programs you don't use but that run in the background. For instance, if you don't use navigation very often, consider freezing the Maps app, as it runs all the time in the background. A number of popular games like to run in the background like GunBros and Aqua Pets. Also switch from 2g/3g or 3g to 2g only at night to save battery there.
To recap, the less you have running in the background, the less battery you'll lose when you phone is in Deep Sleep.
I was also going to say switch to 2g if you don't need the speed. It helps a lot for me. I also usually put my phone in flight mode before I sleep. I lose like 0.5% of battery an hr on flight mode. I'm not on MIUI yet, still on froyo, but should still help.
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
mohitmoudgil said:
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
Click to expand...
Click to collapse
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Can I do voltage Control on stock MIUI Kernal or do I need Neo?
Sent from my Vibrant.
In my experience (admittedly only been on MIUI for a few weeks), Pimp my CPU, Voltage Control, and SetCPU all work fine on MIUI, so yes. You should be able to use Voltage Control. Not entirely sure about Stock MIUI, but if you use the (superior) Revamped version (either SS or Lithium editions) the kernel that comes stock with it allows you to change voltages, though I would still recommend moving to Glitch and using either the ML or LL versions if you want to maximize battery savings.
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Click to expand...
Click to collapse
OV/UV settings can vary widely between phones. Some offer little to no leeway at all, and can't even be overclocked to the rather tame 1200mhz. Others can sit at 1700mhz at 100uv. It's luck of the draw really. Also, Conservative Governor will be kinder to more exotic UV settings, while others like Smartass or OnDemand may only allow for a slight 25 or 50uv for most voltage levels.
Trial and error, my friend. Find what works best for your phone.
Thanks guys.
One more question
If when I test if my phone can handle a certain UV is it good to have it at the lowest I can?
Like example
My 400mhz can go down to -200UV is that good or bad? Should I keep it that low if its not crashing or anything
You need to do some stress testing to be sure it's stable at those frequencies. Depending on the governor you use, your phone may not hit 400mhz often enough for you to really tell if it's stable or not. You could set 800mhz to -800uv, but if your phone tends to skip over 800mhz most of the time...
Undervolting can cause other problems if it's not completely stable. For instance, on Froyo I would get annoying static during music playback. Took me nearly a month to figure out that it was because I was undervolting the 400 to 100mhz range too much.
Undervolting doesn't make THAT big a difference. If you don't want to tweak and stress test and tweak and tweak again and stress test again, etc etc etc, then just reasonable settings that most phones can handle. For instance, 1200 0uv, 1000 25uv, 800 50uv, 400 75uv, 200 100uv, 100 125uv.
xriderx66 said:
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Click to expand...
Click to collapse
In my experience when I switch to only use only 2G networks I get damn near twice the standy time. Also, changing wifi to never sleep and staying connected to wifi has about the same effect. This also holds true for CM7.
3G is a battery killer for MIUI and CM7
The only resolution I see to this is a GB source drop but I'm not holding my breath.
Off topic but does anyone know a good, fast device that runs CM7/MIUI without bugs or this horrible battery drain? I've been running some form of CM7 since Eugene's build this spring and it has gotten MUCH better but I'm kind of disappointed at the lack of vibrant-specific progress lately. There's only so much the devs can do without source (or a working vibrant and a T-Mobile data plan for that matter....). Don't get me wrong, I'm thankful for what we have and what the devs have given us but I'd love GPS that isn't f'd and 3G that doesn't suck my battery dry in a little over 10 hours (working 911 wouldn't hurt either.
Sent from my T959 using xda premium
Caveats: Every CPU and GPU does not come from the same bin, fabricated on the same date and possibly not manufactured in the same facility. They may each display different physical properties and a wider range of stability than others. What works for me may not work for you.
That being said, I've been stress testing my device with different settings for the past couple weeks trying to find a sweet spot of stability, speed, battery life and heat output.
I'm going to share two setups: my current one that I've stress tested for less than 24hrs but has proved stable through all conditions encountered thus far and my tried and true setup I've used for over a week with no trouble.
Tried and true setup:
Governor - ondemand
Range - 100MHz through 1.6GHz
100MHz - 800mV
200MHz - 825mV
300MHz - 850mV
400MHz - 900mV
500MHz - 900mV
600MHz - 900mV
700MHz - 925mV
800MHz - 950mV
900MHz - 1000mV
1000MHz - 1025mV
1100MHz - 1100mV
1200MHz - 1125mV
1300MHz - 1150mV
1400MHz - 1175mV
1500MHz - 1250mV
1600MHz - 1350mV
Experimental but stable battery saver:
Governor - ondemand
Range - 100MHz through 1.6GHz
100MHz - 775mV
200MHz - 775mV
300MHz - 800mV
400MHz - 800mV
500MHz - 825mV
600MHz - 850mV
700MHz - 875mV
800MHz - 900mV
900MHz - 950mV
1000MHz - 1000mV
1100MHz - 1100mV
1200MHz - 1125mV
1300MHz - 1150mV
1400MHz - 1175mV
1500MHz - 1225mV
1600MHz - 1350mV
GPU setup:
Low power state - 100MHz @ 800mV
High performance state - 400MHz @ 1050mV
Notes:
Custom governors were not stable for me AT ALL! I've found ondemand to be the best one for me and my needs, personally.
100MHz @ 750mV was so, SO close to being stable for me but my phone would routinely reboot in the screen off state. I'm assuming the stress of apps updating in the background, notifications etc was just too much.
As much as I love WidgetLocker (and I really do!), I found it to consume valuable resources, have more pronounced wake up lag and generally contribute to instability.
I use Chainfire3D to run my games etc. at x4 MSAA. As previously stated by Chainfire, the Mali can run at x4 with almost no extra overhead. I imagine that if one doesn't use x4 MSAA, one *might* be able to get away with 400MHz @ the stock 1000mV setting. That being said, I consider an extra 50mV to run at 133MHz faster to be a bargain.
Many games can be run with x16 MSAA with minimal overhead but I've found that for some resource intensive ones, especially multiplayer, they'll slow down unless the GPU is fed at 1200mV but this in turn causes a lot of heat generated so I would advise to avoid turning on x16 MSAA for those that you do find slowing down.
I use and recommend Voltage Control (donate version for extra features!) for setting up clock range and voltage for both the CPU and GPU. It also allows one to set boot settings (at setup or init.d script) and create multiple profiles. I do not recommend init.d script for untested settings as it could cause you issues.
Edit: Not everyone's kernels may support GPU OC/UV or the CPU ranges listed here. I am not responsible if you bork your device.
Here's someone else's method for testing settings:
Here's how I test UV settings.
Turn on everything. Wifi, bluetooth, max brightness, the whole works. This ensures the system is at maximum strain.
Start at maximum CPU clock
Lock the CPU clock (set the minimum and maximum allowed clock to the clock you are currently undervolting)
Lower the voltage by one step
Start a benchmark for a few minutes to see if undervolted clock is stable
If it passes, lower it again go back to step 4
When it freezes up your phone, reboot it and increase the voltage at that clock by two steps and consider it safe
Move to next frequency and go back to step 3.
You reached your lowest clock? Congrats, you should have a well undervolted CPU
Your voltages should always be lowering when your go from the highest clock to the lowest. If it happens that you have to increase the voltage at a lower clock, then also increase the higher clock frequency. I had a few hard locks because of this.
Example.
1000mAh (1GHz) > 900 mAh (900MHz) *< 950 mAh (800MHz) * > 700mAh (600mAh)
The 800MHz voltage is now higher than the 900MHz voltage. Also increase the 900MHz voltage to the same or higher voltage of the lower one.
1000mAh (1GHz) > 950 mAh (900MHz) > 950 mAh (800MHz) > 700mAh (600mAh)
Now that you have it undervolted, you may find that it could hardlock/reboot on you. When it happens do this:
Increase the voltage on all undervolted clocks by one step.
Continue using the device for a day
If the device locks up again, go back to back step 1
If its ok for a day, then every day lower the voltage back to what you had of only one clock (I suggest you go from highest to lowest)
You should be able to find which undervolt caused the reboot fairly quickly and still be able to normally use the phone and keep the rest of the "optimal" undervolts.
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda premium
I don't think UV saves battery. It is display that sucks most of the juice.
You save less than 2% with extreme UV and after a single reboot caused by instability - you lose even more battery.
There's an excellent thread in Nexus S forums - "battery drain benchmarks" (please search it).
I had similar UV settings and my phone never crashed during benchmarks or stress tests.
But it always crashed while installing 100+ apps with app backup restore, restoring backups with TB or MBR, gaming.
After removing UV, it never crashed.
I haven't tested UV with ICS... would see and report if it really saves battery.
Boy124 said:
I don't think UV saves battery. It is display that sucks most of the juice.
You save less than 2% with extreme UV and after a single reboot caused by instability - you lose even more battery.
There's an excellent thread in Nexus S forums - "battery drain benchmarks" (please search it).
I had similar UV settings and my phone never crashed during benchmarks or stress tests.
But it always crashed while installing 100+ apps with app backup restore, restoring backups with TB or MBR, gaming.
After removing UV, it never crashed.
I haven't tested UV with ICS... would see and report if it really saves battery.
Click to expand...
Click to collapse
I'm not sure if you've read everything through carefully or you would have seen that I've covered several of your points.
You also would have seen the method I use for stress testing and would have noted that I aim for four things: speed/performance, stability, power management AND thermal regulation.
While I agree that the display, barring a wonky or misbehaving app, will almost always be the #1 battery drainer - power management will certainly help to conserve battery life.
You also would have seen I mention profiles. There may not be a one size fits all setting for everyone but one can most certainly set up profiles for different scenarios.. Such as TiB backups/restores.
Sent from my GT-N7000 using xda premium
Did you do some benchmarks at the highest speed several times to make sure you are getting extra performance? With this phone I noticed that while the phone wont crash.. .some times performance will drop when running at settings now fully correct.
Sent from my GT-N7000 using XDA
You covered a lot of points but UV is total waste of time.
You get nothing out of it.
http://forum.xda-developers.com/showthread.php?t=1478406
Could you please post your data, how much battery do you save after UV?
Disagree boy, cause with wakelock screen is off, there is significant battery drain, I went to 10 hours life on single charge, due to wakelock.
Normally with deepsleep about 2 days. That's a reduction of 87.5% with screen off. Cpu running @200mhz.
Do the same with undervolting will dramatically increase battery life in that situation. So overal it will be a fraction compared to using the device with screen on, but still significant.
Edit: guess I was wrong here
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Disagree boy, cause with wakelock screen is off, there is significant battery drain, I went to 10 hours life on single charge, due to wakelock.
Normally with deepsleep about 2 days. That's a reduction of 87.5% with screen off. Cpu running @200mhz.
Do the same with undervolting will dramatically increase battery life in that situation. So overal it will be a fraction compared to using the device with screen on, but still significant.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I actually did the test on Gingerbread.
I set min and max to 200 MHz, activated flight mode and had stock music player running for 3 hours - with undervolt and without undervolt.
To my surprise battery consumption was the same.
May be experts who know about our processor architecture can shed some light here.
Boy124 said:
You covered a lot of points but UV is total waste of time.
You get nothing out of it.
http://forum.xda-developers.com/showthread.php?t=1478406
Could you please post your data, how much battery do you save after UV?
Click to expand...
Click to collapse
I understand where you're coming from, boy.
I don't have data at the moment though I wish I did. But to be honest, it'd be scrambled anyway since whenever I'm not working or mission critical when I need proven stability, I'm testing out all different sorts of settings leading to lots and LOTS of reboots and such!
That being said, anecdotally, I have seen improved battery life for myself but maybe it's a placebo and I could be wrong about it - I have been before in the past. I do feel though that under my normal usage scenarios, I am experiencing less battery drain. It's difficult to quantify though exactly what this is due to since I experiment with kernels, voltages and frequencies.
But if all I'm getting is a 2% boost, man - I'll take it! Like any modder, whether it's min/maxing in a game, working on a car or whatever else, every little bit of a parameter squeezed out is something.
I also feel that you're too caught up on a single aspect, the battery life thing, to the detriment of my overarching holistic goal - efficiency.
Originally I started undervolting and experimenting with frequencies because of thermal output. I had wanted to experiment with x16 MSAA settings, which led to my GPU needing 400MHz and 1200mV which led to lots of heating up which led to me experimenting with everything I could.
Efficiency is what I want. The best performance at the best speeds at the best battery life at the best thermal regulation I can manage.
Now I'm looking at energy efficiency. I'm seeing suggestions that 100MHz may not be as efficient as 200MHz on our Exynos because the tradeoff in frequency power usage isn't worth the longer time spent completing tasks. I'm also seeing that in some situations, a performance best governor targeting max freq may be efficient because less time is spent completing a task and a quicker return to sleep.
I'm just sharing what I'm doing and hopefully others can benefit.
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my GT-N7000 using xda premium
Wow, thats illogical makes me wonder the math behind it.
Sent from my GT-N7000 using Tapatalk 2
While I appreciate the effort thrown into this, I humbly acknowledge the conclusion is incorrect.
When you lower Voltage slightly, without affecting stability, you pretty much put a toll on the processor for extra "wear and tear" and reduce its lifespan. However, this comes at the reward of reduced current.
So, it should be saving you battery. Underclocking it (safely) is also going to save you battery. And the same thing with different governors, like interactivX compared to regular ondemand, by finishing off processes quicker and reducing the frequency and voltage quicker, and going into Deep Sleep quicker.
I don't have the means to run a Scientific Experiment to prove these claims, nor the time to conduct them. But the majority of "hackers" synonymously agree it saves a noticeable power. These include themers, kernel developers and the casual user. I don't think an educated MAJORITY can be incorrect to the scale of this test's claims.
I read in a post elsewhere that
"but you have to look at your battery.... it will increase battery drain... ( i set max cpu 96 mhz when screen is off and set cpu 1152 mhz when screeen is on... that saves battery an my hd2 is flying with speed when i am using it, and i decreased cpu voltage a little bit)."
Where do i find the settings to set max cpu to 96 when screen is off??
Thanks
Chris
cjbcjbchris said:
I read in a post elsewhere that
"but you have to look at your battery.... it will increase battery drain... ( i set max cpu 96 mhz when screen is off and set cpu 1152 mhz when screeen is on... that saves battery an my hd2 is flying with speed when i am using it, and i decreased cpu voltage a little bit)."
Where do i find the settings to set max cpu to 96 when screen is off??
Thanks
Chris
Click to expand...
Click to collapse
you have to install setcpu :good:
cjbcjbchris said:
I read in a post elsewhere that
"but you have to look at your battery.... it will increase battery drain... ( i set max cpu 96 mhz when screen is off and set cpu 1152 mhz when screeen is on... that saves battery an my hd2 is flying with speed when i am using it, and i decreased cpu voltage a little bit)."
Where do i find the settings to set max cpu to 96 when screen is off??
Thanks
Chris
Click to expand...
Click to collapse
or you use System Tuner
jstef said:
you have to install setcpu :good:
Click to expand...
Click to collapse
SetCPU's good. @OP, the SetCPU Dev is an XDA member and provides it for free from XDA so if you want to search for it and download it from the original thread you can. If you want to support him then please buy the app from the Play Store.
Also I personally feel that the advice you've been given is quite poor. 96MHz max with the screen off is definitely too low. I keep mine at 128 min and 4 something max, that way the battery usage is low but I get a fast response when I unlock the phone. With 96MHz max you're going to get tonnes of wakelocks. I tried to set mine to be at 128MHz once then tried playing music (with the screen off) and the phone froze, so I reckon with 96 max any background syncing or in fact any background processes could result in freezing.