[Q] Voice Mate Issue - Sprint LG G3

I don't own an LG G3 myself, I am just doing this to help a customer who was having issues.
Every time that we went to make a voice command on voice mate via Holding Home key and going to upper left onto voice mate. The Signal to start speaking replayed over and over until you went to the home screen of the phone.
Disabling all of the Voice Mate Services did not fix it, neither did Force Stopping and Clearing all of their Data/Cache.
He is going to come back in a few days, and I wanted to see if anyone had any fixes or proposals for fixing.
If not he will be returning it and going to an S4 which is a huge downgrade.
All Help is thanked!

Seems to be a ton of issues even for G2 users. Did you recommend Google Now?
sent from my LG G3

Related

FIXED: Answer button doesn't answer, data connection turns off after call

EDIT:
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
That post fixed my problem, as well as fixed the problem which the data connection turns off after a call.
Hey guys, sup?
I have a huge problem with my TELUS Touch Pro. Great phone, but just one problem...
Whenever somebody calls me, I can't answer the phone. The onscreen "Answer" button doesn't work, the Talk button doesn't work, pressing the Select button doesn't work...pressing the headphone button does, but sometimes my headphones are in my pocket, or sometimes they're not with me at all!
The only way I can answer them is by ignoring the call, and calling them back. It sucks big time.
Anybody have a solution? And no, I'm not hard-resetting my phone. It started doing this for my first call, so I'm pretty sure it's not my fault.
HEEAAALLLPPP!!!
Is this the stock ROM?
Do you have BT on and connected?
Mine started doing that yesterday. I did a hard reset and so far everythings back to normal. Still do not know what it was tho
I just had my TP replaced and the new one did the same thing, I did not notice until a few days later as I use a bluetooth headset and pushing the answer key on the headset worked. I had to RTN the device to make it work properly. Have not had a problem since. it has been aabout a week and a half.
Sometimes I've noticed this happens when my memory is tied up elsewhere, ie media player or something. Try soft resetting your phone every morning that might help clear it up.
I have had this happen with me on my Titan which I recently traded in for my Touch Pro, and also on my Touch Pro. I noticed it coincided with installing iGo8 GPS software on both. A hard reset was the only way I found to fix it. Uninstalling the software did not do the trick. I could be wrong about the software title I am blaming, but I have everything reloaded on my phone except that, and all is well. I do have a Slide To Answer incoming call screen now with the MightyRom 4.9.5 rom installed, maybe this is a work around, don't know for sure. If anyone else has more feedback, let me know. I would love to find a fix for it so I can use my GPS software.
Mine started doing this crap last night. I reinstalled the S2A cab and just let it go.
I am starting to think it might just be the telus network being a boatload of suck. Mine does it with the stock rom without any programs loaded from time to time. I am thinking it must be the tower failing to acknowledge that you want to answer the call, so the phone keeps ringing becuase it sees there is an incoming call but the tower ignores that you are trying to answer it. This is just my guess based on what I have read about CDMA, I wonder if any GSM users have the same issue.....
Do any of you have Advanced Configuration installed? This is what caused this problem for mine and my brother's TP. Uninstalling didn't fix it. Had to hard reset.
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
earthtodigi said:
Yes, this is a known issue with Advanced Config, perhaps some other apps as well. Try this fix.
http://forum.ppcgeeks.com/showthread.php?t=40427
Click to expand...
Click to collapse
I can tell you that this will more than likely fix this for you. Mine was doing the same thing, applied this, done and shut! Good luck.
OMG OMG OMG thanks!!!! That also fixed the problem where it ended the data connection after the call.
Sorry I took so long, I THOUGHT I was subscribed to the thread...
Thanks again!

[Q] Bluetooth and Voice Search not working. - Returning?

