Jump to content

Pattern of bad connections to legacy network sites with LTE phones?


Recommended Posts

I don't yet have an LTE-capable phone because I am keeping my powder dry for the moment. But I have been watching several forums lately, and notice an unexplained pattern:

 

Some end users of the EVO 4G LTE and Galaxy S III -- and I emphasize some -- report anecdotally what is typically described as "poor signal" when connecting to the legacy Sprint network They generally say that a certain location they used to get good connections and displayed "bars" on their previous handsets, but the LTE-capable models show weak signal and might even kick into roaming mode.

 

Of course, this leads to some angry comments that "this phone radio sucks," etc. But I am not at all convinced that the antennas or radio sensitivity on these new phones are really the root cause, but rather suspect some interaction between the handsets and the network -- which may be running side-by-side with the NV network under construction. I am wondering what might account for this. For example, in certain areas could the phones not be playing well with a developmental NV tower whose signal is being broadcast but blocked, so the phone can't lock onto the legacy tower base station that it should be using? Or even being fooled by eHRPD upgrades as Robert suggests in this case.

 

Sprint surely is aware of these issues, but publicly is not saying much.

 

Note that this is a different case from the EVO 4G LTE anomaly reported here involving faulty connections to a live LTE test site. The case I am talking about is that of LTE-capable phones with bad connections to a legacy site.

 

Ideas? What should such users do to isolate and troubleshoot the problem?

Link to comment
Share on other sites

I am planning a radio performance comparison article between three new LTE devices and three WiMax devices being tested in various strong signal and mid signal and edge of service conditions.

 

Robert via Galaxy Nexus using Forum Runner

  • Like 8
Link to comment
Share on other sites

Another naive theory: Could it simply be that in cases where the new NV network is installed side-by-side with the legacy network, blasting away but being blocked, the NV signal (or at least its pilot channel) is interference that clobbers the Ec/Io of the legacy tower?

Link to comment
Share on other sites

Another naive theory: Could it simply be that in cases where the new NV network is installed side-by-side with the legacy network, blasting away but being blocked, the NV signal (or at least its pilot channel) is interference that clobbers the Ec/Io of the legacy tower?

 

Once a site has upgraded 3G equipment, the legacy equipment is turned off. The only thing being blocked from what I've read here is LTE, not 3G/EVDO.

Link to comment
Share on other sites

I don't yet have an LTE-capable phone because I am keeping my powder dry for the moment. But I have been watching several forums lately, and notice an unexplained pattern:

 

Some end users of the EVO 4G LTE and Galaxy S III -- and I emphasize some -- report anecdotally what is typically described as "poor signal" when connecting to the legacy Sprint network They generally say that a certain location they used to get good connections and displayed "bars" on their previous handsets, but the LTE-capable models show weak signal and might even kick into roaming mode.

 

Of course, this leads to some angry comments that "this phone radio sucks," etc. But I am not at all convinced that the antennas or radio sensitivity on these new phones are really the root cause, but rather suspect some interaction between the handsets and the network -- which may be running side-by-side with the NV network under construction. I am wondering what might account for this. For example, in certain areas could the phones not be playing well with a developmental NV tower whose signal is being broadcast but blocked, so the phone can't lock onto the legacy tower base station that it should be using? Or even being fooled by eHRPD upgrades as Robert suggests in this case.

 

Sprint surely is aware of these issues, but publicly is not saying much.

 

Note that this is a different case from the EVO 4G LTE anomaly reported here involving faulty connections to a live LTE test site. The case I am talking about is that of LTE-capable phones with bad connections to a legacy site.

 

Ideas? What should such users do to isolate and troubleshoot the problem?

 

I'm actually experiencing that on my EVO LTE it constantly loses signal then roams all day when I normally would have full signal. I'm missing phone calls and text messages too. I think it has something to do with the radio in the new EVO because everyone that I know that has one is talking about the same problems. I can't even call out all the time, I have to restart my device a lot just to make and receive calls. Its so sad because the phone is awesome and when it does work on 3G its much faster than my old EVO 3D.

