Jump to content

Breaking Band: Tri-band LTE / eCSFB issues thread


Recommended Posts

----

EDIT:

 

If this is your first time to this thread, please read this article by Robert (S4GRU Admin): 

 

http://s4gru.com/index.php?%2Fblog%2F1%2Fentry-357-nexus-5-and-lg-g2-experience-temporary-sprint-lte-connectivity-issues-due-to-circuit-switched-fallback-technology%2F

 

 

OP:

----

 

As more and more inconsistent LG G2 and Nexus 5 user observations have filtered in over the past few days, S4GRU has decided to reopen a thread that we created as a placeholder to address LTE connectivity issues, if necessary.

 

So, if you have a Sprint Spark tri band device -- especially but not limited to the LG G2 and Nexus 5 -- please report your LTE connectivity experience and location.

 

See my two hypothetical examples below...

 

 

Handset:  LG G2

LTE connectivity:  Great, LTE in places never had before

Location:  Smallville, AB 22222

 

Handset:  Nexus 5

LTE connectivity:  Weak, loses LTE or refuses to connect

Location:  Capital City, YZ 33333

 

 

Please keep this thread objective and factual.  Complaining about the situation serves no productive purpose. But gathering anecdotal evidence that we can cross reference with our Network Vision progress maps can help get to the bottom of the current issues.

 

Finally, expect further edits to this top post, especially as additional insider information and/or S4GRU technical analysis becomes available.

 

Thanks in advance for your reports...

 

AJ

 

------------------------------------------------

 

EDIT:

 

Follow this link for a Sprint memo explaining why Tri-Band devices are not connecting to LTE in some areas: http://s4gru.com/index.php?/topic/5001-tri-band-lteecsfb-issues-thread/page-3?p=235876&do=findComment&comment=235876

 

Follow this link for a breakdown of incumbent and non-incumbent markets, and what that means for your Tri-Band ("Spark") device: https://docs.google.com/spreadsheet/ccc?key=0AhjoCbLKCt72dHJKMTVrc3lrSE95cklOTnB0V0c0M1E&usp=drive_web#gid=0

 

We're still looking for additional reports, as this does not account for all issues.

 

-David

  • Like 17
Link to comment
Share on other sites

The thread is open.  Start submitting your reports.  S4GRU is on the case...

 

AJ

  • Like 4
Link to comment
Share on other sites

LG G2:

 

No LTE Connectivity al all.

 

Harrisburg, PA 17104, 17111

 

Hershey, PA 17033

 

Hummelstown, PA 17036

 

Steelton, PA 17113

 

No modifications or configuration changes to the handset. 

Link to comment
Share on other sites

LG G2:

 

No LTE Connectivity al all.

 

Harrisburg PA 17113, 17104

 

Ah, yes, please include in the report your chosen handset -- and if you have made any modifications or configuration changes to it.  I will make the appropriate revision to the top post.

 

AJ

Link to comment
Share on other sites

Raleigh, NC market. NEXUS 5.

 

LTE if forced in engineering, but no mobile network if set as such, cant make or receive calls. Phone must be set to 3G.

 

Sent from my Nexus 5

 

Edited by smorcy11
Link to comment
Share on other sites

Whats funny is I was having this issue for almost 2 days when I got the device but then it started working normally.

My guess is I was connecting to legacy 3g while 4g was coming from a different tower. They just finished upgrading my towers 3g so the issue went away.

  • Like 1
Link to comment
Share on other sites

Same as smorcy11 ^ above.  N5, Raleigh, NC market. I haven't tried forcing it from debug menu but zero LTE except when switching back and forth from Global/LTE, whereupon the icon switches momentarily to LTE but goes back to 3G.

Edited by cswiii
Link to comment
Share on other sites

LG g2, nexus 5. Lincoln, NE. 68504. No lte. (Connects for 1-2 seconds then falls back to 3g) -4g only accepted sites

 

Sent from my LG-LS980 using Tapatalk

. Will test the sites west of town that are 4G / 3G accepted.

 

Sent from my LG-LS980 using Tapatalk

 

 

Link to comment
Share on other sites

LG G2

 

Excellent 4G reception with no loss of voice or sms

 

Merrmiac, MA, 01860

 

Note: Traveling between Worcester MA and in the Greater Boston area today, 4G LTE worked as well as it did on my Note 3 so it seems to be fine in Central to Northeastern MA where LTE has been live for quite some time.

Edited by jfenton1957
  • Like 3
Link to comment
Share on other sites

So far all these areas look 'purple' to me.

 

Right.  And this "purple" hypothesis is what we want to test.  Scientific method -- you will not find that at a lot of other sites.  But S4GRU holds itself to a higher standard.  We hope that is why you keep coming back.

 

;)

 

AJ

  • Like 13
Link to comment
Share on other sites

Right.  And this "purple" hypothesis is what we want to test.  Scientific method -- you will not find that at a lot of other sites.  But S4GRU holds itself to a higher standard.  We hope that is why you keep coming back.

 

;)

 

AJ

well that and the funny videos. Keep up the good work :)

  • Like 2
Link to comment
Share on other sites

Nexus 5

Midtown Manhattan 10022

Connects to LTE but data speeds are slower than 3G

Same results before and after I enabled all bands.

 

Live in NJ, 07083, no official LTE but my N5 sometimes shows it is connected but slower than 3G speeds.

 

So is my issue related to what is going on here? I show that I am connected to LTE but my speeds are roughly .25 to .50 Mbps down.

Link to comment
Share on other sites

I am currently in the virgin islands and lte is working perfect on my nexus 5 but I will be back home in atlanta on thursday which has lots of band 41 sites all over the place.  I will give an update then.

  • Like 1
Link to comment
Share on other sites

Handset:  Nexus 5


When connected to LTE then going to making a phone call, will always default to 1x voice and not 1x800. (I'm in a heavily saturated 800SMR area)


Location:  Sycamore, IL 60178 & DeKalb, IL 60115


Link to comment
Share on other sites

. Will test the sites west of town that are 4G / 3G accepted.

 

Sent from my LG-LS980 using Tapatalk

. LTE works great west of Lincoln for the 3G/4g accepted sites

 

 

Screenshot_2013-11-09-19-35-17_zps6a7935

 

Sent from my LG-LS980 using Tapatalk

  • Like 1
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

    • 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.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
  • Recently Browsing

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