I’m coming from an EVO 4G and I forget how I finally got it working but I was able to use Voice Search or the Bluetooth headset to make calls by name from the folks in my contacts list.
I do remember that the voice search for making calls or sending text will not use your phone contacts but only your Google contacts. That was the only real gotcha I recall. I had to export my contacts, then import them into Google contacts and then link the two contacts together. Then the voice search would finally work.
I had done this on the DNA but the Voice Search would still not work. I finally had to go into the Voice Search settings under Phone Search and remove everything but “People”. Now when I say “Call: Bob” it pops up Bobs contact info and dials him instead of doing a Google search for “Call: Bob” or whatever. By default it has 4 or 5 things checked including People but it just did not work for me. ???
This did not however affect the Bluetooth headset dialing. It still just says “I didn’t catch that.” or tries to dial voice mail or random numbers. So, it’s still acts like the contacts list is empty.
Any ideas?
The Hotword detection is also not working. “Say Google to launch voice search.”
Thanks.
Hmm… Just me then?
Just over 250 views and no one can say they do or don't have the issue?
I did speak to a few tech support folks at Verizon and HTC but they could not tell me anything. I think I'm taking the phone back in the next few days. I like the phone but a phone that can’t dial from the headset is kind of a big deal.
I am curious about this too.
nabbed said:
I am curious about this too.
Click to expand...
Click to collapse
Same here .It mite be a hardwear/softwear problem. IDK maybe your phone settings or something.But I would take it back
syler2012 said:
Same here .It mite be a hardwear/softwear problem. IDK maybe your phone settings or something.But I would take it back
Click to expand...
Click to collapse
I can confirm the same problem on GS3 running CM10 latest nightlies. It's a Gapps issue....We need a way to force gapps to listen to bluetooth mic....
I think it is a problem with Bluetooth, Jellybean, and Google Now/Voice. This same type of issue was reported on the Galaxy nexus once it had been updated to Jellybean.
Some GN users installed alternative dialers/voice assistants and had success over BT.
I think Android 4.1 has some issues with BT. Android 4.2 switched to a completely new stack, and that too is experiencing problems, or perhaps growing pains. The fact that Android switched bt stacks from 4.1 to 4.2 leads me to believe that Google engineers ran into some deep issues with 4.1, and decided it was better to start from scratch with 4.2 (related a whole host of BT issues, including BT 4, low power modes, AVRCP etc., and interfacing them with the microphone for google voice search/now.
I just took it back and of course the Verizon rep had never heard of any issue with JB. So I showed it to him.
Of course I still had to pay the restocking fee.

Voice command keeps popping up randomly

This is very annoying and it happens a lot when I'm listening to a podcast or music in my car using the aux port. It also seems to happen a lot when my data is turned off and my phone is picked up and put down randomly. Really starting to piss me off and I have disabled voice command settings to no avail. Anyone else having problems like this and what can I do to solve this without root? I also just updated to the latest ota so I'll have to see if it fixes this problem later.
goodfella44 said:
This is very annoying and it happens a lot when I'm listening to a podcast or music in my car using the aux port. It also seems to happen a lot when my data is turned off and my phone is picked up and put down randomly. Really starting to piss me off and I have disabled voice command settings to no avail. Anyone else having problems like this and what can I do to solve this without root? I also just updated to the latest ota so I'll have to see if it fixes this problem later.
Click to expand...
Click to collapse
If it's the same thing, it happened to me also. It's the program called Voice Mate. You need to freeze or disable that program and all is good. Try settings/application manager and go to the "all" tab. Search for anything that has "voice mate" in it. Disable it.
IndianaBond said:
If it's the same thing, it happened to me also. It's the program called Voice Mate. You need to freeze or disable that program and all is good. Try settings/application manager and go to the "all" tab. Search for anything that has "voice mate" in it. Disable it.
Click to expand...
Click to collapse
I'm having the same problem, but i the disable button is grayed out. I've tried clearing the cache and uninstalling the updates, but it still won't stop.
princessyoku said:
I'm having the same problem, but i the disable button is grayed out. I've tried clearing the cache and uninstalling the updates, but it still won't stop.
Click to expand...
Click to collapse
Are you rooted? If so, use Titanium Backup to freeze it.
Did anyone find a solution this problem? It is happening to me too (especially when I'm playing music or when 4g is off) and I can't disable Voice Mate because it is greyed out.
simabd said:
Did anyone find a solution this problem? It is happening to me too (especially when I'm playing music or when 4g is off) and I can't disable Voice Mate because it is greyed out.
Click to expand...
Click to collapse
Took me weeks to figure out but I had to download the swift keyboard app, then remove my PIN to get into the phone, then go into SETTINGS, BACKUP & RESTORE, then Factory data reset.
Be sure to backup all your data first.
I read another post last night in the LG G3 General Forum about this issue. Several of the posters stated that the 3.5mm audio plug is causing the voice mate and voice command to activate when using the headphone port. Several people also stated that they could duplicate the concern repeatedly by turning or twisting the plug. Don't know if it helps anyone here but it looks like the same complaints I read about last night. I'll see if I can find the OP that discussed the issue and post it back here if I can.
Has anyone found a solution? It's happening the same thing to me. Every time I wanna use the jack port (just to listen to music), Voice Mate pops out and it's really getting on my nerves!! I wanna get rid of it, but I can't delete it, just deactivate it (and I did, but it keeps popping out)... I don't wanna be root, because I'm scared of messing up my phone. If any of you guys found the solution without being a root, I'd be truly thankful for life!
OH MY GOD IT'S BEEN HAPPENING TO ME TOO AND I THOUGHT I WAS CRAZY.
I found that it may have been related to water -- when I was running and getting sweaty, or it was raining, the problems were happening. So in terms of what I've done, I have frozen: LG VoiceCommandSpeechPack, Voice Command, Voice Mate, and Voice Mate Engine. This didn't fully fix the issue -- now, I just get random pauses and unpauses occasionally and it's due to the same problem of the jack port being wonky. It fits perfectly, it's not jimmying inside the port or anything but it's definitely re-creatable, it's such an annoying issue...
It's weird, after many restarts and cache clears the issue has definitely gone away, where before it made listening to music unbearable now it happens once in a blue moon, again subjectively I think it might be moisture or water or something.
This began harassing me also two days ago. Nothing fixes it that an ordinary user can get to, including what little I can get to with Google Settings/Search & Now/Voice/OK Google/. In my case, I cannot manually cause the effect by doing anything with the 3.5mm audio jack on the phone or any of several earbud jacks. Think I am going in to my cell phone vendor tonight after work and raise my voice a little to see if I can get them to fix the problem. Sux! Almost makes the cell phone unusable.
fast69mopar said:
I read another post last night in the LG G3 General Forum about this issue. Several of the posters stated that the 3.5mm audio plug is causing the voice mate and voice command to activate when using the headphone port. Several people also stated that they could duplicate the concern repeatedly by turning or twisting the plug. Don't know if it helps anyone here but it looks like the same complaints I read about last night. I'll see if I can find the OP that discussed the issue and post it back here if I can.
Click to expand...
Click to collapse
Any chance you can find us that OP? It's a pretty annoying bug....

"Tap to speak" box won't close or go away

Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk

Android 10 update broke calling

Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.

Categories

Resources