Jump to content

Why is Sprint's 4G LTE Signal so bad almost everywhere [in my area]?


Recommended Posts

I haven't seen any decent results from B26 yet, it's the same strength as B25 for the most part.

 

I have not experienced optimized B26 yet either, and I've been up and down the Northeast plenty of times in plenty of cities. Maybe this will be a springtime task up here, I know another member from NC said his area just got optimized down there. 

Link to comment
Share on other sites

I have not experienced optimized B26 yet either, and I've been up and down the Northeast plenty of times in plenty of cities. Maybe this will be a springtime task up here, I know another member from NC said his area just got optimized down there.

Here's hoping it's soon, it would make the experience so much better.

 

Sent from my Nexus 5

Link to comment
Share on other sites

In my experience samsung devices hold on to a LTE signal better than HTC. I don't care for the Samsung as I have been loyal to HTC for years. Touch Pro, TP2, HTC EVO (wimax), EVO 3D, Evo LTE, M7, M8 and of course will be getting the M9. I have friends that use Samsung and I have used Samsung phones temporally usually your signal strength is a few points higher and they won't roll to 3G as much as the HTC's. Even an old Galaxy S3 would get 2-3 "bars" where my M8 would get one on my home tower. This is my personal experience but it's been that way for as long as I can remember even on the old wimax devices. Back in the day the sanyo phones with retractable antenna were king for reception. 

Holding on to the LTE signal for to long may actually give you worse performance.

Link to comment
Share on other sites

why exactly would they put up equipment and not optimize it then and there? does it really take that long to 'optimize'?

Different groups of workers. I found that band 25 was optimized within weeks but band 26 that started popping up in January still is not optimized
  • Like 1
Link to comment
Share on other sites

Yep. B25 "initial optimization" is essentially a flip of a switch that whoever signs off on the installation can do in a few minutes. B26 optimization requires hours if not days per individual tower of testing settings.

Link to comment
Share on other sites

A friend of mine who works for Ericsson (Sprint's network maintenance) told me that LTE 800 can't be optimized until enough sites that neighbor each other are put into operation, almost every site needs to have 800 except two or three within a larger cluster. When they do optimize a cluster they will leave one on the edge of a cluster non-optimized as a "buffer" to the other sites that are still awaiting optimization to avoid interference.  

 

On another note I aggravate him once a week to get the last three sites in my town put into LTE operation. Good news is that he is suppose to call me before it happens so I can watch a site get integrated with LTE. :)

  • Like 6
Link to comment
Share on other sites

If you're receiving -80dbm on EVDO and -110 on LTE then other you're not connected to the site you think you are, or downtillt hasn't been adjusted at the site.

 

In my experience, per signal check, the LTE (B25) signal is always 25-30dbm weaker than EVDO. I find that unless your EVDO signal is -75 or better you are at risk of dropping LTE. For example, if the evdo signal is -80dbm, the LTE signal will be -105 to -110 and will sometimes drop out completely. And I know for sure it is coming from the same tower. Places where I have almost full bars of 3G can have only 1 bar LTE. I don't know why it is so weak but I hope it improves.. Maybe something is wrong with my phone. No B26 here either so it is almost impossible to get LTE inside buildings at all.

  • Like 1
Link to comment
Share on other sites

In my experience, per signal check, the LTE (B25) signal is always 25-30dbm weaker than EVDO. I find that unless your EVDO signal is -75 or better you are at risk of dropping LTE. For example, if the evdo signal is -80dbm, the LTE signal will be -105 to -110...

 

http://s4gru.com/index.php?/blog/1/entry-308-rssi-vs-rsrp-a-brief-lte-signal-strength-primer/

 

AJ

  • Like 2
Link to comment
Share on other sites

 

Right, I know the RSRP is a different value that is always lower. But in terms of comparing 3g and LTE coming from the same site, my point was that on B25, the signal starts to become unusable past -105 (my experience). Since -105 LTE (b25) seems to correlate with -75 to -80 on evdo (1900mhz) from the same tower, this leads to large areas with poor or no LTE even when 3G is very strong. Basically any area where I was used to -80 to -100 evdo (perfectly useable) has marginal or nonexistant LTE coming from the same tower. This creates a lot of gaps in the LTE coverage that will hopefully be resolved by B26.

 

We do have B41 here, which oddly enough seems provide more/better coverage than B25. B41 seems to hold on to much lower RSRP values (down to -120 or -125), which actually seems to provide a better experience than the B25 at -110dbm.

 

Again this is just my experience. 

Link to comment
Share on other sites

Right, I know the RSRP is a different value that is always lower. But in terms of comparing 3g and LTE coming from the same site, my point was that on B25, the signal starts to become unusable past -105 (my experience).

 

If LTE becomes unusable below -105 dBm RSRP, your network or device is malfunctioning.

 

AJ

  • Like 1
Link to comment
Share on other sites

If LTE becomes unusable below -105 dBm RSRP, your network or device is malfunctioning.

 

AJ

Yes AJ, I can verify what you said by actual usage.   I can work with LTE at a -115 level but the download speed will be significantly slower than with a stronger signal.   As I go below -115, the speed gets even slower and I find that most often, it is the transmit from the phone that can not be received at the cell site.  Between -115 and 120, if the phone can successfully transmit a strong enough signal toward the cell site, you can still receive data from the cell site.

  • Like 1
Link to comment
Share on other sites

If LTE becomes unusable below -105 dBm RSRP, your network or device is malfunctioning.

 

