Related
Hi all,
I've been trying not to let this bother me too much but it just does. Why, when we've come so far with mobile technology, are basic things like this still not done properly?! specifically:
1. my hero doesn't actually start ringing for at least 3 rings on the callers side? this it might not seem much but is almost 10 seconds that the caller is waiting before I know about it. By the time I do and get to the phone I will almost miss the call.
2. this may be a handcent problem but I don't get the trackball flashing 2-3 seconds and the actual audio notification for 5-10 seconds.
-
l just want these things to feel instant and zippy. Is that too much to ask? I don't think so considering this handset can show me which constellation I'm looking at and that there is a 'titty/tapas bar 500 yds that way'.
Is there anything I can do to improve these fustrations?
Don't get me wrong, I think the handset is generally great but don't want a 'Jack of all trades, master of nothing'.
R,ant over.
Orangepeel.
Sent from my T-Mobile_G2_Touch using the XDA mobile application
powered by Tapatalk
Hi,
I get the same problem with my phone not registering a call for atleast 10 seconds and usually missing calls, it's very annoying!
Something I've found that helped me was to prolong the time it takes before the caller is sent to your voicemail i.e. your phone SHOULD ring for longer before the caller gives up...
Search the forums for the code you need to enter to prolong the time period (I think it's 30 seconds).
Hope this helps...
It depends on the rom your running.
For example the latest VillainRom rings instantly now but always used to be quite delayed.
the handset is very well aware of the incoming call, it just takes a few seconds to ring and display the call. when you are listening to music you will notice that it stops, then after a few seconds it will start to ring. try to use .ogg ringtones, apperantly that makes it better.
Lennyuk said:
It depends on the rom your running.
For example the latest VillainRom rings instantly now but always used to be quite delayed.
Click to expand...
Click to collapse
I'm using Modaco 3.2 and have always had this issue since upgrading from the Stock rom months ago!
Are you saying that the latest Villain ROM (based on 2.1) fixes this issue?
So in theory this problem should be rectified once 2.1 is officially released??!
bunt83 said:
I'm using Modaco 3.2 and have always had this issue since upgrading from the Stock rom months ago!
Are you saying that the latest Villain ROM (based on 2.1) fixes this issue?
So in theory this problem should be rectified once 2.1 is officially released??!
Click to expand...
Click to collapse
yes it seems to be fixed in VillainRom 5.2 or its certainly a lot better than it was.
This fix was something the Dev (Nathan) did I think so official 2.1 may still have the problem
Lennyuk said:
yes it seems to be fixed in VillainRom 5.2 or its certainly a lot better than it was.
This fix was something the Dev (Nathan) did I think so official 2.1 may still have the problem
Click to expand...
Click to collapse
Interesting!
I guess I'll wait until 2.1 is released and see if that fixes the problem otherwise I'll be switching to the Villain ROM based on the official 2.1!
Cheers for the info Lenny...
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
I am having the same issue on the stock 2.1. The only answer I have gotten from HTC is hard reset. But I have already done this twice. So I am going to root my phone and hopefully get rid of this problem. It only started after I updated to 2.1.
BigDiz007 said:
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
Click to expand...
Click to collapse
Silly question perhaps, but are you completely wiping data and dalvik cache before flashing any of these 2.1 ROMs? Sometimes this happens if you don't do a full wipe before installing new ROMs.
I'm having the same issue, and I did a full wipe, installed several different roms and finally settled on aloysius
i've had the same problems with every 2.1 rom with the exception of darchdroid.
for me it usually happened after i placed a phone call and tried to hang up
and yes everything was wiped before flashing....
im having the same issue i knew i wasnt the only one, has anyone figured out why this is???
I am getting that error trying to install ZenEXP.
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
I do not have any issues that have been listed here. I am running fresh rom and everything is working great.Just wanted to make sure all views arebeing represented in this thread
hmmm....had a thought, did the phone get really hot when it happened....cause that is what happened when i was on fresh....
NomadHellfire said:
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
Click to expand...
Click to collapse
You won't be able to go back to the stock 1.5 original. That has been tried already by a bunch of developers here and it didn't work. You would probably be able to flash a 1.5 ROM (browse way back into the Development pages forum here), but since you had stock 2.1, there's no way for you to go back to stock 1.5.
For all the rest of you, not sure why you are getting random reboots, but as mentioned in the previous post, sometimes the Heros do that when they get overheated or overworked. It would be best to root and start with a very stable, non-overclocked ROM. A couple of the most stable and reliable stock-based ROMs here in this section are DamageControl 2.09.1 and nfinitefx45's Stock 2.27.651.6. I recommend you try either of those out if you haven't already -- hopefully that will fix/solve some of your troubles.
Please report back if any if you have success or more problems with these...we want to make sure you get the help you need
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
shawnwojcik said:
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
Click to expand...
Click to collapse
Sorry, I don't understand much of the code myself. And I think a handful of our devs here who understand all that coding have already moved on to the EVO. I read your other thread too but don't know what else to suggest. Wish I could help more. You could just be one of the unlucky few who got a bad, buggy phone right out of the box.
Have you thought about just calling Sprint customer service and asking for a replacement phone? Certainly with all the trouble you're having it may be worth it. I think even if you don't have the insurance plan, a replacement phone is only around $35.
@chromiumleaf, yeah sadly i think its time for a different phone.
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
CodeMonk said:
I'm running Fresh 2.1.2 and I've been having a ton of issues with lag that I never had on Fresh 2.0d. Are people having lag issues on the official 2.1 release too? I've tried to check and see what's running when the lag is happening, and it seems consistent with an app updating itself. I'll go to the list and see that mail has 5% or twitter (not peep) is updating and at 10% or something, but nothing is ever over that and it's always just one or two apps like that and the phone is unusable until they are done.
Now I'm noticing that if my phone is just sitting on the desk and someone calls, it takes a good 5 seconds for the phone to display the screen that tells me who it is. It vibrates, waits a couple seconds, then the default ring tone starts to play, then a couple seconds later the display comes up that says who is calling.
It generally is running like ass. It did not do this before on Fresh 2.0d. I was running apps2sd on that as well as on here. It seems that the only difference between fresh 2.0d and 2.1.2 is the fact that it's now the official released rom. Are people with the official rom having the same issues??? If they are, I'm going back to 2.0d. It ran completely fine. This is starting to get on my nerves and is not the experience I want....
Click to expand...
Click to collapse
Just go back to 2.0d. I ran 2.1.2 for a very short time and I couldn't take it anymore plus you know that the sprint 2.1 has confirmed issues one of which is the sdcard
Where can I get the original 2.0d now? Can someone post a download link to it please? I'm also experiencing a lot of lag these days as well..
Here's a quote from Fresh Toast v2.1:
A note on slowness: It is coming to our attention that there are several bugs in the latest Sprint 2.27.651.5 RUU which is the official Sprint release. It doesn't surprise me that there are bugs considering our original 1.5 had plenty. The main one that we have come across is a service called com.htc.bg that sucks up your processor. This causes that phone to become extremely laggy and overall run like crap. Go read my new FAQ: Why is my Android phone running so slow? to see what you can do about it, and to report the issue. Keep in mind that this would be a Sprint bug and not Fresh Rom / Fresh Toast.
Click to expand...
Click to collapse
I think this is why we're experiencing lag, hopefully someone can find a fix for it..
EDIT: Nvm, found the link, here it is:
http://geekfor.me/new-release/fresh-20d
I think you guys are right. I've been toying with the idea of using Fresh Toast to get overclocking, but 2.0d just worked for me and I had no real issues other than keyboard lag.
Are you guys running w/ Auto Killer (or alternative TK) or no? I've been running FT w/ AutoKiller set to Extreme, with max time between boots having been about 48 hours, and haven't seen any significant slowdown the longer the phone's been on..
I've tried pretty much every Froyo ROM that's been released, stock and custom, and have yet to find one that doesn't have Bluetooth issues. It seems to me that the "added Bluetooth functionality" of Froyo has caused problems that have yet to be isolated.
I didn't have any connection issues with any Eclair. It sucks, because I keep bouncing back and forth when a new Froyo ROM is released hoping I won't have these same problems. But I always do!
By the way, the problems are with my hands-free system in my car-- where it will not reconnected without turning on and off Bluetooth. It will also lose it's pairing information, and need to be re-paired on occasion. My wife's Incredible has zero problems in the same car; as does the Epic when it's running Eclair.
The reason I'm hoping for a Froyo release that doesn't have Bluetooth issues is because I do like some of the issues Froyo offers, but having working Bluetooth is more important.
I've had that issue before but SFR 1.1.0 w/ Vision kernel has been flawless for me. I've been running both since the first day of release.
My issue with bluetooth is that unless I hang up with the special 'hang up' button on my dash panel (the other party hangs up first, or the call drops, or etc) then my car thinks it is still on a call and won't release the audio back to music.
The new bonsai rom doesn't seem to have the problem. If you are having the problem then wipe data in cwm. Sometimes you have a corrupt data carryover
Sent From My Evo Killer!!!
JRider said:
I've tried pretty much every Froyo ROM that's been released, stock and custom, and have yet to find one that doesn't have Bluetooth issues. It seems to me that the "added Bluetooth functionality" of Froyo has caused problems that have yet to be isolated.
I didn't have any connection issues with any Eclair. It sucks, because I keep bouncing back and forth when a new Froyo ROM is released hoping I won't have these same problems. But I always do!
By the way, the problems are with my hands-free system in my car-- where it will not reconnected without turning on and off Bluetooth. It will also lose it's pairing information, and need to be re-paired on occasion. My wife's Incredible has zero problems in the same car; as does the Epic when it's running Eclair.
The reason I'm hoping for a Froyo release that doesn't have Bluetooth issues is because I do like some of the issues Froyo offers, but having working Bluetooth is more important.
Click to expand...
Click to collapse
None of the Bluetooth issues currently present in EC05 are ROM related. The problem you are describing occurs usually after ext4 conversion or switching from one ROM to another. I haven't heard anyone report this type of issue that is running stock EC05.
I posted a solution in that has helped several folks and myself who were experiencing similar issues. Try this and let me know how it goes.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
musclehead84 said:
The new bonsai rom doesn't seem to have the problem. If you are having the problem then wipe data in cwm. Sometimes you have a corrupt data carryover
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
I'm currently running Bonsai 4.0 and it's seem to have been the worst. Are you telling me the they've done something in their latest release that fixes this issue? I don't see anything in their release notes that mentions this.
And trust me, I wipe data in CWM every time I try a new ROM.
mattallica76 said:
None of the Bluetooth issues currently present in EC05 are ROM related. The problem you are describing occurs usually after ext4 conversion or switching from one ROM to another. I haven't heard anyone report this type of issue that is running stock EC05.
I posted a solution in that has helped several folks and myself who were experiencing similar issues. Try this and let me know how it goes.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Click to expand...
Click to collapse
Interesting... I seemed to have the problem with stock EC05 as well. I Odin'd to D18, then ran the stock update.zip for EC05. I wiped as well.
I'm going to look at your post right now.
JRider said:
Interesting... I seemed to have the problem with stock EC05 as well. I Odin'd to D18, then ran the stock update.zip for EC05. I wiped as well.
I'm going to look at your post right now.
Click to expand...
Click to collapse
Ok, I just took a look. Wouldn't an Odin to D18 and/or a wipe delete this corrupt data in the data/misc/bluetoothd anyway?
JRider said:
Ok, I just took a look. Wouldn't an Odin to D18 and/or a wipe delete this corrupt data in the data/misc/bluetoothd anyway?
Click to expand...
Click to collapse
Yes, they both would, unless you restored it with Titanium or Nandroid/CWM. If you still have issues after trying the method in my post, you might want to double check your baseband version to make sure it's EC05. The Bluetooth is part of the modem. You might try reflashing the EC05 modem as well.
mattallica76 said:
Yes, they both would, unless you restored it with Titanium or Nandroid/CWM. If you still have issues after trying the method in my post, you might want to double check your baseband version to make sure it's EC05. The Bluetooth is part of the modem. You might try reflashing the EC05 modem as well.
Click to expand...
Click to collapse
I've never restored anything after reflashing. Coming from Windows Mobile ROM flashing taught me it's never a good idea to do.
I'm definitely on EC05 baseband. I've also tried reflashing the EC05 modem with Odin as well. At first I thought that fixed it for me. But a day later, the problems were back.
Again, whenever I flash back to an Eclair ROM, I don't experience any of these problems. So I'm more opt to think the issue lies in Froyo's "updated bluetooth" features.
JRider said:
I've never restored anything after reflashing. Coming from Windows Mobile ROM flashing taught me it's never a good idea to do.
I'm definitely on EC05 baseband. I've also tried reflashing the EC05 modem with Odin as well. At first I thought that fixed it for me. But a day later, the problems were back.
Again, whenever I flash back to an Eclair ROM, I don't experience any of these problems. So I'm more opt to think the issue lies in Froyo's "updated bluetooth" features.
Click to expand...
Click to collapse
EB13/EC05 definitely has a couple BT issues, but the one your describing has not happened on my stock Epic and only happened on my rooted one under the conditions I described in previous posts (and was fixed). We use both phones with several BT devices pretty extensively. If data wipes and reflashes haven't worked for you, and your issue is only with one BT device, you might try clearing the memory of the device. Also you should see if you have issues pairing with other devices.
mattallica76 said:
EB13/EC05 definitely has a couple BT issues, but the one your describing has not happened on my stock Epic and only happened on my rooted one under the conditions I described in previous posts (and was fixed). We use both phones with several BT devices pretty extensively. If data wipes and reflashes haven't worked for you, and your issue is only with one BT device, you might try clearing the memory of the device. Also you should see if you have issues pairing with other devices.
Click to expand...
Click to collapse
Thanks for all of your input!
Like I said in my original post, my wife's Incredible works with the same car without any issues. I've also tried "factory resetting" and erasing all paired devices in the car. And it always ends up with the same issue- any Froyo ROM I run has problems. Like I said, I've tried several, with wipes and Odin to stock, and stock EC05. All of them have the same problems.
I'm definitely not the only person who's experiencing the issues I'm describing. If you read through this other thread at another forum (http://androidforums.com/epic-4g-su...82-bluetooth-problems-after-froyo-update.html) you'll see a couple people describing the exact same problems. One user even talks about the phone showing that it's still connected to the device even after the car is shut off. And the only way to disconnect is turn off bluetooth. Another user talks about the car randomly reporting it as "BCRM Device" instead of what the Bluetooth device name is. Both of these problems, I've had as well.
Trust me, if I can find the cause of this issue, or a ROM that doesn't have it, I'm willing to give it a go. I want the Froyo enhancements, just not the bluetooth issues.
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yes, it does.
Actually, one of the things Froyo does better with handsfree in the car is this feature. Eclair won't sync my Exchange contacts for some reason. It will only sync "Phone Contacts". It also doesn't handle the recent call log as well either. For some reason it will show sent emails and texts in my call history in the car. With Froyo, neither of these problems exist. But that means nothing when there's a fundamental issue with bluetooth itself.
Why do you ask?
JRider said:
Yes, it does.
Actually, one of the things Froyo does better with handsfree in the car is this feature. Eclair won't sync my Exchange contacts for some reason. It will only sync "Phone Contacts". It also doesn't handle the recent call log as well either. For some reason it will show sent emails and texts in my call history in the car. With Froyo, neither of these problems exist. But that means nothing when there's a fundamental issue with bluetooth itself.
Why do you ask?
Click to expand...
Click to collapse
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I actually went back to DI18 yesterday, rooted, removed bloatware, and I haven't had a single problem with hands-free Bluetooth in my car.
Again, there's definitely issues with Bluetooth in every version of Froyo. Disabling certain basic features (that other phones have been successfully doing for years) just to get it to work is not an option for me.
For now, I'll run Eclair, and hopefully these issues are resolved at some point.
I will totally agree with the OP Stock 2.1 was fine with my Parrot BT system. Since 2.2 Ive tried a bunch of roms and finally back to bone stock AND i still get a ton of BT issues ( disconnects,missing calls, phone is muted after calls etc etc) I miss my Palm Pre...lol
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
5111 said:
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
Click to expand...
Click to collapse
I've been running DI18 (stock and rooted) for the past two days with literally zero problems with bluetooth. I even loaded the EC05 modem to prove it has nothing to do with the modem (apparently bluetooth is part of the modem tar). So right now, I'm running Eclair DI18 with EC05 modem and bluetooth is working flawlessly.
So I will say it one more time... there is something in Froyo for the Epic that is causing bluetooth issues. It's not the kernel, it's not the modem, it's the Android OS (Froyo 2.2) that is causing the issues with bluetooth.
JRider said:
I've been running DI18 (stock and rooted) for the past two days with literally zero problems with bluetooth. I even loaded the EC05 modem to prove it has nothing to do with the modem (apparently bluetooth is part of the modem tar). So right now, I'm running Eclair DI18 with EC05 modem and bluetooth is working flawlessly.
So I will say it one more time... there is something in Froyo for the Epic that is causing bluetooth issues. It's not the kernel, it's not the modem, it's the Android OS (Froyo 2.2) that is causing the issues with bluetooth.
Click to expand...
Click to collapse
JRider- Just as an FYI, I am having the EXACT same problems you describe with my Moto Roadster. You aren't alone. I've tried most of what you said you've tried with no luck as well. Hope somebody finds a solution.
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
It's network related. They better pay this months bill for you. Call Sprint and find out.
Sent from my PC36100 using XDA App
I've had a similar problem lately of not getting calls. I'm not missing all of them, but at least once or twice a day, all of a sudden I'll get a nerw Voice Mail, yet the phone never rang. And, I've had people tell me that when they call, it goes straight to Voice Mail
I just attributed it to having WiFi only on, although that is just a longshot guess on my part.
Ive been unable to receive texts girl 3 days now. Anybody find a fix?
Sent from my PC36100 using XDA Premium App
what rom? if it's calkulin's evio 1.8, there's your problem.
Cm7 final
Sent from my PC36100 using XDA Premium App
dkdude36 said:
what rom? if it's calkulin's evio 1.8, there's your problem.
Click to expand...
Click to collapse
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
dschoenike said:
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
Click to expand...
Click to collapse
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
dkdude36 said:
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
Click to expand...
Click to collapse
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
dschoenike said:
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
Click to expand...
Click to collapse
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
dkdude36 said:
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
Click to expand...
Click to collapse
wish i woulda asked you guys earlier i unrooted, went back to stock, spent 4 hours in a sprint store, now have a different evo coming in from sprint on tuesday. guess ill try what you said tomorrow before doing the exchange. cant today as im not home. thank you again for all that info. really appreciate it.
derek
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
JoshuaD80 said:
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
Click to expand...
Click to collapse
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
dschoenike said:
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
Click to expand...
Click to collapse
i'm not convinced it's your fault at all. sometimes funky things happen in the back end on sprint's side.
best of luck to you!
don't think this is a rom specific issue, it's most likely the network.
I'm having the same problem on savage-zen rom rc2...
What may help is updating your radios, prl, etc. I haven't done that in a while, not too sure that it will make a significant difference though.
dschoenike said:
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
Click to expand...
Click to collapse
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
just letting you know, the pri is different than the radio, and we are talking about evio 1.8 starting problems like this for many, including me.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
dschoenike said:
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
Click to expand...
Click to collapse
If you have the time I would try my suggestion and or dkdude36 suggestion. He is correct in that the PRi is not the radio. I was in a hurry to type out the message. But I do mean the PRI, and I use the 1.77. You'll have to root the phone again, and nan-unlock. Then install a ROM and a recovery. If it doesn't work you'll have to restore it to stock before you return the phone so it will take some time to do all that. I was running Evio 1.8 for a while then one day I couldn't receive calls. I tried many things but the PRI fixed my phone. It's really up to you and how much time you have.
calkulin's evio 1.8
dkdude36 i think is right, i had the same problem a month ago, had to call *2 for help.
want ah guess what rom i was running....evio 1.8!
now i'm on Eternal Prophecy 5.8 got to read the hole thread, zero bugs!