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

iPhone Wifi high latency in ping times

N

Nektarios

macrumors newbie
Original poster
Apr 29, 2008
3
0
Hello,

I discovered that iPhone has a problem with it's wifi. It has extremely high latency which I cannot explain why.

The problem:

Desktop computer is connected with Gigabit ethernet to the router
iPhone Jailbroken with pwnage tool, 1.1.4 fw, 3.9 bootloader.
iPhone is connected with 802.11g WPA2 Wifi at the same router with perfect signal.

Pinging from the desktop computer (or from anywhere else on the LAN) to iPhone with ip 192.168.1.75:

ping 192.168.1.75

Reply from 192.168.1.75: bytes=32 time=55ms TTL=64
Reply from 192.168.1.75: bytes=32 time=79ms TTL=64
Reply from 192.168.1.75: bytes=32 time=511ms TTL=64
Reply from 192.168.1.75: bytes=32 time=22ms TTL=64
Reply from 192.168.1.75: bytes=32 time=1274ms TTL=64

As you can see these pings have high latency and extreme jittering (55ms->1274ms) for a LAN, with inconsistency and packet loss.
I have tried this on 5 different wifi routers and 2 different LANs and on all of them the problem is the same. I have also tried it on my windows xp laptop's wifi as ad hoc connection and it was perfect with only 1ms average ping time, which is exactly how much it should be! So I guess there's an incompatibility with the iPhone's wifi implementation (software or hardware) and the router's wifi access point.

The problem is that iPhone is such a GREAT piece of hardware/software which I really LOVE, but with such high ping times the difference in web browsing/email etc is enormous. In other words it could be so much faster if this bug was corrected!
I am a competent programmer and I know my fair share of networking, but I really cannot find what is going wrong here.
Can someone help pinpoint this problem and helpfully eliminate it?

Post your pings and router brand and model so we can at least see which one's have it and which one's do not.

Thanks in advance.
 
N

Nektarios

macrumors newbie
Original poster
Apr 29, 2008
3
0
Oskee2001 said:
what the eff are you talking about???
Click to expand...

There's high latency on iPhone's Wireless (Wifi), it should be at 3ms at most but it's 500ms and that's the problem I am talking about. I know my post is a little technical but that's why I posted it here so I can discuss it with more technical-inclined people.
 
Z

zmit

macrumors regular
Apr 12, 2008
183
0
pinging from my macbook to the iphone through an airport express
(our network is complicated though.. need to fix that...)

64 bytes from 10.0.0.92: icmp_seq=0 ttl=64 time=3.213 ms
64 bytes from 10.0.0.92: icmp_seq=1 ttl=64 time=3.279 ms
64 bytes from 10.0.0.92: icmp_seq=2 ttl=64 time=18.721 ms
64 bytes from 10.0.0.92: icmp_seq=3 ttl=64 time=141.678 ms
64 bytes from 10.0.0.92: icmp_seq=4 ttl=64 time=2.786 ms
64 bytes from 10.0.0.92: icmp_seq=5 ttl=64 time=2.390 ms
64 bytes from 10.0.0.92: icmp_seq=6 ttl=64 time=3.076 ms
64 bytes from 10.0.0.92: icmp_seq=7 ttl=64 time=31.658 ms
64 bytes from 10.0.0.92: icmp_seq=8 ttl=64 time=9.461 ms
64 bytes from 10.0.0.92: icmp_seq=9 ttl=64 time=2.661 ms

--- 10.0.0.92 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.390/21.892/141.678/40.955 ms
 
I

isianto

macrumors regular
Feb 12, 2007
108
0
Indonesia
what's your iphone distance to the ap?
the one thing that I can think of are:
1. The distance between ap and iphone
2. The network itself is slow, can be checked using traceroute to see which device/network is slow.
I hope you're understand what I'm saying.
 
N

Nektarios

macrumors newbie
Original poster
Apr 29, 2008
3
0
isianto said:
what's your iphone distance to the ap?
the one thing that I can think of are:
1. The distance between ap and iphone
2. The network itself is slow, can be checked using traceroute to see which device/network is slow.
I hope you're understand what I'm saying.
Click to expand...

I have already tested and excluded both of these as I did with other common factors that can interfere. The distance is irrelevant, even in < 1 meter away and ofcourse all the other devices in the LANs are at 1ms ping with no problems at all, this is double checked.

