Go Back   Android Forums > Android Phones > HTC EVO V 4G

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree13Likes

test: Reply
 
LinkBack Thread Tools
Old July 5th, 2012, 12:09 AM   #1 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default Radio Interface Resource Shortage FIX

Current only confirmed fix is here: The "Fix everything by turning your phone into an Evo 3d" thread. 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.

Quote:
Originally Posted by KB2VYZ View Post
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.
Blaurad likes this.

metal571 is offline  
Last edited by metal571; October 9th, 2012 at 10:05 AM.
Reply With Quote
The Following 14 Users Say Thank You to metal571 For This Useful Post:
acharlest (July 5th, 2012), Blaurad (October 4th, 2012), Chingling (July 30th, 2012), DKO (July 14th, 2012), Essjay22 (April 3rd, 2013), Fapmaster (July 23rd, 2012), hawnee (September 3rd, 2012), hchen42 (July 5th, 2012), Manicor (July 5th, 2012), Mystic03290 (February 9th, 2013), njs11usc (July 5th, 2012), prrep (December 24th, 2012), raynoldsk (July 10th, 2012), schooley (July 29th, 2012)
sponsored links
Old July 5th, 2012, 12:55 AM   #2 (permalink)
Member
 
Join Date: Aug 2011
Location: Chicago
Gender: Male
Posts: 159
 
Device(s): HTC EVO V 4G
Carrier: Virgin Mobile

Thanks: 6
Thanked 14 Times in 10 Posts
Send a message via AIM to novak921
Default

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
novak921 is offline  
Reply With Quote
Old July 5th, 2012, 01:03 AM   #3 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

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.
metal571 is offline  
Last edited by metal571; July 5th, 2012 at 01:08 AM.
Reply With Quote
Old July 5th, 2012, 01:30 AM   #4 (permalink)
Senior Member
 
thebryceee's Avatar
 
Join Date: Feb 2012
Gender: Male
Posts: 2,245
 
Device(s): Nexus⁴, Evo V 4G, Rooted Kindle Fire
Carrier: T-Mobile

Thanks: 140
Thanked 233 Times in 212 Posts
Default

You can update the PRL in settings
thebryceee is offline  
Reply With Quote
Old July 5th, 2012, 01:31 AM   #5 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by thebryceee View Post
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.
metal571 is offline  
Reply With Quote
Old July 5th, 2012, 01:46 AM   #6 (permalink)
Junior Member
 
Join Date: Aug 2011
Location: Illinois
Posts: 24
 
Device(s): HTC EVO V 4G, Motorola Triumph
Carrier: Not Provided

Thanks: 2
Thanked 5 Times in 3 Posts
Default

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.
OneEyedSniper is offline  
Reply With Quote
Old July 5th, 2012, 01:48 AM   #7 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

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...
metal571 is offline  
Reply With Quote
Old July 5th, 2012, 03:22 AM   #8 (permalink)
Senior Member
 
thebryceee's Avatar
 
Join Date: Feb 2012
Gender: Male
Posts: 2,245
 
Device(s): Nexus⁴, Evo V 4G, Rooted Kindle Fire
Carrier: T-Mobile

Thanks: 140
Thanked 233 Times in 212 Posts
Default

I really only get those errors when I send a bunch of texts consecutively.
thebryceee is offline  
Reply With Quote
Old July 5th, 2012, 09:45 AM   #9 (permalink)
Member
 
Join Date: Mar 2011
Location: New York City
Posts: 128
 
Device(s): Samsung Galaxy S3
Carrier: Virgin Mobile

Thanks: 57
Thanked 16 Times in 16 Posts
Thumbs up

Quote:
Originally Posted by metal571 View Post
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.
hchen42 is offline  
Reply With Quote
Old July 5th, 2012, 11:16 AM   #10 (permalink)
Member
 
dueltothedeath's Avatar
 
Join Date: Oct 2011
Posts: 149
 
Device(s):
Carrier: Not Provided

Thanks: 82
Thanked 23 Times in 22 Posts
Default

Quote:
Originally Posted by metal571 View Post
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
dueltothedeath is offline  
Last edited by dueltothedeath; July 5th, 2012 at 11:26 AM.
Reply With Quote
sponsored links
Old July 5th, 2012, 11:26 AM   #11 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 13
 
