Related
Was wondering what type of profiles people got setup on setcpu for some good battery durations oc'ed.
I'm currently running at 1417MHZ and only profile I have setup is screen off. 275 / 275 conservative. Priority is at 100.
Sent from my HTC Vision G2
I'm running at 1305MHz.
Screen off 245min/245max
Temp > 38.2 C 245min/768max
Battery < 15% 245min/768max
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
mejorguille said:
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
Click to expand...
Click to collapse
sorry im a newbie, how do you set the "on demand governor?" .and powersave bias, u get that from the advanced tab where it says "powersave bias (1-1000)" and just put 20?
donaliar said:
sorry im a newbie, how do you set the "on demand governor?" .and powersave bias, u get that from the advanced tab where it says "powersave bias (1-1000)" and just put 20?
Click to expand...
Click to collapse
Well the scaling governor is on the main page, right under the minimum frequency slider. You are only half right on the powersave bias: 20 would be 2%. So to do 20%, you need 200. Sorry if I wasn't clear.
Sent from my G2.
mejorguille said:
Well the scaling governor is on the main page, right under the minimum frequency slider. You are only half right on the powersave bias: 20 would be 2%. So to do 20%, you need 200. Sorry if I wasn't clear.
Sent from my G2.
Click to expand...
Click to collapse
Oh alright. my sampling rate is 50000. up threshold 95. ignore nice load 0. and powersave bias 200. does that sound about right? or should i change somehthing else? Thanks for the help!
Got my profiles at:
Screen off 245/245 priority 100
Temp > 102F 245/768 priority 80
Battery < 10% 245/245 priority 70
Battery <15% 245/368 priority 65
Battery <25% 245/768 priority 60
Charging/full 245/1459 priority 50
I just set these up so ill report back with how it turned out
mejorguille said:
Mines going at 200 mhz to 1000 mhz, on demand governor, and a powersave bias of 20%. No profiles. Why? Because to implement the profiles setcpu has to remain in memory. It does not feel slow at all and I'm getting terrific battery life.
Sent from my G2.
Click to expand...
Click to collapse
Questions:
Did you notice battery drain with setcpu in memory?
How is the battery temp?
Does the powersave bias mean that you will never scale to the peak value?
Had the phone off the charger since 11am.
Moderate call usage
Heavy texting
Moderate internet usage
Music for roughly 3hours straight
Wireless tethering on Xbox live for roughly an hour
At 9:15pm I have exactly 40% with my profiles from my post above
what does 245/768 mean?
nvm i got it
potentdro said:
what does 245/768 mean?
Click to expand...
Click to collapse
245 min, 768 max
So its a bit after 1am and just over 14hrs after a full charge. While using my profiles and info as posted in my above 2 posts along with 2hrs of GPS usage, light phone call usage, and heavy internet usage my phone finally died 14hrs later with the Gov module on conservative with posted profiles and OC'd at 1459.
Although abought 10min prior to it dieing I did attempt to submit this post from the phone but near the end of the post it froze up, showed the desktop and my battery notification showed 0% and the phone then rebooted itself but I got a bootloop on the "g2" screen and had to pull the battery to fix it.
After 10% battery level I was experiencing lagging and slowness while online so I'm assuming because of my profile setting of 245/245 at that battery level and what probably caused my bootloop.
*Edit: I must say I'm pretty impressed. I had my Nexus one alot more heavily modified than my g2 and only OC'd to 1113 with similar daily usage and I would have to charge it one time at some point during the day to last me throughout the night.
SRT102JZ said:
Got my profiles at:
Screen off 245/245 priority 100
Temp > 102F 245/768 priority 80
Battery < 10% 245/245 priority 70
Battery <15% 245/368 priority 65
Battery <25% 245/768 priority 60
Charging/full 245/1459 priority 50
I just set these up so ill report back with how it turned out
Click to expand...
Click to collapse
What do you have set up in "Main" tab?
Thanks. I'm going to try your settings.Battery life is disappointing...
Sent from my T-Mobile G2 using Tapatalk
Okay, so I got my G2 about two weeks ago, and have been running set CPU with these settings since then.
Main profile: 1478 max / 245 min
Screen Off: 245/245, Priority 100
Temp > 100.4 F: 368/245 Priority 97
Temp > 96.8 F: 768/245 Priority 95
Battery < 20%: 245/245 Priority: 82
Battery < 30%: 368/245 Priority: 81
Battery < 40%: 768/245 Priority: 80
Charging/Full: 1478/245 Priority 60
Charging USB/Full: 768/245 Priority 55
Charging AC/Full: 1478/245 Priority 50
On light use I've gotten almost two days, by light use I mean only a few phone calls or text messages and data turned off. On Normal use I've been averaging around 16 hours, and on heavy use I've been getting around 10 hours. Pretty good battery life, I'm pleased with it being my first Android phone, was a black berry user before this.
I have SetCPU set with all of these profiles, other then charging profiles and it seems that the "Screen Off" profile isn't working. I have it set to 245/245 and it still seems to be at 1497/245 because the battery gets hot and drains very fast (about 8 hours with literally zero use). It shows idle Cell Standby and Phone Idle taking up most of the battery (a combined total of about 85%) anyone know why it wouldn't be working properly?
SetCPU has SU permissions and profiles are enabled... Anything else?
Is SetCPU a lot better then the free CPU tuner? I know it's only 1.99, but I'm feeling cheap at the moment.
ScottRTL said:
I have SetCPU set with all of these profiles, other then charging profiles and it seems that the "Screen Off" profile isn't working. I have it set to 245/245 and it still seems to be at 1497/245 because the battery gets hot and drains very fast (about 8 hours with literally zero use). It shows idle Cell Standby and Phone Idle taking up most of the battery (a combined total of about 85%) anyone know why it wouldn't be working properly?
SetCPU has SU permissions and profiles are enabled... Anything else?
Click to expand...
Click to collapse
you have to make sure the priority is at a higher level than all the others...like 100
abenco said:
Is SetCPU a lot better then the free CPU tuner? I know it's only 1.99, but I'm feeling cheap at the moment.
Click to expand...
Click to collapse
You can get the full version on xda for free. It's nice to donate though.
Sent from my T-Mobile G2 using XDA App
need some help
my htc wont show any clock speeds past the 806mhz. ...any ideas? i tried to perflock disable and it says it is already..and in custom profiles it shows still only max up to 806
edt** read a custom kernal may be required...im on stock. thats probably why
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
akaine2001 said:
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
Thank Samsung for breaking ondemand on every sgs phone.
Sent from my SCH-I500 using XDA App
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
akaine2001 said:
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
Click to expand...
Click to collapse
You are doing something wrong. Conservative is not choppy on my device and the CPU will always ramp up faster than a human being can judge the response time.
Sent from my SCH-I500 using XDA App
My phone makes it the entire day with heavy use, this means about 20 - 10 min phone calls one or two lasting 30 min, texting my wife all day at work, checking emails, and angry birds for at least 1 hour a day i love that game but I suck at it lol. Something that I found is that the phone will last almost an hour of being on the phone after it hits 0%. In my pocket it lasted 4 hours at 0% the day before yesterday. I thought maybe this is on purpose so you have more then enough time to make it to a charger. When I first downloaded angry birds I played it for three hours straight with the screen at full brightness (i always keep it at full brightness, looks prettier that way) I know it was three hourse because it was while i was waiting at the hospital I got there a little before 7 and wasnt called until 10. Overall I am very pleased with the battery life of this phone not so much with other aspects but battery life and lag never came into my mind as a complaint for this phone, except with all the stock touchwiz stuff.
As adrynalyne said, CPU's scaling changes faster than human's perception. It's your phone or setting that's having an issue.
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
I meant "reliable" not trailer.
I get about 5 hours of screen time with little voice calls on wifi.
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge, having even made it to 44 hours on a very rare occasion and that's without setcpu profiles even set.
Wtf... my phone is brand spanking new and I get about 4ish hours of screen time on a full charge, with the lowest brightness + screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on.... wtf. This is running on conservative or interactive the whole time..... wtf!!! With wifi on and 0 extra screens or Widgets using launcher pro without animations... wtf!!!
Sent from my SCH-I500 using XDA App
+1... stock battery indicator is not accurate. Get the accurate battery mod.
soba49 said:
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse
Terror_1 said:
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge...
Click to expand...
Click to collapse
That's because you don't use your phone.
Go play NFS for 3 hours and get back to us.
MoShiBa said:
...screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on...conservative or interactive the whole time...
Click to expand...
Click to collapse
What's the screen filter app? Conservative and interactive? That's SetCPU?
I wouldn't worry about these guys coming in here saying they're getting 2 days of use either. They're not using the phone anywhere near as much as you. I've had 3 of these things and know 2 guys with them. They all got the same battery life. You don't see anyone posting any screenshots, do you?
Me and my gfs fascinate gets about same battery life in our apt and hers is still DI01 and i'm on DJ05... she has jts 11/16 kernel and i have the 12/21 voodoo5 and we get about the same battery life... dependent on how much we use the phone. .... so just use your phone, and charge it as necessary... its better for the type of battery we use anyways in our phones... **************************************************************************************closed.**************************************************************************************
I have been tweaking my G2 ever since I got it and it seems I found a pretty good configuration that gives me awesome battery life of 30 hours on medium light use and stock battery. Now I wonder if I can make it any better.
Ill post my configuration and hope that other will do the same to see if we can squeeze more battery life out of our phones!
CONFIG
SetCPU
screen on - 1000 Max, 122 Min, conservative
screen off - 245 Max, 122 Min, conservative
JuiceDefender/Setting Profiles
wifi on at home and work only
data off when wifi on
data off when screen off, toggle on for 1m every 30m
Home screen
three widgets
beautiful widets @ 4 hr refresh
genie widget @ 4 hr refresh
agenda widget
System
MIUI rom 1.7.22 www.miui.us
streamline5 kernel http://forum.androidspin.com/showthread.php/6555-Streamline5-Nightly-CM7-Test-Kernel-2.6.35.13
darkyy's memory boost script http://forum.xda-developers.com/showthread.php?t=998976
radio 26.0.03.26 with rmk's ril matcher http://forum.xda-developers.com/showthread.php?t=1021463
USAGE - medium light
< 10 calls approx 20 min total
< 50 text
< 15 emails
30 min navigation
45 min slacker radio
15-30 min gaming
30 min genie widget + browser on news
SCREEN - @28 HRS
If you can get more, post a screen, your config and usage. Sense hibernate doesnt count!
Pershoots kernel is the ultimate secret. And not to OC past 1.2 cause there is no noticeable difference once you go past that point.
Sent from my HTC Vision using XDA Premium App
For me it's called rmk40's virtuous g-lite v1.0.2. lol I regularly get 2~ish days without any special tweaking.
xsteven77x is right too, pershoot's kernel is by far the most efficient and nothing above 1.2 Ghz as the voltage requirements increase a lot i believe.
the secret to great battery life: don't use your phone.
xsteven77x said:
Pershoots kernel is the ultimate secret. And not to OC past 1.2 cause there is no noticeable difference once you go past that point.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
If you are using pershoot's kernal, what governer are you setting it to to max battery life? On demand?
Thanks
ill give pershoot a try
crevis24 said:
If you are using pershoot's kernal, what governer are you setting it to to max battery life? On demand?
Thanks
Click to expand...
Click to collapse
His only has on demand, performance, and user space (which I don't even know what that one does). I leave it on demand because performance keeps the CPU ramped up too often for good battery life with no noticeable improvement in actual performance lol.
Sent from my HTC Vision using XDA Premium App
Pershoot impressions @250min 1010max:
1) The ondemand has obviously been tweaked by pershoot to be VERY favourable to the 250mhz. This unfortunately makes the phone just very slight make a stutter step before ramping up to do a CPU intensive task.
2) The kernel is great when the phone is not regularily used, but seems to draw more power than Streamline5 when something is actually running but not requiring full CPU time as Streamline does provide other governors.
3) The kernel seems to take its time going into "deep sleep" 1 2 day uptime and only 17 hours of deep sleep.
Will continue the testing but seem like if you use the phone in a "medium light" usage, Streamline seems to be the better choice.
UPDATE: I am sitting at 64% @ 9h with pershoot...
im using a power sucking rom, virtuous unity. i just set my phone up so it will at least last a day with a little bit of battery left over. Here are my settings
Wake min: 245mhz Wake max: 1516mhz Governer:Ondemand
Sleep min: 245mhz sleep max: 356mhz Governer: conservative
also use juice defender with advanced settings and a auto memory killer with system tweaks for optimal battery life. i get about 12 to 13 hours.
evilcuber said:
im using a power sucking rom, virtuous unity. i just set my phone up so it will at least last a day with a little bit of battery left over. Here are my settings
Wake min: 245mhz Wake max: 1516mhz Governer:Ondemand
Sleep min: 245mhz sleep max: 356mhz Governer: conservative
also use juice defender with advanced settings and a auto memory killer with system tweaks for optimal battery life. i get about 12 to 13 hours.
Click to expand...
Click to collapse
i noticed you are with rogers as i am too, try "3g only" i had similar setup on a sense rom before and can get a few more hours out of it
i remember with sense i was getting 18 hours max. with the same usage outlined in op
lalalandrus said:
i noticed you are with rogers as i am too, try "3g only" i had similar setup on a sense rom before and can get a few more hours out of it
i remember with sense i was getting 18 hours max. with the same usage outlined in op
Click to expand...
Click to collapse
How do you set 3g only? If i set gsm only in settings, i only get edge networks
Sent from my HTC Vision using XDA App
evilcuber said:
How do you set 3g only? If i set gsm only in settings, i only get edge networks
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
in sense roms, two ways, gsm = 2g that explains why you only get 2g. 3g is wcdma
1) dailer -> *#*#4636#*#* -> phone info -> scroll to btm -> WCDMA ONLY -> reboot
2) menu-> settings -> mobile network settings -> network type selection -> 3g only
seems like i found another way to squeeze more battery life out, i extracted the virtuous rom's o/c daemon and uninstalled setcpu. will report with more data but so far everything is working better than setcpu (might be placebo effect)
I update the new radio 26.10.04.12
http://forum.xda-developers.com/showthread.php?t=970809
and matched rils
http://forum.xda-developers.com/showpost.php?p=16489050&postcount=807
and extracted from virtuous unity the performance tweak script for memory from /system/etc/init.d/10-virtuous_performance and the virtuous_oc from /system/xbin
went back to streamline 5 and install daemon tweaker
http://forum.xda-developers.com/showpost.php?p=16015003&postcount=43194
RESULT = 40 hours of battery! (same usage as first post of not more)
I don't know what's wrong with my battery...
I use CyanogenMod 7.1.0 RC1 with cpu OnDemand 245-1209 MhZ, just a few widgets (tajm, battstatt, desktop visualizer), no wlan and average usage. With this setup some people reported they got a battery life of 16-18 hours. I have to charge after 8 hours...with a brand new stock battery :/
lalalandrus said:
USAGE - medium light
< 10 calls approx 20 min total
< 50 text
< 15 emails
30 min navigation
45 min slacker radio
15-30 min gaming
30 min genie widget + browser on news
SCREEN - @28 HRS
Click to expand...
Click to collapse
In your screenshot, "Display" shows as only 1%. In my experience, unless you never actually turn on the screen, the display will tend to be the biggest power consumer. What brightness level do you have it set to? Can you please tap on "Display" and post a screenshot of that? I want to see how long your screen has been on during those 28 hours.
Even at the dimmest setting, an idle CPU @ 245 MHz, and in airplane mode, my phone draws 90 mA. About 60 mA of that is the display and G sensor. At full brightness, the phone draws a total of 220 mA, or 190 mA for the display.
On a stock 1300 mAh battery, 16% remaining is 208 mAh, meaning 1092 mAh has been consumed. 1% of that is about 11 mAh. At minimum brightness, that will run the display for 11 minutes (11 mAh / 60 mA = 0.183 h). At maximum brightness, only 3.5 minutes.
It looks like you had the display on for at least 90 minutes (only nav, gaming, browser), which means your display is only drawing about 7.3 mA, which I do not believe is possible, given the LCD panel in the DZ. That works out to only 27 mW (at 3.7 volts), which is roughly one-tenth the power draw of similar displays where I could find the specs.
So are you just leaving the screen turned off the whole time?
Longest time off charger for me is 2 days and 7 hours. My secret? MIUI with 1800mAh battery. 'Nuff said.
How long battery life do the people with those giant 3600mah batterys have? Just wonderin
Sent from my HTC Vision using XDA App
Pershoot sounds intresting.
How can I backup my current kernel just in case? NAND backup?
taob said:
In your screenshot, "Display" shows as only 1%. In my experience, unless you never actually turn on the screen, the display will tend to be the biggest power consumer. What brightness level do you have it set to? Can you please tap on "Display" and post a screenshot of that? I want to see how long your screen has been on during those 28 hours.
So are you just leaving the screen turned off the whole time?
Click to expand...
Click to collapse
most battery life brags come from people who dont really use their phones...
ill see if i can get actual screen on time. The point is not to brag rather to find the best config when people actually use their phones. That said 16 hours i was sleeping...
I've looked around and haven't found much. I anyone know what would be a good overclocked setting but save alot of battery?
Sent from my DROID X running MIUI
It varies from phone to phone, unfortunately.
Jrummy's "Android Overclock" is what I personally use...
My settings are:
Low Voltage 1.2GHz Preset (Set at Boot)
And I then enable profiles for some battery saving.
Profiles:
Screen off %100 priority 800MHz max 400MHz min.
Temp > 42c %90 priority 800MHz max 400MHz min.
Battery < 30% %80 priority 800MHz max 400MHz min.
Screen On %70 priority 1200MHz max 400MHz min.
This ensures my phone is at 800MHz while the screen is off or while the temp is high or while my battery is low (I like that one so I can draw the last little bit of battery out a bit.) I put the Screen On profile just as a fail-safe to make sure I revert to 1.2 max while the screen is on unless the other conditions are met.
You can even make your screen off profile all the way down to 400MHz max and min...but that just makes me nervous for some reason.
I never had a problem for the few days that I used it, but I'm a bit OCD with some things.
I was worried that I wouldn't receive calls or my alarm wouldn't work or something like that.
Hopefully this helps a bit.
Try that as a starting point, and adjust as you see fit.
Awesome this helps alot, i have a few profiles set, mainly so up like yours lol, ill looking the lower voltage cause before when i was overclocked I drained battery like no tommrow
Sent from my DROID X running MIUI
Spreadsheet of the Battery Drain Data
BATTERY DRAIN BENCHMARKS
VIDEO of how it's done! (Do NOT try it yourself!)
NEW: Lab study done by nathanson666 see here and featured on the XDA's portal and twitter here.
Summary of Results
#1 - With screen on, if the processor is Idle, 100MHz saves the most power.
#2 - Regardless of your choice of governor, even with extreme undervolting, you are not going to be able to increase your battery life by more than 2%. (Click here for explanation.)
For the instability introduced by UV, it seems a 2% increase in battery life isn't really worth it! REMEMBER rebooting uses so much power, a single one would more than undo any savings made by UV.
#3 - The most power saving governor is Ondemand. If you need a high performance governor, use smartassV2, which offers some battery savings.
#4 - This is one point that everyone ought to know, but I'm including because many people seem to believe in myths: if the screen is off, and the CPU is not active, neither deep idle nor UV will have any impact on battery life.
#5 - The matr1x kernel by mathkid95 mainly saves power through UV of the INT voltages. You may need to raise these if you have freezes/reboots with your phone (in addition to raising the ARM voltages). I found that a maximum of 1 mA can be saved through INT UV, regardless of whether the CPU becomes idle (or with screen off in deep idle), so this is a constant saving. However, it is a very small saving, and doesn't apply if the phone is asleep. Remember, reboots cost more juice than UV can ever save.
#6 - If you have an amoled display, black saves a great deal of power. After that, red. If you have a black and red theme, this is saving you power!
#7 - If you are determined to UV, I found that my phone would become unstable with UV settings that were fine when the battery was fully charged. So check what UV your phone can handle when your battery is nearly empty. Again I say: Because of the high likelyhood and massive battery drain that comes with a reboot, I highly recommend you DO NOT USE EXCESSIVE UV. Also remember, even with extreme UV, you will not increase battery life more than 2%
#8 - I found that with bluetooth or GPS preventing the TOP=OFF state, there was no additional power saving from Deep Idle, i.e. the TOP=ON state does not save power.
#9 - Kernels with the 65 fps hack will cause the screen to drain about 10% more power compared to the usual 56 fps.
#10 - Conservative does not save power! For further details and exceptions, refer to my new thread: here.
#11 - This is just general advice: if you are having very poor battery life, have you tried turning auto brightness off? And if you've got no reception, you might as well be in airplane mode, because searching for reception also eats battery.
#12 - If your phone can't handle OC (or UV for that matter) it's because components in general are built to cost, which means factoring in tolerances, and every chip is made as cheaply as possible within the specified tolerances. Outside of those tolerances, whether your chip can cope or not is unfortunately down to the whether you got lucky with the individual device that dropped off the manufacturing line.
ARM document on A8 fault tolerance: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0344k/Babhjhag.html
In fact I measured how UV in particular can cause errors, and saw in action the A8 using MORE power to correct the errors. From my spreadsheet:
At 100Mhz
mV 1500 4.92mA
mV 950 2.83mA (default mV)
mV 800 2.58mA (UV saves some power)
mV 750 2.96mA (Extreme UV uses MORE power)
Same test but with Deep Idle enabled:
mV 1500 1.91mA
mV 950 1.49mA
mV 800 1.29mA
mV 750 1.49mA (Same result again but with DI enabled)
Referenced from my spreadsheet starting row 41.
Recommended reading: http://everything2.com/title/wafer+yield
Stock voltages for reference:
ARM
1000MHz @1250mV
800 MHz @1200
400 MHz @1050
200 MHz @950
100 MHz @950
INT
1000MHz @1100
800 MHz @1100
400 MHz @1100
200 MHz @1100
100 MHz @1000
Summary of Power States by tchaari (thanks!)
After research, and some explanation from Steve Garon, it is clear that Deep Idle & CPU Idle are two completely different things:
1) Three main CPU states are implemented in the standard android kernel: NORMAL, IDLE and SLEEP
2) Ezekeel added an intermediate 4th state: Deep IDLE. This saves more power but only when the processor has a background task to run while screen is off. Bedalus proved here that it really saves a considerable amount of power in particular cases (e.g. music playing when screen is off). A minority of users are reporting some slight instabilities with it, but they may in fact be caused by things other than deep idle.
3) The CPU IDLE backport is a replacement of the standard android kernel drivers used to put the CPU in idle/sleep states by the new ARM methods integrated in the linux 3.2 kernel. This backport is theoretically supposed to improve battery life (with just the basic 3 CPU states). It is 100% stable but no power saving has been shown either in bedalus' amp meter measurements, or Harbb's overnight drain tests.
Where did the other benchmarks go?
All ICS ROM Benchmarks: this thread
Kernel Features and Benchmarks: this thread
CPU Governors and I/O Schedulers: this thread
Power Saving Governors: this thread
Thanks to all the developers, and a big shout out to: Harbb for his dedicated testing; tchaari for his motivation, great ideas and inspiration; jcolinzheng for the idea to test Deep Idle at fixed frequencies (genius); aLNG for links to interesting and useful articles; Steve Garon for demystifying esoteric kernel technicalities and his excellent kernel itself; everybody else who helped; and of course Ezekeel for making Deep Idle work, and for a stimulating debate!
Harbb joined in doing specific battery tests, using the phone's battery graph. This is based on the phone's own readings (State of Charge or SoC for short). It's not very accurate for an instant reading, but over time, it does become more and more accurate. Therefore, Harbb conducted some very long (10 hour) tests. To improve accuracy further, he waited for the level of charge to drop to around 80% before each test. This eliminates the another source of inaccuracy, that the first 10% of the battery tends to deplete rather quickly (due to normal wear and tear over its lifetime). In fact, I use Ezekeel's Battery Life eXtender (BLX) to stop the phone charging early (at a user defined level: I prefer 90%) to help slow the deterioration of the battery's maximum capacity by preventing heat damage caused as the battery tries to absorb the final dose of charge above 90%.
Harbb's Data
Harbb's spreadsheet
Here's a summary of Harbb's 10 hour test findings, in order of best battery drain:
- 15% - SmartassV2 with DI
- 16% - Conservative with DI
- 21% - Lazy with DI and SOMF
- 23% - Lazy with DI
- 36% - Conservative
- 39% - Lazy
- 39% - Lazy with CPU IDLE
- 44% - Lazy with Eugene's DIDLE
- 48% - Lazy with Eugene's DIDLE and SOMF
[where DI means Ezekeel's Deep Idle, and SOMF indicates that Screen Off Max Freq was enabled]
Power Misconceptions
1st Misconception:
There is a misconception about about 200MHz using the same power as 100MHz because the voltage is the same. There is an approximate formula for CPU power consumption:
CPU Power Draw = C x F x V^2 (where C=capacitance, F=frequency, and V^2=Volts squared)
Capacitance is a constant, so we can ignore it. Let's fill in the values for the lowest and highest frequencies:
100 MHz V=0.95 so V^2=0.9025
1000 MHz V=1.25 so V^2=1.5625
So this shows we have roughly an extra 70% power drain due to the voltage increase. However, the maximum frequency is 10 times the minimum, i.e. a 900% increase. So the dominant factor in CPU power drain is in fact the frequency. Roughly speaking, the frequency has 13 times more influence over the power drain than the voltage.
Therefore, the governor that keeps the frequency as low as possible for as long as possible will save the most power. This appears to be consistent with Harbb's finding that conservative saves the most power.
2nd Misconception:
Some people say that if they UV they can play a game on their phone for an extra hour. The most you can get from UV is 2% extra battery life (and it is not worth the reboot risk).
See post #4 for calculations based on the actual measurements taken from the phone.
Here is a more academic proof using the same formula from the 1st misconception:
CPU Power Draw = C x F x V^2 (where C=capacitance, F=frequency, and V^2=Volts squared)
Capacitance is a constant, so we can ignore it. Let's fill in the values for just the highest frequency with the stock voltages and then an extreme undervolt:
1000 MHz V=1.25 so V^2=1.5625 (stock volts)
1000 MHz V=1.2 so V^2=1.44 (the most UV my phone can handle with a fully charged battery)
This is an 8% saving. Happily, this exactly matches what I measured in the real test (see cell F62 in the spreadsheet).
Remember, only the CPU is saving 8%, the screen being on uses about 4 times as much power as the CPU even at its highest frequency. This reduces the power saving to at most 2%.
I am of course assuming the screen is on. For most users, this is correct, as their processor will not be under a heavy load unless the device is in use, and this almost always means the screen is on. If anyone can think of any circumstances where the CPU is under a heavy load, but the screen is off, and show that this happens to all users a high enough proportion of the time to be relevant to this calculation, please let me know. [/far fetched caveat]
Testing Methodology
Two videos are available, and note, a circuit diagram of test now linked within the battery benchmark spreadsheet. I've decided to share it publicly as I've now set up and run this test three separate times, with no major problems. So I've reclassified it from utterly reckless, to merely dangerously stupid. Do not under any circumstances try this with your own phone! You have been warned!
You cannot trust battery monitor widget. (More on that in the 4th post)
Here's a way to test Deep Idle without rewiring your phone:
Note - SOMF means Screen Off Max Frequency
Setup must be identical (apart from SOMF). Install battery monitor widget, set history update rate to 10 minutes (not particularly to monitor the battery, but just to act as a timer). Set to run without widget. Turn off all radios, turn off sync, turn off location services, put in airplane mode. Turn off any of Ezekeel's mods excepting (Deep Idle of course). Set up your music app to play the same song on a loop. Make sure all volumes are down. Phone must be in mute. Turn of auto-brightness just in case. Morfic told me that to avoid the problem of the battery not reporting itself properly you can begin both tests with the same charging procedure: charge while off overnight. In the morning bump charge for exactly one hour. Disconnect, boot, start music immediately. Power button to screen off. Leave phone for 48 hours (should be enough time to auto power off).
After the first test, check the history from battery monitor widget to see how long the phone was on for.
Repeat again but with SOMF set to on.
***
Here's more on metering the amps:
REMEMBER I ADVISE THAT NO ONE SHOULD ATTEMPT THIS.
If you're thinking this is something you'd like to try, you'll need:
1) An analogue multimeter or pure ammeter because a digital one will be difficult to read with constantly changing amps.
2) Two battery caddies with space for 3 AA batteries each.
3) Six rechargeable batteries. Use rechargable ones because the volts are a bit less, 3*1.35=4.05 - close enough to the spec 3.7
4) Lots of cables with crocodile clip ends
5) Some fine copper wire
If you're thinking of soldering something onto your battery, DON'T - you may accidentally make a short circuit that will be difficult to undo, and cause the battery to explode. Plus the heat of the soldering iron certainly won't do it any good. And don't solder anything onto your phone contacts, just carefully twist a few strands of copper wire around them, so they can be easily removed. REMEMBER I ADVISE THAT NO ONE SHOULD ATTEMPT THIS.
[Q] Why do I need 6 AA batteries when 3 would provide enough volts?
[A] My multimeter inserts a 600 ohm resistor into the circuit (yours may be less, and if so you will need different calculations to convert to amps). This resistor allows the multimeter to evaluate the amps by measuring the voltage drop across it. But the resistance will cause your phone to starve of power. Running a parallel battery to the phone will prevent it crashing when the voltage supply isn't sufficient for things like screen on+cpu max frequency+sdcard IO... This parallel supply should run directly to the phone, not through the multimeter. It can be disconnected when the screen is off, and will not harm the phone. Remember to reattach it before powering on your screen, or it is likely your phone will crash. I would advise to start with fully recharged batteries, and not connect the USB charger.
[Q] Won't the amps read half of what is actually being drawn?
[A] Yes, but you'll get the correct reading if you unhook the parallel battery.
[Q] Might I also be able to do that when the screen is on?
[A] Yes, but I recommend that you do that with everything possible powered off, wifi, 3G... etc... screen brightness minimum. Set your screen timeout to never, so that you have control over it with the power button. Always reconnect your parallel battery before changing from screen on to screen off, and visa versa. (Due to large power spike)
[Q] I want to try this. Should I?
[A] No, no-one should try this.
Miscellaneous
[Q] You claim you cannot increase battery life using UV beyond 2%. Justify yourself!
[A] When the processor is in use (i.e. not asleep or idle) UV does save a tiny amount of power. I tested with the most extreme UV my phone could handle. With a high performance governor, e.g. smartassv2, extreme UV would reduce CPU drain by 13%, or about 7 mA. With a governor that keeps the CPU frequency low, CPU drain would be reduced by about 18%, or 4.6 mA (weighted - see the spreadsheet starting cell H88).
Remember, these savings are limited to the processor, and only when it is active. For most users, this will mean the screen is on. For comparison, the screen on minimum brightness displaying black uses 9mA. On max brightness, displaying white, it uses 690mA. Let us assume some median value, ~350 mA.
A saving of 4.6 mA out of at least 350 mA (screen) plus 20 mA (CPU)
= 1.2%
A saving of 7 mA out of at least 350 mA (screen) plus 50 mA (CPU)
= 1.8%
So, regardless of your choice of governor, even with extreme undervolting, you are not going to be able to increase your battery life by more than 2%.
Articles and Documents
Diane Hackborn's article on the formula that produces the dodgy Android OS usage statistic in the battery menu:
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
(note, this bug is fixed as of Android 4.0.4)
Data sheet for the fuel gauge chip:
http://www.maxim-ic.com/datasheet/index.mvp/id/6621
Link to great article on SOC (State of Charge) http://www.mpoweruk.com/soc.htm >>> explains all the reasons why I don't trust battery monitor widget and the phone's own battery stats.
Great article on the difficulties of accurate metering (thanks aLNG):
http://low-powerwireless.com/blog/d...t-schemes-for-battery-powered-devices-part-1/
In the article DUT stands for Device Under Test
The implication is that DMM [Digital Multi Meter] voltage drop readings (to measure amps) take hundreds of milliseconds, a will miss instantaneous battery savings above this time window. However, I am using an analogue meter, the the needle responds to all current. Due to the mass of the needle, there is inertia to overcome, which provides a form of averaging.
Quote from the article:
"a GSM cell phone can have current pulses of 2 amperes that last approximately 500μs while the power amplifier is on and transmitting, and then drop back down to the milliampere level for the remainder of the 4.5 ms GSM cycle."
500μs is 0.5ms, so is 1 tenth of the 5ms GSM cycle. 2 amps at 1/10th of 5ms = average of 200 mA
When I ran the test with my equipment, GSM broadcasting uses at least 170 mA - see row 36. I think this is a nice proof that the analogue multimeter beats the digital multimeter hands down for dynamic amps (i.e. changes happening below the millisecond level.) I'm also very satisfied that my result is close to the result stipulated by the article. It improves faith that my readings are accurate.
[Q] What could add inaccuracy to the readings?
[A] The dBm scale assumes a resistance of 600 ohms, but the resistor has 3% accuracy which means it could be as high as 618 ohms, or as low as 584 ohms.
[A] Also, the scale is very small, so I've read the needle to the nearest fifth of a dB
Other articles (thanks aLNG)
A study of the mA drain of various components of a smartphone
http://www.usenix.org/event/atc10/te...rs/Carroll.pdf
An ARM presentation on unifying power management procedures in the kernel
http://elinux.org/images/0/09/Elce11_pieralisi.pdf
UPDATE: Undervolting the CPU tested (using nstools ARM+INT)
UPDATE: impact of different screen colours tested (amoled)
UPDATE: Running apps tested.
Please note, the running apps draw power for lots of different reasons, access RAM, CPU, I/O, Graphics, all use power, what's being displayed also uses power, eg a brighter 3D scene vs a darker 3D scene. But it does give an overall idea of what Amps might be pulled when you are using the phone normally.
Thanks for your hard works I'm impressed with the systematic research.
Many things just the theoretical possibility? just something we created in our minds...
mobile_pc said:
Thanks for your hard works I'm impressed with the systematic research.
Many things just the theoretical possibility? just something we created in our minds...
Click to expand...
Click to collapse
Indeed, i agree. Now, with no benefit to under volting, perhaps we can all suffer less reboots.
For kernel benchmarks and more, see here: http://goo.gl/mpeHI
I have undervolted and overvolted in GB with direct impact on the battery life. The fact your undervolting tests show absolutely no difference in battery drain make me think the settings aren't even applied.
Also this part of your spreadsheet seems to be a bit lacking. What frequency voltages were changed? 100MHz? 200Mhz? All?
The smallest voltage I've seen stable for 100MHz ARM seems to be 825mv, for example.
Cheers
polobunny said:
I have undervolted and overvolted in GB with direct impact on the battery life. The fact your undervolting tests show absolutely no difference in battery drain make me think the settings aren't even applied.
Also this part of your spreadsheet seems to be a bit lacking. What frequency voltages were changed? 100MHz? 200Mhz? All?
The smallest voltage I've seen stable for 100MHz ARM seems to be 825mv, for example.
Cheers
Click to expand...
Click to collapse
The frequency information is there in the first column, eg 400/400 means the min and max settings were both 400. If you're not changing frequencies you can get it down very low.
Yes, perhaps nstools is defective. However, i did get an instant reboot with the lowest setting. Want me to do a repeat in GB?
For kernel benchmarks and more, see here: http://goo.gl/mpeHI
So undervolting does nothing? That seems strange ...
Also what about using juice defender? Worth it ?
italia0101 said:
So undervolting does nothing? That seems strange ...
Also what about using juice defender? Worth it ?
Click to expand...
Click to collapse
Yeah, does nothing to save battery. I don't know what juice defender is?
Sent from my SNES
polobunny said:
I have undervolted and overvolted in GB with direct impact on the battery life. The fact your undervolting tests show absolutely no difference in battery drain make me think the settings aren't even applied.
Also this part of your spreadsheet seems to be a bit lacking. What frequency voltages were changed? 100MHz? 200Mhz? All?
The smallest voltage I've seen stable for 100MHz ARM seems to be 825mv, for example.
Cheers
Click to expand...
Click to collapse
Okay, I went ahead and tested Gingerbread (carbon, ICS themed Oxygen 2.3.1, android 2.3.7) using franco's last kernel for GB. Starts at row 329.
Neither extreme undervolting nor overvolting had any impact on the battery drain.
Juice defender is a battery saving app that basically d/cs the data and wifi when screen is off and reconnects when screen is on... also when screen is off it uses schedules to turn wifi/data on to receive stuff and sync
italia0101 said:
Juice defender is a battery saving app that basically d/cs the data and wifi when screen is off and reconnects when screen is on... also when screen is off it uses schedules to turn wifi/data on to receive stuff and sync
Click to expand...
Click to collapse
Sounds sensible enough to me!
Sent from my SNES
Some reserves
bedalus said:
2 - If you use NStools to undervolt, don't bother. No gain to be had from undervolting either ARM or INT voltages. I tested this to the extreme. Check the spreadsheet, near the bottom. (Tested in both ICS and GB).
Click to expand...
Click to collapse
First, I want to thank you for all your efforts in the benchmarks especially for the battery drain. However, I kindly have some reserves on this. Maybe undervolting does not save so much power at idle but at higher loads, energy can be surely saved. Besides, maybe the energy saved is too minimal for your analog multimeter and it can't be noticed on it.
This is the theory :
The switching power dissipated by a chip using static CMOS gates is C·V2·f, where C is the capacitance being switched per clock cycle, V is voltage, and f is the switching frequency,[1] so this part of the power consumption decreases quadratically with voltage.
Click to expand...
Click to collapse
source : http://en.wikipedia.org/wiki/Dynamic_voltage_scaling
And this a more practical reference about a study made by tom's hardware on AMD Athlon clock, voltage and power consumption. I think it can be generalized (at a smaller scale) for our ARM processor in the nexus S:
It’s only when we change the voltage that we're able to significantly save more power--about 13 watts lower consumption, or a total of 20 watts compared to running without power management. That's a savings of 25%.
Click to expand...
Click to collapse
source (you may also read the entire article. It is very significant):
http://www.tomshardware.com/reviews/processor-power-management,2453-9.html
Other scientific papers and studies can be also found stating that undervolting saves power.
Kind regards.
I also appreciate all the hard work you have done for testing, on both kernels and everything, but im going to "gingerly" throw my hat in with tchaari here...
The only way to actually test battery drain would be to attach a multimeter and let it drain all the way on every test, using every kernel, and every setting - multiple times to omit false positives. Obviously this is beyond the acceptable timeframe it would actually take to accomplish. anyone would go insane sitting there waiting.
there are nuances here that will affect results regardless how carefull one is. the program itself might suck juice, your kernel/gov choice affects how the program runs too...also the status of your battery makes a difference. is it past it's half cycle life? etc..then the multimeter is another massive factor. there are many many different types not saying yours is bad, but over the years as an electrician ive played with some that are $20 as well as $2000 - and they are a far cry from each other even though they both do the exact same functions!
The undervoltage is a prime example. there are so many factors that will affect the results it's unusual to see your sheet having barely any differences - when we know that undervolting does actually save you battery under loads.
so it's nice to see a massive sheet like you did, as it does give a good start point reference - but it should be used not as chipped into stone law either.
Thanks for taking the time to give a great, no excellent base line to work off of though and preform more intense testing if people would like to go that far.
t3xboar said:
there are nuances here that will affect results regardless how carefull one is. the program itself might suck juice... then the multimeter is another massive factor. there are many many different types not saying yours is bad, but over the years as an electrician ive played with some that are $20 as well as $2000 - and they are a far cry from each other even though they both do the exact same functions!
Click to expand...
Click to collapse
What program? I'm playing a loop of silence in the music app to keep the processor awake.
The multimeter I'm using isn't fancy, but even if it's reading 10% down, it's doing it for all readings, so it's a fair comparison.
t3xboar said:
The undervoltage is a prime example. there are so many factors that will affect the results it's unusual to see your sheet having barely any differences - when we know that undervolting does actually save you battery under loads.
Click to expand...
Click to collapse
What makes you say we know this? I want to get to the bottom of this, so i need to see a concrete source.
Tchaari posted the capacitance times volts squared times frequency formula. I know this, and when I adjust the ARM voltage by more than half a volt, i expect to see this:
0.8x0.8=0.64
1.5x1.5=2.25
That should be 3.5 times as much power use.
Now, double the power in the dB scale is a difference of ~3dB. 3.5 times ~5dB. And I can notice a change of 1/5th of a dB on my multimeter's scale. There was no change. Here is how i tested.
Start music. Go into nstools, set ondemand with min and max at the same frequency. Go to volt, select the lowest possible voltage for that freq and exit. Screen off, measure amps. Screen on, nstools, volts, highest volts this time, exit, screen off, measure amps. Result: identical.
Seriously, if you have a background in electronics, have a go yourself (NO ONE SHOULD TRY THIS THEMSELVES) and get back to me.
In theory, it should save power, but it isn't. I'd love to be able to say why. At this point i don't think it's a problem with nstools, because i got a crash the second i put the volts to minimum when i was testing on Steve's kernel in ICS.
Sent from my SNES
As contradictory as some of these results may (or may not) be, bedalus is in the right with his methodology as far as i can see. Though at this point nothing should be set in stone. Not yet at least.
A few people saying with UV that they get more screen on hours, up from 3 to 6 hours. I'll check amps pulled (with both UV and OV) with screen on next.
Sent from my SNES
bedalus said:
A few people saying with UV that they get more screen on hours, up from 3 to 6 hours. I'll check amps pulled (with both UV and OV) with screen on next.
Click to expand...
Click to collapse
That is a good idea bedalus but it seems that undervolting gain is very minimal instantly. In a long period, it can make some difference in battery life...
I have also many doubts about how sensitive your amps-meter is? Since we are dealing with small values in our case, maybe a more sensitive device can measure some difference that yours can't...
Anyway, your work is very interesting and as Harbb said : At this point, nothing should be set in stone yet.