The tweak is only affecting the animation speeds at which the iOS firmware carries out specific tasks, it will not speed up the loading of actual applications on your iDevice. Animations faster, but loading is the same time.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
New Animations are SO MUCH BETTER [in 7.0.3]
- Thread starter kre62
- Start date
- Sort by reaction score
LMAO this is why you don't understand, they don't make the phone faster, hell why do you think that tweak was called FAKEclockup
I think you the one who doesn't understand. Or you two aren't talking about the same kind of "faster", processor speed or UI speed.
The "fake" refers to the following "clockup", because it doesn't change the processor speed, it just speeds up the animations. However, while the animations were a nice way to hide slowness on older iphones because by the time the animations were finished, the app (that is, if you take opening apps as an example) had already been loaded up fully or at least partly. Newer iPhones don't need the extra time, so the animations are just something that slow the user down.
I love the new fade in animation. So much better. And the touch ID works a lot faster now once you are at the lock screen, just fades right in instantly. Perfect.
Let me try this again. Keep in mind the below is illustrative only.
Example Scenario 1 total time:
Unlock Animation Duration: 0.5 seconds
Load time of safari: 1 second
Animation duration to desktop: 0.5 seconds
Animation duration to open settings: 0.5 seconds
Load time of settings: 1 second
Animation to close to home: 0.5 seconds
Total time: 4 Seconds
Example Scenario 2 (Animation time reduced):
Unlock Animation: 0.1 seconds
Load time of safari: 1 second
Animation duration to desktop: 0.1 seconds
Animation to open settings: 0.1 seconds
Load time of settings: 1 second
Animation to close to home: 0.1 seconds
Total Time: 2.4 Seconds
So as mentioned SEVERAL times, yes the actual load times are not decreased. HOWEVER the total time is reduced since you aren't waiting for animations.
In my example, if you set your phone to 0.1x and I set mine to 10x, your phone would take 15-20 SECONDS to draw one animation. In this example, it would take 1minute 20 seconds to do what I did in 2.4 seconds.
So, hopefully you now understand. If one phone takes 2.4 seconds, and another takes 4 seconds, to do the same task:
THE ONE THAT TOOK 2.4 SECONDS IS FASTER. OMG SO HARD TO UNDERSTAND!!
Hope that helps.
Last edited:
New Animations are SO MUCH BETTER [in 7.0.3]
Except that you can't interact with anything. So in practice your scenarios would look more like this.:
Example Scenario 1 total time:
Unlock Animation Duration: 0.5 seconds
Load time of safari: 1 second
Animation duration to desktop: 0.5 seconds
Animation duration to open settings: 0.5 seconds
Load time of settings: 1 second
Animation to close to home: 0.5 seconds
Total time: 4 Seconds
Example Scenario 2 (Animation time reduced):
Unlock Animation: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Load time of safari: 1 second
Animation duration to desktop: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Animation to open settings: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Load time of settings: 1 second
Animation to close to home: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Total Time: 4 Seconds
If the interaction delay did not exist then your original scenarios would be correct. However, it does exist thus rendering them invalid.
Except that you can't interact with anything. So in practice your scenarios would look more like this.:
Example Scenario 1 total time:
Unlock Animation Duration: 0.5 seconds
Load time of safari: 1 second
Animation duration to desktop: 0.5 seconds
Animation duration to open settings: 0.5 seconds
Load time of settings: 1 second
Animation to close to home: 0.5 seconds
Total time: 4 Seconds
Example Scenario 2 (Animation time reduced):
Unlock Animation: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Load time of safari: 1 second
Animation duration to desktop: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Animation to open settings: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Load time of settings: 1 second
Animation to close to home: 0.1 seconds
Wait for delay to end before you can interact: 0.4 seconds
Total Time: 4 Seconds
If the interaction delay did not exist then your original scenarios would be correct. However, it does exist thus rendering them invalid.
Last edited:
I love how this thread turned so EPIC!
Also love how people have these sub-second timing data for animation lengths...
There will be no end to this until either:
1)Apple says so
2)Someone gets the code to see how many clock cycles occurs
EDIT: What is the human response time? Isnt it something like 0.3 SECONDS? It might be IMPOSSIBLE for anyone here to detect sub-second differences.
Also love how people have these sub-second timing data for animation lengths...
There will be no end to this until either:
1)Apple says so
2)Someone gets the code to see how many clock cycles occurs
EDIT: What is the human response time? Isnt it something like 0.3 SECONDS? It might be IMPOSSIBLE for anyone here to detect sub-second differences.
no worriesAh, I hope you didn't take offence
see the reply below of Ks383 to try to see if can understand him/her then.
This is one way of saying it
----------
I love how this thread turned so EPIC!
Also love how people have these sub-second timing data for animation lengths...
There will be no end to this until either:
1)Apple says so
2)Someone gets the code to see how many clock cycles occurs
EDIT: What is the human response time? Isnt it something like 0.3 SECONDS? It might be IMPOSSIBLE for anyone here to detect sub-second differences.
lmao, don't worry the TS won't understand.
So you are saying that if one phone uses that tweak so that its animation takes 1 second, and another had it take up 5 seconds, it would be exactly the same? Factor in that the loading of the app might take 2 seconds. So, in one case you can use the app as soon as 3 seconds, while in the other case, at best, you can only use it 5 seconds later since the animation alone would take that long. Clearly there's no improvement there simply due to faster animations, right? Exactly.
----------
Yup...just like retina is there based on what people can perceive as far as pixels on the screen and above that they can't tell the difference...yet plenty of people can. You can try to speak for other people, but all you would be doing is trying, since you can't actually speak for them, and can't truly say what they do or don't see for themselves. If it's faster for them in some fashion, then that's really all that matters to them--the idea that you or someone else might not find it faster doesn't mean anything to anyone else.I love how this thread turned so EPIC!
Also love how people have these sub-second timing data for animation lengths...
There will be no end to this until either:
1)Apple says so
2)Someone gets the code to see how many clock cycles occurs
EDIT: What is the human response time? Isnt it something like 0.3 SECONDS? It might be IMPOSSIBLE for anyone here to detect sub-second differences.
New Animations are SO MUCH BETTER [in 7.0.3]
Except that you are neglecting the delay that persists after the animation ends, preventing interaction.
If a different animation make someone feel as if their phone is faster in certain aspects and that makes them happy then great for them. Yet, just because someone perceives something as being faster does not mean in reality (quantitatively) it is.
Except that you are neglecting the delay that persists after the animation ends, preventing interaction.
If a different animation make someone feel as if their phone is faster in certain aspects and that makes them happy then great for them. Yet, just because someone perceives something as being faster does not mean in reality (quantitatively) it is.
Well, as before, something has changed/improved, like interaction with pages in folders, for example.
Plus, again, just because some or even most don't notice an improvement in speed, doesn't mean that there isn't one, and doesn't mean that someone else out there might not notice it (even if it is fairly tiny overall), again, similar to the whole retina thing (where some people don't see any difference with higher PPI and others do).
Ultimately, maybe it might be hard to quantitatively prove that there's an overall increase in speed because it's fairly small and would take a lot to measure and show it, but it doesn't seem it could quantitatively be shown that there isn't an improvement either (especially seeing how there is actually observable improvement with some things, like the folders interaction mentioned before).
New Animations are SO MUCH BETTER [in 7.0.3]
And by the same token, just because you perceive a speed increase does not mean that there is (quantitatively) one.
Also as I stated before (once in a reply to you), the folder interaction is an actual improvement. I don't and have never denied that fact. However, some are saying that having reduce motion enabled improves the speed of other interactions (such as the speed at which you can launch apps). It does not due to the delay between the end of the animation and the ability to interact. Were Apple to remove that delay it would indeed be faster.
And by the same token, just because you perceive a speed increase does not mean that there is (quantitatively) one.
Also as I stated before (once in a reply to you), the folder interaction is an actual improvement. I don't and have never denied that fact. However, some are saying that having reduce motion enabled improves the speed of other interactions (such as the speed at which you can launch apps). It does not due to the delay between the end of the animation and the ability to interact. Were Apple to remove that delay it would indeed be faster.
Well, I guess as far as the speed is concerned, the best we can say is that it's not clear whether there is an actual measurable improvement or not for a typical user, even though some people might perceive one to be there, while others might not.
As far as animations in general are concerned--e.g., movement, zooming, etc.--and as far as some interactions are concerned--e.g., folder pagination--there are certainly some improvements.
So, in the overall sense, it's still an improvement for those who didn't care much or at all for the animations (even though the extent of that improvement might be different for different people).
sighhh That could be correct only if the animations do take longer than the loading time for the app, opening of a folder, etc and said action was told to wait until said system animation finishes to load said action. Which in the end does not happen w/ "normal"/motion animations in iOS7. right? Exactly. Say for example if opening a folder takes 1 sec to load w/out considering animation load times, does it matter that said animation takes .5, .75, .9, .99 if at the end you still have to wait 1 second for it to load.
Let's think in a fake example minutes to visualize better, say MS Word takes 2 minutes to load in OSX, the splash screen takes 1 minute to finish animating, but you speed up the splash screen to 30 seconds, does the app load faster because the splash screen finished before hand? no, it doesn't, you still have to wait the 2 minutes for you to use MS Word. What happens when you say fudge it and delete the splash screen altogether so it doesn't load, does the app open instantly? No, you still have to wait the 2 minutes.
Without the stupid animations, now the sky is brighter, the birds sound better, food tastes more delicious, and I can now enjoy my sadistic tendency in reading about the complaints and suffering of hard to please people with bad attitudes without reservation.
You are correct, but in the previous posts we were talking about using fakeclockup, as that was brought up and was used to discuss an example. In the example that was brought up was a comparison of using 10x vs. 0.1x.
So, if the loading of the app is longer than animation (which would be the case with 10x) then you still have to wait for the loading to be done after the animation completes, not really saving any time. But, if the animation takes longer than the loading of the app takes (which could very well be the case with 0.1x) then you would in fact be waiting longer for the animation to finish before you can do anything. Clearly, in one case there you can do something faster in the app than the other.
So, within the context of that example--which is what was brought up in the discussion--saying that nothing is actually faster would be in fact incorrect.
Sigh indeed.
Last edited:
If it IS faster, it's likely the difference is less than human response time. So...
That would explain why many people think you people awe nuts right now.
That particular example and discussion about fakeclockup is not related to human response time.
----------
What do you know, actual quantitative information that shows there are some speed improvements.
Their little experiment doesn't qualify as anything but an experiment...
I could post the same thing and state the opposite. What else do you believe from the internet?
We really need a look at clock cycles...
All in all, if Apple intended to speed up the slow animations, then they failed.
That's a fail apple...The difference should be undeniable, night and day.
For so many to struggle to believe its faster means something is wrong.