Important Information for Everyone with this Phone Directly from HTC Escalation

[metal571]

For everyone who has had the Radio Interface error and even those of you who don't, I just learned some very valuable information directly from an HTC Escalations Department rep by phone. Before you go on, I'm very serious about this. This guy knows what an RUU is. That's saying something when it comes to CS!

Alright here's what you need to know. The HTC EVO V 4G DOES have a SOFTWARE bug in it that causes this Error 64 Class 2 bug, and it is directly related to the fact that this phone was not designed for Virgin Mobile's specific network. The problem has nothing to do with "cell tower outages." All of that, and I mean all of that, if CS tells you that's related, is BULL. The phone has a software bug that is currently being worked on by HTC themselves. The worst part of all this is that this guy specifically said that the likelihood of the bug being fixed within the next 3 weeks (the end of my billing cycle, 8/20 for me) is slim to none. Thus, I will be selling my EVO and never looking back, never to touch VM ever again. This is bad business, bad practice, and poor planning. Don't you just wish more companies would at least do a serious field trial before actually releasing bugged out software? I sure do, and they probably didn't even bother. So now you know. Once again, this is definitive, and I just got off the phone with these guys less than an hour ago. There's not much you can do if you get this bug as it is related to the ROM (the guy I talked with even used the acronym ROM, so I kinda have to believe what he's saying here). Thanks for your attention guys, I wanted to make this a new thread so people would start seeing it, so spread the word. You'll have to either get out now while you can if you need the phone for important business, or wait it out, but don't hold your breath for an update within the next month, though.

I for one will be porting my number to T-Mobile prepaid @ $30 a month and add minutes whenever necessary, with the fabulous and all-powerful Jelly Bean loaded Samsung Galaxy Nexus. I'm done with this VM garbage.

 

[hchen42]

For everyone who has had the Radio Interface error and even those of you who don't, I just learned some very valuable information directly from an HTC Escalations Department rep by phone. Before you go on, I'm very serious about this. This guy knows what an RUU is. That's saying something when it comes to CS!

Alright here's what you need to know. The HTC EVO V 4G DOES have a SOFTWARE bug in it that causes this Error 64 Class 2 bug, and it is directly related to the fact that this phone was not designed for Virgin Mobile's specific network. The problem has nothing to do with "cell tower outages." All of that, and I mean all of that, if CS tells you that's related, is BULL. The phone has a software bug that is currently being worked on by HTC themselves. The worst part of all this is that this guy specifically said that the likelihood of the bug being fixed within the next 3 weeks (the end of my billing cycle, 8/20 for me) is slim to none. Thus, I will be selling my EVO and never looking back, never to touch VM ever again. This is bad business, bad practice, and poor planning. Don't you just wish more companies would at least do a serious field trial before actually releasing bugged out software? I sure do, and they probably didn't even bother. So now you know. Once again, this is definitive, and I just got off the phone with these guys less than an hour ago. There's not much you can do if you get this bug as it is related to the ROM (the guy I talked with even used the acronym ROM, so I kinda have to believe what he's saying here). Thanks for your attention guys, I wanted to make this a new thread so people would start seeing it, so spread the word. You'll have to either get out now while you can if you need the phone for important business, or wait it out, but don't hold your breath for an update within the next month, though.

I for one will be porting my number to T-Mobile prepaid @ $30 a month and add minutes whenever necessary, with the fabulous and all-powerful Jelly Bean loaded Samsung Galaxy Nexus. I'm done with this VM garbage, done!

I concur with Metal. HTC admitted to me there's a software issue. I filed an unsatisfactory HTC support survey last week. HTC called me today and acknowledged there's a software bug. I asked for an ETA on this issue, and he's not sure and won't promise anything. Then I told him, if you can't fix the issue, how can I be "satisfied"? They can't even provide an ETA.

 

[metal571]

I concur with Metal. HTC admitted to me there's a software issue. I filed an unsatisfactory HTC support survey last week. HTC called me today and acknowledged there's a software bug. I asked for an ETA on this issue, and he's not sure and won't promise anything. Then I told him, if you can't fix the issue, how can I be "satisfied"? They can't even provide an ETA.

In fact, the guy I talked to said that they can't provide an ETA because it's actually policy for them not to. They can only give you two answers; 1. they are working on it, or 2. it is currently rolling out. HTC isn't known to give release dates on updates anyway, but at least those who have to stick with the phone will eventually get an update. To add to that, they told me it's most likely going to be an OTA update. My rep said that if they don't release the update OTA, it'll be an RUU.

 

[lordj]

I for one will be porting my number to T-Mobile prepaid @ $30 a month and add minutes whenever necessary, with the fabulous and all-powerful Jelly Bean loaded Samsung Galaxy Nexus. I'm done with this VM garbage, done!

That's what I did, and I couldn't be happier. Much better device, much better network.

 

[EarlyMon]

How can this phone not be designed for this network when it was designed for the Sprint network?

Hope they get this sorted out soon.

 

[metal571]

How can this phone not be designed for this network when it was designed for the Sprint network?

Hope they get this sorted out soon.

I guess there are fundamental differences between Virgin Mobile's shared timeslices of the network and Sprint's main part of the bandwidth? I don't know this is pretty stupid, I totally agree.

 

[hchen42]

How can this phone not be designed for this network when it was designed for the Sprint network?

Hope they get this sorted out soon.

I don't think HTC got it right from the beginning. Search "radio interface resource shortage" on google, you'll see this has been an issue since last year with Evo 3D, Evo 4G mostly. There are other makers/phones, but overwhelming majority problems are with Evo 3D and Evo 4G. I narrowed the search date down to the past week, and there are reports not just within my area, but through out the US. They are reported by Sprint users as well.

 

[Droidula]

Thank you for the update. Now I have to think about whether or not to keep this phone. This is my third phone and second carrier switch this year. It's getting a bit ridiculous. I almost feel like getting a "normal" plan. Almost. I wonder what the chances are of them fixing this at all? As hchen42 said above, this problem has plagued those on Sprint with the 3D as well. So I wonder what he meant about the issue being a problem with the design for Virgin. I really hope they create a fix soon. Tmobile doesn't work for me because of the low minutes, and the more expensive plan has 100 mb regular speed data before you're throttled. (WTF.) If HTC hasn't even fixed the 3D yet, what are the chances of them fixing the V. If they're really working on it. What to do, what to do.

 

[metal571]

Thank you for the update. Now I have to think about whether or not to keep this phone. This is my third phone and second carrier switch this year. It's getting a bit ridiculous. I almost feel like getting a "normal" plan. Almost. I wonder what the chances are of them fixing this at all? As hchen42 said above, this problem has plagued those on Sprint with the 3D as well. So I wonder what he meant about the issue being a problem with the design for Virgin. I really hope they create a fix soon. Tmobile doesn't work for me because of the low minutes, and the more expensive plan has 100 mb regular speed data before you're throttled. (WTF.) If HTC hasn't even fixed the 3D yet, what are the chances of them fixing the V. If they're really working on it. What to do, what to do.

Two of my fellow computer engineering major friends who I just graduated with had the 3D. They never complained once about it. In my opinion the Sprint 3D and EVO only have this problem when there is legitimately a problem with a tower or if they are not activated properly. This phone will always do this. Always, because it is a software problem causing what appears to be a network issue, but it's the software inducing it, if that makes any sense. There's nothing inherently wrong with the network.

 

[Rolo42]

I found the same and that is why I'm skeptical of htc (or anyone) working on it at all.

Thanks for posting their response; I think I'm going shopping.

 

[hchen42]

Thank you for the update. Now I have to think about whether or not to keep this phone. This is my third phone and second carrier switch this year. It's getting a bit ridiculous. I almost feel like getting a "normal" plan. Almost. I wonder what the chances are of them fixing this at all? As hchen42 said above, this problem has plagued those on Sprint with the 3D as well. So I wonder what he meant about the issue being a problem with the design for Virgin. I really hope they create a fix soon. Tmobile doesn't work for me because of the low minutes, and the more expensive plan has 100 mb regular speed data before you're throttled. (WTF.) If HTC hasn't even fixed the 3D yet, what are the chances of them fixing the V. If they're really working on it. What to do, what to do.

I am going to wait until end of August and see. Evo 3D will have an update soon. Assuming it is not delayed, then I'll see what happens. If I don't see much complain on Sprint forum, then an update is promising.

 

[doboy]

Since people with HTC One V don't seem to have this issue, hopefully HTC will find a way to fix it on the Evo V. I'll stick with it for few more months until iPhone 5 or next Nexus line is released.

 

[EarlyMon]

I don't think HTC got it right from the beginning. Search "radio interface resource shortage" on google, you'll see this has been an issue since last year with Evo 3D, Evo 4G mostly. There are other makers/phones, but overwhelming majority problems are with Evo 3D and Evo 4G. I narrowed the search date down to the past week, and there are reports not just within my area, but through out the US. They are reported by Sprint users as well.

I own a launch-day Evo 3D on Sprint, just recently deactivated it, after a full year of use.

Never once gave me a lick of 3G trouble (except for the broken lemon that came out of the first box, LoL) and WiMax worked well enough in any of the cities that I traveled to that had it. Also, closely managed our 3D forum here for about 8 months. This is all news to me.

Same story on the Evo 4G I had from its launch through the 3D launch.

Not saying that there isn't an issue today, just saying, I am a little hard pressed on buying the corporate excuse.

Anyway, I don't pretend to know, just saying, hope they get this sorted out soon.

 

[metal571]

I own a launch-day Evo 3D on Sprint, just recently deactivated it, after a full year of use.

Never once gave me a lick of 3G trouble (except for the broken lemon that came out of the first box, LoL) and WiMax worked well enough in any of the cities that I traveled to that had it. Also, closely managed our 3D forum here for about 8 months. This is all news to me.

Same story on the Evo 4G I had from its launch through the 3D launch.

Not saying that there isn't an issue today, just saying, I am a little hard pressed on buying the corporate excuse.

Anyway, I don't pretend to know, just saying, hope they get this sorted out soon.

I've heard similar stories. It's just VM's 3D that's really having a major issue here. Stupid stuff...again lack of test engineering. Gotta love modern systems engineering where just about nobody cares about, well, anything that matters.

I for one, just bought the Nexus, and man am I excited.

 

[EarlyMon]

I've heard similar stories. It's just VM's 3D that's really having a major issue here. Stupid stuff...again lack of test engineering. Gotta love modern systems engineering where just about nobody cares about, well, anything that matters.

I for one, just bought the Nexus, and man am I excited.

Congratulations on the new phone!

I hate this whole QA situation in our industry.

I blame marketing, they run things and set engineering constraints.

Anyway, fwiw, I take it that folks have tried a factory data reset and the problem remains?

Sorry for being out of the loop here, just wanting to help if I can.

 

[metal571]

Congratulations on the new phone!

I hate this whole QA situation in our industry.

I blame marketing, they run things and set engineering constraints.

Anyway, fwiw, I take it that folks have tried a factory data reset and the problem remains?

Sorry for being out of the loop here, just wanting to help if I can.

We've tried a lot more than that. There is a way to clear the EPST for this phone with a special code typed into the dialer so that the phone reactivates itself upon reboot. It seems to help, but the problem returns every single time regardless. It's ridiculous...

 

[Faydes]

I have never had the issue all of you are talking about...not once.

 

[metal571]

I have never had the issue all of you are talking about...not once.

Count yourself as lucky buddy...lol. It's a software flaw, it should be in every single EVO V available right now.

 

[raynoldsk]

I have never had the issue all of you are talking about...not once.

Me, either.

 

[The MANdroid]

Me, either.

OK..but how long have you had your phone?? This is for BOTH guys that haven't had the problem.

 

[hchen42]

For those without problem, could you do me a favor? Could you text to your google voice account number or a number which accept text? First message being the time of your text, 4 characters, ie 0545 (5:45). Next message if it's still 5:45, text "5452", then next message "5453". If time changes... I usually get the problem at roughly 4th to 5th messages. If you can achieve 10 texts in succession within 1 minute, then I am 99% sure your phone doesn't have a problem.

If you ended up having the problem. Before doing any prl/profile update, could you try to call your cell from another number and see if the Evo V 4G rings?

TIA.

 

[OctopusOptimus]

I still get the radio issue, but I've found the best way to fix it is to simply restart whenever I get it. This fixes it usually for a few days. At first it only fixed it for a few hours, but now it goes days without giving me the error. As soon as I see the error, just reboot the phone and not only does everything work fine but it even automatically sends the messages that wouldn't send. I don't have to retype them. I know this isn't a proper fix but its the best there is.

 

[Leslie Ann]

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.

 

[metal571]

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.

I remember mentioning that the Sprint users that flashed our firmware had the same issue as us somewhere else, so that's definitely true. Wasn't aware the PRI had anything to do with it. That fix you mentioned appears similar to the one I posted, since mine also forces the phone to reactivate...and the results are similar, problems again after a few hours potentially. Jeeze I'm never coming back to this company again, they blew it for me this time.

 

[Leslie Ann]

The more I look, the more likely it seems to be the PRI, the question is, can we use theirs (most likely yes).

I'm not that scared to flash it, I'm scared of the flashing process, which seems pretty intense. If it was a cheaper phone I would have done it already.