Link to comment
Share on other sites

I noticed that as well on my Gnex. I was out for a drive this morning, and noticed poor signal in places that my Epic Touch would be fine. I'm referring to real dB differences.

 

Hopefully it's a fluke.

Link to comment
Share on other sites

I noticed that as well on my Gnex. I was out for a drive this morning' date=' and noticed poor signal in places that my Epic Touch would be fine. I'm referring to real dB differences.

 

Hopefully it's a fluke.[/quote']

 

I don't think it's a fluke. That's my observation as well. :(

 

Robert via Kindle Fire using Forum Runner

Link to comment
Share on other sites

I have generally the same service with my EVO LTE as I did with my Of EVO. I'm in San Antonio, maybe its a region specific issue? 3g speeds are faster than my wife's epic touch 4g.

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

    • As far as I know it's ubiquitous. Ultimately the network decides if you should use VoNR vs VoLTE but pretty much anytime my phone is in standalone mode and I place a call, it goes over NR.   Yup, it was terrible. After a while, I just connected to the WiFi, and that worked fine at about 90Mbps. I get the feeling that rather than doing a "real" upgrade where they install new antennas, upgrade backhaul, etc., T-Mobile instead installed new radios onto the existing and already overloaded DAS and called it a day, which isn't enough. Compared to Yankee Stadium, where they actually went and deployed new antennas/radios for their n41 upgrade, and you're able to get upwards of 200Mbps at sold-out games, Arthur Ashe really is a joke. What's worse is that the folks in their NOC likely know this already, but no effort is being made to change that. I'm not asking for T-Mobile to deploy mmWave everywhere like Verizon but there is a real use case for it at stadiums.
    • Does anyone know how well implemented is VoNR in the 5 boroughs. Does anyone use it? I have an iPhone 15 Pro. Does anyone know if T-Mobile is still working on upgrading their network? It seems like the service has gone down. My phone struggles in parts of the Belt Pkwy, and data is slow. 
    • I come to the US Open men’s semifinals and finals every year, and I’ve never been able to use my T-Mobile phone successfully. Usually AT&T is the top performer—good to hear Verizon has upped their game. 
    • One sector down, two more to go — — — — —  I was at Arthur Ashe Stadium for the U.S. Open today and the good news is that there is an n25/41 DAS setup throughout USTA Billie Jean King National Tennis Center. From the "boardwalk" to the outdoor concession area, to inside the stadium; you connect to standalone n41 and n25 everywhere via oDAS and iDAS. The bad news is that in the actual stadium it's beyond useless. While I saw strong coverage as indicated by signal bars and I was able to make calls and send texts, there was no data throughput at all. Running a speed test failed 9 out of 10 times. The only time I got a speed test to work was by switching to LTE funnily enough or by using NSA 5G where the test would initiate via LTE and then n41 would kick in giving me ~20Mbps. T-Mobile has so much traffic on their 5G network that now n41 gets bogged down before LTE. That was a first for me! In the stadium in the same area Verizon got 1.2Gbps on mmWave and LTE kept timing out when trying to test it. My Boost line on AT&T got upwards of 150Mbps on C-band and I know they have mmWave deployed as I saw their Nokia mmWave antennas deployed but I was unable to test it. In the outdoor concession area T-Mobile performed well getting over 150Mbps on n41. AT&T in these areas saw over 250Mbps on C-band and I didn't get the opportunity to test Verizon there. It just seems like 140MHz n41 is not enough capacity for the amount of people inside the stadium. Hopefully T-Mobile is considering deploying n258 to all of these stadiums since they now own that mmWave nationwide. It'd make a world of difference in terms of capacity at these venues. Bonus Pics: Verizon and AT&T mmWave Hidden carrier neutral DAS: 
  • Recently Browsing

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