I have a Nexus7 (flo). I have never been able to get Speech-to-text functional. I think the device came with KitKat, but I've upgraded it all the way through to Marshmallow without getting the damn "Voice Typing" function to work. I'm using the google keyboard, and everything has been stock up until now. A couple weeks ago I flashed to TWRP and CM12, and it still doesn't work. Here's the lowdown-
Google Keyboard is properly set up with my native language.
The microphone icon on the keyboard is shown, but there is no result when it's pressed, long-pressed, or tapped repeatedly in anger.
I've tried several suggestions involving deleting any cache or app data via TitaniumBackup and TWRP.
There is no voice typing option in any of the menus.
I have the following Google-related apps installed:
Google Play Store
Google Keyboard
Google Contacts Sync
And the following Google services:
google backup transport
google account manager
google one time init
google partner setup
google play services
google services framework
Unfortunately I don't know what services or components are required for google voice typing. It didn't work when I had absolutely *everything* from google installed (as it came on this device), so any advice is greatly appreciated!
hello everyone,
got the same problem as artician on my i9100 under CM12. I installed the gapps pico.
Is another gapps version needed? If yes which one?
thanks a lot for anyone's help
Yeah I still haven't heard anything. Not even from Google.
Bricolux said:
hello everyone,
got the same problem as artician on my i9100 under CM12. I installed the gapps pico.
Is another gapps version needed? If yes which one?
thanks a lot for anyone's help
Click to expand...
Click to collapse
By the way, I am also experiencing some loss of wifi connection. I need to switch off, and then back on the wifi of the phone to reconnect to my router.
Do you also have this problem? (I'm running the CM12 20151116 SNAPSHOT version)
cheers
Related
I'm using Flinny's Andromadus CM11.0 [alpha5] and a CM11 GApps package.
The first time I rooted and installed the above, the slider option to switch on Google Now was greyed out (may have been because of the above error message, not sure). I was told that uninstalling all updates to the Google app, enabling Google Now, and re-updating would solve it. And it did.
Now, I've had to re-wipe and reinstall the same ROM and GApps package. Google Now gives me the above error. However, when I uninstall all updates for the Google app, the option to enable Google Now simply disappears.
I should say that Location Reporting is not available in my country (Malta), and those options were never on even at the first rooting and ROM installation.
Any suggestions?
Thanks a lot!
Found a workaround involving disabling Google Play Services, signing out of Search account, signing back in and re-enabling Services.
Thanks anyway
whenever I try to add a calendar event using a voice command in Google Now, it will get to the final confirmation screen and then error out.
This was an issue with 5.0.0, and remains an issue after I updated to 5.0.1 via OTA. Unfortunately I never tried to add calendar events with voice commands back in KitKat, so I don't know if it was a problem in 4.4.
I've tried many times and get the same result each time, regardless of whether I am on WiFi or LTE.
Google Now works fine in every other way. For example, if I use a voice command to start navigating to a specific address, there are no issues with that.
Here's what happens after I say the command. Everything looks fine at this point: http://imgur.com/8wpP5oc
However, as soon as I press the check mark in the bottom right corner, this happens: http://imgur.com/pOJkufp
Any ideas on a fix? Thanks!
Are you blocking/disabling anything regarding Google Play Services/Google Search?
Lethargy said:
Are you blocking/disabling anything regarding Google Play Services/Google Search?
Click to expand...
Click to collapse
Can you elaborate? I just recently upgraded to 5.0.1, so most of my settings are at defaults. I don't think I've gone in and specifically uninstalled/blocked anything related to Google search yet.
996gt2 said:
Can you elaborate? I just recently upgraded to 5.0.1, so most of my settings are at defaults. I don't think I've gone in and specifically uninstalled/blocked anything related to Google search yet.
Click to expand...
Click to collapse
Try clearing the data of Google Search/Google Play Services and maybe try removing and readding your Google Account.
If that doesn't work then make a backup then reflash factory images.
I finally got around to completely re-flashing my phone via fastboot. I am now on a completely clean install of Android 5.0.1. I've even gone back to stock keyboard and launcher in case Nova or Swiftkey was causing an issue.
However, still no luck. Getting the exact same error as before when trying to add a calendar event via Google Now voice command.
Any ideas?
Hello everyone,
so this is 100% my fault and I feel stupid for it happening to me....but oh well. It started when I couldn't get into Google Apps anymore. Play store told me I had no network connection, YouTube couldn't get into my account with the same error, even though I was connected to our Wifi and had internet. So classic Google Services issue, and looking up the problem it seemed I had to uninstall Google Play Services and then reinstall them and the problem should be fixed.
Now here is where I went derp and uninstalled the Google Services without looking at it before to know what version I had to install. Okay, no problem, this should be easy to find out. I'm on Android 6 with the recent update we got, CPU is armv7 architecture and the phone is in 480dpi. A quick look at the backup I had from Android 5.1.1 confirmed this, where the last number in the parenthesis was 238. So I downloaded the most recent Google Play services version, 9.0.83, with the 438 number for Android 6, installed it and it keeps crashing. Now I already tried multiple ones, I tried the one for nodpi, I tried the 238 but it all keeps crashing, constantly spamming the "Google Play Services has stopped working" error.
So here I am, at wits end and asking you guys for help. Did I go wrong somewhere along this? What version for the Google Play Services have you guys installed? I completely removed the app each time before installing the new one, removing all leftover data, clearing cache and the dalvik cache but to no avail. Keeps crashing.
1. Backup data trough usb if possible
2. Clean wipe, reinstall rom + gapps = profit
hosseltietjes1990 said:
1. Backup data trough usb if possible
2. Clean wipe, reinstall rom + gapps = profit
Click to expand...
Click to collapse
Seems I'll have to do that, yeah. I had hoped I could do it without wiping....but ****
9.0.83 has problem on my OPO. I rolled back to april version and now it is ok.
Hi there,
for some months now I have a Honor View 10 with LineageOS 15.1 installed.
Recently I also got a Huawei smart watch which I coupled to the View 10.
On both devices, it was working perfectly fine to talk to the Google Assistant by just saying "OK Google" if the screen was turned on.
It automatically unlocked and followed my commands.
Since some weeks, though, the "OK Google" detection stopped working and I cannot find out, why.
When trying to activate Voice Match in the settings page of the Google app, there's a message that the service was not available in my current language...
(But I already tried many different languages - of course including "English (US)". And: it used to work until some weeks ago!)
I already changed many settings, tried several combinations of different settings unpaired my smart watch, deleted the cache and all updates of the Google apps, but I was not able to get OK Google back running...
I am not sure if this is a device-specific issue or a LineageOS-specific issue, but on my device with LineageOS it does not work anymore...
(Btw, when tapping the microphone icon in Google's search bar, the voice recognition is working fine!)
Any ideas?
Anyone having the same problem?
Anyone already fixed that?
Best,
Tom
I have the same problem with my stock phone.Ok google/Hey google not working.
BoxyK said:
Since some weeks, though, the "OK Google" detection stopped working and I cannot find out, why.
Click to expand...
Click to collapse
Try this:
https://forum.xda-developers.com/showpost.php?p=76652234&postcount=3
Unfortunately, this did not work.
Still all options for voice match are greyed out...
BoxyK said:
Unfortunately, this did not work.
Still all options for voice match are greyed out...
Click to expand...
Click to collapse
Try to delete google app data after you pushed those files. Here it works as expected.
I don't get that.
The Google app is part of the gapps. It's installed in the /system partition.
After deleting it, how should I re-install it?
From the Play Store (is it available there?)?
Or in the /system partition again (how?)
BoxyK said:
I don't get that.
The Google app is part of the gapps. It's installed in the /system partition.
After deleting it, how should I re-install it?
From the Play Store (is it available there?)?
Or in the /system partition again (how?)
Click to expand...
Click to collapse
Not the app eheh, only its data from Settings - Apps and notifications - Show all apps - Google - Storage space - Manage space - Delete all data.
I've done that several times already.
Now again, with the two apps installed in /system.
I deleted all the data of the Google app.
I've even tried to delete all data from Play services which meant re-configuring all the accounts and settings and so on again from scratch, but that didn't help, either.
This is really weird.
Check also if it's not a gapps issue, try this within Lineage: https://www.androidfilehost.com/?fid=674106145207491329
Otherwise i'm out of ideas, you could try my build (https://androidfilehost.com/?fid=962339331458996492) and see if you can enroll Ok Google again. Then, if it works, you could even try to flash Lineage again and see if it still works (you know, Google server side voodoo lol).
Completely stock here and having the same issue. I am starting to regret getting this phone.
I've tried now to
- re-install Lineageos 15.1
- install another build of Lineageos 15.1
- using different versions of GApps
but nothing brought my voice match back...
Now I'm a little bit frustrated
I am on EMUI12 (C432) and want to know whether or not it is safe to update google play services.
I installed it over a year ago using a method I cannot remember where I found, and currently have GSF frozen with icebox and the phone has been working perfectly (inc notifications) ever since. I just use Aurora to install/update apps (a bit of a pain having to do it manually but liveable).
Since going to EMUI/Android11 I am having some issues with Samsung Galaxy Wareable app being flakey with syncing with my Galaxy Watch, and also having recently got a car with Android Auto Wireless, I am having some issues with it too. On the latest version of Android Auto. Sometimes wireless works and sometimes it doesn't (the car has bluetooth connection which prompts phone to connect to the AA SSID but sometimes it just joins the bluetooth and then drops..
Anyway...
Currently on GPS version 20.47.13
Wondering if it is possible to update to a later version of play services without breaking notifications without first downgrading to EMUI10 -> EMUI11?
Thanks!
maximum 21.24.56.
It is possible to ruin all when you de-freeze GSF (play protect errors, auto-upgrade of Play Services, etc).
Thanks for your quick reply.
Can I go ahead and update the APK to 21.24.56 without defrosting GSF?
You can try. I dont remeber if it will counts if the GFS is frozen. In my method I have to have GFS not frozen. You are on other method.
Okay that didn't work
Downloaded it from apkmirror. It installed OK but now all google apps won't open.
Tried to reinstall old version, same thing.
Looks like I am going to have to downgrade (which I assume means wiping) and then follow your method.
mcall_r said:
Okay that didn't work
Downloaded it from apkmirror. It installed OK but now all google apps won't open.
Tried to reinstall old version, same thing.
Looks like I am going to have to downgrade (which I assume means wiping) and then follow your method.
Click to expand...
Click to collapse
Don't downgrade. We will talk after 2 hours