Should I assume that you don't have this problem? Did you test the ping to your iPhone?
 
EspressoLove

EspressoLove

macrumors 6502
Jun 29, 2007
423
2
Bay Area
Same here, ping to iPhone :

PING 192.168.0.156 (192.168.0.156): 56 data bytes
64 bytes from 192.168.0.156: icmp_seq=0 ttl=64 time=118.549 ms
64 bytes from 192.168.0.156: icmp_seq=1 ttl=64 time=40.059 ms
64 bytes from 192.168.0.156: icmp_seq=2 ttl=64 time=473.773 ms
64 bytes from 192.168.0.156: icmp_seq=3 ttl=64 time=501.897 ms
64 bytes from 192.168.0.156: icmp_seq=4 ttl=64 time=531.897 ms
64 bytes from 192.168.0.156: icmp_seq=5 ttl=64 time=342.740 ms
64 bytes from 192.168.0.156: icmp_seq=6 ttl=64 time=57.954 ms
64 bytes from 192.168.0.156: icmp_seq=7 ttl=64 time=288.092 ms
64 bytes from 192.168.0.156: icmp_seq=8 ttl=64 time=112.002 ms
64 bytes from 192.168.0.156: icmp_seq=9 ttl=64 time=130.167 ms

--- 192.168.0.156 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 40.059/259.713/531.897/182.686 ms
 
EspressoLove

EspressoLove

macrumors 6502
Jun 29, 2007
423
2
Bay Area
For a comparison, here how it should be (ping to my MBP) :

Ping has started ...

PING 192.168.0.104 (192.168.0.104): 56 data bytes
64 bytes from 192.168.0.104: icmp_seq=0 ttl=64 time=39.575 ms
64 bytes from 192.168.0.104: icmp_seq=1 ttl=64 time=1.470 ms
64 bytes from 192.168.0.104: icmp_seq=2 ttl=64 time=1.140 ms
64 bytes from 192.168.0.104: icmp_seq=3 ttl=64 time=6.613 ms
64 bytes from 192.168.0.104: icmp_seq=4 ttl=64 time=0.951 ms
64 bytes from 192.168.0.104: icmp_seq=5 ttl=64 time=1.098 ms
64 bytes from 192.168.0.104: icmp_seq=6 ttl=64 time=1.094 ms
64 bytes from 192.168.0.104: icmp_seq=7 ttl=64 time=1.209 ms
64 bytes from 192.168.0.104: icmp_seq=8 ttl=64 time=1.090 ms
64 bytes from 192.168.0.104: icmp_seq=9 ttl=64 time=1.003 ms

--- 192.168.0.104 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.951/5.524/39.575/11.468 ms
 
EspressoLove

EspressoLove

macrumors 6502
Jun 29, 2007
423
2
Bay Area
What funny is, on WiFi network created to test tethering, i got these :
(Ping from MB to iPhone)

PING 169.254.61.68 (169.254.61.68): 56 data bytes
64 bytes from 169.254.61.68: icmp_seq=0 ttl=255 time=5.087 ms
64 bytes from 169.254.61.68: icmp_seq=1 ttl=255 time=2.076 ms
64 bytes from 169.254.61.68: icmp_seq=2 ttl=255 time=2.041 ms
64 bytes from 169.254.61.68: icmp_seq=3 ttl=255 time=2.130 ms
64 bytes from 169.254.61.68: icmp_seq=4 ttl=255 time=2.014 ms
64 bytes from 169.254.61.68: icmp_seq=5 ttl=255 time=2.045 ms
64 bytes from 169.254.61.68: icmp_seq=6 ttl=255 time=1.983 ms
64 bytes from 169.254.61.68: icmp_seq=7 ttl=255 time=4.280 ms
64 bytes from 169.254.61.68: icmp_seq=8 ttl=255 time=2.202 ms
64 bytes from 169.254.61.68: icmp_seq=9 ttl=255 time=2.051 ms

--- 169.254.61.68 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.983/2.591/5.087/1.063 ms
 
Z

zmit

macrumors regular
Apr 12, 2008
183
0
so thats a direct connection.....

heres my results with my airport express.
MB>airport>iphone

