Radio Interface Resource Shortage FIX

[metal571]

Current only confirmed fix is here: http://androidforums.com/evo-v-4g-all-things-root/595109-fix-everything-turning-your-phone-into-evo-3d-thread.html. It's your best bet.

Old OP:

There is an OTA available from HTC. Not much luck is being had with it, but it's something to try first.

WARNING: IF YOU INSTALL AN OTA ON AN S-OFF AND/OR BOOTLOADER-UNLOCKED DEVICE YOU COULD BRICK YOUR DEVICE. TO BE SAFE, RELOCK YOUR BOOTLOADER AND RUN THE STOCK RUU AS INSTRUCTED IN THE UNROOT GUIDE BEFORE ATTEMPTING THE BELOW INSTRUCTIONS FOR THIS OTA UPDATE.

Check for software updates first, then update your PRL, then update your profile. Try it for a while and see if this fixes the texting issue. Some say it's better at least, but it may not completely fix it. My old solution is under the following quote from this thread.

EDIT: people are saying this isn't fixing their issue, but you should still apply the OTA when you can anyway.

This is the order I updated my phone doboy, don't know if it makes a difference.
I first downloaded and installed the update, then the prl and then the update profile, after I completed those 3 things I rebooted my phone, I haven't had a problem since.

Older OP:

I've had this problem for the entire time I've owned this phone up until now. Here's how I fixed it. I can't believe VM doesn't tell you to do this, but apparently it's in the manual somewhere. You're supposed to do this right after you activate online or swap online.

EDIT: when you swap phones online and/or do this fix, make absolutely sure your old VM phone or phones are OFF and the batteries are REMOVED just as a precaution.