Device(s): HTC One V, Optimus V, Kindle Fire
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by metal571 View Post
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.
a12tmoreno is offline  
Reply With Quote
Old July 5th, 2012, 12:39 PM   #12 (permalink)
Member
 
Join Date: Apr 2012
Posts: 165
 
Device(s): LG G2 (white D-801); Note II (SGH-TT889); GS III (SGH-T999);
Carrier: T-Mo $30 plan

Thanks: 24
Thanked 19 Times in 15 Posts
Default

Quote:
Originally Posted by a12tmoreno View Post
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.
doboy is offline  
Reply With Quote
Old July 5th, 2012, 01:35 PM   #13 (permalink)
Junior Member
 
Join Date: Apr 2012
Posts: 84
 
Device(s):
Carrier: Not Provided

Thanks: 12
Thanked 3 Times in 3 Posts
Default

Quote:
Originally Posted by metal571 View Post
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?
avi2003 likes this.
vernave is offline  
Reply With Quote
The Following User Says Thank You to vernave For This Useful Post:
avi2003 (November 9th, 2012)
Old July 5th, 2012, 02:02 PM   #14 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

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.
metal571 is offline  
Last edited by metal571; July 5th, 2012 at 02:05 PM.
Reply With Quote
Old July 5th, 2012, 04:36 PM   #15 (permalink)
Junior Member
 
Join Date: Aug 2011
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 11 Times in 10 Posts
Thumbs down

I have had the error since doing this.
fleshlightt is offline  
Reply With Quote
Old July 5th, 2012, 05:39 PM   #16 (permalink)
Member
 
jr2673's Avatar
 
Join Date: Apr 2011
Location: Homestead,FL
Posts: 149
 
Device(s): Samsung Galaxy S2 (T-Mobile), HTC EVO V 3D (Retired) , LG Esteem , Sumsung
Carrier: Not Provided

Thanks: 21
Thanked 11 Times in 9 Posts
Default

Quote:
Originally Posted by fleshlightt View Post
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
jr2673 is offline  
Reply With Quote
Old July 5th, 2012, 05:41 PM   #17 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

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...
metal571 is offline  
Reply With Quote
Old July 5th, 2012, 05:50 PM   #18 (permalink)
Member
 
Join Date: Aug 2011
Location: Chicago
Gender: Male
Posts: 159
 
Device(s): HTC EVO V 4G
Carrier: Virgin Mobile

Thanks: 6
Thanked 14 Times in 10 Posts
Send a message via AIM to novak921
Default

Still received the same error on the way home from work today. I just don't text a lot so it's not horrible.
novak921 is offline  
Reply With Quote
Old July 5th, 2012, 05:52 PM   #19 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by novak921 View Post
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.
metal571 is offline  
Reply With Quote
Old July 5th, 2012, 06:06 PM   #20 (permalink)
Junior Member
 
Join Date: Aug 2011
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 11 Times in 10 Posts
Default

I was having the error before and after, in all types of signal situations. It seems the radio has problems recovering.
fleshlightt is offline  
Reply With Quote
sponsored links
Old July 5th, 2012, 06:09 PM   #21 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

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.
metal571 is offline  
Reply With Quote
Old July 5th, 2012, 06:29 PM   #22 (permalink)
Member
 
Join Date: Apr 2012
Posts: 165
 
Device(s): LG G2 (white D-801); Note II (SGH-TT889); GS III (SGH-T999);
Carrier: T-Mo $30 plan

Thanks: 24
Thanked 19 Times in 15 Posts
Default

Quote:
Originally Posted by novak921 View Post
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.

Quote:
Originally Posted by metal571 View Post
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.
doboy is offline  
Reply With Quote
Old July 5th, 2012, 06:30 PM   #23 (permalink)
Member
 
Join Date: Aug 2011
Location: Chicago
Gender: Male
Posts: 159
 
Device(s): HTC EVO V 4G
Carrier: Virgin Mobile

Thanks: 6
Thanked 14 Times in 10 Posts
Send a message via AIM to novak921
Default

Quote:
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.
novak921 is offline  
Reply With Quote
Old July 5th, 2012, 06:48 PM   #24 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by doboy View Post
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.
metal571 is offline  
Last edited by metal571; July 5th, 2012 at 07:05 PM. Reason: Update
Reply With Quote
Old July 5th, 2012, 08:52 PM   #25 (permalink)
Member
 
