Jump to content

  •  

Most Liked Content


#1766 Network Vision/LTE Deployment Running List

Posted by S4GRU on 17 February 2012 - 02:12 PM

We use this thread to keep track of all the markets announced or completed with Network Vision and LTE deployment. It will be Pinned to the top of the Network Vision Forum. This will be convenient for linking so you can post in other threads and forums.

TOTAL NUMBER OF MARKETS (99)

 

FIRST ROUND MARKETS (14):
First round markets have no preceding markets before them. NV OEM's will mobilize in these markets and begin deployment. These markets will deploy slowly as there is a significant learning curve to Network Vision. Most first round markets started between December 2011 and March 2012.

 

Updated as of  Friday, March 6, 2015.




#84487 OldSpottingThread (Ericsson Style) [Abandoned]

Posted by digiblur on 27 December 2012 - 02:07 PM

Everyone take a seat in the desks....and welcome to Sprint RRU Spotting 101. 
 
First lets look at what to NOT look for. In our area, AT&T has RRUs that look almost identical to the ones Sprint has. They are both made by Ericsson.
 
 
 
The box circled above is NOT an RRU. Do not confuse these. These are probably some sort of junction box and/or amplifier that AT&T used on previous deployments. Take note of the size.
 
 
 
Hey that's an RRU! Yep. One big problem though. Where are the others? Not to mention the antenna next to it is another give away. We will get to that in a minute. Since there is only one RRU located on this sector and antenna, this is NOT Sprint's.
 
 
 
Let's look at the cables. Notice there are only 2 hooked up the antenna itself? (Do not confuse the ACUs hanging out of the bottom). There are 4 inputs on this antenna but only 2 are used. Easier to see in the next picture. Again this is AT&T's equipment for LTE.
 
 
 
See what I'm talking about now? AT&T is only using one side of this antenna. Hence the one RRU. Those other little pieces sticking out of the bottom are actually stepper motors that change the downtilt of the antenna from a remote location. They daisy chain from one another.
 
 
 
This is a different site. Do you notice the same thing? One RRU with only 2 cables on the one antenna. This is AT&T again. "But but..where's Sprint?" Read on...
 
 
 
Looks like the same RRU right? Count them! 2 back to back, then one at the top. Some sites will have more depending on the traffic.
 
 
 
Look! It's three RRU's again.
 
 
 
Now let's look at the antennas. Notice how the cables are right up at the front of the antenna and not in the center? Also, count them. There are 6 inputs. 2 for PCS 1X/EV, 2 for 800SMR, and 2 for PCS LTE. There are also 3 ACUs for downtilt control (more on that later). See how all the cables are hooked up?
 
ymDHMkJ.jpg

 

 
Six cables all hooked up again. Creates almost a "wall" of cables where you can't even see the ACU's tucked in behind them.
 
 
 
A little different angle. But again 6 cables hooked up. Look behind the cables on the bottom of the antenna and you can see the 3 ACUs with the RFS stickers on them. This allows Sprint to remotely control the downtilt of all three interfaces all independently. 1X/EV, 800SMR, PCS LTE, could all have their own downtilt setting. If another site comes online or even another site is added later due to capacity or to thicken coverage. Sprint could change the downtilt angles of the adjacent sites all without ever visiting the site.
 
There's also another type of antenna to look for on Network Vision upgrades. See below:
 
 
This antenna is a narrow beamwidth antenna used in some dense urban areas and even rural areas to "shoot" down the interstate to the next city. This different antenna is circled on the sector on the left. Notice the regular antenna on the left? You can also see the narrow beam legacy antennas with the "fins" on the sides of them on the same sector. But once again the dead give away are the multiple RRU's behind the antenna. (Thanks to kevins669 in the NOLA market thread for this picture)
 
I hope these graphics and explanations can help you recognize the Sprint equipment in your area. Just remember, every tower is different due to the thousands and thousands of variables between sites. If you are ever in doubt, take a picture and post it. You have to learn some how... that's what I did. Then you'll take on the addictive hobby of taking pictures like I have of the sites above.

 

Ericsson Network Vision Basestation Cabinets

 

 

 

http://imgur.com/adS...1zQZr,ymDHMkJ#0




#2158 Network Vision/LTE Deployment Running List

Posted by S4GRU on 20 February 2012 - 02:16 AM

SECOND ROUND MARKETS (28):
There is a lot of variability of when Second Round markets start, approx. between July 2012 and December 2012.

 

 

Updated as of  Friday, March 6, 2015.




#46043 LTE Plus / Enhanced LTE (was "Sprint Spark" - Official Name for the T...

Posted by S4GRU on 17 September 2012 - 03:17 PM

NOTE:   This information is starting to get obsolete.  It only pertains to single band Sprint LTE devices (2012-2013) running Android versions before 4.3.  This does not apply to any Triband LTE devices, iPhones and any LG Android devices.  They do show LTE signal accurately.  We are maintaining this pinned thread because there are a lot of older Uniband devices out there.  Many being resold on the market and being passed down.

Did you know that with many Sprint (Uniband) LTE Android devices, the signal strength indicator at the top does not show your LTE signal strength? Even if 4G or LTE is displayed next to it?

That's right!  This signal displayed here is your 1x (voice signal), and it is not your 3G EVDO signal strength, nor your LTE signal strength.  Regardless of whether it says 3G or 4G next to it. This is the cause of a lot of confusion.  Also, third party apps like NetMonitor do not show accurate LTE signal strengths. They also only show the 1x signal strength, even though they may reference being connected to LTE.

The purpose of this thread is to help educate the masses, because many people think they have a strong LTE signal, when in fact they do not. And then they are unhappy, thinking that Sprint LTE is really slow, even with a strong signal. LTE performance is very signal strength dependent. So, when you have a weak signal, you can expect much slower than peak results.

There is only one accurate way to get your LTE signal strength, and that is from your LTE Engineering screen in your Debug menu. And we will discuss the different ways to get that below.

