dkyeager

from conference call: 60% covered by 800 LTE, other 40% this year. might use 1.9 for uplink, 2.5 for downlink

Sprint powerpoint presentation: http://investors.sprint.com/Cache/1500068070.PDF?Y=&O=PDF&D=&fid=1500068070&T=&iid=4057219

http://finance.yahoo.com/news/sprint-reports-results-third-fiscal-123000887.html;_ylt=A0LEViQOZNNUZjkA838nnIlQ Strange $2.1 billion charge -- to improve future earnings? there is also a 101 day category Some of Sprint's notes are at a high interest rate of 14.75% from Clearwire explanation starts at 8:30am

Posting for nowerlater: 1x1900 and 1x800 BID info from v3-GCI-PCI-BID finder for 12/27: sid nid bid bid_latitude bid_longitude rssi latitude longitude Type BID Status (hex)? SID-NID-BID 22442 214 59506 39.621944 -83.498889 -88 39.698906 -83.464216 1x800 E87x 22442, 214, E87x 22442 204 59603 39.709722 -83.447222 -84 39.697880 -83.457772 1x800 E8Dx 22442, 204, E8Dx 22442 214 59811 39.824722 -83.171667 -83 39.813902 -83.185634 1x800 E9Ax 22442, 214, E9Ax 22442 214 60515 39.949722 -83.480833 -70 39.941945 -83.472968 1x800 EC6x 22442, 214, EC6x 22442 214 60739 39.954722 -82.551667 -64 39.957832 -82.532501 1x800 ED4x 22442, 214, ED4x 22442 204 61138 39.950278 -83.491389 -81 39.942070 -83.486962 1x800 New BID: EEDx 22442, 204, EEDx All new BIDs are plausible. The all match existing 1x800 BIDs Posted into special 3G spreadsheet tracking NID-SID-BID for user with SCP user notes to display proper street location.

You might also run into trouble with that. But iCellularInfo gets no hits on Google search. Great work!!

Do you have the problem only when using or near to Clear sites? (Does it work at home, but not at work?)

Posting for imex99: 1x1900 and 1x800 BID info from v3-GCI-PCI-BID finder for 12/14: BS Latitude BS Longitude SID NID BID Type BID Status(hex) New SID-NID-BID 39.70638889 -82.68666667 4418 214 59521 1x1900 E88x 4418, 214, E88x 39.73833333 -82.64250000 4418 214 59635 1x1900 New: E8Fx 4418, 214, E8Fx 39.73250000 -82.71166667 4418 214 59682 1x1900 E92x 4418, 214, E92x 39.77555556 -82.60972222 4418 214 59715 1x1900 E94x 4418, 214, E94x 39.78388889 -82.67305556 4418 214 59746 1x1900 E96x 4418, 214, E96x 39.83361111 -82.75388889 4418 214 59826 1x1900 E9Bx 4418, 214, E9Bx 39.83833333 -82.54666667 4418 214 59842 1x1900 New: E9Cx 4418, 214, E9Cx 39.89694444 -82.57638889 4418 214 60067 1x1900 New: EAAx 4418, 214, EAAx 39.99027778 -82.52750000 4418 214 60737 1x1900 ED4x 4418, 214, ED4x 39.99527778 -82.39083333 4418 214 61571 1x1900 New: F08x 4418, 214, F08x 40.00611111 -82.58250000 4418 214 61666 1x1900 New: F0Ex 4418, 214, F0Ex 40.14416667 -82.35194444 4418 214 61841 1x1900 F19x 4418, 214, F19x 40.04694444 -82.46444444 4418 214 61858 1x1900 New: F1Ax 4418, 214, F1Ax All new BIDs are plausible. The all match existing 1x800 BIDs Posted into special 3G spreadsheet tracking NID-SID-BID for user with SCP user notes to display proper street location.

