• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Radio Interface Resource Shortage FIX

euphan1555 said:
the last email i got from vm said i was escalated to the engineering department.i took back the phone before hearing anything back.i then bought a new evo a week later and when i activated it i had 3 texts from the engineering department at least that is who i assume it was from.the first one just asked if i was still experiencing problems.since i couldnt get back to them they sent a second text the next day telling me they reset my services and gave me some 1 855 number to call if i was still having problems.the next day they sent me another text saying the same thing as the second text.i really wish i wouldnt of deleted the texts since after 3 days of owning my now third evo i started getting the the -120 error again
Click to expand...

They texted you? I gave VM my Google Voice number so I could get in touch with them without needing to use my phone (can receive & make calls from Gmail).
 
metal571 said:
They texted you? I gave VM my Google Voice number so I could get in touch with them without needing to use my phone (can receive & make calls from Gmail).
Click to expand...


yeah but like i said im just assuming it was the engineering department since the last email i got said they escalated me to the engineering department.they probably tried calling first and when they couldnt get a hold of me sent the texts.
 
I was getting the Resource error the first night I got my Evo, couldn't text or talk. All I did was goto the Update PRL option and then restart, and its worked fine ever since. I have PRL version 61009, not sure what version it had prior to updating, didn't even look.
 
OctopusOptimus said:
I was getting the Resource error the first night I got my Evo, couldn't text or talk. All I did was goto the Update PRL option and then restart, and its worked fine ever since. I have PRL version 61009, not sure what version it had prior to updating, didn't even look.
Click to expand...

when it first launched it had 60007 and when you updated it it went to 60008 and a few days later they updated it to 60009 edit- wasnt a few i was thinking about when i got the phone on july 6 or so.a few days after that is when they updated the prl to 60009
 
euphan1555 said:
when it first launched it had 60007 and when you updated it it went to 60008 and a few days later they updated it to 60009 edit- wasnt a few i was thinking about when i got the phone on july 6 or so.a few days after that is when they updated the prl to 60009
Click to expand...

I shouldn't have posted the above message, I think some spirit has been watching me, waiting for me to post it. Because RIGHT AFTER I POST THAT MESSAGE I start getting the same error again. Right in the middle of a very important conversation it starts screwing up. And I go into the info menu and its hopping between 1xRTT, EVDO REV 0 and EVDO REV A. Now its working again, hopefully it will stay this way.
 
OctopusOptimus said:
I shouldn't have posted the above message, I think some spirit has been watching me, waiting for me to post it. Because RIGHT AFTER I POST THAT MESSAGE I start getting the same error again. Right in the middle of a very important conversation it starts screwing up. And I go into the info menu and its hopping between 1xRTT, EVDO REV 0 and EVDO REV A. Now its working again, hopefully it will stay this way.
Click to expand...

Welcome to the real state of the EVO V 4G software my friend...atrociously unreliable
 
I guess now we know how Virgin Mobile is able to offer such low priced plans, because they don't spend a cent on repairing any issues or fixing anything.
 
OctopusOptimus said:
I guess now we know how Virgin Mobile is able to offer such low priced plans, because they don't spend a cent on repairing any issues or fixing anything.
Click to expand...

The ROM must have just been rushed. What I'm thinking is that HTC should release a radio update that helps this issue. The EVO 3D isn't scheduled to get ICS until Aug. and around then hopefully we should have the most up to date radio released to us as well.
 
OctopusOptimus said:
I shouldn't have posted the above message, I think some spirit has been watching me, waiting for me to post it. Because RIGHT AFTER I POST THAT MESSAGE I start getting the same error again. Right in the middle of a very important conversation it starts screwing up. And I go into the info menu and its hopping between 1xRTT, EVDO REV 0 and EVDO REV A. Now its working again, hopefully it will stay this way.
Click to expand...

This seems like just a low signal thing. At least it wasn't a interference error.
 
metal571 said:
It can happen at ANY signal strength. I had a drop when I was in a -60 dBm area
Click to expand...
Same here. I live/work in the center of NYC. There's a tower every 2-3 blocks. I live on 14th floor with no obstruction to cell tower; I can see the cell tower. I always get full bars of signal. So it's not low signal issue.

I have been consistently doing profile update every morning and every evening. Seems whenever I do the profile/prl update, the phone would be steady for about 5-8 hours.
 
HTC called me today because I left a dissatisfied response on their survey so that was pretty cool they called. The lady said she wasn't aware of any problems with the EVO V but would forward the dialing / radio shortage issue onto the development team.

From what everyone else on here has said, I'm going to hope they already know about the issue but that's what she told me.

~Cheers
 
Thanks for the update. I haven't heard from their engineering team yet, maybe during the week this week, who knows
 
i only had the error 1 time since my last post and i can deal with that.i still wish it would be a priority to fix this but for now i just use the signal notification app so i know when it happens.
 
As far as HTC not knowing , there's posts on Sprints forums on this phone and error dating back over a year , so its a known issue by all involved.
 
RG570 said:
As far as HTC not knowing , there's posts on Sprints forums on this phone and error dating back over a year , so its a known issue by all involved.
Click to expand...

Yes it is a sprint "thing" All my friends who has sprint says they get these errors all the time. So it just not one phone
 
Although what I've seen is that once they use the ##CLEAR# method, it usually fixes the problem. Here it happens again and again. I have two friends with an EVO 3D and they've never had the issue before...and then on top of that the 3D owners who flashed VM's firmware to test it had serious radio issues which are well documented. Here's to hoping it's a software issue related to the network problem in this case
 
tommieq94 said:
Yes it is a sprint "thing" All my friends who has sprint says they get these errors all the time. So it just not one phone
Click to expand...

Yeah, just did some Googling - it's all over Sprint, not just the Evo 3D, in fact, it's not even isolated to one phone manufacturer - some people are reporting it on LG phones as well.
 
For those of you running non-stock ROMs who are saying "I'm no longer getting the error" - you may not be getting the error, but have you gotten the symptoms?

I for one am running S-off with MidNightROM and still have the same issues, to the point of not being able to send/receive texts and unable to make/receive calls. The only way I know for sure that the problem is happening is either to try and make a call or to send a text, which then keeps telling me that it's unable to send the text.

So, no funky number error codes, but the same exact problem.
 
I've had the issue with every single ROM on this site. It's gotta be either a radio firmware issue (more likely) or the network (less likely). You'll know your device is glitched because when the radio freezes, Signal Notification will display -120 dBm and your signal bars will NOT show an "X". Clearly, that's a frozen radio that is stuck, and that's what the problem's root cause is. That alone says to me that the radio firmware is bugged.
 
I now get the error daily, particularly sending/reciving MMS messages seems to cause it even more. The best way that I've found to solve the issue (temporarily) is to simply restart the phone. That usually fixes it for a few hours.
 
You must log in or register to reply here.
Back
Top Bottom