I am a longtime CM user on AT&T. I bought a Roger's HTC Magic as soon as it came out and immediately put CM on it. I now have an Desire HD/Inspire as well as a Nook Color.
I have a question and I'm not sure if it is just me or if other people are experience this as well. Also, I do not know if it is an AT&T issue or something with CM. Anyway, here it goes....
Sometimes when I try to make a call by selecting the contact and have full signal and everything, I just get a series of constant beeps (like a busy signal almost) and the call never goes through. I can try 10 times in a row and the same thing will happen BUT as soon as I type the number in the dialer, it will immediately go through. The same scenario almost always plays out the exact same.
Does anyone else get this? If so, is it a development problem with CM, an AOSP issue, an At&T issue, or something else?
Thank you ahead of time.
Related
Hello,
I've tried searching for the problem but it seems like no one else has the same thing happening to them.
My screen freezes pretty much every other time i turn on the phone. The lock screen would show up but I can't swipe to unlock. It also happens when people call me and I have to swipe to answer the call. To fix it I have to turn the screen off and then back on and then it starts to work normally for the remainder of the time I have the phone on.
I have it fully rooted and have wiped and reflashed multiple roms (icluding original rom) but it still persists for every rom.
Does anyone have any idea what's going on? Im starting to think its a hardware problem.
I've been battling this problem too, I feel your pain. In my case the screen only locks or doesn't work correctly every so often, I would say on 1 in 5 calls. It also happens every now and then when I get texts. I tried different third party texting apps too, Handcent, Go and Chomp, all three would do it. Just like you I tried all kinds of removing of apps and widgets, different ROMs and wipes, formatting SD in case it was corrupt, different kernals and radios, even deleting and recreating contacts in case they were somehow corrupt, nothing fixed it. Finally the other week I got Sprint to send me a replacement. You know what? It did it too and it was a different HW version ( 0003 instead of the 0002 I had ). I was even able to make the new one do it with no SD or connected to any accounts such as FB or Google, and I hadn't messed with it either ( read as no rooting or anything which my previous one I had done ). I've had to get with Sprint and they have yet another one on order for me now, I really hope it does the trick. I posted on this site for advice but got almost no response, but I got quite a few on PPCGeeks. If you want to read my thread, do a search on that site for 'intermittent wake up problems' or something to that effect. End result was that everybody who read it said it was most likely hardware related and so that's the route I finally went down, but in my eyes it seems like astronomical odds that the new one is doing it as well. Good luck to you, I'll let you know if the next replacement fixes me up.
Update : I got my second replacement yesterday, turned it on and nearly cried...I've never seen such bad separation at the bottom under the soft buttons before, though I know this is a known problem with EVOs. My 0002 had it a little but my first replacement ( which was an 0003 model ) did not at all. This latest replacement is an 0003 model as well but it was stunning how bad the light leakage was. I didn't even bother trying to activate it to see if it would fix the much more important problem of not being able to answer calls though...I'm sorry if I sound like a whiner, but it's just ridiculous how bad it was and I just can't see how this could make it through manufacturing or QA. I went to a Sprint store this morning after talking to them on the phone because they said the problem had to be verified there. Following that I called them back and they are sending me yet another replacement. One of the guys at Sprint support said his EVO does this from time to time as well, I'm surprised more people don't experience it and that there are no suggestions for how to possibly go about fixing it. Uggggg....
Another Update : Well, this past Friday I finally received ( believe it or not ) replacement #3. As detailed above, #1 still exhibited this behavior and #2 I didn't even bother trying as it had the worst light leakage crack at the bottom imaginable. Anyway...#3 is doing the same thing and I'm now just about at the end of my rope as the saying goes. As before, I was able to get it to do this with stock and nothing installed. I just can't believe at this point that I could have gotten this many bad models, it has to be something else! What settings could there be on the network side that could be following me that might be making this happen? I was thinking about the stuff you get to using ## codes perhaps? The reason I mention this is because I did change one or two of those back on my very first EVO but it didn't start exhibiting this behavior until months later, do these live on the back end or on the device? I found them in the thread on XDA by a poster with the name of something to the effect of 'technofile'? His thread was originally about using Verizon PRLs on EVOs to get Verizon 3G but there were other things mentioned as well such as these codes to get to call quality settings I think. Please help, I love my EVO but if I can't reliably answer calls I'm going to have to try to get something else under the 'lemon law', probably an EPIC.
Hi, just want to start out saying that the Evo is such an amazing phone!
But.... there is this issue.
Sometimes (less then %10 of the time) and at random as far as i know, when i am making and receiving a phone call I only hear my voice in an echo. Like when you have 2 phones, you call one, and talk and listen to both at the same time. I can NOT hear anything else except my own voice, when obviously the person on the other end is talking. I have to hang up and try again. One time, this happened 4 times in a row, but usually its just once.
When I'm at home, Im connected to the Airave. Im not sure this has anything to do with it as I dont specifically remember having this issue when Im not connected to it. Ill try to remember if this happens again when im not on the Airave.
Anyone have this problem?
I am rooted and am running a Sense based rom (something thats almost pure stock Sense).
Also, on another note, is there someway to fix the calling lag? what i mean is: someone calls me, on their end it rings 3-4 times before my phone actually starts ringing. (with the GV integration it was worse, it would ring 5-6 times, sometimes go to voicemail and my phone would either just start ringing or just a voicemail notification would pop up)
If nothing can fix this, can I at least change the number of rings? Im think 10 would work.
Thanks!
Every phone I've ever had, and I've had a lot of them, at some point would ring zero to one time on my end while the caller has heard several rings. The same thing can be said about the echo. I assume there are a number of reasons why those things occur including but not limited to roaming, cell handoff, signal strength & fluctuation and network problems. If you are experiencing the things you mentioned on a frequent basis, you may want to notify Sprint.
posting & replying via the XDA Premium app.
oh i forgot to mention that the echo problem never existed on the HTC Hero I had.
there was a call lag/bug (on the hero), but that was a 2.1 issue that was solved with a software update. By the time the update came out, I was already on cyanogenmod, so those issues didnt effect me.
Im thinking of trying out some gingerbread roms that have the updated Sense rom for the Evo. I havent seen one that i like yet (tbh, i havent really looked yet).
Could be this modified Sense rom? i dunno. Maybe I can find where I got it. It was included in a root method i used back in December.
I used to have echo on my evo until I upgraded to the newest radio found here...
http://forum.xda-developers.com/showthread.php?t=715485
Of course flashing a radio is dangerous so follow instructions thoroughly
tim
is it the kind of echo im referring too? were you only hearing yourself until you retried the call?
I get the echo, on my us cellular phone for work, a razor. It must just be a cellular thing.........
this echo has never happened on any other phone before. this leads me to believe that its software based on my phone. hardware would almost always repeat the problem. one of these days im going to flash another rom and see if that fixes it.
As the title says, i flashed Slimkat 4.4 onto my old GNex that my girlfriend is using and within a couple days she told me that almost every call is getting dropped within 30 seconds to 5 minutes. The one time i saw it happened i saw no signal drop but the call went silent and eventually ends if she does not end it first.
I asked in the slimkat topic but no one has reported similar issues and i've done a lot of google searches and haven't had much luck on anyone with a similar issue. I'm assuming that it might just need a new radio but i'm not sure if there is one or where to find it.
So I'm looking for any help or ideas as to how to go about fixing this. I'd like to leave her on kitkat as it does make the phone run better but if necessary I'll go back to stock.
I am not entirely sure if it is an android bug or specifically samsung. Anyway on my s5 and my N4 if I go to make a call occasionally it will say call not sent...when I go to redial the number the phone has already chosen a different contact at random to call...to make the issue worse the screen will then blink on and off in succession preventing me from stopping the random call...this seems to happen once or twice a week...I have already disabled the gesture option that calls people so I am at a loss here...anyone else experience this?
Not an Android bug. I've had it where the phone would try to connect and give up, but the second attempt would go through. That's a reception issue though.
It sounds like your software is glitch in for some reason. Usually a factory reset will fix this (unless you rooted and did something to alter the system, in which case, your alteration could be the cause). If not, then warranty time.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk
Yes, I have this too. Really annoying, happens every few weeks, and seems to go away after a restart.
Sorry to bring an old thread back to life but, has anyone figured out this problem? This happens on my Verizon Note 4 as well, so it is not carrier specific.
Everywhere else I have searched no one has an answer.
Just usually a call is placed. Then a quick message pops up with "Call not sent". Then another contact gets called instead. For me I don't see any pattern to how the wrong contact gets chosen.
This happened in KitKat and now is happening still in Lollipop.
Also I did a factory reset when I upgraded to Lollipop. Any ideas?
Edit: Just thought about this. Do any of you who have the problem use Google Voice?
Greetings all,
I tried to find this issue before posting a new thread (I did find an old thread with no solutions to the issue but I didnt want to try to revive a dead thread from a year ago) so I apologize in advance if this is a duplicate and if so please link me to the existing thread.
I have an on going issue that ATT has been useless with so I am reaching out to the XDA community now in hopes that I do not need to start using my phone as a door stop.
I have done a ton of research on this issue and it seem that it is software related but the few fixes that I have tried have not helped at all.
The issue is when I am talking on the phone the "mic" will cut out and sometimes so will the speaker. I can be talking just fine with no issues and then the person I am speaking with says its like I hung up. Some times I can hear the person fine but they can not hear me and other times it truly seems as if the phone was hung up. Some times the issue lasts 5 seconds other times its upwards of a minute. I am on my second phone, att was nice enough to replace it once but the issue persists on the new one as well. The issue occurs on the handset as well as bluetooth. Every so often I luck out and have no issues with a call (normally under 3 minutes) but typically when I use my phone as an actual phone the calls are longer than 10. The issue also occurs when speaker is turned on as well with the phone sitting next to me on a table so I do not think it has to do with any form of auto mute (like the old thread I found mentioned).
One of the things that I had found was to make a call with skype and it magically fixes it. Well sadly to say it I have tried that multiple times and it still did not fix it. I have tried running my phone just stock and the issue still occurs so i do not think its an issue with what is installed (mostly just google apps for work and a few games).
If any one has any ideas please let me know. At this point I am willing to try almost anything. Thanks
Turn off Enhanced LTE (HD Voice).I just had an AT&T rep confirm that this is their networknetwork problem. Apparently, HD Voice (VOLTE) isn't quite right, and the bugs are numerous. Turn it off, should fix these issues and maybe more.
keithfrombm said:
Turn off Enhanced LTE (HD Voice).I just had an AT&T rep confirm that this is their networknetwork problem. Apparently, HD Voice (VOLTE) isn't quite right, and the bugs are numerous. Turn it off, should fix these issues and maybe more.
Click to expand...
Click to collapse
I just reset my note 4 to stock last night. I just checked and Enhanced LTE is off and I am still having the same issues that others are reporting and just terrible signal strength in general. If I am indoors anywhere I am lucky to have 2 bars and then half the time calls don't go through. I am headed to the ATT store now to see what they say. I am on next and could upgrade but looking at the list of available phones from ATT I don't know if anything is really going to be better. I don't want to shell out the cash for a nexus 6p but I may end up doing it.
Turning off enhanced seemed to help but I still encounter the issue from time to tine. I'm just counting down the days till my 6p shows up...
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app