I have a weird and annoying issue with my 10 (stock 7.0, 2.51.531.32):
During every phone call, after ~1 minute, my microphone seems to cut out for perhaps 10 seconds (as reported by the person at the other end). After that, it works normally again. I just installed "automatic call recorder" so I can start to pin down these numbers precisely.
The microphone(s) pass the HTC hardware tests, and when I use "Voice Recorder" in voice notes mode, it will record for many minutes without any issues. In addition, I don't think this ever happens when I use a Bluetooth headset for calls.
Any suggestions?
Related
Hi All,
I have my Galaxy Nexus about a week now, so far I am quite happy with it. It's my 1st Android. It's a GSM one.
I have noticed an odd issue, and am wondering if others could test and see if they are getting it, on either GSM or 4G.
On to the issue.
It can happen in two different ways with the same outcome.
The first way it happens:
I receive a phone call. I answer the call as normal. I immediately hear the other party on the call for a split second, then a split second later I hear my ringtone through the earpiece for a split second. Then the call will carry on as normal.
Once the call has been finished, I will then notice a delay in certain sounds. E.g. I will try dial another number on the Dialpad, and the tones will be delayed by several seconds or just don't play. And when I hit buttons on the screen, e.g. recent apps, The usual click is delayed by a couple of seconds and is followed by a second click.
If I open the Music app or the YouTube app and play music/video, both audio and video play fine, but when I hit pause on either it will pause then play for a split second again, then pause and stay paused.
Sometimes if I receive another call afterwards; my ringtone will, instead of playing from the start, play from where it was when I answered my last call.
The second way it happens is if I call someone. When I press the hang up button, I will hear a tone in the earpiece, followed by the same tone through the speaker. I will then have all the weird audio bugs as above.
Restarting the phone resolves the post call issues, of course until I receive another call.
As I said, I am wondering if anybody else is experiencing this? It is a little bit odd, to say the least.
So I had a brain wave.
I went through all my apps and did a force stop on every one that was a downloaded non stock app.
I tried the steps above to reproduce the issue and I couldn't.
So It seems that an app I have installed is causing the issue.
Now to find out which one.
I will report back when I do.
And the culprit is Air PlayIt.
I will continue testing other apps just in case.
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.
Ok, so found a really annoying issue when the watch is set to play phone audio. Basically when you answer a call or make a call from your phone, the functionality of the screen turning off when you put your phone to your ear no longer works, which means you end up controlling your handset with your ear if you ear touches the screen.
Very annoying!
This only happens if the watch is basically setup as bluetooth audio for the phone (as in you can take calls on your watch).
This was already discussed here:
http://forum.xda-developers.com/huawei-watch/help/phone-audio-proximity-sensor-t3330372
It seems to be a problem in the Google Dialer App. The problem is not present with Samsung phones.
For the moment you'll have to press the power button, to disable the screen. Hopefully a future update of the phone dialer app will fix this, you may support this here:
https://code.google.com/p/android/issues/detail?id=202776
There is an update MHC19J mentioned for the Nexus 5X, which may improve the situation.
Hi,
I've been experiencing this for a few months since I installed @McFy 's LineageOS 15.1 on my A320Y.
After making/receiving a call (the call went fine with no glitches), when I pressed the home button, it will only show a black screen with the notification bar. I can still switch between apps but none of them are responding to input. Soon the phone will reboot itself and everything goes back to normal.
This will occur on all kinds of calls, cellular and VOIP (I tested Telegram and Signal). So it seems that the audio system is the problem here.
I gave it a few more tests and it seems that it will only occur after the system stayed on for a few days, freshly rebooted systems don't have this problem.
In addition to that, a few things related to audio that I had observed:
- sometimes the microphone doesn't work on calls (both cellular and VOIP), I can hear the other end but the recipient can't hear me
- sometimes the audio playback responds quite slowly, for example, when i click "play" on Spotify, it will show "playing" but progress bar doesn't progress, I will hear the audio ~10 seconds later
I have logs for some of the scenarios, happy to provide them to devs.
Thanks!
Hi, there.
I've using my S9 for a couple of weeks now and I noticed a very annoying problem.
If I'm on a call (phone call, video call, regardless the app), using the speakerphone completely ruins it. On a video call it's easier to feel the problem: you can still see me talking, but you can't hear anything. The voice keeps fading out and back in and out again, like the volume was lowered and put back to normal. It's basically impossible to understand anything. Quality of the image is fine, it's smooth, not pixelated, but the voice is just terrible.
If I use the earpiece or wired phones (have not tried with BT yet) this problem doesn't happen.
I have the feeling that this has to do with the noise cancelling trying to filter out the noise.
When calling my wife (Xiaomi Mi A1), it also happens from her side to the point where we can't do video calls anymore. If I call my sister (iPhone 7), the audio is just fine for the same app and on a video call.
I have the feeling that this is a known issue, but I couldn't find a post about it.