Posting for Oakley707: 1x1900 and 1x800 BID info from v3-GCI-PCI-BID finder for 12/9: Last Date sid nid bid bid_lat bid_long rssi latitude longitude Type BID Status (hex)? New SID-NID-BID 12/9/14 4418 214 60915 39.958889 -82.626667 -63 39.960142 -82.628084 1x1900 New BID: EDFx 4418, 214, EDFx 12/9/14 22442 214 60915 39.958889 -82.626667 -83 39.960151 -82.639949 1x800 EDFx 22442, 214, EDFx 12/9/14 4418 204 63443 40.305556 -83.575000 -92 40.307260 -83.585580 1x1900 F7Dx 4418, 204, F7Dx 12/9/14 4390 203 30450 40.312778 -83.630278 -88 40.323463 -83.621878 1x1900 76Fx 4390, 203, 76Fx Posted into special 3G spreadsheet tracking NID-SID-BID for user with SCP user notes to display proper street location.

Posting for UPdownLoAD: 1x1900 and 1x800 BID info from v3-GCI-PCI-BID finder for 12/7 from Signal Check Pro Last Date sid nid bid bid_lat bid_long rssi latitude longitude Type BID(hex) New SID-NID-BID 10/8/2014 22442 214 61265 39.988542 -82.754653 0 0 0 1x800 EF5x 22442, 214, EF5x 9/17/2014 4418 214 61969 40.057361 -82.680764 0 0 0 1x1900 F21x 4418, 214, F21x 12/7/2014 22442 214 61921 40.061667 -82.813611 -103 40.14825 -82.687072 1x800 F1Ex 22442, 214, F1Ex Posted into special 3G spreadsheet tracking NID-SID-BID for user with SCP user notes to display proper street location.

Posting for UPdownLoAD: 1x1900 and 1x800 BID info from v3-GCI-PCI-BID finder for 12/7 from Signal Check Pro Last Date sid nid bid bid_lat bid_long rssi latitude longitude Type BID(hex) New SID-NID-BID 12/01/14 4418 214 61905 40.059167 -82.868333 -88 40.057504 -82.863530 1x1900 F1Dx 4418, 214, F1Dx 11/03/14 4418 214 61922 40.051042 -82.809722 -89 0 0 1x1900 F1Ex 4418, 214, F1Ex 12/01/14 4418 214 61923 40.045000 -82.825556 -83 40.063884 -82.846398 1x1900 F1Ex 4418, 214, F1Ex 12/06/14 4418 214 62146 40.036389 -82.486667 -70 40.063466 -82.472183 1x1900 F2Cx 4418, 214, F2Cx 12/07/14 4418 214 62801 40.134444 -82.708333 -42 40.148294 -82.687145 1x1900 F55x 4418, 214, F55x 11/02/14 4418 214 62803 40.123611 -82.741875 -81 40.125403 -82.782733 1x1900 F55x 4418, 214, F55x 12/07/14 4418 204 63297 40.272500 -83.535278 -59 40.274630 -83.533529 1x1900 F74x 4418, 204, F74x Posted into special 3G spreadsheet tracking NID-SID-BID for user with SCP user notes to display proper street location.

