Im now on the evaluation period of WM6 AKU.03, coz im looking for a good ROM which will save my battery. I used to install XCPUScalar in all ROM (auto scale coz i thought lesser batt) , i stop using SPB mobile already coz i know its power hungry, but still my life of Atom Pure is 24 hrs maximum. BUT AFTER REMOVING XCPUSCALAR ON MY ATOM ( AS SUGGEST BY CKAIDI) MY BATTERY LIFE BECOME GOOD... 70% now as of 3pm -last charge 7pm yesterday...i think now it will last for 2-3 days now
.........
Please post other TIPS TO SAVE BATTERY and have a GOOD BATTERY LIFE in our Atom
That's true... It eats up battery life (on my Hima and my exec WM5). seems like it's the same case with WM6. Oh well, nice to hear that discovery though. I dont overclock anyway.
Yeah, had the same experience with XCPUScalar. Why isn't there an overclocking program that doesn't do this? Better yet, why the hell does my video skip if I stream the sound over bluetooth unless I overclock? -.-
so now many agree to me coz they experience it too...now it is ver clear.
if you donot overclock then there should be no issue with the battery..
You should autoscale the frequency .. low freq when system is idle and high for power hungry applications..
Based my try out with many many 3rd party softwares, hard resetting to confirm. Things that eat battery power are down to 3 main things
=>> Hardware usage eg. bluetooth, wifi
=>> RAM
=>> CPU Load
For RAM we can do nothing about it. Be it your device start with 30mb free or 10mb free, it consume the same amount of battery as RAM always and never stop running.
For Hardware usage, you can reduce the usage to increase the battery hours. Go setting->Connections->Beam = uncheck the Receive all incoming beams.
Reduce the usage of camera, bluetooth simple as that
Reduce the backlight power will increase the battery by alot.
For CPU Load, this is the part why XCPUscalar can reduce battery life. It keep CPU running and running tell it what speed to run on and although it had little effect on the RAM but the CPU load is very very high. Try install batterystatus and see the CPU usage, it show 100% usage at all times. And if you have rltoday on your today screen, although it does not eat much RAM but you will see CPU usage jumping from 1-5% every sec as the clock's sec update. Activesync is another thing that always auto run in the background that eat your battery without you knowing it!! ALWAY KILL IT with your task manager!!
Therefore low RAM low resource program doesn't mean eat less power!!
CHeer!!!
kaidi
I dont think XCPUscalar just only eat the battery life. In my case, it save the battery.
When i set it to this :
Speed / CPU usage
a. 208 / 0-25%
b. 312 / 26-50%
c. 416 / 51-75%
d. 520 / 76-100%
As you see, in almost time, our ATOM will run with 0-50% CPU usage. With that setting, it use the lower speed and save the battery life. And when we run some applications which need the power CPU, Ofcouse we should lose the battery for the high performance.
XCPUscalar's not only overclock your CPU but also help you save the battery life!
shpy said:
I dont think XCPUscalar just only eat the battery life. In my case, it save the battery.
When i set it to this :
Speed / CPU usage
a. 208 / 0-25%
b. 312 / 26-50%
c. 416 / 51-75%
d. 520 / 76-100%
As you see, in almost time, our ATOM will run with 0-50% CPU usage. With that setting, it use the lower speed and save the battery life. And when we run some applications which need the power CPU, Ofcouse we should lose the battery for the high performance.
XCPUscalar's not only overclock your CPU but also help you save the battery life!
Click to expand...
Click to collapse
your atom will be slow then, im using autoscale before thats why.
most of our experience is other story, sorry my friend
generalriden said:
your atom will be slow then, im using autoscale before thats why.
most of our experience is other story, sorry my friend
Click to expand...
Click to collapse
Lower speed = lesser power (save batt) TRUE
Process of Pushing CPU to Lower speed = High CPU load (eat batt too)
So end up not saving much batt too. I suggest u try with and without XCPUscaler and see the batt life then you decide which is good or bad for you. I do keep it in my device but only run it when I'm playing resources demanding games
generalriden is right, why scale down ur device speed when it doesnt save you batt. AND i am confirm that jiggs's ROM is already very fast at aku3.3.3 and very very sure that in his wm6, you wont need it cos it will be damn fast!! yeah!!
CHeer!!
kaidi
I also recommend removing XCPUscaler at startup if you don't need to overclock your atom all the time (autoscale is useless to me). Just run it when you need it.
Lower speed = lesser power (save batt) TRUE
Process of Pushing CPU to Lower speed = High CPU load (eat batt too)
Click to expand...
Click to collapse
I do not use autoscale.
Listening to MP3s with GSPlayer over Bluetooth, EVEN AT FORCED 208MHZ with Scalar, the Atom eats battery faster than without it running, taking up about 2-3% more power in just half an hour (Note that the lowest automatic stepping on the Atom by default is 208mhz). Both with screen on and off.
And that's unfortunately with regular skipping, which only running at forced 624mhz solves.
Overnight on sleep mode, an Atom w/[email protected] consumes 1% more power than an Atom wo Scalar.
A little research on my part seems to show that Scalar doesn't adjust voltage supplied to the processor, only speed. This is why the slowest settings still eat more battery than leaving it alone - the processor is still supplied a constant voltage. Now, I'm not saying Scalar doesn't work - it does (which is especially great for Bluetooth streaming). However, it's not in the way you expect.
For now, I set it to perma overclock @624, and exit the program completely when I don't need it.
*waits for next version, hopefully with voltage stepping support this time*
Ei, i agree with that.. i just use scalar when i need more power from my atom like watching movies but i always close it afterwards..
Now with NEW WM6, my battery life is still good without XCPUSCALAR. Everything is doing well, 2 days before I recharge. With a good numbers of calls..
ryve25 said:
Ei, i agree with that.. i just use scalar when i need more power from my atom like watching movies but i always close it afterwards..
Click to expand...
Click to collapse
your right bro!
One more thing:
Dont forget to DISABLE the receive all beams in your atom. I forget this once then my battery life goes back for one day only. Now I disabled it, my batt life goes to normal again 2-3 days
generalriden said:
your right bro!
Click to expand...
Click to collapse
i'm using scalar just after i perform a soft reset, (it usually slow), then open all folders, (accesories, games, office mobile, etc), next, i open setting menu, move from personal tabs to system tabs and connection tabs, then i close the scalar,.
my batt drain not so quickly, because i dont use any apps like scalar,.
just dont install too many apps in your device, it will reduce your speed then,.
i think the speed of my atom while using scalar and not using scalar is same,.
not if play music or movie, it become slower,.
wat is the best speed to use when surfing the internet??!!
ghostrecon2050 said:
wat is the best speed to use when surfing the internet??!!
Click to expand...
Click to collapse
520 but you will not feel the difference...just dont use it
ghostrecon2050 said:
wat is the best speed to use when surfing the internet??!!
Click to expand...
Click to collapse
its up to you bro, you may use 520 or higher is fine, i think generalriden was right, nothing changed,.
As experienced by most people, without XCPUscalar the battery life of their ATOM is better.
Related
Is there a thread on over clocking the prophet ? tools? safely?
Battery Status! Nice tool and very stable!
http://forum.xda-developers.com/showthread.php?t=270751
BS rulez
I've set the CPU up to 273 mhz with BatteryStatus.
Absolutely stable.
Also the integrated tools in BS are verry comfortable.
Give it a try.
Greetings from Germany,
skylow
Sweet
Thanks Skylow
Ive over clocked it to 273mhz and wow is it fast& stable like you said ....thanks for the tip and greetz from Sweden
Hi !
I have also this speed for my S200, stable fast etc. no crash + I have dynamic overclocking "cpuscaler" settings.
min.:134 org.:195 max.:273
What do you think ? The oc is negative for battery uptime ?
Greatings from Hungary !
about 2 months ago, someone (I think it was Gullum) has noted that using cpuscaler has a negative effect on battery life as it prevents the device from going to sleep. I haven't used it ever since but also I haven't verified the effect. I always overclock my device to 273 and tap on the battery status today plug-in to set the speed back to 195 when oc is not needed (again, just as gullum suggested)
I have dynamic 123-175-208. Great for battery life for me.
amazing, after i overclock it to 273mhz im able to see the streaming video with no lags (live tv channels over wifi) !!!
im verry happy, watchin tvchannels on my prophet =)
I've heard that it has a bad effect on CPU and may cause CPU breakdown.
Is there anyone to verify that?
Bluetooth and overclocking
Hi!
Recently I discovered that if I overclock my devices (Prophet and Touch) I have a strange behavior using the bluetooth freehand environment integrated in my car. The WM Device connects and after a short time it disconnects suddenly. If I receive a call it takes a few seconds and it reconnects again - but you miss a few seconds of the phonecall!
With no overclocking everything works normal - bluetooth connect and disconnect if you leave the car.
(Btw my car is an Audi.)
Maybe somebody has the same problem.
Regards!
HAHA
skylow said:
I've set the CPU up to 273 mhz with BatteryStatus.
Absolutely stable.
Also the integrated tools in BS are verry comfortable.
Give it a try.
Greetings from Germany,
skylow
Click to expand...
Click to collapse
i use always at 286mh and till now i haven't problems with.
guys,do you use application based overclocking???
Baterystatus
tonydeli7 said:
guys,do you use application based overclocking???
Click to expand...
Click to collapse
Baterystatus for me
maxniper said:
Baterystatus for me
Click to expand...
Click to collapse
i know,i use it too but do you use the application based overclocking feature for phone&camera?? today i noticed some missed calls that showed up 3hrs later... I was using 2.20.21 Radio rom and CPU at 260MHz.Now i flashed 2.19.21 and CPU at 273MHz...and no problems so far..
Is that safe push it that way??
270 is not too much???
how about temps??
thks
CPU clock
I have a Jamin G4 and here is the overclocks that I tested:
I use Batt Status and Set CPUscaler.
Range from 99 to 286MHz is stable for Prophet (in my case)
- more than 286MHz which is 299 or higher PDA freezes.
- under 100MHz, 99MHz the screen has a light flick.
- I believe lower clock will save battery and higher clock may shorten CPU life.
- use Cpuscale to vary the cpu clock, especially when idle, it drops to lowest, hence save more battery and as active the cpu will step up to the max limit where you set your max
- Don't overclock unless you have to.
- My reference: CPUScaler from 99 to 260Mhz for normal use. And set to 286MHz unless you need to like games.
Eg: I have tested 286MHz and played Skyforce Reload for a few hours... beautifully... no problem
vnt said:
I have a Jamin G4 and here is the overclocks that I tested:
I use Batt Status and Set CPUscaler.
Range from 99 to 286MHz is stable for Prophet (in my case)
- more than 286MHz which is 299 or higher PDA freezes.
- under 100MHz, 99MHz the screen has a light flick.
- I believe lower clock will save battery and higher clock may shorten CPU life.
- use Cpuscale to vary the cpu clock, especially when idle, it drops to lowest, hence save more battery and as active the cpu will step up to the max limit where you set your max
- Don't overclock unless you have to.
- My reference: CPUScaler from 99 to 260Mhz for normal use. And set to 286MHz unless you need to like games.
Eg: I have tested 286MHz and played Skyforce Reload for a few hours... beautifully... no problem
Click to expand...
Click to collapse
Don't you have any problems with camera at this speed? Mine already at 221-247MHz has pure picture quality at highest resolution - some colors disapearing...
ZRimaZ said:
Don't you have any problems with camera at this speed? Mine already at 221-247MHz has pure picture quality at highest resolution - some colors disapearing...
Click to expand...
Click to collapse
The same happens on my NEO when I go beyond 221 MHz. My camera shows weired colors.
had a strange issue with batterystatus today... i tapped on 'minimize' and it appeared to minimize to the system tray... but i cannot get it to come back. tapping on the phone icon in the system tray shows a maximize option,,... but it does not bring the today screen plugin back... :/
anybody see this issue?
I got 12% battery drain in 17 hours, standby. I'm not a pro at android but I might give a little tut. on how to save battery life to the max. Atleast, it works for my P500 so it should work for you & for any other android device as well.
Uninstall every unnecessary app, including system apps (those apps, that does not mess up with the system stability - If you uninstall Email app, you will not solve your problems with Gmail app).. same with Messaging. That said, leave as minimum apps in the background as you can. App killer does not solve this problem, it just closes bg apps - they restart after some time. I'm using ATK (Advanced Task Killer), It usually kills 1 - 3 apps, so.. I have a minimum of apps running in the bg.
Basic stuff.. turn off your 3G, wifi, bg sync, gps when not in use. If you need to check your email, use 2G network only option, not 3G. Use 2G always when you don't need 3G speed. Screen brightness is not that important if you set it to anywhere below 70%. It should not drain the battery that fast.
Setcpu - profiles - governors--
My profiles are as follows
Charging - 480min - 748max
Battery <90% - 245min - 600max
Battery <70% - 245min - 600max (U can live with one profile for the battery, I have 2 in case I want to change the 2nd profile)
Screen off - 122min - 245max -- This is what saves my battery in standby.
The governors are ondemand for usage & conservative for screen off.
I'm using Void.echo rom with tapps & gapps modules, uninstalled everything I don't need.
I hope this helps If anyone has a better idea on how to save battery life, please share yours as well.
Thanks for your post, but actually most background apps don't drain battery. I have made lots of experiments (removing system aps, preventing autorun etc., and I don't see any major difference in battery life. So now, I'm on stock 2.2 and I'm now at 80% after almost 30h use: about 20 min talk, 10-15 min wi-fi (mail), 10-15 min EDGE. The latter by the way drains battery more than wi-fi. So instead of messing with system apps I recommend putting the phone in airplane mode during the night and as mentioned in the above post - not using 3G when not needed (EDGE has decent speed).
thats the why linux works !!! use all the memory u possibly can...These Microsoft *****es have changed the way computers were supposed to be used not reinstalling windows and other crapware all the time..Switch to Debian while its still time
And i use these settings
screen off 245-245 powersave (otherwise phone gets hot Its summer in india)
600-245 ondemand otherwise
kopchev said:
Thanks for your post, but actually most background apps don't drain battery. I have made lots of experiments (removing system aps, preventing autorun etc., and I don't see any major difference in battery life. So now, I'm on stock 2.2 and I'm now at 80% after almost 30h use: about 20 min talk, 10-15 min wi-fi (mail), 10-15 min EDGE. The latter by the way drains battery more than wi-fi. So instead of messing with system apps I recommend putting the phone in airplane mode during the night and as mentioned in the above post - not using 3G when not needed (EDGE has decent speed).
Click to expand...
Click to collapse
If there are many apps running in the bg, phone runs out of ram, so it tries to free up some space constantly. I think that drains battery, not the apps themselves. As well as the more cpu power is used, the faster it drains battery. Airplane mode shuts off any connection, so either that or you could just shut down the phone during night. Hmm you could tell me how to prevent app autorun, i have not looked into that.
btw juicedefender does wonders with the phones battery i had a 2% percent over night normal mode (not airplane) no 3g/Edge/Wifi/Bluetooth active and just sleeping
sarfaraz1989 said:
thats the why linux works !!! use all the memory u possibly can...These Microsoft *****es have changed the way computers were supposed to be used not reinstalling windows and other crapware all the time..Switch to Debian while its still time
And i use these settings
screen off 245-245 powersave (otherwise phone gets hot Its summer in india)
600-245 ondemand otherwise
Click to expand...
Click to collapse
True about windows & linux hehe. You havent tried 122-245mhz on screen off? Ofcouse, it lags even when i receive an sms, it's something like this - the screen turns on, then after 2 sec. i hear a notification, then after 1 sec. i see the sms but that does not make any problems for me, it's extreme powersaving
I don't get the point of airplane mode while you're sleeping.
If you don't want to get calls while sleeping, shouldn't it be better if you turn off the phone?
I had a good experience with JuiceDefender until now too. Last night my phone was 100% and no airplane mode while sleeping. It drained only 3%.
SoundTone said:
If there are many apps running in the bg, phone runs out of ram, so it tries to free up some space constantly.
Click to expand...
Click to collapse
From what I've read, Android doesn't swap. It'll just kill the background apps on it's own. I don't think there even is a swap unless you root, rom and create one on your uSD.
rapharias said:
I don't get the point of airplane mode while you're sleeping.
If you don't want to get calls while sleeping, shouldn't it be better if you turn off the phone?
I had a good experience with JuiceDefender until now too. Last night my phone was 100% and no airplane mode while sleeping. It drained only 3%.
Click to expand...
Click to collapse
It's more convenient, because the on/off process is quite slow...in contrast - airplane mode on/off is 3-4 secs. In airplane mode you can still use wi-fi. Last night the battery drained only 1%
i read somewhere that changing the CPU speed doesnt change the voltage, thus it does not affect battery life... anyone can confirm this???
As far as I can remember from school, a logic gate uses more power when switching, thus a higher frequency would also mean higher power drain (higher frequency = more switching of the logic gates), without voltage modification.
Voltage is changed in order to keep stability - higher voltage means a more stable logic signal, and a faster switching gate, and thus people reccomend using a higher voltage for higher frequencies/lower voltage for lower frequencies.
Thus, a CPU with so many logic gates does not operate just like a simple resistor. In fact it is worse, because when you use higher voltage AND higher frequency power drain is increased much more.
On the other hand, most modern CPU's simply deactivate CPU regions when idling, so, in case of our hardware (constant voltage) there should not be such a great difference when idling (most of the CPU is powered down). The only thing is for the phone to be REALLY idling (no background tasks eating too much of the CPU when screen off).
Basically, what this means is that if you want extreme power saving use a governor with 128MHz minimum and have as few background services as possible (or at least the ones that are there should be optimized for the least CPU usage).
Now I use the standard governor (248 - 600) and I thing my idle power drain is OK.
I guess I will test a governor that is plain 600MHz and one wit 320 or 480 as a minimum, in order to see if power drain is higher when using a lower lag configuration.
And, just as a guess, if background tasks are triggered by timers, a governor with just 600MHz (or 320 - 600 or 380 - 600?) could (just a wild guess) mean that background tasks take less time to execute, and leave the CPU to si more in IDLE mode, causing a very similar power drain as an extreme power saving governor. But this is just a guess, i have not tested it yet. And it also depends on what apps you have (what the apps do when phone is sleeping).
Basically, my best advice would be to watch the apps (after you install a new app, wait for a night to see if the new app causes a higher drain; if it does, search for another app that does the same thing)
spaic said:
As far as I can remember from school, a logic gate uses more power when switching, thus a higher frequency would also mean higher power drain (higher frequency = more switching of the logic gates), without voltage modification.
Voltage is changed in order to keep stability - higher voltage means a more stable logic signal, and a faster switching gate, and thus people reccomend using a higher voltage for higher frequencies/lower voltage for lower frequencies.
Thus, a CPU with so many logic gates does not operate just like a simple resistor. In fact it is worse, because when you use higher voltage AND higher frequency power drain is increased much more.
On the other hand, most modern CPU's simply deactivate CPU regions when idling, so, in case of our hardware (constant voltage) there should not be such a great difference when idling (most of the CPU is powered down). The only thing is for the phone to be REALLY idling (no background tasks eating too much of the CPU when screen off).
Basically, what this means is that if you want extreme power saving use a governor with 128MHz minimum and have as few background services as possible (or at least the ones that are there should be optimized for the least CPU usage).
Now I use the standard governor (248 - 600) and I thing my idle power drain is OK.
I guess I will test a governor that is plain 600MHz and one wit 320 or 480 as a minimum, in order to see if power drain is higher when using a lower lag configuration.
And, just as a guess, if background tasks are triggered by timers, a governor with just 600MHz (or 320 - 600 or 380 - 600?) could (just a wild guess) mean that background tasks take less time to execute, and leave the CPU to si more in IDLE mode, causing a very similar power drain as an extreme power saving governor. But this is just a guess, i have not tested it yet. And it also depends on what apps you have (what the apps do when phone is sleeping).
Basically, my best advice would be to watch the apps (after you install a new app, wait for a night to see if the new app causes a higher drain; if it does, search for another app that does the same thing)
Click to expand...
Click to collapse
I don't know about CPU's as much as u, but simple logical thinking helps here.. Low frequency + minimum of bg tasks = great power saving, I have now used the phone for 36hours without charge, 61% battery left. That is not only idling, i write about 50 to 150 sms a day & use the phone for other stuff too. So, those governors & frequencies i mentioned earlier in this post, helps a lot.
fransisco.franco thinks otherwise read the his post that contains the link to his rom devoid.francov6(ROM is cool btw and unfortunately i have a slow sdcard )
I think the first post is by far the best I have seen so far.
Sent from my LG-P500 using Tapatalk
Wow, only 1% all night?
I'll take a deeper look at your tips!
I use devoid.franco with franco.kernel v12. From all ROMs I've isntalled, it's the best: great performance and long battery life.
I get 5% battery drain in 7:30 hours (at night), without doing anything special, without running a custom ROM and without uninstalling apps. I just make sure GPS, Bluetooth, WiFi and data are off before going to bed.
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Markymarc206 said:
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Click to expand...
Click to collapse
I'm not entirely sure, but with your example, doesn't that depend how long you're going 30 or how long your screen is off at a crack? If you turn on your screen for 10 minutes for every 20 it's off, I think it would save your battery more in the long run.
You use more gas in the car analogy as you have to overcome a ton or so of mass driving at 30 mph. Changing clock speeds faces no such resistance, so it won't be the same with the phone.
yes, the acceleration doesn't really affect the drain. the fact you're running at a higher clock speed is the drain. you can adjust your steps and max speed, thus saving a little bit of battery. undervolting can help to, but the cpu usually draws so little power that the savings may go unnoticed.