1. Start the Phone app.
2. Enter "##25327#" (this is ##CLEAR#)
3. The EPST menu should come up. Tap on Menu, then tap Reset
4. Tap on OK on the popup
5. Your phone will reboot, reactivate itself, and update its PRL. Then your SMS bug *should* be gone.

This is the ONLY fix I've found yet to be seemingly helpful in fixing the extremely common Cause Code 64 Class 2 bug when sending text messages. Unfortunately, it hasn't been completely successful for most people. In the event this does not help you, please do the following: email saveme@thevirginangels.com as well as calling their Executive Resolution Team at 877-291-5717 and tell them about the error and when it happens. The more people who do this, the better. Let's continue using this thread to tell people to contact VM about this issue so it gets resolved faster.

 

[novak921]

Well figured I would patronize you and give this a try. Not sure if it will help or not but I will let you know. Besides the SMS issue which quite a few of us have, the Evo V is a fantastic phone.

So far I've heard from some users that HTC is working on a fix, I've heard that VM is working on a fix, I've contacted VM and they have "re provisioned" my account but I still get the error and quite a few claim poor signal or signal issues which hopefully will be fixed because overall, this is a great phone.

Hope for optimistic news in the next week or two about a fix for the radio issue that we're having and no more cause code 64 issues. Fingers crossed.

~Novak

 

[metal571]

Believe it or not, I haven't had a single problem since I tried this, and a number of people on other forums have had the same news. Most threads about the radio interface error seem to end a few posts after someone posts this fix. Supposedly VM put this in the manual or something for the phone, and it's supposed to be done every time the phone is activated or you swap to this phone from another phone, but I have no idea why they don't tell you this online when you activate the phone. I know I'm a new user here, but at the same time, I can't seem to break texting via code 64 ever since I did this with the phone so far. Hopefully it works for you and others.

As far as the signal issues are concerned, the phone bars appear to be an inaccurate indicator of the actual signal. This can be verified by the use of an app called Signal Notification (the app has a monkey as the avatar in the Play Store) which displays the dBm of your signal in your status bar. The bars seem to be very sensitive, overly sensitive to the actual dBm reading, so it confuses people.

 

[thebryceee]

You can update the PRL in settings

 

[metal571]

You can update the PRL in settings

That's true. This fix does a lot more than that. It deactivates your phone, reboots it, and reactivates it over the air. You don't lose your account or minutes or end date. It just fully reactivates your phone and guarantees it.

 

[OneEyedSniper]

Thanks for this. I had the occasional sms error but not to the extent some had on these forums. I mainly did it to fix my data. I was applying new PRLs to the phone via QPST and I guess my data was screwed up and it was stuck at 1xRTT. So I decided to give this a try and it worked, I know have working 3G.

OP, should also add in to keep any old VM phones that you had swapped from off with the battery out. I did just in case since I still have my Triumph in possession. Just throwing this out there as a precaution.

I will try to report back if I get any more sms errors, if at all. Anyway thank you OP.

 

[metal571]

Glad it worked for you! I will edit my post with your suggestions. Trust me I wanted to throw a party after I discovered how effective this was...been wanting a fix like this since the day I got the phone...

 

[thebryceee]

I really only get those errors when I send a bunch of texts consecutively.

 

[hchen42]

I've had this problem for the entire time I've owned this phone up until now. Here's how I fixed it. I can't believe VM doesn't tell you to do this, but apparently it's in the manual somewhere. You're supposed to do this right after you activate online or swap online.

EDIT: when you swap phones online and/or do this fix, make absolutely sure your old VM phone or phones are OFF and the batteries are REMOVED just as a precaution.

1. Start the Phone app.
2. Enter "##25327#" (this is ##CLEAR#)
3. The EPST menu should come up. Tap on Menu, then tap Reset
4. Tap on OK on the popup
5. Your phone will reboot, reactivate itself, and update its PRL. Then your SMS bug should be gone.

Reply if you also have success with this. This is the ONLY fix I've found yet to be reliable in fixing the extremely common Cause Code 64 Class 2 bug when sending text messages in a low signal environment.

I read this somewhere in another thread. Not sure if it was posted by OP or not. Regardless, thanks to OP and all who suggested this.

The old method of just updating prl was not a a permanent fix. I "reactivated" with the ##CLEAR# tuesday night around 10pm est. It is now 10AM thursday morning (36 hours). I haven't encountered any radio interference errors since. My calls also have been coming in as well. Although something still seems fishy. But I would say this is getting better.

I recall when I first got OV, I had to do a lot of "Activation"/"Reactivation" and or toggle the airplane mode on OV. Roughly 1 month or 2 after receiving the phone, everything worked on OV. Guess we are going through the same growing pain with Evo V 4G.

 

[Member717347]

I've had this problem for the entire time I've owned this phone up until now. Here's how I fixed it. I can't believe VM doesn't tell you to do this, but apparently it's in the manual somewhere. You're supposed to do this right after you activate online or swap online.

EDIT: when you swap phones online and/or do this fix, make absolutely sure your old VM phone or phones are OFF and the batteries are REMOVED just as a precaution.

1. Start the Phone app.
2. Enter "##25327#" (this is ##CLEAR#)
3. The EPST menu should come up. Tap on Menu, then tap Reset
4. Tap on OK on the popup
5. Your phone will reboot, reactivate itself, and update its PRL. Then your SMS bug should be gone.

Reply if you also have success with this. This is the ONLY fix I've found yet to be reliable in fixing the extremely common Cause Code 64 Class 2 bug when sending text messages in a low signal environment.

It's asking for password when I hit reset.
Anyone know the password?

Edit: nevermind figured it out

 

[a12tmoreno]

I've had this problem for the entire time I've owned this phone up until now. Here's how I fixed it. I can't believe VM doesn't tell you to do this, but apparently it's in the manual somewhere. You're supposed to do this right after you activate online or swap online.

EDIT: when you swap phones online and/or do this fix, make absolutely sure your old VM phone or phones are OFF and the batteries are REMOVED just as a precaution.

1. Start the Phone app.
2. Enter "##25327#" (this is ##CLEAR#)
3. The EPST menu should come up. Tap on Menu, then tap Reset
4. Tap on OK on the popup
5. Your phone will reboot, reactivate itself, and update its PRL. Then your SMS bug should be gone.

Reply if you also have success with this. This is the ONLY fix I've found yet to be reliable in fixing the extremely common Cause Code 64 Class 2 bug when sending text messages in a low signal environment.

I tried that with two different phones, the error would go away for a few hours and then come back. It would happen regardless of signal strength.

 

[doboy]

I tried that with two different phones, the error would go away for a few hours and then come back. It would happen regardless of signal strength.

It seems like the issue is not the phone, but their system.

 

[vernave]

I've had this problem for the entire time I've owned this phone up until now. Here's how I fixed it. I can't believe VM doesn't tell you to do this, but apparently it's in the manual somewhere. You're supposed to do this right after you activate online or swap online.

EDIT: when you swap phones online and/or do this fix, make absolutely sure your old VM phone or phones are OFF and the batteries are REMOVED just as a precaution.

1. Start the Phone app.
2. Enter "##25327#" (this is ##CLEAR#)
3. The EPST menu should come up. Tap on Menu, then tap Reset
4. Tap on OK on the popup
5. Your phone will reboot, reactivate itself, and update its PRL. Then your SMS bug should be gone.

Reply if you also have success with this. This is the ONLY fix I've found yet to be reliable in fixing the extremely common Cause Code 64 Class 2 bug when sending text messages in a low signal environment.

Can we get a sticky of this?

 

[metal571]

Yeah, I actually discovered that I got the error again as well this afternoon. This problem appears to come back a little less readily with this method though, as this fix helps for what seems like a longer time than a simple system profile update. Just thought I'd throw that out there.

The password you need to enter is your MSL. On some ROMs I didn't need to enter it, however for some reason. Let me know if you guys want that added, I might have to mention that.

 

[fleshlightt]

I have had the error since doing this.

 

[jr2673]

I have had the error since doing this.

have you ever heard ? if its not broke don't try & fix it.


PS.
Try And Do A System Restore / Reset

 

[metal571]

Hopefully he had the error first before he tried this for reactivation. This fix I know works for at least a number of hours at a time. IMO it may be the best shot we have right now at combating this bug. I for one am going to keep bombarding the ERT call center until they know exactly what the real problem is. I wish I could call up the engineers who made the phone, holding an engineering degree myself...

 

[novak921]

Still received the same error on the way home from work today. I just don't text a lot so it's not horrible.

 

[metal571]

Still received the same error on the way home from work today. I just don't text a lot so it's not horrible.

Did this occur when your signal was pretty low? That seems to be the main type of area where this error occurs.

 

[fleshlightt]

I was having the error before and after, in all types of signal situations. It seems the radio has problems recovering.

 

[metal571]

Yeah, the phone appears to have an issue of becoming deactivated and reactivated, and in the time it's deactivated, it won't make or receive calls or texts. That's my experience anyway. Also, the mobile data connection dies when I get the error 64 as well for me. Maybe this thread can turn into one of people posting where and when this error occurs (like what signal strength) so we can further investigate. I'm going to complaing to upper level Sprint people about this until a fix happens.

 

[doboy]

Still received the same error on the way home from work today. I just don't text a lot so it's not horrible.

I don't either, but I can't receive calls when I get the error and that's the main issue for me.

Yeah, the phone appears to have an issue of becoming deactivated and reactivated, and in the time it's deactivated, it won't make or receive calls or texts. That's my experience anyway. Also, the mobile data connection dies when I get the error 64 as well for me. Maybe this thread can turn into one of people posting where and when this error occurs (like what signal strength) so we can further investigate. I'm going to complaing to upper level Sprint people about this until a fix happens.

I had the error 64 three times so far. Even before getting the error for the 1st time, I've read other people having problems so I frequently checked my signal strength. I only get the error when I notice that my signal at -120 dBm. So far all three times happened when I was connected via WiFi. Once at home where signal is between -80 to -95 dBm. Second time happened at work where signal is -75 to -85 dBm immediately after restarting the device (ironically, to help prevent error 64). Third time happened at work right after doing the profile update and PRL update (again as an preemptive measure). These events happened in three separate days and all resolved by turning off the WiFi then enabling it once the signal strength improved from -120 dBm. It's always at -120 dBm when I run into this problem and it just suddenly jumps to -120. Today I've installed opensignalmaps app to monitor my signal strength and log it in the background.

 

[novak921]

Did this occur when your signal was pretty low? That seems to be the main type of area where this error occurs.

Yea, the signal skipped out right after I hit send and I had 5 bars and 3G. Fingers crossed that HTC and VM aren't lying about a radio fix.

 

[metal571]

I don't either, but I can't receive calls when I get the error and that's the main issue for me.



I had the error 64 three times so far. Even before getting the error for the 1st time, I've read other people having problems so I frequently checked my signal strength. I only get the error when I notice that my signal at -120 dBm. So far all three times happened when I was connected via WiFi. Once at home where signal is between -80 to -95 dBm. Second time happened at work where signal is -75 to -85 dBm immediately after restarting the device (ironically, to help prevent error 64). Third time happened at work right after doing the profile update and PRL update (again as an preemptive measure). These events happened in three separate days and all resolved by turning off the WiFi then enabling it once the signal strength improved from -120 dBm. It's always at -120 dBm when I run into this problem and it just suddenly jumps to -120. Today I've installed opensignalmaps app to monitor my signal strength and log it in the background.

That is my experience exactly as well. -120 dBm is what it just sits at and gives you the error. This seems to help the evidence I've read elsewhere that this happens when WiFi is enabled. That's the case here too. Interesting. Opensignalmaps app you say? Is that on the Play Store? I've been using Signal Notification by LogicMonkey to display my signal strength on the status bar.

Update: I have contacted HTC on twitter, who forwarded me to their support website, and I have placed a detailed email complaint into their support system. I'll update here if I can glean any considerable information regarding any kind of fix for the radio. For now it seems like the radio firmware needs to be rewritten and/or edited and an update released. It's possible guys...VM did issue a radio update for the OV, for example. I used to own one.

 

[doboy]

That is my experience exactly as well. -120 dBm is what it just sits at and gives you the error. This seems to help the evidence I've read elsewhere that this happens when WiFi is enabled. That's the case here too. Interesting. Opensignalmaps app you say? Is that on the Play Store? I've been using Signal Notification by LogicMonkey to display my signal strength on the status bar.

Update: I have contacted HTC on twitter, who forwarded me to their support website, and I have placed a detailed email complaint into their support system. I'll update here if I can glean any considerable information regarding any kind of fix for the radio. For now it seems like the radio firmware needs to be rewritten and/or edited and an update released. It's possible guys...VM did issue a radio update for the OV, for example. I used to own one.

I had two more issues today. Again after a reboot (with WiFi on) the signal went to -120 dBm immediately and when I pulled into my garage at home (where it's typically poor in signal). However, I had the WiFi off at the time it went to -120 dBm at home so this is the first time that happened. It eventually recovered on it's own after ~3 minutes of leaving it alone. Opensignalmaps is both a website and an app. I had the widget running today when I lost the signal and it gave me a notificaton (optional) immediately when I totally lost the signal (-115 dBm per widget) and notified me again when the signal was restored. Seems like an awesome app.