I'm not sure what the problem could be.
When I first wipe the phone everything is fine but as soon as I put a ROM on there I lose the ability to receive phone calls. Every call goes straight to voicemail. At first I thought it was an app causing the problem (YouMail, Timeriffic...). I uninstalled those but still no calls. I did a wipe, phone rings. Put a ROM (no apps yet), straight to voicemail. Right now I'm using Damage 1.5 but that doesn't make a difference because it happens with Fresh & Darch too.
Is there a common setting somewhere that changes and could be interrupting my ability to get calls?
edit.....
Now that I think about it, this all started yesterday when I changed that CDMA auto thing. But that setting doesn't keep after restarts right? And wiping the phone should have cleared that anyway right?
trindy said:
I'm not sure what the problem could be.
When I first wipe the phone everything is fine but as soon as I put a ROM on there I lose the ability to receive phone calls. Every call goes straight to voicemail. At first I thought it was an app causing the problem (YouMail, Timeriffic...). I uninstalled those but still no calls. I did a wipe, phone rings. Put a ROM (no apps yet), straight to voicemail. Right now I'm using Damage 1.5 but that doesn't make a difference because it happens with Fresh & Darch too.
Is there a common setting somewhere that changes and could be interrupting my ability to get calls?
edit.....
Now that I think about it, this all started yesterday when I changed that CDMA auto thing. But that setting doesn't keep after restarts right? And wiping the phone should have cleared that anyway right?
Click to expand...
Click to collapse
One word:
nandroid
That was the first thing I did
I've nandroided (is that a word?) all the way back to January. That's all I've done since this started yesterday. Wipe... New image. Wipe... old backup. Wipe, older backup.
I'm about to smash this thing lol
go back into the test menu and make sure your phone isn't set to evdo only tht will keep calls from, coming in
You only get to ask one question per thread, so I'll answer the one in your title.
Yes.
bcnice20 said:
go back into the test menu and make sure your phone isn't set to evdo only tht will keep calls from, coming in
Click to expand...
Click to collapse
It says I'm on GSM auto (PRL). I'm afraid to change it again. I think thats how I got into this mess in the first place
gthing said:
You only get to ask one question per thread, so I'll answer the one in your title.
Yes.
Click to expand...
Click to collapse
Gee thanks! lol
After living like this for 2 days I'm thinking it's not so bad. I changed my voicemail message to say I'm having a problem, send me a text and I'll call them back. I dont have angry ex's calling, no kids needing money, no mother complaining. They text me! And if I want to listen to it I'll call them back. It's kinda quiet. I think I like it
I'll put it back to stock and take it to Sprint tomorrow. Let them deal with it.
I have been having issues with my Hero lately, and going through the Tech Support/Store/Retention phone transfers has made me pretty pissed off. (I was hung up on by 2 supervisors, and I was not even talking to him angrily) I hope that one of you guys who I helped out at one point or another with anything could help me out with my phone issues and figure out where to go from here with my phone/account.
If you are a rep/tech from Sprint, I would really appreciate a reply or pm. Thanks in advance guys
Dan
1. We can't hang up on people, or we get fired.
2. What's up bro?
DirtyShroomz said:
1. We can't hang up on people, or we get fired.
2. What's up bro?
Click to expand...
Click to collapse
Yeah the hanging up thing was weird, I was talking and then all of a sudden I hear a click and the dial tone after that. I called from my corded home phone to make sure I didn't lose signal.
regaw_leinad said:
Yeah the hanging up thing was weird, I was talking and then all of a sudden I hear a click and the dial tone after that. I called from my corded home phone to make sure I didn't lose signal.
Click to expand...
Click to collapse
Its our phone system, sometimes it sucks. What's going on?
DirtyShroomz said:
Its our phone system, sometimes it sucks. What's going on?
Click to expand...
Click to collapse
Sent you a LOOONNNNGGGG pm lol sorry bout the length haha
DirtyShroomz said:
1. We can't hang up on people, or we get fired.
2. What's up bro?
Click to expand...
Click to collapse
Actually I am pretty sure I have been hung up on blatantly AND purposely requeued, companies wouldnt pull a trigger like that after a hang up. I worked for sprint -- Ive seen it
Tipharet said:
Actually I am pretty sure I have been hung up on blatantly AND purposely requeued, companies wouldnt pull a trigger like that after a hang up. I worked for sprint -- Ive seen it
Click to expand...
Click to collapse
I don't know when you worked for Sprint but we have a "release" button to drop calls. If we hit it, we get pulled up on a report and the call is listened to see why the release button was hit I WORK for sprint
Ok guys, nevermind. I am selling my Hero.
http://forum.xda-developers.com/showthread.php?t=712250
Dude, what's the issue? I don't know if I can help. I used to be an AT&T Retention CSR and I'm an ex-military comms tech.
Good bye regaw-mod for good?
Sent from my HERO200 using XDA App
radxcoresteven said:
Good bye regaw-mod for good?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I hope not
Sent from my HERO200 using XDA App
Seriously, what's up?
I'd be afraid to buy your phone if you've got such problems that you're willing to dump it because of them.
Inquiring minds want to know!
Well, it was more of me trying to get an EVO using the known problems of the Hero lol. My phone is great. my bad
regaw_leinad said:
Well, it was more of me trying to get an EVO using the known problems of the Hero lol. My phone is great. my bad
Click to expand...
Click to collapse
Did they finally let you upgrade?
Hey, I've got problems if any Sprint Techie would please listen to me!!! I've asked for help from a couple of developers and all I get is ignored and told, "Sorry dude."
Two weeks ago, I themed using MM instead of the usual signed zips. Since then, my phone completely freezes/black screen every single time I get an incoming call, requiring me to pull the battery and hard reboot. No buttons work/black frozen screen until I fully reboot. Everything else works perfectly except for incoming calls. I can't have this!
I pulled a logcat (found nothing), RUU'd, re-rooted, reflashed the ROM (Flipz 2.1d), wiped the SD, etc. Still happens and am now so ticked I'm about to auction this POS and get me the EVO too! I took it to a Corporate Sprint Store 25 miles away and after I had to show the morons where the 'on' button was on the Hero (yeah, seriously, I did), they told me I'd be without a phone til after 7/5 while they work on it, because of the holiday (I can't, I use my phone for work!!!).
All I themed was a revised rosie killing off the top-bar clock & battery signal meter, and another hiding the text under homepage apps.
WTH??? Could someone please, please help?
jedijackie said:
Hey, I've got problems if any Sprint Techie would please listen to me!!! I've asked for help from a couple of developers (Chi...) and all I get is ignored and told, "Sorry dude."
Two weeks ago, I themed using MM instead of the usual signed zips. Since then, my phone completely freezes/black screen every single time I get an incoming call, requiring me to pull the battery and hard reboot. No buttons work/black frozen screen until I fully reboot. Everything else works perfectly except for incoming calls. I can't have this!
I pulled a logcat (found nothing), RUU'd, re-rooted, reflashed the ROM (Flipz 2.1d), wiped the SD, etc. Still happens and am now so ticked I'm about to auction this POS and get me the EVO too! I took it to a Corporate Sprint Store 25 miles away and after I had to show the morons where the 'on' button was on the Hero (yeah, seriously, I did), they told me I'd be without a phone til after 7/5 while they work on it, because of the holiday (I can't, I use my phone for work!!!).
All I themed was a revised rosie killing off the top-bar clock & battery signal meter, and another hiding the text under homepage apps.
WTH??? Could someone please, please help?
Click to expand...
Click to collapse
I don't think theming with metamorph could potentially harm your phone in a way that an RUU couldn't correct. Have you used an overclocked kernel or done anything that could potentially break your phone's hardware? If it happens when you receive an incoming call, I'd tend to think there's something going on with the cellular radio. Do you have any issues with data connection or receiving SMS? Any other issues at all?
Nope, absolutely no other issues at all. Data, SMS, all fine.
jedijackie said:
Nope, absolutely no other issues at all. Data, SMS, all fine.
Click to expand...
Click to collapse
Does it happen EVERY time you get a call or with less frequency? Are you using a non-standard PRL? I suppose there could be 100000 different things making your phone do that, but I just don't see MM doing it.
Then again I've been wrong before.
No, when I have it plugged in on USB or straight charger, I'll occassionally get the incoming call. Not always, but occassionally. Once today it rang through, then I got 8 lock ups, all on incoming.
But when the phone is off the charger, I won't get the call at all. It completely locks & goes black even before I know there's an incoming call. I only find out when I check the phone or hear the BT shut off in my ear. Then I'm forced to pull the charge & reboot, only finding out 5-10 min later that I missed a call and have a VM message.
I had to call it myself to find out that it's locking down on all incoming calls, because at first I just thought it was doing random lock ups. But, no, it's only on incoming calls.
I've had some weirdness with incoming calls recently, but that's due to forcing my clock speeds way low when the screen is off with overclock widget.
If you successfully RUU your phone and you still can't receive calls, my money is that it's busted.
Anyone else have any ideas?
Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840
Hello guys
Ran into a snafu yesterday, clicked home a N6 demo-ex from one of the internetstores here, it was cheap and I've always wanted one. Of course it came with a pre-unlocked bootloader and everything else you'd expect from a used Nexus, but I wasn't too bothered about that, I would have unlocked it myself anyways. Flashed MM on it as soon as the images were available. I played around with it for a few more hours, then late last night I decided I should move my simcard to the N6 and try Speedtest and a few other goodies. Speedtest went just fine, got the usual 64 Mbit over LTE, then .. I'll call my automated bank just to check the earpiece and speakers. "Dial .... call ended". Try again. "Dial... call ended". Put the simcard back into my Nexus 5, dialed the same number, worked perfectly. Back into the N6, same number, it dials, then just as it's supposed to start ringing, "call ended". Has anyone got any ideas as to what could be wrong here?
Done so far to find the error:
*Reboot *duh*
*Reflash MM
*Flashed 5.1.1, thinking it was a new modem and my simcard didnt like it. Sim is about 2 weeks old by the way.
*A couple of factory resets, just to be sure
This is the very last Nexus 6 these guys had on the shelves so I would really, really rather not have to return it but of course a phone that you can't use for phonecalls .. I already own a Nexus 7, don't need a miniversion of it. Bright ideas or even far fetched guesses appreciated!
Hey bud, I had a similar issue with my phone as well and the way to fix it is by rebooting exactly 6 times in a row....literally. Power on, power off power on power off etc........ Ive encountered that issue several times, it usually happens when i left my phone die and then reboot after full charge. I could only use data, no voice/text and sometimes it would be backwards, no data, voice text only
Hey all - I did the Sunshine bootloader unlock/root/5.1 update, and the phone's been running fantastically, but now it's not receiving all incoming calls. Some do get through but many don't; I'll either get a voicemail or frustrated people will tell me in person that I'm not calling them back.
So I've just done a test by calling my phone from a landline; it rings three times, then does the quicker, shorter ring like just before it goes to voicemail; then, my cell phone starts ringing and rings four times before going to voicemail.
I restarted the phone when I first became aware of this, so it appears that at least I'm getting some calls now; any idea what may be up?
Many, many thanks - this site is absolutely fantastic. Who could quantify the difference this place and these people have made for countless thousands?
thetastycat said:
Hey all - I did the Sunshine bootloader unlock/root/5.1 update, and the phone's been running fantastically, but now it's not receiving all incoming calls. Some do get through but many don't; I'll either get a voicemail or frustrated people will tell me in person that I'm not calling them back.
So I've just done a test by calling my phone from a landline; it rings three times, then does the quicker, shorter ring like just before it goes to voicemail; then, my cell phone starts ringing and rings four times before going to voicemail.
I restarted the phone when I first became aware of this, so it appears that at least I'm getting some calls now; any idea what may be up?
Many, many thanks - this site is absolutely fantastic. Who could quantify the difference this place and these people have made for countless thousands?
Click to expand...
Click to collapse
its not an issue with the bootloader being unlocked or anything. I think its just network issues that verizon will have cleared up before too long
I wondered that - coincidences happen more often that I usually realize! Thanks.
I had this exact same issue about a month before rooting and unlocking my bootloader. After several factory resets I resorted to calling VZW tech support. The dude spent about an hour on he phone with me trying tons of things before he was able to fix it. If I remember correctly he had to send an update or something to my SIM, but I'm really not sure any more since it was months ago.
Sent from my XT1254 using XDA Free mobile app
Thanks cstone - I'm not aware of the issue happening since I posted but if it does I will absolutely call VZ! Thank you very much.
I am having the same issue. Did calling verizon fix your issue?