So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
zetsumeikuro said:
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
Click to expand...
Click to collapse
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
zetsumeikuro said:
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
Click to expand...
Click to collapse
Benchmarks do have a some good uses... while comparing different phone models with benchmarks can be iffy, it can give an overall insight, (things like graphics capabilities with very GPU extensive games) but in the end user experience and daily use are the real judges.
Where benchmarks can be of the most use, is when comparing changes to the same phone model.
E.G. Comparing performance impacts of AOSP vs Sense, overclocking and under-clocking, and de-sensing/bloat removal.
When used for these reasons, you can get a really good feel for how changes are affecting your device overall. Even then, benchmarks are not the be all end all, and user experience is still important. As you may introduce lag or other performance issues that do not show up in benchmarks.
Which temp root method are you using? Mine isn't staying rooted long enough for me to justify using setCPU at all...
The new version and the one that comes with the newest clean tool stays until reboot.
Marine6680 said:
The new version and the one that comes with the newest clean tool stays until reboot.
Click to expand...
Click to collapse
Thx for the info, guess I must still be using the outdated method. I'll run the latest version of Scott's Clean tool and give it a shot.
Izeltokatl said:
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Click to expand...
Click to collapse
Please let us know what settings you use that work for you.
I generally stay temprooted unless I'm going to be away from a charger for a bit and need BT (since you can't turn BT back on after temproot). I wouldn't have SetCPU autostart on boot (since it won't ever be able to get root access immediately after boot).
Meanwhile, I also set it to conservative and will see what that accomplishes.
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
This kernel apparently does work with SetCPU. I've confirmed using other cpu monitoring apps that the clock speed changes are capped.
I own 7 android phones, and have been rooting, overclocking, undervolting each and every single one of them (well one I still cant get rooted). I know when the cpu is under clocked and when it is not. Been doing these tweaks for 4 years now. If you use a tool like System Panel, at stock settings you can see the max cpu around 1500 on our little bad boy. When it peaks out the clock speed is shown. When you under clock it, then check again it won't go beyond the max cpu set in my testing I put a ceiling at 918mhz. System Panel reported full CPU usage (100%) at clock speed 918mhz. Typically with stock kernels, your absolutely right, changes to SetCPU do nothing at all to the real cpu. Which is confirmed, when I reboot and dont have root, if I attempt to use SetCPU and make the changes, System Panel reports 1500mhz (roughly) at full load regardless of what I set it to in SetCPU. If I did this to any of my other phones with stock kernels, you are correct it makes no difference as SystemPanel reports the stock max setting.
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Grnlantern79 said:
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my rezound.
Izeltokatl said:
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Click to expand...
Click to collapse
Or I would say, "half the fun is messing with the phone and trying to get it to do things it should have always been allowed to do...." Just sayin'.
Are you using the profiles at all? Im interested to know what seems to be working out the best for you.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
douger1957 said:
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
Click to expand...
Click to collapse
Linpack and Quadrant are not reliable benchmarks. TBH I don't take any of the benchmarks seriously, they are more for entertainment for me. But to each their own right?
Yeah some of the benchmark apps are a bit unreliable to say the least...
If I use one, I try to use ones that Anandtech uses. I trust them to find the better benchmark tools.
Related
So I've gotten anywhere between 2.5 to 5.1 MFLOPS using various ROMS and have yet to be able to notice something incredibly different.
710...768...806 - What does it matter? What program other than Linpack shows a sizable difference? Sure, maybe things open quicker? What am I missing here?
I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS.
MFLOPS mean jack when there is little way to observe the difference.
Carreno43 said:
So I've gotten anywhere between 2.5 to 5.1 MFLOPS using various ROMS and have yet to be able to notice something incredibly different.
710...768...806 - What does it matter? What program other than Linpack shows a sizable difference? Sure, maybe things open quicker? What am I missing here?
I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS.
MFLOPS mean jack when there is little way to observe the difference.
Click to expand...
Click to collapse
Linpack MFLOPS - measures the floating point performance of your phone.
710...768...806 - refers to CPU frequencies
increasing the CPU frequency should equate to better general-case performance, including things opening quicker as you mention, but also other types of general snappiness like moving between screens and so forth.
"I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS." - This may have less to do with the performance of your phone and more to do with the emulator itself. Emulation is a surprisingly CPU intensive operation, especially if the emulater isn't well written. Rather than looking a ton into overclocking and JIT, etc, maybe you ought to look for a better piece of software.
Yea,
I've tested most emulators. Wish there was an Atari emulator!
Thanks for the response.
Carreno43 said:
Yea,
I've tested most emulators. Wish there was an Atari emulator!
Thanks for the response.
Click to expand...
Click to collapse
I have run roms with 5.1 MFLOPS and now am running a rom that gets 3. I can honestly say I see no difference.
Spencer_Moore said:
I have run roms with 5.1 MFLOPS and now am running a rom that gets 3. I can honestly say I see no difference.
Click to expand...
Click to collapse
I can see a difference... in battery life! Lolz
g00gl3 said:
I can see a difference... in battery life! Lolz
Click to expand...
Click to collapse
Haha Awesome
it looks like to me that everyone is look at the wrong things.
for example:
I am running a Tom that is getting on a average of 4.9 mflops.
I get smoother screen changes....
streaming videos online is so much faster compared to a 3.0 mflop rom. ...
tubetube and other....... websites.
to me everything I do is faster...
I.don't play game on my phone so I don't know how that is.... but everythng else I do is very much faster.
I love high mflop roms...
I have notice about mflops is that it matters about the kernal that u use.
Isn't it true that the MSM7201 in our phones is already overclocked to get to 528mhz as it is? I see a lot of different places saying Qualcomm chips in general are just not worth overclocking... and since our chip is factory overclocked to begin with... just seems like we're pushing the already-pushed here. But the way this board goes crazy for overclocking... it's contradictory. I don't know what to think, cause I've run Linpack myself and gotten ~4.9 with JIT + OC versus ~2.5 without... but I'm with the OP on this one... only difference I'm seeing is my battery draining faster and my phone getting physically hotter.
xatch said:
Isn't it true that the MSM7201 in our phones is already overclocked to get to 528mhz as it is? I see a lot of different places saying Qualcomm chips in general are just not worth overclocking... and since our chip is factory overclocked to begin with... just seems like we're pushing the already-pushed here. But the way this board goes crazy for overclocking... it's contradictory. I don't know what to think, cause I've run Linpack myself and gotten ~4.9 with JIT + OC versus ~2.5 without... but I'm with the OP on this one... only difference I'm seeing is my battery draining faster and my phone getting physically hotter.
Click to expand...
Click to collapse
I have OC and JIT and getting about 5.1 mflops and haven't had worse battery life or a hotter phone. It could be the battery I'm using but meh (got a replacement one that's 2000 mAh) but I got worse battery life on leak 2.1 than with the rom I'm using now that has OC, JIT, LWP, etc. I can go about 8 hours with heavy texting, moderate internet usage and my lwp's running and it only goes to about 65%
so OC and Jit don't make that big of a difference in gameplay?
Sent from my Eris using the XDA mobile application powered by Tapatalk
What the OP and all the respondents are noting is frankly quite typical of what happens when performance tuning focuses on a single benchmark: the results obtained are essentially meaningless for different kinds of activities on the same device.
That's because there's a whole chain of dependencies that are specific to a given task, any number of which could become the rate-limiting factor; and a different task on the device will have a different set of dependencies and therefore different rate-limiting behaviors.
For instance, let's take writing to an SD card as an example: there's really no way that OC'ing will speed that up in a measurable way - because the CPU isn't the rate limiting factor.
That Linpack benchmark measures floating-point performance using a software library (as the Eris has no hardware FP capability). Most of the apps on the phone do very little FP work at all. But, it's not a bad test of CPU speed, because it performs no I/O. It also may not be very memory bandwidth intensive, either (if the problems it works on stays in the uP cache and there are few page faults).
OTOH, a game emulator needs to write to the graphics display (at a minimum) and possibly also do read I/O from flash.
Different task, different results. Sometimes things can be improved by hardware or firmware; sometimes the software itself needs to be improved.
bftb0
im sorry, but could you just answer in plain english
Sent from my Eris using the XDA mobile application powered by Tapatalk
TheSonicEmerald said:
im sorry, but could you just answer in plain english
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Lima beans bad.
Pork good.
Slow phone bad.
Fast phone good.
bftb0
Thanks for my laugh of the day on that one.
What I'm trying to get at is -
I should be able to play, at the basic level, Sonic or Mario - Without issues.
At the very least
I prefer roms over market games any day (Sonic, Mario, Zelda, DK-Country) and it cripples the phone, at least in my view, that I cannot enjoy the fruits of old games.
Although, I was able to find some old Atari games - which, thankfully, work without stuttering.
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
This is agreed up to a point. Sooner or later they will be creating apps and OS' that will truly utilize the full dual cores potential within the phone. I personally believe that up until that point the OP is 100% right on. But once this does happen, these apps will become more and more processor heavy. And once that happens, I believe we'll be back in the same boat as before and 1.2 vs. 1.7 will actually make a bit of a difference to the typical end user (and not just by benchmark enthusiasts).
The only reason I believe this to be true is look at how PCs and laptops evolved. We got dual core processors and apps weren't quite using the full potential, then as time went on and programmers started utilizing the full processing capabilities of dual/quad cores (& as these processors became more and more common) the differences began to matter again. That's just my 2 cents & I could be completely wrong, but just wanted to share my thoughts. Good topic though
Sent from my badass HTC EVO 3D... Get in our dimension!
mitchellvii said:
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
* UPDATE *
Ooops!
Thought I was putting this in the Q & A section. My bad. Mods please move this.
Everyone else please don't flame me - just goofed
Click to expand...
Click to collapse
lol i did this once gotta love having multiple tabs and think you clicked on the right one ya? least thats what happend to me when i did it
I agree with you. Even in the games i play there is almost no difference, except that the battery gets drained faster because of the higher voltage.
P.s. wrong section, rable, rable, rable
I kinda agree with you in the matter of it not making a HUGE difference. But when I'm overclocked to 1.7, I do notice that it seems to scroll smoother. But that's the only difference I can see.
Sent from my PG86100 using XDA Premium App
I'm comin from a heroc running 768 so 1.2g MORE than enough for me. Besides any faster an yer batterys gonna last w couple hours.
Sent from 3D A.W.E.S.O.M-O
Hi Mitch! You're right, no real need for OC.
From a SuperCharged Evo4g!!!
motoelliot said:
I'm comin from a heroc running 768 so 1.2g MORE than enough for me. Besides any faster an yer batterys gonna last w couple hours.
Sent from 3D A.W.E.S.O.M-O
Click to expand...
Click to collapse
This would be my philosophy. A 1.2 GHz Dual Core is absolutely insane compared to what us Hero users used to have to deal with. My phone couldn't even handle 768, it was stable at 691.
LiquidSolstice said:
This would be my philosophy. A 1.2 GHz Dual Core is absolutely insane compared to what us Hero users used to have to deal with. My phone couldn't even handle 768, it was stable at 691.
Click to expand...
Click to collapse
Yeah... My poor heros still mad at me.
Sent from 3D A.W.E.S.O.M-O
I have my 3D oc'ed to 1.5 and ever so slightly undervolt to 1175000 (too many zeroes?)
Totally stable for me. Battery doesn't seem effected much.
Of course I haven't done heavy gaming yet. So. I dunno. I'm still in the honeymoon phase of just being Able to overclock, ya know. Lol.
Sent from my PG86100 using Tapatalk
Delete post
felacio said:
I have my 3D oc'ed to 1.5 and ever so slightly undervolt to 1175000 (too many zeroes?)
Totally stable for me. Battery doesn't seem effected much.
Of course I haven't done heavy gaming yet. So. I dunno. I'm still in the honeymoon phase of just being Able to overclock, ya know. Lol.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I dont know what the stock voltage is, but wouldnt this essentially balance out the extra battery draw from running a slightly higher clock?
Faster, Stronger .. make it so.
Sent from my PG86100 using Tapatalk
I've overclocked mine a few days, now I'm at stock 1.2 almost no difference. Running the script for overclock is nice though because it allows the use of apps like setcpu. That way profiles can be set for temperature and battery charge level.
As for overclocking because its awesome fast... No need, sweet the way it is.
mitchellvii said:
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
* UPDATE *
Ooops!
Thought I was putting this in the Q & A section. My bad. Mods please move this.
Everyone else please don't flame me - just goofed
Click to expand...
Click to collapse
I agree. It doesn't feel much if any faster and is probably needlessly using excess battey.
On the otherhand, I find there to be a pretty big difference between driving 120, 150, or even 170 mph.
mitchellvii said:
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
* UPDATE *
Ooops!
Thought I was putting this in the Q & A section. My bad. Mods please move this.
Everyone else please don't flame me - just goofed
Click to expand...
Click to collapse
I overclock because it makes my friends with lame iPhones jealous.
bavman said:
I agree with you. Even in the games i play there is almost no difference, except that the battery gets drained faster because of the higher voltage.
P.s. wrong section, rable, rable, rable
Click to expand...
Click to collapse
You goto KU?
Nice internet speeds, dorm/campus internet sucked when I was there
Once there's permanent root and htc releases the kernel source, will our phones be able to be over clocked higher then 1.7?
Sent from my PG86100 using Tapatalk
braggin' rights
Buff McBigstuff said:
I overclock because it makes my friends with lame iPhones jealous.
Click to expand...
Click to collapse
+1
10Characters
First I am aware that overclocking is not "safe" and all that kind of stuff
However for some reason I am unable to OC my SGS2 and run the phone on a steady way.
I have tried several ROMs (stock and custom) with different kernels and OCing apps with no avail.
I am not even able to run at 1.4Ghz or 1.6Ghz without having my phone reboot or hard lock on me.
Is there a particular or recommended setting (most successful combination) that anyone out there can suggest me trying?
Sometimes it will hang under heavy gaming but sometimes even browsing app and regular stuff will cause the phone to reboot or lock. If I work with no OCing at all then everything is fine and dandy.
Thanks, you can see my current configuration @ my signature.
Sounds like a very temperamental cpu. Currently I have the same setup you do and have never had issue with 1400mhz or 1600mhz. Though I usually leave mine at 1200mhz. What app are you running when it hangs?
And just as important, do you have alot running in the background? The modified touchwiz launcher unnamed comes with can be enabled to show a red dot next to the apps that have been opened and are in the background.
If you could list the apps with the red dots.
Sent from my páhhōniē
gr8hairy1 said:
The modified touchwiz launcher unnamed comes with can be enabled to show a red dot next to the apps that have been opened and are in the background.
Click to expand...
Click to collapse
It does? That sounds more like one of the themes that includes TW4.5.
Not all CPUs can overclock - there's a reason it was sold as a 1.2 GHz chip.
Well as I've mentioned before, it could even hand when browsing through my apps menu, browsing the gallery, playing a game (non in particular) and the funny part is that the phone is not even hot to touch.
What I know for sure if that if no OC = no hangs, no reboots.
I do have the App monitor widget that comes with the stock ROM and currently using it on UnNamed 1.3.1 and I only have Widget Locker App. However I have try closing it and still will happen.
Not sure if maybe this CPU is somehow having an issue that makes it unstable as soon as I OC it.
Entropy512 said:
Not all CPUs can overclock - there's a reason it was sold as a 1.2 GHz chip.
Click to expand...
Click to collapse
Now that is new to me, I thought that all of them were OCable. Is there anyway to identify which can be or not OCed?
nope.. just by testing. it does have to do a little bit with the kernel and rom. the roms didnt originally have stable OC. i would assume that all of them do now. one thing you might try is giving them a little more voltage (just a little) at the higher clocks, but be careful. if you increase the voltage that means that you will sink more enery through the cpu and it will get hot quick. make sure you watch the temp.
i find that setcpu is less stable than the built in cm7 oc menu but cm7 doesnt have a voltage menu.
but on the same token... why OC? i can and i did but i dont need to... everything is like butter and i didnt see that huge a gain by OCing it anyways
tmckenn2 said:
nope.. just by testing. it does have to do a little bit with the kernel and rom. the roms didnt originally have stable OC. i would assume that all of them do now. one thing you might try is giving them a little more voltage (just a little) at the higher clocks, but be careful. if you increase the voltage that means that you will sink more enery through the cpu and it will get hot quick. make sure you watch the temp.
i find that setcpu is less stable than the built in cm7 oc menu but cm7 doesnt have a voltage menu.
but on the same token... why OC? i can and i did but i dont need to... everything is like butter and i didnt see that huge a gain by OCing it anyways
Click to expand...
Click to collapse
I know, this Exynos processor is the best out there right now, forget about Qualcomm's Snapdragon on the Skyrocket. I am just trying to OC for the fun of it
Guti1977 said:
I know, this Exynos processor is the best out there right now, forget about Qualcomm's Snapdragon on the Skyrocket. I am just trying to OC for the fun of it
Click to expand...
Click to collapse
Although it makes me wonder if the CPU could be having an issue, since it hard locks when attempting to.
Guti1977 said:
Although it makes me wonder if the CPU could be having an issue, since it hard locks when attempting to.
Click to expand...
Click to collapse
have you ever overclocked PC CPUs? if you have spent much time doing that, then you would know that not every chip, even within the same model/family, will clock the same. take 2 CPUs, from the same batch, same model, with identical hardware tied to them. you will probably find that one clocks higher stable speeds than the other.
its very likely the proc in your phone just cannot handle the overclocks that the next person's could.
Like pirate said, no two pieces of hardware are identical. Sort of shows how much variance there can be in a manufacturing process. Id guess theres a few chips that come off the same line that arent stable at 1.2 ghz, but they dont make it to the devices, whereas one that can handle a higher clock will. (No sense tossing one that exceeds minimum requirements, thatd just be throwing good hardware away)
You could try nudgin the voltage up and seeing how it behaves, just use caution.
Sent from my SAMSUNG-SGH-I777 using XDA App
garyd9 said:
It does? That sounds more like one of the themes that includes TW4.5.
Click to expand...
Click to collapse
My bad. You are correct.
Sent from my páhhōniē
To get mine to overclock to 1.4 and 1.6Ghz I had to actually INCREASE the voltage settings via Voltage control app. So my settings are: 1.6Ghz= 1475mV and 1.4Ghz=1325mV
Try those out and see if is better for you. I tried undervolting the higher voltages and would either lockup or reboot instantly until I tried adding voltages. So you may need to play with your settings to get it to work for you.
Sent From My KickAss ATT SGS2 SPORTING CM7
twiggums said:
Like pirate said, no two pieces of hardware are identical. Sort of shows how much variance there can be in a manufacturing process. Id guess theres a few chips that come off the same line that arent stable at 1.2 ghz, but they dont make it to the devices, whereas one that can handle a higher clock will. (No sense tossing one that exceeds minimum requirements, thatd just be throwing good hardware away)
You could try nudgin the voltage up and seeing how it behaves, just use caution.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yup, or if they want to sell a "premium" device with a higher clock rate, they will take the parts that test well at 1.4 and sell them as such - meaning parts rated 1.2 will be LESS likely to be overclockable if a device comes out with CPUs rated at 1.4 - like the Galaxy Note did.
Before, anything that could meet the requirements of stable at 1.2 was sold to any Galaxy S II - but now, the premium parts are going into the Note.
RockRatt said:
To get mine to overclock to 1.4 and 1.6Ghz I had to actually INCREASE the voltage settings via Voltage control app. So my settings are: 1.6Ghz= 1475mV and 1.4Ghz=1325mV
Try those out and see if is better for you. I tried undervolting the higher voltages and would either lockup or reboot instantly until I tried adding voltages. So you may need to play with your settings to get it to work for you.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
I am having the same issue as the original poster on my new GS2. I will have to try the settings you mention but would it be possible to do this and also apply /UV to the remaining lower (1000ghz to 200ghz) processor speeds and maintain stability?
So I overclocked my GSII to 1.6Ghz, and ran benchmarks and it was blazing fast. So what's the point of overclocking other than running benchmarks? I'd rather not have my processor running at 1.6Ghz all the time and draining battery power. I actually prefer underclocking to save power. So my question is - how else can I benefit from overclocking my device?
yo whyd you put this in the dev section? get flame suit on brotha.
miui+siyah = beast
Well its obviously to have your device performance better. Honestly it's not really practical to run higher than 1.2 ghz though.
You also put this in the wrong section. Prepare your anus.
NJGSII said:
Well its obviously to have your device performance better. Honestly it's not really practical to run higher than 1.2 ghz though.
Click to expand...
Click to collapse
But in what ways other than benchmarks? Am I really going to notice a difference if I kick it up to 1.4 or 1.6Ghz when browsing the web or playing Angry birds or something?
where is the download link and what does it do?
Some serious development going on here.. [\sarcasm\]
OP even if you crank it up to 1.6GHz, unless your isolating that step, your phones not using that clock speed unless your doing sh*t on your phone. It will increase how fast apps or menu's open navagating throughout the phone. Your making the CPU think faster so your phone ends up doing its tasks little and big ...faster
But dude.. Googling the benefits of OC could have giving you an answer ..and FASTER. Lol
Sent from my SAMSUNG-SGH-I777 using xda premium
The benefits of overclocking you ask? Let me tell you just a few.
1. For every overclocked phone, one dollar is anonymously donated to poor and starving children, families, and college students across the world [citation needed].
2. Overclocking your phone emits a low frequency gamma wave inhibitor which in some cases, tested by prestigious scientists, has proven to protect you from harmful UV rays from the sun, nuclear fallout, increases neural synapse action in the brain, lowers bad cholesterol AND blood pressure, increases lifespan up to a minimum of three years, and is a natural antimicrobial agent that also interacts with your white blood cells to not only increase output and strength, but also breaks down the DNA rebuilding process by inhibiting protein synthesis in a wide variety of foreign microbes in your body.
3. Overclocking has been used to successfully treat sever depression, obesity, dementia, and AIDS.
4. With an overclocked phone, it's been observed waiting times for and inside elevators is severely decreased.
5. Bad driver? Accident prone? Overclocking has been shown to heighten driver awareness and overall skill.
6. It speeds up your phone on a day to day basis, with some, but not terribly noticeable battery drain [citation needed].
Sent from my SAMSUNG-SGH-I777 using xda premium
Overclocking is entertaining. But I'm running the Unnamed rom on my device and have it UNDER clocked to 800mhz. Crazy good battery life and zero lag.
Overclocking is pointless as it runs everything great already. I'm waiting to overclock until my phone is outdated and my contracts about to expire.
While its rather easy to do there really isn't any benefit to overclocking the SGSII. Yes, it'll run a little faster and your Angry Birds might run smoother (really? ), but it'll also mean a little more heat and more battery drain all to accomplish something you really won't be able to get any real advantage from.
another reason to overclock would be bragging rights
DJSLINKARD said:
another reason to overclock would be bragging rights
Click to expand...
Click to collapse
Only reason in my opinion lol...
Sent from my Galaxy S II (I777) - 1.4Ghz
For this phone, it's pretty much useless. The phone runs great without the faster clock speeds.
On the other hand, if it was a snapdragon processor, you'd need 1.5 GHz just to be marketable next to this phone (and 1.8GHz to perform as well in day to day usage.)
One reason could be... Because we can!
Sent from my SAMSUNG-SGH-I777 using xda premium
highaltitude said:
One reason could be... Because we can!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
haha ... love it!
Sent from my SAMSUNG-SGH-I777 using xda premium
MattMJB0188 said:
So I overclocked my GSII to 1.6Ghz, and ran benchmarks and it was blazing fast. So what's the point of overclocking other than running benchmarks? I'd rather not have my processor running at 1.6Ghz all the time and draining battery power. I actually prefer underclocking to save power. So my question is - how else can I benefit from overclocking my device?
Click to expand...
Click to collapse
Most people overclock for a smoother/snappier experience. I notice that roughly 20% increase in scrolling/tabbing around. Also you can think of it like this:
1.4ghz will finish tasks faster then 1.2, that way taking less battery. You could also undervolt that 1.4 to 1.2 (1275mV), so your finishing tasks quicker while draining no more then stock.
I switch between 1.4 and 1.0 every other day it seems. 2 months later, still looking for the right one for me. 1.6 should only be for benchmarking imo, epeen.
cwc3 said:
1.4ghz will finish tasks faster then 1.2, that way taking less battery. You could also undervolt that 1.4 to 1.2 (1275mV), so your finishing tasks quicker while draining no more then stock..
Click to expand...
Click to collapse
It's not that simple.
There are dozens of bottlenecks in these devices (and any other computer), and 9 times out of 10, it's NOT the processor. Persistant storage, RAM, bus speeds, etc - all those things will ensure that a 10% bump in processor speed will NOT give you a 10% decrease in run time for a given typical application. In many cases, you'll see no speed increase at all, as it takes the same amount of time to flush to persistant storage no matter how fast the write cache fills.
I'm not suggesting that a person shouldn't O/C, but don't be surprised when going from 1200MHz to 1400MHz makes no visible difference other than the battery draining slightly quicker.
I know someone is going to respond that the processor will bump back down to a slower speed and therefore it runs at the higher speed for less time, etc. However, unless you have the governor set to poll for usage so often that the governer is driving your clocks up to max, it's not going to poll often enough to make much (if any) difference.
Think of it this way: We both own a mustang, but mine is a V6 at 220HP and yours is a V8 at 300HP. In theory, yours can accel faster and maintain a higher top speed. In reality, neither one of us can go faster than the car in front of us (but you'll burn more gas doing it.) (Of course, you'll have more fun in yours.)
I hope this helps with a very common misconception.
Take care
Gary
garyd9 said:
It's not that simple.
There are dozens of bottlenecks in these devices (and any other computer), and 9 times out of 10, it's NOT the processor. Persistant storage, RAM, bus speeds, etc - all those things will ensure that a 10% bump in processor speed will NOT give you a 10% decrease in run time for a given typical application.
Click to expand...
Click to collapse
Very true. Also I am guessing in gaming, that OC will drain your battery quite well.
Consider I mostly do Web browsing on my phone (I need a tablet), 1.4 is a much better browser experience imo. Worth the 100mV.
garyd9 said:
Think of it this way: We both own a mustang, but mine is a V6 at 220HP and yours is a V8 at 300HP. In theory, yours can accel faster and maintain a higher top speed. In reality, neither one of us can go faster than the car in front of us (but you'll burn more gas doing it.) (Of course, you'll have more fun in yours.)
I hope this helps with a very common misconception.
Click to expand...
Click to collapse
Excellent analogy.
Sent from my Galaxy SII
While for now Overclocking is mainly just done for fun im hoping that closer to my upgrade time that i will be overclocking for more actical reasons. That is the way it was for my Captivate. I enjoy trying to push my hardware to its limits. Ive gotten my GSII so far to a stable 1700mhz but i think i can squeak out a little more speed especially with the gpu down clocked a little. I run it at 1400MHZ Though with the gpu forced at 267mhz.
ive tried every rom/kernal combination and with each i get lock ups when doing intensive cpu work such as a game or benchmark overclocked to 1.6 any ideas? Thanks
Just means your processor was built a little weak. Its only built to run at 1.2ghz so anything above that is pushing it hard... some phones can be oc'd that much, some can't. Just take it down to 1.4. I can't even get mine to 1.4 so he thankful
Sent from my AT&T cellular device.
What voltage do you have it at? Try raising it 25mV at a time stressing you cpu at each step until you're stable. That is if you are determined to run 1.6 and i would not push more than +100mV personally.
joeyzadoe said:
ive tried every rom/kernal combination and with each i get lock ups when doing intensive cpu work such as a game or benchmark overclocked to 1.6 any ideas? Thanks
Click to expand...
Click to collapse
Have you considered there is a reason that your phone was only sold as capable of 1.2 GHz?
Entropy512 said:
Have you considered there is a reason that your phone was only sold as capable of 1.2 GHz?
Click to expand...
Click to collapse
Wow... You got real issues man..The OP is just looking for some tips from others that have succeeded in getting their phones to 1.6.. You need some help buddy...
If youve nothing nice to say..
But then I guess youd never speak would you?
/end rant
Sent from my SAMSUNG-SGH-I777 using xda premium
Stevenrogers_420 said:
If youve nothing nice to say..
Click to expand...
Click to collapse
Hope you heed your own advice.
Stevenrogers_420 said:
Wow... You got real issues man..The OP is just looking for some tips from others that have succeeded in getting their phones to 1.6.. You need some help buddy...
If youve nothing nice to say..
But then I guess youd never speak would you?
/end rant
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I do not think entropy is the one who has issues...
This has been discussed in 10 different threads already and in great detail. If the OP did as much as search he would of have found the answer himself. That is why they call it research
the only question left is...... You mad bro?
Keep all voltages stock, then use voltage congrol and click on 1400 and increment the slider+ 25, then do the same for 1600. This is what i had to do to get my phone stable at 1.6 Some phones may need EXTRA voltage and others need less. It takes some testing to get your particular phone stable at anything over 1.2Ghz. I only did it to see if I saw any gains. Actually for me and my phone I found as far as MY SETUP and testing many different benchmark style apps at 1.4Ghz i got better benchmarks than i did at 1.6Ghz. Now everyones phones will act sligbtly different so your mileage may vary.
Sent From My KickAss ATT SGS2 SPORTING CM7
At 1.6 ghz... your phone will be discharging your battery ON your charger... I personally wouldn't recommend doing it as it gets the phone really hot, and causes the chip lots of stress due to high heat. Personally if you need more performance (this phones pretty damn fast anyways) go to 1.4ghz.
Most of our phones can be overclocked to 1.4 and some can go to 1.6 but not all. If you change the voltages and it still craps out, then take it down a notch to 1.4 and see how that works for you.
Entropy512 said:
Have you considered there is a reason that your phone was only sold as capable of 1.2 GHz?
Click to expand...
Click to collapse
Now now. Since when do we encourage keeping things stock.
My point is - if it were guaranteed to hit 1.6, it would be sold as 1.6.
Being able to hit 1.6 is luck of the draw, pure and simple.
There's a reason:
1) OC is not default on my kernel
2) I held off on providing OC support for a while here, and NEVER released it on Infuse (users weren't mature enough to handle it over there)
3) I have a warning in GIANT RED LETTERS not to complain about OC stability issues on my kernel thread.
Entropy512 said:
My point is - if it were guaranteed to hit 1.6, it would be sold as 1.6.
Being able to hit 1.6 is luck of the draw, pure and simple.
There's a reason:
1) OC is not default on my kernel
2) I held off on providing OC support for a while here, and NEVER released it on Infuse (users weren't mature enough to handle it over there)
3) I have a warning in GIANT RED LETTERS not to complain about OC stability issues on my kernel thread.
Click to expand...
Click to collapse
This is all true... but the OP was simply asking a question now lets all play nice.
We should have an OC that allows n00bs to melt their cpu.... 2.5ghz ftw
No no no.... We have too many "I tried to load the ICS in the I9100 forums, and I bricked my phone, please help!" threads. we don't need "I OC'ed my phone to 8ghz and melted my cpu" threads too
Tegrak allows you to go past 1.6. I thought these CPU were locked @ 1.6 but i had to up my voltage at 1.7 and i got a small bump in my benches though i probably did run my test enough to confirm the bump. At so.e point, when i get some time ill beat on my CPU some more
penguinlogik said:
At 1.6 ghz... your phone will be discharging your battery ON your charger... I personally wouldn't recommend doing it as it gets the phone really hot, and causes the chip lots of stress due to high heat. Personally if you need more performance (this phones pretty damn fast anyways) go to 1.4ghz.
Click to expand...
Click to collapse
I ran my phone at 1.6 for days just to see performance. No UV at all.. battery certainly drained faster, but not while charging. It charged just fine.. and stayed cool even when stressing. Like many have stated, all CPU's are slightly different .. just cause yours melts at 1.6 and wont charge doesn't mean this will happen for anyone trying to run 1.6GHz.
sent from my SGSII... suckas
Try bumpin' up the voltage 1-2 notches.
Just to add to the stats...
I've been able to run @ 1.4 with the same voltage as 1.2, but my phone will freeze once in a while when running apps like camera or navigation. Had to bump the voltage up slightly to get it stable, though I will likely just run 1.2.
I cannot run at 1.6.
fallingreason said:
Just to add to the stats...
I've been able to run @ 1.4 with the same voltage as 1.2, but my phone will freeze once in a while when running apps like camera or navigation. Had to bump the voltage up slightly to get it stable, though I will likely just run 1.2.
I cannot run at 1.6.
Click to expand...
Click to collapse
Try changing or updating your kernel. Im the OP and had the same problems. with the new siyah kernel at 1.6 even if i try i cant make it lock up or freeze.
Your processor was made from a different silicon wafer than other people's phones and was rated for 1.2ghz.
Since each wafer is different, some processors take voltage better than others as well as speed. It happens.
Sent from my GT-I9100 using xda premium