Jump to content

Certain Phones Won't Work after 7/1/16?


Recommended Posts

Hammondsport is not affected by these changes. 

If I understand this correctly, the phone may work in Hammondsport now and in the future, but if he travels to another area it might not work. Am I wrong on that?

Link to comment
Share on other sites

If I understand this correctly, the phone may work in Hammondsport now and in the future, but if he travels to another area it might not work. Am I wrong on that?

You are correct. Just may not work in the areas outlined on map. Keep prl updated if possible.

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

Almost everything done with the eNB are software configurations that are pushed out remotely. 

 

The T-mobile and Verizon swap deals are still pending in the FCC. 

 

See here for the ATT / SPR markets that will be the first ones to swap. 

Will any of these markets get wideband LTE after the swaps are complete?

Link to comment
Share on other sites

That's the whole point!

 

Sent from my LG G4

I would not call it wideband. More like putting Sprint on even ground with other carriers having at least a 10x10

 

Sent from my SM-N920P using Tapatalk

  • Like 2
Link to comment
Share on other sites

I would not call it wideband. More like putting Sprint on even ground with other carriers having at least a 10x10

 

Sent from my SM-N920P using Tapatalk

 

No, Tim just meant wider channels. I understood what he was asking. Just wider channels, 10x10 or eventually the possibility of 15x15.  (It is known that "wideband LTE" is just a marketing term and doesn't actually mean anything).

  • Like 2
Link to comment
Share on other sites

No, Tim just meant wider channels. I understood what he was asking. Just wider channels, 10x10 or eventually the possibility of 15x15. (It is known that "wideband LTE" is just a marketing term and doesn't actually mean anything).

It's actually implied to be 15/20 MHz FDD LTE to be called wideband at least by tmobile.

 

The only wideband b25 markets are Chicago and Columbus Ohio with 10x10 +5x5 PCS carriers (10+5).

I would not call it wideband. More like putting Sprint on even ground with other carriers having at least a 10x10

 

Sent from my SM-N920P using Tapatalk

 

Sent from my Nexus 5X

  • Like 1
Link to comment
Share on other sites

It's actually implied to be 15/20 MHz FDD LTE to be called wideband at least by tmobile.

 

The only wideband b25 markets are Chicago and Columbus Ohio with 10x10 +5x5 PCS carriers (10+5).

 

 

Sent from my Nexus 5X

Any other markets in a position for wideband in the future?

 

Sent from my SM-N920P using Tapatalk

Link to comment
Share on other sites

Any other markets in a position for wideband in the future?

 

Sent from my SM-N920P using Tapatalk

Yes, plus you have a number with 10x10 or b25 second carrier. It is really done a county by county basis. Obviously you want a sizable group of counties with enough contiguous bandwidth.

 

Sent from my LGLS991 using Tapatalk

Link to comment
Share on other sites

Any other markets in a position for wideband in the future?

 

Sent from my SM-N920P using Tapatalk

 

Any markets with at least 40 MHz total of PCS preferably contiguous but this entails shutting down CDMA down to 3x 1.25 MHz carriers + guardbands in 10 MHz of PCS spectrum. 

 

This is a bit further away until Sprint can densify its network and bring more LTE as a base level coverage. Shut down CDMA EVDO 3G too early and it's Ok to abysmal performance on the few remaining carriers may collapse since there won't be LTE coverage to cover the areas where EVDO demand is high and where spectrum was refarmed from. 

Link to comment
Share on other sites

It's actually implied to be 15/20 MHz FDD LTE to be called wideband at least by tmobile.

 

The only wideband b25 markets are Chicago and Columbus Ohio with 10x10 +5x5 PCS carriers (10+5).

 

 

Sent from my Nexus 5X

It's only really called wideband if it allows for speeds of 100mbps+. 10x10 can't do that.

 

Sent from my SM-G900P using Tapatalk

Link to comment
Share on other sites

It's actually implied to be 15/20 MHz FDD LTE to be called wideband at least by tmobile.

 

The only wideband b25 markets are Chicago and Columbus Ohio with 10x10 +5x5 PCS carriers (10+5).

 

 

Sent from my Nexus 5X

It's also that way with vzw. Where vzw has it which they call XLTE is 15x15 and some 20x20. That's on band 4. Vzw does have some cities with 15x15 band 2. att also has 15x15 band 2 in select places like California.

 

Sent from my SM-G900P using Tapatalk

Link to comment
Share on other sites

Very old feature phones. 

How about the Katana II, or Diamond or HTC TP2?

How about Syracuse, NY and surrounding areas? The maps is too small to resolve around Upstate, NY...

Edited by monkeyboy
Link to comment
Share on other sites

There is no such as wideband or xlte they are both purely marketing terms used to make companies LTE networks look better than others.

there is no such thing as lte plus either. Either way it is no secret that Sprint needs more FDD spectrum and I'm glad they are doing something about it.
Link to comment
Share on other sites

Any markets with at least 40 MHz total of PCS preferably contiguous but this entails shutting down CDMA down to 3x 1.25 MHz carriers + guardbands in 10 MHz of PCS spectrum. 

 

This is a bit further away until Sprint can densify its network and bring more LTE as a base level coverage. Shut down CDMA EVDO 3G too early and it's Ok to abysmal performance on the few remaining carriers may collapse since there won't be LTE coverage to cover the areas where EVDO demand is high and where spectrum was refarmed from. 

 

Looks like it's happening sooner than expected. Baton Rouge went live today with 2C B25, and there certainly hasn't been any densification effort there.

  • Like 2
Link to comment
Share on other sites

Looks like it's happening sooner than expected. Baton Rouge went live today with 2C B25, and there certainly hasn't been any densification effort there.

 

That's good news. Joins Cincinatti / Dayton as a 20 MHz PCS A-F market with only 3 CDMA carriers left over after LTE refarming. 

Link to comment
Share on other sites

That's good news. Joins Cincinatti / Dayton as a 20 MHz PCS A-F market with only 3 CDMA carriers left over after LTE refarming.

I hope this is only happening in small-medium markets. I can't imagine Sprint doing this for cities such as San Francisco or Houston. Too many users to risk call reliability.

 

God forbid a hurricane rolls into the BR area. Because if it does, Sprint may regret refarming those CDMA carriers.

Link to comment
Share on other sites

That's good news. Joins Cincinatti / Dayton as a 20 MHz PCS A-F market with only 3 CDMA carriers left over after LTE refarming.

It's really good they're getting aggressive with that. And it makes sense.

 

A network vision site without high capacity magic/RF combiners can only handle 4ish PCS CDMA carriers depending on vendor, right? The only places where having 10+ CDMA carriers spread over 15+ MHz FDD makes sense is in city cores where you can have, say, one site with CDMA on channels 225, 250, and 275, another site with CDMA on channels 300, 325, 350, and 375, and another site with channels 725, 750, and 775 within a few blocks of each other without interference. (That's more or less how it is in uptown Charlotte.) Where I'm at, about 2/3rds of those carriers are EVDO.

 

But in hyper-dense environments like that where density is so great that some sites have 800 disabled, you're gonna be on LTE pretty much all the time anyway. And you'd be on LTE even more with a 10x10 that has better edge cell and interference performance than a 5x5. So it makes sense that they'd refarm three or four (depending on contiguity) EVDO carriers for LTE.

 

Because in the rest of a market, sites are far enough apart that you can have all of them pretty much broadcasting the same three or four CDMA carriers. So you've got almost 10Mhz FDD sitting unused over large portions of the market if it's 15 FDD A-F. (It's already like that in Charlotte.)

 

This should be pretty easy in a 15 MHz A-F market provided adequate density in the center-city, and it appears it can be done in a 10 MHz market too given the right conditions.

 

Of course this is all armchair conjecture, but it all feels right to me. I hope now that most markets are 95+% LTE complete Sprint looks at their options for refarming like this.

Link to comment
Share on other sites

That's good news. Joins Cincinatti / Dayton as a 20 MHz PCS A-F market with only 3 CDMA carriers left over after LTE refarming. 

 

Actually, four CDMA2000 carriers and one 5 MHz FDD carrier could fit within a PCS A-F block 10 MHz FDD (20 MHz) contiguous spectrum market.  LTE already has built in internal guard bands, so Sprint needs to trim down the unnecessarily large 0.625 MHz external guard bands for CDMA2000.  See the math:

 

4(1.25) + 1(4.5) = 9.5

 

That still leaves 0.5 MHz for guard bands against the adjacent licenses and between CDMA2000 and LTE.

 

AJ

Link to comment
Share on other sites

Actually, four CDMA2000 carriers and one 5 MHz FDD carrier could fit within a PCS A-F block 10 MHz FDD (20 MHz) contiguous spectrum market.  LTE already has built in internal guard bands, so Sprint needs to trim down the unnecessarily large 0.625 MHz external guard bands for CDMA2000.  See the math:

 

4(1.25) + 1(4.5) = 9.5

 

That still leaves 0.5 MHz for guard bands against the adjacent licenses and between CDMA2000 and LTE.

 

AJ

 

Unfortunately they went with EARFCN 8109 for the whole market.

 

I hope this is only happening in small-medium markets. I can't imagine Sprint doing this for cities such as San Francisco or Houston. Too many users to risk call reliability.

 

God forbid a hurricane rolls into the BR area. Because if it does, Sprint may regret refarming those CDMA carriers.

 

Funny you should mention that, because everybody flocked to Nextel when Katrina hit and took out all the other networks.

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...