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

Radio Interface Resource Shortage FIX

add me to the list. Every once in a while I try to send a text and it's got that little arrow that won't go away, indicating it's trying to send but won't.

When this happens I can't make phone calls either, the phone becomes worthless, could really suck if I actually needed to use it for something important. I could see this causing issues with my girlfriend (why didn't you reply? you send me straight to voicemail) or missing a call for a job interview or a message from an important client... it's a pretty serious issue. If I can't send/receive messages or make calls, what's the point of the phone? I suppose I can watch 3D videos and play games while I'm missing important calls/texts...

Sounds like there's no fix yet. Just a phone that has issues with it's network. This never happened with my Optimus or the Triumph.
 
Okay, did some investigating (since I was texting a bunch today).

It's definitely a timeout error, but I'm now convinced it's a phone issue, not a communications issue.

My guess is that the phone is timing out sooner than it should, which is being aggravated by the radio spikes. A bit annoying, they really need to fix the issues with this phone, soon.
 
Leslie Ann said:
Okay, did some investigating (since I was texting a bunch today).

It's definitely a timeout error, but I'm now convinced it's a phone issue, not a communications issue.

My guess is that the phone is timing out sooner than it should, which is being aggravated by the radio spikes. A bit annoying, they really need to fix the issues with this phone, soon.
Click to expand...

It really looked to me like the signal bars freeze, indicating the radio is getting stuck at some point in the code and infinite looping until it recovers somehow.
 
Just a quick warning to those going to t-mobile do not use foxfi.they just disconnected my data because of it.its kinda funny 7 months of using pdanet without a problem but they caught me after only using foxfi a few hours.I think I learned my lesson and will just pay vm the extra 15 to tether
 
euphan1555 said:
Just a quick warning to those going to t-mobile do not use foxfi.they just disconnected my data because of it.its kinda funny 7 months of using pdanet without a problem but they caught me after only using foxfi a few hours.I think I learned my lesson and will just pay vm the extra 15 to tether
Click to expand...

Couldn't you have just used Wireless Tether for Root Users after rooting?
 
euphan1555 said:
My exhibit wasn't rooted.I rarely root my phones.I only did it on my triumph because of gingerbreak
Click to expand...

Well there you go, you can tether on pretty much anything if you root. I've rooted every single android phone I've ever had, even my first one. There's almost no risk as long as you aren't stupid.
 
Think they did catch me because I did something stupid.I was using foxfi to get WiFi on my tv and odds are that data looks different.
 
Interestingly, supposedly companies can tell when a computer also accesses your phone internet as that looks different as well...idk I've never been caught
 
Hello, I'm new to the forums and was looking into getting this phone.

After reading this thread this seems like a major problem and has me reluctant on ever wanting to buy it until there's a fix for it since I would be doing a lot more texting than talking so I would definitely run into this problem a lot.

Is this the only problem that the phone suffers from?

Any talks of a fix to this issue?

I'm looking into the HTC One V to see if it's a better alternative.
 
AnonymousUsar said:
Hello, I'm new to the forums and was looking into getting this phone.

After reading this thread this seems like a major problem and has me reluctant on ever wanting to buy it until there's a fix for it since I would be doing a lot more texting than talking so I would definitely run into this problem a lot.

Is this the only problem that the phone suffers from?

Any talks of a fix to this issue?

I'm looking into the HTC One V to see if it's a better alternative.
Click to expand...

No one has any idea when this will be fixed, but it seems that HTC is working towards a solution. Right now, this phone is not functional (at least to me) and I'm moving to T-Mo with a Nexus. If you plan on sticking with this VM company who clearly doesn't care about their flagship devices' quality, the One V or the Optimus Elite is your best bet, the former being more powerful except that you have to deal with Sense (YUCK!).
 
I just did a bunch of research on this, and actually, Evo 3d users on Sprint experienced the same issues when using the leaked firmware. A few experienced it in the past as well, long before the Virgin firmware even.

For the most part, it's an ICS issue with the hardware (PRI apparently), which begs the question if Sprint users will again ave the same problem with the Sprint ICS when it rolls out and if not, can we get a patch.

For Sprint users who flashed our firmware, flashing back to Spring Firmware did not entirely fix it, but they did make a PRI patch that fixed it for those people, or at least helped. No word on whether it will work for us yet, however the question has been asked. I did find a way that at least temporarily helps, and that is re-activating/re-provisioning the phone. How much or how long it helps is questionable though.


Update: definitely not permanent, but does help.
 
