Related
My PRL is 60668. When I click update PRL or update Profile, it says "Checking for PRL/Profile update", then says "PRL/Profile could not be updated. Please try again later. If the problem persists, you may need to contact Customer Service. Error code:1012". This happened to me a couple of ROMs ago, any suggestions as to what this is about?
bump????????????
OMG I am having the same problems today. I leep getting the exact same response when I try to do my profile update. I spent 4 hours on the phone with Sprint today. They had me do a hard reset and now my phone is useless. PLEASE PLEASE PLEASE someone help us!
lillygirl7 said:
OMG I am having the same problems today. I leep getting the exact same response when I try to do my profile update. I spent 4 hours on the phone with Sprint today. They had me do a hard reset and now my phone is useless. PLEASE PLEASE PLEASE someone help us!
Click to expand...
Click to collapse
Through research all I can see is the hard reset route, and CDMA workshop. It just seems like no one cares honestly
I've done at least 5 hard resets today and nothing. It just keeps saying "searching for network" I really didn't want to waste my entire day doing this. ugh. I know it must be somewhere in the settings, but Sprint peeps don't seem to have a clue either.
lillygirl7 said:
I've done at least 5 hard resets today and nothing. It just keeps saying "searching for network" I really didn't want to waste my entire day doing this. ugh. I know it must be somewhere in the settings, but Sprint peeps don't seem to have a clue either.
Click to expand...
Click to collapse
No it's not somewhere in the settings, that's the problem. You went to settings, system upgrade, then update prl and got the same error as me right?
If you have another phone, go online and switch over to it, then switch back, and it will be fixed. That or sprint themselves have some other option. The only way to fix it yourself is pretty complicated
We did all of that. The Sprint rep switched phones and everything and still nothing. It's just not finding the network. LAME!!!
lillygirl7 said:
We did all of that. The Sprint rep switched phones and everything and still nothing. It's just not finding the network. LAME!!!
Click to expand...
Click to collapse
Oh wow that sucks IDK, I'd call em back and complain, demand free service
UPDATE!!!! I thought wth I'll give Sprint another call and see if I can get a different advanced tech that might have some more ideas and get me back up and running. Well after about 2 minutes she asks for my ESN number to validate and well......IT WAS INCORRECT! She updated it to the correct one and voile it works now! My suggestion is to call them and verify that they have the correct ESN. Good luck.
There have been issues with CDMA activation/provisioning all day today. This would include data profile issues and possible PRL updates as well. Try again this weekend.
lillygirl7 said:
UPDATE!!!! I thought wth I'll give Sprint another call and see if I can get a different advanced tech that might have some more ideas and get me back up and running. Well after about 2 minutes she asks for my ESN number to validate and well......IT WAS INCORRECT! She updated it to the correct one and voile it works now! My suggestion is to call them and verify that they have the correct ESN. Good luck.
Click to expand...
Click to collapse
I will, thanks for the update, and glad your problem was fixed. This seems like a possible problem, considering all of the trouble I had switching the lines over, along with selling my old phone, activating old phone, then dummy phone, then evo, then switched evo.. I'll look into it.
mactruc said:
There have been issues with CDMA activation/provisioning all day today. This would include data profile issues and possible PRL updates as well. Try again this weekend.
Click to expand...
Click to collapse
Ha bro this issue has been happening for a long time, check the dates
I'm having this same problem. Just did my first root and installed Fresh Evo 3.1.0.1, with the recommended newest radio/wimax. Everything but the phone works great. I can still dial and receive calls at my normal number, showing good reception, but there is tons of hiss and my voice almost never makes it to the other phone.
Tried to Update Profile and Update PRL, and both gave me Error 1012. Sprint's website is down right now (4 AM Sunday morning), so maybe the network is simply not currently serving updates.
However, if it's something that can be fixed, I'd be grateful if anyone has an idea.
I could be wrong but if i recall error 1012 is a Sprint data/vision username/password error and is correctable with a call to tier 2 tech support.
I cant remember for certain tho, But I believe thats what that is, I know i've seen it quite a few times before.
Im now having this issue. What has been the cause for most of you? If you found out.
Sent From My HTC Evo 4G Using Tapa Talk Pro!
I just bought a new evo for my wife off of ebay last week. I got it activated by sprint everything was good. two days after that she told me every call was coming in as unknown. I rooted it using unrevoked and installed myns rls5 new radio all that good stuff. I then checked the caller id and still doing the same thing. I called sprint to make sure there was not a problem with my service they checked everything was good they even reset my service and caller id still doesn't work. Has anyone had this problem or know of a fix? please help.
zombietxff said:
I just bought a new evo for my wife off of ebay last week. I got it activated by sprint everything was good. two days after that she told me every call was coming in as unknown. I rooted it using unrevoked and installed myns rls5 new radio all that good stuff. I then checked the caller id and still doing the same thing. I called sprint to make sure there was not a problem with my service they checked everything was good they even reset my service and caller id still doesn't work. Has anyone had this problem or know of a fix? please help.
Click to expand...
Click to collapse
That's odd. It's happening all the time, on every call? That happens to me once in a great while, but only when it's call waiting (I'm already on the phone, then get a second call, it usually doesn't show the caller ID, but for some reason, sometimes it does) I dont know what causes, and I've never seen it reported to happen, other than when it's call waiting. So the caller id was working at first, then stopped? Then you rooted and flashed RLS5, and the same thing? That must be annoying, and wish I had a fix for ya. Are all of the contacts stored as a 10 digit number? area code + regular number? Not sure if that matters or not, but just throwing off ideas. Hope you get it figured out.
ya does it all the time for every call even for numbers stored in contacts as 10 digit numbers.
just root it and flash a custom rom rather than dealing with sprint on this one
That's what i did rooted using unrevoked 3.21 flashed myns rls5 hoping that would work and still same problem. I don't understand it had my other evo since a came out and never had anything like this happen even flashing unstable roms
zombietxff said:
ya does it all the time for every call even for numbers stored in contacts as 10 digit numbers.
Click to expand...
Click to collapse
Thats extremely odd. You are the first person I've seen report this, and I've never had it happen, so unfortunately don't have or know of a fix. Did you or your wife make any changes to the phone prior to this happening?
EDIT:
I actually just googled this issue for you, and it seems you're not the only one. I've never seen it mentioned here in XDA before, but I guess your problem is somewhat known. I didn't look too deeply in these threads, but a couple people made some suggestions that they said worked. Take a look, a guy suggested removing the - from the phone number (do 1112223333 as opposed to 111-222-3333), and said that worked for him. Crazy, if that's the case, but who knows? And now that I've read that, I checked my contacts, and all are stored as google contacts, and have no -'s in the numbers, no separators. Would be a PITA, but try it, see if it works. Change your saved number in your wifes phone, so there are no -'s, then call her and see if it works. If it does, sync all contacts to google, edit them on the computer, then sync back. That would be crazy if call ID doesnt work with -'s in the number.
http://forum.androidcentral.com/htc-evo-4g/44794-caller-id-not-working.html
http://community.htc.com/na/htc-forums/android/f/94/t/6907.aspx
cool i will try this as soon as i get home. thank you k2buckley hope it works ill let you know if it does
zombietxff said:
cool i will try this as soon as i get home. thank you k2buckley hope it works ill let you know if it does
Click to expand...
Click to collapse
You're welcome. I hope it works as well, it's always good to figure things out! Let me know if that actually does the trick! If so, I have never seen such a thing, such a little nit-picky thing on someone's part (google? htc?)
EDIT:
Well, I've been messing around with my phone, trying to reproduce your problem. I can't do it. I tried saving my work phone number as 702-591-6##1. Called the evo from my work phone. Caller id worked. I saved it as a phone contact, instead of google contact. Caller id still worked. I saved it as something other than a 'mobile' contact, such as work. Caller ID still worked. The only way I could force caller id NOT to work, was if I didn't save the full 10 digit number, if it was just the 7 digit number, without area code it did not work. So I don't know how helpful the other suggestion will be. Still try it, as you've got nothing to lose. Im perplexed.
Damn still didn't work k2buckley I've tried entering the my number all kinds of different ways and still same problem even after a factory reset
Sent from my PC36100 using XDA App
zombietxff said:
Damn still didn't work k2buckley I've tried entering the my number all kinds of different ways and still same problem even after a factory reset
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yea man, I don't know if you noticed, but I edited my last post. I couldn't reproduce your issue no matter what I tried. I'm lost on this one, out of ideas at the moment. Good luck, I hope you figure it out. Maybe take it to sprint?
Sent from my PC36100 using XDA App
k2buckley said:
Yea man, I don't know if you noticed, but I edited my last post. I couldn't reproduce your issue no matter what I tried. I'm lost on this one, out of ideas at the moment. Good luck, I hope you figure it out. Maybe take it to sprint?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I tried doing some research as well...and couldn't find anything. I'd take it to Sprint [unrooted of course] And say it happened after you updated your PRL and installed the newest OTA.
cool thank you for your help unrooting taking it to sprint tomorrow. ill post the outcome it might be helpfull to someone later. so frustrating not to be able to fix it myself lol
zombietxff said:
cool thank you for your help unrooting taking it to sprint tomorrow. ill post the outcome it might be helpfull to someone later. so frustrating not to be able to fix it myself lol
Click to expand...
Click to collapse
No problem, but that was a rather uncommon problem though. They should at least exchange it for you.
Called tech support. They've no idea what it is.
Went into Sprint and had techs assess it. No idea. Manager has never seen code.
Switched ROMs from CM 7.0.2.1 to MikG to see if ROM was affecting it. Nope.
Unable to send/receive SMS and make/receive calls. Data fully functional in all aspects (1x, 3G, 4G, GPS, WiFi).
Intermittent issues yesterday. Can't do any SMS or calling period today.
Any idea?
totalanonymity said:
Called tech support. They've no idea what it is.
Went into Sprint and had techs assess it. No idea. Manager has never seen code.
Switched ROMs from CM 7.0.2.1 to MikG to see if ROM was affecting it. Nope.
Unable to send/receive SMS and make/receive calls. Data fully functional in all aspects (1x, 3G, 4G, GPS, WiFi).
Intermittent issues yesterday. Can't do any SMS or calling period today.
Any idea?
Click to expand...
Click to collapse
What were you doing prior to this happening?
Sent from my PC36100 using XDA App
I was doing nothing prior to it. Business as usual. Same locations I'm always at, same amount of text messaging, same people I contact as usual. It came out of nowhere and came to stay, sadly.
totalanonymity said:
I was doing nothing prior to it. Business as usual. Same locations I'm always at, same amount of text messaging, same people I contact as usual. It came out of nowhere and came to stay, sadly.
Click to expand...
Click to collapse
You say you switched ROMs? So I would assume you wiped everything.
Which would be
System/Data
Dalvik
Cache
Boot
Android Secure
And everything else besides ext partition and your SD right?
Now let's trouble shoot this problem. Have you tried installing an OTA ROM? If not, wipe your phone completely and install an OTA rooted Rom.
As you are doing this, I will research on this problem.
Sent from my PC36100 using XDA App
Also have you attempted reprogramming your phone? I remember someone having this problem a long time ago and someone suggested dialing *228
Found the article. The number is indeed *228, but this was for the Droid Eris, so a different carrier. But dialing *228 fixed the problem.
Ignore the previously mentioned. It seems it may be for Verizon only.
EDIT#2
Good god I just read you can't make phone calls. So before we start messing with these codes, have you updated radios at all? If not, try to do so after doing the first step I requested you to do.
EDIT#3
This seems to have to do with your phones provisioning. Try provisioning your phone, it seems that has worked for others whom have had the problem.
To do this you will need to call sprint to do the provisioning process. So if wiping your phone does not work along with reinstalling a rooted OTA, try this.
Sent from my PC36100 using XDA App
@DDiaz007:
I had not installed an OTA ROM and I had read elsewhere about the *228 code and was quite sad when it was for Verizon only, considering those people were having the precise errors I was having.
I ended up calling into Advanced Tech at Sprint as per someone's advice in the IRC for Evo. Forgot the guy's name, wish I could give him credit here.
Solution was:
##231465#
Edit Mode
MDN: Should be current phone number. If not, correct it.
MSID: Should be number AT will tell you you should have. If not, correct it to such. If it already is, change number to some other 10-digit number, commit modifications. Reenter this edit mode by same means and change back to number AT said it should be, commit modifications. It required a reboot for me to acquire service again after changing that number and changing it back, but both SMS and voice now work flawlessly for me. Hell, maybe faster than before!
Thank you for your continued persistence in helping me solve my problem, though. I really appreciate it.
totalanonymity said:
@DDiaz007:
I had not installed an OTA ROM and I had read elsewhere about the *228 code and was quite sad when it was for Verizon only, considering those people were having the precise errors I was having.
I ended up calling into Advanced Tech at Sprint as per someone's advice in the IRC for Evo. Forgot the guy's name, wish I could give him credit here.
Solution was:
##231465#
Edit Mode
MDN: Should be current phone number. If not, correct it.
MSID: Should be number AT will tell you you should have. If not, correct it to such. If it already is, change number to some other 10-digit number, commit modifications. Reenter this edit mode by same means and change back to number AT said it should be, commit modifications. It required a reboot for me to acquire service again after changing that number and changing it back, but both SMS and voice now work flawlessly for me. Hell, maybe faster than before!
Thank you for your continued persistence in helping me solve my problem, though. I really appreciate it.
Click to expand...
Click to collapse
Man that is good to know. I was going to get ready and post a bunch of programming codes for the Evo, but you solved your problem. Very good!
Sent from my PC36100 using XDA App
i am still having this issue and the mdn and msid are fine. anybody find anything else about this? this only start happening to me when i flashed bliss. other roms are fine.
totalanonymity said:
@DDiaz007:
I had not installed an OTA ROM and I had read elsewhere about the *228 code and was quite sad when it was for Verizon only, considering those people were having the precise errors I was having.
I ended up calling into Advanced Tech at Sprint as per someone's advice in the IRC for Evo. Forgot the guy's name, wish I could give him credit here.
Solution was:
##231465#
Edit Mode
MDN: Should be current phone number. If not, correct it.
MSID: Should be number AT will tell you you should have. If not, correct it to such. If it already is, change number to some other 10-digit number, commit modifications. Reenter this edit mode by same means and change back to number AT said it should be, commit modifications. It required a reboot for me to acquire service again after changing that number and changing it back, but both SMS and voice now work flawlessly for me. Hell, maybe faster than before!
Thank you for your continued persistence in helping me solve my problem, though. I really appreciate it.
Click to expand...
Click to collapse
I been having this same issue for a few days already. What do you mean by Edit mode?
Hello I am that same problem on my EVO 4G but all things work and data work Its just keep saying SMS ERROR something 34 and code 2 and this occured after i downloaded the blaze beta 4 rom. I am new to this phone tech stuff and do not want to make things worst on phone. I will be waiting for someones help and thanks...
I got the same problem about 2 weeks ago. Short sms sends good, but then sms length not suited in one message, this cause error. Solution i still has not found.
I tried to get into service mode by code? wrote upper, but no menu appeared.
Bump for a solution for this problem...
I am currently running the fresh rom 4.3.3 by flipz and constantly receiving this message. I have tried resetting the phone...doing a full wipe of the phone and doing a clean install of the rom.
This problem Also occured on the Team Nocturnal's 4.67 OTA Rom with the updated radios and updated OTA kernel...I have recently gotten an Airave howver, this problem was happening about 2 weeks prior to getting my Airave.
Any help would be greatly appreciated...
I had LOS between 2-3 times per day since I got my my E4GT on launch day. About two weeks ago I followed the instructions here http://forum.xda-developers.com/showthread.php?t=1281287 by flashing SPH-D710_Zedomax_EpicTouchKernelStock-v1.tar first and then flashing acs-eg30-stock-kernel-pulled.tar because I wanted the stock kernel but rooted. Since I did that, no more LOS issues. Not once.
I have no idea why this might have worked and if it will work for anyone else, but I thought I'd share just in case it is useful to anyone.
Good Luck.
I started having LOS again. No changes to my phone. I guess this wasn't the ultimate fix I had hoped for.
probation said:
I started having LOS again. No changes to my phone. I guess this wasn't the ultimate fix I had hoped for.
Click to expand...
Click to collapse
Try and update profile?
You get los regardless on stock or rooted? Los. Happens when your in a low signal area and when thee phone attempts to roam, you get los.
Sent from my SPH-D710 using xda premium
expertzero1 said:
You get los regardless on stock or rooted? Los. Happens when your in a low signal area and when thee phone attempts to roam, you get los.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
then why do ppl get LOS when they are connected to an airrave? (myself included though i havent had one in recent days)
LOS is a samsung problem, they are aware of it and most likely already have a fix, but are waiting to roll it out.
Bielinsk said:
LOS is a samsung problem, they are aware of it and most likely already have a fix, but are waiting to roll it out.
Click to expand...
Click to collapse
Those are rumors.
nabbed said:
Those are rumors.
Click to expand...
Click to collapse
Those are facts. I have been in touch with Sprint techs for the past 3 weeks, this is an acknowledged problem.
Bielinsk said:
Those are facts. I have been in touch with Sprint techs for the past 3 weeks, this is an acknowledged problem.
Click to expand...
Click to collapse
Those remain rumors until something official comes from Sprint. Talking to techs is not an official channel by which Sprint makes announcements. Right now, this update may or may not happen, at an indeterminate time.
U might want to update the name of the thread, maybe add a "nevermind" in the end.
Sent from my SPH-D710 using xda premium
The Airrave issue is not actual LOS. LOS is when you lose all services IE. Data, and Calls. With actual LoS You have a circle with a line through it and you might as well be in airplane mode. Dropping a call or not being able to send a text message isn't LOS, although it is an issue. On the Airrave you may be unable to send text messages, but may receive them and can make calls therefore its not true LOS. For me I updated prl, restarted phone, restarted Airrave and the issue was gone. It has popped up on occasion from time to time, but for the most part this resolved the issue. As for the best solution for actual LOS - LoSt Kernel/the tasker set up which can be found here in the general forum. This will not guarantee that you will have service everywhere you go and it wont guarantee that you will never drop a call, it will however significantly lower how frequent you get actual LoS. The tasker set up will make sure that as soon as you get true LoS your phone resets so you dont have to worry about missing anything.
ayman86 said:
then why do ppl get LOS when they are connected to an airrave? (myself included though i havent had one in recent days)
Click to expand...
Click to collapse
vikramjatt11 said:
U might want to update the name of the thread, maybe add a "nevermind" in the end.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha yeah I clicked this thread thinking "oh something new regarding LOS?".
This is definitely a Samsung issue, and something about the source code they released seems to exasperate the issue. Other then the auto reboot scripts that are being worked on, nothing is going to fix this until we see an update get pushed out.
Devi0124 said:
The Airrave issue is not actual LOS. LOS is when you lose all services IE. Data, and Calls. With actual LoS You have a circle with a line through it and you might as well be in airplane mode. Dropping a call or not being able to send a text message isn't LOS, although it is an issue. On the Airrave you may be unable to send text messages, but may receive them and can make calls therefore its not true LOS. For me I updated prl, restarted phone, restarted Airrave and the issue was gone. It has popped up on occasion from time to time, but for the most part this resolved the issue. As for the best solution for actual LOS - LoSt Kernel/the tasker set up which can be found here in the general forum. This will not guarantee that you will have service everywhere you go and it wont guarantee that you will never drop a call, it will however significantly lower how frequent you get actual LoS. The tasker set up will make sure that as soon as you get true LoS your phone resets so you dont have to worry about missing anything.
Click to expand...
Click to collapse
from my experiences, ive lost data and calls. i dont receive any texts when it happens. im already on the lostkernel. it helps but then again i dont have LOS as frequent as others. as i said earlier, i dont get it that often.
I apologize in advance if this is a thread somewhere I couldn't find it.
I was recently using CM9 alpha3 on my E4GT, and last night suddenly I wasn't able to make calls. It says "we're sorry but we can't complete your call right now" or it just instantly hangs up. I thought it may have been an issue with the rom or modem, so I went back to Calkulin's GB EL29 ROM. Same issue, even after resetting PRL and profile multiple times with phone restarts. I can send and receive texts, and I can receive calls, but I can't make calls. Another thing to note is I use an Airrave in this house, I tried resetting that as well, and dialing *99 which is supposed to also refresh or reset it. None of these tactics have worked and I was wondering what else I could try. Thanks again in advance!
Robots88 said:
I apologize in advance if this is a thread somewhere I couldn't find it.
I was recently using CM9 alpha3 on my E4GT, and last night suddenly I wasn't able to make calls. It says "we're sorry but we can't complete your call right now" or it just instantly hangs up. I thought it may have been an issue with the rom or modem, so I went back to Calkulin's GB EL29 ROM. Same issue, even after resetting PRL and profile multiple times with phone restarts. I can send and receive texts, and I can receive calls, but I can't make calls. Another thing to note is I use an Airrave in this house, I tried resetting that as well, and dialing *99 which is supposed to also refresh or reset it. None of these tactics have worked and I was wondering what else I could try. Thanks again in advance!
Click to expand...
Click to collapse
Maybe you might be hotlined from Sprint. Sounds silly but is you bill paid?
Sent from my SPH-D710 using xda premium
possibly Blacklisted
expanding on the previous post..
Did you get the phone direct from SPRINT. or via ebay or at a pub?
Bills paid?
are you the only registered owner of the handset?
people will sell you a phone, then after a little bit of time passes. they register the phone as LOST/STOLEN/DAMAGED the network Blacklists it and provides the fraudster with a shiny new handset.
you end up out of pocket without a working phone.
its an increasingly popular fraud technique I'm afraid.
Silly question but it needs to be asked, are you sure it wasn't something with the number you were calling? Did you try calling several number?
Airrave services are having issues. Power it off for a day.
Sent from my SPH-D710 using Tapatalk 2
The bill is current, I have called multiple numbers, both on the sprint network and others neither has worked. I have other family members in the household on the same plan using the airrave and they are able to make calls. I bought the phone directly from sprint brand new from the store with my 2 year contract.
Why don't you use sfhub's one-click EL29, get yourself back to simple stock rooted and see if it clears up the issue. It's always my fall back whenever something goes awry.
http://forum.xda-developers.com/showthread.php?t=1433101
Esoteric68 said:
Why don't you use sfhub's one-click EL29, get yourself back to simple stock rooted and see if it clears up the issue. It's always my fall back whenever something goes awry.
http://forum.xda-developers.com/showthread.php?t=1433101
Click to expand...
Click to collapse
I did actually use that right before I flashed Calk's E4GT rom and I had no luck with it either Probably should've mentioned that.
Robots88 said:
I did actually use that right before I flashed Calk's E4GT rom and I had no luck with it either Probably should've mentioned that.
Click to expand...
Click to collapse
Don't reflash Calkulin's ROM until you've been able to recover your voice calling services. Both CM9 and Calkulin's ROM are custom, so maybe that's where the problem is coming from. You need to get back as close to stock as possible then see if the problem persists.
Go back to EL29 (plain stock or stock-rooted), see if everything is working then you'll know if maybe it's something in the flashing process that is knocking out the voice calling.
I'm also having the exact same issue with my airave. If I unplug it I'm able to make calls without a problem. So as someone else posted I believe the airaves are having issues today. But I am on the stock FD26 ICS if anyone else is having the problem and thinks it has anything to do with the leak.
Compusmurf said:
Airrave services are having issues. Power it off for a day.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
This must be the issue then, thanks!
priceaw1 said:
I'm also having the exact same issue with my airave. If I unplug it I'm able to make calls without a problem. So as someone else posted I believe the airaves are having issues today. But I am on the stock FD26 ICS if anyone else is having the problem and thinks it has anything to do with the leak.
Click to expand...
Click to collapse
Yeah I unplugged the airave and I walked far outside to get a bar and was able to make a call. Didn't think it was the culprit because other family members can make calls with it, they have different phones though.
Thanks for the help guys
Having the same issue as well today. Tried powering down, chatted w sprint, still having issues. Don't think it has to do with build or rom as I have been on just about everything since I had mine.
Sent from my SPH-D710 using XDA
dante32278 said:
Having the same issue as well today. Tried powering down, chatted w sprint, still having issues. Don't think it has to do with build or rom as I have been on just about everything since I had mine.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
+1 having same issues. It was driving me crazy.
Sent from my SPH-D710 using xda premium
Exact same issue here too. Started yesterday morning. Have not had a chance to test it out today. Sister's iPhone works fine with the airave. Seems only my phone is affected for some reason. Spirit said they would get back to me in 72 hours. Hope the issue is resolved soon. Using Grooveip to make calls in the meantime.
Sent from my SPH-D710 using xda premium
Four people in the house on my plan and no-one has mentioned any issues with the airave other than the spamming txt issue sometimes.
Update: mine just started working again. Last night I reset the box by pressing the reset button for 15 seconds, still having issues after it reset through this morning. Sometime in the last hour it has become fully functional again. Weird.
Sent from my SPH-D710 using XDA
dante32278 said:
Update: mine just started working again. Last night I reset the box by pressing the reset button for 15 seconds, still having issues after it reset through this morning. Sometime in the last hour it has become fully functional again. Weird.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Will try when I get home.
Sent from my SPH-D710 using xda premium