...In HTC, Motorola & LG Sprint LTE devices:

  • Go in to your phone app, and dial ##DEBUG#
  • Select LTE Engineering
  • Go down to RSRP. The number under RSRP shown in dBm is your LTE signal strength.

...In Samsung Sprint LTE devices:

  • Go in to your phone app, and dial ##DEBUG#
  • Enter 777468 for your lock code
  • Select LTE Engineering
  • Go down to RSRP. The number next to RSRP shown in dBm is your LTE signal strength.

...In the Galaxy Nexus, Nexus 5:

  • Go in to your phone app, and dial *#*#DEBUG#*#*
  • Enter 777468 for your lock code
  • Select LTE Engineering
  • Go down to RSRP. The number next to RSRP shown in dBm is your LTE signal strength.

The LTE Signal Strength Scale:

Now you have determined your actual LTE signal strength in dBms your device is receiving, you can use the following scale below to determine its strength:

  • Better than -88dBm RSRP is a strong signal
  • Between -89dBm and -96dBm is a very good signal
  • Between -97dBm and -105dBm is good
  • Between -106dBm and -112dBm is fair
  • Worse than -113dBm RSRP is poor

Feel free to link people to this thread for explanation. Hopefully, this will clear up some confusion out there!

 




#267069 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 15 January 2014 - 05:56 PM

Site acceptance reports from Monday (1/13) and Tuesday (1/14):

  • Alabama – 6 updates (3 LTE)
  • Albuquerque – 1 update (LTE)
  • Arkansas – 2 updates (1 LTE)
  • Atlanta/Athens – 3 updates (2 LTE)
  • Baltimore – 308 updates (307 CDMA 800)
  • Boston – 465 updates (5 LTE, 458 CDMA 800)
  • Central Iowa – 6 updates (LTE)
  • Central Jersey – 4 updates (LTE)
  • Charlotte – 14 updates (12 CDMA 800)
  • Chicago – 2 updates (LTE)
  • Cincinnati – 32 updates (4 LTE, 27 CDMA 800)
  • Cleveland – 4 updates (LTE)
  • Colorado – 63 updates (7 LTE, 55 CDMA 800)
  • Columbus – 9 updates (1 LTE, 1 CDMA 800)
  • East Kentucky – 1 update (LTE)
  • East Texas – 2 updates (1 LTE)
  • GA/SC Coast – 1 update (LTE)
  • Houston – 61 updates (2 LTE, 57 CDMA 800)
  • Indianapolis – 127 updates (127 CDMA 800)
  • Inland Northwest – 58 updates (58 CDMA 800)
  • Jacksonville – 2 updates (1 LTE)
  • Kansas – 3 updates (1 LTE, 1 CDMA 800)
  • LA Metro – 396 updates (3 LTE, 393 CDMA 800)
  • Las Vegas – 6 updates (LTE)
  • Long Island – 1 update (LTE)
  • Louisiana – 1 update (LTE)
  • Lower Central Valley – 1 update (LTE)
  • Milwaukee – 4 updates (LTE)
  • Minnesota – 341 updates (1 LTE, 339 CDMA 800)
  • Mississippi – 4 updates (3G)
  • Missouri – 5 updates (3G)
  • Nashville – 1 update (LTE)
  • New Orleans – 1 update (3G)
  • New York City – 344 updates (2 LTE, 341 CDMA 800)
  • Norfolk – 1 update (3G)
  • North LA – 1 update (3G)
  • Northern Connecticut – 4 updates (3 LTE)
  • Northern Jersey – 2 updates (LTE)
  • Oklahoma – 2 updates (LTE)
  • Oregon/SW Washington – 279 updates (2 LTE, 277 CDMA 800)
  • Orlando – 4 updates (3 LTE)
  • Philadelphia Metro – 4 updates (3 LTE)
  • Phoenix – 5 updates (LTE)
  • Pittsburgh – 4 updates (LTE)
  • Providence – 1 update (LTE)
  • Raleigh/Durham – 3 updates (3G)
  • Riverside/San Bernardino – 4 updates (LTE)
  • Rochester – 12 updates (LTE)
  • San Diego – 9 updates (7 LTE)
  • SF Bay - 359 updates (358 CDMA 800)
  • South Bay – 147 updates (146 CDMA 800)
  • South Carolina – 1 update (LTE)
  • Southern Connecticut – 43 updates (1 LTE, 42 CDMA 800)
  • Southern Jersey – 7 updates (LTE)
  • South Texas – 2 updates (3G)
  • South West Florida – 1 update (LTE)
  • Tampa = 6 updates (1 LTE)
  • Tucson/Yuma – 1 update (LTE)
  • Upper Central Valley – 68 updates (2 LTE, 65 CDMA 800)
  • Upstate NY Central – 1 update (LTE)
  • Upstate NY East – 2 updates (LTE)
  • Utah – 56 updates (3 LTE, 48 CDMA 800)
  • VT/NH/ME – 3 updates (2 LTE)
  • Washington DC – 391 updates (2 LTE, 389 CDMA 800)
  • West Iowa/Nebraska – 153 updates (3 LTE, 150 CDMA 800)
  • West Kentucky – 8 updates (2 LTE)
  • West Michigan – 106 updates (5 LTE, 101 CDMA 800)
  • West Texas – 4 updates (3 LTE)
  • West Washington – 2 updates (1 LTE)

Maps are updated.  The big CDMA 800 numbers are not a typo.  I'm finally caught up to date on CDMA 800 acceptances.  Thanks to radem for helping me to automate that process!

 
Robert

Links: Comments regarding this threadNV Sites Complete Map




#172829 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 22 July 2013 - 07:10 AM

