larryt510

I've had this phone since 11/2012 and can't wait to ditch it on 7/1 when I qualify for a new device. Been battling constant force close issues with the apps (especially text messaging and browser). Battery life started out very good but has degraded significantly over time. Incoming calls often roll to voicemail without the phone ringing. Also occasionally have to reboot the phone to get certain functions to work again.

25017 is out

I think certain phones just don't jive well with the Airave. It was like that back in 2008 and even with the supposedly improved models there remains issues with some phones. My LG Optimus G absolutely won't connect to it. Once in a while it sees the PN offset of the Airave (debug engineering screen shows this) but it immediately rejects it and goes back to the regular network even though the Airave signal is stronger.

My original Samsung version 1 from 2008 could make handoffs to the regular network. But it didn't always work.

An Airave broadcast 800? I wasn't even aware that was possible.

Update. Once again it no longer connects to the Airave after I walked outside and came back in. This might be unfixable.

Ok so I called tech support and they fixed it. There was nothing wrong with the Airave channel (225) and the channel my phone was on from the regular network (25). They had me reprogram the phone with the handsfree activation thing and then update profile, PRL. All things I had already tried yesterday but for some reason today it worked. He claimed that sometimes certain smartphones will get stuck on a channel and have to be reset like this to pick up the Airave. So far good results. Calls sound good, texts send out fine and the data speeds are the same as what I normally get from my DSL connection. I did have to hook up the GPS antenna and run it to the window as the red light would intermittently come on and blink. But now it's fine with the antenna.

I don't know anything about PRL editing. Sprint should make sure that the Airave works correctly with every phone, PRL etc. You shouldn't have to mess around with the PRL to get it to work. But I will call tech support and see what they can do tomorrow and mention what you said about the channel thing.

Still happening. I waited about 6 hours and my phone still wouldn't connect to it. Had the phone in the same room right next to it for at least 2 hours. I don't think it's a problem with the unit because an older Samsung flip we have connects to it fine. It appears to be an incompatibility issue with the LG Optimus G and the 2.5 Plus Airave. I'm going to have a friend bring over another LG OG and see if it can connect.

That's strange. All four lights are green now but phone will not connect to it. My old Samsung Airave would connect immediately.

Got my 2.5 Plus the other day and am trying to activate it right now. So far the fourth light is still blinking red after about 25 minutes.

Exactly right. Bouncing on different cell sites and PN offsets on the same NID and you will probably be fine. But when you're right on the border between two or more cell sites on different Network ID's it's a whole different story. I thought this problem here would be fixed when they made new boundaries and consolidated NID's but I was wrong. The phones still behave the same way they always have with the missed incoming calls. So not sure what's going on unless the two separate switches are still there under a single NID.

Yeah it's been happening since 1997 when I first signed up. At first I didn't know what the cause was but someone later tipped me off to the NID boundary. Congestion in the paging channel (capacity) can cause this too but I do not believe that is the reason here.

Just called and requested my replacement Airave since my old Samsung no longer works as of today. They said they are sending me a 2.5 plus. I wish I had called last week because my local cell site went down on Saturday after someone tried to steal copper from it. Could be weeks or months before it's fixed as it's located on our local power company transmission tower and land and only they can repair it. So very poor signal until the new Airave arrives.

No, the problem I'm talking about is not related to NV upgrades.

Update. So after giving this a fair amount of time I have come to the conclusion that the NID consolidation here DID NOT fix the missed incoming calls problem. Still have the exact same issues as I always had before. So I'm thinking that even though the cell sites around here are now on the same NID, there still must be two separate sub switches in that NID that still produce the same symptoms as being on the NID boundary did before. Very disappointing. AJ, any idea on this?

Same thing happened in Norwalk, CA with the widening of the I-5 freeway. A motel that used to house antennas for at least three carriers (inlcuding Sprint) had to be torn down for the construction work. They ended up putting up a monopole about 300 feet away to replace it and they timed it so all three carrier's had their new equipment on the new tower before the building and the old equipment were demo'ed.

As of a couple of years ago Verizon actually had the same NID boundary here in my area as Sprint did. Meaning their two neighborring cell sites on different NID's were in the exact same location as Sprint's. Just a coincidence? No idea. The great majority of both Verizon and Sprint users do not live or work near these NID boundaries and would not be affected.

Good to hear as having fewer NID's will make for a better and more reliable network. Orange County has always had just the two NID's but I have yet to pick up the other one. A friend at Sprint told me that we still have both but I haven't had a chance to travel out to the Southern and Northern parts of OC yet to see exactly what they have done and where the new borders are. I'm also wondering what might have occured in Los Angeles and the Inland Empire with those NID's.

NID 2 (Irvine switch 1) seems to have vanished. I drove a few miles further today and was still on NID 3 in what was formerly solid NID 2 territory. Interesting. More testing later when I get the time.

As some of you like AJ know I have been complaining for years about the terrible way that the Irvine 1 and 2 network switch boundary (also known as Orange County NID 2 and NID 3) was set up. These boundaries are supposed to be set up in a way that has the least amount of impact on the customers. This was not the case here in my area as they basically split it up right along a busy freeway and highly populated residential and shopping areas. Now had they moved NID 2 just one more cell site to the West it would have been much better as there would have been a separation by a hill to help minimize the impact. So my hope all along was that they would do just that. I'm very happy to report that they even did better than that. They also moved all the cell sites that I can possibly connect to to the same NID. So they scaled back the territory of NID 2 and increased the size of NID 3 which was a great idea. I haven't completely driven around and tested a wider area yet to see all of the exact changes but I can say for sure that the six closest cell sites to me are all now on NID 3 whereas before there were two on NID 3 and four others on NID 2 which created an epidemic of missed incoming calls. Now that it's been changed to a much better layout I would expect that the days of missed incoming calls are over. I can post a more detailed analysis and give specific cell site locations and ID #'s in the sponsor forum if anyone's interested.

The Katella/Tustin tower does have LTE installed and ready to go. But they haven't officially activated it yet unless maybe for some quick testing.

Yeah you are right. The site was working in the morning but later it shut down again. As of 11PM last night it was restored again. Hopefully this time it will stay operational but with the way this site has been malfunctioning I wouldn't bet on it. Never seen an outage this prolonged before that wasn't caused by fire or something like that.

They were working on it last night and it appears like it's been fixed now. Let me know if it's back to normal now.

Probably because the cell site near Fletcher and Glassell has LTE installed but might still be in the testing phase.