Jump to content

Breaking Band: Tri-band LTE / eCSFB issues thread


Recommended Posts

I didn't see that.  People kept saying call or chat with Sprint or connect your phone to adb and do logcat to search for a 6 digit number for your MSL.

Occom's Razor, bro... Y'all were doing all the crazy technical exploits...gotta love those dialer codes.

Link to comment
Share on other sites

Occom's Razor, bro... Y'all were doing all the crazy technical exploits...gotta love those dialer codes.

I know.  I took logic in college.  Guess I didn't pay attention. 

Link to comment
Share on other sites

Open a ticket and be sure to let them know you have 4 devices. Two of yours and two of other LTE devices. That way they can't say your device is bad.

I talked to a chat representativeAnd she said she would escalate it to their network team or something like that
Link to comment
Share on other sites

Easy way to tell, force LTE via hidden menu *#*#4636#*#* > Phone Info > LTE Only. If it works, its an eCSFB problem. 

 

I think I'm in an area with eCSFB enabled because I would make a phone call and then my LTE connection would be restored afterwards. I just tried changing my phone to LTE Only and I couldn't get a signal. I switched it back to "LTE/CDMA auto (PRL)" and now I can't get an LTE connection anymore. I should've remembered what the original setting was but I didn't keep track. Is "LTE/CDMA auto (PRL)" the default setting? I have a LG Nexus 5.

Link to comment
Share on other sites

I think I'm in an area with eCSFB enabled because I would make a phone call and then my LTE connection would be restored afterwards. I just tried changing my phone to LTE Only and I couldn't get a signal. I switched it back to "LTE/CDMA auto (PRL)" and now I can't get an LTE connection anymore. I should've remembered what the original setting was but I didn't keep track. Is "LTE/CDMA auto (PRL)" the default setting? I have a LG Nexus 5.

The default setting is LTE/GSM/CDMA auto (PRL), but as a Sprint user you should not see a difference with the setting you chose.

 

-Mike

Link to comment
Share on other sites

This is happening with me... I can see the LTE connection but I can't get any data from the tower while on "LTE" so ib won't v recieve text or get calls after awhile it itv drop down to 3g. The same thing was happening at another tower. They seemed to have changed the v tower Id as I don't v hat the same gci PCI as I was before now that I'm connecting again...

  • Like 1
Link to comment
Share on other sites

For those in Wilkes-Barre/Scranton, it looks like Sprint is starting to comb over the 1X areas as well. There are three towers going into the Back Mountain (Dallas/Shavertown area) with Samsung cabinets and antennas next to them ready to be installed. Looks like they were delivered over the past two weeks. I find it odd they just dumped them next to the towers. Anyone can take them. I doubt this area will see tri-band LTE as it wouldn't cover much, so I'm eager to see if my Nexus 5 will work well with the new equipment or not.

Edited by LongTermEvolution
Link to comment
Share on other sites

Is Sprint still activating 4G only towers? 3 towers just went LTE live today near my ome, but I cannot connect to any of them on my Nexus 5 unless I force 4G. I thought Sprint would only be activating LTE if 3G was activated at the same time. 

Link to comment
Share on other sites

Is Sprint still activating 4G only towers? 3 towers just went LTE live today near my ome, but I cannot connect to any of them on my Nexus 5 unless I force 4G. I thought Sprint would only be activating LTE if 3G was activated at the same time.

Negative. Sprint will no longer "launch" markets without CSFB being active. There is no harm in allowing an LTE site go live without CSFB. Because if you think about it, no one knows except those who read S4GRU maps.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 3
Link to comment
Share on other sites

Negative. Sprint will no longer "launch" markets without CSFB being active. There is no harm in allowing an LTE site go live without CSFB. Because if you think about it, no one knows except those who read S4GRU maps.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

 

So, if you're in a non launch market, they may still be doing so (last few map updates seem to confirm this in my area, or the 3G just hasn't been approved yet)?  It seems like they've been doing the whole let "LTE site go live without CSFB." here for a while now as they work their way across the area.

Link to comment
Share on other sites

Negative. Sprint will no longer "launch" markets without CSFB being active. There is no harm in allowing an LTE site go live without CSFB. Because if you think about it, no one knows except those who read S4GRU maps.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

Well, plenty of people who don't read S4GRU will be aware that their new tri-band phones are not connecting to LTE. For instance, my wife has an S4, which connects, and I have an N5, which doesn't connect. 

Link to comment
Share on other sites

Well, plenty of people who don't read S4GRU will be aware that their new tri-band phones are not connecting to LTE. For instance, my wife has an S4, which connects, and I have an N5, which doesn't connect. 

 

Yes, it will effect some people.  But what do you want them to do?  Would you rather that even SVLTE not be able to use them either?  If the 3G doesn't come online with the LTE, it is because it can't.  Not because they like alienating Triband device owners.  However, Sprint says that by the time they launch service in the market, they will make sure the 3G NV upgrades with CSFB are active by the time LTE launches in the market.

 