Site acceptance reports from Thursday (7/18), Friday (7/19) and Saturday (7/20):

  • Alabama – 1 update (LTE)
  • Albuquerque – 1 update (LTE)
  • Arkansas – 8 updates (4 LTE)
  • Atlanta/Athens – 7 updates (3G)
  • Austin – 9 updates (6 LTE)
  • Baltimore – 1 update (3G)
  • Boston – 5 updates (2 LTE)
  • Central Jersey – 3 updates (2 LTE)
  • Cincinnati – 1 update (3G)
  • Cleveland – 4 updates (3G)
  • Colorado – 9 updates (1 LTE)
  • Delaware – 1 update (3G)
  • DFW – 3 updates (3G)
  • East Kentucky – 1 update (LTE)
  • East Michigan – 11 updates (LTE)
  • East Texas – 1 update (LTE)
  • Ft. Wayne/South Bend – 2 updates (LTE)
  • GA/SC Coast – 3 updates (3G)
  • Georgia – 5 updates (LTE)
  • Gulf Coast – 1 update (LTE)
  • Houston – 5 updates (3G)
  • Indianapolis -1 update (LTE)
  • Jacksonville – 5 updates (3 LTE)
  • Kansas – 7 updates (3 LTE)
  • LA Metro – 8 updates (4 LTE)
  • Las Vegas – 3 updates (3G)
  • Louisiana – 2 updates (LTE)
  • Memphis – 5 updates (3 LTE)
  • Miami/West Palm – 5 updates (1 LTE)
  • Milwaukee – 1 update (LTE)
  • Minnesota – 12 updates (7 LTE)
  • Mississippi – 5 updates (3 LTE)
  • Missouri – 11 updates (5 LTE)
  • Myrtle Beach – 1 update (3G)
  • Nashville – 16 updates (8 LTE)
  • New Orleans – 6 updates (2 LTE)
  • Norfolk – 1 update (LTE)
  • Northern Connecticut – 1 update (3G)
  • Northern Jersey – 4 updates (3 LTE)
  • Oklahoma – 6 updates (5 LTE)
  • Orange County – 3 updates (3G)
  • Oregon/SW Washington – 4 updates (LTE)
  • Phoenix – 4 updates (3G)
  • Providence – 3 updates (3G)
  • Riverside/San Bernardino – 4 updates (2 LTE)
  • Rochester – 3 updates (3G)
  • San Antonio – 4 updates (1 LTE)
  • San Diego – 9 updates (4 LTE)
  • South Bay – 1 update (LTE)
  • Southern Connecticut – 4 updates (3G)
  • Southern Jersey – 4 updates (3G)
  • South Texas – 5 updates (4 LTE)
  • South West Florida – 4 updates (3 LTE)
  • Tucson/Yuma – 1 update (3G)
  • Upper Central Valley – 1 update (LTE)
  • Upstate NY Central – 1 update (3G)
  • Upstate NY East – 3 updates (2 LTE)
  • Utah – 5 updates (1 LTE)
  • VT/NH/ME – 1 update (3G)
  • Washington DC – 7 updates (3G)
  • West Iowa/Nebraska – 2 updates (LTE)
  • West Kentucky – 1 update (LTE)
  • West Texas – 7 updates (LTE)
  • West Washington – 5 updates (LTE)
  • Winston/Salem – 2 updates (LTE)

Maps are updated.  This was a lot of work with a 100kbps connection in the remote wilds of South Central Colorado.

 

Robert

Links: Comments regarding this threadNV Sites Complete Map




#35684 Frequently Asked Questions

Posted by pyroscott on 30 July 2012 - 05:47 AM

Without further ado, here is the official S4GRU FAQ. Hopefully this can answer your questions, a search of the site, or google search may also be able to find the answer to your question if it is not on here. Otherwise feel free to ask the members of S4GRU. The old saying says "there is no such thing as stupid questions" after all. Hopefully one of the other members can help you out.
S4GRU SITE FAQ
What are the standards and expected behaviors of this site?
See S4GRU Posting Guidelines thread.
 
Who are the administrators and staff who run this site?
See S4GRU Staff thread
 
I haven't posted yet but I want to follow a particular post, thread or map. How can I?
First off, welcome to the forums, second, don't be shy, post in the thread. This way you would automatically get a email reminder when new posts are added to the thread. If you still don't want to post and just follow, then just click on the "Follow this topic" button.
 
There are way too many map and device threads, is there a directory or index?
Yes, just click on any of the the link to get to the list of…
Directory of All S4GRU Maps
Sprint LTE Device Release Dates
History of Sprint Devices (coming soon)
For Future use
 
How come I can only see a few maps and not the ones with more detail?
We provide numerous maps showcasing the markets being upgraded to Network Vision. Some of these are very detailed and are only provided to members that have donated to the upkeep of our site. These sponsor and premier sponsor members get access not only to these maps but to other Network Vision threads.
 
Ok, I love what you are doing here, so how do I become a Sponsor/Premier Sponsor?
Please see the Information about S4GRU Sponsorship levels and how to become a Sponsor thread.
 
I think a post is inappropriate, what should I do?
Click the report button and leave a comment of why you are reporting it. This will alert the Moderating team, who will address the post.
 
I am a sponsor but I am unable to access the sponsor forums using Tapatalk. What can I do?
You can add the S4GRU Lounge to your favorites in Tapatalk and access it through the favorites tab , or you can try out the ForumRunner app. Currently there is a problem with Tapatalk and the way they authenticate access to the protected forums, and they have stated that they are not going to fix the problem.
 
How do I attach a picture to a post?
The thread "Adding images to Posts" shows you how to add images to your posts.
 



#135146 Potential Sprint rural buildout by 2016

Posted by WiWavelength on 02 May 2013 - 12:39 PM

A frequent point of contention here at S4GRU is Sprint rural buildout.  Some argue that Sprint needs to add more rural coverage to compete with the VZW and AT&T duopoly.  Others counter that doing so would not pass the cost benefit analysis test.  Well, an impending regulatory issue may partly satisfy both camps.

