[Q] Hear Echo Only When Making/Receiving Calls - EVO Shift 4G Q&A, Help & Troubleshooting

Hi all,
I've done some searching on this and found some "general" instances of this happening in the official Sprint Community forums, but nothing of value and certainly nothing with particular application to the Shift.
I recently rooted and installed CM7.2RC2 on a family member's phone (not 7.2 final due to bluetooth bug). Although I'm no expert, I've rooted a number of phones and had no issue with the awesome directions provided on these forums.
Randomly, when making a call, the Shift dialer does not ring once "send" is pressed, but rather one only hears an "echo" of anything being said into the phone. On the other end, the call seems to connect normally; however, the recipient only hears an echo of their own voice as well. As such, the two parties cannot communicate, despite the fact that for all appearances the call is connected.
This occurs in the opposite situation as well. Seemingly randomly, if a call is placed into the Shift, the user of the Shift can accept the call no problem. However, once the call is accepted, the person using the Shift only hears an echo of their own voice. On the dialing end, the call appears to be connected, but that caller only hears an echo of their own voice as well.
The issue tends to occur in "blocks", like a few calls won't work, but then it'll work normally again all of a sudden. The phone might be fine for a few hours, then randomly it'll happen again.
I've attempted to downgrade to CM7.1, upgrade to the latest nightly, and use just about everything in between with no luck. I updated the radios to the current version again (also did this during the rooting process, updating the profile/prl/pri as well, before flashing CM). Last night I downloaded newSENSE in the hopes of flashing that tonight and using the Sense interface to update the Profile on the phone. However, I'm not sure that will do any good if I nan back to CM7.2RC2.
Just wanted to shoot this out to the rest of the group to see if anyone else might have had this same or a similar issue with their Shift. I've used CM/AOKP on my OG Evo since I brought it home and never experienced anything similar.
Thanks for any thoughts/input!
--DC

This happens to me on cm9.
I can still hear the other person, but I always hear a slight echo (not enough to make the conversation impossible)
Its annoying, but its not too bad.
As far as I know, the other person doesn't experience any echo.

Sounds similar...but the only difference is, with my issue, neither party can hear the other. All each party hears is a slight time-delayed echo of their own voice; not the other person.
When the issue occurs during a dial-out on the Shift, the caller on the Shift doesn't even hear the "ringing" of the phone on the other end to confirm that the call is being routed (although it is, and the person on the other end can pick up)...all the Shift user hears from the point where they press the dial key is an echo of what is on their end of the line.
It's very weird.
Also, if it helps, the phone has Google Voice integration enabled on Sprint. I'm seeing some posts saying that this may be the issue, although I'm not convinced since this problem never presented itself prior to rooting/flashing.
Thanks!
--DC

DamienChaos said:
Sounds similar...but the only difference is, with my issue, neither party can hear the other. All each party hears is a slight time-delayed echo of their own voice; not the other person.
When the issue occurs during a dial-out on the Shift, the caller on the Shift doesn't even hear the "ringing" of the phone on the other end to confirm that the call is being routed (although it is, and the person on the other end can pick up)...all the Shift user hears from the point where they press the dial key is an echo of what is on their end of the line.
It's very weird.
Also, if it helps, the phone has Google Voice integration enabled on Sprint. I'm seeing some posts saying that this may be the issue, although I'm not convinced since this problem never presented itself prior to rooting/flashing.
Thanks!
--DC
Click to expand...
Click to collapse
Yeah, it hasn't been as bad as your situation.
This ROM has google voice installed on it, but I disabled it (i dont like it lol)
I honestly don't know what could be causing the echo.
I haven't tried flashing other roms to see if the echoing persists because it's not too much of a nuisance for me.

I don't know the cause of your issue, so not much help. But I can say I have had Voice integration setup for a while now, across all different types of ROMS and never experienced this problem. Everything from the new ICS/CM9 Roms, chinese ports and etc.. to me just having to unroot back to stock today, the integration has worked for me without a problem on everything.

