-
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
-
It seems to happen most often in Ericsson markets. But it is not something I track. Especially since automation. It has to be something that stands out to me (like a market I watch closely, like ABQ) for me to even notice. Because if I get a 3G acceptance, and the site already has been 3G accepted, I don't actually log anything. And now that the whole thing is automated, if the computer script sees something is 3G accepted, and it was before, it just completely ignores it. And I'm none the wiser. It is also possible, that a second 3G acceptance is related to voice and data integration happening separately. Most of the time, they are integrated together. But sometimes, they are not. I have seen many Sprint schedules where 3G Voice and 3G Data integration occurred on different dates. Especially in Ericsson markets. Robert
-
Just good, old fashioned, they can't seem to get it done. The 'brown dot' sites are still not converted to Network Vision and probably have a variety of permitting, owner or contractor issues. The red/light blue marker sites (3G only) are suffering from backhaul install issues. It's just a mess. Robert
-
In a place like Denver, the market should perform pretty darn well for some time. Especially on a Triband device. Since Denver already has some of the lowest Sprint subscriber numbers, and so many more have left, and that it will be pretty much built with all three bands from the beginning...well, it should be pretty darn nice. Robert via Samsung Note 8.0 using Tapatalk Pro
-
It will not improve anytime a soon for single band LTE devices. You will need a Triband device with Band 26 and Band 41 to get faster speeds. Band 25 airlink is overloading. It is not backhaul. But Triband devices have access to tons more capacity. B41 is already working on many San Antonio area sites. And B26 deployment will start soon. It appears you have an N5. So you just need to wait for the update. Although, you may be able to force it to run on the existing B41 sites if you flash the .15 radio. You can read more about that in our N5 thread. Robert via Samsung Note 8.0 using Tapatalk Pro
-
Sprint does not have good coverage maps. Their LTE maps have been horribly overstating coverage since day one. But to be fair, Tmo coverage maps only have coverage in the two darkest levels, and Verizon almost never has LTE in their Extended areas either. Sprint's coverage maps do get a little more accurate fully zoomed in, but I won't pardon Sprint's bad coverage maps. They're awful. Robert via Samsung Note 8.0 using Tapatalk Pro
-
There were two reacceptances yesterday. One in Albuquerque and one in Alamogordo. So, someone is working again. A reacceptance is a site that was accepted complete, but later was found to be deficient during integration. Hopefully they will continue with more. Robert via Samsung Note 8.0 using Tapatalk Pro
-
I wondered the same thing when I saw it appear. It's possible the site is 3G accepted, but is still broadcasting on legacy. Waiting for the cluster to go live before the NV side of this site goes live. It's possible that the whole cluster is live, but for some reason the other sites did not show up on the same acceptance report. It's also possible that it's accurate and everyone using 3G on that site is getting dropped when they hand off to another site. Or it's possible that this is a reporting error on Sprint's side. It will be interesting to see if this cluster does get fully accepted in the next day or two. Robert
-
They are upgrading the entire market all at once. LTE goes live at each complete converted site when the backhaul is complete and ready by the backhaul vendor. It has nothing to do with planning by demographics. Robert
-
I remember a chat in the Lounge a few years ago when I told members that Winston-Salem was going to be a Round 4 market and that it would be one of the last Top 100 markets to launch. One of our core members even left Sprint because of it. It turned out to be one of the best deployment markets ever. Once ALU finally showed up and started the market. Although Round 4 markets have had to wait a long time. Most of them have gone pretty well and fast. Some even getting launched or nearing completion before their Round 3 or some Round 2 markets even. Heck, there is even a Round 1 market not even launched, yet. Robert
-
I'm gonna close this thread. I have emailed with the member a few times. He either is messing with us or he's like 12 years old. Robert
- 8 replies
-
- 10
-
Probably watching subscriber numbers. It goes to free when people are porting out at higher numbers. I absolutely believe they used tablets to try to stabilize numbers last quarter. Robert
-
No. There are no plans to install anything but Band 41 LTE on Clearwire sites at this time. They may eventually do full Network Vision upgrades and install CDMA and other LTE bands at Clearwire sites in the future. Especially if additional CDMA capacity is needed. But given that voice demands are going down, and Band 41 provides mondo capacity, I wouldn't hold your breath. But if you get CDMA 800 and Band 41 near a Clearwire site, you don't really need anything else. You have a voice and high speed data connection. And Band 26 LTE will help fill in the gaps. Robert
-
I thought of him and aerxx both when I saw that last night. Robert
-
Richmond is more than just CSFB. There is a new vendor. Richmond has legacy Motorola gear and being replaced with Alcatel Lucent. So Sprint and Lucent are now in a pickle that they have to bring 3G up in clusters to prevent massive voice handoff/call drop problems. And they will no longer bring up LTE by itself, because of the CSFB problem. So Richmond is being deployed more like a Samsung market now. They have to work marketwide all at once now and bring up 3G in clusters. Then when 3G/eCSFB is live in each cluster, they can double back and bring online the LTE on the sites in those clusters who already have their backhaul in place. Robert
-
Ahhh. That is not normal. Did this appear in an update recently on the EVO LTE? Robert via Samsung Note 8.0 using Tapatalk Pro
-
Roaming should be disabled by default. That way the user has to decide to enable it and accept the warning that they may be subject to fees, etc. Otherwise the user may not realize they are roaming or that there are limitations to roaming. It would not be good form for Sprint to enable it for their customers. Robert via Samsung Note 8.0 using Tapatalk Pro
-
It is most likely the area you moved into doesn't have CSFB available. So it allows you to keep your LTE connection when you move out of CSFB. But as soon as you lose LTE, it will no longer let you reconnect to LTE until you reestablish a CSFB connection. If you are in an area that doesn't have 3G accepted on the maps and only 4G, this could be the problem. Ericsson has eCSFB functioning on all their 3G accepted sites. On the 4G only sites, they are using a legacy CSFB network that isn't very good and often goes offline. But even if you are in an area with 3G accepted and eCSFB is active, there still could be problems with CSFB working properly. Robert via Samsung Note 8.0 using Tapatalk Pro
-
If you've never received 50-60Mbps from those sites, they do not have upgraded backhaul, yet. An unburdened legacy WiMax backhaul can run even 20-40Mbps in ideal situations. If you're finding highly variable B41 speeds, you're on legacy backhaul. Also, in the Dallas area, Clearwire used a lot of long chain microwave. This can cause a lot of variability in performance. Especially at times when there are a lot of WiMax home ISP users online stressing the backhaul. Like evenings. If you were far away from the primary microwave/fiber interface and had a lot of home users along the MW chain (even if not a single one on your site) and the speeds would bog down. Sprint is upgrading the Clearwire network backhaul to better support B41 speeds. In the case of long string microwave, it often involves bringing fiber to all the connected sites. As there are too many sites in the chain for an ultra high speed solution to be consistent at all the sites. You may even find the legacy backhaul will get even worse at peak times before things get consistently good at each site with upgraded backhaul. Robert via Samsung Note 8.0 using Tapatalk Pro
-
Think of it this way. Samsung and Sprint used to allow sites where equipment was already installed that had backhaul complete to at least bring the LTE online and be used. Why let the LTE just sit there months and months waiting for the 3G cluster to be turned on? But this only helped Uniband devices. Late summer/early Fall last year, Samsung switched gears and focused hard on whole 3G clusters. Bringing them up one at a time. This allowed eCSFB to go live over the whole cluster at once and make sure that Triband devices were good to go. And then LTE was brought up on all the sites within each cluster where backhaul was ready after the fact. So now backhaul is sitting there unutilized for months at many sites waiting for the 3G cluster to go online before any LTE can be integrated in that cluster. So some may think that's silly. In some ways it is. So it goes both ways. Which is better, allow some sites to go early that are ready and let some customers use them and get relief or make everyone wait until months later and the cluster is ready? You'll probably get a mixed bag of answers. But neither one is really the non silly answer. But given the dire condition of the Sprint network, I would prefer they open anything and everything possible as early as possible. And if that means firing up LTE before 3G clusters and CSFB are ready for Triband customers, that's what I'd do. Robert via Samsung Note 8.0 using Tapatalk Pro
-
Comments related to the NV Running List Thread
S4GRU replied to MacinJosh's topic in Network, Network Vision/LTE Deployment
A broken clock is right twice a day too. The texts went out nationwide, so it will appear correct everywhere it's true. But it will be devastatingly wrong in all the places it's not. Robert via Samsung Note 8.0 using Tapatalk Pro