Jump to content

Sprint TD-LTE 2500/2600mhz Discussion


Recommended Posts

Now I know why we aren't discovering 800 lte coverage.

 

I wish you all would set the priority to 26, 41, 25. So you see SMR first then BRS then PCS.

 

Sent from my HTC One using Tapatalk 2

 

No point though, I don't believe LTE is deployed at all on 800mhz.

Link to comment
Share on other sites

No point though, I don't believe LTE is deployed at all on 800mhz.

I think his point is that it can be any day now that we could see LTE 800 so why not set priority to B26 on highest.

 

I agree with u in that I think its still too early to assume any LTE 800 is currently deployed.

 

Sent from my Motorola Photon 4G using Tapatalk 2

 

 

  • Like 1
Link to comment
Share on other sites

IPhone 5s might support LTE TDD so hopefully this year's version is triband

 

The trials and tribulations of tri band...

 

:P

 

AJ

  • Like 2
Link to comment
Share on other sites

I think his point is that it can be any day now that we could see LTE 800 so why not set priority to B26 on highest.

 

I agree with u in that I think its still too early to assume any LTE 800 is currently deployed.

 

Sent from my Motorola Photon 4G using Tapatalk 2

 

Considering the last reports from Rob peg 800 1x deployment at <1%, I seriously doubt we'll see 800mhz LTE soon. Also, that should strictly be a fallback, and the priority should be 41, 25, 26, in my opinion.

Link to comment
Share on other sites

Considering the last reports from Rob peg 800 1x deployment at

I agree that B26 should be last priority from a network standpoint once LTE is deployed on all bands and the ordee should be B41, B25, B26.

 

I think what makes this community so great compared to other sprint forums is that a lot of the members share information on their findings especially with network vision progress (permit maps and pics of sites in progress, etc) and i think we are all just trying to look for evidence that LTE 800 is underway. We have evidence of LTE 2600 deployed and thats great but what most sprint customers care about is LTE 800 which is really going to be a game changer with indoor penetration and also usable data for those that are just outside of 1900 mhz range.

 

Sent from my Motorola Photon 4G using Tapatalk 2

 

 

  • Like 1
Link to comment
Share on other sites

I agree that B26 should be last priority from a network standpoint once LTE is deployed on all bands and the ordee should be B41, B25, B26.

 

I think what makes this community so great compared to other sprint forums is that a lot of the members share information on their findings especially with network vision progress (permit maps and pics of sites in progress, etc) and i think we are all just trying to look for evidence that LTE 800 is underway. We have evidence of LTE 2600 deployed and thats great but what most sprint customers care about is LTE 800 which is really going to be a game changer with indoor penetration and also usable data for those that are just outside of 1900 mhz range.

 

Sent from my Motorola Photon 4G using Tapatalk 2

I personally care more for 800 mhz voice than I do LTE. Low signal kills battery life and I often find myself having to go nearer to windows on the current Sprint 1900 mhz signal I get. 

  • Like 1
Link to comment
Share on other sites

I personally care more for 800 mhz voice than I do LTE. Low signal kills battery life and I often find myself having to go nearer to windows on the current Sprint 1900 mhz signal I get.

Everyone has their priorities.

Link to comment
Share on other sites

So the hand off on a city expressway should be good going from 2600 to 2600? This is asuming the best signal and prl order has 2600 first.

If site density is high enough, handoff shouldn't be any different than from 1900 to 1900.

  • Like 1
Link to comment
Share on other sites

So the hand off on a city expressway should be good going from 2600 to 2600? This is asuming the best signal and prl order has 2600 first.

 

A PRL is a cdmaOne/CDMA2000 thing.  It has almost no bearing on LTE.

 

AJ

  • Like 1
Link to comment
Share on other sites

On my way to Venice Beach and picking up Band 41 all over the place. :)

 

Posted Image

 

Sent from my SPH-L900 using Tapatalk 4

Glad to hear that TD-LTE is working in LA!

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

  • Like 2
Link to comment
Share on other sites

Glad to hear that TD-LTE is working in LA!

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Yep, they've still got a long way to go though. Upon arriving at Venice Beach, it all became Band 25. I'll still take though.

 

Sent from my SPH-L900 using Tapatalk 4

 

 

  • Like 2
Link to comment
Share on other sites

On my way to Venice Beach and picking up Band 41 all over the place. :)

 

Posted Image

 

Sent from my SPH-L900 using Tapatalk 4

What's the channel bandwidth?
Link to comment
Share on other sites

Honestly, I didn't even check. I'm not certain how to find that out on my Zing.

 

I have not seen any engineering screen readout on the Netgear tri band hotspot that specifies LTE carrier bandwidth.  But no way are you getting 34 Mbps down, 18 Mbps up out of a 10 MHz TDD carrier, nor a 5 MHz FDD carrier.  The process of elimination indicates a 20 MHz TDD carrier.

 

AJ

  • Like 3
Link to comment
Share on other sites

So the hand off on a city expressway should be good going from 2600 to 2600? This is asuming the best signal and prl order has 2600 first.

I handed off to dozens of TD-LTE 2600 sites in Denver. Had zero problems. Worked flawlessly, even while streaming.

 

Robert via Samsung Galaxy Note 8.0 using Tapatalk

 

 

  • Like 5
Link to comment
Share on other sites

Now I just need TDE LTE on my towers and a phone that uses it.

 

You might be waiting a while for "TDE LTE"...

 

;)

 

AJ

  • Like 8
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • 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.
    • Yeah both of those instances were on my AT&T s22 ultra. Seems ro be working as intended today in latest release.
  • Recently Browsing

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