Jump to content

Network Vision/LTE - Chicago Market


thesickness069

Recommended Posts

There should be only HSPA in band C... But it could well be that TMUS is also cramming GSM channels into the guard bands built into HSPA.

 

Knowing GSM interferes like a mother (ask AJ about it), that seems like the likely possibility.

  • Like 2
Link to comment
Share on other sites

How can we verify?  Would Sprint verify? And if T-Mobile is the cause of the interference what will happen?

 

Sprint is not likely to comment, for legal reasons, unless they file an FCC complaint or a lawsuit.  What we need is someone with a spectrum analyzer to go into the city and look at the G Block and the adjacent frequencies. Hypothetically, if TMO is the cause, they would get slapped with some very hefty fines.

Link to comment
Share on other sites

. . .  According to AJ and other sources, Sprint has initially deployed 1900 LTE on PCS Block G (1910-1915MHz and 1990-1995MHz). PCS Block C (1895-1910MHz and 1975-1990MHz) falls directly below Block G, and is operated by T-Mobile in Chicago. The frequencies above Block G are not mobile communication, and I have no idea what they are used for. So, is the ultra-urgent TMO LTE deployment in Block C somehow responsible for the Sprint LTE mess? Or is something going on in the frequencies above 1995, and is THAT somehow responsible?

 

 

And a later note: TMO also occupies all of C Block in the St. Louis market, but does not have the C Block band adjacent to G Block in Minneapolis.  What has their experience been?

 

See the chart at:

 

http://www.google.com/imgres?imgurl=http://2.bp.blogspot.com/-pj4vuAanG1g/Uc3Hf4eyCdI/AAAAAAAAAUQ/4BwgaajgDzQ/s1102/uscellular_chicago_pcs.JPG&imgrefurl=http://allnetlabs.blogspot.com/&h=614&w=1102&sz=200&tbnid=_b503cgiADZAdM:&tbnh=90&tbnw=162&zoom=1&usg=__9nCMl-2pHzdJqXpAhxhNIcYcMn0=&docid=rWUks6D4xSLtDM&sa=X&ei=_Vd8UofCDsTmsATghYDQCw&ved=0CGQQ9QEwBg

Link to comment
Share on other sites

attachicon.gifScreenshot_2013-11-07-19-27-58.png

 

I am currently in downtown Colorado Springs, and the LTE screenshot I am posting above is a site about 1.7 miles east of me (although the 1xRTT address is offset to the west), based on the latest NV map update. The RSRP is poor, but the SNR is very good. Speeds between .6 and 2.0 down, .25 and 1 up, ping low 100's. Technically, Colo Springs is pre-launch, but the SNR number is fairly typical of what I have seen in recent trips to California, Missouri, and Colorado

 

That said, some comments on the Great Chicago SNR Debacle. One of the customers at the user group meeting that I am attending operates an extensive, combined wireless/wired ISP on a Caribbean island. I showed him the "Red Line" screen shot from earlier today (-55 dBm RSPR, 0.1 dB SNR), and based on his experience, his immediate comment was that there was MAJOR interference from an adjacent frequency, and that whoever is responsible is violating the law. Mobile phones are very good at cutting through noise (my phrase) on the frequencies they are programmed to receive, but cannot not cope well with noise on either side of a given frequency.

 

Which leads to some questions: According to AJ and other sources, Sprint has initially deployed 1900 LTE on PCS Block G (1910-1915MHz and 1990-1995MHz). PCS Block C (1895-1910MHz and 1975-1990MHz) falls directly below Block G, and is operated by T-Mobile in Chicago. The frequencies above Block G are not mobile communication, and I have no idea what they are used for. So, is the ultra-urgent TMO LTE deployment in Block C somehow responsible for the Sprint LTE mess? Or is something going on in the frequencies above 1995, and is THAT somehow responsible?

 

The Sprint D and E blocks are voice/CDMA at this time, and it is not likely that they would be impacted by the same interference that might affect LTE in the G Block. And as far as we know, Sprint hasn't started using, at least at full power, the USCC segment of Block B, so that probably isn't causing a problem, and Verizon (which owns the rest of the B block) hasn't done anything radical that we know of, so that probably isn't the cause.

 

