Related
With this new rom I can now enable conformation when using MS voice command 1.6. Before i would have to disable conformation in order to use bluetooth with MS voice command, this is no longer a problem; can any one else confirm this?
Wow, I so have to check this out.
No lie! ha ha ha it works! saweet!
well, now caller id and messages arent sent through
there is a reg tweak which will let the caller id come through the bt headset,
sorry but not sure where it is.
Notification
I set the notification options to "Announce notifications using bluetooth hands free if available" and it works. When the phone rings I hear the ringing and the announcement through the headset. I did not do any registry changes as I used to do before this ROM. I am using a Jabra 8010.
I'm more excited about the confirmations working on 3.16 than even GPS and EVDO-A. I don't keep my headset in my ear very much, so I haven't even checked to see if notifications work through the headset.
JimSmith94 said:
I'm more excited about the confirmations working on 3.16 than even GPS and EVDO-A. I don't keep my headset in my ear very much, so I haven't even checked to see if notifications work through the headset.
Click to expand...
Click to collapse
I can also confirm that this problem is fixed. I took the plunge with the pre-release ROM and it's been working like a charm. I have not had to modify the registry to get notifications to work, either. I just went to Settings->Voice Command and setup my preferences.
I also have to agree that the Bluetooth fix is more exciting to me than the GPS stuff since I use this feature way more than I use GPS.
where can I get this fix?
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
mtnTOUCH said:
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
Click to expand...
Click to collapse
touch forum? lol. we have a newer radio rom and bt drivers witch fixed the issue, so wait for someone to port them over. Sorry man.
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
taxilian said:
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
Click to expand...
Click to collapse
Did you assign Voice Command to Button 5? (Start > Settings > Buttons). I have Button 5 set to Voice Command, and Button 5 (Press & Hold) set to Record.
mtnTOUCH said:
HTC TOUCH
VOICE COMMAND 1.6
NO CONFIRMATIONS THOUGH BLUETOOTH
Where can I get this fix?
Click to expand...
Click to collapse
This worked for me on my wizard and Hermes
taxilian said:
Question: bluetooth definitely seems to be working 100% better (no longer disconnecting randomly, I can shift all sound to it now if I want, etc), but the button on my bluetooth earpiece no longer brings up the voice command prompt. When I run the bluetooth voicecommand proggy thingy it works, but I can't do it from the earpiece.
Am I missing something ridiculous? I've done some searching on the forums, but haven't found anything. ('course, I might just be pathetic and searching)
Click to expand...
Click to collapse
i have the same problem. after a hard reset and then installing ONLY voice command, it works PERFECTLY - announcements, confirmations, everything. after a soft reset something gets changed in the registry and it no longer is activated from the headset.
is there a program that can tell you what has been changed in a registry?
its frustrating that is working PERFECTLY and only upon a soft reset does it not work anymore...
ok... still trying to isolate what the problem is.
here are the symptoms. as before, everything works GREAT until i soft reset.
then, rather than the headset triggering the voice command, it opens the dialer app and hangs open. i have to uncheck the object in bluetooth settings, save, then recheck to reset headset.
i am trying some more stuff...
i found a PITA fix. apparently whatever happens after a soft reset messes up the bluetooth files. so i uninstall, soft reset, then reinstall.
sad thing is - i'd rather do this than keep trying to figure out what is causing this conflict...
1.6 Voice Command; announcements not coming over incoming calls
I have a ppc-6800 sprint mogul.
I have WM6 Professional
CE OS 5.2.1238 (Build 17745.0.2.3)
My issue is that when I installed VC 1.6, everything works fine, except I don't get the incoming call or calendar announcements. I have checked the appropriate boxes in the VC options settings to no avail.
I am certainly no xda-developer, and can become easily confused when talking about registry edits and .dll files. If anyone can provide explicit directions on how to fix, I would truly appreciate.
JFA
Hi all,
I have searched the forums and have not seen anything related to my question so please forgive me if this is repetitive.
I have never used a BT Headset before and I just bought a little cheap one today. It works very well and I only paid $10 bucks for it so I am quite satisfied but...
In the instructions, it tells me how to make "voice calls" from the headset but it says to "enable the function" on my mobile device and I cannot find where you "ENABLE" this on my phone.
Can anyone point me to where and how I do this? Do I need an app of some kind to do this or should this function be native to the SGSII?
If this may be ROM related... Please see my siggy for info...
Please advise...
Thanks,
Just pressing the button on the Bluetooth device for a second should bring up the voice controls.
Thanks for the reply but that is the problem... Pressing the button on the BT device does nothing. I hear the tone in my ear as the instructions mention but nothing opens up on the phone.
I realized that I did not have the voice Dialer apk installed so I installed it but still nothing happens when I press the BT Device button. It only opens when I press the app on screen and I want COMPLETE HANDS FREE...
Try making sure you have VoiceToGo installed and your rom didn't replace it with that homemyhome app. I never had voice dialer work with the BT button either so I had to stay stock voice apps.
What rom are you on? I can't see sigs since I disabled them a long time ago.
shadowofdarkness said:
Try making sure you have VoiceToGo installed and your rom didn't replace it with that homemyhome app. I never had voice dialer work with the BT button either so I had to stay stock voice apps.
What rom are you on? I can't see sigs since I disabled them a long time ago.
Click to expand...
Click to collapse
I have "Vlingo" installed and I think that is what you mean by "voice to go" if Im not mistaken. Vlingo only works if you press all of the appropriate buttons on screen and only accepts commands from the phones mic and not the BT.
I installed another app called "Choice Dialer Free" and it is much better except that I still have to enable the app first on screen and then give commands so that is still NOT what I want.
I am on CheckRom Revo.v4
***EDIT*** I found the Samsung Voicetogo app and am installing it now. I will see how that works and advise...
On my phone it works fine from the BT device I start it using the button on the BT device then talk into it.
Your phone isn't pin or pattern locked right? Because Samsung stupidly removed the ability to use voice commands when locked (normal slide to unlock is fine though) I had to give up security for the ability to use my phone when driving because of it.
I am also from Alberta so I know the laws you are dealing with that require voice dialing.
I wonder if any others you installed are conflicting with voicetogo which is the preinstalled Samsung version of Vlingo.
shadowofdarkness said:
On my phone it works fine from the BT device I start it using the button on the BT device then talk into it.
Your phone isn't pin or pattern locked right? Because Samsung stupidly removed the ability to use voice commands when locked (normal slide to unlock is fine though) I had to give up security for the ability to use my phone when driving because of it.
I am also from Alberta so I know the laws you are dealing with that require voice dialing.
I wonder if any others you installed are conflicting with voicetogo which is the preinstalled Samsung version of Vlingo.
Click to expand...
Click to collapse
I am using the JKAY Deluxe Mod that comes with my ROM and yes... I have the "slide to unlock" but under it I have the "pin lock" as well however... even when the phone is unlocked it is not working.
I just installed the "voicetogo" and will give it a try and report back...
shadowofdarkness said:
On my phone it works fine from the BT device I start it using the button on the BT device then talk into it.
Your phone isn't pin or pattern locked right? Because Samsung stupidly removed the ability to use voice commands when locked (normal slide to unlock is fine though) I had to give up security for the ability to use my phone when driving because of it.
I am also from Alberta so I know the laws you are dealing with that require voice dialing.
I wonder if any others you installed are conflicting with voicetogo which is the preinstalled Samsung version of Vlingo.
Click to expand...
Click to collapse
You ROCK my friend!!! With the Samsung "voicetogo" app reinstalled this now works as it should and LIKE A CHARM!!! Best $10.00 I ever spent at HMV!!!
I have clicked thanks to you and THANKS TO YOU!!! Lol...
No problem.
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.
Hi. My dad bought LG L9 P760, soft V20B. Every site says that he can use voice dialing, but he cannot. One quick button press start redial function, two quick do nothing, same as one long. Tested on nokia and SE WM600 bluetooth headset (music flow without problems). Is there a way to enable this option, maybe CyanogenMod, other rom or something, because it was primary function in his old Nokia C6-01?
Ed. Roms with CM works, and long press start voice dialer, but headset make "modem" noise only and caller app hangs.
Did this ever worked for you? I just got a LG-769 and can't use the Bluetooth to voice dial. Pressing the button on the Bluetooth does not do anything when using it with other phones it will ask me to 'Say a Name' to call.
voodoodoo1226 said:
Did this ever worked for you? I just got a LG-769 and can't use the Bluetooth to voice dial. Pressing the button on the Bluetooth does not do anything when using it with other phones it will ask me to 'Say a Name' to call.
Click to expand...
Click to collapse
I have the same issue with the 769 they forced me to have (they called it "alternate swap"). It's because the "Voice Dialing" app is missing from the phone. If you look at any Android phone going all the way back to the G1, there's an app on there just called Voice Dialing or Voice Dialer. That's the app that gets called whenever you push the dial button on your bluetooth headset. Because that app is MIA on the L9, there's nothing there for the bluetooth system to bring up. I'm still trying to find a way to dump that app from the G2X I have lying around and see if that fixes it. From what I've seen, third party voice dialer apps don't work because the headset is very specifically trying to call up that application at some level. If anyone else has been able to find a fix for this, I'd be interested.
neo1piv014 said:
I have the same issue with the 769 they forced me to have (they called it "alternate swap"). It's because the "Voice Dialing" app is missing from the phone. If you look at any Android phone going all the way back to the G1, there's an app on there just called Voice Dialing or Voice Dialer. That's the app that gets called whenever you push the dial button on your bluetooth headset. Because that app is MIA on the L9, there's nothing there for the bluetooth system to bring up. I'm still trying to find a way to dump that app from the G2X I have lying around and see if that fixes it. From what I've seen, third party voice dialer apps don't work because the headset is very specifically trying to call up that application at some level. If anyone else has been able to find a fix for this, I'd be interested.
Click to expand...
Click to collapse
I gave up on this a while ago. I would be great if there is a fix though because I am still interested.
voodoodoo1226 said:
I gave up on this a while ago. I would be great if there is a fix though because I am still interested.
Click to expand...
Click to collapse
Likewise. I feel it's as if the phone doesn't even recognize that the button has been pressed. I've tried several apps in the play store which try to capture this event to divert it to a different app and none of those work either. Any idea what I can do?
Bluetooth
Get a different phone. That's what I did.
If that's the only option I might just do that. But I would think this could be fixed since I can run a bluetooth keyboard just fine with the device. Also, pressing and holding the button on my bluetooth performs a redial as it should so I believe that the O.S. is ignoring an incoming command which someone with understanding might be fixable. Does an aftermarket ROM or different kernel fix the issue?
jjtjp said:
If that's the only option I might just do that. But I would think this could be fixed since I can run a bluetooth keyboard just fine with the device. Also, pressing and holding the button on my bluetooth performs a redial as it should so I believe that the O.S. is ignoring an incoming command which someone with understanding might be fixable. Does an aftermarket ROM or different kernel fix the issue?
Click to expand...
Click to collapse
Artas182x have rom with working BT voice 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.