It seems like the same audio routing problem seen in other Samsung Android phones also affects the Epic 4G:
code.google.com/p/sipdroid/issues/detail?id=366 (I can't post links)
This is shows up on SIPDroid and Fring. I've contacted Fring support about this issue. It looks like some people have fixed with a patch to the audio routing code in other Samsung Android phones:
forum.samdroid.net/f9/sipdroid-voip-i5700-problems-983
forum.sdx-developers.com/android-2-1-development/fixing-the-moment%27s-audio-routing-%28so-we-can-use-sipetc!%29
A cursory search shows this issue hasn't been reported here yet so I think I might take a look this weekend to see if the patches can be ported over to this phone. I'll admit I'm a bit out of my element here so I could use any advice and help from the seasoned devs on the forum. Thanks.
I was seeing the same thing on SipDroid, but then I tried Fring last week, and it worked fine. My biggest issue was the SIP call quality (with both apps) connecting directly to gizmo. It was really bad both over wifi and 3g. Almost unusable. Not sure what the cause was.
I agree that Fring call quality on SIP leaves much to be desired. I found SipDroid to be much better but still somewhat unusable. I have an Asterisk box at home so I can tweak things with codecs as soon as the audio routing issue is addressed.
As far as Fring fixing the bug... yes, Fring only fixed part of the bug in the latest version (2.1.1.24 I believe). Right now the initial call comes through the ear piece correctly. However, if you switch to the speaker phone during the call then the audio will never go back to the ear piece no matter how many times you click the button on the screen. The button on the screen will change but the audio is still piped through the speaker phone. I've reported this bug to Fring but haven't heard back from them yet.
Once they fixed it (if they can fix it), then I may ask them how they did it. At best they can tell us how they squashed the bug and then I can share the info with the SipDroid developers. At worst, they say no and we're not worse off than before. I still believe porting over the fixes in the other Samsung phone is an easier-to-implement solution than asking every VoIP developer to add a special case for Samsung Android phones (if that's in fact how they solved the issue).
Sipdroid still routing to speakerphone for me...
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.
Hello Everyone,
I have recently purchased a bright red Nexus 5 32GB, and found that there is a problem with mic.
I have to speak loudly or repeat my words so that the other person on call will be able to hear me.
I have gone through this thread and found that am not the only person with this problem and users have also raised the same in this google group.
Users are stating that they have RMA'd the phone but the problem still exists.
I too have done testing with sound recorder apps and they all seem to record my voice properly.
I want to find out if this problem is only in the stock ROM or does it also effect custom ROMs and custom kernels.
so, anyone using custom ROM or kernel can please check and update us if the mic is working properly in your phone, can the other person hear you clearly. can you check any voice recording app and google keep and confirm if the voice recordings are of same volume and clarity.
Thank You.
It exists for everyone and there is no known fix as yet
Sent from my Nexus 5 using Tapatalk
rootSU said:
It exists for everyone and there is no known fix as yet
Click to expand...
Click to collapse
Ah, so it's not my network then... lots of people saying I'm either very quiet or garbled when I call them. I wonder if the noise cancelling needs tweaking? Could be that it's partially cancelling our voices.
Dave Trouser said:
Ah, so it's not my network then... lots of people saying I'm either very quiet or garbled when I call them. I wonder if the noise cancelling needs tweaking? Could be that it's partially cancelling our voices.
Click to expand...
Click to collapse
It is indeed believed to be a problem with the noise cancellation algorithm.
some rooted users change a value in their build.prop to "turn it off" but I cannot say for sure it works for everyone.
Waiting for a fix.
rootSU said:
It is indeed believed to be a problem with the noise cancellation algorithm.
some rooted users change a value in their build.prop to "turn it off" but I cannot say for sure it works for everyone.
Waiting for a fix.
Click to expand...
Click to collapse
i believe its because of noise cancellation.
to check it, i tried using ' ok google ' on my home screen. it wasn't picking up my voice.
then i've closed the secondary mic on top with my finger and said ' ok google ' and it works as it should.
this is working even with my phone 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.
Hello,
we have several Samsung S7s here and all of them have the echo problem with current custom ROMs. Especially during calls between the S7 phones, an echo can be heard after more than about 15 seconds. However, this is almost negligible during calls with the landline. The sound is also slightly distorted, so that it sounds like speaking Parseltongue from Harry Potter.
We have tried LineageOS 16-18.1 and the PixelExperience without success so far. With Lineage 14 and the Stockrom everything was ok. Applying relevant settings (from audio_effects.xml, mixer_paths_0.xml and build.prop) from these two ROMs unfortunately did not bring any improvement. Also other tips did not lead to any relevant improvement so far.
In different places you read that it is a copyright problem with noise reduction on several Samsung phones (e.g. https://forum.xda-developers.com/t/lineageos-16-0-for-s7-build-30.3842465/page-99#post-81525627). But what are the relevant files to solve the problem?
It is noticeable that the problem occurs more often with mobile calls and only some time passes before the echo starts. Sometimes you also read that it depends on the provider - we use Vodafone Germany here and are affected. Also, the connection switches back from 4G to Edge during the calls - but I don't know if this is normal?!
What else could we do? I am very grateful for any tips! Maybe others write their experiences with the Echo problem in this thread, because it goes under too easily in the individual ROM threads?!
Thanks in advance, PaulchenPlump
Cool, builtin delay line... not.
I've heard this happen with specific Verizon cell towers. Verizon and AT&T are well know in the USA not to play well together.
I always blamed NSA
It gets very annoying and tedious whatever the cause.