Robert

Link to comment
Share on other sites

N5 via Google

 

SEPA/Philadelphia Market.

 

Mixed results here on 3/4G accepted sites.

 

Some towers seem to allow LTE without an issue but some others causing problems.

 

3/4G tower covering 19525 no LTE connection, connects using 3G and every 3minutes drops the network completely and takes around 40sec to re-acquire then 3mins later drops it again repeating the sequence over and over.

3/4G tower covering 19486 i guess has the more typical issue, intermittent LTE, so connects using 3G then every 12mins connects to LTE for around 10secs before rolling back to 3G.

Link to comment
Share on other sites

Don't know if you are all are still keeping track of this. But Fredericskburg Va. is also having the tri band switch issue and it is consider as the Washington DC market.

On all sites?

Link to comment
Share on other sites

On all sites?

 

There are only 2 sites with LTE on it in that area. I have not gotten any on either.  I right on the Washingtion DC/Richmond market line and might check out the 2 Richmond towers in Spotsylvania county that should have LTE on it.

Link to comment
Share on other sites

There are only 2 sites with LTE on it in that area. I have not gotten any on either.  I right on the Washingtion DC/Richmond market line and might check out the 2 Richmond towers in Spotsylvania county that should have LTE on it.

I mean if you got outside of that area but inside the Washington DC Market, do you have any problems? We are still experiencing some problems in Incumbent markets like DC and here in MO where some sites(not very many) won't accept connections from non-SVLTE devices and as such kill the connection from surrounding sites as well. A lot of the sites were fixed a couple weeks ago but we still know of at least 2 problem sites here in MO Market.

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

    • Uploaded data without issues on Friday. Now with the latest update I am getting "Cluster #1 skipped: invalid file format detected. File exported for inspection." Doing same with all other clusters. Did this on 4 phones in a row.  Seems to work on s24 ultra just fine. On s21 ultra it says "web data upload failed. No data to send" although 8800 records were displayed. Now gives same error as above. I have not sent the data from 3 other phones.  All should have latest update.
    • After several months of testing, an update to SignalCheck Pro is rolling out on Google Play. It may take up to 48 hours to become available for download. Notable changes include: Added option to display site notes for NSA 5G-NR cells. Enabling this new option (Preferences > Display Settings > Show NSA 5G-NR Site Notes) will cause the app to make an "educated guess" as to what the most appropriate site note is linked to the connected NSA 5G cell, using the PCI and the device location. If it finds an existing entry that is likely to be relevant, it will display the note along with the distance from where the strongest signal from that cell was logged. While connected to NSA 5G, these notes cannot be edited; a valid NCI is required to add/edit notes and that information is not available on NSA connections.   Added option to log cells with missing/invalid PLMN (such as NSA 5G-NR cells). Users asked for the ability to log data for NSA 5G, so a new option (Preferences > Logger Settings > Log Cells with Missing PLMN) will permit this.   Added option to display LTE info above 5G-NR info. Enabling this new option (Preferences > Display Settings > Show LTE Cells Above 5G-NR Cells) shows the same information that is currently displayed, but moves the LTE information above the 5G-NR information. Other changes: Code optimizations and enhancements. Improved Android 15 compatibility. Overhauled Purchases module. Resolved force closes impacting some GSM/LTE connections. Resolved issue with improper 5G-NR PLMN display when NR/LTE PLMNs did not match. Resolved issue with improper PLMN display with single-digit MNCs. Resolved issue with incorrect 5G-NR bands displayed on some devices due to Android bug. Resolved issue with incorrect number of neighbor cells displayed when some cells were unknown. Resolved issue with missing 5G-NR data when sector display is enabled. Resolved issue with saving 5G-NR site notes when NR/LTE PLMNs did not match. Resolved issue with settings to log missing GCI/NCI/TAC/PLMN being ignored. Resolved issues with web data export function. Updated internal libraries. Updated provider database. Updated target API to Android 15. I appreciate all of your support, and a big thank you to the members of the Beta Crew that help with testing and feedback!
    • Oct security update is out.
    • Stopped by again today and the antennas are up but it isn't live just yet. If other Sprint conversions are anything to go by it'll likely take about a month for the site to go live.
    • It is an Android bug that was reportedly fixed in August 2023 but definitely has not been. I have implemented numerous workarounds in SCP to correct the NR bands the app displays. The OS ignores the possibility that many NR-ARFCNs are valid across multiple bands.. it reports the lowest NR band that is valid for the current ARFCN. In your example, channel 432530 can be n1, n65, or n66.. so the OS just (lazily) reports n1.   Awesome, thanks! I will add an n65 override also.
  • Recently Browsing

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