Join Date: Apr 2012
Posts: 165
 
Device(s): LG G2 (white D-801); Note II (SGH-TT889); GS III (SGH-T999);
Carrier: T-Mo $30 plan

Thanks: 24
Thanked 19 Times in 15 Posts
Default

Quote:
Originally Posted by metal571 View Post
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.
doboy is offline  
Reply With Quote
Old July 5th, 2012, 08:56 PM   #26 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by doboy View Post
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.
I'll definitely have to look into that app. For now, notifications when I lose signal to -120 could prove very useful. Also, the more people report this problem to HTC and VM, the better. They have to see the backlash to do anything about it, so the more complains, phone calls, and emails, the better.
metal571 is offline  
Reply With Quote
Old July 5th, 2012, 09:08 PM   #27 (permalink)
Junior Member
 
Join Date: Aug 2011
Posts: 83
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 11 Times in 10 Posts
Default

HTC updated the wildfire S. So I believe if it is brought to their attention by enough people, they will fix this.
fleshlightt is offline  
Reply With Quote
Old July 6th, 2012, 09:08 AM   #28 (permalink)
Member
 
Join Date: Mar 2011
Location: New York City
Posts: 128
 
Device(s): Samsung Galaxy S3
Carrier: Virgin Mobile

Thanks: 57
Thanked 16 Times in 16 Posts
Default

Quote:
Originally Posted by metal571 View Post
I'll definitely have to look into that app. For now, notifications when I lose signal to -120 could prove very useful. Also, the more people report this problem to HTC and VM, the better. They have to see the backlash to do anything about it, so the more complains, phone calls, and emails, the better.
Agreed, I've sent both HTC, VM emails (via the contact). I will also post on facebook and perhaps twitter.

BTW, ##clear# helped some and the 64/2 error came back. I was just testing as one of the poster mentioned it happened to him when he texted multiple messages quickly. Lo and behold, it happened. Before i performed the ##clear#, the text would be stuck on 64/2 error until I did a prl update. Now, the phone seems to "reset" the signals and the messages would send. So while ##clear# didn't totally fix this issue, it did improve somewhat (for me).
hchen42 is offline  
Reply With Quote
Old July 6th, 2012, 09:28 AM   #29 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 13
 
Device(s): HTC One V, Optimus V, Kindle Fire
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

