This may be a "Work Around" for the Galaxy S3 and Airave texting Error 97 issue. Here's what I am doing. If this quits working I will certainly update or remove this posting, however, it's been working for quite some time now.
NOTE: We were NOT in range of an airave when our phones were activated for the first time. Both phones were activated at the Sprint store.
1: UNPLUG your Airave.
2: Put all of the affected phones into Airplane mode shutting off all radios in the phones.
3: Now plug your Airave back in and let all 4 lights green up solid. (I know, this seems like it takes forever)
4: Wait 2 more minutes. (Have Patience Danielson)
5: Now and only now, take your phones out of airplane mode and give them a few minutes to sync up with the Airave. Don't dial the *99 thing either. just wait until your signal bar goes to full strength while in close range of the Airave.
6: You should now be able to send and receive text messages. (It works at my house anyway)
DO NOT UPDATE PROFILE, PRL, OR ACTIVATE A NEW PHONE WHILE IN RANGE OF AIRAVE. If you have done this, it would be a good idea to get out of range of Airave and acquire cell tower signal, and only then update your PROFILE and PRL.
NEVER ACTIVATE A NEW PHONE IN RANGE OF AN AIRAVE. If you have done this, you will probably need to contact Sprint and have them change your MSID/reactivate your phone while in cell tower range only and away from an Airave.
Here's how I came up with this: Of course I called Sprint tech support first when we noticed the issue with our brand new Galaxy s3 phones. My phone would text fine but her's wouldn't send any outgoing text messages. It kept giving her an error code 97. He tweaked some settings and reset the airave remotely. Now her phone would text but mine quite working and I was getting the error code. He said it was a known issue, and that Sprint was working with the manufacturer of the Airave on a solution. To sum up the entire conversation, he basically said to try resetting the Airave "When" it quit working and "Maybe" that would fix the problem. He confirmed that we were stuck with this issue until a software/firmware update was implemented with either the Airave or the GS3 phones. We would either have cell coverage and no text, or be forced to unplug the airave, go upstairs, and maybe get a signal to send a text or make a phone call. This simply isn't a viable option for us as our main living area is downstairs and we don't get any reception there.
Well, the texting issue bent back and forth between my S3, her S3, and most of the time both S3 phones not sending outgoing texts (code 97). It never once affected the other 2 LG rumor phones in the house and they worked flawlessly. Apparently this issue only affects certain phones and the GS3 is one of them. Simply resetting the Airave was just not doing the trick. Rarely (actually never) did just unplugging or resetting the Airave work on both phones at the same time. It finally dawned on me one day that when her phone would text and mine wouldn't, that she was out of the house when I reset the airave. Her phone would now text and mine wouldn't, Then we had a short power outage at the house another day. I was not home but she was, Then only my phone would text and hers quit working. So a thought popped into my head to run a little experiment and try taking the phones out of service while rebooting the airave. So far so good. Both phones are working 100% of the time unless we have a power blip or the Airave resets while we are in range. Apparently this is an issue that only happens with certain phones, and the Galaxy S3 is one of them. When the Airave resets in range of Galaxy S3 phones, there must be some sort of "handshake" routine that runs during initialization. I believe that this may be the source of the issue. Putting the phones in airplane mode stops this from happening when the Airave goes through the boot sequence and finally acquires "mobile".
I ran further experiments rebooting the airave with the phones radios turned on to see if the problem returned. The problem returned upon the first boot and only 1 phone could send outgoing texts. Further experiments proved (at my house at least) that having the radios turned off while booting the Airave solved the problem. Testing back and forth, and sure enough, when the radios were turned off (airplane mode) both phones worked fine. When the radios were turned on, the problem returned. Anyway, it is working at my home at least, and I can only hope it helps others out there to get around this very frustrating problem.
I love Sprint and my Galaxy S3 phone, I love the fact that they provided me with a free Airave to fix a reception problem, but the Texting bug is a pain in the rear irregardless. I certainly hope they are able to resolve this issue soon.
Good luck and I hope this helps others with this frustrating problem until a permanent solution is found.
I had this same issue with another phone. Nylox2004, you fixed it for me. I have been on the phone several times with Sprint and got nowhere. They finally referred me to the phone manufacturer, who said it was a Sprint problem. Then I read your post about rebooting the Airave while the phone was set to airplane mode. It now works perfectly. I think Sprint should give you some commission.
Well I had thought the issue was resolved with the new Airave from Sprint.
The Code 97 came back last night and still the same today.
I emailed Sprint and they had the standard response that there was an outage in my area that had been fixed (they always say that), and to also turn OFF the cell and take battery out for a few minutes. I did and it still didn't work.
Texting works fine if I unplug the Airave.
So something happened.... I wonder if there was a software update the Airave. I need to call them and elevate to someone who knows.
The problem just got weirder. I left home today (away from Airave) and my sister sent me some texts (from Verizon). I never got them. I was at her house and I then texted myself and got my own. She texted me again and I did not get it. I then went home and connected to Airave I got the messages from her in duplicate. I texted my self (while on Airave) and it worked fine.
So the issue seems intermittent on the Airave and seems to be an issue off of it too... unless there was an issue b/w Verizon and Sprint or a network outage (as Sprint said the other day in email reply although they ALWAYS say that).
Anyway, it seems OK at home now but I will try your solution and see what happens.
I did try your solution.... I got a Code 97 when trying to send Text to myself. It just worked prior to using your reset technique ):
I posted this earlier in this thread.... The steps below are basically changing the MSID, and completely removes and re-adds your phone back into their systems.
I was experiencing something similiar. When I was at home on my Airave I could make and receive calls without issue, but text messaging would not work (Code 97). I wouldn't be able to send or receive texts while on the Airave.
When I was on a normal 3G connection I could make calls and send text messages, but not receive calls or text messages. (Only items that use the voice services were affected like text messages, voicemail, calls, etc).
Short answer after a lot of trouble shooting, something didn't appear to complete properly when I transferred phones. So they deactivated and reactivated my phone and after it finally got a 3G signal (making sure not on the Airave), it started acting properly. IF you have this done make sure they put in the special code so you don't get charge the early termination fee, because this was done as a part of trouble shooting.
Now everything works both on and off the Airave. I don't even get the Code 97 while connected to the Airave. So my thought is, a lot of these problems are related to a failed activation or a partial activation.
I don't know if changing the MSID is the same as deactivating and reactivating the phone but I will call Sprint. Is it?
They did deactivate and reactivate my phone twice while NOT on the Airave before sending me the new Airave that they assured me would cure the problem.
Obvioulsy it did not.
Just weird that it is random...
Latest from Sprint Tech:
There is an issue even with the new Airave too. They are working with the manufacturer on a software upgrade.
They pushed some update to me but say it may not work (and to unplug/plug Airware later if issue reappears).
He said changing the MSID is not the solution (and I have had my phone deactivated and reactivated several times).
My experience is random even I do not reset the Airave....
Seems like they are still floundering a bit and I hope it is an issue with the Airware software.
Not sure why I had issues the other night OFF the Airware but they say it could have been a network issue with Verizon.
I'd say there is something more going on that their first level techs don't know. Because you are describing having issues outside of the Airave now.
One step I neglected to mention when I went through the reactivation process. After they deactivated my phone, I did a full reset on my phone (which I didn't want to do).
I'm guessing you might have tried this since they tried to do the deactivate/reactivate several times now, but thought I'd mention that just in case.
So far I've still be fortunate enough to have had no further issues, phone works fine on and off the Airave for all voice and data services.
Alas, this method did not work for my S III and Airave.
I tried it a few times over a few days with no luck. Sometimes, I would unplug the Airave and get one bar and my text messages would POUR in from all day long.
It seems that after connecting to the Airave and working for a beat text messages and calls would freeze until I get home or reboot the phone. This is rare; happens maybe once a week. But it only happens after connecting to the Airave.