Having read many other posts, apparently the phone is trying to connect on channel 476, which doesn't work. Are there any ways to force the phone to connect on another channel? I have forced the network to be CDMA only. Every once and a while, after numerous reboots, reactivations and so forth, apparently the phone randomly connects using a channel that does work, but this is seldom the case. And every time one takes the phone out of range of the Airave, it doesn't reconnect.
It's frustrating that after a couple of years of this problem, Sprint still doesn't have a fix or work-around. Because the signal strength is highly variable, tending towards zero, at my house, the Airave is essential, but it doesn't work because of this channel connection issue.
Hello,What kind of broadband do you have? Does the Airave have an antenna hooked to it? An Airave only works on certain types of internet providers. It works on cable and not on Satellite internet. If you have an antenna hooked to it is it pointed at the tower. the antenna is very directional. Does the Airave connect to your cellphone from a tower of wifi router? If it is wifi then you have to put a a code to get full connection. An Airave is just an amplifier which has the ability to send calls over the internet. You very well have to connect your phone to the Airave with the setup code. You may find it in the manual. Forget Sprint Support they have no answers. Do internet research the Truth is Out There!
One thing you have to understand about wifi is you can turn on the wifi but it doesn't mean that you get a full connection. You have to go to your router control page and click on wireless and it will ask you for a code. The code is found on your cell phone. Go to settings, wifi and bring up the list of wifi connections and look for WPS pin entry. There you will find the code. Enter the code into the router control page and click register. Then you get a full protected connection. When I did this I found a faster better connection. Wifi calling works better!
Thanks for the attempt at helping, but as you mentioned, changing the PRL doesn't solve the problem. The phone is usually using channel 476 to connect to the Airave, which won't accept it. Basically it's a problem with the PRL priority of the phone overriding that of the Airave.
This has been going on for a year and still no solution.
Actually isn't using channel 476 the problem? If the phone randomly ends up on another channel, the Airave works. But this has been going on for a very long time without any resolution. Apparently make Airave work with newer phones isn't important to the company.
Hello Yannick... It's been a long and frustrating experience with the present Airave 2.5 Plus. On occasion, the connection will work, but usually, it doesn't. At this location, we are pretty much dependent upon Airave as the local Sprint availability has gotten significantly worse over the past couple of years.
In any event, from the perspective of the Android developer community, the problem relates to the Airave having lower priority for snagging a phone channel than the local Sprint tower. On occasions when the tower isn't detectable, the phone connects to the Airave, for a while at least. The link below discusses one fix, along with a detailed analysis and description of how the PRL needs to be changed.
It seems like a complete and rather simple solution, namely just a couple of lines in the PRL have to be changed. Can you escalate this to Sprint engineering and see if we can actually get this fixed? Given that the Samsung Galaxy S 5 is a flagship product, it would seem like it should have high priority for the fix. This has been going on for over two years and absolutely no meaningful solution from Sprint other than maybe try this or maybe try that. It's a question of whether the corporation recognizes that there's a problem, as perhaps there are only a handful of customers using Airave, and wants to devote resources to implement it. Apparently the answer is no. But it would be nice to be wrong about this, having been a Sprint customer for close to 15 years and a high-value post-paid account.
About two weeks ago, I noticed an OTA PRL update come across. This was also after an OTA upgrade to Android 5.0 which perhaps occurred a few days beforehand.
Thus encouraged, I fired up my Airave, and found that almost all the time, the Galaxy S5 will connect to the Airave for outbound calls. Call quality is still variable; sometimes the party called will fade in or out, even if they are on a landline. However, it's an overall improvement compared with trying to use the local tower, or Wi-Fi calling, which had terrible voice quality or often simply didn't work (this is on a 30 megabit download/5 megabit upload connection).
Here's what's still not working.
If someone calls me, my phone always connects to the tower, not to the Airave, to receive it.
We're going on almost two years not that the Airave isn't working with the S5. Anything further to report?
My Airave was made in January 2013. Is it a 2.0, 2.5, or 2.5+ model?