Related
I'm really struggling with battery life at the moment. Has anyone got settings I can use to save on battery life in SetCpu? Profiles etc
+1
I'd like to know too.
I would also like to know =[ my battery dies wayy too fast. I have the darkstone froyo build on my htc hd2 phone energy rom. Any programs or SETcpu settings that will help out?
If your on a rom with preflock disabled then you can underclock.
The only thing you need to change in setcpu really is to make a profile for screen off and set it to 245 (or whatever is the lowest I can't remember) both max and min (leave it on demand, or interactive if your rom has that).
This should give you about 10-15 hours longer battery life
so i wouldnt have to make any other profiles like battery? temperature? stuff like that? should i get rid of my green power and advanced task killer?
No you can keep them (well I don't know what green power is....)
The other profiles are mainly only needed if your OVERCLOCKING, however if your not touching the default max (main profile) then your not overclocking (1ghz).
To save power you UNDERCLOCK which setting a lowered screen off profile would do.
If your slowing the CPU down then the temperature will not rise, so that profile is not needed.
And you don't need to slow the phone down when your using it so none of the others are really needed either.
No you can keep them (well I don't know what green power is....)
The other profiles are mainly only needed if your OVERCLOCKING, however if your not touching the default max (main profile) then your not overclocking (1ghz).
To save power you UNDERCLOCK which setting a lowered screen off profile would do.
If your slowing the CPU down then the temperature will not rise, so that profile is not needed.
And you don't need to slow the phone down when your using it so none of the others are really needed either.
i think im kinda get what you're saying (sorry im kind of slow) so i had just deleted my other profiles and made a screen off one have it set to max all the way right and min all the way left, on demand, priority 100. Now on the main screen i think i touched it cause i read somewhere for max all the way to the right and min all the way to the left. This is confusing lol
The settings I have for my Desire:
Default:
Conservative 245-998
Profiles:
Screen Off - Priority 100 - Powersave
Charging/Full - Priority 50 - OnDemand 245-1305
Battery < 30 - Priority 0 - PowerSave
Running along side JuiceDefender, battery life is acceptable to me
jdeezyboo said:
so i wouldnt have to make any other profiles like battery? temperature? stuff like that? should i get rid of my green power and advanced task killer?
Click to expand...
Click to collapse
Remove everything, setcpu included
Sent from an ipho.../ NETWORK DOWN-PLEASE DON'T TOUCH THE PHONE
Remove everything, setcpu included
Sent from an ipho.../ NETWORK DOWN-PLEASE DON'T TOUCH THE PHONE
__________________
When Chuck Norris holds the Iphone4, the signal increases
That totally defeated the purpose of my question and others before me. Our battery lifes sucked without any programs so now we delete it?
I used darkstones froyo for awhile too. Battery drain killed it for me. I had no luck with anything. Changed to a nand build and its much better. Apparently SD builds just use more battery. With the SD froyo I could never stay below 60ma a few times would drop to less than 10ma but just not consistent. I lost about 8% an hour in sleep mode. Give a well designed nand build a go. In sleep I hover AT 4ma. My battery with Moderate use easily last the day, heavy use (multiple calls, emails, and browsing for an hour or two) still does require a recharge
Im using carbon ara theme with pcb just turn data off wen aint using it via toggle and have a profile for sleep in set cpu for min and max of 245 and from full charfe at 7am by 6 pm im still 65%. Thats using fb checkin email playing angrybirds and checking the forum
Sent from my HTC Desire using XDA App
I also use advanced task killer and kill all tasks wen not in.use
Sent from my HTC Desire using XDA App
bad idea as you are actually making your battery work more by doing that.
Sent from my HTC Desire using XDA App
Hello folks,
first post, pleasure to be part of the group
Arc LT15i, 2.3.4, doomkernel#11, 4.0.2.A.0.42
more than 10 seconds to wait to be able to answer a call
takes 3-4 sec to light the screen (it's an eternity when you have to answer), and often first appears the unlock screen, then after seconds the sliding green botton.
really sorry for the noobhood, but any ideas?
thanks a lot
Cavin
I updated my phone to latest official firmware and i alos have this lag, but not that much. It takes 2 seconds for the screen to show who is calling and to be able to answer it, and it takes around 0,5 seconds when pressing the unlock button to light up the screen.
same problem when i was using stock rom
but when i moved onto MIUI,the phone is pretty fast and answer screen appears pretty quickly
Which CPU scheduler are you using? I have seen that using smartass or other schedulers which reduce the clockspeed on standby can reduce the responsetime of the answer screen.
setxperia raise the clockspeed on incomming call to make the response a bit better.... ;-)
Sent from my MT15i using Tapatalk
Thanks guys for answering
You're right! It's due to the clock's settings. May be, i'll come back to the former firmware any hints?
upgrading clock's frequencies works well, but drains battery faster (and this setup requires already a lot of energy ).
using "no lock" app, gains few secs
last night came up with the same good idea of using the incall profile
i noticed that using a too low min clock freq, the device is less reactive, although using "interactive", "smartassv2" or "ondemand". "scary" profile seems to work slightly better on incall reactivity. any experience?
Thanks
Cavin
If you use smartass (v1/v2), there's no need to set any profiles for screen off. The governor will stick to the lowest available frequency.
Smartass v1 used to have wake issues (on HTC Desire, at least), but v2 seems to be fine, I'm using it on the Arc S, I haven't experienced any lags with either stock or CM7 ROMs.
I'm not familiar with Setxperia and its settings, though, could something be set wrong, causing poor performance? Just a guess...
thanks
i noticed some lags with a very low min clock (e.g. 122), disappearing setting min at 8-900mhz (max 1.2ghz)
actually dunno why, but if i succeede in changing the rom discovering what to wipe, gonna tell you more
Cavin
Ok .. so, seeing many questions w/o real answers regarding the power consumption of the GN under various circumstances, I decided to create some testing conditions and generate some data.
The original idea and requirement started on Franco's kernel development thread but as this topic might be of interest I decided to create its own thread.
Test conditions:
- device: Galaxy Nexus i9250 - GSM version
- rom: bigxie's rom
- kernel: Franco kernel
*************************
1. IDLE test
2. MP3 play test
3. DISPLAY test
4. CPU Power test
5. Still image test
6. MKV play
7. Additional Display, MP3 play, YouTube and TuneIN media streaming
*************************
If you have any suggestions of tests you would like to see, please drop me a PM so I can make a list and implement them (depending on my possibilities).
*** Original post was heavily modified due to inaccurate measurements. The replacement posts linked here are the ones that matter ***
Why exactly did you decide not to run tests with wifi and 3G/2G, like grabbing and playing a youtube video?
That was the plan but seeing that I don't have enough resolution for this run, I decided to keep the test as simple as possible.
In few hours I'll do a more detailed run, with 1mA reasolution and I'll include online media too, as well as wifi versus 3g power comparison. It looks like a long friday night for me
// sent from my green robot //
ro_explorer said:
It looks like a long friday night for me
Click to expand...
Click to collapse
Haha! Well... I'm already looking forward to those higher res tests... don't forget to include 3G vs 2G as well, because I'm really not sure if there is much of a difference since you take so much longer to load... oh, maybe not a late friday but an early saturday?
thanks for doing these tests, its a great idea and cant wait for more results.
Yes. Thanks. Definitely need more.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Thank you for support guys .
I've managed to build the new test circuit. I can now read the current with 1mA steps.
As a first set of measurements with the new setup - idle power .
Kernel and rom - see first post.
HotPlug function is a feature of Franco's kernel to turn off CPU 1 while phone is in sleep mode (in case some of you are wondering). It is supposed to be a feature to save power while phone is idle.
Voltage constant at 3.9V over all set.
1. AIRPLANE MODE - any governor, both 350-1200 and 700-1200 frequency range:
1.1. HotPlug OFF - 3 mA steady
1.2. HotPlug ON - 3/4 mA - the multimeter was unable to choose a value
So .. in airplane mode, the standby power is between 11.7 - 15.6 mW
2. 3G mode,WiFi - OFF, interactive governor
2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
2.2. Freq: 700-1200, HotPlug - OFF - 4/5-8 mA
2.3. Freq: 350-1200, HotPlug - ON - 4-8 mA
2.4. Freq: 700-1200, HotPlug - ON - 4-7 mA
3. 3G mode,WiFi - OFF, conservative governor
3.1. Freq: 350-1200, HotPlug - OFF - 3-8 mA
3.2. Freq: 700-1200, HotPlug - OFF - 3-8 mA
3.3. Freq: 350-1200, HotPlug - ON - 3-7 mA
3.4. Freq: 700-1200, HotPlug - ON - 3-6/7mA
4. 3G mode,WiFi - ON, conservative governor
4.1 - 5GHz WiFi
4.1.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
4.1.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA
4.1.3. Freq: 350-1200, HotPlug - ON - 4-7/8 mA
4.1.4. Freq: 700-1200, HotPlug - ON - 4-6/7 mA
4.2 - 2.4 GHz WiFi
4.2.1. Freq: 350-1200, HotPlug - OFF - 4-8 mA
4.2.2. Freq: 700-1200, HotPlug - OFF - 4-8 mA
4.2.3. Freq: 350-1200, HotPlug - ON - 4/5-8 mA
4.2.4. Freq: 700-1200, HotPlug - ON - 4/5-8 mA
When NOT in airplane mode, my phone has data and sync ON, and (over night at least) only Google services are being synced - gmail, g+, gtalk.
The measurement with data on/off, sync on/off are identical to the data on, sync on, when there is no activity that is. So, the the only way the phone will consume more power when data/sync is on is exactly when an event is being synced .. the rest of the time the radio being idle, identical with data/sync off.
Conclusion regarding IDLE (in my case at least): best power saving while phone idle is with WiFi off while screen off (or on only when plugged), conservative governor, 700-1200 freq. range and HotPlug - ON. Of course these values are experimental and are specific to my device but the numbers are looking reasonable.
I did not take any video of the above measurements because it was really boring .. put device at sleep and wait for it to really sleep (about 2 minutes for each test). But I'm attaching a photo of the test bench .
... to be continued with awake tests with video capture also ...
Awesome work!
I can think of one more scenario that's worth testing: when the screen is off but there is a wakelock keeping the CPU awake. This would give us a baseline of CPU awake but screen off, which would tell us exactly how much juice is going to the screen and CPU when the device is on.
Would MP3 play in background meet your expectations?
ro_explorer said:
Would MP3 play in background meet your expectations?
Click to expand...
Click to collapse
Wakelock but idle would be ideal I think, but actually an MP3 playing might be perfect if you can compare MP3 playing with the screen on in one of the previously tested states and MP3 playing with screen off. Then some simple subtraction should tell us everything we need to know.
I'd like to be able to calculate how much is used when the CPU is awake due to a wakelock, and how much power is saved by getting out of that wakelock ASAP to get back to power collapsed state. It might turn out that ideal screen off profile is 920 or even higher.
Good stuff. Glad someone is taking their time to collect this data.
Something to try: Loop a program to browse site content with white (light) heavy colors vs black (dark) heavy colors.
excellent info. if anyone's interested we did a similar test with the nexus one where we were able to use the actual resistor in the fuel gauge chip within the battery. so we did various testing scenarios, and that phone pulled very high currents. seems like our galaxy nexus is actually more efficient with some of those screen tests.
here's the link, prob boring though since it's not our shiney new GN.
http://forum.xda-developers.com/showthread.php?t=998544
This is my simple, yet efficient circuit (and quite precise I might say).
As you can see, the sense resistor is quite small not to interfere with normal operations and I think the 1% tolerance is making it perfect.
MP3 test
This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no
Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).
I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.
Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU
Values from this second test:
~0.62W consumption with screen ON, autobrightness, showing homescreen
~0.72W when mp3 is started (70% volume, headphones)
~0.155W with screen off/playing mp3
~0.05W with screen off, no mp3 play and a software waiting for input (in this case, poweramp's lockscreen)
~0.011W in standby - airplane mode.
The above values are with 350-1200MHz freq range, conservative gov.
The frequency CPUs have used during screen-off play was 350MHz. If I'm increasing the min. frequency to 700, the average consumption is increasing with an average of 2-3mA.
ro_explorer said:
This is the mp3 failed test: http://www.youtube.com/watch?v=LOwnFcro0no
Why is a failed test? because the 3g, data and sync were on, so, beside the small 5-10 mA instability, there was a syncing action resulting in totally messed up readings while playing with screen off (1:42).
I hope now people will understand why these tests should be done in airplane mode. Having all the data at hand, one can easily add different values to get an approximation of his particular situation.
Now .. with airplane mode ON, I have a second mp3 play test: http://www.youtube.com/watch?v=IXHy0Ru45XU
Values from this second test:
~0.62W consumption with screen ON, autobrightness, showing homescreen
~0.72W when mp3 is started (70% volume, headphones)
~0.155W with screen off/playing mp3
~0.05W with screen off and a software waiting for input (in this case, poweramp's lockscreen)
~0.011W in standby - airplane mode.
Click to expand...
Click to collapse
Perfect. Thanks so much for taking the time to do this. I had been trying to come up with a semi-scientific way to measure some of this stuff and you just hit it out of the park with this.
Do you know what frequency the CPU was at when playing the MP3 with the screen off?
Display test
This is the hi-res (1mA) display test: http://www.youtube.com/watch?v=cqSQ5QE-4S0
Values (with device awake, of course):
- auto brightness, relative low light conditions, dark homescreen: 162mA / 3.87V = 0.14W
Maximum brightness:
- white screen: 380mA * 3.8V = 1.44W
- red screen: 287mA * 3.83V = 1.1W
- green screen: 295mA * 3.82V = 1.127W
- blue screen: 327mA * 3.81V = 1.246W
- gray screen (50%): 240mA * 3.84V = 0.92W
- black screen (but awake): 147mA * 3.87V = 0.57W
aron7awol said:
Do you know what frequency the CPU was at when playing the MP3 with the screen off?
Click to expand...
Click to collapse
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.
ro_explorer said:
No, but I can find out .. all I have to do is to turn on recording on system tuner pro application ... Let me check this and I'll update the MP3 test post with the cpu frequency data. I can tell you that I was on conservative, 350-1200 MHz settings, HotPlug ON.
Click to expand...
Click to collapse
Thanks, my guess is that this CPU can play an mp3 at 350 MHz just fine
I've solved the mistery ... above post updated.
The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.
ro_explorer said:
I've solved the mistery ... above post updated.
The cpu was in 350MHz state ... and (of course) if I'm setting the min freq. to 700, it will stay at 700. The 700MHz min value will add 2-3 mA on average during m3 play.
Click to expand...
Click to collapse
Sorry to keep bothering you for more, but do you also know the CPU usage playing the mp3 at each frequency?
The final question I'd like to be able to answer is: Is getting to idle faster at the expense of using a higher frequency to get there beneficial?
I guess to answer that question we need to separate how much power the CPU uses at 100% CPU usage at 350 MHz, 700 MHz, 920 MHz, etc.
Does anybody know what the ondemand governor uses as it's default screen off settings. By that I mean if I have profiles disabled in setcpu and just allow the ondemand governor to determine frequencies and I leave the max min freq's at default values, then what happens when the screen is turned off?
I know the cpu will eventually go into deepsleep but there are inconsistencies.
If I dont use setcpu and just allow the default kernel settings (im on doomlords btw) to determine the frequencies, then when I turn the screen on after leaving the phone for a while, the cpu speeds up very quickly and the system becomes responsive before I can ever notice.
If I use setcpu however, with a screen off profile set to ondemand, max 245, min 120, then it still takes achieves deepsleep as often as not using setcpu but there is a noticeable lag and stutter for about 5-10 seconds as I turn the screen on to use it again.
Does anyone have any idea;
A) Why this happens?
B) What is the default screen off behaviour for the ondemand governor on doomlords kernel.
you may need a program like system monitor to record your % of cpu activity, im on stock rom and i have it at 100 - 300 mhz max when screen off, i used the program while im asleep to see if there was issues but there was none or lag when the screen turned on
there isnt any inconsistency with mine,but then again i removed alot of the programs i dont use to have very few programs running in the background,playing music with this setting doesn't cause issues
i havent read alot into his kernal yet,guess you wait till someone that has more knowlege in his rom.
[v03 onwards] added new CPU governors:
InteractiveX
Savaged-Zen
SmartAssV2
I recently have bought a Defy plus.
Stock 2.3.4 ROM used so far with LauncherPro.
Doing OK with battery life so far, but now starting to look at the CPU over/underclock capabilities. Started with Antutu CPU Master and CPUTuner also.
One thing I haven't seen as yet is the ability to underclock clock below the min 300MHz.. or even whether this makes sense. I guess undervolting is the other option, but perhaps someone can guide me here.
use setvsel to oc/uv, thats the easiest and best app imo. although underclocking your phone below 300mhz may cause instability and makes the phone wake up much slower in my experience.
sent from my cm7 defy...
I agree with zakoo2: Going below 300 will not be a good idea and it will most likely not improve your battery life in any significant way:
My Defy is running between 300-600Mhz and right now the LCD screen is the biggest consumer: Changing the (auto-)brightness settings in CM7 will do *much* more to your battery life than going below 300mhz.
What really helps saving battery life: use setvsel and leave the minimum clockspeed at 300MHz, but set a vsel value of about 20 for it, then scroll down and enable "limit to vsel1 while screen is off".
Also, going below 300MHz will probably make the phone sluggish when waking up from sleep like if a call comes.
Sent from my MB525 using XDA App
im just change from 300mhz to 330mhz lowest. 300mhz will make my defy+ lag when got incoming call. im using smartass govenor.
I heard some guy out there got 80 MHz and running, but I'm not sure of it.
As people said, clocks lower then 300 MHz would make your phone run horribly while waking up (i.e., it would take a long time for the screen to turn on when receiving a call, and you would probably miss it most of the times). Setting 300 as VSel1 and limitting to it while screen is off (2nd-init enabled bootmenu has this option, and downloading SetVSel - free at Android Market - will also do the trick if you have a rooted, but stock ROM) will help you save a lot of juice. Using a lightweight launcher (I personally recommend MetroUI or Zeam) also boosts up batt saving. Last, but not least, setting brightness to auto or minimum (using frosted/mat screen protectors will help a lot while using the phone under direct sunlight) also saves loads of charge.
Obviously, using a light ROM (I think Barebones may be a good option, though I think it's not suitable for me, but it's a personal matter) and calibrating your battery in a monthly basis (via manual calibration - you can find how to do so by googling -, wiping batt stats in custom recovery and/or using the batt calibration app included in most ROMs - but also free at AM) also help.