microphone problem - Nokia 3.2 Questions & Answers

Hi everyone. My nokia 3.2's microphone stops working every now and then. but it doesn't seem to be a normal problem as it works perfectly for my phone calls, everyone can hear me. it just doesn't work when I try to record my voice on applications e.g sending voice message on social media, making voice command with google assistant. it won't work until I restart my phone, then it's fine for a couple of hours, then it stops working. the problem started when I had Android 9, I updated it to Android 10, I even reseted it but none of them has solved the problem. do you think rooting my phone might help?
I would appreciate if you could help me.

thenoidian said:
Hi everyone. My nokia 3.2's microphone stops working every now and then. but it doesn't seem to be a normal problem as it works perfectly for my phone calls, everyone can hear me. it just doesn't work when I try to record my voice on applications e.g sending voice message on social media, making voice command with google assistant. it won't work until I restart my phone, then it's fine for a couple of hours, then it stops working. the problem started when I had Android 9, I updated it to Android 10, I even reseted it but none of them has solved the problem. do you think rooting my phone might help?
I would appreciate if you could help me.
Click to expand...
Click to collapse
I had the very same problem, To fix this go to settings > Google > Account services > Search, Assistant and Voice > Google Assistant > Voice Match and then turn off Hey Google and Delete your voice model if you have one, then restart your Phone. This permanently fixed the issue for me so hopefully it does for you too.

Related

phone randomly goes directly to vm, no notification call occured, cont asks to reset

Reset app preferences! Any fixes for these issues?? Have cleared cache partition,. got 2 new sim cards to no avail. Randomly mine n my husbands phones go straight to vm without ringing or showing missed calls!! Same for my son in another state. Cust svc is no help. Have cleared app preferences multi times. Anyone else with these issues?! Any help appreciated.
I had that on mine when I was running 4.3, but only with wifi calling. first random incoming calls, then all incoming calls would go straight into voice mail and then I couldn't even call out on wifi. Temporary solution was to change preferences to cellular calling from wifi calling. Then I updated to 4.4.2 (nf4) and its fixed now and it works fine with wifi calling and all. I suspected t-mo made some changes in their server software and either accidently or on purpose never tested properly with older firmware, introducing some bug, but feel free to call it wrong guess. The reason I suspected problem was on their side, was that I have not updated or changed my phone at all, since before problem started and installed probably only 1 new program, which later I deleted it as first suspect, but deleting it didn't fix the problem at all.
Did you ever install google voice? I was having similar problems because I had installed google voice, then removed it, thinking everything would be fine. It turns out you need to change something on your Google account also. There was a previous thread about google voice.
No google voice in my case. The program I installed I think it's called Wechat for text, voice and video calls over internet. I deleted it after my family came back from overseas vacation since no longer needed, but that didn't fix wifi calling until firmware update. Could have been some settings got messed up and weren't restored until update.
smaisonville said:
Did you ever install google voice? I was having similar problems because I had installed google voice, then removed it, thinking everything would be fine. It turns out you need to change something on your Google account also. There was a previous thread about google voice.
Click to expand...
Click to collapse
thanks
I reflashed firmware from SamMobile. Appears to be working better. Difficult to tell 100% yet. Appears the app prefernce requests are no longer an issue.

Ok Google not working on Wear 2.0