I'm running NewSense and get an echo call once a day or so. Isn't continous and if I hang up and dial again it always goes through normally. I was running CM7 and UKE ROM and can't remember if I had the same issue so I just deal with it and assume it's a Sprint service glitch. As it's not terrible, I don't feel like reflashing just to see if that would fix it.

As a quick update: This morning I deactivated Google Voice integration on the line and the user has had not experienced the problem since I took that action (approx 14hrs of normal use sending/receiving numerous calls).
I'm going to reintegrate Google Voice on the line tomorrow, giving it 24hrs to be sure that was the issue, and will report back whether the problem returns.
In the interim, thanks again to all for your input!
--DC

After reintegration of Google Voice on Sprint, the issue reappeared immediately. As a result, I've just decided to forego Google Voice integration and instead set up conditional call forwarding. Not really a big deal; but still a very odd bug! Odds are I'll re-try the integration again at some point in the future, but for now call forwarding should be fine.
Oh well, hope this might help out someone else in the future!

same issue on Evo 4G LTE
I am experiencing exactly the same issue on my Evo 4G LTE. I have Google voice integration as well. I was told at a Sprint store that it is a known network issue (even happening on iphones) and that I should call Sprint and tell them where it was happening, but I'm pretty sure they have no idea it has anything to do with Google Voice, and I know the low level customer support rep that I get when I call *2 is not going to be helpful at all, nor will they accept the evidence that it is a GV issue. I really don't want to disable GV integration, but if that is what I have to do, I will.
Oh, and this is happening on a stock rom both with S-OFF and S-ON

Same thing on ET4G (S2), At first I thought it was a hardware problem so I took it to Sprint and they gave me a new phone. The problem persisted. Then I suspected it was Google Voice. I use GV's features all the time so disconnecting it from Sprint is not a preferable option. Has anyone made any progress on this?

If you read the other posts, he said that the only way to fix it that he found was to disable google voice. If you mean to ask if there is any workaround, I would not think so, but if you absolutely needed to use Google Voice, you could RUU back to stock (only if rooted) and then take it to Sprint to have them replace it
It might also help if you exaggerated your problems a bit, thats what I did and they gave me a new phone for no charge
Sent from my PG06100 using xda premium
EDIT: Sorry ignore my post, I didn't read your post completely.
---------- Post added at 02:13 PM ---------- Previous post was at 02:07 PM ----------
As an alternative to Google Voice, you could always use something like Skyvie from the Play Store
Sent from my PG06100 using xda premium

Just thought I'd update for posterity. The user of the Evo Shift 4g has been using a Photon Q since release with Google Voice integration. This week it started developing this same issues with calls in/out echoing with at least one party not being able to hear the other. Although the user of that handset loves GV, I think I might just turn off integration permanently and relegate GV to a voicemail service rather than an all-encompassing messaging client. Too bad, really. The integration was a great idea.

Related

[Q] Inspire voice dialer doesn't understand no?

Using the stock voice dialer in my Inspire.
On the occasions that it misunderstand me and if asks me if I want to dial the wrong person, I say no -- yet it still dials the wrong person anyway.
I've tried "no", "NO!", "cancel", "stop", "kiss my butt", and a host of other things not acceptable in this forum. Seriously, though, the voice dialer misunderstands me about 25% of the time, so I get plenty of opportunity to say no. iI've tried saying no immediately and I've tried a delay of half-a-second to 2 seconds or so.
Is there something I'm missing?
Did you root your phone and are you running any ROMs?
It did it on the stock ROM before I rooted, and does it after rooting with the modified stock rom (Ace_Cingular_US_SL_1.84.502.11_Radio_26_06_06_30_M_PD98IMG.zip).
Try it in Japanese
Not sure whats wrong, possibly hardware failure?
I would try a voice dialer off the market and see if it works and if it doesn't you know it a hardware failure.
Try using TopVoiceControl or Vlingo.
A hardware issue that causes the voice dialer to recognize everything I say except for "no"?
Pretty unlikely. as it recognizes "call...", "dial...", "open..." with at least 75% accuracy. It just refuses to hear the "no" when confirming something.