PING 10.0.0.92 (10.0.0.92): 56 data bytes
64 bytes from 10.0.0.92: icmp_seq=0 ttl=64 time=68.698 ms
64 bytes from 10.0.0.92: icmp_seq=1 ttl=64 time=93.097 ms
64 bytes from 10.0.0.92: icmp_seq=2 ttl=64 time=14.111 ms
64 bytes from 10.0.0.92: icmp_seq=3 ttl=64 time=37.901 ms
64 bytes from 10.0.0.92: icmp_seq=4 ttl=64 time=61.817 ms
64 bytes from 10.0.0.92: icmp_seq=5 ttl=64 time=85.735 ms
64 bytes from 10.0.0.92: icmp_seq=6 ttl=64 time=7.245 ms
64 bytes from 10.0.0.92: icmp_seq=7 ttl=64 time=30.359 ms
64 bytes from 10.0.0.92: icmp_seq=8 ttl=64 time=158.786 ms
64 bytes from 10.0.0.92: icmp_seq=9 ttl=64 time=68.242 ms

even that isnt that great..... the only thing i can think of, is that apple have integrated a HELL OF A LOT of error-correcting to ensure things dont get dropped....
or they just suck with wifi....

another comparison.
MB>Dlink AP>iphone

PING 192.168.0.100 (192.168.0.100): 56 data bytes
64 bytes from 192.168.0.100: icmp_seq=0 ttl=64 time=114.958 ms
64 bytes from 192.168.0.100: icmp_seq=1 ttl=64 time=87.010 ms
64 bytes from 192.168.0.100: icmp_seq=2 ttl=64 time=270.099 ms
64 bytes from 192.168.0.100: icmp_seq=3 ttl=64 time=32.961 ms
64 bytes from 192.168.0.100: icmp_seq=4 ttl=64 time=9.975 ms
64 bytes from 192.168.0.100: icmp_seq=5 ttl=64 time=185.230 ms
64 bytes from 192.168.0.100: icmp_seq=6 ttl=64 time=157.291 ms
64 bytes from 192.168.0.100: icmp_seq=7 ttl=64 time=281.302 ms
64 bytes from 192.168.0.100: icmp_seq=8 ttl=64 time=318.425 ms
64 bytes from 192.168.0.100: icmp_seq=9 ttl=64 time=23.552 ms

and then via adhoc
MB>iphone

PING 169.254.93.163 (169.254.93.163): 56 data bytes
64 bytes from 169.254.93.163: icmp_seq=0 ttl=255 time=6.656 ms
64 bytes from 169.254.93.163: icmp_seq=1 ttl=255 time=1.799 ms
64 bytes from 169.254.93.163: icmp_seq=2 ttl=255 time=285.427 ms
64 bytes from 169.254.93.163: icmp_seq=3 ttl=255 time=9.823 ms
64 bytes from 169.254.93.163: icmp_seq=4 ttl=255 time=1.689 ms
64 bytes from 169.254.93.163: icmp_seq=5 ttl=255 time=2.137 ms
64 bytes from 169.254.93.163: icmp_seq=6 ttl=255 time=2.651 ms
64 bytes from 169.254.93.163: icmp_seq=7 ttl=255 time=437.631 ms
64 bytes from 169.254.93.163: icmp_seq=8 ttl=255 time=5.749 ms
64 bytes from 169.254.93.163: icmp_seq=9 ttl=255 time=11.634 ms

that was about a foot away!
 
O

outz

macrumors 6502
Jul 17, 2007
444
14
i know this is an old thread, but i noticed my 3g iphone was having the same extremely high wifi latency my old iphone had... for me, the high latency is only there when the phone isn't rx/tx anything... once i start a large download or upload on the phone the pings to it jump down to a steady 2ms. perhaps it is a power saving method? it lowers the wifi chipset power when not in use and that results in crazy high/unstable latency?
 
R

rvjr

macrumors newbie
Oct 25, 2008
2
0
Wow, same here!

Hi guys,

same here, with a first generation iPhone and a Vista ad-hoc host. The problem didn't occur with XP though... And, I also had the phenomena that when I joined another XP machine into the ad-hoc network between the Vista machine and the iPhone, the pings were ok again (meaning <5ms), but that only happend once and I couldn't reproduce it...

