Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iPhone Does ioverclock 2 really work?

FatPuppy

FatPuppy

macrumors 68000
Original poster
Jul 14, 2012
1,709
151
Applied with winterboard, does it really work? I tried it on my iphone 4 with 7.1.1 and it is a bit better. I just hope it's a placebo effect cause I don't want to keep my iphone 4 tether jailbroken. I ran geekbench 3 and in both cases the score is 213.
 
No, there is no way to overclock an iOS device. All that does is make your battery drain faster by not allowing the CPU to sleep.
 
Even if it did work, what's the point of an extra 2% speed you're going to get out of it? A faster phone will probably be out this fall, and another one next year, and the year after that.
 
No over clock avaliable, just the fact that it's applied in winterbiard should be a red flag for you
 
Hello... In defense of my tweak, I've always stated that it DOES NOT over clock the device... iOverclock is just the name... It was purposely made to make you feel like your device had been "over clocked" because it IS faster. This tweak does make the device faster, it's just more of in loading, transitions, animations, etc... It has been proven in multiple reviews of the older version that it does in fact speed up the device. Just look it up on YouTube. I've stated in the description from day one that it just prevents the CPU (and now GPU) from going into power save mode... It actually goes faster than when plugged in... (Apple apparently under clocked while plugged in? Go figure) so, anyway I respect your opinions and criticisms, some people just don't like it because they're afraid it may damage their device or they don't like the battery drain... It won't damage your device, and the drain is so minimal that actually it may not in fact be a drain, that review from Jon Vitas is from an actual user who saw better battery performance, I don't understand how, but I don't dispute it because since I have received more emails with the same claim, he was just the first. So try it, if you don't like it, well you just don't like it. Since the original there has been over 166,000 downloads of it, and this version works even better than the first so apparently it has some people who like it ;-) like I say in the description, it's not a placebo effect, I have seen a small increase in performance in my iPhone 5s loading times and transitions/animations, and I have since tested it on an A5 iPad Mini and it is soo snappy it's amazing! Honestly I had just sold my iPhone 4, so I couldn't test it on it... But from the testimony I have been receiving iPhone 4 and iPad 2 have amazing increases in performance! So anyway, I understand your criticisms and you have the right to criticize, may I just ask that you try it before you make a decision on whether you like or not?
Thanks
 
Last edited:
^even if it was to speed up animations, that's not something that you would implement via winterboard
 
It does more than that but that's where the most speed is seen by users... Winter board is a great simple way to implement it and activate it without it violating any default repo rules of system file changing. I had an experimental version for my friend's non default beta repo that installed it directly and was "safe" to uninstall but I never trusted the reliability of it to release it to a third party repo, plus winter board is very good for modifying system files and won't slow you down unless you have it theming a huge amount of stuff... Saruik designed Winterboard to theme more than PNG files, it's a great way to theme system files and it won't wreck a device if it doesn't work correctly thanks to substrate safe mode. I tried to come up with another way to do it but short of writing custom code for substrate (which would probably slow the device down and be pointless), I never had a better way to do it and not violate rules. Winterboard is the best way to implement it that I know of, if you know of a better way I'm open to suggestions?
 
The thing that controls UI animations is a few lines of code within the UIKit framework as part of the shared dynamic library cache. Winterboard cannot theme the dylib cache because it is a binary type file, of which Winterboard cannot touch. The only thing that can change the speed of UI animation elements is a MobileSubstrate extension, nothing else.

Changing the value of "Reduce Processor Speed" or in any way alter the com.apple.SystemPowerProfileDefaults.plist does nothing beneficially at all. This has been well disproved by many people over the years. Not only on iOS, but with the equivalent settings within Android.

PS: For maximum possible performance, save the plist as binary not as ASCII.
 
Ok... It still has been proven to speed up device response and speed in general so... If the device is more responsive and loads faster... It'll speed up animations and that is where a lot of people see massive increases in performance... It's purposely made to speed the device up in general not just animations... And that's all I can really say about it
 
Do you have a reputable source that shows it speeds up animations? The responsiveness is mostly a placebo effect because the CPU cannot go faster than its non-idle speed. Because of this, it cannot change the computational speed of the CPU. Thus, it does not speed up the device in general. iOS devices can have a 5Ghz 16 core CPU, but the animations will always be the same speed as set within the UIKit. The only time were they would change, sans MobileSubstrate extension, is when the slow down due to a higher average load. They cannot go faster than their already set maximum speed.
 
Intell said:
The thing that controls UI animations is a few lines of code within the UIKit framework as part of the shared dynamic library cache. Winterboard cannot theme the dylib cache because it is a binary type file, of which Winterboard cannot touch. The only thing that can change the speed of UI animation elements is a MobileSubstrate extension, nothing else.

Changing the value of "Reduce Processor Speed" or in any way alter the com.apple.SystemPowerProfileDefaults.plist does nothing beneficially at all. This has been well disproved by many people over the years. Not only on iOS, but with the equivalent settings within Android.

PS: For maximum possible performance, save the plist as binary not as ASCII.
Click to expand...

Thanks, that's what I was trying to get to

Doesn't iOS automatically convert any ASCII plist files to binary plist files when that plist file is accessed? At least, that's from my experience
 
darricksailo said:
it only needs to convert the plist from ASCII to binary once, right?
Click to expand...

Generally yes, but only for plists within the mobile user's folder. Anything else, like those in a Winterboard bundle or on the OS partition, must be dynamically converted everything they are loaded into memory.
 
I don't really understand too much from the last posts but when I applied this tweak or theme, whatever, on 7.1.1 iphone 4, the only thing that I noticed is that scrolling in music app through albums is smoother and that's it. Also in geekbench 3, it is the same score. I just... I'm suspicious that the dev of this tweak can respond to almost any posts about his tweak on any site.
 
I've been conducting the experiences of it the last few days and needless to say, it was very hard to depict the differences between having it on and off.

I took a very critical approach to it and considering I'm using an iPhone 6, you may question why I even bothered.

Albeit, I could really say I did notice the slightest differences. This includes UI transitions, scrolling and CPU wake time monitored on the BatteryLife app.

For the UI, it seemed as if the slightest lags your eye could catch were appointed to at the seeming cost of responsiveness, and it feels like this appoints to typing as well, but I can't really confirm it.

As for the BatteryLife monitoring / CPU wake, it seemed that using this tweak also made it more stable and not ramping up randomly, staying as low as around -85 to -145.
 
Anyone tried this together with speed intensifier? Are they both compatible with each other?
 
dereknas said:
Anyone tried this together with speed intensifier? Are they both compatible with each other?
Click to expand...

I actually gave it a shot at one stage, but it was almost impossible to measure accurate settings on the scale seeing as it's still a bit glitchy with iOS 8.1. Animations seemed a little tighter though so that's one observation. It seems as if the tweak changes something within the refresh rate, of course I could be wrong but just a thought.
:)
 
ioverclock doesn't do anything be prevent the CPU from sleeping with the screen off causing the battery life to be much less.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back