-
Posts
33,136 -
Joined
-
Last visited
-
Days Won
1,212
Content Type
Profiles
Blogs
Articles
Media Demo
Gallery
Downloads
Events
Forums
Everything posted by S4GRU
-
Network Vision/LTE - Shentel Market (Shenandoah Valley/Hagerstown/Harrisburg)
S4GRU replied to Boosted20V's topic in Markets
I now have had three Shentel sources tell me that Sprint and Shentel have come to an agreement on Band 41 and they will begin deployment before the end of the 2nd Quarter. And possibly sooner if they can get equipment faster than currently scheduled. It is believed to just be an urban overlay, and not going to be over the whole Shentel network. At least for now. In my mind, I see it Harrisburg, Hagerstown and Harrisonburg for sure. And likely in Altoona, York, Martinsburg and Winchester. The types of places that could go either way are Gettysburg, Chambersburg, Carlisle, Lebanon, Charles Town, Strasburg/Front Royal, etc. Robert -
Sprint announces 40 more cites for LTE
S4GRU replied to ab30494's topic in Network, Network Vision/LTE Deployment
We have our share of oil. And also, a lot of the oil industry and oil fields in SE Montana, NE Wyoming, SW North Dakota and Western South Dakota base themselves in Rapid City. Oil is becoming an increasing factor in our economy. Especially as North Dakota runs out of resources and housing for the boom. Robert -
Network Vision/LTE - Shentel Market (Shenandoah Valley/Hagerstown/Harrisburg)
S4GRU replied to Boosted20V's topic in Markets
No. People are bailing on Sprint and Swiftel in Eastern South Dakota. If Swiftel was at least maintaining its 3G service, it wouldn't be so bad. But its awful. I almost get a vibe that Swiftel may sell off its wireless to a Sprint competitor or make a new alliance. They seem to not care about their network outside of their hometown of Brookings. Robert via Nexus 5 using Tapatalk -
Network Vision/LTE - Shentel Market (Shenandoah Valley/Hagerstown/Harrisburg)
S4GRU replied to Boosted20V's topic in Markets
In a place like Harrisburg, a fully deployed Band 26 network on Sprint should be killer. And now that Shentel has confirmed a Band 41 overlay, it should be glorious! Forget Sprint taking over Tmo. Shentel should take over Sprint. (Yes, I know that Shentel is only so successful because they are small, but they are even well run for a small company. Swiftel is even smaller and is tragically run.) Robert via Nexus 5 using Tapatalk -
Also, I heard the same thing about non WiMax devices being able to use WiMax because WiFi was so close in frequency. I also heard that WiMax devices just need to be recertified to use LTE. And I've also heard that Band 25 devices will be able to be recertified using Band 41 because of WiFi antennas. Until it's proven, I will be doubtful. Robert via Nexus 5 using Tapatalk
-
I suppose it could be remotely plausible. But two issues... One, it concerns me that only evidence of this after this device being out for 15 months is one comment from one Sprint Customer Service rep (which are historically bad. Two, this has not passed the FCC to authorize it for use in Band 26. So I highly doubt Jose's father is using Band 26 LTE on the iPhone 5 now. If this is possible, we will see it in short order through FCC recertification. However, if this is always the plan, why haven't they done it in the last 15 months? What are they waiting for. There already is some Band 26 live that 5S/5C customers are using. Robert via Nexus 5 using Tapatalk
-
Sprint has been saying internally that their plan is 41 > 25 > 26. Although they may do some mixing it up while still deploying. Robert via Samsung Note 8.0 using Tapatalk Pro
-
The iPhone will not search out CDMA 800 unless it has absolutely zero signal on 1900. There is no way around this except to install a custom PRL. Which involves jailbreaking. But also, there is no guarantee that the 800 is even live. 800 signals still come and go in the early stage. Robert via Samsung Note 8.0 using Tapatalk Pro
-
You can't really just crank up the transmission power at a site. It's a delicate balance. Radio communications are two way. If they crank up the power, the signal may reach farther, but your device won't reach a transmission back. It no workee. Devices are really the limiting factor in signal strength. Robert
-
Please post a productive comment in the Galaxy Note 3 section outlining your issues. It's off topic to complain about your Note 3 in the market thread. Thanks. Robert
- 1,028 replies
-
- Grand Rapids
- Lansing
- (and 16 more)
-
PCS/AWS-2 H block FCC Auction 96 results thread
S4GRU replied to WiWavelength's topic in General Topics
Peyton Manning accidentally purchases H Block in Omaha. He thought it was a Papa John's Franchise. Robert -
All right S4GRU Nexus 5 owners in Band 41 areas. Give these exact settings a try and report back! Robert
-
What will the Tmo Koolaid drinkers say if this deal gets formally announced and Legere starts running around talking about how good this deal is going to be. Will they reject him for that line of thinking, or will the embrace their Messiah and go along with the buyout message being good for their souls merely because the Pied-Magenta-Piper says so? It will be interesting. Robert
-
Glad to hear. I see the Hulu problem posted occasionally. This must be a G2 bug with the app. Robert
-
Site acceptance reports from Tuesday (1/28): Alabama - 2 updates (3G) Atlanta/Athens - 1 update (3G) Baltimore - 3 updates (3 LTE) Boston - 1 update (3G) Buffalo - 1 update (3G) Central Jersey - 1 update (1 LTE) Columbus - 4 updates (4 LTE) East Michigan - 21 updates (21 LTE) Ft. Wayne/South Bend - 1 update (1 LTE) GA/SC Coast - 1 update (3G) Georgia - 1 update (3G) Jacksonville - 2 updates (1 LTE) LA Metro - 3 updates (2 LTE) Long Island - 2 updates (1 LTE) Memphis - 3 updates (3G) Milwaukee - 1 update (1 LTE) Mississippi - 2 updates (3G) Missouri - 2 updates (1 LTE) Myrtle Beach - 1 update (1 LTE) New Orleans - 4 updates (3G) New York City - 1 update (1 LTE) Northern Connecticut - 4 updates (4 LTE) Northern Jersey - 6 updates (6 LTE) Oklahoma - 1 update (3G) Philadelphia Metro - 2 updates (1 LTE) Providence - 1 update (1 LTE) Raleigh/Durham - 3 updates (3 LTE) Riverside/San Bernardino - 8 updates (6 LTE) SF Bay - 2 updates (2 LTE) San Antonio - 1 update (3G) San Diego - 2 updates (1 LTE) South Carolina - 9 updates (8 LTE) South Texas - 1 update (3G) South West Florida - 3 updates (3G) Southern Connecticut - 3 updates (3 LTE) Southern Jersey - 2 updates (2 LTE) Tampa - 3 updates (3G) Upper Central Valley - 12 updates (1 LTE) Upstate NY Central - 1 update (1 LTE) Upstate NY East - 3 updates (3 LTE) Utah - 8 updates (2 LTE) West Iowa/Nebraska - 5 updates (5 LTE) West Washington - 2 updates (2 LTE) Winston/Salem - 10 updates (10 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map
- 206 replies
-
- 20
-
It's my understanding CL offered it to Sprint because they were going to be so late with fiber connections. CL said they could get something temporary via copper that would run ~25Mbps (if memory serves) as a stop gap until fiber could be brought. Sprint was interested and they connected two sites, one in Cruces and one in ABQ. It would not have been stellar, but at 25Mbps, it could have provided about 8Mbps throughput speeds per sector. Unfortunately, the CL copper solution could not pull 25Mbps. Not even close. After a few days of fiddling with the Cruces site, they gave up and instead decided to wait until fiber backhaul was delivered. This was relayed to me by an Ericsson integration tech I ran into at the Los Alamos North Mesa water tower site about 6 weeks after the ABQ site was LTE accepted and then "unaccepted." I never found out more, or could really even verify it. But it seemed plausible. Especially since the Cruces site did go live for awhile and had really low speeds, like 1-4Mbps. Robert
-
It is highly variable. We will continue to see sites go live every week. I think Sprint will likely be substantially complete with all backhaul in 5-6 months. With only a site here or there continuing without because of specific problems. I hope Sprint just uses microwave to any remaining problematic sites. Robert
-
Site acceptance reports from Monday (1/27): Alabama - 1 update (3G) Arkansas - 4 updates (3G) Baltimore - 1 update (1 LTE) Boston - 2 updates (1 LTE) Buffalo - 13 updates (3G) Central Jersey - 1 update (1 LTE) Cincinnati - 3 updates (3 LTE) Colorado - 1 update (1 LTE) East Michigan - 1 update (3G) Gulf Coast - 1 update (3G) LA Metro - 2 updates (2 LTE) Las Vegas - 2 updates (2 LTE) Louisiana - 1 update (1 LTE) Lower Central Valley - 1 update (1 LTE) Memphis - 1 update (3G) Milwaukee - 6 updates (5 LTE, 1 new 3G/LTE site) Mississippi - 3 updates (3G) Missouri - 2 updates (3G) Myrtle Beach - 1 update (1 LTE) Norfolk - 1 update (3G) North LA - 1 update (1 LTE) Northern Connecticut - 3 updates (2 LTE) Northern Jersey - 2 updates (2 LTE) Oregon/SW Washington - 1 update (1 LTE) Orlando - 1 update (3G) Phoenix - 1 update (3G) Providence - 2 updates (2 LTE) Riverside/San Bernardino - 5 updates (5 LTE) South Bay - 2 updates (2 LTE) South Carolina - 1 update (3G) South Texas - 1 update (3G) South West Florida - 4 updates (1 LTE) Southern Connecticut - 1 update (1 LTE) Southern Jersey - 2 updates (1 LTE) Tampa - 2 updates (3G) Toledo - 1 update (3G) Tucson/Yuma - 1 update (3G) Upper Central Valley - 3 updates (3 LTE) West Iowa/Nebraska - 1 update (3G) West Kentucky - 1 update (3G) Winston/Salem - 1 update (3G) Maps were updated yesterday. I'm just late in posting the summary list. Robert Links: Comments regarding this thread, NV Sites Complete Map
- 206 replies
-
- 14
-
PCS/AWS-2 H block FCC Auction 96 results thread
S4GRU replied to WiWavelength's topic in General Topics
I'm interested in watching which markets are seeing action still and the amount. But if I am the only one interested, I wouldn't want you to waste the time to keep up the thread. Robert -
PCS/AWS-2 H block FCC Auction 96 results thread
S4GRU replied to WiWavelength's topic in General Topics
http://s4gru.com/index.php?/topic/5386-pcsaws-2-h-block-fcc-auction-96-results-thread/?p=270990 -
Most of the Central Illinois market has all their equipment upgraded and ready for LTE. So any site that does not have LTE live, it is most often backhaul related. Rural areas are much more likely to get backhaul sooner. I know it seems strange, but rural sites are often along major highways with fiber running right along the site. And when they are not, access is often easier because trenching in farm areas as there is typically just dirt in between fiber and the site. Not roads, concrete, buildings, etc. Robert via Samsung Note 8.0 using Tapatalk Pro
-
It cannot be remotely activated. It involves a site visit. But the site visit is pretty simple. Just installing a Band 26 carrier card and integrating with the network. So it will go much faster. The biggest hindrance to Band 26 deployment is getting cards from OEM's (which has been slow going) and getting SMR rebanders out of the way. Robert via Samsung Note 8.0 using Tapatalk Pro
-
Band 25 could feel a little relief with the addition of Band 26. But the adoption of Band 26 devices is probably similar to the add of Band 25 only devices still occurring. So the difference will be negligible for Band 25 users when 26 go live. Band 25 will likely only see any noticeable performance improvements when another site nearby goes live or the addition of a second Band 25 LTE carrier. It's all about the Triband, baby. Or at least dual band, in the minimum. Robert via Samsung Note 8.0 using Tapatalk Pro