Jump to content

time in Complete but blocked until LTE general use


DaQue

Recommended Posts

Anyone have a guess on the average time Sprint blocks a site thats complete? I know if its the first one in an area it will be longer. What's the longest a site has been complete but blocked?

 

Side question dose the sponsor section have a launched and working list.

 

Im getting real close to sending some cash. I would have already but things ave been tight last few years. Ok that and Im just cheap.

Link to comment
Share on other sites

There are a sites complete list that Rob updates every week in the sponsors section, there is also a running list of markets but does not require sponsorship but you get a lot of great info with becoming one.. donating 20 bucks would be good but we you can offer Rob would be welcomed

 

Link to comment
Share on other sites

Anyone have a guess on the average time Sprint blocks a site thats complete? I know if its the first one in an area it will be longer. What's the longest a site has been complete but blocked?

 

Side question dose the sponsor section have a launched and working list.

 

Im getting real close to sending some cash. I would have already but things ave been tight last few years. Ok that and Im just cheap.

 

We had some sites complete in early March but were blocked until Mid July. That was the longest. However, I don't think that's going to be typical anymore.

 

It is so variable though, its not really possible to answer your question. Early sites will likely be blocked longer than later sites within a market. Sprint doesn't block some sites ever, probably in error. However, most sites are blocked after Sprint accepts the site from the OEM until a market is pre launched or launched.

 

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

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...