S4GRU

And in a place like NYC, it is very hard to get zero CDMA 1900 signal. Robert

Tyson Chicken

I would say it slightly different. They are sites in which we have not received any status update for yet to date. Probably 1/2 to 2/3 of them are In Progress. Robert via Nexus 5 using Tapatalk

Sprint is net losing subscribers. MVNO's aren't hurting the network. The issues here are much bigger than MVNO's. Robert via Nexus 5 using Tapatalk

This is the first I've heard of any confirmation of the rumors. Exciting to consider. If it is 1,200 sites, it would have to be a build over of all the nTelos territory, from Morgantown down to Blacksburg, from the Tri-Cities over to Roanoke and Lynchburg. And then it would have to be amazingly dense. But that may be because of Band 41. I hope it happens. Robert

Yes. You are not in the know. Robert

We had about half a dozen sites go from nothing to 3G/4G accepted in today's update. Happens all the time. Robert

You shouldn't have a problem. I didn't with mine. I take it you already have your SIM card? Robert

This is our understanding. Google provides the update. However, we also would have told you a few days ago that you should have no problem using a Tmo Nexus 5 on Sprint. So, take that for what it's worth. Robert

My wife used to work in this building back in the Mid 90's at Commerce Security Mortgage. I also hit a pedestrian in front of that building in 1996. She walked right out in between two large commercial vehicles into my path. I clipped her in the leg with my bumper from my 1991 Isuzu Trooper. Oh the memories. Fortunately a Reno PD officer was right behind me. She was claiming I was speeding and swerving, but he saw the whole thing. Fortunately she wasn't injured except for some scrapes and bruises. She never even looked where she was going. What were we talking about again? Robert

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 thread, NV Sites Complete Map

What PRL is it running? That's likely why it will not pick up and run on nTelos 3G. Robert via Nexus 5 using Tapatalk

Then you lose out. Case closed. On to the next regional carrier. Robert via Nexus 5 using Tapatalk

I wonder if AT&T has since added Google MEIDs into their database? Although with AT&T, they didn't hesitate to add an MEID to the system for me. Mine was added at a store. And my wife's was added on a phone call with customer service while we were in Wyoming. Robert via Nexus 5 using Tapatalk

I can tell you that on AT&T, you can put the SIM in a Nexus 5 and it will work on EDGE, GPRS, HSPA and HSPA+. However it will not work on LTE. You have to call AT&T or go into an AT&T store and have them add the MEID to their system for it to work on AT&T LTE. But AT&T will add any MEID to their system, no questions asked. With Tmo, I have only used the Nexus 5 and Nexus 4. Neither of these did I need to call and have the MEID added to use LTE. But then again, Google may have supplied them the MEIDs and they already had them in the network. Robert via Nexus 5 using Tapatalk

We are really short on details about what will happen to remaining license holders. I like what you've outlined as the best way to handle it. I hope it comes to pass that way as it would allow FDD to be used. Robert via Nexus 5 using Tapatalk

Sprint only adds MEIDs for devices it purchases from the OEM. Not ones sold by the OEM to anyone else. Sprint has a closed network, by design. Just like Verizon. The only exception to this is Apple and Google. Apple provides the data to Sprint for Apple devices bound for the Sprint network. Google provides MEIDs for all the Nexus 5's it sells directly to consumers to Sprint to add to their MEID database. That's it. We used to believe that Google provided MEID's to Sprint for all North American N5's. But it turns out they only provide the ones Google sells, not the ones sold by other carriers. To my knowledge, the only other American provider that sells the N5 directly is T-Mobile. AT&T does not sell the N5. AT&T customers have to buy directly from Google. Robert

It may not be as bad as it sounds. Sprint has contracts for backhaul at all sites already. So there is a backhaul vendor assigned to that site. If you had access to the Sprint database, you would see that each site has an anticipated backhaul ready date. The backhaul vendors periodically update Sprint on their progress and those get updated in the master database. If the backhaul vendor has not provided a schedule date yet, it says N/A or TBD. The "manager" you spoke to said what he said because in the schedule for that site it has no information. It says backhaul ready date as N/A or TBD. He is interpreting that to mean it is not even scheduled yet. And that may be true. But it is also possible that a date will pop in there only a week or a month before backhaul arrives. It also happens that backhaul is installed without a date ever being put in that field. It really comes down to the backhaul vendor. N/A or TBD in the backhaul ready date field just really means that the backhaul vendor has not provided a date for the site. Not that work has not been scheduled for the site. They may be finishing up their plans or waiting for crews to become ready from another state before finishing up their schedules. And one final thought. The one time I talked with a field crew manager and he showed me his schedule, it was almost 60 days old. Meaning he had not printed an updated schedule for along time and it was way out of date. It is possible also that the a site does have a scheduled date now, but did not the last time he received an updated printed copy for his sites. I'm not trying to get your hopes up. I'm just trying to give you some more background info to give you a more complete picture. Robert via Samsung Note 8.0 using Tapatalk Pro