Bluetooth Voice Dialing [FIX]

So after realizing that my brand new $650 phone did not have bluetooth voice dialing, I decided to do some work.... good news.
HTC did not include the VoiceDialer.apk with the Sensation. Why? No clue!
After getting it here...
http://download615.mediafire.com/m4f6kpd3g06g/mdh1m1x0dzh/VoiceDialer.apk
I was able to prompt my car stereo's Voice Dial button, but the Voice Dial still did not want to work correctly, but... just get ChoiceDialer+ from the market, and all is good.
How did you install the apk I would like to try this before I return the phone. Sorry if this is a stupid question.
Connect your phone to your computer via USB cable, and switch to Disk mode or Mass storage mode or whatever you call it.... drag it onto your phone. Use Astro or Root explorer to navigate to your phones folder, and just open the apk to install, and then restart.
Again, I dont think the voice dialer itself will give you prompts, so get a third party app like ChoiceDialer+
I can't get the voice dialer to repeat what I say for confirmation.
After I press my bluetooth, voice dialer opens up, I say my command, and then a pop-up comes up asking me to press ok or cancel.
Anybody got any luck with this?
I have been using vlingo since launch for bt dialing and works great. The app even has an in car mode and can read texts and emails. Of course you can turn that off as well.
I just use vlingo as my default app when long pressing the search button. So upon a long press, vlingo launches and listens via bluetooth and you can say your command from searching whatever to navigate to wherever to call whomever in your address book. Try it out, it's free. You can always uninstall if you do not like the functionality.
Is there an option for me to press the button on my bluetooth to trigger the app? It is illegal to use the phone while driving up here in Canada.
Make sure voicedialer.apk is installed, and then install a third party voice dialer like Vlingo or Choice Handsfree. You need that voicedialer.apk installed to trigger the prompt when you press the Bluetooth button on your headset... When you press it, it should bring up a prompt asking you which program you'd like to use.
Sent from my HTC Sensation 4G using XDA App
my voicedialer Force closed
after i installed choice dialer, i got the same menu still.
I press my bluetooth, say something, and then on my phone screen, it gives me a prompt as to what to do (in this case, who to call).
I don't want to touch my phone while driving.
The voicedialer app worked perfectly fine with my nexus one with the same bluetooth headset, no idea why it's not working on my sensation.
I think HTC needs to do something about this. I just bought the Sensation yesterday and didn't realize this issue till this morning. I am using the BlueAnt Q2. Call recognition works fine. But using the voice commands on the Q2 is a bust cause the device is no compatible. WTF.
305buddyluv said:
I think HTC needs to do something about this. I just bought the Sensation yesterday and didn't realize this issue till this morning. I am using the BlueAnt Q2. Call recognition works fine. But using the voice commands on the Q2 is a bust cause the device is no compatible. WTF.
Click to expand...
Click to collapse
I have the same situation, Q2, Sensation, hopefully a rooted ROM will fix this issue.
Sorted
I have a HTC Desire and have long been frustrated at its inability to voice dial via bluetooth. Last week I was annoyed by HTC's attitude to a Gingerbread update for the Desire, so I took the plunge and rooted my phone, installing Cyanogen mod 7.
Wonderful change, it's like having a new phone! One bonus is that, just today I decided to try voice dialling in my car, and it works perfectly! Paired the phone with my Alpine car radio, pressed the phone button on the radio and up came the message 'voice dialling', I said 'call John' and a female voice replied 'calling John' and there I was speaking, totally handsfree. Miraculous I thought, why couldn't HTC manage that?
So, all credit to Cyanogen for a superb update to my phone and I'll be donating, although it's free.
Same issues here. HTC seems to have rushed this one out the door. Besides the lack of BT voice dialing, I'm seeing hangs/crashes in the phone dialer app, and rapid battery drain when playing games. I wish there was a way to turn off Sense; it really adds nothing to the Android experience and usually gets in the way.
installs fine but keeps force closing and does not work with bt and no confirmation prompts. found vlingo but it does not work with sensation.in fact,the app will lock your phone and you will have to restore phone if you can even manage to get it installed in first place. so please stop telling people to use this app. you should be ashamed of yourself.
kpjimmy said:
I have been using vlingo since launch for bt dialing and works great. The app even has an in car mode and can read texts and emails. Of course you can turn that off as well.
I just use vlingo as my default app when long pressing the search button. So upon a long press, vlingo launches and listens via bluetooth and you can say your command from searching whatever to navigate to wherever to call whomever in your address book. Try it out, it's free. You can always uninstall if you do not like the functionality.
Click to expand...
Click to collapse
you are full of crap. if you claim to be using vlingo on an htc sensation you most certainly are full of it. the app is not available for this model and if you manage to find a work around,it will brick the phone. quit lieing to these nice people.
thefattexan said:
you are full of crap. if you claim to be using vlingo on an htc sensation you most certainly are full of it. the app is not available for this model and if you manage to find a work around,it will brick the phone. quit lieing to these nice people.
Click to expand...
Click to collapse
Its too bad you don't know what you're talking about fattexan. I downloaded VLingo from Android Zoom the first day I had my Sensation and have used it everyday since with a blackberry bluetooth speaker. It has not bricked my phone, caused a force close and anything but work beautifully. And please, don't call me a liar like you've done before. I'd be happy to post pictures to get it through your fattexan head.
thefattexan said:
you are full of crap. if you claim to be using vlingo on an htc sensation you most certainly are full of it. the app is not available for this model and if you manage to find a work around,it will brick the phone. quit lieing to these nice people.
Click to expand...
Click to collapse
I've been reading through the threads and have been most interested in voice dialing. I had it on my HD2 and it was quite useful as I use a bluetooth headset as my primary means of talking on the phone. I just hate holding the phone up to my head. In any case, voice dialing IS possible without using BT. I'm sure most of you know this as all you have to do is hold the search button on the phone for a second to get a voice command prompt pop up where you can simply say "call <contact name>" or "dial <phone number>" and it will do as told. I have no modifications on my phone, it is as stock as stock can come.
With my headsets, it used to be where I held the activate button for a moment, a tone would play in my ear, and a voice would say "say a command". Keep in mind, that was on my HD2. The sensation doesn't come with BT voice dialing by default, it seems, and it does appear that there are work-arounds to it like the apk listed above. In fact, I've seen some relatively talented people figure out how to make things work, that weren't supposed to work in the first place. Also keep in mind that voice dialing and other functions are software based, and simply writing the proper code can overcome pretty much anything.
With that being said, thefattexan, I've seen you call other posters and responders liars, and in this thread alone, you've told someone that they're "full of crap". In all honesty, those comments are not appreciated, and at least one thread was closed by a moderator because of attacks like that.
Let me submit to you, that just because you've never seen or heard of something, does not mean that it doesn't exist. Simply because you could not make it work, does not mean that someone else wasn't able to. Calling someone a liar based only on your own experiences is pretty much out of line, and your behavior is somewhat disgraceful. So I am asking you nicely, to please refrain from that sort of behavior. Maybe if someone says they can do something that you are not able to, rather than call them a liar, ask them how they accomplished it and you may learn something in the bargain. Obviously, they tried something that you didn't, and voila. Otherwise, don't say anything, because carrying on like you do will only result in the moderators banning you.
for those that agree, click the thanks button and show the love.
I have had the same problems with the voice dialer apk. It installs just fine but it force closes when trying to use from the bluetooth headset.
I tried vlingo and some other apps but they are too complicated and usually require some interaction with the phone.
I want it to work just like my Thunderbolt. When my phone is in my pocket I can press the bluetooth call button and be prompted to speak now. The say "call John" and then prompted, "calling john" and the phone dials the number. Very simple and easy to work without any interaction.
thefattexan said:
you are full of crap. if you claim to be using vlingo on an htc sensation you most certainly are full of it. the app is not available for this model and if you manage to find a work around,it will brick the phone. quit lieing to these nice people.
Click to expand...
Click to collapse
I have seen your past posts and I can see you do not play well with others. Man, are you a native Texan? You are the most....well how can I put this...ignorant person here. This is XDA. A place where developers and users help each other troubleshoot things here.
And your great additions to this community? Just badmouthing everyone that does not share your view. Name calling really got you where you are today /sarcasm.
I do not know what your problem is and why you resort to name calling literally everytime you post.
Back to topic and to simply replying to you. I have been the early adopters of vlingo. I even paid for the app when it was first released. I have to say I did indeed install this via market when I got the phone because a week ago the in car setting kept fc'ing on me and I uninstalled and reinstalled the version I found in the market.
The funny thing is I tried looking again on the market and I do see that it is marked incompatible with the Sensation like you said, but I did uninstall the app and reinstalled fresh from the market and not use any restores.
I am done sparring with words with you and you can keep calling me and every one else here names....I don't know maybe you were bullied as a child, not given enough attention as a child, or maybe you found out that the Easter Bunny is a myth *gasp*....
I part with this: Get that stinking cross off your back, use the wood to build a bridge and get the hell over it.....
caliber177 said:
So after realizing that my brand new $650 phone did not have bluetooth voice dialing, I decided to do some work.... good news.
HTC did not include the VoiceDialer.apk with the Sensation. Why? No clue!
After getting it here...
http://download615.mediafire.com/m4f6kpd3g06g/mdh1m1x0dzh/VoiceDialer.apk
I was able to prompt my car stereo's Voice Dial button, but the Voice Dial still did not want to work correctly, but... just get ChoiceDialer+ from the market, and all is good.
Click to expand...
Click to collapse
downloaded installed both but when i press the voice dial button on my bluetooth it does nothing, only works when I open the program directly from the apps section in my device, any suggestions?
caliber177 said:
Make sure voicedialer.apk is installed, and then install a third party voice dialer like Vlingo or Choice Handsfree.
Click to expand...
Click to collapse
You are d'bomb!! Worked exactly as you stated. I now have a completely hands free dialing experience using only my bluetooth headset.
Just a tip for anyone watching... I had to restart my phone after installing the voicedialer.apk in order for it to respond correctly. THEN I installed the Hands Free Voice dialer.