I am not sure why this did not occur to me until just the other day, but as a side effect of its acquisition of Nextel, Sprint will have to deploy, at a bare minimum, some additional "license protection" footprint within the next three years.  

To explain, Nextel's PCS G block 10 MHz licenses are nationwide but geographically divided by BEA.  See the map linked below:

http://wireless.fcc....ata/maps/ea.pdf

The FCC chose a BEA licensing scheme because that corresponds with the licensing scheme used for Nextel's SMR 800 MHz spectrum, some of which Nextel agreed to relinquish in the Public Safety 800 MHz rebanding arrangement.  The PCS G block is, thus, compensatory spectrum designed to align with Nextel's remaining SMR 800 MHz spectrum.

Now, Sprint's traditional PCS A-F block licenses are all based on MTA or BTA geographic divisions.  The 30 MHz MTA and BTA based licenses require one third POPs coverage within five years and two thirds POPs coverage within 10 years.  The 10 MHz and 15 MHz BTA based licenses require one fourth POPs coverage within five years.  Sprint satisfied those construction requirements roughly a decade ago.  See those maps linked below:

http://wireless.fcc....ta/maps/mta.pdf
http://wireless.fcc....ta/maps/bta.pdf

But here is the regulatory issue that Sprint faces in the next three years.  Sprint holds PCS G block licenses in BEAs where it never had to construct a network because Sprint satisfied its PCS A-F block buildout requirements in the more densely populated areas of several very large MTAs.

For example, see Sprint's PCS G block license for the Great Falls, MT BEA:

http://wireless2.fcc...?licKey=3130353

The first buildout deadline, requiring "substantial service," is just a little bit less than three years from now.  And Sprint currently has no native footprint anywhere in Montana.  The same deadline and requirement hold for all PCS G block licenses across the country.

So, the likes of Great Falls, Billings, and Missoula, MT; Minot, ND; Rapid City, SD; and Scottsbluff, NE, etc., are apt to see, at the very least, a few PCS G block LTE 1900 "license protection" sites in the coming years.

And, by that time, SMR 800 MHz should be completely unencumbered outside of the IBEZ.  Thus, Sprint may even use the PCS G block construction requirement as a means to deploy CDMA1X 800 and LTE 800, too.  This may even help to explain why Sprint has chosen Montana as the location for its LTE 800 FIT area.

AJ


#2467 Network Vision/LTE Deployment Running List

Posted by S4GRU on 22 February 2012 - 12:38 AM

THIRD ROUND MARKETS (30):
Below are markets that are in the Third Round, with scheduled starts from December 2012 to May 2013. However, some markets with GMO sites have started a little earlier.

 

 

Updated as of  Friday, March 6, 2015.




#221311 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 16 October 2013 - 03:48 PM

Site acceptance reports from Thursday (10/10), Friday (10/11), Saturday (10/12), Sunday (10/13), Monday (10/14):

  • Alabama  -  12 updates ( 3G )
  • Arkansas  -  3 updates ( 1 LTE )
  • Atlanta/Athens  -  20 updates ( 2 LTE )
  • Baltimore  -  3 updates ( 3 LTE )
  • Buffalo  -  1 update ( 1 LTE )
  • Boston  -  8 updates ( 4 LTE )
  • Central Illinois  -  5 updates ( 5 LTE )
  • Central Jersey  -  1 update ( 1 LTE )
  • Central Pennsylvania   -  7 updates ( 2 LTE )
  • Chicago  -  9 updates ( 9 LTE )
  • Cincinnati  -  8 updates ( 8 LTE )
  • Cleveland  -  5 updates ( 3G )
  • Columbus  -  6 updates ( 6 LTE )
  • Delaware  -  2 updates ( 2 LTE )
  • DFW  -  21 updates ( 13 LTE )
  • East Iowa  -  1 update ( 1 LTE )
  • East Kentucky  -  3 updates ( 3 LTE )
  • East Michigan  -  29 updates ( 3G )
  • East Texas  -  6 updates ( 5 LTE )
  • Ft. Wayne/South Bend  -  4 updates ( 4 LTE )
  • GA/SC Coast  -  9 updates ( 4 LTE )
  • Georgia  -  6 updates ( 6 LTE )
  • Gulf Coast  -  4 updates ( 4 LTE )
  • Houston  -  22 updates ( 5 LTE )
  • Indianapolis  -  3 updates ( 2 LTE )
  • Jacksonville  -  4 updates ( 4 LTE )
  • Kansas  -  24 updates ( 6 LTE )
  • LA Metro  -  14 updates ( 9 LTE )
  • Las Vegas  -  15 updates ( 9 LTE )
  • Long Island  -  2 updates ( 1 LTE )
  • Louisiana  -  4 updates ( 4 LTE )
  • Lower Central Valley  -  1 updates ( 1 LTE )
  • Memphis  -  13 updates ( 7 LTE )
  • Miami/West Palm  -  4 updates ( 3 LTE )
  • Milwaukee  -  1 update ( 3G )
  • Minnesota  -  6 updates ( 1 LTE )
  • Missouri  -  20 updates ( 20 LTE )
  • Myrtle Beach  -  4 updates ( 2 LTE )
  • Nashville  -  6 updates ( 3 LTE )
  • New Orleans  -  2 updates ( 2 LTE )
  • New York City  -  13 updates ( 7 LTE )
  • Northern Connecticut  -  3 updates ( 3G )
  • Northern Jersey  -  4 updates ( 2 LTE )
  • North LA   -  2 updates ( 1 LTE )
  • North Wisconsin  -  4 updates ( 4 LTE )
  • Oklahoma  -  14 updates ( 2 LTE )
  • Orange County  -  13 updates ( 10 LTE )
  • Oregon/SW Washington  -  2 updates ( 2 LTE )
  • Orlando  -  14 updates ( 12 LTE )
  • Philadelphia Metro  -  17 updates ( 16 LTE )
  • Phoenix  -  9 updates ( 2 LTE )
  • Providence  -  10 updates ( 9 LTE )
  • Riverside/San Bernardino  -  2 updates ( 3G )
  • Rochester  -  1 update ( 1 LTE )
  • San Antonio  -  1 update ( 3G )
  • San Diego  -  13 updates ( 7 LTE )
  • SF Bay  -  3 updates ( 3 LTE )
  • South Carolina  -  8 updates ( 5 LTE )
  • Southern Connecticut  -  8 updates ( 3 LTE )
  • Southern Jersey  -  7 updates ( 5 LTE )
  • South Texas  -  2 updates ( 2 LTE )
  • Southwest Florida  -  2 updates ( 3G )
  • Tampa  -  6 updates ( 3 LTE )
  • Tucson/Yuma  -  4 updates ( 2 LTE )
  • Upper Central Valley  -  2 updates ( 2 LTE )
  • Upstate NY Central  -  2 updates ( 1 LTE )
  • Upstate NY East  -  9 updates ( 7 LTE )
  • VT/NH/ME  -  3 updates ( 3G )
  • Washington DC  -  4 updates ( 4 LTE )
  • West Kentucky  -  2 updates ( 2 LTE )
  • West Michigan  -  22 updates ( 17 LTE )
  • West Texas  -  1 update ( 1 LTE ) 

