I cant figure out why this is happening but when i am in the call on speakerphone the phone will sometimes just turn off speaker and revert to the phone earpiece but the software still thinks its in speaker mode thus the only way to go back to speaker is to change the audio to handset first then reenable speaker.. this can sometimes happen several times withing a single call. I also have an android wear watch that is paired via bluetooth which i though may be the culprit but i have noticed it even when my watch is dead... anyone else?
Having same issue when connected to Bluetooth in my car. It will change output and I have to manually put it on phone headset then back. Sometimes it will just drop a call all together. Usually 6 minutes approx into the call. I am on Verizon 7.1.1. NMF260. Anyone else still having these issues on most recent update as I am.
Yeah I noticed it to. Thought it was my Android wear watch so I turned off gestures thinking the wrist movements were switching the output. I haven't had a chance to retest.
Sent from my Pixel XL using Tapatalk
I am going to resurrect this thread because I'm having the same issue and it's one of the most infuriating things ever. To have my private conversation suddenly switch to speakerphone, or to be in the car and have it switch from car speakers to speakerphone is frustrating beyond words!
I have the issue as well. Sometimes it happens when another calls comes in or when a notification comes in, but also happens randomly. Pixel 2, Android 9.
Back from the dead
Odd bug, any mention of it on the bug tracker?
Related
Hi,
I've been using a DESIRE HD for a long time , suddenly an issue has cropped up
1) My phone automatically uses the speaker when i receive or make a call !
Any Idea why is this happening?
i had the same issue for the last few weeks. i couldn't find a fix so ive just got into a habit of hitting speaker as soon as i make or recieve a call (to turn it OFF speakerphone) But...
the issue has now developed! one i make/recieve a call, and turn off speaker, the speaker continues to flick on and off throughout my call, mainly as it moves, depends on the tilt of the phone during the call. its like an overly sensitive exaggeration of the "flip for speaker" feature, as it happens when its vertical. thing is, ive turned this feature on and off many times to try and resolve it, but it still happens!
has anyone got any ideas that might help???
thanx
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.
Ok, as per the title, and here are some things covering the issue:
Initially the speaker stopped working immediately after plugging the charger in. It is a genuine Pixel charger.
The problem went away in less that a day later, but reappeared straight after charging again.
Yet again the problem went away
Yesterday the issue reappeared randomly whilst using the phone and hasn't corrected itself since
The issue results in any short sound played giving exactly 16 feint clicks from the speaker, no crackling or coarse sounds, just 16 programmed clicks from the speaker. Press the home button - 16 clicks, like a comment on the Facebook app - 16 clicks
Playing a Youtube video results in constant feint clicking from the speaker, same frequency as the 16 clicks, but as said, constant.
Set the phone to "do not disturb" so no sounds from apps/software are allowed and the 16 clicks from phone interaction (home button etc etc) still happen exactly the same as before; this confuses me further as if it was ingress or a faulty speaker it would not give any sound while "do not disturb" is enabled. If it was a hardware fault, it'd have to be at chip level, so pointing toward software/firmware
Safemode has no effect
Factory reset has no effect
The Google "piano" boot up sound is not played.
Now, the very odd one; if I am browsing the Facebook app and auto play videos are on, the clicking sound is developed. To clarify, the video has not been clicked, it is not full screen, it is just there, on the newsfeed playing thus creating constant clicking while the video is playing. There would be NO sound playing if the speaker worked, but still, it clicks.
I'm unsure how the phone picks up audio playing for the volume rocker to adjust media volume instead of notification volume, but from what I can infer, it works on some sort of pass through. If the phone picks up sound, the volume rocker, when pressed, focuses on and adjusts media volume. As per number 11, in this state of a video playing but NOT focused, the volume buttons revert to notification volumes, hence no sound coming from the app; why is the clicking apparent when there is no sound trying to be played?
Phone calls work fine
Phone calls with loud speaker do not work
Sound via headphones do work perfectly
I have tried checking to see if ingress via the headphone jack is causing the issue by plugging/unplugging headphones but this has had no effect.
Bluetooth is OFF
Have turned on headset in "System UI Tuner" in status bar to show if the phone thinks they are connected. There is no notification of this
Any ideas?
Regards​
Dave
whoa that's crazy, is it similar to the issue in this video?
https://www.youtube.com/watch?v=7ZH8lLFRWN4
does audio play through your earphones when connected or does this also come across as clicks?
fatapia said:
whoa that's crazy, is it similar to the issue in this video?
https://www.youtube.com/watch?v=7ZH8lLFRWN4
does audio play through your earphones when connected or does this also come across as clicks?
Click to expand...
Click to collapse
Headphones work as normal. Such a confusing issue with the phone. With regards​ to phone condition etc, it is two months old and in immaculate condition, never dropped or wet. It's my second pixel as my previous one died one day and wouldn't turn on again. Google are happy to replace, but as it's an intermittent fault they have warned me that if they don't find anything wrong when this phone by the time it gets back to them, I could have to stump the cost of a new phone.
They had organised a return, but a day later it started working again, so cancelled the return; now stopped working again
As for the video, will wait until I'm at a PC, can't hear what's going on in that one currently (on my phone haha).
EDIT
@fatapia - I have watched the video, the fault is nothing like that in the video. There is no sound no matter what, just 16 feint programmed clicks as mentioned before after every interaction with the phone that would make a click/sound, even on silent it still does it.
DavidVanstone said:
Headphones work as normal. Such a confusing issue with the phone. With regards​ to phone condition etc, it is two months old and in immaculate condition, never dropped or wet. It's my second pixel as my previous one died one day and wouldn't turn on again. Google are happy to replace, but as it's an intermittent fault they have warned me that if they don't find anything wrong when this phone by the time it gets back to them, I could have to stump the cost of a new phone.
They had organised a return, but a day later it started working again, so cancelled the return; now stopped working again
As for the video, will wait until I'm at a PC, can't hear what's going on in that one currently (on my phone haha).
EDIT
@fatapia - I have watched the video, the fault is nothing like that in the video. There is no sound no matter what, just 16 feint programmed clicks as mentioned before after every interaction with the phone that would make a click/sound, even on silent it still does it.
Click to expand...
Click to collapse
Did you ever solve this? I just started having the same exact problem with the 8.1 update.
Sent from my Nexus 7 using Tapatalk
psychephylax said:
Did you ever solve this? I just started having the same exact problem with the 8.1 update.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm having the same issue on my Pixel 1st gen too after my 8.1.0 update. In phone calls, I can only hear sound when i turn on speaker phone. Headphone sound works fine, but all media volume isn't playing.
Did anyone solve this? I am having the same issues. No sound. But ringtones and notifications work fine. Speakphone only during calls.
Google approved an RMA for mine and sent me a refurbished handset which works great
Sent from my Nexus 7 using Tapatalk
Haven't seen this specific issue answered yet - if its a duplicate somewhere a point to the right thread would be appreciated.
For whatever reason over the last couple months, the volume on my pixel 2xl will jump way up (or way down) when on bluetooth either after a call or after using google assistant. It doesn't seem to happen everytime, but just now I was listening to music on my bluetooth headphones at my desk and got a call. I took the call on the headphones by answering the phone and then as soon as I hung up, the volume on the phone shot up to 100% which was not enjoyable.
This also happens when connected to my truck (Ford SYNC) or my running earbuds, and it can also crank the media volume way down (happens frequently in the truck) after a call, at which point I have to manually adjust the volume again. The same activity also happens if I activate google assistant and issue a voice command, but in both cases it is not 100% consistent. It appears like the system is trying to dynamically change the volume for some perceived situation, but it sucks at it.
I also use A2DP app for volume control settings and app launching for all my connections, but I have used that since I got this phone 2 years ago and none of the settings have changed.
Anyone had similar behavior and found a fix? It is really annoying when my music goes so low that I can't even hear it in the truck after a call, and equally annoying when I have headphones on and it cranks the volume up and tries to blow out my eardrums.