This is my understanding as well. With TCP Optimizer, it allows for more "out of order" or "missing" packets to be received by the iPhone. Normally what happens, since wi-fi is more unreliable than wired, the phone allows YouTube to continually send packets even though some might get lost along the way. The phone re-requests any lost packets so it can continue streaming the video. But the phone can only "buffer" so many extra packets at one time because it's still receiving all the other packets that are coming in order from the server. This tweak theoretically increases that buffer limit. Since the phone recognizes packets are getting lost it needs to stop accepting new packets while it asks the server again for the already missing packets. Therefore with this tweak installed, it increases the threshold for the number of unaccounted for packets which basically allows YouTube (or other websites) to continue sending packets while the "backlog" of missing packets grows. The phone will sort out the confusion on the fly by asking the server to keep sending new packets while simultaneously asking the server to resend the missing packets. The phone keeps receiving all of these packets and it processes and organizes everything as fast as it can which, in the case of youtube, results in a video! This in a nutshell is how the TCP Protocol works. UDP is the opposite. UDP allows a server to send packets in bunches and they may or may not ever reach the client.
This is why Otosan said it will not increase your download and upload speeds. The results from a speed test reflects the completed transactions of packets. It does not account for the "buffer" of missing packets. This is why it won't show up on a speed test but you'll notice YouTube videos load much better. The phone will continue asking the server to resend packets while the video plays. All of this is unnecessary on a fast network with little traffic but is somewhat helpful on a slow, congested network because of the high probability of packet loss. Toe this is all theoretical and assumed. I am not aware of any real world test that could quantify this tweaks performance. Many people have claimed this tweak slowed down their phone. I'm gonna play around with it for some time and see if I can determine definitely that it helps or hurts my iphone's wi-fi performance.
I hope this helps clarify the tcp optimizer tweak. And if I'm wrong with anything please point it out. I'm still learning and love knowing when I'm wrong. It's easier for me to remember stuff when people point out my errors! But this is how it was explained to me.
Are you on a 4 or 4S? Because on my 4S Google Chrome is just a fast as Safari now. I'll post screenshots of my results later on today when I get home from work.
I don't know anything about this, but very helpful post nonetheless! Thank you!
If only many other tweaks would have such in depth of how things work for users to understand what is going on with the tweak!
Just a heads up, for nitrous I noticed that if any app you turned on for this tweak has an app update, the update resets the app to "off" in the nitrous settings. For example twitter had an update today and I had to set it to "on" again in the settings.
Good catch! I didn't even notice this till you mentioned this, Twitter was updated a few mins ago and sure enought Nitrous was off for Twitter.
I'm one of the few who can't see the speed difference![]()
Are you on a 4 or 4s?
I'm on a 4 and it may be my imagination, but the nitrous only seems to kick in immediately After I enable it in nitrous settings. Regularly even after killing all background, things seem to go back to regular speed even though it is still enabled.
Very disappointed.
Chrome is fast with Javascript, but laggy zooming and scrolling - especially half loaded pages are insanely laggy, and zooming out from a close zoom really stutters.
If Google make their app better, then it'll be awesome - Opera Mini is smooth and slick, if Chrome was like that + Nitrous, then it'd be great.
Don't bother getting Nitrous if you expect it to make Chrome a true replacement for Safari
It does however make the Facebook app usable.
Very disappointed.
Chrome is fast with Javascript, but laggy zooming and scrolling - especially half loaded pages are insanely laggy, and zooming out from a close zoom really stutters.
If Google make their app better, then it'll be awesome - Opera Mini is smooth and slick, if Chrome was like that + Nitrous, then it'd be great.
Don't bother getting Nitrous if you expect it to make Chrome a true replacement for Safari
It does however make the Facebook app usable.
So what's the deal here??? Even I don't find any differences except for benchmarks. So is this some kind of placebo??
Also, I would like to consider the fact that is the difference too small to be noticed in real life usage.. I mean we are getting better benchmarks.. That can't be faked..
I tried Nitrous and cause I wanted the Facebook app to improve in speed, but the Facebook app kept crashing, I uninstalled Nitrous and no crashes, Wanted to use Nitrous, not sure why the instability. Any suggestions?
i've been using nitrous on my 4s. i honestly cannot tell any difference in speed (besides the sunspider benchmark test). i've been using chrome as my default browser since it was launched and performance with and without nitrous has not been noticeably different at all. same with facebook app.
No, do you?
Anyone try it yet?