Also strange: there is a very regular pattern: it starts at around 25ms latency and goes up to 210ms, then starts all over again...

Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time=210ms TTL=64
Reply from 192.168.0.2: bytes=32 time=28ms TTL=64
Reply from 192.168.0.2: bytes=32 time=50ms TTL=64
Reply from 192.168.0.2: bytes=32 time=73ms TTL=64
Reply from 192.168.0.2: bytes=32 time=96ms TTL=64
Reply from 192.168.0.2: bytes=32 time=119ms TTL=64
Reply from 192.168.0.2: bytes=32 time=142ms TTL=64
Reply from 192.168.0.2: bytes=32 time=165ms TTL=64
Reply from 192.168.0.2: bytes=32 time=188ms TTL=64
Reply from 192.168.0.2: bytes=32 time=211ms TTL=64
Reply from 192.168.0.2: bytes=32 time=29ms TTL=64
Reply from 192.168.0.2: bytes=32 time=52ms TTL=64
Reply from 192.168.0.2: bytes=32 time=75ms TTL=64
Reply from 192.168.0.2: bytes=32 time=98ms TTL=64
Reply from 192.168.0.2: bytes=32 time=121ms TTL=64
Reply from 192.168.0.2: bytes=32 time=144ms TTL=64
Reply from 192.168.0.2: bytes=32 time=167ms TTL=64
Reply from 192.168.0.2: bytes=32 time=190ms TTL=64
Reply from 192.168.0.2: bytes=32 time=213ms TTL=64
Reply from 192.168.0.2: bytes=32 time=31ms TTL=64
Reply from 192.168.0.2: bytes=32 time=54ms TTL=64
Reply from 192.168.0.2: bytes=32 time=77ms TTL=64
Reply from 192.168.0.2: bytes=32 time=100ms TTL=64

Anyone suggestions how to solve this?

Regards
Rainer
 
R

rvjr

macrumors newbie
Oct 25, 2008
2
0
[solved]

Ok, sorry for bugging you. That was actually easy to solve for me: Computer Managment -> Device Manager -> Network Adapters -> Wifi Card (Intel WifiLink 5100 for me) -> Properties -> Advanced -> Ad-Hoc Power Managent -> Disabled

That was the only setting that worked for me, but now my pings are these:

Pinging 192.168.0.2 with 32 bytes of data:
Reply from 192.168.0.2: bytes=32 time=4ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=2ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1ms TTL=64
Reply from 192.168.0.2: bytes=32 time=1ms TTL=64

I hope disabling power management also helps you, even if you're on different hardware.

Bye
Rainer
 
J

jazzwhistle

macrumors newbie
Nov 5, 2008
2
0
The same youtube clip takes 5 mins on Wifi, 2 mins on 3G!

I started checking this out when I noticed youtube downloading exceptionally slowly on my home wifi, slower than 3G... I'm using the latest 16Gb iPhone 2.1(5F136) and a Linksys WRT54GSv4 with the latest Firmware 1.06.3. Distance from the router makes no difference to these pathetic speeds, and I've tried changing the DNS to the router IP to no avail.

For those who dont "ping", downloading a 1min46 video clip on youtube takes:

5 minutes on iPhone Wifi
2 minutes on iPhone 3G
30 seconds on Macbook Wifi

For those who do, here are my pings between Router and iPhone, between Macbook and iPhone, both while downloading from youTube on iPhone, and while idle:

Linksys > iPhone while downloading from youtube:
64 bytes from 192.168.1.101: icmp_seq=35 ttl=64 time=8.9 ms
64 bytes from 192.168.1.101: icmp_seq=36 ttl=64 time=274.3 ms
64 bytes from 192.168.1.101: icmp_seq=37 ttl=64 time=58.8 ms
64 bytes from 192.168.1.101: icmp_seq=38 ttl=64 time=3.1 ms
64 bytes from 192.168.1.101: icmp_seq=39 ttl=64 time=306.5 ms
64 bytes from 192.168.1.101: icmp_seq=40 ttl=64 time=134.8 ms
64 bytes from 192.168.1.101: icmp_seq=41 ttl=64 time=3.2 ms
64 bytes from 192.168.1.101: icmp_seq=42 ttl=64 time=29.0 ms
64 bytes from 192.168.1.101: icmp_seq=43 ttl=64 time=151.7 ms
64 bytes from 192.168.1.101: icmp_seq=44 ttl=64 time=18.2 ms
64 bytes from 192.168.1.101: icmp_seq=45 ttl=64 time=249.0 ms
64 bytes from 192.168.1.101: icmp_seq=46 ttl=64 time=68.4 ms
64 bytes from 192.168.1.101: icmp_seq=47 ttl=64 time=2.0 ms
64 bytes from 192.168.1.101: icmp_seq=48 ttl=64 time=217.1 ms
64 bytes from 192.168.1.101: icmp_seq=49 ttl=64 time=185.9 ms
64 bytes from 192.168.1.101: icmp_seq=50 ttl=64 time=7.3 ms
64 bytes from 192.168.1.101: icmp_seq=51 ttl=64 time=130.5 ms
64 bytes from 192.168.1.101: icmp_seq=52 ttl=64 time=250.6 ms
64 bytes from 192.168.1.101: icmp_seq=53 ttl=64 time=73.6 ms
64 bytes from 192.168.1.101: icmp_seq=54 ttl=64 time=51.2 ms
64 bytes from 192.168.1.101: icmp_seq=55 ttl=64 time=268.0 ms
64 bytes from 192.168.1.101: icmp_seq=56 ttl=64 time=92.0 ms
64 bytes from 192.168.1.101: icmp_seq=57 ttl=64 time=319.6 ms
64 bytes from 192.168.1.101: icmp_seq=58 ttl=64 time=293.1 ms
64 bytes from 192.168.1.101: icmp_seq=59 ttl=64 time=267.6 ms
64 bytes from 192.168.1.101: icmp_seq=60 ttl=64 time=287.5 ms
64 bytes from 192.168.1.101: icmp_seq=61 ttl=64 time=111.3 ms
64 bytes from 192.168.1.101: icmp_seq=62 ttl=64 time=2.0 ms
64 bytes from 192.168.1.101: icmp_seq=63 ttl=64 time=259.3 ms
64 bytes from 192.168.1.101: icmp_seq=64 ttl=64 time=88.1 ms
64 bytes from 192.168.1.101: icmp_seq=65 ttl=64 time=140.4 ms
64 bytes from 192.168.1.101: icmp_seq=66 ttl=64 time=2.0 ms
64 bytes from 192.168.1.101: icmp_seq=67 ttl=64 time=294.5 ms
64 bytes from 192.168.1.101: icmp_seq=68 ttl=64 time=118.5 ms
64 bytes from 192.168.1.101: icmp_seq=79 ttl=64 time=1557.9 ms
64 bytes from 192.168.1.101: icmp_seq=80 ttl=64 time=560.4 ms
64 bytes from 192.168.1.101: icmp_seq=81 ttl=64 time=2.0 ms
64 bytes from 192.168.1.101: icmp_seq=82 ttl=64 time=191.7 ms
Click to expand...

Linksys > iPhone, idle:

64 bytes from 192.168.1.101: icmp_seq=9 ttl=64 time=2952.4 ms
64 bytes from 192.168.1.101: icmp_seq=10 ttl=64 time=1953.8 ms
64 bytes from 192.168.1.101: icmp_seq=11 ttl=64 time=954.9 ms
64 bytes from 192.168.1.101: icmp_seq=12 ttl=64 time=1.9 ms
64 bytes from 192.168.1.101: icmp_seq=13 ttl=64 time=24.8 ms
64 bytes from 192.168.1.101: icmp_seq=14 ttl=64 time=49.9 ms
64 bytes from 192.168.1.101: icmp_seq=15 ttl=64 time=75.4 ms
64 bytes from 192.168.1.101: icmp_seq=16 ttl=64 time=100.8 ms
64 bytes from 192.168.1.101: icmp_seq=17 ttl=64 time=115.6 ms
64 bytes from 192.168.1.101: icmp_seq=18 ttl=64 time=141.1 ms
64 bytes from 192.168.1.101: icmp_seq=19 ttl=64 time=165.5 ms
64 bytes from 192.168.1.101: icmp_seq=20 ttl=64 time=191.0 ms
64 bytes from 192.168.1.101: icmp_seq=21 ttl=64 time=312.2 ms
64 bytes from 192.168.1.101: icmp_seq=22 ttl=64 time=30.0 ms
64 bytes from 192.168.1.101: icmp_seq=23 ttl=64 time=55.7 ms
64 bytes from 192.168.1.101: icmp_seq=24 ttl=64 time=82.5 ms
64 bytes from 192.168.1.101: icmp_seq=25 ttl=64 time=154.7 ms
64 bytes from 192.168.1.101: icmp_seq=26 ttl=64 time=180.2 ms
64 bytes from 192.168.1.101: icmp_seq=27 ttl=64 time=205.5 ms
64 bytes from 192.168.1.101: icmp_seq=28 ttl=64 time=231.0 ms
64 bytes from 192.168.1.101: icmp_seq=29 ttl=64 time=245.7 ms
Click to expand...

