larryt510

So why did I go from 51104 to 55022 after getting the Android 5.0 update last night om G3?

Still no update here...

Update. Looks like they installed a small microwave dish on the South facing RRU yesterday. So my site will get LTE 1900 using microwave relay which is what I expected considering that the AT&T site on the same tower also uses a microwave relay. Hard to get Ethernet feed up in the hills.

Looks like my site might finally be getting LTE installed. There's some type of work being done at the base station as well as the antennas. Hopefully it's LTE

51104 just came in on my G3

A friend of mine reported that this could be an update that affects Arizona but not confirmed yet. There was a Sprint internal bulletin sent out about an upcoming network change there and at least one other state too.

Am I the first to report that 51103 is out?

Yes this NID boundary was set up back in the 1990's when Sprint first entered the market here. It was the absolute worst place they could have picked to divide up the NID split. 12 months ago (last September) they finally merged the two NID's into one but the incoming call failure was still happening even worse than it had been before the NID merge. I kept putting pressure on them with repeated tickets on it and was in contact with one of the top RF engineers in So. Cal. Finally one day I woke up in early June and it was fixed. I also breathed a sigh of relief last week when they converted my local cell site over to 3G NV and nothing got messed up in the process. lol

Site went NV 3G live today! Got a nice strong signal. Possibly even better than I had before. In debug mode Ec/Io seems better now!

They are probably thinking 2017 is a long way off so why worry about it now.

Haha I doubt it. A few of the sites around here have the dual RRH's and some don't. Not sure why that is and capacity does not appear to be a factor since some of the sites with only one RRH are located along busy freeways and some of the ones that have two RRH's like this one do not get a lot of traffic. It looks like they kept the same azimuth's on this site (thankfully) but unfortunately the panels appear to be mounted slightly lower (by 1-2 feet) now than they were originally, even with the taller NV panels taken into consideration. Hopefully this does not affect coverage as this site really needed higher mounting not lower due to the hilly terrain as evident by AT&T taking the top spot on the tower. The site is not NV active yet but I can only hope that the RRH's will boost signal strength slightly to make up this difference but so far I have not been able to see any gains in signal strength with NV on any other sites.

2 RRH's per sector. Today:

3 sector site.

Pics taken today of my site. Notice they are about to hoist up the NV panel and RRH to the mounting bracket. Here's the site back in 2013. Sprint is on the lower level. AT&T is the higher level.

Yeah but I decided not to go public with it since it might contain proprietary info. I don't want to get in trouble.

Yeah probably because all of those require extra red tape and/or have more challenging installations. There are plans to convert many of the DAS sites around Malibu, Topanga, Palisades, Studio City, etc but it looks like most of them are planned for 2015.

Full build site. All of the utility power line towers in this area are full build.

I had reported a few times the past couple of years that Sprint typically wasn't doing NV upgrades on most of the cell sites that were located on power company utility lattice towers. More specifically Southern California Edison property towers. Well I'm happy to report that most of them are finally getting done now including mine which construction began this morning. With over 95% of all sites already been upgraded it figured that mine would be in the final 5%. Been a LONG wait and glad it's finally over. Now I'm just hoping that they don't mess anything up and keep the azimuth pattern the way it's been without modification.

But I don't get why it is showing my phone as being on SID 19 and NID 33. We are clearly SID 4145 and NID 3.

Just got an LG G3 and now I notice in debug mode I'm switching back and forth between band class 1 and band class 3. Also switching back and forth between NID 3 and NID 19 (This entire area is definitely NID 3 so not sure how this 19 factors in). What's the deal with this? It's not causing missed incoming call thankfully.

Ok so that confirms it's just the way the charging port is on this phone. Thanks.

Joined the LG G3 club on Thursday. Picked one up at Best Buy for $100. One of the thing's I noticed was that the micro usb charger connector seems tight or hard to get in and needs a sweet spot to get in just right. At first I thought it might have been a minor manufacturing glitch but a friend's G3 is the same way (purchased from same store at same time). Anyone else notice this? Does it need a little breaking in before it fits easy? Also does this phone tend to heat up when charging or when running navigation in the car? Seems like it gets a little warmer a little faster than my previous LG Optimus G. Other than that it's a great phone so far although it's too bad it wasn't a tad smaller.

I'm all set to get a new handset and will probably do so once the LG G3 becomes available on 7/18 so I should be good to go from this point on. Last night's testing once again confirmed that they have finally fixed the NID boundary blocked call issue here in Orange County (nearly 9 months after they consolidated the two NID's). So hopefully the days of missed incoming calls are now behind me.

Here in the Orange County, CA area there's been only 2 or 3 new sites added in the past 3 years and I think one was a replacement for one that was decomissioned. Hardly anything and disappointing. It's possible that I might have missed one or two but I try to keep a watch on it with my own source.

Well here it is 10 months later and I have some good news to report. It appears that the NID consolidation here in Orange County has finally eliminated the failed incoming call problem. When they first consolidated the NID's late last year the incoming call problem seemed to have actually gotten worse right on the border where the old NID's were set up even though all of the cell sites in this area were now showing on the same NID. I kept calling in and filing tickets on it but it never seemed to do any good. The issue remained horrible up until early last month. But it appears that the problem has finally been solved now. But I'm going to keep testing it out for another couple of weeks to make sure and report back again.