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...
Related
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
After many months of normal usage on the HTC Inspire with an AT&T sim card, this problem has occurred:
When using the regular phone app, while either placing or receiving a call, the other party hears me fine, but no sound comes out of the regular speaker at the top area on the phone. However, normal 2-way audio works fine if I plug in a headset. Also, sound is heard from the speaker after I change to speakerphone mode, but this is not the way that I wish to normally use the phone. Changing any and all of the volume settings makes no difference, including "In call" volume. Strangely, I can still hear the phone ring for incoming calls, but I cannot hear the ringing on the line after I dial a proper number. A few more details:
-Restarts, long off-periods, battery removals, recovery screen restarts, all haven't fixed the problem
-Doing factory reset doesn't fix, including reinstalling Gingerbread update
-Speaker sound is normal for all other apps (any media app, audio notifications, etc.)
-However, if I install any data telephone-type apps, such as SipDroid (for a Sip number) or Groove IP (for Google Voice number), these apps encounter the exact same speaker problem as the stock phone app.
-If this relates to a hardware problem, it's odd that it worked normally for many months, and the phone didn't encounter a fall or water damage, not to mention that the speaker seems to physically work properly for all other apps except phone apps.
Any clues to solve this problem are appreciated.
ms2k said:
After many months of normal usage on the HTC Inspire with an AT&T sim card, this problem has occurred:
When using the regular phone app, while either placing or receiving a call, the other party hears me fine, but no sound comes out of the regular speaker at the top area on the phone. However, normal 2-way audio works fine if I plug in a headset. Also, sound is heard from the speaker after I change to speakerphone mode, but this is not the way that I wish to normally use the phone. Changing any and all of the volume settings makes no difference, including "In call" volume. Strangely, I can still hear the phone ring for incoming calls, but I cannot hear the ringing on the line after I dial a proper number. A few more details:
-Restarts, long off-periods, battery removals, recovery screen restarts, all haven't fixed the problem
-Doing factory reset doesn't fix, including reinstalling Gingerbread update
-Speaker sound is normal for all other apps (any media app, audio notifications, etc.)
-However, if I install any data telephone-type apps, such as SipDroid (for a Sip number) or Groove IP (for Google Voice number), these apps encounter the exact same speaker problem as the stock phone app.
-If this relates to a hardware problem, it's odd that it worked normally for many months, and the phone didn't encounter a fall or water damage, not to mention that the speaker seems to physically work properly for all other apps except phone apps.
Any clues to solve this problem are appreciated.
Click to expand...
Click to collapse
You do know that it uses a different speaker when on speaker phone and for other apps right? It sounds like the speaker used for phone calls maybe loose or dead.
So if that's the case, I guess getting it fixed is not really a viable option. Seems like such a repair would cost more than a phone replacement. Would you agree?
ms2k said:
So if that's the case, I guess getting it fixed is not really a viable option. Seems like such a repair would cost more than a phone replacement. Would you agree?
Click to expand...
Click to collapse
Well that depends. You could most likely do it yourself for pretty cheap. That is what I would do as it is not really that hard with the time and research. I would call around to repair places and see what they will charge you.
Well you can look into the inspire tinny audio fix but its for cm roms. But there is a modify version of it for sense roms. I had some what of the same issue..
Sent from my HTC Inspire 4G With Beats Audio using xda premium
I probably had tried the Tinny Audio Fix before, but to be sure, I loaded it again within CM7. Still not fixed.
I've had to accept the fact that the front speaker is broken and needs to be repaired or replaced, so that's what I'll do. I guess that all hardware breaks eventually. Thanks!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Sounds like the phone may be stuck in headphone mode. Try plugging in headphones and pulling them out a few times and see if that corrects it. My cousin had that issue on a different phone. Lots of dirt and pocket fuzz gumming up the headphone jack.
Sent from my Inspire 4G using XDA
This seemed to only recently have come up.. but the handset microphone does not pick up sound nearly as well. It is maybe 1/10th the amplitutde. I've tested phone calls to myself (to GVoice headphones, other phones, etc.) and the speaker mic works great. When you take it off speaker mode it barely picks up sound at all.
When I use Evernote voice note recorder or a simply voice recorder I get similar results of extremely attenuated sound.
I do not _believe it is a CM10/custom ROM issue as this new behavior seems to have only started recently (past 2 days?) and was running the same stable ROM the whole time. I haven't yet isolated, but it could be a bluetooth problem (doubtful) - as I recently paired with two devices sometime in the past 3 days, or maybe some App has taken control over the amplification of the handset microphone.. but I install/uninstall so many apps to test throughout any given day this would be hard to isolate.
Has anyone had this issue before??
I'll go ahead and reset to a clean ROM, stock ROM, etc. and see what results I get, but I wanted to post a Q first to see if anyone ran into the same issue. Thanks in advance!
ray
This is concerning the Samsung Moment. It does effect other Samsung models as well.
As I'm sure some of you know, when trying to make calls with GrooveIP or SIP apps, the sound for the person you connect to comes out the rear speaker. Apparently this is a kernal issue. I read that crappykernal fixes this on the intercept, but what about the Moment?
Also, although this is supposedly a kernal issue, Sipdroid 1.3.7 fixes this and routes the sound to the earpiece. This is the only version of Sipdroid that works like this on this phone. I know for a fact it does, because I spent a few days trying to get it to work a few months back. However, I don't like using SIP. I want to use GrooveIP. It's much simpler and sounds better too.
Does anyone know of a kernal, or solution of any kind, that will route the sound to the earpiece correctly? I'm currently using the Ubermoment rom.
I posted this over at SDX, but hoping someone here might know a way to fix this that I haven't come across.
**EDIT**
Found out my current kernal kinda fixes this. I have to mute, then unmute, the speaker. Then audio is routed to the earpiece. It's a workaround, but would like to not have to do that.
No ideas anyone? Would love to be able to fix this issue. I can't believe nobody has figured out how, or tried to.
Hello!
I have a major issue during videocalls using google duo, skype where if there are any background noise around me, i can't hear the person i am talking to. The audio cuts off. It has to be silent around me in order for me to hear the person i am talking to. Is there any fix to this problem? I have already reset the phone but the problem is still there.
mic (over) sensitivity? perhaps some will stop by and know the file and file entry to edit.
any of this type setting elsewhere (Settings, the app itself, and sound modification yo have installed, eg Viper, etc... that you can check/get to?
I have no sound modification installed. I checked the settings but there seems to be no part adressing this issue. The same problem happens when i use different apps like skype, google duo and signal. Could it be a hardware problem? The microphone works fine when i record a video or recording audio.
Maybe.
Rooted? If so, and you've done a full, clean install, and sure that the install is working ok, maybe try another custom ROM.
Normal calls work, as I get you it's (just) video calls? Another possibility, I'd consider looking up mic sensitivity and ways to decrease it. On the OnePlus One I am aware there was a configuration file folks could mess with to try and resolve that phone's mics over sampling. That was a common issue for many.
Have you tried turning the volume down and see if that has any effect?
Wish I could offer more ideas, I have used video calls maybe 3 times in 8 years.
The phone is not rooted. This problem occurs only when i use internet based videocalls (skype, google duo). The volyme is not usually high when i call. Thank you for your time, hopefully i will find a solution soon.
Frustrating. Good luck.