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
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?
Just to let you know ahead of time, I know how to overclock & undervolt
My question:
Should I notice better battery life with 1400MHz @ 1275mV or 1200MHz @ 1275mV?
Even more basic - "With my voltages the same, but clocks higher, will I notice less battery life?"
My thoughts:
Not using more mV than a stock 1200MHz, so I shouldn't notice anymore drain
Should be finishing tasks faster - Saving Battery Life
So I shouldn't be noticing any more drain then stock, but it is faster.I do notice a difference in speed between 1200 & 1400MHz, otherwise I would just use 1200MHz @ my current stable of 1200mV.
Overclocking/Undervolting
You might want to grab SetCPU or Pimp My CPU from the market and memorize some different CPU profiles that would allow you to test and see the results of what you want to do.
I've never OC'd any of my phones before but was keen to try it on the Galaxy Europa as the 600MHz CPU seems a bit weedy at times. What settings would people recommend? Ideally I would like good on-demand performance, good battery life and no frying of the CPU
Thanks
I not guaranted for the results but you can try to raise to 710. I tryeid and its work for me on any of cyanogen roms.
I use smartassV2 with a frequencies range of 122-480 Mhz. For me a longer battery life it's more important than waiting a second! And if I need to play something hard I set max to an upper freq..
my 2 cent..
First of all, I am totally new to this forum.(I mean as an registered user)
Before that I always had the thing from the forum what I needed.
Now here is my question,
If i overclock the processor speed of my android device to a higher position, isn't it gonna take more battery power than usual?
Phone model: Xperia Live With Walkman
Boot loader: unlocked
Root Access: Rooted
Kernel: Rage 3.2
ROM: Real ICS r6
overclocking is going to drain your battery obviously.
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
saqib nazm said:
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
Click to expand...
Click to collapse
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Saimoon said:
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Click to expand...
Click to collapse
Power consumption = Voltage x Voltage x cpufreq x some constant for your device. If you OC (raise the cpufreq) you will have more power consumption and more heat generation because most of the power is dissipated as heat and the heat is what damages your cpu. It is probably impossible to kill your cpu in one go, because your device should shut off when it begins to over heat (this will look like a random reboot). But you will slowly degrade the over all performance of your cpu and eventually you get to a point where you see a lot of random reboots. So if you decide to OC you probably want to also undervolt as well. This is because power consumption (and heat) scale with the square of the applied voltage. One rule of thumb is that your maximum cpufreq is actually determined by the voltage. For example, my cpu is rated to be stable at 1 GHZ and 1200 mV, so when I OC and UV, I scale the cpufreq as high as I can go, as long as the voltage is not greater than 1200 mV, for me this is 1.5 GHz.
Also remember that your cpu governor will have a big effect on your power consumption and it is probably doing a good job keeping the cpu running in the low range of the cpufreq table, so you are unlikely to see big effects of OC or UV on real life battery consumption.
every chipset is different, even though the brand and model is the same. noone can guarantee you any safe value to overclock.
Thanks Giving!
Thanks Everybody for helping me out!
I am applying 1.402 GHz :laugh:
Overclocking is not the only thing you have to think of in order to improve your phone's overall performance. The most important issue for me is choosing the right kernel and applying the right governor + I/O scheduler. From my experience with Mini (i have tried ALL available kernels and most of ROMs) I can surely say that now with my phone (ICS .587, custom ROM + kernel) overclocked to 1.5 GHz battery with minimal use (20 mins calls, 40 mins WiFi per day) lasts at least 60 hours. When I bought my phone (GB, no OC, all stock) battery was struggling to stay alive for 24 hours with the same minimal use. Conclusion: first pick the right kernel and ROM, then OC.