Jump to content

Breaking Band: Tri-band LTE / eCSFB issues thread


Recommended Posts

 

Handset:  Nexus 5

When connected to LTE then going to making a phone call, will always default to 1x voice, no higher.

Location:  Sycamore, IL 60178 & DeKalb, IL 60115

 

 

These non SVDO, non SVLTE handsets are always going to fallback to CDMA1X while in call.  There will be nothing "higher."  

 

So, can you explain a bit further?

 

AJ

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

 

 Fixed.

Link to comment
Share on other sites

 Fixed.

 

CDMA1X 800 is not intended to be every Sprint user's sandbox.  It will be there when you need it.  If you can access CDMA1X 1900, then you do not need CDMA1X 800 at that moment.

 

AJ

Link to comment
Share on other sites

CDMA1X 800 is not intended to be every Sprint user's sandbox.  It will be there when you need it.  If you can access CDMA1X 1900, then you do not need CDMA1X 800 at that moment.

 

AJ

 

So why did my GSIII always connect to 1x800 when available but my N5 does not? Was that strictly a by-product of an SVLTE device? 

Link to comment
Share on other sites

I purchased my Google Nexus 5 directly from Sprint and received it yesterday. Today, while I was driving with my wife in parts of Milwaukee where 4G LTE is live, my Nexus 5 stayed on 3G, while my wife's Iphone 5S lit up with LTE.

 

I just called Sprint business tech support and reported the issue. All they did was refresh my network services and told me to call back if the 4G does not light when I return to a 4G area.

Link to comment
Share on other sites

Lg G2-conneted to the LTE tower only for about 5 seconds and then back to 3g. Brooklyn/Cleveland Ohio. Updated prl and profile but haven't checked to see if it helped, I don't live in that area.

Link to comment
Share on other sites

So why did my GSIII always connect to 1x800 when available but my N5 does not? Was that strictly a by-product of an SVLTE device? 

 

Yes, that could be a contributing factor.  The Galaxy S3 has both SVDO and SVLTE capabilities.  We do not entirely know how these tri band, non SVDO, non SVLTE handsets will function in comparison/contrast.  Our sample sizes are simply too small at this point.  So, we have to observe now, reserve conclusions for later.

 

AJ

  • Like 2
Link to comment
Share on other sites

The speed of your LTE should not be affected by this. either you can connect or you can't.

Thanks, I am going crazy trying to figure out why my speeds are the way they are. Is there another way for me to see exactly what I am connected to when my signal bar is showing LTE?

Link to comment
Share on other sites

Yes, that could be a contributing factor.  The Galaxy S3 has both SVDO and SVLTE capabilities.  We do not entirely know how these tri band, non SVDO, non SVLTE handsets will function in comparison/contrast.  Our sample sizes are simply too small at this point.  So, we have to observe now, reserve conclusions for later.

 

AJ

 

Thank you, I'm sorry to keep pushing this minor issue by comparison to others, but its important to me.

Link to comment
Share on other sites

Thanks, I am going crazy trying to figure out why my speeds are the way they are. Is there another way for me to see exactly what I am connected to when my signal bar is showing LTE?

Lte discovery and Signal check are both good.

  • 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

 

 

 

my LG G2 connects fine to 1x 800

 

Sent from my LG-LS980 using Tapatalk

 

I can connect, just not when going from LTE to a phone call.

  • Like 1
Link to comment
Share on other sites

LG G2, Louisville and Shepherdsville, Kentucky, works as good as my S3. Had issues at first but changed from global to cdma/lte and started working normal. I even have b26 enabled and set to higher priority. No problems with calling or texting while on lte. Seems to be good. Very few 3g acceptances here so legacy Ericsson must be compatible with NV Ericsson.

 

Sent from my LG-LS980 using Tapatalk

 

 

  • Like 1
Link to comment
Share on other sites

Here is an N5 connected to a 4G only site in St. Louis/Missouri Market. Stock, unmodified. Sigh of relief!

Posted Image

lilG, glad you got your phone. In my unscientific testing its the towers that you have as yellow on your map that the tri band phones are having issues with. Purple ones are fine.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

Nexus 5

Portland, OR

I can only connect to LTE forced through engineering near my house (all purple towers), but just south there is a non-purple tower that I randomly connected to.

 

According to LTE engineering, the serving cell was 458 on Band 25

 

Serving cell 132 also on band 25

 

I did not drive down to the other section of the city that is 3G/800/4G to see if those work.

 

Also, after reading many many comments, I was able to look at some other regions where people have reported the same issue, and it looks to be the same story.  Areas dominated by 4G only (SF) down to south bay (3G/4G) as well as Raleigh (4G) -> Wilson (3G/4G)

Link to comment
Share on other sites

Nexus 5. St Paul Minneapolis area (near Metrodome). No LTE now when I had it on my Galaxy s3. Purple areas causing issues. I drove south 20-25 miles into the yellow area (a little south of Lakeville) and had LTE. On the completed maps the 4g only purple area is what is causing my issues apparently.  I can force it to LTE in the 4636 menu but it will not do it on its own.

  • 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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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