Problems with google voice through hangouts - Xiaomi Mi Max 3 Questions & Answers

I use google voice through hangouts app. The problem is, when i am on speaker phone and talking on Hangout (google voice call), as soon as the screen
Turns off (after minute setting) the calls gets disconnected.
I want to be able to keep talking while the screen shuts off to conserve battery. On all other phones, the calls continues but on mi max 3 (global rom 10.3.2) , the call disconnects. Please show me how to fix it. Thanks.

Related

[Q] Google Voice calling blanks the screen

Hi everyone.
When I try to make a call using Google Voice, the screen blanks for the duration of the call. That means I can't use the keypad or enable the speaker.
As soon as the call is over I have control back.
This problem does not happen when making a call without Google Voice.
I've searched elsewhere on the forums and haven't found it mentioned quite this way.
Any suggestions?

New update voice issues.

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.

Calls default to being handled through watch all the time.

I have a Google Pixel and Huawei Watch (version 1). I've set up my watch to be able to make and receive calls, which works fine, however now my phone will default to the watch for all calls even if I don't touch the watch while making or receiving a call.
For example, I just received a call now, answered it on my phone (didn't touch the watch), and the call defaulted to the watch as a bluetooth device. This also happens when I make a call through the phone (again not touching the watch). Every time I have to look on the handset, and change the audio from bluetooth to handset in the call screen.
This also used to happen with my Xiaomi Mi5 which I recently changed from, so I know it's not something specific to this phone.
I like occasionally answering calls through my watch if I don't have my handset around, so I don't want to switch off this feature entirely, but I only want to do that when actually touching the answer button on my watch. Does anyone have any suggestions?

Phone calls take 5 or 6 seconds for audio to work

I've noticed recently that when answering a call I don't hear anything and the caller doesn't hear me for at least 5 seconds. That's long enough for the caller to hang up and call again, at which point the delay is only 1 or 2 seconds before all audio starts working. I've tried clearing the Phone app data, but that didn't help. I don't think it's the mic because OK Google works immediately. It's only happening on phone calls.
I'm running 8.1 DP1, so of course Google support won't help me.
enzoevo said:
I've noticed recently that when answering a call I don't hear anything and the caller doesn't hear me for at least 5 seconds. That's long enough for the caller to hang up and call again, at which point the delay is only 1 or 2 seconds before all audio starts working. I've tried clearing the Phone app data, but that didn't help. I don't think it's the mic because OK Google works immediately. It's only happening on phone calls.
I'm running 8.1 DP1, so of course Google support won't help me.
Click to expand...
Click to collapse
I had the same issue until I turned off Wifi calling.
Went away after that.
Kind of sucks but I manually turn it on in bad reception areas, you know Tier 3 DCs.
I checked, but wifi calling wasn't enabled. I enabled and disabled. Stab in the dark. Now to wait for someone to call me
This would happen to me on the original XL. It would take a few seconds after picking up the call for Wifi calling to kick in. Turning Wifi calling off should solve the issue.
Wifi calling was not enabled on the phone. Still getting the delay. I wonder if there's a setting with T-Mobile on the carrier side that's causing this.

Trivial solution for Galaxy Watch overtaking calls

Trivial solution.
For those who experiance overtaking calls via Watch, In phone call screen disable bluetooth icon.
.
Voice on watch picture 1.
Voice on phone picture 2
And it is permanent untill you switch vice versa.

Categories

Resources