I believe that only the Google sold and Sprint sold N5's have been put into the Sprint database. The ones sold by Tmo directly to their customers apparently are not in the Sprint database. And Sprint probably would think that's a good idea, in general, because it creates a way for people who bought Tmo N5's who have not paid off their device from leaving their unpaid device balance behind on Tmo. Typically the people who buy the N5 from their wireless provider it is because they want it to be financed/subsidized. I know that most Sprint customers who bought the N5 from Sprint did so under contract. People who paid full cash price bought them from Google (because they were cheaper in most instances). This could cause havoc on the resale market. How many Tmo purchased N5's are going to end up being sold by their original customers to people who think that they can take that device and use with Sprint? I think we should no longer say any N5 can be used on the Sprint network. We need to be saying only N5's purchased from Google or Sprint can be used on the Sprint network. Sprint should reconsider and find a way to add N5 MEIDs to their system like AT&T and Tmo do. They are at a disadvantage. Basically they are saying they don't want Tmo N5 customers to switch to Sprint...ever. But the reverse is not true. Sprint N5 customers can freely move to Tmo. This is going to bite them in the derriere. But it's hard to imagine if this will end up affecting 1,000 or 500,000 people. It could be pretty limited. Not sure. Robert via Samsung Note 8.0 using Tapatalk Pro

http://s4gru.com/index.php?/topic/517-nv-sites-complete/?p=266641 Robert via Samsung Note 8.0 using Tapatalk Pro

We had one report of someone connecting to a Band 26 site in North Wisconsin. That's it so far. If any of you get into range of an accepted Band 26 site, change your banding priority to put Band 26 up top and cycle airplane mode and see what happens! Robert via Samsung Note 8.0 using Tapatalk Pro

Beaver Dam Robert via Samsung Note 8.0 using Tapatalk Pro

Site acceptance reports from Thursday (1/9) through Sunday (1/12): Alabama – 7 updates (5 LTE) Albuquerque – 2 updates (3G) Arkansas – 2 updates (3G) Atlanta/Athens – 12 updates (2 LTE) Austin – 7 updates (2 LTE) Baltimore – 9 updates (7 LTE) Boston – 7 updates (5 LTE) Central Illinois – 2 updates (1 LTE) Central Jersey – 2 updates (3G) Central Pennsylvania – 3 updates (3G) Charlotte – 1 update (LTE) Chicago – 10 updates (6 LTE) Cincinnati – 7 updates (LTE) Cleveland – 10 updates (8 LTE) Colorado – 2 updates (1 LTE) Columbus – 3 updates (2 LTE) DFW – 5 updates (2 LTE) Delaware – 1 update (LTE) East Iowa – 2 updates (1 LTE) East Kentucky – 1 update (3G) East Michigan – 14 updates (4 LTE) East Texas – 8 updates (LTE) Ft. Wayne/South Bend – 1 update (LTE) Georgia – 4 updates (2 LTE) Gulf Coast – 5 updates (LTE) Houston – 8 updates (2 LTE) Idaho – 3 updates (LTE) Indianapolis – 3 updates (2 LTE) Inland Northwest – 1 update (LTE) Jacksonville – 6 updates (4 LTE) Kansas – 5 updates (1 LTE) LA Metro – 5 updates (4 LTE) Las Vegas – 4 updates (1 LTE) Louisiana – 2 updates (LTE) Lower Central Valley – 1 update (3G) Memphis – 3 updates (1 LTE) Miami/West Palm – 8 updates (6 LTE) Milwaukee – 14 updates (12 LTE) Minnesota – 19 updates (17 LTE) Mississippi – 3 updates (LTE) Missouri – 11 updates (4 LTE) Myrtle Beach – 1 update (LTE) Nashville – 8 updates (3 LTE) New Orleans – 3 updates (2 LTE) New York City – 16 updates (11 LTE) Norfolk – 10 updates (2 LTE) North LA – 5 updates (3 LTE) North Wisconsin – 6 updates (LTE) Northern Connecticut – 2 updates (1 LTE) Northern Jersey – 8 updates (5 LTE) Oklahoma – 4 updates (3 LTE) Orange County – 3 updates (2 LTE) Oregon/SW Washington – 9 updates (8 LTE) Orlando – 6 updates (LTE) Philadelphia Metro – 5 updates (4 LTE) Phoenix – 13 updates (11 LTE) Pittsburgh – 2 updates (1 LTE) Providence – 1 update (LTE) Raleigh/Durham – 3 updates (3G) Riverside/San Bernardino – 9 updates (5 LTE) Rochester – 3 updates (3G) SF Bay – 8 updates (4 LTE) San Antonio – 4 updates (3 LTE) San Diego – 4 updates (1 LTE) South Bay – 6 updates (4 LTE) South Carolina – 6 updates (5 LTE) South Texas – 6 updates (2 LTE) South West Florida – 2 updates (LTE) Southern Connecticut – 3 updates (2 LTE) Southern Jersey – 6 updates (5 LTE) Tampa – 5 updates (3G) The Panhandle – 1 update (3G) Tucson/Yuma – 12 updates (10 LTE) Upper Central Valley – 21 updates (8 LTE) Upstate NY Central – 1 update (3G) Upstate NY East – 2 updates (LTE) Utah – 16 updates (4 LTE) VT/NH/ME – 3 updates (3G) Washington DC – 4 updates (1 LTE) West Kentucky – 15 updates (8 LTE) West Michigan – 19 updates (17 LTE) West Texas – 6 updates (1 LTE) West Washington – 5 updates (3 LTE) Winston/Salem – 4 updates (1 LTE) Maps are updated. Robert Links: Comments regarding this thread, NV Sites Complete Map

I don't even have the problem when updating the app. Strange. Robert

There is no apparent risk to sharing your ID. However, it wouldn't be a big leap for scammers to set up a site and ask for more info and people provide it trying to build their family. We just don't have the time or ability to go evaluate different Framily group venues outside of S4GRU. Members should be mindful, cautious and not provide any personal information to people they do not know personally. We cannot assist or be held responsible for anyone working with strangers on Framily groups. Robert