Maps are updated.  I have a lot of CDMA 800 updates to post and they will likely be added this weekend if I can scrounge up enough time.  Also, a LTE site went live in the Lower Central Valley market near Coalinga.  What is interesting is this site was also slated to get LTE 800 in October.  So if anyone finds themselves near Coalinga with a Triband device, go check it out and see if you can connect on Band 26.

 
Robert

Links: Comments regarding this threadNV Sites Complete Map

 

 

:




#171765 Sprint TD-LTE 2500/2600mhz Discussion

Posted by S4GRU on 19 July 2013 - 04:10 PM

Specialists: All

Customers: All 

Effective Date: 7/19/13

What you need to know:

 

7/19 is a big day for Sprint‘s Network Vision with new spectrum and new devices launching. 2.5GHz LTE data traffic will overflow to the Clearwire network in: Los Angeles, San Francisco, Denver, Seattle, Miami, New York City, Tampa and Chicago.

 

3 new data connection devices launch supporting 2.5GHz LTE frequency:

MiFi 500 LTE by NOVATEL, NETGEAR Zing Mobile Hotspot and NETGEAR 341U USB Modem.

 

Why you need to know it:

As Sprint completes the merger with Clearwire, we are gaining access to 2 new spectrums to use on the CDMA LTE network.

 

800MHz frequency provides better inbuilding penetration and larger coverage footprint, but reduced capacity.

 

2.5GHz frequency provides smaller coverage footprint, but greater capacity and speeds.

 

This additional spectrum allows LTE devices to intelligently and dynamically select the appropriate frequency between 1900MHz, 800MHz and 2.5GHz to nail down a call. 

 

What you can expect next: New smartphones supporting 2.5GHz LTE will launch in the fall of 2013. LTE 800MHz network upgrades are scheduled to be completed by the end of this year.

 

Robert from Note 2 using Tapatalk 4 Beta




#97114 Current & Coming Soon Sprint Communities - LTE Status

Posted by Dkoellerwx on 25 January 2013 - 01:26 PM

I put together a map of cities where Sprint has already announced LTE, and the communities that Sprint has announced will have LTE soon. I have also marked the cities that have LTE available in the area, but are not yet launched. These are marked as Pre-Launch cities.In total, there are about 570 cities or communities that have LTE or are slated to receive LTE soon.I will update the map as more cities are launched, or Sprint adds more cities to the coming soon list.

 

Current & Coming Soon Sprint Communities - LTE Status

KEY:

Coming Soon: Sprint has announced LTE will be coming in the next several months

Launched: Sprint has formally announced LTE in this area

Pre-Launch: This city has been announced by Sprint, LTE is available, but not formally launched.

LTE Available: This city has not been announced, but LTE is available in some locations.

View Sprint Current and Coming Soon LTE Communities in a full screen map

 

 

Current Sprint Communities - LTE Type




#267720 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 16 January 2014 - 05:49 PM

Site acceptance reports from Wednesday (1/15):

  • Alabama – 2 updates (1 LTE)
  • Cincinnati – 2 updates (LTE)
  • Cleveland – 2 updates (LTE)
  • Columbus – 6 updates (LTE)
  • GA/SC Coast – 1 update (LTE)
  • Gulf Coast – 2 updates (1 LTE)
  • Houston – 1 update (3G)
  • Las Vegas – 4 updates (LTE)
  • Memphis – 1 update (LTE)
  • Miami/West Palm – 2 updates (3G)
  • Milwaukee – 1 update (LTE)
  • Minnesota – 2 updates (LTE)
  • Mississippi – 1 update (3G)
  • Missouri – 1 update (3G)
  • New York City – 1 update (3G)
  • Norfolk – 1 update (3G)
  • North Wisconsin – 4 updates (LTE)
  • Oregon/SW Washington – 3 updates (LTE)
  • Orlando – 1 update (3G)
  • Phoenix – 6 updates (3 LTE)
  • Riverside/San Bernardino – 1 update (LTE)
  • SF Bay – 3 updates (LTE)
  • San Antonio – 1 updates (3G)
  • South Bay – 1 update (LTE)
  • South Carolina – 1 update (LTE)
  • South Texas – 1 update (3G)
  • South West Florida – 2 updates (3G)
  • Tampa – 2 updates (3G)
  • Upstate NY Central – 2 updates (LTE)
  • Washington DC – 1 update (LTE)
  • West Kentucky – 5 updates (2 LTE)

Maps are updated.  Pretty anemic update today.  I'm loving this faster automated update process!

 
Robert

