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

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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