Hi everyone, please help me with an issue. When I drive, my phone is connected to my bluetooth receiver. Problem is, when that happens, Android voice recognition does not seem to work. I would occasionally like to be able to dictate a text message, however the microphone seems to be disabled when I tap the mic button on the keyboard. This happens no matter what bluetooth headset I have connected. However, S Voice seems to turn the mic on, for voice recognition. So, is there any way for me to fix this and use Android's native voice recognition? I am running a stock rooted ROM and stock kernel. I appreciate all your suggestions.
I recently bought a BT car speakerphone and tried to place a call using my Xperia ZL (on 4.2.2). The call goes thru but I cannot hear anything from the speaker. I can hear sound if I play music but nothing if I make a phone call. I checked with my wife’s ZL (on 4.3) and the BT speaker works fine.
I tried my phone with another BT speaker and still no go for voice calls. Music is fine though. I believe there is an issue with the phone calls over the BT connection.
Anybody else experienced this issue? Any possible fix? I hate to send it back to Sony. Thanks
hangouts dialer problems mic not working end call speaker not working
Hi,
I have a couple android phones and hangouts dialer works just fine on my rooted htc evo 3d. The galaxy s3 sprint phone has problems with hangouts dialer that maybe some one can help me with.
The microphone is not working again. Last time I did an update it stopped working so I uninstalled and reinstalled and it started working again. Today it will not work again and I tried reinstalling the app but it did not work.
The speakerphone and end call button will not work on the galaxy s3 sprint phone. when I select these items it takes me back to the main dialer page showing an ongoing call. I can not hang up and I have to shutdown the phone to end call. If I have bluetooth connected these end call and speakerphone buttons will work though.
Does anyone know what the problem is with the galaxy s3 on hangouts dialer? Maybe I should just stick to HTC phones for now on?
Same problem here. Only fix so far is using a Touchwiz ROM. Lame. Hopefully someone fixes this. Stay vocal and talk to the devs. Ive been trying to sort this out all month. No one is of much help, honestly.
STAY VOCAL.
totbl said:
Same problem here. Only fix so far is using a Touchwiz ROM. Lame. Hopefully someone fixes this. Stay vocal and talk to the devs. Ive been trying to sort this out all month. No one is of much help, honestly.
STAY VOCAL.
Click to expand...
Click to collapse
I have the same problem. No one can hear me when I call them on google hangouts with out bluetooth. If I used a wired headset they still cant hear me. They can only hear me if I use bluetooth
customromlover said:
I have the same problem. No one can hear me when I call them on google hangouts with out bluetooth. If I used a wired headset they still cant hear me. They can only hear me if I use bluetooth
Click to expand...
Click to collapse
on the latest CM11 and 12.1 (unsupported) I found that it activates the microphone on the TOP of the phone, rather than at the bottom. Not sure how to swap it around. Had to go back to stock
Since I ported my number into Google Voice, I have been using Hangouts Dialer as my go-to voice service on my S3. My calls will usually connect after a 3-5 second pause. I can then hear the other person crystal clear, but they can only hear my voice garbled and extremely low volume. It doesn't matter if I'm on WiFi or mobile data. It doesn't matter if I make the call or receive the call. I am currently using PAC-man ROM 4.4.4.RC-3. Does anyone else have this issue or know how to solve it? Is there anyone who has been using Hangouts Dialer regularly that does not have this issue that can maybe help? Thank you!
OK, so after further testing I have discovered that Hangouts is using the wrong microphone for audio. It seems to be using the speakerphone microphone (at the top of the phone) instead of the handset microphone at the bottom. Is there any way to switch the microphone that is being used for just this application?
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.