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?
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?
Hey, back again on a question about overclock an HTC Thunderbolt rooted with CM7 and Tiamat kernel. Anyways, I can overclock it to 1.9ghz pretty stable and suprisingly good battery life ( believe it or not ), get's kind of hot when charging though about 107 farenheit and 99 on daily use w/o it being plugged in. I was trying to get it to reach 2.0ghz, I know some of you will say its not that big of a jump from 1.9 to 2.0 but that's not the point, I am using SetCPU and Incredicontrol, and I just can't seem to keep it stable because I set it 2.0ghz and put the SVS volt in Incredicontrol to the high which is 1550 If I remember correctly, It's pretty stable but as soon as I press the lock button it freezes up and I have to take battery in/out. Any suggestions ? Thanks.
I'm not the most brilliant when it comes to overclocking (Having similar problems), but you have to keep in mind that 2GHz is double your stock clock speed, so yes, that is a big push. My recommendation is to find a low-voltage kernel that has Smartass V2 and try again.
Hmm wel l i do have smartass v2 but using smartass v1 with 1.9ghz overclocked no problems yet maybe il just stay at 1.9 but then again ill keep trying 2ghz until i get bored lol
Watoy said:
Hmm wel l i do have smartass v2 but using smartass v1 with 1.9ghz overclocked no problems yet maybe il just stay at 1.9 but then again ill keep trying 2ghz until i get bored lol
Click to expand...
Click to collapse
...or cook your device. At the voltages you describe, I can all but promise you that you're slowly killing guy your phone. You're talking about a 5% gain in clock for a performance gain of less than 2%. Your phone probably isn't stable at all at 2ghz. Smartass ramps up to policy max at screen on, unless you change it, and it probably locks before the display even comes on. If you like your phone, stop. The return you get probably won't even do 1.9ghz, so count yourself lucky at that. Mine won't run that fast.
loonatik78 said:
...or cook your device. At the voltages you describe, I can all but promise you that you're slowly killing guy your phone. You're talking about a 5% gain in clock for a performance gain of less than 2%. Your phone probably isn't stable at all at 2ghz. Smartass ramps up to policy max at screen on, unless you change it, and it probably locks before the display even comes on. If you like your phone, stop. The return you get probably won't even do 1.9ghz, so count yourself lucky at that. Mine won't run that fast.
Click to expand...
Click to collapse
What is a safe voltage for 1.9ghz? I think right now it's at 1300-1450 I forgot, SVS(I don't know what the SVS is, just says on top of Incredicontrol). It's very stable and the phone doesn't even run hot, no random reboots or anything like that, but since you said the voltage thing I am worry now, can you explain some more? With my overclock right now which is as I said 1.9ghz, Am I still killing my phone? My battery life is pretty good except when watching videos, goes down very fast but other than that it's good. Btw what are good temps for my phone?
Watoy said:
What is a safe voltage for 1.9ghz? I think right now it's at 1300-1450 I forgot, SVS(I don't know what the SVS is, just says on top of Incredicontrol). It's very stable and the phone doesn't even run hot, no random reboots or anything like that, but since you said the voltage thing I am worry now, can you explain some more? With my overclock right now which is as I said 1.9ghz, Am I still killing my phone? My battery life is pretty good except when watching videos, goes down very fast but other than that it's good. Btw what are good temps for my phone?
Click to expand...
Click to collapse
That kind of voltage tends to stress the silicone. If 1450 is your top limit, that's not too bad, but I probably wouldn't venture past that. Your governor is keeping it from running at that speed most of the time. Most of the heat you feel the phone give off is the battery. You really don't feel much of the heat from the CPU. Too much voltage is going to cook your CPU well before it begins to show temperatures on the battery sensor. As far as temps go, pretty much anything under 135F is ok. The battery will be the first thing to fail as temperatures rise. The SoC can tolerate much more. SVS just stands for Static Voltage Scaling, as opposed to HAVS, Hybrid Adaptive Voltage Scaling, which I don't think any Tbolt kernels support.
I don't get the purpose of that level of overclocking. My phone is snappy smooth and basically SAFE at 1.15 or 1.2
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
RevosFTS said:
I don't get the purpose of that level of overclocking. My phone is snappy smooth and basically SAFE at 1.15 or 1.2
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
Click to expand...
Click to collapse
The core is designed to run at 1.5ghz (though the caches and memory arent fabbed to, really) so running at 1.5 or 1.6 isn't a big deal. More than that and you're really challenging it.
Hi!
While playing around with my hero more and more I've been experimenting with different roms, kernels and cpu clock speeds. While doing that I've been trying to keep below 710MHz, but after a while i thought "what the hell..." and kept it at 710MHz for a long time. At 710MHz my hero seems to work fine, a little faster then it used to be, and a little more battery consuming. My noob question is since most of the post in here says " be careful going all the way up to 710MHz" almost no one suggest trying anything above, am I doing something wrong? Is the increased performance and the decreased battery life all in my head? I'm using setcpu 2.24, been tested on most roms here, both flykernel 12 and 13 and LV 5.0 and LX 6.2 ++++, and of course i always give it SU.
also, if i'm doing this right, my phone does not get particularly hot at 710MHz, so could i go even higher?
There are differences in devices. Mine for example freezes totally at 710.
I have been using my overclocked hero for a year now, running at 730mhz with no problems, my maximum is 748mhz but approximately after 20 minutes of runing at so high freq the hero was doing really some weird things..730mhz is my ok freq where I can run it without freezing up or any errors, the back cover gets little hot only when doing hards tasks..oh and, dont enable auto apply overclock on boot when testing the highest overclock, did that you dont want to be there when hero freezes up I just pulled out the battery...
I can overcloking my Hero with no problem upto 748.8mHz. If i use 760mHz my Hero are freeze...
Overclocked to 729, it works fine but eats battery like anything. Speeds above 614 are too much for our Heros poor battery.
I'm overclocking to 691, cause it freezes at 710.
If the cpu is really running at 691 for a while it goes upto 40°C. Just use a temperature profile in setcpu.
691 Mhz - 176 Mhz too, moderately stable.
Mine is stable up to 729 MHz
Mine freezes at 710MHz. For everyday use i have 614/352 Screen On settings
172-691Mhz Smartass is good idea. My hero is freeze at 729Mhz.
I am not that aggressive, 352 - 633 MHz. So far very stable.
690 is optimal for me, it does not freeze at 710 but it becames slower if I do a benchmark.
264-633 smartassv2 works perfectly for me. I found at 710 it was a little faster/smoother, but my battery lasted less than a day - using gps at 710 would also cause my phone to reboot.
Mine works till 691, at 710 freezes after few minutes.