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.

 Share

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • ...and I just this morning realized you meant Cumberland, MD.  It threw me because there's an Ashby in Cumberland County, VA, which I'm far more familiar with. - Trip
    • I don't have anything solid to offer on Cumberland, but I came down US-15 today and the water tower site in Weber City is now up and running with B2/12/4/71 (035ACCxx), I believe I saw new T-Mobile antennas on the tower at Sprouses Corner which I will try to confirm on Saturday (definitely not running if they're there), and I believe I may have connected to something that got converted in Farmville.  By process of elimination, my guess is Lancer Park, but I hope to find out tomorrow or Saturday. So upgrades are clearly coming.  You may want to see if your local government officials can tell you anything.  Probably not, but can't hurt to ask. - Trip
    • Interesting twist.  Today, I took off for southern Virginia and had my T-Mobile B71 phone (Revvlry on Android 10) and I noticed the GPS was bad as compared to my other two devices on SCP on the dash.  Couldn't get it to clear by toggling the Location Services box, so I quit and restarted SCP. When I did so, it first came up with the bad coordinates, then extremely rapidly zipped through from where it was stuck all the way up to where I was currently, like the coordinates were backlogged and then suddenly flushed out within a few short seconds.  More bizarrely, I noticed the same behavior on two other devices (Pixel 3a and Moto One 5G Ace, both on Android 11) and had to do the same thing to those.  I also dumped my trails on all three, assuming they were all bad by then.  The rest of my devices were correct. I was barreling down the highway at the time, so I couldn't investigate further.  Other than my quoted message above, I've never seen this behavior before, and now it seems to be widespread.  - Trip
    • Does anyone have any updates to the Cumberland/Mineral County area? Specifically looking to get TMHI in Ft. Ashby.
    • Actually, you are correct. It is possible Dish won't take it. Meanwhile both Dish and T-Mobile pretend they don't want it for negotiation purposes.
  • Recently Browsing

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