Leslie Ann said:
I just did a bunch of research on this, and actually, Evo 3d users on Sprint experienced the same issues when using the leaked firmware. A few experienced it in the past as well, long before the Virgin firmware even.

For the most part, it's an ICS issue with the hardware (PRI apparently), which begs the question if Sprint users will again ave the same problem with the Sprint ICS when it rolls out and if not, can we get a patch.

For Sprint users who flashed our firmware, flashing back to Spring Firmware did not entirely fix it, but they did make a PRI patch that fixed it for those people, or at least helped. No word on whether it will work for us yet, however the question has been asked. I did find a way that at least temporarily helps, and that is re-activating/re-provisioning the phone. How much or how long it helps is questionable though.


Update: definitely not permanent, but does help.
Click to expand...



Great i hope your fix will hit the spot and give users actually some lead way to a working phone! If i had the phone i would give it a try(that's why i like buying from wally world they pretty much beg you the get a exchange before giving you the money back) but i will wait until another brave soul try this!!!! ANYBODY TAKE ONE FOR THE TEAM!
 
What you quoted is completely safe, just not permanent. It's something the VM techs will tell you to do. What we need is a permanent fix, which requires a patch and that is where it gets dangerous.
 
Last night it was extra bad in my apt (10016).

As soon as one text is sent, the second text would encounter the error. Actually, if a phone call/text is made/sent/received, the problem would occur. I applied the usual ##Clear# and profile/prl update. Then as soon as I send a text/make a phone call, the error would come back on the second call/text. I had 3G on.

Then I recall someone wrote that he/she didn't encounter the problem with 4G. So I turned on 4G. WHOA! All the texts/calls are sent/received!! 4G does drain my battery faster. Typically, if I leave 3G on overnight (midnight to 8am), battery would drain about 5%. With 4G last night, it drained about 10%. I guess I can live with that if this prevent the error from happening again.
 
hchen42 said:
Last night it was extra bad in my apt (10016).

As soon as one text is sent, the second text would encounter the error. Actually, if a phone call/text is made/sent/received, the problem would occur. I applied the usual ##Clear# and profile/prl update. Then as soon as I send a text/make a phone call, the error would come back on the second call/text. I had 3G on.

Then I recall someone wrote that he/she didn't encounter the problem with 4G. So I turned on 4G. WHOA! All the texts/calls are sent/received!! 4G does drain my battery faster. Typically, if I leave 3G on overnight (midnight to 8am), battery would drain about 5%. With 4G last night, it drained about 10%. I guess I can live with that if this prevent the error from happening again.
Click to expand...

that would explain why i had the problem a lot more the first few days of owning my first evo.i would lose 4g constantly and get the error at least 5 times a day.since i came back most days i never lose my 4g signal and i rarely get the error.the next time i get the error im gonna look and see if im on 4g or 3g.


edit- i went back and read one of my first posts in this thread and i wrote that for the first time i had 4g all day and didnt get the error
 
It happened to me last night around 2. I suddenly lost connection to Virgin and the fix metal571 provided helped with regaining my connection. Soon after that I noticed I could do everything but send texts. It got extremely annoying so I plugged my phone in to charge and went to sleep. This morning I checked if I could send texts, and success. It seems to be happening a lot at night for me.
 
metal571 said:
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.
Click to expand...
Tried this twice on my EVO, and it was only a temporary fix. Switching SMS programs to Chomp seems to have taken care of it, at least for now.
 
ThisCouldWork said:
Tried this twice on my EVO, and it was only a temporary fix. Switching SMS programs to Chomp seems to have taken care of it, at least for now.
Click to expand...

Switching SMS programs does NOT solve the issue. It still happens in the background, but the error is only thrown by the stock SMS app. If you download Signal Notification (Free) by Logic Monkey, you'll quickly see that your signal bars freeze from time to time when sending SMS and your signal goes to -120 dBm, which indicates a no-signal state where the bars still do not show an "X". That's the bug we're getting at here in a more specific form.
 
Changing the SMS did resolve what for me (personally) was the biggest part of the problem: not being able to use the phone for other things. I can see how switching SMS programs wouldn't solve an underlying signal notification problem, but I'm happy not to have the constant error messages hanging up my phone and happy not to have to reset it to get the messages to stop. I suppose people who rely on texting more than I do would be more bothered by it.

Thanks for the tip on the app.
 
Yeah, if you're not a heavy texter this isn't as big of a deal, but be warned that because of this signal issue you will miss calls or have very late delivery/receipt of texts
 
You must log in or register to reply here.
Back
Top Bottom