so you think Verizon made its customers pay more for the XLTE switch? try again, my bill was the same rate both before and after by many months during the XLTE Switch.
show me the IP also, i see you cut that out. you will be the FIRST T-Mobile i have EVER seen touch 30% near that.
and if you have a XLTE capable phone, they cannot deny it to you if you are within range of a XLTE Tower.
and as of now, Atlanta is NOT the only part providing XLTE, go read the list for areas in GA and the rest of the country with XLTE Service.
"they like to promote it and charge you for it but actually providing that service.... not so much."
^ ^ ^ just about as obvious as saying, i want a cheese burger, get charged for one and get a plain hamburger.
the phones are automatic to switching to XLTE, but there are ways to tell. one is a XLTE App that has a 2 mb app that resides a 565Kb notification app that tells you XLTE is active or not. the way to tell without anything 3rd party, is noticeably the latency.
oh BTW: what was the steady rate for that 116 Mbit run? run a jitter test yet?
and 584 MB of data took 90 seconds? should have taken no more than 65-70 seconds..... someone has consistency issues
easy to factor a steady rate is:
size of data divide by 1024 multiply by 60 and again by 2
so!
584/1024*60*2= 68.4375 Seconds
Provided like your speed test shows a decent consistency of data flow.
now how did i get that formula...its easy.
584 MB of data needs to be changed to bits. 1 MB is 1024 Mb. rule of thumb in networking, your rated speed is what you normally see, but in actuality, your THROUGHPUT is ALWAYS the real data rate. data rate is calculated in a quick shot guess by means of testing throughput and then calculating that to a minutes worth of data flow or a near estimate of that, based on the fluctuation of data flow. then, throughput will ALWAYS be a 10 factor division of your rated speeds. so that 116 Mb you see, you actually downloaded at 11.6Mb or very near it for TCP Protocol overhead.
the interesting part is, the last part of the formula.... why times 2?
many arguments have come from that. the best way to explain it, it is the closest factor to showing Throughput to Rated speed. how those engineers got that, beyond me.
scanner, T-Mobile actually DOES roam off other towers. INCLUDING Verizon towers.
"On August 21, 2012, the FCC approved a deal between T-Mobile and Verizon in which T-Mobile gains additional AWS spectrum licenses in 125 Cellular Market Areas."
Source:
http://transition.fcc.gov/Daily_Releases/Daily_Business/2012/db0823/FCC-12-95A1.pdf
another thing rapid, he came within 2 Mbit of your upload at a almost 2.5 fold the distance latency. that DESTROYS your upload.
he tested further away and got a near same result for your more local test, and you call that "A ways to go"
more like, "i should be RUNNING from you!."
he shattered your download and got very close to your upload at a much higher latency, that is FAR better than your always local test. why don't you send out a cross country test and lets see how fast you get?
that 100ms latency is showing a Canadian server, and he is in the US. Barrie Ontario is right above Toronto. if his location is accurate, he just ran a test anywhere from 1300 miles away to over 2000.
beats your less than 200 miles in my books.
the sheer likeliness of you hitting a Verizon tower in that test, is almost 90%. and you wont know either what tower you are hitting unless you have the ability to decode the tower's base code. which, unless you work on the towers, you wont.