Posting BIDs here, which is now typically going to be with offset data, which we will match and/or compute. Posting for UPdownLoAD: 1x1900 and 1x800 BID info from v3-GCI-PCI-BID finder for 12/6 from Signal Check Pro Last Date sid nid bid bid_latitude bid_longitude rssi latitude longitude Type BID (hex) New SID-NID-BID 11/16/14 4418 214 61043 39.975833 -82.825278 -76 39.970216 -82.822001 1x1900 New: EE7x 4418, 214, EE7x 12/01/14 4418 214 61265 40.002222 -82.722500 -90 40.055638 -82.863670 1x1900 New: EF5x 4418, 214, EF5x 12/01/14 4418 214 61347 39.999167 -82.679444 -83 40.055638 -82.863670 1x1900 New: EFAx 4418, 214, EFAx 10/27/14 4418 214 62385 40.086389 -82.816667 -68 40.094815 -82.823122 1x1900 New: F3Bx 4418, 214, F3Bx 11/03/14 4418 214 62386 40.086389 -82.816667 -90 40.079785 -82.770528 1x1900 New: F3Bx 4418, 214, F3Bx 11/03/14 4418 214 62387 40.086389 -82.816667 -67 39.962703 -83.325430 1x1900 New: F3Bx 4418, 214, F3Bx 12/01/14 4418 214 61905 40.059167 -82.868333 -88 40.057504 -82.863530 1x1900 F1Dx 4418, 214, F1Dx 11/03/14 4418 214 61922 40.051042 -82.809722 -89 0 0 1x1900 F1Ex 4418, 214, F1Ex 12/01/14 4418 214 61923 40.045000 -82.825556 -83 40.063884 -82.846398 1x1900 F1Ex 4418, 214, F1Ex 12/01/14 4418 214 62065 40.071389 -82.527778 -69 40.065715 -82.523803 1x1900 F27x 4418, 214, F27x 11/24/14 4418 214 62066 40.055833 -82.508611 -56 40.063791 -82.526091 1x1900 F27x 4418, 214, F27x 10/28/14 4418 214 62067 40.063542 -82.527986 -53 40.062575 -82.527630 1x1900 F27x 4418, 214, F27x 11/03/14 4418 214 62273 40.079236 -82.865833 -57 40.089304 -82.823698 1x1900 F34x 4418, 214, F34x 12/01/14 4418 214 62274 40.071389 -82.846944 -73 40.064180 -82.854502 1x1900 F34x 4418, 214, F34x 10/25/14 4418 214 62290 40.079722 -82.493333 -87 40.055216 -82.480073 1x1900 F35x 4418, 214, F35x 10/30/14 4418 214 62291 40.079722 -82.493333 -57 40.045266 -82.477285 1x1900 F35x 4418, 214, F35x 10/30/14 4418 214 62305 40.081806 -82.556250 -83 40.154379 -82.567620 1x1900 F36x 4418, 214, F36x 10/30/14 4418 214 62306 40.081806 -82.556250 -69 40.089684 -82.539912 1x1900 F36x 4418, 214, F36x 12/02/14 4418 214 62307 40.070278 -82.585000 -63 40.074377 -82.607836 1x1900 F36x 4418, 214, F36x 12/04/14 4418 214 62401 40.093889 -82.676389 -45 40.148148 -82.687124 1x1900 F3Cx 4418, 214, F3Cx 12/01/14 4418 214 62402 40.057222 -82.734167 -82 40.055638 -82.863670 1x1900 F3Cx 4418, 214, F3Cx 10/27/14 4418 214 62403 40.086806 -82.733958 -90 40.094815 -82.823122 1x1900 F3Cx 4418, 214, F3Cx 11/15/14 4418 214 62449 40.115556 -82.512778 -76 40.133050 -82.518514 1x1900 F3Fx 4418, 214, F3Fx 11/01/14 4418 214 62451 40.089514 -82.522847 -65 40.072045 -82.626834 1x1900 F3Fx 4418, 214, F3Fx 12/04/14 4418 214 62801 40.134444 -82.708333 -42 40.148294 -82.687145 1x1900 F55x 4418, 214, F55x 11/02/14 4418 214 62803 40.123611 -82.741875 -81 40.125403 -82.782733 1x1900 F55x 4418, 214, F55x 12/03/14 4418 214 62866 40.127778 -82.877222 -70 39.962703 -83.325430 1x1900 F59x 4418, 214, F59x 12/13/14 4418 214 62867 40.133889 -82.911944 -73 39.962703 -83.325430 1x1900 F59x 4418, 214, F59x 12/04/14 4418 214 63091 40.159444 -82.680556 -75 40.167066 -82.701886 1x1900 F67x 4418, 214, F67x 11/24/14 4418 214 63121 40.204167 -82.794722 -96 40.212192 -82.803221 1x1900 F69x 4418, 214, F69x 11/24/14 4418 214 63123 40.173056 -82.823056 -88 40.162472 -82.820549 1x1900 F69x 4418, 214, F69x 10/25/14 4418 204 63235 40.236944 -82.482153 -79 40.152404 -82.520103 1x1900 F70x 4418, 204, F70x 11/24/14 4418 204 63315 40.252500 -82.805000 -96 40.230002 -82.802852 1x1900 F75x 4418, 204, F75x 11/25/14 22442 214 61345 40.018611 -82.641944 -74 40.148252 -82.687148 1x800 EFAx 22442, 214, EFAx 12/04/14 22442 214 61665 40.036111 -82.593056 -84 40.148252 -82.687148 1x800 F0Ex 22442, 214, F0Ex Posted into special 3G spreadsheet tracking NID-SID-BID for user with SCP user notes to display proper street location.

There are wooden pole sites in the Columbus Market with B41, so they can provide good service. https://www.dropbox.com/s/97q39j10nhwvmrz/IMG_9554%20cropped.jpg?dl=0

