Now that Google Assistant is now available on the Pixel C, when I try to train my voice, I always get: Trouble with microphone. Try again in a few seconds.
Anybody is having the same issue?
Android 8.1 Stock with the Google App 7.17.28.21
Yeah, sadly I think it's because the Pixel C still doesn't have Google Assistant, as evidenced by the "Screen Search" option and lack of a "Google Assistant" option. To further back this position, Google's official statement announcing Assistant for tablets only mentioned Marshmallow and Nougat.
Yes, I have this problem. Google app update wanted to initially train my voice for "Hey Google" and then flashes up a screen for a micro-second as though to go through the set-up and then a toast error Trouble with Microphone.
Also Google Assistant isn't available. The roll-out of Assistant is only for US English at the moment and I don't think this app update was achieving that.
Same here. I'd been using the build.prop edit, and it was working great for months. Recently I started getting this flash of a screen for a micro-second (like m+a+r+k). So I tried toggling the setting off and back on. Now I cannot re-enable the "OK Google" voice detection at all, and it says "not available for this language" (English-US). So I did a factory reset, re-configured everything, and tried enabling it... Nope. Still grayed out.
So I disabled the build.prop edit (set it back to false), and rebooted again. This time I tried something a little different, I tried changing the language settings to "English-Generic". Going back into the "OK Google" detection screen, I can now toggle it on, and train my voice.
So rather than train it without the "Hey Google" option, I thought I'd skip that and re-enable Google Assistant through the build.prop edit. Going back into that setting, it's grayed out again. So I toggled back and forth from English-US and English-Generic, but if Google Assistant is enabled, they forcibly disable the "OK Google" detection, even though the device is clearly capable and compatible, since I've been using it this way for a year now....
Anybody got any ideas? Maybe some ADB commands to toggle some settings we don't have GUI access to?
**Edit**
After making these changes, I uninstalled the Google app (since it's a system app, you just revert to the original version released with this ROM). Now I can re-train my voice, minus the "Hey Google" that this latest update includes. So, I'm turning off all auto-updates until they get this figured out. I'll just update all other apps manually.
Note for those who want to use Google Assistant: It's really easy now if you're rooted. Just use a root file explorer (I use ES File Explorer Pro) and go to /system. Now open up the build.prop file with the editor of your choice (I use the ES Note Editor, since it already has root permissions), and find the line that says ro.opa.eligible_device=false, and delete the word false and replace it with true, save and reboot.
michaave said:
Note for those who want to use Google Assistant: It's really easy now if you're rooted. Just use a root file explorer (I use ES File Explorer Pro) and go to /system. Now open up the build.prop file with the editor of your choice (I use the ES Note Editor, since it already has root permissions), and find the line that says ro.opa.eligible_device=false, and delete the word false and replace it with true, save and reboot.
Click to expand...
Click to collapse
Thanks for that. Tried it and when I say "OK Google" the screen turns to portrait mode. Google Assistant will only work in Portrait mode? Unbelievable!
Opened the Google app and finally got it to set up "Hey Google". Then it immediately switched off 'Say "OK Google" any time' and 'Unlock with Voice match' - both greyed out!
However Assistant is working just in Portrait mode. I knew Google didn't really give a damn about tablets but this really is quite unbelievable.
They seem to be deliberately holding us back for some reason... I can't imagine what. But as far as the "Hey Google" thing, that appears to be a feature of the updated version of the Google app, so if you see the option for "Hey Google", your options will be grayed out. My solution is holding for now, with applying updates manually to avoid the auto-update of the Google app that deliberately sabotages us. I think I can use TitaniumBackup to break the market link of that one app, that's another option.
Confirmed, using TitaniumBackup you can locate the Google app and detach from the market. In doing so, all your other upates will go through fine, but the sabotaging update won't even show up.
Oh, and like you've observed, it only runs in portrait mode... That annoys me too.
TRY THIS - Go to Settings> Apps >Google >Storage >Manage Space >Clear Google Search Data & Clear ALL DATA . Then Open Google app >Settings >ON "OK GOOGLE >Retrain Voice model. Thanks.
Related
I could have sworn that before the update I could use the ok google detection anywhere (after I enabled it search settings). I tried it again, and it's grayed out in the Search, Voice settings in Google Search. Only the top main option to enable OK google voice allows me to toggle it on or off.
Are you sure you weren't using Google Now launcher?
efishta said:
I could have sworn that before the update I could use the ok google detection anywhere (after I enabled it search settings). I tried it again, and it's grayed out in the Search, Voice settings in Google Search. Only the top main option to enable OK google voice allows me to toggle it on or off.
Click to expand...
Click to collapse
Disable S Voice in app management, reboot, then go back to Google Now settings. It shouldn't be grayed out anymore.
Woot! Your response led me on the right path. I am and was using the Google now launcher, but the reason I kept referring to Google Search (which is actually just called Google in the app store) is because I thought it was a separate app responsible for the search functionality and that it hooked into the Now launcher. So I uninstalled the standalone Google app, rebooted phone, and now the option is no longer grayed out in the voice detection section of the Now launcher settings.
I think it's strange that Google allows the Google search app to coexist and override the built in Now launcher search functionality (or at the very least seems to pull the standalone Google search app's settings when I try and configure them through the Now launcher)
I'm sooo confused right now. What I uninstalled was just an update. The "Google" search app is still installed and asking me to update it, which means it came built in to the firmware. Aarrghh!
I updated it, and the option for OK Google functionality anywhere in the phone (different apps, screen off, etc) now became grayed out again. So its' at least linked to that it seems. I also don't get the ability to train the OK Google voice recognition (also grayed out) with the updated Google (search) app. The stock, original firmware version of the app does allow it. Aggravating!
Yup I noticed the same thing, the ability seems broken after the update.
Sent from my SAMSUNG-SM-N910A using Tapatalk
I followed the advice to disable the s voice app through the application manager, rebooted... And forgot to check it till today. Yes! Its working. I'm 99% sure it was disabling s voice that did it, and 1% possibility it was an a background google update... So I'm leaning toward the s voice fix.
Thank you to the 2nd poster above with the recommendation. Fixed it.
Hmm. My svoice is enabled and I am able 'ok google' from anywhere. Including the lock screen. I haven't actually used svoice since the update so I will try it and then see if ok google still works from everywhere.
I can 't force stop or disable S-Voice and OK Google options are grayed out. Any ideas?
In the past I was not able to disable s voice through the application manager, but this time I was.
A couple of possibilities I can think of. In the s voice settings, disable any available options that may be enabled, such as activating it via home button, etc. (Don't recall all the various settings now because it's gone completely from my application settings section)
Also, go into the Security settings of the phone and make sure s voice is not listed as a Device Administrator. I've noticed that apps can't be disabled or uninstalled as long as they're listed in this section as device admins. As usual reboot after just in case, and check if you can disable it then.
I haven't modified anything on the phone other than manually disabling a bunch of apps through application manager and replacing touchwiz with the Google Now home screen.
efishta said:
In the past I was not able to disable s voice through the application manager, but this time I was.
A couple of possibilities I can think of. In the s voice settings, disable any available options that may be enabled, such as activating it via home button, etc. (Don't recall all the various settings now because it's gone completely from my application settings section)
Also, go into the Security settings of the phone and make sure s voice is not listed as a Device Administrator. I've noticed that apps can't be disabled or uninstalled as long as they're listed in this section as device admins. As usual reboot after just in case, and check if you can disable it then.
I haven't modified anything on the phone other than manually disabling a bunch of apps through application manager and replacing touchwiz with the Google Now home screen.
Click to expand...
Click to collapse
it was a device administrator. once removed, i was ale to force stop/disable s-voice
How can I get the stock voice dialer on my phone working again (without giving up privacy)?
There used to be a dedicated voice dialer app. I would tell it to dial numbers, or I could tell it to dail contacts, and it worked, but that app seems to be gone. Can this be fixed with stock android, or does it require a third-party app?
If you're interested, here's how I got to this point, and how to recreate this problem:
A few months ago, the voice dialer functionality on my Nexus 5X changed (maybe because of an upgrade, or maybe I accidentally changed some settings). Now, when I hold the action button on either a wired headset or a bluetooth headset, the phone launches the "Google App" instead of the stock voice dialer app and subsequent voice commands are interpreted as a Google web search. For example, saying "Call Jane Doe on mobile" doesn't actually call anybody, rather the app hears me perfectly but launches a search for the string "Call Jane Doe on mobile" instead of actually calling her. I've found a solution to this awkward web search behavior: enable "OK Google Hotword Detection" within the Google App's settings (bad design, really, because the microphone action button already works to initiates voice commands so it's not necessary for the app to listen for the 'OK Google' hotword to then start listening, but let's put that aside for now). So now it's working a bit better, and when I say "Call Jane Doe on mobile", it actually acknowledges that I have issued some kind of phone dial command. And here's where the big problem is: it refuses to place the call. It gives a message over audio saying that the Google needs permission to my contacts, but I've verified that the app already does have the contacts permission enabled. So what's stopping it? Well it turns out, it's not asking for local access to your contacts, rather it's asking for you to send Google your calendar, apps, music, battery life, and sensor readings -- uhhhh no thanks! I'm not "in" with allowing Google to generically "store and use" sensitive information in exchange for looking up a contact and placing a phone call (this is still a phone, right?). To summarize: although the app already has access to both my contacts and to my microphone, it refuses to dial a contact unless I give Google blanket permission to store and use my sensitive data .
So let's give up on that because that's a deal breaker for me. Let's circumvent the contact lookup and go old-school by directly dialing phone numbers! "Call one-two-three-four-five-six-seven-eight-nine-ten", and... it refuses again. It wants asks for permission to access your contacts again. Everything is the same. Why does it need to access my contact list if I'm telling it the exact number to dial? Something is very wrong with my phones voice dialing. I want the old app back and I never want to use the google app for voice dialing, but I couldn't figure out how to do it, so I was left with one option: factory reset! No, i didn't actually factory reset my phone to bring voice dialing back, but I did add a generic android user profile to my phone, and to my dismay, the new generic android user profile works the same as my real profile does now, and not how it used to work a few months ago. Refuses to voice-dial a phone number unless I give away my privacy. Is anyone else having this problem?
makogaleos said:
How can I get the stock voice dialer on my phone working again (without giving up privacy)?
There used to be a dedicated voice dialer app. I would tell it to dial numbers, or I could tell it to dail contacts, and it worked, but that app seems to be gone. Can this be fixed with stock android, or does it require a third-party app?
If you're interested, here's how I got to this point, and how to recreate this problem:
A few months ago, the voice dialer functionality on my Nexus 5X changed (maybe because of an upgrade, or maybe I accidentally changed some settings). Now, when I hold the action button on either a wired headset or a bluetooth headset, the phone launches the "Google App" instead of the stock voice dialer app and subsequent voice commands are interpreted as a Google web search. For example, saying "Call Jane Doe on mobile" doesn't actually call anybody, rather the app hears me perfectly but launches a search for the string "Call Jane Doe on mobile" instead of actually calling her. I've found a solution to this awkward web search behavior: enable "OK Google Hotword Detection" within the Google App's settings (bad design, really, because the microphone action button already works to initiates voice commands so it's not necessary for the app to listen for the 'OK Google' hotword to then start listening, but let's put that aside for now). So now it's working a bit better, and when I say "Call Jane Doe on mobile", it actually acknowledges that I have issued some kind of phone dial command. And here's where the big problem is: it refuses to place the call. It gives a message over audio saying that the Google needs permission to my contacts, but I've verified that the app already does have the contacts permission enabled. So what's stopping it? Well it turns out, it's not asking for local access to your contacts, rather it's asking for you to send Google your calendar, apps, music, battery life, and sensor readings -- uhhhh no thanks! I'm not "in" with allowing Google to generically "store and use" sensitive information in exchange for looking up a contact and placing a phone call (this is still a phone, right?). To summarize: although the app already has access to both my contacts and to my microphone, it refuses to dial a contact unless I give Google blanket permission to store and use my sensitive data .
So let's give up on that because that's a deal breaker for me. Let's circumvent the contact lookup and go old-school by directly dialing phone numbers! "Call one-two-three-four-five-six-seven-eight-nine-ten", and... it refuses again. It wants asks for permission to access your contacts again. Everything is the same. Why does it need to access my contact list if I'm telling it the exact number to dial? Something is very wrong with my phones voice dialing. I want the old app back and I never want to use the google app for voice dialing, but I couldn't figure out how to do it, so I was left with one option: factory reset! No, i didn't actually factory reset my phone to bring voice dialing back, but I did add a generic android user profile to my phone, and to my dismay, the new generic android user profile works the same as my real profile does now, and not how it used to work a few months ago. Refuses to voice-dial a phone number unless I give away my privacy. Is anyone else having this problem?
Click to expand...
Click to collapse
What app are you giving the contacts permission? You should be giving it to the Google App (aka Voice Search). At minimum, you need to allow that app Contacts, Microphone, and Phone permissions.
Full Android permissions have already been granted to the Google App, and the setting "OK Google hotword detection" is also enabled. But it still asks me for even more intrusive uses of my data, to just dial a phone number. Screenshots attached.
Why would it even need access to contacts to straight up dial a number that I dictate?
@makogaleos have you tried clearing cache and data for that app? Mine doesn't need contact permissions to dial by number.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
@makogaleos have you tried clearing cache and data for that app? Mine doesn't need contact permissions to dial by number.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I cleared cache, and that didn't change anything. Can't clear data because that option seems to be unavailable for the Google app.
Perhaps it's not asking you because you've already given permission?
makogaleos said:
I cleared cache, and that didn't change anything. Can't clear data because that option seems to be unavailable for the Google app.
Perhaps it's not asking you because you've already given permission?
Click to expand...
Click to collapse
I have given it permission before but to try and trouble shoot it I turned the "Information from your devices" thing off and cleared the data Google stored. My contacts are stored on my Google account anyway. Are yours stored locally on your phone?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I have given it permission before but to try and trouble shoot it I turned the "Information from your devices" thing off and cleared the data Google stored. My contacts are stored on my Google account anyway. Are yours stored locally on your phone?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Let's ignore contacts for the moment, and just consider phone numbers. Before, I could say "Dial 1-800-555-5555" and a voice dialer app would execute that command. That isn't happening anymore. It's taking me to the Google app, and it's asking for android permissions and then some really intrusive general permissions. How can I get the original voice dialer app back so that it can just work as normal?
makogaleos said:
Let's ignore contacts for the moment, and just consider phone numbers. Before, I could say "Dial 1-800-555-5555" and a voice dialer app would execute that command. That isn't happening anymore. It's taking me to the Google app, and it's asking for android permissions and then some really intrusive general permissions. How can I get the original voice dialer app back so that it can just work as normal?
Click to expand...
Click to collapse
So it didn't open the Google App before? What app did it open?
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
So it didn't open the Google App before? What app did it open?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It opened this app "Voice Dialer":
makogaleos said:
It opened this app "Voice Dialer":
Click to expand...
Click to collapse
I can't say I've ever seen that app on my 5X or any other phone I've had...
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I can't say I've ever seen that app on my 5X or any other phone I've had...
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I don't think it had a launcher shortcut. But it's what popped up when pressing the action button on a headset.
makogaleos said:
I don't think it had a launcher shortcut. But it's what popped up when pressing the action button on a headset.
Click to expand...
Click to collapse
When you setup your phone did it restore any apps? I just went through all of the system apps with a file explorer and there is no voice dial app.
PiousInquisitor said:
When you setup your phone did it restore any apps? I just went through all of the system apps with a file explorer and there is no voice dial app.
Click to expand...
Click to collapse
I just found several threads online discussing how the stock voice dialer app has been deprecated, and so for the Nexus 5X, the microphone action button takes you to the Google App / Google Now. That means my Nexus 5X probably never had the Voice Dialer app (by the way, the Voice Dialer app does have its own launcher shortcut in some earlier versions of Android).
As I said in my original post, the voice dial functionality within the Google app is disabled unless users agree to Google's use of sensitive data, so that's where I am now: the most advanced phone I can buy won't execute a simple voice dial -- a standard feature in flip phones from 2004.
Why am i not getting Google Assistant on my OnePlus2 LOS 14.1? I have enrolled myself in the Google beta program, cleared cache, changed search and voice language to English(US). But I still didn't get Google Assistant. Any flashable files for that?
having the same issue :/
Its very easy to get google assistant on your phone by following steps:-
1)download velvet zip file from google
2)use buildprop application and add 2 commands at the end ro.product.model=pixel XL and ro.opa.eligible_device=true
3)boot into any custom recovery and install the velvet.zip file
Now you are all good to go!!!!!!!!
Sent from my Redmi Note 3 using XDA Free mobile app
Here's how I got it working on a JDCteam Lineage OS Nougat 14.1 ROM. I can't guarantee it will work, but give it a try, since you don't have to use any mods to get it working.
Note: You might not need to install the Google Now Launcher, so if you want, you can skip that. If The Assistant doesn't work, then try installing the Google Now launcher.
If you have Google Assistant and Google Now Launcher installed. Uninstall them, and reinstall both of them. If you want, clear their cache for good measure.
Now, set the Google Now Launcher as your default launcher, and launch a couple of apps. Then switch back to your preferred launcher. You can set the Google Now Launcher as your default launcher by going into System Settings > Apps > Tap the Gear Icon > under Home App (tap that to change the launcher). If the Google Now Launcher does not appear as a choice, then make sure you have it installed.
Next, open the Google Assistant by clicking its icon in the app drawer. Click the microphone icon in Google Assistants search box. This should prompt you to grant permissions for the microphone.
Next, in the Google Assistant app, tap the hamburger button (top left corner) and make sure your Google account appears. Now, tap Settings and tap the other settings that appears. This should open Google Assistants settings menu.
Exit the setting menu, and test Google Assistant with a voice command to see if it responds. Hopefully it works.
This is what got me working, but it's sometimes a bit buggy. For instance, sometimes after I say OK Google, the Google Assistant screen does not pop up, but it still accepts a voice command. If that happens, try these steps over again. Also, the Say "OK Google" any time setting is greyed out, and I can't get that setting to activate, though Google Assistant works when the screen is active.
This is an easy guide to making all of the normal features of google feed, assistant and stuff work properly on any android 7+ phone (haven't tested below 7) in any country that doesn't allow these features.
this is not for everyone, read this in full before starting so that you know what you are getting into.
so far, there has been no danger to my phone's software doing these stuff.
however im not responsible if you do something wrong. follow the steps properly.
DO NOT DELETE GOOGLE FRAMEWORK DATA ON ANDROID 9. THERE SEEMS TO BE A PROBLEM
1. first of all download a VPN app from the play store, I personally used the CM VPN but use whatever you want. only important thing is that your vpn must have USA connection.
2. update your google app to the latest version, or even go all the way to the latest beta (I prefer the normal because feed looks nicer)
3. turn on the VPN and go to your location settings, and select GPS Only mode.
4. go to your apps in the settings, press "show system apps" and go to the G letter and find Google Services Framework.
delete all of the cache and data for that app. then find the google app. do the same but it happens in a different window, you gotta press manage data and then delete it from inside the google app.
5. open the google app, wait a few seconds and the google feed shows up. weather is missing and most of the features dont work yet, we will get back to them.
6. disconnect and close the vpn. then restart your device.
7. start by activating the assistant. first i suggest that you pause voice activity in google account settings.then activate the voice assistant step by step to the finish.
8. go to the google app, the 3 lines to the right( settings and stuff) go to assistant settings, in the 2nd tab find "phone" and activate voice unlock (this is just to test if the assistant is working properly) if the voice unlock gets activated properly then you're good, if it doesnt, try deactivating voice and audio activity and try again.
you can disable voice unlock after.
9. so now the assistant is activated, google feed is working, you also need to install a launcher that supports google feed page(i am using lawnchair 2 which is in alpha currently, you can use Nova, Rootless Pixel, or CPL or any other that supports it)
10. in order to get google at a glance on screen if your launcher doesn't have it, there is a widget in your widgets screen, from google themselves.
11. in order to activate the weather, go to location settings, select high accuracy, turn on google location history, and then go to the google feed page in your home screen, on the search bar type "weather" and search for it, open the weather page (the google weather app thingy) and close it. refresh the page and its up and running as the top card.
common problem: disappears after a while
do the search bar thing again and it works.
12. the last thing is reminders. type "reminder" in the search bar of the google feed page, make a reminder, then close the whole thing. open assistant, say show me my reminders, it will tell you the reminder you just set up. delete it using voice commands. then make another reminder using voice commands, go to the google app, open the 3 lines page (bottom right) then open reminders. if you have done everything properly, the reminder you set up in search is gone, and the voice reminder is there. if you don't need it, delete the reminder.
Thats all. I'm living in iran so i know all of this works 100%
Good Luck. ill be answering questions if there is any, whenever i check this again.
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.