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.
Related
long time lurker, first time poster.
So I've had the EVO for about 2 months and really love it; however, from the beginning I have had people callign me, i answer and can't hear them....they hear me fine. Now, recently, I'll dial a #, phone's screen says it's ringing, but it's not, and then the call will just drop. Both situations happen w/ full bars on 3G and it's very, very frustrating.
Phone does everything great except.....ya know......when it needs to be a phone. lol!
Here's my current setup:
ROM: VaelPak 2.3
Kernel: HTC 10 (whichever comes w/ vael's 3.3_
ROOT: unrevoked
Baseband: 2.15.00.09.01
PRI: 1.77_003
Thanks a lot!
My GF and I have been having a very similar problem. Have you found out anything about it yet?
What happens to us is that the receiving person can't hear anything, however the caller can. I just tested it out, and I could call her phone, and hear sound from her phone, but couldnt hear anything from my phone. If I hung up and called my phone with hers, I could hear my phone but couldnt hear hers. This happened several times in a row. Once (while I was just testing it) I couldnt hear anything from either phone, then mine started ringing again during the call as if I 3-wayed called someone. This has happened before. I hung up, called again, and it worked. Then the problem started again.
We both have EVOs, I have google voice which I was bypassing when calling out, and both of of phones are rooted, hers with the stock rom, mine with myns two point. I have not had this problem calling anyone else except her phone, however I don't much of anyone else.
Do you have Google Voice?
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.
OK so this has been an issue for several months now and its gotten worse.
The ear speaker has been working intermittently and will usually not come on at all.
This seems specific to CM7 because flashing back to CM6 it works fine.
Problem is: Speaker works randomly, at first i thought it was hardware issue but every time a loud sound or voice was played through it would come on.
I would use a saved voicemail and play it a couple times and that would usually kick the speaker to work. But as of recently its doesnt come on at all, only when it wants to.
I have no idea if this would help, but using OSMonitor's log, whenever i tried to play a sound through the ear speaker it would always log audio_disable().
Sometimes reboot works, mostly it doesn't. Ive done clean wipes, fresh installs, and reverting back to previous nightlies and stables. it only has gotten worse with newer updates.
I've looked everywhere for an answer. I dont mind uploading a log, just dont no what to exactly copy for the speaker.
it happpened to me too.
Called tmobile.. pretended to run the test they told me to run.. they then agreen that it was broken internally, and sent me a replacement.
Then I un-rooted my phone, sent it to them, and life is good now
lol
do it..
any other ideas on whats causing this??any solutions besides the return?? ha
I dont know if this is a coincidence or not.. but my speaker died as soon as I flashed the Salsa Slide ROM.
I have had no issues previously.... and I am not trying to pin the blame, it just seems coincidental.
I do have a slide that I bought right at launch, so I dont know if that has anything to do with it...
Either way, I will be calling today to get it replaced because when I flashed back to NB-mod I still could not hear from the internal speaker.
I've been having an odd issue with my GSM Gnex lately (probably past month or two). During a phone call, after a short amount of time (usually within 5 minutes), the outgoing and incoming audio will quickly fade away with some garbling. I can call back and have the audio return, only to die again. I don't make/take many phone calls, so I don't have a lot of data on it. I can't say if it happens on every phone call, but it has happened enough times that I know it's a problem.
This has persisted through various clean installs. I'm not sure, but I think it started with a ROM whose name I can't remember, then in CM 10.1 for a few weeks, and it just happened again tonight, after a clean install of the stock 4.3 JWR66Y image directly from Google last night. Although I did flash the newest UGLL1 radio, as well as SuperSU for rooting.
I'm thinking it's hardware, but I don't know enough to make a decision on it; I've had this phone since last summer.
Sorry for the vagueness and lack of detail. Does anyone have any ideas? Experiences? Things I could test?
Thanks in advance.
Bump.
EfemaN said:
Bump.
Click to expand...
Click to collapse
Bumping again. Forgot about this thread a while back.
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