I had three different EVO V’s, for me, this issue happened regardless if I was on WIFI or off. The signal would show full bars and then all go away once I hit send just like the previous post said, I had the exact same problem on all three.
I tried all the fixes VM told me to do on all three phones, in email communication and with the support techs over the phone (updating Profile, PRL, Factory Reset, ##CLEAR#, re-activating, suspending/un-suspending my account & re-provisioning services) in all the two weeks I had this phone, I spent more time trying to fix it instead of enjoying it.
What I still don’t understand is why some people don’t have this problem at all; if it is indeed a software problem shouldn’t all EVO V’s be affected? Out of the three units I had, two were Sprint branded and one was not, so that clears up the myth that only the Sprint branded units were defective.
a12tmoreno is offline  
Reply With Quote
Old July 6th, 2012, 10:24 AM   #30 (permalink)
Member
 
flboy91's Avatar
 
Join Date: May 2012
Posts: 293
 
Device(s):
Carrier: Not Provided

Thanks: 180
Thanked 6 Times in 6 Posts
Default

How do u find to phone's msl???
flboy91 is offline  
Reply With Quote
sponsored links
Old July 6th, 2012, 12:19 PM   #31 (permalink)
Junior Member
 
Join Date: Dec 2010
Location: Durham, NC
Posts: 93
 
Device(s): Samsung Galaxy S III
Carrier: Virgin Mobile

Thanks: 34
Thanked 18 Times in 16 Posts
Default

Quote:
Originally Posted by flboy91 View Post
How do u find to phone's msl???
Grab MSL Reader from Google Play.
aldamon is offline  
Reply With Quote
The Following User Says Thank You to aldamon For This Useful Post:
flboy91 (July 6th, 2012)
Old July 6th, 2012, 12:29 PM   #32 (permalink)
Member
 
flboy91's Avatar
 
Join Date: May 2012
Posts: 293
 
Device(s):
Carrier: Not Provided

Thanks: 180
Thanked 6 Times in 6 Posts
Default

Thanx brb with update
flboy91 is offline  
Reply With Quote
Old July 6th, 2012, 03:00 PM   #33 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by a12tmoreno View Post
I had three different EVO V’s, for me, this issue happened regardless if I was on WIFI or off. The signal would show full bars and then all go away once I hit send just like the previous post said, I had the exact same problem on all three.
I tried all the fixes VM told me to do on all three phones, in email communication and with the support techs over the phone (updating Profile, PRL, Factory Reset, ##CLEAR#, re-activating, suspending/un-suspending my account & re-provisioning services) in all the two weeks I had this phone, I spent more time trying to fix it instead of enjoying it.
What I still don’t understand is why some people don’t have this problem at all; if it is indeed a software problem shouldn’t all EVO V’s be affected? Out of the three units I had, two were Sprint branded and one was not, so that clears up the myth that only the Sprint branded units were defective.
Thanks for your input, that seems to dispel the myth that the Virgin branded ones are better. Still no response from HTC yet...

UPDATE: An ERT guy finally yielded to me and finally understood that this is a phone-specific issue rather than being an issue with the low signal in my area and is forwarding me to the "technical" department, hopefully even higher up. He said usually they eventually escalate this issue to the manufacturer themselves. I can't WAIT to talk to HTC one on one.

UPDATE: On the phone right now with the technical support above the Executive Resolution Team, and they listened carefully to a detailed description of the issue. Let's see what they do...
metal571 is offline  
Last edited by metal571; July 6th, 2012 at 04:07 PM.
Reply With Quote
The Following User Says Thank You to metal571 For This Useful Post:
doboy (July 6th, 2012)
Old July 6th, 2012, 04:19 PM   #34 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 13
 
Device(s): HTC One V, Optimus V, Kindle Fire
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Good luck, I read somewhere in these forums that someone actually got an email back from HTC saying that it was a radio software issue and that they were "working" on a fix but did not have a reasonable estimate of when it would be completed, let alone released. But again, if some users aren't having these issues then I don't see the radio software being the only problem. I think it has something to do with their network. Too bad they haven't figured it out yet.
a12tmoreno is offline  
Reply With Quote
Old July 6th, 2012, 04:25 PM   #35 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

It's gotta be a firmware issue. Top tech support just reset my service (or so it seemed) then told me to send 3 texts to myself. Those went through. They said they'd call me back again tomorrow. The very first text I sent after that conversation concluded was one to my girlfriend, and guess what? Radio Interface Resource Shortage. Can't wait to see what they do next when I tell them this tomorrow.
doboy likes this.
metal571 is offline  
Reply With Quote
The Following 2 Users Say Thank You to metal571 For This Useful Post:
flboy91 (July 6th, 2012), RichardSeq (July 11th, 2012)
Old July 6th, 2012, 08:43 PM   #36 (permalink)
Member
 
marco562's Avatar
 
Join Date: Jun 2012
Location: ������
Gender: Male
Posts: 104
 
Device(s): Samsung galaxy S3,HTC EVO V 4G,
Carrier: vmobile

Thanks: 8
Thanked 7 Times in 5 Posts
Default

I did this method and I got a sms error 2hrs after..
marco562 is offline  
Reply With Quote
Old July 6th, 2012, 08:49 PM   #37 (permalink)
New Member
 
Join Date: Jun 2012
Posts: 13
 
Device(s): HTC One V, Optimus V, Kindle Fire
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by metal571 View Post
It's gotta be a firmware issue. Top tech support just reset my service (or so it seemed) then told me to send 3 texts to myself. Those went through. They said they'd call me back again tomorrow. The very first text I sent after that conversation concluded was one to my girlfriend, and guess what? Radio Interface Resource Shortage. Can't wait to see what they do next when I tell them this tomorrow.
That is the same experience I had. After they finished their rounds of troubleshooting of course my text, data & phone calls would work fine just to have the error come back a few minutes later. I can't even recall how many departments I was transferred to.
I gave up my $25 plan for this mess! I'm just happy I was able to get my $300 back.
a12tmoreno is offline  
Reply With Quote
Old July 6th, 2012, 09:54 PM   #38 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

I'm going to do whatever it takes to get HTC to fix this. It's their fault for writing a bad radio for ICS. That's what I expect to happen eventually, to get in direct contact with HTC. Hell, I'd like to take a look at the firmware myself since I can read C with no problem. Who knows what they wrote it in though. If this gets too terrible, I'll probably hop on the Nexus/T-Mo bandwagon myself. However I need more than 100 minutes a month...but that's another discussion in itself. This thread should be named different, but I'm not sure how to change the name now. It's more like "Radio Interface Resource Shortage - Get VM and HTC to fix it"
metal571 is offline  
Reply With Quote
Old July 7th, 2012, 12:05 AM   #39 (permalink)
Senior Member
 
Austrie's Avatar
 
Join Date: Jan 2011
Location: St.Thomas, US Virgin Islands
Gender: Male
Posts: 1,325
 
Device(s): HTC EVO V 4G, Running: AOKP 4.1.2 v3.5.2, Skill Level(s): App, ROM, & Kernel Dev
Carrier: Virgin Mobile

Thanks: 0
Thanked 899 Times in 316 Posts
Default

Well a VM manager told me that it will fixed by the latest of the second week of August.
__________________
I Don't ASK You For Cash, So Atleast Hit My Thanks Button Everytime You See A Good Post... ~~~~ \/My Wish List\/
~Faster Internet~
~55$ dollar plan~
~64GB SD Card~
Austrie is offline  
Reply With Quote
Old July 7th, 2012, 12:09 AM   #40 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

Quote:
Originally Posted by Austrie View Post
Well a VM manager told me that it will fixed by the latest of the second week of August.
Did they say if HTC was going to push out an update to fix it? I'm pretty sure it's a software thing and not a tower issue....well i guess it could be the latter, it's still possible
metal571 is offline  
Reply With Quote
sponsored links
Old July 7th, 2012, 12:37 AM   #41 (permalink)
Senior Member
 
koopakid08's Avatar
 
Join Date: Mar 2011
Location: Behind you
Posts: 772
 
Device(s): LG Optimus V, Nook Color
Carrier: Not Provided

Thanks: 72
Thanked 165 Times in 105 Posts
Default

I think we should start some sort of customer service campaign or something so they get there stuff together to fix it. This problem has been really annoying lately and frankly I'm sick of it.
amk2795 likes this.
koopakid08 is offline  
Reply With Quote
Old July 7th, 2012, 01:59 AM   #42 (permalink)
Senior Member
 
Austrie's Avatar
 
Join Date: Jan 2011
Location: St.Thomas, US Virgin Islands
Gender: Male
Posts: 1,325
 
Device(s): HTC EVO V 4G, Running: AOKP 4.1.2 v3.5.2, Skill Level(s): App, ROM, & Kernel Dev
Carrier: Virgin Mobile

Thanks: 0
Thanked 899 Times in 316 Posts
Default

The manager didn't get too finish; the call cut off. I do think it's a software issue though since when Sprint users tried our Leaked ROM they have the same network issues as we do now. So I'll put my money that VM is just improving their service and HTC is the one dealing with the actual problem/software fixing.
Austrie is offline  
Reply With Quote
The Following User Says Thank You to Austrie For This Useful Post:
RichardSeq (July 11th, 2012)
Old July 7th, 2012, 06:09 PM   #43 (permalink)
Member
 
Join Date: Jun 2012
Posts: 209
 
Device(s):
Carrier: Not Provided

Thanks: 29
Thanked 8 Times in 8 Posts
Default

Is it safe to do this even if your phone wasn't recently activated? I still get the interface resource shortage error a few times a day but i've had my evo for about 2 weeks.
blh2012 is offline  
Reply With Quote
Old July 7th, 2012, 06:51 PM   #44 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

yeah should be totally safe i've done it a number of times. it should be noted that this thread is now being used to urge people to contact virgin mobile and HTC about the issue as it seems to be software related and there is no known permanent fix. this fix seems to keep your phone in check the longest but the error usually comes back.
metal571 is offline  
Reply With Quote
Old July 7th, 2012, 07:55 PM   #45 (permalink)
Member
 
Join Date: Jun 2012
Posts: 209
 
Device(s):
Carrier: Not Provided

Thanks: 29
Thanked 8 Times in 8 Posts
Default

Quote:
Originally Posted by metal571 View Post
yeah should be totally safe i've done it a number of times. it should be noted that this thread is now being used to urge people to contact virgin mobile and HTC about the issue as it seems to be software related and there is no known permanent fix. this fix seems to keep your phone in check the longest but the error usually comes back.
are there any benefits to doing this besides fixing the error? like refreshed signal, better reception, refreshed network...i only get the texting errors a couple times a day now, especially when I have low signal.
blh2012 is offline  
Reply With Quote
Old July 7th, 2012, 08:00 PM   #46 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

yeah generally it refreshes the signal strength. the low signal errors are pretty related to software problems with the radio that need to be fixed still. tl:dr version: it couldn't hurt.
metal571 is offline  
Reply With Quote
Old July 9th, 2012, 03:05 PM   #47 (permalink)
Member
 
Join Date: Apr 2012
Posts: 165
 
Device(s): LG G2 (white D-801); Note II (SGH-TT889); GS III (SGH-T999);
Carrier: T-Mo $30 plan

Thanks: 24
Thanked 19 Times in 15 Posts
Default

Update:
I was in an area with great signal (-51 to -60 dBm), but still had my signal jump to -120 dBm all of sudden after using the camera for few shots. So to me this error is not related to low signal. I've tried using Opensignalmaps app to alert me when signal drops and use their widget, but the widget sometimes doesn't update correctly and the app crashes after ~1 day of use. I've since uninstalled the app and now using Signal Notification (free) by LogicMonkey (thanks to metal571) to display the numerical signal strength in my status bar so I can easily check when the signal drops to -120 dBm (signal at which the error occurs). I would recommend everyone with issues to install this app (or equivalent) to keep an eye on their signal so you can quickly remedy the problem by toggling WiFi (when on WiFi) or toggling airplane mode.
doboy is offline  
Reply With Quote
Old July 9th, 2012, 03:21 PM   #48 (permalink)
Member
 
Join Date: Nov 2011
Posts: 295
 
Device(s):
Carrier: Not Provided

Thanks: 40
Thanked 57 Times in 35 Posts
Default

What does toggling wifi or airplane mode do for you in this case?
swerver32 is offline  
Reply With Quote
Old July 9th, 2012, 03:26 PM   #49 (permalink)
Senior Member
Thread Author (OP)
 
Join Date: May 2012
Location: Philadelphia, PA
Posts: 517
 
Device(s): Samsung Galaxy Nexus maguro, Codename Android JB. Sometimes a Nexus S crespo.
Carrier: Not Provided

Thanks: 34
Thanked 74 Times in 54 Posts
Send a message via Skype™ to metal571 metal571
Default

That's what I would recommend doing too. Toggling usually allows the -120 dBm signal to go back to what it should be. It sort of gets the signal "unstuck." Not too many updates on my end yet. The best I got out of HTC is that "they are investigating" as to the cause of the problem. Yeah, that's real helpful. I'm going to call VM again today.
metal571 is offline  
Reply With Quote
Old July 9th, 2012, 03:41 PM   #50 (permalink)
Member
 
Join Date: Apr 2012
Posts: 165
 
Device(s): LG G2 (white D-801); Note II (SGH-TT889); GS III (SGH-T999);
Carrier: T-Mo $30 plan

Thanks: 24
Thanked 19 Times in 15 Posts
Default

Quote:
Originally Posted by metal571 View Post
That's what I would recommend doing too. Toggling usually allows the -120 dBm signal to go back to what it should be. It sort of gets the signal "unstuck." Not too many updates on my end yet. The best I got out of HTC is that "they are investigating" as to the cause of the problem. Yeah, that's real helpful. I'm going to call VM again today.
The standard "investigating" response.
doboy is offline  
Reply With Quote
Reply

HTC EVO V 4G
Current Rating:
Rate this Phone:

The HTC EVO V 4G is Virgin Mobile's first 4G WiMAX Android device. And if it looks familiar, it is because the phone is the same as the EVO 3D, but optimized for this network. Release date is set for May 31st, 2012, for a price of $300 off-co... Read More



Go Back   Android Forums > Android Phones > HTC EVO V 4G
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 12:30 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.