AJ

 

Must be then I guess, although this is my second phone so it must be the towers. B41 chugs along perfectly fine to much lower RSRP, but b25 definitely falls apart for me after 105.

Link to comment
Share on other sites

  • 4 months later...

Ive had pretty good luck with Sprint in the back of stores with 3g. It gets me enough data to browse the web efficiently and make calls. However since getting my Nexus 5 I have much greater coverage with the band 26 LTE.

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

    • Just installed the update, and it's good!  As you recommended, I turned off both TA adjustments, and turned on displaying it when it's zero.  The value is basically spot-on.  It's bouncing between 18 and 19 for the Cameron Valley site, and it is in fact between 0.87 and 0.92 miles, as displayed in the app.  This is probably a better estimate of the TA values than any other device I own provides. As far as the -44 goes, I'll have to take it out and verify that it no longer records those cases. If this device didn't have that annoying reset problem, and got the Android 14 update (and in so doing supported TA on NR and continued to allow band locking), it would easily be the best device I own.  Easily.  And would be the device I standardize on for the 5G era.  I'll probably have to wait for a future device to come out with Android 14 and then see what happens. And I know I didn't have to, but I love SCP.  It is my primary tool for tracking the goings-on of the various networks and is very easy to use and work with across my 10 phones.  I am very happy to send a token of my appreciation your way now and then.  Thanks again! - Trip
    • Sorry, I misread your message -- yes, the app would show 0 if an invalid value was being reported. I don't think I had any MediaTek devices myself, but the beta testers have had a decent variety of devices over the years.   Sorry, I didn't word that very well in my last post -- I added an option to control display of LTE TA when it is 0. By default it will now be hidden (sadly a lot of devices do not show it) but anyone who wants to display it can adjust accordingly. There will be 3 user-selectable options related to LTE TA now -- the existing correction option, correction on LTE-TDD (which is independent/in addition to the existing correction option), and TA:0 display. In your case, I'd disable the TDD option and enable the TA:0 option; the defaults will be the opposite of what I think you need.   You did not have to do that, but I sincerely appreciate it, thank you! Beta update is rolling out now, let me know how it goes.
    • In order: This is very helpful to know.  Thanks. That makes a lot of sense, though it's showing me zero rather than nothing; it looks like if it's calculating a negative number, I'm seeing zero instead.  It makes me wonder how many devices you've tested against which use the MediaTek chipset.  This is only the second one I've used, and the first one was very, very old (didn't have B41), so it's possible that the MediaTek chip doesn't need the correction while others do.  Separately, I doubt that a real world case will ever see 1282, so I imagine any value above 1281 could be ignored. I would ask you to please not hide TA values of 0, or if you hide them by default, add an option to not hide them.  I am aware that, for example, the S22 doesn't report a valid TA value and always reports zero, but zero is a legitimate value and is useful to know when trying to identify sites. I'll look forward to your impending update, and I'm going to send along another donation if I can find the link.  Thanks so much, as always!  - Trip
    • I received the reports, thanks! You didn't catch it happening (it captures the diagnostics as soon as you hit send or long-click the connection banner on the main screen), and I had sent you an e-mail to clarify which value was -3.. but your screenshots confirmed my hunch that you meant RSRQ!   I know exactly what is happening here. Somewhere along the way, I learned that TD-LTE bands (33-53) needed a TA correction of -19 applied, and I confirmed it on several devices. Perhaps that is no longer universally true.. but what you're seeing SCP display matches that correction. Below 19 you see nothing, at 19 you see 0, and above that you see TA-19. The upper limit is 1282, which is why you see 1263. Your phone must report 1282 when the TA is unknown, which is not technically safe but I can work around that. Funny enough, I had a change to TA coming in the next update that had nothing to do with your issues.. TA:0 will be hidden moving forward, since several devices report 0 when it cannot be identified. I'll have an app update out shortly that addresses all of this, let me know how it works for you and thanks for the detailed feedback!
    • Mike, We ended up going out this morning to do errands in spite of the tropical storm.  I locked the phone on LTE B41, turned off the TA correction checkbox, and watched it carefully while out and about.  I have four screenshots for you. https://imgur.com/a/kCPTCnB First, I happened to get a screenshot of it doing the -44 dBm thing.  I also tried to send you at least one set of diagnostics showing the -44 dBm but I don't know where precisely in the process it collects the diagnostics.  Hopefully there's something useful in them. The rest of the screenshots are far more interesting.  All three were taken within seconds of each other in the CVS parking lot.  The phone's diagnostic screen shows a TA of 17, and oddly, the SCP diagnostics screenshot also appears to show a TA of 17.  But SCP's normal display is showing 0.  Not entirely sure what to make of that.  It looks like SCP won't show me a value other than 0 until I hit about 19 according to the phone diagnostic screen. It also appears that when SCP is showing a TA of 1263, that's the equivalent of a null value for the TA--no TA is calculated.  The phone diagnostic screen appears to show just "12" when that's happening; the SCP diagnostic screen shows 1282 in the TA section when that happens, a difference of 19, which is highly convenient given what I noted above about the TA value.  (I can't test that the phone diagnostic screen is limited to two characters and is thus truncating 1282 to just "12" as I suspect given where I am right now.  Had I known to be looking for it, I'd have tested in the middle of nowhere yesterday.) Anything catch your eye?  Anything I can do to help more?  - Trip
  • Recently Browsing

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