Links: Comments regarding this threadNV Sites Complete Map




#249133 LTE Plus / Enhanced LTE (was "Sprint Spark" - Official Name for the T...

Posted by UndeadNexus on 05 December 2013 - 09:25 PM

Connected to Band 41 on my Nexus 5

 

I'll let the pics do the talking lol

 

This is from San Bernardino, CA  

 

VERVzdc.png

 

 

 

 

GZua0tJ.png

 

 

One Bar of LTE

 

vr6Q3vy.png

 

2-3 Bars of LTE

 

6l1uo4N.png

 

mg6Dp65.png

 

and my personal favorite.......

 

zo5xBaB.png




#173307 Sprint TD-LTE 2500/2600mhz Discussion

Posted by S4GRU on 22 July 2013 - 10:47 PM

Here is some points today of my Denver Band 41 TD-LTE testing.

  • Netgear TriBand LTE Hotspot is awesome.  Love the color touch screen display.  Easy to use.  And in Network Settings, it will tell you which LTE Band you are using.  Around Denver I used Band 41 (2600) in most places, and occasionally Band 25 (1900).
  • Denver TD-LTE 2600 seemed to me to be on every WiMax site I encountered.  It just very well may be a full market deployment.
  • I rarely lost LTE 2600 signal, unless I went into a tunnel, under a long overpass, went into a significant depression or behind a hill.  On the wide open Denver freeways and boulevards, I kept a steady Band 41 LTE signal with smooth handoffs.  Way smoother than WiMax.
  • I bounced around between -130dBm RSRP and -55dBm RSRP all over the Denver Metro area.  Zero to six bars.  This MiFi will hold on to some very weak signals.  I don't know if triband smartphones will be able to do the same.  However -120dBm signals were usable most of the time with 2-6Mbps speeds.  Even at -130 RSRP I was able to get 1-2Mbps download.  I kept the device in LTE Only mode, and it may not do so well in mixed LTE/CDMA mode.
  • I tried to get Band 41 LTE to hand off to Band 25 LTE.  Over in East Aurora near DIA, it looked like my best shot.  However, there was about a 1/2 mile between where Band 41 ended and Band 25 started.  So no luck there.
  • Maximum speed test hit was 40Mbps in all my testing.  Maximum upload hit was almost 25Mbps.  Lowest ping time was 100ms.  But remember that this was from a hotspot, so some ping is lost there.  When I could test on Band 25, my hotspot was adding between 75-150ms to pings over what my Note 2 was doing from the same site/sector.
  • It seems in the current Denver deployment, LTE 2600 download speeds seemed limited on Clearwire's existing backhaul that is being shared with WiMax.  For instance, I had a WiMax Galaxy S2 that I was using side by side with my TD-LTE hotspot.  When I hit 40Mbps DL on TD-LTE, I was hitting 14-16Mbps DL on WiMax (although I cannot guarantee I was on the same site).  However, when I would hit 8Mbps DL on TD-LTE with a full signal, I would also only hit about 6-8Mbps DL on WiMax.  So with this, I concluded that Clearwire is sharing their LTE and WiMax on the same backhaul.  So if the LTE/WiMax 2600 site has more backhaul speed available than the WiMax airlink could support, then the LTE would be much faster than WiMax, up to whatever speed the backhaul was currently running.  If the backhaul was burdened to a speed lower than the WiMax airlink, then the LTE and WiMax 2600 were the same speed roughly.
  • Upload speeds.  Upload speeds were good to great.  I averaged 8-10Mbps upload speeds.  Sometimes hitting into the 20's.  At sites where speeds were below 7-8Mbps, the upload was averaging higher.  WiMax upload was limited to 1.5Mbps, but Clearwire TDD LTE is much higher.  This leads me to conclude that these are indeed 20MHz channels.  I don't think we would see 20Mbps+ upload speeds on Time Division with only 10MHz channels.
  • My conclusion after 8 hours of testing is that I believe these to be 20MHz TDD channels.  With the very high upload speeds, I'm left with no other conclusions.  With a full signal, I encountered between 6Mbps - 40Mbps download speeds, and 6Mbps - 25Mbps upload speeds.  Even though a 10MHz TDD channel could hit 40Mbps DL speeds in ideal situations, I don't think it could then also deliver 20Mbps+ speeds too on it.  A 10MHz TDD channel would likely have around a 10Mbps upload speed, or even possibly less.  I think that the 40/20 could be even higher with better backhaul delivered to these sites.
  • Indoor usability on Band 41 stinks.  No suprise, though.  I would lose between 15-25dBm going indoors.  If I had worse than -100dBm outside, I likely wasn't going to get inside reception at all.  Since LTE 2600/Band 41 is supposed to be overlaid always with 1900 and 800, this will not be a problem at build out.  And I had better reception and speeds than WiMax.  But you will not be fond of LTE 2600 indoor usage.
  • Another point about the hotspot, but not Band 41 (TDD-LTE) related, is that it is a RF beast.  The Netgear MiFI tends to best my Note 2 on Band 25 LTE signals by 6-10dBm.  That's a lot.  In Castle Rock, Colorado with a 10dBm difference, my Note 2 would do 11Mbps on its own, but connected to the hotspot it would do 20Mbps.  Huge difference in speed with 10dBm.  Also, my CDMA RSSI is roughly 4-8dBm better too.

Robert




#147213 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 31 May 2013 - 10:06 AM

As requested by many members, I am creating a Site Acceptance Report Update thread that will be closed for comment.  That way members can subscribe/follow this thread and not be inundated with notifications from members, and only get notifications when I post an update.

 

I also decided to open this thread to non-sponsors, so they can see generically what is happening in their market every day.  Hopefully, it will encourage more sponsorship for these standard members to access the additional details about these updates.  The comments section about this thread will remain in the Sponsor section, as well as coordinating maps.

 

Here are some important links for Sponsors:

 

