Some of you may have seen this in my MeanROM thread, but I thought I'd start a thread for it for others who may have the problem. I noticed a few days ago that my phone was no longer ringing while roaming. People would call and it goes straight to voicemail while roaming. I tried all manner of tricks (some which did work for others) but none worked for me. I did PRL updates, profile updates, wiping dalvik and cache, wiping multiple times, factory resets, multiple factory resets. Bottom line: my phone flat out will NEVER ring when roaming on PRL 25006 (the normal PRL for us now): only when on Sprint. Odd thing is, you can pick up the phone and make an outgoing call fine on roaming: just won't ring. As a last ditch effort before getting mired up in Sprint phone support for an hour, I put back my old 12124 corporate PRL that I had used for about a month and then dumped (only because I didn't see a difference). I've now done this at least a half dozen times: as soon as I push 12124, the phone will ring (and work) every time while roaming! Put 25006 back: won't ring.
Again, I've tried every trick that everyone has mentioned and the only factor is the PRL. Push 12124: works fine. Do "update PRL" and get 25006 back: won't ring while roaming; only when on Sprint. At my house, depending on what part of the house I'm in, that means I can't get calls at least half the time on PRL 25006 so thankfully we have 12124. Now I know 12124 isn't compatible with LTE but I couldn't care less as my area here isn't compatible with LTE either: and I'd rather be able to get phone calls when I need to!
This message is nothing more than a "tickler" to say hey, I think the 25006 PRL might be hosed. Either that or Sprint has changed something on the network that makes 25006 affect some of us this way. I've never had this happen before but the only other explanation I can think of is... maybe by me running 12124 for a month or so, my phone somehow got "re-provisioned" to corporate PRL's and the way it's provisioned now, 25006 doesn't work right. That's possible too: that I caused it by running 12124 for a while. Also possible that Sprint could fix it if I could actually find someone who knows how to reset/fix provisioning. I just don't have time right now for their BS and going through 6 techs over 2.5 hours on the phone. Been hammered lately.
Anyway, might be worth checking if you roam often: if you can actually receive a call when roaming. I know it doesn't affect everyone on 25006 nor does it affect every area. Might have to be special circumstances but I feel like there must be a bunch of people here who don't even know it but can't receive calls when roaming.
Mike
samething for me on 25006. just noticed it last night when i was roaming out in the country and my wife and daughter were trying to call phone never rang once.
mikeyxda said:
Some of you may have seen this in my MeanROM thread, but I thought I'd start a thread for it for others who may have the problem. I noticed a few days ago that my phone was no longer ringing while roaming. People would call and it goes straight to voicemail while roaming. I tried all manner of tricks (some which did work for others) but none worked for me. I did PRL updates, profile updates, wiping dalvik and cache, wiping multiple times, factory resets, multiple factory resets. Bottom line: my phone flat out will NEVER ring when roaming on PRL 25006 (the normal PRL for us now): only when on Sprint. Odd thing is, you can pick up the phone and make an outgoing call fine on roaming: just won't ring. As a last ditch effort before getting mired up in Sprint phone support for an hour, I put back my old 12124 corporate PRL that I had used for about a month and then dumped (only because I didn't see a difference). I've now done this at least a half dozen times: as soon as I push 12124, the phone will ring (and work) every time while roaming! Put 25006 back: won't ring.
Again, I've tried every trick that everyone has mentioned and the only factor is the PRL. Push 12124: works fine. Do "update PRL" and get 25006 back: won't ring while roaming; only when on Sprint. At my house, depending on what part of the house I'm in, that means I can't get calls at least half the time on PRL 25006 so thankfully we have 12124. Now I know 12124 isn't compatible with LTE but I couldn't care less as my area here isn't compatible with LTE either: and I'd rather be able to get phone calls when I need to!
This message is nothing more than a "tickler" to say hey, I think the 25006 PRL might be hosed. Either that or Sprint has changed something on the network that makes 25006 affect some of us this way. I've never had this happen before but the only other explanation I can think of is... maybe by me running 12124 for a month or so, my phone somehow got "re-provisioned" to corporate PRL's and the way it's provisioned now, 25006 doesn't work right. That's possible too: that I caused it by running 12124 for a while. Also possible that Sprint could fix it if I could actually find someone who knows how to reset/fix provisioning. I just don't have time right now for their BS and going through 6 techs over 2.5 hours on the phone. Been hammered lately.
Anyway, might be worth checking if you roam often: if you can actually receive a call when roaming. I know it doesn't affect everyone on 25006 nor does it affect every area. Might have to be special circumstances but I feel like there must be a bunch of people here who don't even know it but can't receive calls when roaming.
Mike
Click to expand...
Click to collapse
Hey Mike.. On 25006 here running your Mean 3.6. When I first forced roam and attempted to call my first attempt resulted in several network courtesy rings but no ringing on my device with it eventurally rolling to voicemail... My 2nd attempt I heard about 4 network courtesy rings then myh device actually rang once before it rolled to voicemail. 3rd attempt and all subsequent attempts afterwords calls rang right through to my phone and I also tested sms text messages and data and they both worked fine. Cant really explain why 12124 works fine for you and 25006 doesnt other than possibly the first preferred roaming partner is different between the 2 because of an agreement change between carriers. Maybe whatever carrier is the 1st prefferred in your area for 25006 is having issues with correctly registering your device to its network to notify of incoming calls.. Most of the time just registering to network by completeting an outbound call but obviously isnt working for you.. Sometimes powercycling will resolve the issue also... On another note.. Im not sure if its the new sense 4.1 or your new rom that has stripped out some of the funtionality of beats audo settings.. But now the only options I get for beats audio is on/off... I no longer get the extendted options of beats ur beats.. beats solo and other.... or the option of the equalizer with beats off... Is it that way for everyone or just me?
Hope mikeyxda doesn't mind....
I have been talking back and forth with mikeyxda, it's a metropcs issue. Sounds like there is an issue with metropcs telling sprint that his phone is on their tower. Unfortunately when a call comes in, sprint thinks his phone is off so it sends it to voice mail.
The 12124 prl doesn't have metropcs in the list for his area. So he sits on vzw which works fine, but 12124 doesn't allow Lte connections. Working on a solution to fix both issues....
Sent from my C64 w/Epyx FastLoad cartridge
Do other phones work when roaming on MetroPCS?
Sent from my EVO LTE
Yeah I have this issue too. And I roam a lot too. That's not good.
Sent from EVO LTE using the XDA app
digiblur said:
Hope mikeyxda doesn't mind....
I have been talking back and forth with mikeyxda, it's a metropcs issue. Sounds like there is an issue with metropcs telling sprint that his phone is on their tower. Unfortunately when a call comes in, sprint thinks his phone is off so it sends it to voice mail.
The 12124 prl doesn't have metropcs in the list for his area. So he sits on vzw which works fine, but 12124 doesn't allow Lte connections. Working on a solution to fix both issues....
Sent from my C64 w/Epyx FastLoad cartridge
Click to expand...
Click to collapse
Mind? I'm hella grateful that we have someone with your knowledge here! I feel a lot better knowing the reason for the problem and feel a little better about Sprint because it seems like a MetroPCS problem. Although, with Sprint doing work on upgrading towers around here, I guess it could still be a Sprint problem where something they did is no longer compatible with MetroPCS. Either way, I think this problem is more widespread than people realize and I suspect anyone roaming in an area that is being upgraded while on a MetroPCS tower might have this problem. Kinda brings to light the fact that PRL's can affect more than people realize. If you're roaming, a PRL can affect data, data speed, whether or not you connect at all, and now whether or not your phone will ring when it looks like you have a signal.
Mike
mikeyxda said:
Mind? I'm hella grateful that we have someone with your knowledge here! I feel a lot better knowing the reason for the problem and feel a little better about Sprint because it seems like a MetroPCS problem. Although, with Sprint doing work on upgrading towers around here, I guess it could still be a Sprint problem where something they did is no longer compatible with MetroPCS. Either way, I think this problem is more widespread than people realize and I suspect anyone roaming in an area that is being upgraded while on a MetroPCS tower might have this problem. Kinda brings to light the fact that PRL's can affect more than people realize. If you're roaming, a PRL can affect data, data speed, whether or not you connect at all, and now whether or not your phone will ring when it looks like you have a signal.
Mike
Click to expand...
Click to collapse
Looking into the issue also... will report back when have an update...
I just chatted with a sprint tech online and so far the issue seems to have been resolved. This was the transcript:
You: well, my phone recently upgraded. Since then, whenever i am roaming, when people call, it goes straight to voicemail
Russ B.: Please confirm which line you are concerned about.
You: **********
Russ B.: Thank you.
Russ B.: Please turn off your phone and let me check this for you.
You: turning off
Russ B.: Thank you.
You: its off
You: i roam a lot, so its a problem
Russ B.: Thank you for waiting.
Russ B.: I have done some basic troubleshooting on your phone.
Russ B.: Please turn on your phone and check if you still face same issue. However I can see you are on data plan and roaming is included in your plan and you will not be charged for roaming.
You: no i know, and thats good, but if i dont receive calls while roaming, then it does me no good
You: ok its on, and im roaming right now. can you call it to see if it works?
You: i have no other phone
Russ B.: I am sorry, we are at chat support and do not have option to call.
Russ B.: I hope you can understand this. Please ask some one to call you.
You: i will try to find someone hold on
Russ B.: Sure.
You: sorry for the wait
You: someone is trying right now
Russ B.: Sure, no problem.
You: it has worked 2 times, but im trying a third just to be sure!
Russ B.: Sure.
You: it worked 3 times
Russ B.: I have just refreshed services on phone by doing some troubleshooting on your phone.
Russ B.: Great. It will be more better once provisioning will get completed.
You: ok oh it says service update right now
Russ B.: Let t get completed. Provisioning is running on your phone.
Russ B.: Yes, however it may take some time. So please do not use services on phone for 10-15 minutes.
Hope this helps. Ive received 5 calls while roaming since, some say it rings 4 or more times, and i only hear one, but it seems to be working!
mikeyxda said:
Mind? I'm hella grateful that we have someone with your knowledge here! I feel a lot better knowing the reason for the problem and feel a little better about Sprint because it seems like a MetroPCS problem. Although, with Sprint doing work on upgrading towers around here, I guess it could still be a Sprint problem where something they did is no longer compatible with MetroPCS. Either way, I think this problem is more widespread than people realize and I suspect anyone roaming in an area that is being upgraded while on a MetroPCS tower might have this problem. Kinda brings to light the fact that PRL's can affect more than people realize. If you're roaming, a PRL can affect data, data speed, whether or not you connect at all, and now whether or not your phone will ring when it looks like you have a signal.
Mike
Click to expand...
Click to collapse
Just making sure, don't want to bring PM stuff out in the public.
When roaming you are at the mercy of whatever the provider gives you. But for the most part, the other provider wants you to use all the minutes and data you can so they can bill Sprint more.
This MetroPCS issue might be just a regional thing and not nationwide. It could be even a smaller subset of users in your area as well. It's going to take quite a few phone calls to get fixed though. The easier option is to just use a PRL that doesn't use MetroPCS.
So the fact that i seem to be working just fine now is a fluke? because ive received several calls now while roaming and they have all worked just fine, whereas before they wouldnt go through at all.
edit: upon reading my post, i feel it may sound accusing. I did not intend for that, I really want to know, if it is a fluke. maybe im just paranoid!
ooonimrodooo said:
So the fact that i seem to be working just fine now is a fluke? because ive received several calls now while roaming and they have all worked just fine, whereas before they wouldnt go through at all.
edit: upon reading my post, i feel it may sound accusing. I did not intend for that, I really want to know, if it is a fluke. maybe im just paranoid!
Click to expand...
Click to collapse
What SID are you Roaming on? Check your 1x engineering screen in the ##DEBUG screen.
Sent from my C64 w/Epyx FastLoad cartridge
digiblur said:
What SID are you Roaming on? Check your 1x engineering screen in the ##DEBUG screen.
Sent from my C64 w/Epyx FastLoad cartridge
Click to expand...
Click to collapse
that would be SID # 4107
ooonimrodooo said:
I just chatted with a sprint tech online and so far the issue seems to have been resolved. This was the transcript:
Click to expand...
Click to collapse
Thanks for sharing. I rolled back to the 25006 PRL so that I have the problem again and started a chat session. They did the same thing, reprovisioned my phone, my phone got the message about starting network services. Still won't ring. Rebooted, did PRL and profile updates after that. They had me call *720 (while NOT roaming). Tried some other things too. Still won't ring on 25006. Push 12124 and it rings every time.
So I guess moral of the story: YMMV.
Mike
I hesitate to post this due to its non-technical nature. Inside the sense music app is a choice to enter Sprint Music+.
When I entered it for the first time the phone automatically went into a PRL update. The actual PRL number (25006) did not change afterwards, the 3g connectivity at fringe did. It could be the placebo affect, but maybe just maybe there was a reason for the PRL update. Just thought it should be mentioned.
BTW I also get a lot of no ring > voicemail calls while roaming. I work in a sprint fringe area.
ooonimrodooo said:
that would be SID # 4107
Click to expand...
Click to collapse
You shouldn't be roaming on 4107, that a Sprint SID.
Sent from my C64 w/Epyx FastLoad cartridge
digiblur said:
You shouldn't be roaming on 4107, that a Sprint SID.
Sent from my C64 w/Epyx FastLoad cartridge
Click to expand...
Click to collapse
My mistake. I wasn't roaming at the time. I'm roaming now and it says 6005.
Sent from EVO LTE using the XDA app
Haha truth be told, I thought it was normal for me not to be able to receive calls while roaming, thought it was just cause I force roam..
Sent from my EVO using xda app-developers app
ooonimrodooo said:
My mistake. I wasn't roaming at the time. I'm roaming now and it says 6005.
Sent from EVO LTE using the XDA app
Click to expand...
Click to collapse
That's Cricket. I'm thinking this is only a MetroPCS issue...it might even just be a regional MetroPCS issue as well.
Just an update, doesn't seem to be am across the board national issue with prl 25006 as many users have reported being able to receive calls fine while roaming. Maybe onto something with it being with certain partners or a certain partner. Definately nothing to do with anything sprint is doing to their towers as your not connected to a sprint tower if roaming..now if you are in good sprint coverage and roaming then a coverage issue may need to be looked into.
Related
For the last week or so I've noticed my dbm goes anywhere from -78 to -109. It doesn't appear to be a ROM issue (Aloysius, xtra sense, Kaos, TazzCyanFroyo), and I've flashed some radios to see if that fixes the problem.
I've tried the *#*#4636 trick, for some reason on the TazzCyanFroyo rom when I hit Select Radio, Get the force close, it kicks me out of the prog so I can't see if that option is still set to GSM.
I've also noticed my 3g kicks down to 1g. Frequently. I'm missing a ton of texts, and some of mine aren't going through. I dug around on here, but didn't exactly see anyone running as a high a dbm as I am.
Does this mean I have to unroot and drag my ass to Verizon?
As an additional, maybe useless piece of information- I live in Florida and the weather here is not usually ideal. It's been super rainy/wet/muddy here lately, could the yucky weather be a contribution? I'd LIKE to think my paying through the nose for their sub-par service means I wouldn't have to face issues like this, but I also know technology isn't impervious to forces of nature.
Thanks for your reply, folks. I *ask* that you don't flame me, but I also sort of expect it.
Possibly a PRL issue? I don't suppose you live in or around an area that was formerly Altell strong? You may need to have someone smart at Verizon tech support send you a hybrid so your phone looks for other towers that it wouldn't otherwise lock onto. I read about an issue like this and that was the solution. Seems to me it was even in Fla.
TheBadBen said:
Possibly a PRL issue? I don't suppose you live in or around an area that was formerly Altell strong? You may need to have someone smart at Verizon tech support send you a hybrid so your phone looks for other towers that it wouldn't otherwise lock onto. I read about an issue like this and that was the solution. Seems to me it was even in Fla.
Click to expand...
Click to collapse
It's incredibly likely, but I never even knew about that. Originally I came from South Carolina where my signal was excellent, but when I moved down here I never bothered to get my number changed.
Is it a piece of hardware that perhaps does it, or is it an internal program?
Where exactly are you? If you did move into a divested market that was bought by Verizon then it could be causing problems.
MrObvious said:
Where exactly are you? If you did move into a divested market that was bought by Verizon then it could be causing problems.
Click to expand...
Click to collapse
A little north of Miami, in West Palm Beach.
lilly1185 said:
Is it a piece of hardware that perhaps does it, or is it an internal program?
Click to expand...
Click to collapse
It's not hardware at all. Purely software programming. Actually, if you haven't dialled *228 since you moved that may fix your problem. PRL stands for prefered roaming list(or something close to that). Basically it's the program that tells your phone's radio which signals to pick up if you can't find a strong Verizon signal. In some markets, especially ones where Verizon has squires towers rather than built them, the default programming may not be looking for those towers even if the signal is very strong.
Try dialling *228 and updating your roaming capabilities and if that doesn't work a call to Verizon should really help.
Has anyone else had this issue with the airave? Whenever I get back into my house I guess my photon doesn't connect to the airave correctly and I get silent calls until I reboot my phone. Anyone else? I didn't have this issue with my 3d.
Airave is kinda old, that could be it.
Sent from my MB855 using Tapatalk
Bigjim1488 said:
Has anyone else had this issue with the airave? Whenever I get back into my house I guess my photon doesn't connect to the airave correctly and I get silent calls until I reboot my phone. Anyone else? I didn't have this issue with my 3d.
Airave is kinda old, that could be it.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
I used to have that problem before the OTA update came out, but it happened regardless of whether I was by my Airave or not. The OTA seems to have solved it though
Bigjim1488 said:
Has anyone else had this issue with the airave? Whenever I get back into my house I guess my photon doesn't connect to the airave correctly and I get silent calls until I reboot my phone. Anyone else? I didn't have this issue with my 3d.
Airave is kinda old, that could be it.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
I was given an Airvana by Sprint a few months ago. I had major issues with the Nexus s 4G and the Airvana. It would work fine for a bit, then it would block all my incoming and out going calls. Sometimes it would miss route them as well. It was only on the Nexus and when I unplugged the Airvana everything would work again. That's actually how I got the Photon. Sprint sent it to me to address the issue. You problems seem more like a well known bug with the phone that was addressed with the OTA.
I don't seem to be having any problems with the Photon and Airave at all. I have one of the older models that's voice only, I wish I had the one that's data as well.
I have the new airave and my photon connects just fine. I also don't have that issue anymore either where my evo would send the same message a million times to the same person...lol...not one blip with the mopho and airave!
Sent from my MoPho using XDA Premium.
I have the newer airave, and the Photon connects just fine. I do have problems with the airave fairly often. Probably once or twice a week I have to reboot the airave because it loses its internet connection, or stops putting calls through. The issue is always the airave, though, not the phone.
I guess I will have to see if sprint will send me a newer one. I have had this one for two years now and I really can't live without it. The reception in my house is terrible and if sprint didn't send me one of these for free I would have dropped my service........no point in having a carrier that you can only use outside your house
My parents have one of the new airraves and my photon connects but all I get is weird alien like sounds sounds like a scrambled code or something it is really weird and annoying if anyone knows of a fix please let me know
Sent from my MB855 using XDA App
Bigjim1488 said:
Has anyone else had this issue with the airave? Whenever I get back into my house I guess my photon doesn't connect to the airave correctly and I get silent calls until I reboot my phone. Anyone else? I didn't have this issue with my 3d.
Airave is kinda old, that could be it.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
I have airave airvana and i get silent calls all the time. Had to unplug airave.
OK Guys here's the issue. I spoke with Airwave support and he had me do a test:
http://voiptest.packet8.net/
Click the Start Test Button. When it's finished the thing you are looking for the most is Jitter Rate( you will have 5 different catagories). If your Jitter Rate is High (mine was 65ms) you WILL NOT be able to maintain a VOIP call thru the Airwave (it has to be no higher than 5ms). The Sprint Rep told me to call my ISP (TWC) and have them Clean and Flush my line, I did, and my Jitter Rate went down to 1.1ms and my Airwave works GREAT. Have your lines Cleaned and Flushed and rerun the test and you WILL see a difference.
So I figured out my problem I forgot I had set my voice codac to 4GV and the air rave doesn't support that. switched it back to evrc-b and all is well.
Sent from my MB855 using XDA App
ghodzilla5150 said:
OK Guys here's the issue. I spoke with Airwave support and he had me do a test:
http://voiptest.packet8.net/
Click the Start Test Button. When it's finished the thing you are looking for the most is Jitter Rate( you will have 5 different catagories). If your Jitter Rate is High (mine was 65ms) you WILL NOT be able to maintain a VOIP call thru the Airwave (it has to be no higher than 5ms). The Sprint Rep told me to call my ISP (TWC) and have them Clean and Flush my line, I did, and my Jitter Rate went down to 1.1ms and my Airwave works GREAT. Have your lines Cleaned and Flushed and rerun the test and you WILL see a difference.
Click to expand...
Click to collapse
I have this same issue - where 50% of my incoming calls never reach me and go straight to voicemail. Other times, I would not be able to call out and other times it would go without doing anything... same goes for incoming.
Spent hours back and forth with sprint tech, with battery pulls, profile updates, power cycling of airvana and phone and reseting airvana and photon - tried switching to "sprint only" / "any cdma" / "automatic" - nothing particularly gave better results.
After the voip test, everything was in range except for the jitter - mine was between 70-300ms and average in between that which you are right about VOIP not being optimal.
I tried explaining this to comcast (my isp) and they had no idea, saving signal, upstream/downstream is good..
*** How or what do you need to do to have them [the isp] "clean / flush" the line? Is there a better technical term to convey to them?
Is this something they do over the phone from their network side? I have a comcast tech coming in, and from what a sprint tech told me - there's a possibility that the cable lines to my apartment may have not been shielded well creating RF/radio frequency interference, which results in high jitter - so it, according to him is a physical issue - not sure.
I have an old samsung voice only airave - and this works perfect without changing anything...
Would love to get the 3g data back on the airvana and have this work.
This is a legit problem. Been dealing with it for about 4 months now. Started out where the everything works great after a power cycle. Then at some point the Nexus S 4G I had would stop working with the Airvana (the new Airave). All my calls in and out were blocked and other times my calls were incorrectly routed.
I was really weird because at times the Airvana would completely kill the radio on the Nexus. I would just have the signal bars with the little x over top. Other times I would roam on Verizon and no one was able to force me back to the Sprint Network.
I actually lost a some business due to my phone not receiving the calls.
However, as soon as I unplugged the Airvan everything went right back to normal.
My wife's Epic worked just fine as did the Hero, Evo and Evo 3D. Thats actually how I got the photon for free. I had just bought the Nexus outright and was not able to return it. My problems were so well documented that a manager called me one day and offered me an Evo 3D as a way of addressing the problem.
After 2 bad Evo 3D's they sent me the Photon. Everything worked well until last weekend. I had to kill the Airvana once again. My calls were getting blocked.
Apparently what has happened is that Sprint pushed an update to the Airvana and some customers will need to have the device reset on Sprints end. I tried resting it on my end and it's a no go. I just have had to much on my plate to call them again and deal with the scripted support.
Honestly, the radio in the Photon is way better then either of the Samsungs and even the Evo 3D. So it hasn't been a huge rush.
Hope this helps. Also thanks for writing this because I thought I was going crazy as Sprint claims to have never seen these problems before.
I even had a Sprint rep tell me he was going to "boost" the signal to my phone so I got better reception in my area.
It's definitely as I agree an airvana issue - as yourself - as soon as I turn off the airvana... everything works fine... or of out of the airvana network.
What was worse is that the trroubleshooting timing - when calling/testing with tech, it works... best was that they thought everything was great when they called to test incoming, A few minutes to wrap up, I asked if they could dial it once more... straight to voicemail I really wish it did get corrected
The 1st gen samsung hasn't given me any problems thus far which makes me wonder what the issue really is... I was given a replacement 2nd gen airvana because we thought the other airvana was going bad or malfunctioned somehow.
The airvana apparently has an "access menu" which I haven't looked at : the ip they gave me : 192.168.17.2 username : admin / password : admin (or blank). They said there weren't many things to change (I can't confirm this) from there ... i,e time zone/date
This ISP clean/flush looks interesting, but I don't know what that entails or how to convey the message to them to do it.
I lost a lot of calls which should have went through - I know that feeling. It's quite a bit of time to reconvey the issues over and over going through the same steps over and over (regardless of previous call log notes) - just hoping, that this time it will work....
Is it maybe a high jitter issue??
If your Jitter Rate is too high, it will NOT keep a constant VOIP call (that's what we are using with the Airwave, VOIP). I just tell TWC to Clean/FLush my line and they know what to do. You can also tell them to Reset your Modem. This all happens on Their end. The can Reset your Modem over their line.
same Issue
I had the same issue, i upgraded from the epic to the motorola photon, when i got home all my calls were blocked and i had no air rave coverage.*99 didnt go through. I went through the settings and did a manuel update to the latest motorola software to address the silent call issue. Then i logged into my sprint account online, and reconfigured the settings to my air rave(its the new air rave airvanna) After i restricted my airvanna air rave to only my cell phone number and my wifes, i turned off my phone and turned it on, and all my problems were solved. If anyone needs help finding the settings for your air rave, let me know, it took me some time to find it, i could help you locate it. It appears we all have indifferent issues with this phone. My problems been fixed since the 23rd of august. Still no issues today.
Right thanks - I had them "reset" and send a "refresh" signal to my modem - but that didn't do anything to the jitter unfortunately... still in the ~70ms range jitter. Is that what you mean then by "clean / flush" ?
Regarding the mention of restricting the your phone number on the website, yes this was a bit tricky to get to - I initially did use this, but removed my #.
I think my apartment complex has so many airvanas around because wherever I walk around to the outside, I am at times connected when I know it shouldn't...
Apparently - if anyone else comes to your residence that has a sprint connection, their sprint phones don't work - the old airave samsung was able to add multiple phone numbers in that situation. I forgot how long it took for the sprint network to accept the guests' phone #'s - but how much can we ask for?
I am not sure if you could add more "sprint" lines to the account if guests arrived with sprint phones to have it work...
Just got my Airave last night the thing is just disgusting! I love ti and couldn't ask for better. Got my own tower in my house. Still connected down the street too. Frickin sweet. No silent calls here, will respond with more use too.
-DJ
Just got my phone and it worked fine for the first day. For the past two days however, I have been unable to make or receive calls/text messages. 3g and 1x work fine but everytime I dial out, I get: "we are unable to complete your call, please try again"
I am rooted via revolutionary and running the stock deodexed rom and latest radio. I tested cdma connectivity after rooting and everything worked fine. I've had sprint reset my profile, updated prl etc...
I've been told by CS that there is an outage affecting certain users, anyone else not able to use the phone part of your smartphone?
If you are getting an "Error 16" then you have to call Sprint and have them fix it, takes 5 minutes. They don't care.
However if you are on the East Coast you might be experiencing the same crap I am. Most Sprint towers are still down. I have had to use the Alltell PRL to get decent speed....I figure WTH not, I'm already roaming 100% of the time, I might as well get decent speed.
daneurysm said:
If you are getting an "Error 16" then you have to call Sprint and have them fix it, takes 5 minutes. They don't care.
However if you are on the East Coast you might be experiencing the same crap I am. Most Sprint towers are still down. I have had to use the Alltell PRL to get decent speed....I figure WTH not, I'm already roaming 100% of the time, I might as well get decent speed.
Click to expand...
Click to collapse
Where would I see this error 16? I've called sprint and had them reprovision my account twice and just about everything else I can think of. Im located in hawaii and my roommates og evo works fine.
Not an error 16 but even with my airave im roaming? yeah... outtage...
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Lately I have noticed my phone going into roaming mode a lot. Sitting in my house today it went into roam. I live in town and get a good 4G signal when I turn it on. I should not be roaming. Here and there running around town I go into roaming too. If I try to make a call it tells me welcome to Verizon this account can not ne authenticated. it won't let me make a call. Now I know we roam on verizons towers but if i can't make a call when i actually need to because I am roaming I am gonna be pissed. If i try to send a text it gives me an error 64 as well. I have been rooted for about a month or longer and just started having problems.
My thought is it is some sort of security thing sprint has been doing to crack down on rooted devices that are forced to roam. I am not forcing mine into roam and have no intention to. Is there any suggestions I can try to keep from going into roam so much.
I live around Austin tx. Anyone else notice more roaming lately?
Sent from my PG86100 using XDA App
I had the same exact problem and searched for a solution for months. Call sprint, ignore everything they try to do to fix it and request an hlr refresh (or reload, reset, etc....). It's the only solution I found and is very easy provided you get the right rep. I've also heard its easier doing this over sprint chat on their website. Hope this helps!
There is a thread in the general section that has a few prls up. I had to switch mine a few times to get good signal back.
I know there are a few towers down in my area because of the storm. Sprint is taking their sweet time fixing them as well. I called a few times to submit a ticket and they always say they will call me back within 24-72 hours and never do. I always have to call back. Really bad customer service if you ask me! Sprint's network right now is a joke! It can't compare to Verizon or ATT in my area.
oohaylima said:
There is a thread in the general section that has a few prls up. I had to switch mine a few times to get good signal back.
Click to expand...
Click to collapse
What area are u in and which one worked best for u
Sent from my PG86100 using XDA App
I live in Fort Leonard Wood. 1115 worked best for me.
I have been having this problem as well. After about 2 weeks of constant phone calls to Sprint, multiple CHLR resets, and even an exhange, the new 1 does the same thing. It will work for a few days, then I'll go into a roaming area, and whamo, the Verizon lady tells me my phone cannot be authenticated! Funny thing is my original 4G, never roams in these areas, and when it does, it roams perfectly well...
So here goes...
I'm on travel for the holidays, and we arrive in a backwoods Vermont town, then suddenly I lose cell signal, no biggie, this is usually expected in Vermont, but since we bring along our Wilson 45dbm cell booster, I usually regain my signal to full bars as soon as we turn it on (no matter where we are). I just thought that maybe the tower in the area was down from the snow we just got.
I thought nothing of it, until when we arrived at out destination and then I notice my phone still had no signal. At my suggestion a few years ago, I convinced the family we visited to invest in a Wilson home booster, which my wife currently has no problem picking up a signal from.
So this got me thinking, well maybe my PRL file was outdated/updated and the cell tower is not in my list. So I notice my wife has version 60690, and I had version 21090. Wow this must be really really old I thought, so I followed instructions using QPST and upgraded mine to the same version as my wife's. Still nothing, no signal what-so-ever.
Then I noticed that Sprint is upgrading their network and this meant that the newest version numbers were in the range of what I had on my phone originally, and now I think someone said 21092 is the absolute latest for the Evo 3D. So with this said, maybe I need to update my PRL to 21092, problem is I can't without a signal, and so far no one has posted it on any site yet. Anyone have the latest PRL file that I could try?
Then today I got to thinking that maybe the problem started at the car ride with the booster. Did my booster output too much power that it fried my radio? The car booster uses a stick-on antenna, not the direct to phone connector cable, so I don't see how it could have over saturated the radio, but now I am second guessing that notion. Or maybe, could my phone have a different radio than my wife's phone? I'm sure my evo3d was working the last time I was here in Vermont, but I'm not 100% certain it was the same phone.
So with this said, how can someone verify that the radio is shot? I've tried entering field trial mode using ##33284# to see if there is even a signal dbm level being reported, which it seems to see something because it does fluctuate.
Attached are some photos. Thanks!
For prls on the 3d I run the sprint corporate prls. I believe the latest we have on xda is 12126. The benefit of these is that when roaming it gives full 3g on the Verizon network as opposed to your 21xxx prl that only gives 1x. These prls I believe are distributed to customers in corporate accounts with sprint. I've been running 12124 with no problem s, I just haven't updated yet. I'm pretty sure there's a thread in the general section on this. I'm on tapatalk or I'd link you. Anyways, I doubt you fried anything... I've loaded the prl you did before and it didn't pull any signal for me either on my 3d... I have no clue what the difference is though.
Sent from my PG86100
1branchonthevine said:
So here goes...
Click to expand...
Click to collapse
I have no idea what your problem is but just wanted to say that I love the title of your thread. Sounds like a country and western song to me.
ramjet73
I forgot to add that this is a US Cellular tower that shows up as roaming on the sprint network. It's my understanding that prl files list roaming towers only, so it would seem to imply that something is wrong with the prl file. But then why does my wife's phone work when mine doesn't using the same prl. Anyhow, maybe I will try a corporate prl for giggles, just to see if it still even works. Thanks for the suggestion, I will try it soon and let you know!
Oh and thanks for the country song title idea, I should have had more fun with that one!
Sent from my PG86100 using xda app-developers app
my 3d is inferior to my 4G
Sent from my PC36100 using xda app-developers app
Thanks p3tr0s, I think I used the corporate PRL you suggested and after QPST rebooted the phone, I still had no signal. But somewhere in between going into my ICS >Settings>Mobile networks and toggling all the Domestic/Roaming/Guards and setting them back (even though this still did not give me signal), then going into >Settings>Usage and toggling Mobile Network suddenly my phone finally connect to the cell tower. Immediately after a good connection, I did a PRL update (in >Settings>System updates), and now it is using the latest 21092 PRL and it is still working just fine, so now I'm totally confused. I'm thinking that the issue was resolved somehow with the toggles. Even though I had tried toggling the Usage mobile setting and a couple of the data options on previous PRL's, I hadn't tried toggling all of them in the Mobile networks area as I did this time. But, then again, this is the first time I have gotten a signal, so maybe the combination of the corporate PRL worked is some weird way. Thanks!