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?
Related
I suppose that this is a well known fact, but anyway: the StrTrk can be overclocked just like the HTC Wizard (with omapclock).
I'm running mine now at stable 240MHz (instead of 180).
Makes quite a difference.
Cheers
hrb
It will revert back to 180Mhz after you close the phone after a few minutes.
Has anyone figured out how to make the changes stick
is overclocking too risky for a smartphone? does cpu burn or just freeze when overclocked to its limit?
I'm using 252mhz when playing 3D games (no java, they are working nice at 180 mhz anyway) then down to 180mhz.
thx
Im using my startrek with WM6.1 Pro with the battery status plugin now Homescreen ++. I have it underclocking to 143mhz 180mhz is nominal 260 is my high setpoint and 273 is my temporary boost. Its dynamic based on cpu load. Works like a champ get about 3 days charge with my extended battery. Dont know about stock battery time. Besides the phone getting a little warm its fine to overclock. Just make sure its stable at whatever speed you set it at. It will lock up immediately if its not stable 240-252 is safe and stable for most on this phone for continuous use. When underclocking you may notice scale lines appearing on the screen like it has a reduced refresh rate.
My3125 also can keep @252mhz...
haha
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.
Hi guys!For the last few days(that I have my Hero rooted that is) I'm using VillainRom 10 as my everyday ROM and have tried some others.Anyway,that's not the point!
Being one of the lucky ones whose Hero can happily overclock to 768 I came to use RaduG's extremekernel and ben39's no-bfs no-whining kernel.With the second,while configuring OverclockWidget I saw that it gives a 848MHz option with auto-detect frequencies.Is it possible?I'm not asking about stable daily use,but even for some minutes for benchmarking?Has anyone achieved it?Without making their phone catch on fire that is!
And secondly,why are we all using linux 2.6.29(for total newbies I mean the kernel) while there is 2.6.32-33-34?Can't a newer kernel be compiled for use with the Hero?Newer kernels would provide native ext4 support and would probably prove to be better overall.
Oh,forgot one more!I am currently running on minimum 176MHz-maximum 749MHz(after I got a couple reboots with 768 I abandoned 19MHz for stability) with screen on and minimum 123MHz-maximum 384MHz with screen off.Should I give it a higher minimum frequency?Sometimes it lags when waking up,the screen turns on but shows nothing but black and turns off again or it turns on and everything is distorted,colors are completely distorted,background is upside down and some other unnormal things,but everything is alright when turning the screen off and back on again.Does it have to do anything with the frequencies I am using?I am running on VillainRom 10.3.
Now I have set the minimums to 160 and 190 MHz to see what happens!
Thanks in advance!
About the high MHz... I have done it with over 800 but don't max it out at 848 or your phone will freeze but anything below works And that screen **** I've also had and it has something to do with the high MHz (don't know why) but it helped me to set the MHz lower when the phone sleeps in SetCPU And at last about the kernel... It runs on the old one on Android 2.1 but in 2.2 it will be upgraded to ....33 or ....32 don't remember which...
-------------------------------------
Sent via the XDA Tapatalk App
Thanks for your reply C0mpu13rFr34k!
I know Eclair is running on the old kernel.I just would like to know if it is possible to compile a newer kernel for it.
As for the frequencies...Are my settings alright?Some too high or too low?The way I see it there is a big gap between maximum and minimum frequencies when screen on which results on the CPU working at low frequencies most of the time,thus sacrificing performance.But it helps with battery life and presumably this and the screen-off underclocking reduce the overall damage caused to the CPU by the overclocking,which is said to reduce the CPU's total lifetime by 50% or more,depending on how much you overclock it.Working at 749 I sometimes get a nice 43 degrees Celsius while charging,but that's only when charging.Average temperatures are 30 for standby and 37 with screen on(average,can be lower or higher).
And one more question.At 800+ how hot does it get?Will it be stable for some minutes to do some basic benchmarking or nah..?
Thanks!
tolis626 said:
Thanks for your reply C0mpu13rFr34k!
I know Eclair is running on the old kernel.I just would like to know if it is possible to compile a newer kernel for it.
As for the frequencies...Are my settings alright?Some too high or too low?The way I see it there is a big gap between maximum and minimum frequencies when screen on which results on the CPU working at low frequencies most of the time,thus sacrificing performance.But it helps with battery life and presumably this and the screen-off underclocking reduce the overall damage caused to the CPU by the overclocking,which is said to reduce the CPU's total lifetime by 50% or more,depending on how much you overclock it.Working at 749 I sometimes get a nice 43 degrees Celsius while charging,but that's only when charging.Average temperatures are 30 for standby and 37 with screen on(average,can be lower or higher).
And one more question.At 800+ how hot does it get?Will it be stable for some minutes to do some basic benchmarking or nah..?
Thanks!
Click to expand...
Click to collapse
If your phone is stable your settings are just fine even though your phone might have problems waking up if the low freq is under 246MHz (something like that) Also if you want better performance you might want to test some other freqs and then benchmark... Sometimes it makes a BIG difference if your phone is running at 691MHz or 710MHz For me my phone works like **** if it runs at 749MHz but it works like a dream at 729MHz (I think the difference was 0.5-0.8MFLOPS) Im also pretty sure your temp is fine (OC shouldn't make your phone that much hotter since the voltages in all ROMs are adjustet). If you should compile a newer kernel you would first of all need a .32 (.33?) from HTC because of hardware capabilities and im sure there's is A LOT more things devs need to compile such a kernel but i don't know to much about kernels I don't really know that much about 800+ because I only did it once and benchmarked it (MFLOPS was **** and i couldn't get them high at all) actually it slowed down my phone but you should test it. Maybe your very lucky and your phone can take it
Well,I have set it to 653min-749max with screen on and 160min-352max with screen off.Testing only!But it runs like a dream if we don't take into account a small lagging when I turn the screen on and it has to change frequencies!But it's great so far.Will see how battery life goes!By the way,tried 800,806 and 848MHz,but none worked.It didn't crash or something,it just wouldn't change to it and stayed at lower frequencies(low as 246).
Thanks for your time anyway!
And a small question...How bad does overclocking affect the CPU's life?I asked around and was told that the maximum overclock for desktop PCs is 20-25%,depending on the CPU,while needing special cooling systems,and that it can reduce the CPU's life up to 50%.Given that we overclock over 40%,how bad do we damage our CPUs?
tolis626 said:
Well,I have set it to 653min-749max with screen on and 160min-352max with screen off.Testing only!But it runs like a dream if we don't take into account a small lagging when I turn the screen on and it has to change frequencies!But it's great so far.Will see how battery life goes!By the way,tried 800,806 and 848MHz,but none worked.It didn't crash or something,it just wouldn't change to it and stayed at lower frequencies(low as 246).
Thanks for your time anyway!
And a small question...How bad does overclocking affect the CPU's life?I asked around and was told that the maximum overclock for desktop PCs is 20-25%,depending on the CPU,while needing special cooling systems,and that it can reduce the CPU's life up to 50%.Given that we overclock over 40%,how bad do we damage our CPUs?
Click to expand...
Click to collapse
I haven't heard to much about that actually but from what I've heard it shouldn't damage the CPU at all because of the voltage adjustments but i find that very hard to believe... Talking from personal experience my phone runs as smooth now as it did when i bought it so my CPU has probably taken minamal- or no damage at all and I got it when it had just come out here in Denmark (Europe) which is about 8+ months i think? So I wouldn't care to much about the lifetime since It's probably like 1-2 years and by that time I don't think people are using the Hero anymore Keep up the good work with optimizing and your welcome
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.