Based on the small number compared to their overall site count, I assume Ntelos was unable unload their sites that use wooden poles. You could not typically add another carrier to a wooden pole site without building a metal tower first.

Mike, we wish to use SCP's user notes to get around the use of offsets in the base station location for 3G 1x1900 and 1x800. Columbus has almost all BIDs identified, Cincinnati has most, and Cleveland is getting rolling. What are the data fields (items) must we supply to pull this off with SCP? (Sorry if this has been asked before).

Sprint appears to be redoing the B41 Coverage map on a city by city basis. Much more realistic than prior version. Slight exaggeration remains in a few local spots, but this is far far outweighed by B41 that is not shown. http://coverage.sprint.com/IMPACT.jsp?INTNAV=SJS:HE:Cov

Over 90 b25 second carrier sites have been found in the Cleveland Market so far. Maybe they can be moved up to the big league on the first page of this thread. Columbus continues to have just one B25 second carrier site.

These types of issues are happening across the three main apps used in the Columbus, Cleveland, and Cincinnati markets using numerous phone types. They seem to happen with SCP the most, Signal Detector the least, and LTE Discovery falls in the middle. SCP logs are more reliable than SCP screen shots. I have taken the approach of being gentle with new sites when it fits the GCI pattern, tough on missing or changed PCIs. That is the PLMN must match, must have the right TAC for the site. I was thinking that some of the missing GCIs might be neighbor sites seen just for a instant. We are getting to the point with these logs that we are also capturing sites as they change during setup and tuning (I can see this across several phones and apps for the same site). This backs up UPdownLOad's assertion. A field showing how many hits for a particular record in the log might also be useful. Many of these errors may simply not have a large enough sample size. Even G2's typically should the correct PLMN for a clear site 80% of the time, which this would also handle. Thanks for all your work. FYI, SCP is the least intrusive in terms of privacy and seems to have very low battery consumption when operating in the background.

Any updates on when we can roam with RRPP and CCA given the right phone? (nexus 5, 6 and LG Flex 2 I believe) I am hoping it is when the start shipping the LG Flex 2.

The table may have been expanded for clarity or I just focused on the "Total maximum bandwidth of 20Mhz" (I originally quoted the table but that was removed). I will now wait for reviews / actual usage.

Total maximum bandwidth of 20Mhz. That boat just may have sank. Waiting for reviews and actual usage or the next boat... > 2GB RAM > 48 GB storage microSD card 1080p or greater android 4 or greater Sprint and CCA bands

3xCA, 300Mbps theoretical max (source: http://www.androidcentral.com/lg-g-flex-2-specs) my next phone could already be on the boat if CA works with Sprint.

When service gets really really bad, then it might be time to visit sites. You might find work being done in new cabinets. The antennas tend to go up last.

Typical time to upgrade a power tower site by aep contractors according to regular sprint contractors: five weeks.

http://newsroom.sprint.com/blogs/sprint-perspectives/sprint-meets-its-2014-network-milestones-sets-its-sights-on-the-year-ahead.htm Press comment #1: http://www.fiercewireless.com/story/analyst-sprint-likely-hit-spark-buildout-target-2014-will-focus-small-cells/2014-12-17 My comment relating mostly to Ohio: The International Boundary Exclusion Zone (IBEZ) of 87 miles and Sprint's defacto buffer zone of 30 miles or more, reaching into most sites in the northern half of the Columbus metro area, will very likely not have 1x800 service by the end of the year. There has been a small amount of movement lately, but that could easily be taken away just as it has in the past. Sprint has been going gangbusters on B41 LTE 2500/2600. I am puzzled as to why their B41 LTE 2500/2600 coverage maps contain fictional areas while ignoring areas where it has existed for months. However, they do seem to be able to deliver on these maps within several months. B26 LTE 800 is a great service. Optimization of each individual band is going well. Optimization of getting the best utilization of the overall triband experience needs significant work in many areas. Small cells fascinate us -- we have been watch Verizon built and extensive small Cell network in Columbus that they have yet to deploy. While we would love to see some Sprint small cells here in a few places, they are better suited for NYC, LA, and Chicago. No discussion of B25 LTE 1900 second carrier which seems to be expanding into many markets.