Hi,
I've problems with Bluetooth calls in my car since the first day with Pie stock rom.
When a call comes in or I want to make a call, I only hear a sound of distortion. The person on the other side can't here me in any way.
Normal calls are okay. I have made a clean install, got no error messages while installing and so on.
Can someone make Bluetooth calls with Pixel XL on Android Pie stock rom ?
I am having the same issue with Android Auto. It is like a very loud static noise. It doesn't happen all the time tho.
Ah yes, using Android auto here, too.
Hoping, that I am not alone with this problem.
Seems that Google fixed it with the September update.
Related
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:
I'm running a stock galaxy nexus, and since a few days (suddenly), people can't understand me anymore when I'm not on speakerphone, I sound really far-off and muffled.
Since it's working fine when on speakerphone I'm suspecting either a fault in the noise cancellation or with the microphone which is used in regular calls.
In the stock android I run I don't find an option to disable the noise cancellation.
Can anyone recommend me a rom which has this option? I'll be giving the phone to my wife next month (provided I can fix this problem), so I don't really care one way or the other if the experience/ui of the new rom matches what I get from stock android. All that matters is that the phone works well.
If disabling the noise cancellation doesn't pan out, would there be any way for me to force the phone to use the secondary microphone for all calls? (Since it still works fine on speakerphone...)
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.
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)?
Hi,
I just got a OnePlus 7T HD1907 for my wife that I'm setting up. I've got the bootloader unlocked and LineageOS 18.1 20211121 installed (with latest open_gapps and Magisk). Everything works except for a problem during phone calls and other interactive voice type calls.
Here are the symptoms:
When I have an incoming or outgoing phone call, or a Skype call or Signal call, the person on the other end hears a squealing noise. I can hear the person on the other end normally, but they just hear this screech that goes on and on for the duration of the call, and cannot hear anything coming through the
If I change to speakerphone mode during the call, the sound of the screeching changes on the other end but still is definitely there.
When I use a bluetooth headset for the calls instead, the problem does not occur.
When I record audio using a sound recorder app, the recorded audio does not have the screech in it.
Any suggestions?
Thanks,
Elliot
Go back to stock or try another rom
Found https://gitlab.com/LineageOS/issues/android/-/issues/3752 and
https://www.reddit.com/r/LineageOS/comments/on3u7q
One suggestion on the reddit thread was to go from T-Mobile stock -> Global stock -> LineageOS. I went directly from T-Mobile stock to LineageOS.
I just tried going to global stock (problem gone) and then back to LineageOS and the problem seems gone for good.