Sponsor Member Comments regarding the NV Sites Complete Map & Acceptance Reports:  http://s4gru.com/ind...view=getnewpost

 

Sponsor NV Sites Complete Maps:  http://s4gru.com/ind...sites-complete/

 

For Non-Sponsor Members:

 

For more information about how to become a S4GRU Sponsor, visit this link:  http://s4gru.com/ind...come-a-sponsor/

 

Robert




#214690 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 03 October 2013 - 10:22 AM

Site acceptance reports from Saturday (9/28), Sunday (9/29), Monday (9/30), Tuesday (10/1) and Wednesday (10/2):

 

  • Alabama – 9 updates (LTE)
  • Arkansas – 1 update (LTE)
  • Atlanta/Athens – 8 updates (4 LTE)
  • Austin – 7 updates (3 LTE)
  • Baltimore – 5 updates (4 LTE)
  • Boston – 8 updates (4 LTE)
  • Central Illinois – 5 updates (3G)
  • Central Iowa – 2 updates (3G)
  • Central Jersey – 3 updates (3G)
  • Central Pennsylvania  - 1 update (LTE)
  • Charlotte – 21 updates (1 LTE)
  • Chicago – 7 updates (LTE)
  • Cincinnati – 32 updates (2 LTE)
  • Cleveland – 7 updates (3G)
  • Colorado – 3 updates (1 LTE)
  • Dakotas – 9 updates (3G)
  • Delaware – 2 updates (3G)
  • DFW – 15 updates (7 LTE)
  • East Iowa – 5 updates (4 LTE)
  • East Kentucky – 9 updates (LTE)
  • East Michigan – 7 updates (LTE)
  • East Texas – 6 updates (LTE)
  • Ft. Wayne/South Bend – 2 updates (LTE)
  • GA/SC Coast – 6 updates (3 LTE)
  • Gulf Coast – 9 updates (8 LTE)
  • Houston – 6 updates (4 LTE)
  • Idaho – 11 updates (2 LTE)
  • Inland Northwest – 1 update (LTE)
  • Jacksonville – 8 updates (6 LTE)
  • Kansas – 7 updates (4 LTE)
  • LA Metro – 14 updates (6 LTE)
  • Las Vegas – 11 updates (6 LTE)
  • Long Island – 6 updates (3 LTE)
  • Louisiana – 4 updates (LTE)
  • Lower Central Valley – 12 updates (3G)
  • Memphis – 10 updates (5 LTE)
  • Miami/West Palm – 15 updates (14 LTE)
  • Milwaukee – 4 updates (2 LTE)
  • Minnesota – 21 updates (8 LTE)
  • Mississippi – 1 update (LTE)
  • Missouri – 18 updates (LTE)
  • Myrtle Beach – 5 updates (1 LTE)
  • Nashville – 11 updates (8 LTE)
  • New Orleans – 5 updates (LTE)
  • New York City – 23 updates (15 LTE)
  • Northern Connecticut – 4 updates (3G)
  • Northern Jersey – 8 updates (4 LTE)
  • North LA – 3 updates (3G)
  • North Wisconsin – 17 updates (7 LTE)
  • Oklahoma – 7 updates (2 LTE)
  • Orange County – 10 updates (8 LTE)
  • Oregon/SW Washington – 13 updates (3 LTE)
  • Orlando – 14 updated (8 LTE)
  • Philadelphia Metro – 20 updates (12 LTE)
  • Phoenix – 9 updates (3G)
  • Pittsburgh – 16 updates (3G)
  • Providence – 7 updates (3G)
  • Richmond – 5 updates (3G)
  • Riverside/San Bernardino – 11 updates (5 LTE)
  • San Antonio – 6 updates (3 LTE)
  • San Diego – 10 updates (2 LTE)
  • SF Bay – 3 updates (1 LTE)
  • South Carolina – 15 updates (11 LTE)
  • Southern Connecticut – 6 updates (3G)
  • Southern Jersey – 5 updates (3 LTE)
  • South Texas – 3 updates (2 LTE)
  • Southwest Florida – 5 updates (3G)
  • Tampa – 3 updates (LTE)
  • The Panhandle – 1 update (LTE)
  • Tucson/Yuma – 3 updates (3G)
  • Upper Central Valley – 3 updates (LTE)
  • Upstate NY Central – 7 updates (4 LTE)
  • Upstate NY East – 8 updates (3 LTE)
  • Utah – 15 updates (3G)
  • VT/NH/ME – 9 updates (4 LTE)
  • Washington DC – 7 updates (2 LTE)
  • West Iowa/Nebraska – 2 updates (LTE)
  • West Kentucky – 8 updates (7 LTE)
  • West Michigan – 8 updates (LTE)
  • West Texas – 3 updates (2 LTE)
  • West Virginia – 12 updates (3G)
  • West Washington – 2 updates (1 LTE)

Maps are updated.

 
Robert

Links: Comments regarding this threadNV Sites Complete Map




#200735 Network Vision Site Acceptance Report Updates

Posted by S4GRU on 08 September 2013 - 07:12 AM