Macbook > Linksys > iPhone downloading from youtube:

64 bytes from 192.168.1.101: icmp_seq=0 ttl=64 time=292.657 ms
64 bytes from 192.168.1.101: icmp_seq=1 ttl=64 time=161.050 ms
64 bytes from 192.168.1.101: icmp_seq=2 ttl=64 time=35.612 ms
64 bytes from 192.168.1.101: icmp_seq=3 ttl=64 time=263.085 ms
64 bytes from 192.168.1.101: icmp_seq=4 ttl=64 time=76.408 ms
64 bytes from 192.168.1.101: icmp_seq=5 ttl=64 time=304.656 ms
64 bytes from 192.168.1.101: icmp_seq=6 ttl=64 time=131.806 ms
64 bytes from 192.168.1.101: icmp_seq=7 ttl=64 time=2.108 ms
64 bytes from 192.168.1.101: icmp_seq=8 ttl=64 time=9.918 ms
64 bytes from 192.168.1.101: icmp_seq=9 ttl=64 time=247.029 ms
64 bytes from 192.168.1.101: icmp_seq=10 ttl=64 time=267.437 ms
64 bytes from 192.168.1.101: icmp_seq=11 ttl=64 time=144.835 ms
64 bytes from 192.168.1.101: icmp_seq=12 ttl=64 time=2.088 ms
64 bytes from 192.168.1.101: icmp_seq=13 ttl=64 time=2.116 ms
64 bytes from 192.168.1.101: icmp_seq=14 ttl=64 time=310.774 ms
64 bytes from 192.168.1.101: icmp_seq=15 ttl=64 time=133.637 ms
64 bytes from 192.168.1.101: icmp_seq=16 ttl=64 time=2.072 ms
64 bytes from 192.168.1.101: icmp_seq=17 ttl=64 time=82.027 ms
64 bytes from 192.168.1.101: icmp_seq=18 ttl=64 time=251.350 ms
64 bytes from 192.168.1.101: icmp_seq=19 ttl=64 time=128.892 ms
64 bytes from 192.168.1.101: icmp_seq=20 ttl=64 time=2.083 ms
64 bytes from 192.168.1.101: icmp_seq=21 ttl=64 time=224.839 ms
64 bytes from 192.168.1.101: icmp_seq=22 ttl=64 time=45.565 ms
64 bytes from 192.168.1.101: icmp_seq=23 ttl=64 time=318.647 ms
Click to expand...

And finally... Macbook > Linksys > iPhone, idle:

64 bytes from 192.168.1.101: icmp_seq=2 ttl=64 time=14.655 ms
64 bytes from 192.168.1.101: icmp_seq=3 ttl=64 time=38.035 ms
64 bytes from 192.168.1.101: icmp_seq=4 ttl=64 time=63.407 ms
64 bytes from 192.168.1.101: icmp_seq=5 ttl=64 time=77.897 ms
64 bytes from 192.168.1.101: icmp_seq=6 ttl=64 time=102.219 ms
64 bytes from 192.168.1.101: icmp_seq=7 ttl=64 time=123.946 ms
64 bytes from 192.168.1.101: icmp_seq=8 ttl=64 time=149.329 ms
64 bytes from 192.168.1.101: icmp_seq=9 ttl=64 time=174.656 ms
64 bytes from 192.168.1.101: icmp_seq=10 ttl=64 time=198.684 ms
64 bytes from 192.168.1.101: icmp_seq=11 ttl=64 time=213.860 ms
64 bytes from 192.168.1.101: icmp_seq=12 ttl=64 time=81.960 ms
64 bytes from 192.168.1.101: icmp_seq=13 ttl=64 time=109.315 ms
64 bytes from 192.168.1.101: icmp_seq=14 ttl=64 time=134.950 ms
64 bytes from 192.168.1.101: icmp_seq=15 ttl=64 time=160.541 ms
64 bytes from 192.168.1.101: icmp_seq=16 ttl=64 time=186.221 ms
64 bytes from 192.168.1.101: icmp_seq=17 ttl=64 time=211.614 ms
64 bytes from 192.168.1.101: icmp_seq=18 ttl=64 time=226.640 ms
64 bytes from 192.168.1.101: icmp_seq=19 ttl=64 time=251.038 ms
64 bytes from 192.168.1.101: icmp_seq=20 ttl=64 time=276.699 ms
64 bytes from 192.168.1.101: icmp_seq=21 ttl=64 time=302.132 ms
Click to expand...

