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
"Fortunately" it's only happening in FB messenger right now... but I've been hearing horror stories after the last update... Every outgoing or incoming call from FBM is automatically on speakerphone and it cannot be turned off... very frustrating for sure!!
Anyways, has anyone had the same problem and if so, how did you fix it
Thanks! :good:
Nobody at all??
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.
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?
So this is a weird and sporadic issue and I first noticed it on Nougat but it has persisted since the upgrade to Oreo. Occasionally, I'll answer a call and my ringtone continues to play to the point where I need to either wait 10 - 15 sec for it to stop or I need to hang up and call the person back. Doesn't happen every call - hard to quantify how often it does happen - but enough to be annoying. I've gone to no ringtones / vibration only for phone calls due to the issue. Anyone else experience this? Any ideas?