Site acceptance reports from Tuesday (9/3), Wednesday (9/4), Thursday (9/5) and Friday (9/6):

  • Alabama – 4 updates (1 LTE)
  • Albuquerque – 4 updates (3G)
  • Arkansas – 2 updates (LTE)
  • Atlanta/Athens – 8 updates (4 LTE)
  • Austin – 8 updates (3 LTE)
  • Boston – 3 updates (1 LTE)
  • Central Illinois – 1 update (LTE)
  • Central Jersey – 4 updates (1 LTE, 1 new 3G site)
  • Central Pennsylvania – 1 update (3G)
  • Charlotte – 1 update (3G)
  • Chicago – 9 updates (LTE)
  • Cincinnati – 7 updates (3 LTE)
  • Columbus – 1 update (LTE)
  • Dakotas – 4 updates (3G)
  • Delaware – 3 updates (2 LTE)
  • DFW – 10 updates (7 LTE)
  • East Iowa – 1 update (LTE)
  • East Kentucky – 2 updates (3G)
  • East Texas – 4 updates (LTE)
  • Ft. Wayne/South Bend – 5 updates (LTE)
  • GA/SC Coast – 4 updates (3G)
  • Georgia – 3 updates (LTE)
  • Gulf Coast – 6 updates (3 LTE)
  • Houston – 11 updates (7 LTE)
  • Inland Northwest – 3 updates (3G)
  • Jacksonville – 11 updates (1 LTE)
  • Kansas – 14 updates (4 LTE)
  • LA Metro – 10 updates (3 LTE)
  • Las Vegas – 15 updates (10 LTE)
  • Long Island – 3 updates (3G)
  • Louisiana – 4 updates (3 LTE)
  • Memphis – 7 updates (LTE)
  • Miami/West Palm – 8 updates (6 LTE)
  • Milwaukee – 5 updates (LTE)
  • Minnesota – 4 updates (2 LTE)
  • Mississippi – 1 update (LTE)
  • Missouri – 13 updates (12 LTE)
  • Myrtle Beach – 1 update (3G)
  • Nashville – 25 updates (14 LTE)
  • New Orleans – 6 updates (LTE)
  • New York City – 15 updates (10 LTE)
  • Northern Connecticut – 5 updates (1 LTE)
  • Northern Jersey – 4 updates (1 LTE)
  • North LA – 1 update (3G)
  • North Wisconsin – 1 update (LTE)
  • Oklahoma – 12 updates (2 LTE)
  • Orange County – 7 updates (1 LTE)
  • Oregon/SW Washington – 1 update (LTE)
  • Orlando – 6 updates (5 LTE)
  • Philadelphia Metro – 16 updates (10 LTE)
  • Phoenix – 14 updates (5 LTE)
  • Providence – 1 update (3G)
  • Raleigh/Durham – 1 update (3G)
  • Riverside/San Bernardino – 3 updates (1 LTE)
  • Rochester – 8 updates (3G)
  • San Antonio – 12 updates (3G)
  • San Diego – 6 updates (1 LTE)
  • SF Bay – 3 updates (2 LTE)
  • South Carolina – 16 updates (10 LTE)
  • Southern Connecticut – 3 updates (LTE)
  • Southern Jersey – 6 updates (3 LTE)
  • South Texas – 4 updates (2 LTE)
  • South West Florida – 6 updates (3 LTE)
  • Tampa – 10 updates (5 LTE)
  • The Panhandle – 3 updates (2 LTE)
  • Toledo – 18 updates (3G)
  • Tucson/Yuma – 2 updates (3G)
  • Upper Central Valley – 1 update (3G)
  • Upstate NY Central – 1 update (3G)
  • VT/NH/ME – 2 updates (1 LTE)
  • West Kentucky – 17 updates (9 LTE)
  • West Michigan – 18 updates (3G)
  • West Texas – 17 updates (4 LTE)
  • West Virginia – 2 updates (LTE)
  • West Washington – 2 updates (LTE)

Maps are updated.

 

Robert

Links: Comments regarding this threadNV Sites Complete Map




#173062 Sprint TD-LTE 2500/2600mhz Discussion

Posted by S4GRU on 22 July 2013 - 01:37 PM

Robert presents TD-LTE 2600 from Denver, Colorado.  I'm at the Lone Tree Mall.  Activated the new Netgear MiFi and had LTE 2600 instantly.  See below: uploadfromtaptalk1374525160279.jpg uploadfromtaptalk1374525191400.jpg uploadfromtaptalk1374525212256.jpg uploadfromtaptalk1374525235447.jpg uploadfromtaptalk1374525288396.jpg So even with a weak indoor -109dBm RSRP (one bar), I had very usable results.  I'm inside a shopping mall where I even only have one bar Verizon LTE. Best speed test over 11Mbps.  Weakest in the Mid 7's.  Not shabby with such a weak signal.  Heading over toward Stapleton in the next hour.  We will see how widespread this TD-LTE is around Denver. But I was shocked to have it in the very first place I turned it on.  Could it be market wide already?  Hmmm... Robert from Note 2 using Tapatalk 4 Beta


#137124 COUNTDOWN!!! Nextel iDEN Shutdown

Posted by S4GRU on 07 May 2013 - 01:21 PM

S4GRU readers, want to see your name up in lights? Here is your chance...The Nextel iDEN countdown clock is up on the front page of The Forums.http://s4gru.com/index.php?/index

 

As a fundraiser for non profit S4GRU, you can claim "naming rights" to the iDEN countdown clock for a day for a $10 donation. I have already made my claim on the first three days through the end of this workweek. Now, who will step up to the plate and meet my challenge to keep the sponsorship going?

 

Celebrate the shutdown of iDEN. Show your support for CDMA1X 800 and LTE 800. And, of course, see your name get recognized by thousands of other readers around the country.Just make a $5 PayPal donation, put "iDEN countdown" in the message, and the clock is yours for a day (or more).

 

AJ.........................................................................................................................................................................

 

Countdown Clock Sponsors:

  • 5/8-5/10 WiWavelength

  • 5/11-5/13 4ginnc

  • 5/14-5/16 leerage

  • 5/17-5/20 PDXmike

  • 5/21-5/24 RCM

  • 5/25-5/28 shawn_kc

  • 5/29-6/2 kvnjcby

  • 6/3-6/4 cletus

  • 6/5-6/5 thewezgrays

  • 6/6-6/7 dkoellerwx

  • 6/8-6/10 irwinshere

  • 6/11-6/12 squigey

  • 6/13-6/14 gr8nuguy

  • 6/15-6/24 mooeydj

  • 6/25-6/26 gr8nuguy

  • 6/27-6/28 Groovy

  • 6/29 - To be auctioned off to the highest bidder on E-Bay