Help!!
 
R

Resist

macrumors 68040
Jan 15, 2008
3,003
93
I know this is kind of an old thread but, I also noticed slow download speeds on my iPhone 3G compared to my laptop over my home WiFi. My Cable Internet is 10meg download service and my desktop (wired) and laptop (wireless) get that speed most of the time. But for some reason my iPhone 3G gets only 6meg at the most and usually is around 3megs. I don't understand why the iPhone is so much slower.
 
X

xStatiCa

macrumors regular
Oct 7, 2009
157
1
Yes I am resurrecting this thread...

I noticed the same latency when my iPad 2 is idle. 40 - 200+ms pings from the router. Pinging my macbook air was 3ms from the router. I at first was concerned about such horrible pings for the local wifi.

I just tested the Galaxy Tab 10.1 and it had the same results when it was idle. 40 - 200+ms pings when idle.

The second I request something from the internet on either mobile device the pings go down immediately to 3ms or so to match the macbook air.

The person above who mentioned power savings got it right. When the device is idle the wifi hardware goes into a powersave mode because it isn't critical to get data quickly. When network data is needed the wifi hardware is taken out of power save mode until network traffic is reduced to an idle state again so that power save mode is kicked back in.
 
B

beej69

macrumors member
Nov 22, 2003
43
3
Puerto Rico
xStatiCa said:
Yes I am resurrecting this thread...
Click to expand...

me, too :)

i'm seeing this latency on a 4S running iOS 5.0.1.

xStatiCa said:
The second I request something from the internet on either mobile device the pings go down immediately to 3ms or so to match the macbook air.

The person above who mentioned power savings got it right. When the device is idle the wifi hardware goes into a powersave mode because it isn't critical to get data quickly. When network data is needed the wifi hardware is taken out of power save mode until network traffic is reduced to an idle state again so that power save mode is kicked back in.
Click to expand...

fascinating info and maybe it explains what you're seeing, but i'm still seeing ridiculously high latency between a MBA and my iphone over wi-fi even when the device is, say, downloading a youtube movie. my AP is an AirPort Express, so one would think the environment has been heavily tested...

i don't see the same behavior when i ping the iphone using USB tethering, so that kind of rules out something affecting the networking stack, in general. pings from the iphone to outside hosts like google.com are about 7 times as slow as the same pings from my MBA, which is bad, but nowhere near as bad as the multiple-hundred-ms latencies i see between MBA and iphone.

anybody have other theories?

----------

just to get other data points, could somebody who doesn't think they have this problem and are jailbroken post the result of a ping from their phone to their AP?

you'll need the inetutils package to get ping.

thanks!
marc
 
B

blatopilot

macrumors regular
Sep 24, 2011
149
0
Here is a suggestion. Turn off cell network search and see what you get. It is in location services. See pictures below.

Not claiming remedy as my iphone 4s is not jailbroken, but this little test made my iphone network experience go from junk to working like the first day I got it.
 

Attachments

  • IMG_0009.PNG
    IMG_0009.PNG
    196.6 KB · Views: 825
  • IMG_0010.PNG
    IMG_0010.PNG
    174.6 KB · Views: 787
M

Mickaël

macrumors newbie
Jan 30, 2013
1
0
My turn to resurrect the thread...

I am developing an application that requires low latency between a mobile device and a PC.
When it comes to using any Apple device (currently tested with an iPhone and two iPads 2) there is a huge networking problem... It looks like the Apple devices are only capable of sending data at a rate of 3-4 frames per second, and while they are sending data their ping times raise to 200-300ms. If the same ping is done without transferring data, they keep in the 2-5ms zone.

I tested the same use case with Samsung devices (both smartphones and tablets) and the problem does not appear. On the mobile device, data is sent using websockets in Javascript while the data is being handled on the PC in a C++ app. Does anyone has experienced something similar? Does someone has a hint on what can be going wrong?
 
B

beej69

macrumors member
Nov 22, 2003
43
3
Puerto Rico
still seeing crappy pings with an iPhone 5s running iOS 7.0.2 using a DD-WRT access point between my MBA and the phone :(

it really is too bad that Apple has such ****** support...
 
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