Jump to content

Sprint Launching New LTE Cities Oct. 29


Recommended Posts

Speeds today in Lakeland, FL, are painfully slow.   Areas I used to get decent speeds are to a crawl today.  I'm talking about they are barely usable for data on 3G/4G.     Areas that I used to get 4G in Lakeland won't even connect, and when they do it's like .05Mbps down and .007Mbps up.   I was in a bunch of Lakeland locations today, and all were bad.

 

  My current job-site is in Bartow (10-15 minutes south of Lakeland, FL, and the speeds there are unusable also.  I get around the same speeds mentioned above in Bartow.

 

On the way home in Auburndale, FL, I pulled over and did a few speed test  at different locations. Where I would normally get 18mb down, I'm maybe getting 10-12mb max. 

 

This could be due to the network getting the extra load from those customers coming online to use the LTE or prob glitches due to the new cities been added.

 

Also, could be the many customers who might be pulling SPEED TESTS :)  

 

And last but not least customers who even though they knew they had LTE were annoyed of the NONWORKING LTE areas and and when possible just put their phones on CDMA only mode. They are now setting back to CDMA/LTE and are causing slow downs.

 

10-12mb is still above the QOS though :)

Link to comment
Share on other sites

Manhattan is not ready for launch. lol.

 

Half of it is, the other half is not. In uptown Manhattan, I get LTE basically everywhere. In Midtown, it is spotty. In lower Manhattan, I get it in school in SoHo, near my mother's job in Chelsea, and when going over the Manhattan or Williamsburg Bridge.

Link to comment
Share on other sites

Half of it is, the other half is not. In uptown Manhattan, I get LTE basically everywhere. In Midtown, it is spotty. In lower Manhattan, I get it in school in SoHo, near my mother's job in Chelsea, and when going over the Manhattan or Williamsburg Bridge.

 

There is literally like 1 tower turned on in the entire financial district and it is so overloaded it is barely useable. Not to mention many locations where there is a strong LTE signal (<90rsrp) and speeds of <1mbit. You are going to launch service in Manhattan when there is no singal on Wall st? Again, LOL

Link to comment
Share on other sites

There is literally like 1 tower turned on in the entire financial district and it is so overloaded it is barely useable. Not to mention many locations where there is a strong LTE signal (<90rsrp) and speeds of <1mbit. You are going to launch service in Manhattan when there is no singal on Wall st? Again, LOL

 

Again, as stated before Sprint launches LTE when over 40% of the population is covered. In the case of Manhattan, over half of the island is covered with LTE. I personally thought that they should have waited for more ubiquitous downtown coverage, however, It is not as if Sprint is going against their word with the launch of Manhattan. 

 

Though I do understand your response.

  • Like 2
Link to comment
Share on other sites

This could be due to the network getting the extra load from those customers coming online to use the LTE or prob glitches due to the new cities been added.

 

Also, could be the many customers who might be pulling SPEED TESTS :)  

 

And last but not least customers who even though they knew they had LTE were annoyed of the NONWORKING LTE areas and and when possible just put their phones on CDMA only mode. They are now setting back to CDMA/LTE and are causing slow downs.

 

10-12mb is still above the QOS though :)

 

Hopefully it's just glitches and they fix them.   Today service was horrible in certain areas again, but others worked a little better.    At my house I usually average 4-5Mbps, but tonight I'm getting .63Mbps on 4G.   

 

 

At my Bartow job-site I was able to pick up LTE for a few seconds.    The location I'm in has them updating a tower, so that's probably why service is so bad.    I just hope service around here gets much better, for many reasons.

Link to comment
Share on other sites

Sprints coverage maps and sensorly say I'm in a 4g area but it connects to a weak signal unless I'm a couple of houndred feet away from the tower, my dBm is always -115 or -116.

 

One possible reason for this is the downtilt and proximity to the actual panels. Too close and you get next to nothing too far and you get nothing... double edge sword.

Link to comment
Share on other sites

One possible reason for this is the downtilt and proximity to the actual panels. Too close and you get next to nothing too far and you get nothing... double edge sword.

So, living close to a tower gives you crappie service. Great. My home area is now listed as fair LTE service. In fact, I get NO LTE service and weak or no 3G service. If this is the case on all carriers, I'm screwed at home.

 

Sent from my Samsung Galaxy S3 using TapaTalk 4

 

 

Link to comment
Share on other sites

So, living close to a tower gives you crappie service. Great. My home area is now listed as fair LTE service. In fact, I get NO LTE service and weak or no 3G service. If this is the case on all carriers, I'm screwed at home.

 

Sent from my Samsung Galaxy S3 using TapaTalk 4

 

Living extremelly close... could... if you live in a launched city you can call Sprint and open a trouble ticket. If you are not in a launched city you will have to wait as your city is still in testing phase.

Link to comment
Share on other sites

Living extremelly close... could... if you live in a launched city you can call Sprint and open a trouble ticket. If you are not in a launched city you will have to wait as your city is still in testing phase.

My city just launched this week. Sprint told me to turn off my LTE. They don't know if all the upgrades are done yet. They were supposed to do a ticket, but really didn't seem interested.

 

Sent from my Samsung Galaxy S3 using TapaTalk 4

 

 

  • Like 1
Link to comment
Share on other sites

So, living close to a tower gives you crappie service. Great. My home area is now listed as fair LTE service. In fact, I get NO LTE service and weak or no 3G service. If this is the case on all carriers, I'm screwed at home.

 

Sent from my Samsung Galaxy S3 using TapaTalk 4

 

The problem is probably not living close to the tower.  The problem is the OTHER signals from OTHER carriers emanating from the SAME tower interferring with Sprint's signal.

 

Or maybe the tower you live next to isn't a Sprint tower at all!!

 

In tests I've run, when right next to a Sprint tower I get full bars and a RX signal level in the -50 dBm range.  And voice and data quality is EXCELLENT.  BUT sometimes when I am driving past a cell tower that I know Sprint isn't using my signal level drops due to interference from that tower.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Quote from wsj; "The T-Mobile deal could be reached as soon as later this month, while discussions with Verizon on a separate transaction are expected to take longer or might not result in an agreement, the people said." "The rising value of wireless licenses is a driving force behind the deal. U.S. Cellular’s spectrum portfolio touches 30 states and covers about 51 million people, according to regulatory filings." https://specmap.sequence-omega.net/
    • From WSJ which is paywalled but they're reporting that T-Mobile and Verizon are working on a joint deal to buy and split up U.S. Cellular. https://www.wsj.com/business/telecom/t-mobile-verizon-in-talks-to-carve-up-u-s-cellular-46d1e5e6?st=qwngrnh4s3bcr76 — — — — —  Summary from a user in the Reddit thread:  
    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...