S4GRU

spectrum deficiency

The whole market is actively receiving Network Vision/LTE upgrades, including Queens. Sites are being completed every week. There may be some live LTE sites in the boroughs in the next 30-45 days or so. We track completed sites in the NV Sites Complete thread in the Sponsor section of S4GRU.com. Robert

trash compactor Robert via Samsung Galaxy S-III 32GB using Forum Runner

Backhaul is going in a little earlier in later markets. But Sprint doesn't have the cash flow to do all the backhaul in advance for all four rounds. But some backhaul is starting already in Round Three markets. Additionally, some of the 2nd and 3rd Round markets placement was determined because of backhaul availability. For instance, some 2nd round markets would have been 3rd Rounders, but they can get backhaul deployed faster. And some 3rd Rounders could have been in the second round, but they had backhaul infrastructure issues that wouldn't have allowed so fast of a start. If people understood this, there may be less complaining about market order. Sprint wants NV to be done as soon as possible. But there has to be an order and there has to be a budget. So they are trying to get it done as fast as possible within the parameters of reality of their situation. Robert via Samsung Galaxy S-III 32GB using Forum Runner

The site next to my home has two T1‘s. One for voice, one for data. All three sectors share the same T1's. Most rural and low usage sites have 2-3 T1's. Robert via CM9 Kindle Fire using Forum Runner

toll booth Robert via CM9 Kindle Fire using Forum Runner

root directory Robert via CM9 Kindle Fire using Forum Runner

Love Canal Robert via CM9 Kindle Fire using Forum Runner

I believe the LTE scan is an issue based on things I've seen and heard. But the threshold issue is real, and the LTE scan is an unrelated issue. Thresholds were modified in the last round of OTA's. So threshold issues have been vastly improved. However, LTE scan could be affecting a lot of users now, and would explain a lot of the issues that EVO LTE customers are having. Cycling through CDMA only and CDMA/LTE mode forces the device to scan LTE, whereas it might take up to 30 minutes if you waited for it to scan on its own. On the GS3, it's called "nextLTEscan timer" and it is also set to 30. And there is a BSR timer set to 2. I went to modify the LTE timer down to 1, and it said "insert correct value" when I tried to save it. I changed it to 29, and it repeated the same error. It doesn't look like I am able to change the scan timer on my GS3. I will check my other LTE devices when I get a chance. Robert via CM9 Kindle Fire using Forum Runner

Kool cigarettes Robert via CM9 Kindle Fire using Forum Runner

Power Wagon Robert via Samsung Galaxy S-III 32GB using Forum Runner

I have been able to connect to Verizon eHRPD on 850 Cellular here locally on my GS3. Can't keep it long. It will dump me back to EVDO-A in approximately 20 seconds. Robert via Samsung Galaxy S-III 32GB using Forum Runner

Fun Dip Robert via Samsung Galaxy S-III 32GB using Forum Runner

As we say in New Mexico, "Holy Frijoles!!!" Or more like Frijoles del Negro. Robert via Samsung Galaxy S-III 32GB using Forum Runner

falling water Robert via Samsung Galaxy S-III 32GB using Forum Runner

Halloween Mask Robert via CM9 Kindle Fire using Forum Runner

sewer rat Robert via Samsung Galaxy S-III 32GB using Forum Runner

road construction Robert via Samsung Galaxy S-III 32GB using Forum Runner

primal instinct Robert via Samsung Galaxy S-III 32GB using Forum Runner

fear monger Robert via Samsung Galaxy S-III 32GB using Forum Runner

shit faced Robert via Samsung Galaxy S-III 32GB using Forum Runner