Someone way earlier in this thread asked if TMO might be the cause of Sprint's Chicago LTE problem. Based on the spectrum allocation and on TMO's ultra-aggressive LTE deployment, the answer may very well be "Yes!!!!!"

 

FWIW

This is some seriously good stuff and some serious acquisition of malpractice.  The symptoms of band interference match exactly what we are dealing with here with metro wide degraded SNR, even when literally ontop of a tower.  Though what exactly are we supposed to do with this kind of information now?  I doubt SprintCare would be any assistance, this is way above any CS agent's pay grade, this is call your lawyers and call the FCC type stuff.

  • Like 1
Link to comment
Share on other sites

Anyone know a good one to buy for a decent price? Links?

 

Digiblur recently bought one, I think there is a thread, but don't have a clue how to find it.  PM him???

Link to comment
Share on other sites

This is some good stuff, folks. Problem solving at work. It's a shame that it takes a handful of people on a forum to diagnose what their network issues are. A multi-billion dollar company in the middle of their biggest network upgrade in history, teams of engineers across the country, and it takes a forum to figure it out. ????

Link to comment
Share on other sites

This is some good stuff, folks. Problem solving at work. It's a shame that it takes a handful of people on a forum to diagnose what their network issues are. A multi-billion dollar company in the middle of their biggest network upgrade in history, teams of engineers across the country, and it takes a forum to figure it out.

I suspect Sprint knows what the issue is, I just don't think they will confirm what it is.

  • Like 2
Link to comment
Share on other sites

I suspect Sprint knows what the issue is, I just don't think they will confirm what it is.

 

Right. There might even be impeding legal action. Who knows. They'll never come out and admit it, assuming this is the cause of slow speeds here.

Link to comment
Share on other sites

Yeah, I suspect Sprint won't say anything, what will likely happen is the problems will suddenly cease because of actions happening at a level far above our pay grade.

 

If they don't do anything, more and more customers are jumping ships with 100kb LTE speeds. I think someone needs to prove in fact it is an interference and tweet that to Mr Son.  Maybe he will do something.

Link to comment
Share on other sites

Hesse is not active on Twitter. Imagine reporting such an issue to John Legere on his Twitter, I bet we would have a response,

I got Legere to fix a nationwide network problem over the summer when I was on a one-month trial on tmus. He reads twitter and responds to customers daily. We need something like that.

Link to comment
Share on other sites

This actually would make sense T-Mobile likely has in the same vicinity as sprint. That's why we are seeing a 55 RSRP (insane signal strength) but horrid SNR.

 

Sent from my HTCONE using Tapatalk

 

 

Link to comment
Share on other sites

This actually would make sense T-Mobile likely has in the same vicinity as sprint. That's why we are seeing a 55 RSRP (insane signal strength) but horrid SNR.

 

Sent from my HTCONE using Tapatalk

It's the best theory that we have to date. Now, it just needs to be proven and fixed. Even though it has been an ongoing issue for approximately 6-8 weeks, we have to just assume Sprint knows about this (if it's truly the problem). Now we just play the waiting game.

Link to comment
Share on other sites

Although it probably wouldn't prove anything I would like to see a spectrum analyzer to see if there is interference from a neighboring band. I'm not sure if I can but I will see if I can fire one up at work. No promises though.

 

Sent from my HTCONE using Tapatalk

 

 

  • Like 3
Link to comment
Share on other sites

Although it probably wouldn't prove anything I would like to see a spectrum analyzer to see if there is interference from a neighboring band. I'm not sure if I can but I will see if I can fire one up at work. No promises though.

 

Sent from my HTCONE using Tapatalk

 

Post on Youtube please if indeed T-Mobile is bleeding over.

Link to comment
Share on other sites

If I can get access to a SA and I can check the band please everyone keep in mind that even if it shows that there is signal in the guard band between the Sprint G block and T-Mobile it probably won't prove that T-Mobile is the cause and it for sure won't prove that T-Mobile is intentionally doing it. I really don't want an industry event created from the picture.

 

Sent from my HTCONE using Tapatalk

 

 

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

  • Similar Content

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