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
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.
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.
Hey guys,
since amazon is out of stock - and therefore, getting a replacement device is kind of difficult - and I'm still waiting for oneplus to respond, I'd like to hear from you if you encountered similar issues with your OP6:
During calls, I can hear the other side just fine, but the person on the other side can not hear me most of the time. Sometimes, it seems some shreds of voice are being transmitted. It happened on about 90% of calls. There are calls that are perfectly fine, but most of the time, the phone is unusable.
What I could test so far:
- it happens in handset mode, speakerphone and with a bluetooth headset
- it happens on both SIMs, swapping them does not change anything
- it happens on 2G as well as 3G (no VoLTE available yet)
- the microphone works fine if I use the audio recorder (outside of calls)
- calls made via VoIP-software seem not to be affected, though audio quality on the other side isn't that great either (but that might be unrelated)
- sometimes, it seems to happen mid-call
Both SIMs did obviously work fine in my previous device (OP3), signal strength in calls is about -70dBm, both SIMs are on T-Mobile (Germany).
I'm on an A6003 with OOS 5.1.5, Baseband is MPSS.AT.4.0.c2.10-00012-SDM845_GEN_PACK-1.147963.5, bootloader is unlocked and rooted with Magisk.
I did find a thread describing similiar issues on the oneplus-forums (https://forums.oneplus.com/threads/dual-sim-issues.838595/#post-18474985), but I'm currently unable to login to their forums, for whatever reason.
Can any of you guys give me a hint on what to test to narrow down if it's a hardware or a software issue or maybe even suggest a workaround?
I'm happy to provide more details where necessary.
I'll probably have to switch back to my OP3 anyway, so I could give the Android P beta a shot and see if it happens there as well.
Best Regards.
So, it turns out (*after* factory resetting and flashing Android P of course ><) that the echo test number I've been using is equally broken on otherwise working phones, so most of my test results are null and void. I'll give it some more testing...
Just a heads-up for users who may stumble upon this thread in the future: call quality problems are mostly gone after updating to 5.1.6 (and replacing SIM-cards).
I've bought a OP6 just three days ago and I've updated it immediately to OS 5.1.8 (I've also rooted it) and the phone calls problems (call drops and other person can't hear my voice sometimes) are present.
I hope OnePlus will fix the issues not so later...
Unfortunately, I can't rule out that replacing the SIM-cards actually fixed the issue - it might be worth a shot. I haven't had any issues since my last post.
Hey everyone,
So for a while now when I am on a hands-free call in Android Auto in either of my Chevy vehicles (a 2019 Trax and a 2020 Equinox), the other person's voice will make like a stuttering sound for 2-3 seconds, and then jump back to normal. I ended up missing what they said though and it seems to happen almost every 5 minutes or more. I also noticed that it happens once in a while when I am at home talking just on speakerphone or regular.
I thought it was the Bluetooth possibly at first from some things I found while Googling, but everything seemed to reference the music audio stuttering, not the phone audio for phone calls. The only thing I can think of is it has to do with the network (T-Mobile), but it shows that I have a full 5G signal when it is happening, or at least 4G. I am running on the latest update, and my A71 5G was bought unlocked new from Best Buy (not tied to any specific network).
Any ideas? It is starting to make trying to have a phone conversation impossible, and I am in the car a lot for work so it is making it hard to keep up-to-date with family and work stuff. Thanks in advance for any ideas / help / suggestions!
RevM