[Q]Please Help! Microphone not working on incoming calls..

Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App

[Q] Anyone have issues with calls not coming through? (Google Voice?)

First let me state my current phone is s-off and rooted, but otherwise stock. I have been playing with some lockscreen replacements but not much else altering the phone.
I do also have google voice running for voicemails (I like the notification system, the inbox style tracking and the transcribing) and this was running on my rezound as well so may very well be the issue but not sure.
This occurred a lot on my last phone (rezound) and I chalked it up to it being a little older. But last night it happened on this phone (at home where I have excellent service), my girlfriend called twice and I got no notifications until google voice picked it up and notified me I had a voicemail (she normally doesnt let the voicemail hit so I often never know she calls until its much later and she is much angrier).
Has anyone else experienced this? Is it a verizon thing, a google voice thing or something that just happens sometimes regardless?

Persistent echo during VOIP calls

Hi,
my girlfriend has a Moto G and, since she lives in another country, we use to speak through VOIP calls using WhatsApp or Viber.
Every time I speak I hear the echo of my voice and it is terribly annoying. It does not depends on my phone, because I've changed it few days ago. In addition, it is not related to speakerphone, because it also happens when she does not use it. If she turn down the volume it helps, but on the other side she cannot hear me as well as before. Of course this does not happen when we do a "normal" call, without using third party apps.
Am I the only one experiencing this? I found out another person had a similar issue (http://forum.xda-developers.com/moto-g-2014/help/echo-problem-call-t2994157), but no solutions were given.
Is there a solution for this? Any recommendations? The only thing I thought was to buy her headphones and force her to use them, but of course this is not the ideal solution of the problem.
Yeah I've faced this issue too. It turns out the only way to avoid this is turning the volume down. It could also be high latency issues.

Categories

Resources