Finally figured out how to over clock my CPU/GPU on One X with CM11 KitKat rom. Bumped the CPU to 1809 (what I researched is stable) and GPU to 512. My Antutu benchmark score dropped from low 17k's to mid 13k?
Help please!! Could running Trickster Mod App interfere with Performance option in CM11....?
Trickster Mod isn't interfering with the performance, it just means your phone won't perform at its peak with those settings. Higher CPU/GPU clocks don't necessarily mean better performance, I've seen this through extensive personal testing. Dial the settings back to stock and increase the clock speed incrementally while testing after each increase, you'll reach a point where performance suffers, dial it back one notch and there you have your "peak" settings.
Unless you're doing some really hardcore gaming on your phone it's all pretty pointless. There's no advantage to overclocking in everyday use of the device other than to say it's overclocked, you just can't notice a difference, any noticed difference is more than likely a placebo. I actually underclock my CPU to 1242mhz to improve battery life and have zero negative response whosoever, no matter what I throw at it.
Sent from my Evita
I agree with Tim here. I'm running cm11 on power saver mode, and it runs just fine. A little slow opening and closing apps, but buttery smooth for everything else.
Sent from my One X using xda premium
Related
Anyone using "performance" scaling for daily use while overclocked at 1.5 ghz?
If so what its your experience? Battery, stability, heat, force closes,...?
I just rooted and overclocked last nite and it is great, but Iam a little hesitant to go full "performance" for daily use. I love the speed but apprehend some risk. What is your experience?
Performance governor isn't really "scaling." In *nix OSes, performance governor just runs it at the maximum speed 100% of the time. There's usually absolutely no point in doing this.
If you're concerned with the performance of "on demand," just turn the "sampling rate" down in SetCPU's Advanced Tab. On my Nexus S, I find 30,000us with an 85% up threshold to be the best balance between battery life and performance.
Basically, just play around with the settings a bit. Performance is generally not the way to go, unless you're benchmarking.
Setting up treshold can be very important to make the device respond faster. I use 70% on my desktop Ubuntu because the default value (95%, definitely too high!) caused problems with HD movies.
This is a question for those who have overclocked their Xoom. How much is overclocking to 1.5Ghz affecting battery life?
Overclocking would be the only reason I would root right now, and I am trying to make up my mind on whether to do it.
My battery life is better after using setcpu to overclock. The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom) with setCPU you are extending the top end of how fast the CPU can go. The clever bit is you can also tell your xoom to slow itself down and go very efficient when the screen is off or if the chipset gets too hot (which it never has). If you do go for it I recommend using setcpu using interactive scaling (prioritising the user interface) and whack the max speed up to 1500 and the min speed down to 217 mhz
I wouldn't recommend setting screen-off profiles at the moment. It seems to lead to some strange issues once in a while.
That said, because you're only going to 1.5 GHz when needed, battery life doesn't really suffer. Additionally, at least in my usage, my screen uses ~70-85% of my battery. This is even during heaving gaming, where the Tegra 2 really has to work hard.
I wouldn't worry about its effects, personally.
MrGinger said:
The reason is that the tegra2 chipset scales the performance based on whether it's needed(IE, when you're using your xoom)
Click to expand...
Click to collapse
All CPUs do this, not just Tegras.
Re scaling, never said otherwise I've never had a problem with screen off profile. Maybe just lucky
I am loving my Android experience so far coming from and iPhone 4. I am running LeeDroid and have been playing around a lot with SetCPU. At this time, I am not concerned about battery as of yet. I am asking this question in regard to optimal, blazing fast performance with minimal hiccups.
I have done Quadrant testing at various min/max CPU levels. I had excellent results at 1804 high 904 min. However I had to yank the battery after not being able to unlock the device.
For profiles, real basic, again I am not concerned about battery charge life ATM. I have it set to revert to stock performace (1036/245) if the battery temp reaches 100F.
With the screen locked, I have it set to 499/245. All of my settings are using the "ondemand".
I would like to know what an ideal minimum is for PERFORMANCE as well as ideal max (1804? Highest might not always be fastest?). I got amazing results with Quadrant full benchmark with settings of 1804/499. This also caused a lockup when trying to unlock the device though. Maybe because there was a conflict with my lockscreen max setting? I would think the app would put priority to the lock profile though.
Also, does this phone have a built in CPU temperature sensor that I could utilize with a CPU temp widget?
Thanks for reading my lengthy ramblings.
Ray
A. This thread belongs in the q&a
B. Some inspires can't that much of an overclock, might seem like yours is one of them
C. You might get more help if you post in the leedroid thread
Sent from my Inspire 4G using XDA Premium App
Thanks for your excellent A, B, C format response. I'll head elsewhere.
I am loving my Android experience so far coming from and iPhone 4. I am running LeeDroid and have been playing around a lot with SetCPU. At this time, I am not concerned about battery as of yet. I am asking this question in regard to optimal, blazing fast performance with minimal hiccups.
I have done Quadrant testing at various min/max CPU levels. I had excellent results at 1804 high 904 min. However I had to yank the battery after not being able to unlock the device.
For profiles, real basic, again I am not concerned about battery charge life ATM. I have it set to revert to stock performace (1036/245) if the battery temp reaches 100F.
With the screen locked, I have it set to 499/245. All of my settings are using the "ondemand".
I would like to know what an ideal minimum is for PERFORMANCE as well as ideal max (1804? Highest might not always be fastest?). I got amazing results with Quadrant full benchmark with settings of 1804/499. This also caused a lockup when trying to unlock the device though. Maybe because there was a conflict with my lockscreen max setting? I would think the app would put priority to the lock profile though.
Also, does this phone have a built in CPU temperature sensor that I could utilize with a CPU temp widget?
Thanks for reading my lengthy ramblings.
Ray
Not all Processors are created equal and therefore some can OC to 1900+ and some cant overclock at all. Most will be in between. Sounds like you are over doing it. I clock mine to about 1400 when charging. I have had it to 1700 without an issue at all, but I don't find a need to be faster then 1400. When screen is off I actually tell it to go to 250MHz. Sometimes its alittle slow to "wake". But it saves mucho battery. When just on battery I am running at about 1250. Been this way for about 3 weeks. Not an issue.
I have never had to yank my battery and quite frankly if I did I would never run it that high again. You are going to burn it up running it at that speed. Nothing over 1500 for extended periods. 1800+ for showing off maybe? But that's kinda dumb too.
I have not read about any built in temp thing so can't really answer that.
I don't know what kind of power hungry apps you guys are running, but I run mine underclocked to 906MHz. Snappy as ever.
I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.