Samsung s9 exynos
After update the ui2.5 my mic isn't working properly when i receive the call the other person don't hear my voice until i put it on the speaker and once mic started then i can put the speaker off.
But when i make the call the mic works properly. I don't need to put the call on speaker.
I also had this same issue, thought something was wrong with my phone. I fixed mine by flashing latest rom through odin.
Dear, after some tests it seems properly working removing bixby features: vocal activation, automatic listening, use with locked smartphone and other features letting bixby automatic activation. After different incoming calls it seems properly working. Please let me know your experience.
I have the exact same issue with my S9 over the last few months or so. Does anyone know what caused it or a less intrusive fix (other than reflashing stock OS)?
Related
Wanted to ask if anybody else is having dropped calls?
Using the headset included in the box and another one that I have that I know works the call kept cutting out after 5 minutes or so and then the call hanging if I did not wake up the screen.
I thought it was a phone issue obviously, but if I leave the screen on and play around with it, then the phone call does not hang.....
Also if the sound cut out and before the call was dropped, if I wokeup the screen then we could hear each other again.
Has anyone else got this issue? I am on the original Three firmware v1.26.xxx, handset was sim locked but now sim unlocked.....
And since then I have tried calling with just the speakerphone and the call did not drop, not used the phone for long or with the speaker near my ear as I usually use a headset.
Thanks.
Bump, someone must have used the headset and made a long 10 minute+ call?
Using without a headset and the speakerphone the call has not dropped.
I only use a bluetooth headset but i don't seem to have problems with it (and i realy talk alot at the phone).
Just FYI this does not happen anymore for me after installing the 1.28 update from Three..... Still waiting on the other updates for other fixes!
Hi guys, hope you can help with an odd problem...
Very, very occasionally (maybe 1 in 50 calls) I get an issue where I can't hear the other party, as if the earpiece was dead. If I drop the call and re-dial, 99% of the time everything is fine. (I think I had one time in 6 months where the 2nd call did the same.)
Now, I can't decide if this is a network issue (Vodafone) or a phone issue. I mostly use a Bluetooth headset due to the size of the Note but I doubt it's headset related as I have tried two different high end brands and it happens with either.
Things I have noticed:
Problem applies to incoming AND outgoing calls
I have checked I haven't accidently muted the call
My Bluetooth headsets all chime at the start of a call but there is no call audio
The other party can hear me but I can't hear them
System sounds are all fine, only call audio is affected
Switching between headset, phone and speaker phone make no difference
Applies to all incoming call audio, including ringing tones and busy tones
I reboot my phone sometimes but as the issue is rare I couldn't say if it makes a difference. Also this is a standard Note II (not a branded Vodafone one) with all the latest patches downloaded. Looking through my app downloads I can't see any obvious ones that might affect the phone. Apart from the stock Samsung apps I most connect to CCTV systems. I have CSipSimple but I haven't used it in ages.
Any suggestions on how to investigate this further?
Regards,
Andy
Seriously... no ideas?
So, no one's ever had this problem and no one has any ideas?!
:crying:
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.
Hello,
The microphone doens't work on my S9 when I use the speaker phone. The people do not hear me. I have no problem in normal call mode.
I tested to call in "safe mode" but the problem always appears.
Thank you for your help!
No idea?
Same problem here (replace xx by tt) : hxxps://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GalaxyS/thread-id/51619/page/12
Thank you!
Up
m also having the same problem, but also While video recording
Same problem here. Only when HD calling is enabled. If you disable HD calling, the problem should go away. I'm hoping the first software update fixes it. Just to be clear the problem is that the other person cannot hear you when on speakerphone. You should be able to hear them clearly and have no idea there is a problem unless they tell you that you sound muffled or like you are underwater. Turn off HD calling on Verizon and it goes away.
Thank you for your solution. I disabled the HD calling ("4G calling" in French) and the voice can be heard now. But the quality is very very bad! It is scandalous for a phone of this price!
Is there an other solution to improve the microphone quality during a call with speakerphone?
Thank you!
HD Calling?
I have the same issue, but have no idea how to disable HD Calling ( I'm on Sprint BTW). These minor issues are ticking me off; I've already had for factory reset once due to Camera settings crashing the app.. . now this nonsense. Phone isn't even 14 days out of the box, and its DEFINITELY not an "third party-app" issue. Bad time to switch from iPhone, huh? This is unacceptable for a $300 phone, nonetheless a $1K phone.
Hello, I have the same issue, on VoIP apps like WhatsApp as well. https://forum.xda-developers.com/ga...rphone-loudness-clarity-t3746298#post78757253
Does anyone experience the same problem on custom ROM?
Speakerphone mic not working in any call apps
Bond70 said:
Hello,
The microphone doens't work on my S9 when I use the speaker phone. The people do not hear me. I have no problem in normal call mode.
I tested to call in "safe mode" but the problem always appears.
Thank you for your help!
Click to expand...
Click to collapse
Same problem here, first on Note7, now on Note9. Disabling HD calling did not fix it for me.
any solution for it ? please post solution
I've discovered the issue is that the phone attempts to mute your microphone while the speaker is playing sounds. (If you're on the phone with someone they have background noise or are talking) and your phone's microphone attempts to lower the sensitivity so that the person whom you are speaking with doesn't hear an echo of themselves on their end. If they aren't making a sound then you can be heard normally. This is the downfall of my S9+ because the speaker and microphone are right beside each other.
After the recent update I can't put my phone on loudspeaker when on a call. Any else had this happen?
I did have this happen to me once before, where I made a call and it wouldn't allow me to switch to the speakerphone. I rebooted and now it seems just fine.