I have an issue, Ok Google keyword is activated in the options of wear 2.0 but the keyword does nothing. if i long press the button the assistant come in but the keyword don't work. Is there a workaround? Am i the only one with this issue?
On my watch it works well.
Settings-presonalization-ok google.
Mike
sp5it said:
Settings-presonalization-ok google.
Mike
Click to expand...
Click to collapse
Already activated but no effect, trying factory reset
Ok, just pinpointed the issue, "ok google" works only if the language is set to english, don't work in french...
Problem was here too. I do reset/wipe my watch and now all work. And now battery is better. Yesterday in 12 hours 80%, today after reset in 6 hours 10%
Working now after 3 factory reset and changing language to english and to french thereafter.
Same problem after the OTA : Ok google doesn't work ! long press the button works fine !
After factory reset all works perfectly !
I have the same problem. I also noticed that instead of using assistant on push held it defaults to google search. That's why the keywords aren't working. I have factory reset my watch at least four times and the problem comes back after a couple of days. I am in English US and have switched it back and forth just for kicks. Has anyone had any luck?
edit: I also noticed my Talkback services are buggy and don't provide and example when I tap on the icon under the settings
joeanca said:
I have the same problem. I also noticed that instead of using assistant on push held it defaults to google search. That's why the keywords aren't working. I have factory reset my watch at least four times and the problem comes back after a couple of days. I am in English US and have switched it back and forth just for kicks. Has anyone had any luck?
edit: I also noticed my Talkback services are buggy and don't provide and example when I tap on the icon under the settings
Click to expand...
Click to collapse
Hello everybody,
As i've said it in my post above, a factory reset has resolved the problem and now Ok Google works perfectly !
BillalS3 said:
Hello everybody,
As i've said it in my post above, a factory reset has resolved the problem and now Ok Google works perfectly !
Click to expand...
Click to collapse
Did you actually take the time to read my post? I mentioned I have done that several times and the problem keeps coming back.
Hello joeanca
Yes I've taken time to read your post, and I don't understand why a factory reset don't resolve your problem. Because, for myself it resolves it.
Perhaps somebody else could have a new idea to help you
I have the same issue. Factory reset only fixes the issue for a few hours then it happens again (I think once they lose the connection between them (for example because of distance) and reconnect again. Factory reset also enables wi-fi again. The issue is that if the watch is connected only through Bluetooth with wi-fi closed, google assistant and play don't work , if you go in watch settings it says disconnected in Bluetooth but no "cloud" icon pops up at the screen and on phone Bluetooth settings it says connected furthermore the watch works perfectly like receiving notifications changes song track etc. Oh also the silence phone setting from android wear app doesn't work
I just had this problem and resolved it by dumb luck.
I originally synced two Google Accounts to my watch. After updating apps on the watch, OK Google detection hasn't worked.
I found that my default account in Google Assistant on my phone had changed from my primary account. I removed all but my primary account from the watch, and selected my primary account in Google Assistant. OK Google now works again on the watch.
Darkmage40 said:
[..]if you go in watch settings it says disconnected in Bluetooth but no "cloud" icon pops up at the screen and on phone Bluetooth settings it says connected furthermore the watch works perfectly like receiving notifications changes song track etc.[..]
Click to expand...
Click to collapse
This exactly my problem. The phone says it is connected and the watch works, but the Assistant only says it is offline and cannot understand me. That drives me crazy. I have only one account synced. This Thread is the only thread so far that has my exact problem in it. I know it is a little older, but is there anyone with an idea?
thx and regards
My issue is the Ok Google gets locked into a loop. Whatever the first command I speak to it after Ok Google.. it just loops. Be it What is the time, what day is, send a message, etc. it keeps looping on that command. only seems to affect my Huawei watch 2 classic. phone doesn't have the same issue. have rebooted watch. If i swipe the google assistant away and execute another command, it loops on that one. I have both Facer and Watchmaker watchface apps installed. an issue like this should not have been present in a beta stage so I have to wonder.. what could I have on my watch causing this?
--edit--
Well... it seems Wear 2.0 does NOT like more than one account on a watch. I had three accounts hooked to the watch. My phone's private account. My professional email account, and a purchases account. 3 accounts. Seems that just wasn't how it wanted to work things. As soon as I cut out the pro and purch accounts it starts acting right. I have one account that my android devices get to access for uniformity of data but nothing else gets to use it. I have several emails for various purposes.
So if you have more than one account, as others have found.. remove them down to a single account. Things will probably start working right.
And its back to looping. basically.. if I say Ok Google, then wait for the ready prompt and give it a command "Set an alarm" it will process that command, ask when I want the alarm for, but feed itself the "Set an Alarm" command, ask when, feed command back to itself, ask when... on and on.
Had the same problem. Deleting cache and data of Google app on the watch worked for me. OK google finally works, but I cannot send WhatsApp messages via ok Google, what worked a few days ago with manually starting google by press and hold the upper button.
With Google even talking back works now
i solved the ok googlo hotword problem by deleting chache and data of google app on my huawei watch 2 and it started working again

Question for Google Voice users.....

I've had this odd bug every now and then in which my phone automatically dials itself when it connects to the car. You didn't always know it until you tried to play music or something "Hey Google" related and you had no audio feedback.
This would only happen once every few weeks so it wasn't something I was always watching for. It happened again today and found it is related to Google Voice.
If Google Voice is open and in focus/being used when connecting to vehicle Bluetooth the phone will dial itself. It Google Voice is running in the background or opened after the connection three problem doesn't occur
Can anyone that uses Google Voice have the app open and in focus when it connects to your vehicle and see if you get the same self-dialing error?
cahiatt said:
I've had this odd bug every now and then in which my phone automatically dials itself when it connects to the car. You didn't always know it until you tried to play music or something "Hey Google" related and you had no audio feedback.
This would only happen once every few weeks so it wasn't something I was always watching for. It happened again today and found it is related to Google Voice.
If Google Voice is open and in focus/being used when connecting to vehicle Bluetooth the phone will dial itself. It Google Voice is running in the background or opened after the connection three problem doesn't occur
Can anyone that uses Google Voice have the app open and in focus when it connects to your vehicle and see if you get the same self-dialing error?
Click to expand...
Click to collapse
I get this at least once a week. At first it freaked me out until I realized that it wasn't really making a call. Now I ignore it. I didn't realize it was related to the app being open.

Whatsapp Microphone Bug In Pixel Experience

I have been using Pixel Experience PixelExperience_ginkgo-10.0-20201223-1313-OFFICIAL.zip for about 2 weeks now. But i am still facing one problem. Everytime im receiving Whatsapp Calls, my phone start lagging, hanging, and eventually crashed. Also happened when i try to record voice note.
I tried:
- Rebooting the phone
- Revoking whatsapp microphone permission and allow it again
Do you know what's the problem? I tried to not uninstall the app or doing factory reset because that will delete all my whatsapp chats. I do have backup on Gdrive but that will cost both my time and my limited internet usage.
Thanks to you all who tried to help me.
EDIT1: This problem only occurs in Whatsapp. I Tried to phone call on telegram, video call on gmeet, and etc, everthing works fine.
ipaaaaan said:
I have been using Pixel Experience PixelExperience_ginkgo-10.0-20201223-1313-OFFICIAL.zip for about 2 weeks now. But i am still facing one problem. Everytime im receiving Whatsapp Calls, my phone start lagging, hanging, and eventually crashed. Also happened when i try to record voice note.
I tried:
- Rebooting the phone
- Revoking whatsapp microphone permission and allow it again
Do you know what's the problem? I tried to not uninstall the app or doing factory reset because that will delete all my whatsapp chats. I do have backup on Gdrive but that will cost both my time and my limited internet usage.
Thanks to you all who tried to help me.
EDIT1: This problem only occurs in Whatsapp. I Tried to phone call on telegram, video call on gmeet, and etc, everthing works fine.
Click to expand...
Click to collapse
Btw can you also please check if the google dialer works and the call recording option is shown during a call? Thanks
change vendor.audio.feature.compr_voip.enable = true to false in vendor/build.prop

Question Bugs - Voice Dictation & Lock screen Text

Hi all!
I got my RM8P yesterday. I really like the device, but definitely see the software lackings that everyone has mentioned.
My current bugs:
1. I copied my data from my Pixel 6 Pro to the RMP8. It also copied the lock screen text I had "My Google Pixel 6 Pro, *****es". So when I go into personalized setting to try to change this text, it won't let me. When I click the option, it just goes back to the Settings menu.
2. More importantly, my voice dictation/voice to text functionality is now broken. It was fine until this afternoon when I updated a bunch of apps in Play Store. Now, no voice dictation is working for any app. I've tried every possible app and rebooting. The OK Google still works so it's "hearing" my voice in general.
Any feedback?
Thanks!
EDIT: I figured out that enabling Google Assistant (Hey Google) broke the voice dictation. Strange that it breaks it.
darbylonia said:
Hi all!
I got my RM8P yesterday. I really like the device, but definitely see the software lackings that everyone has mentioned.
My current bugs:
1. I copied my data from my Pixel 6 Pro to the RMP8. It also copied the lock screen text I had "My Google Pixel 6 Pro, *****es". So when I go into personalized setting to try to change this text, it won't let me. When I click the option, it just goes back to the Settings menu.
2. More importantly, my voice dictation/voice to text functionality is now broken. It was fine until this afternoon when I updated a bunch of apps in Play Store. Now, no voice dictation is working for any app. I've tried every possible app and rebooting. The OK Google still works so it's "hearing" my voice in general.
Any feedback?
Thanks!
EDIT: I figured out that enabling Google Assistant (Hey Google) broke the voice dictation. Strange that it breaks it.
Click to expand...
Click to collapse
I was about to tell you that disabling hey google fixed the dictation thing. The first os layer is funny af, it does that and doesn't carry the swipe between apps gesture. And a bunch of things, I worked the hey google with the swipe from a corner gesture tbh I don't use Google assistant that much but still it was a thing
Alextakatu said:
I was about to tell you that disabling hey google fixed the dictation thing. The first os layer is funny af, it does that and doesn't carry the swipe between apps gesture. And a bunch of things, I worked the hey google with the swipe from a corner gesture tbh I don't use Google assistant that much but still it was a thing
Click to expand...
Click to collapse
I don't use hey Google assistant too often, but I do use it occasionally. It's just strange that I have to choose between enabling that functionality and enabling voice dictation. I guess I'll choose the voice dictation and give up Google assistant or enable it when I feel I need to use it at times. I'm not sure it's a Red Magic thing as it may be a broader Android thing.
darbylonia said:
I don't use hey Google assistant too often, but I do use it occasionally. It's just strange that I have to choose between enabling that functionality and enabling voice dictation. I guess I'll choose the voice dictation and give up Google assistant or enable it when I feel I need to use it at times. I'm not sure it's a Red Magic thing as it may be a broader Android thing.
Click to expand...
Click to collapse
Pretty sure it's only a redmagic thing. Their support has been largely useless when I attempted to alert them to this issue.
darbylonia said:
Hi all!
I got my RM8P yesterday. I really like the device, but definitely see the software lackings that everyone has mentioned.
My current bugs:
1. I copied my data from my Pixel 6 Pro to the RMP8. It also copied the lock screen text I had "My Google Pixel 6 Pro, *****es". So when I go into personalized setting to try to change this text, it won't let me. When I click the option, it just goes back to the Settings menu.
2. More importantly, my voice dictation/voice to text functionality is now broken. It was fine until this afternoon when I updated a bunch of apps in Play Store. Now, no voice dictation is working for any app. I've tried every possible app and rebooting. The OK Google still works so it's "hearing" my voice in general.
Any feedback?
Thanks!
EDIT: I figured out that enabling Google Assistant (Hey Google) broke the voice dictation. Strange that it breaks it.
Click to expand...
Click to collapse
Hello, I have Alexa installed as the main assistant, if you select it as the default transcription program, it already works for you to transcribe messages. The failure after several tests I have realized that when you select Google as an assistant it stops working, the mobile does not listen to you. I have already opened several incidents on the Magic network page but they only tell me that I formatted the mobile.

Categories

Resources