I noticed that google voice match and assistant just stopped working randomly. I was "ok googling" to basically an unresponsive phone.
Now I realize, that voice assistant deletes my voice match information nearly every day now. I have to retrain it, and then it only lasts another day.
Also, I am noticing some connection issues that I have never experienced before, since the latest update. (8.0.0 poop sandwich or whatever they are calling it)
Anyone else have these problems?
Thanks.
PM
I have almost the same issue regarding "OK google".
My trained voice doesn't get deleted, but "OK google" turns itself always off after 1-3 days. It's really frustrating, if you want to speak to your phone while driving and suddenly it's not working anymore.
After turning it on again, everything is fine for a short time.
papamalo said:
I noticed that google voice match and assistant just stopped working randomly. I was "ok googling" to basically an unresponsive phone.
Now I realize, that voice assistant deletes my voice match information nearly every day now. I have to retrain it, and then it only lasts another day.
Also, I am noticing some connection issues that I have never experienced before, since the latest update. (8.0.0 poop sandwich or whatever they are calling it)
Anyone else have these problems?
Thanks.
PM
Click to expand...
Click to collapse
I use Google Assistant almost every day while driving to call my wife.
What variant do you have? Are you on a custom ROM?
I'm on rooted stock firmware myself, but my wife's phone is not rooted. She uses Google Assistant most every day also and has no problems. We are both on US998 Oreo.
THanks Cazzmatt!
I am on an unrooted LG V30, LG-H932 variant, hardware rev 1.0 running Android 8.8.0, running google 8.10.22.21.arm64
Basti: Different problem. If it suddenly works after a few days, it is likely that your problem is with a connection to the server, where the commands are processed, which would be a WiFi or cellular data connection problem.
For all I know my problem may originate form the same issue.
Thanks.
PM
Related
Up until like a week ago everything was running mostly OK. Once in a while it would say it was connecting but would actually go through to voice mail. All of a sudden (before flashing Eugene's V7 ROM, so that's not the issue) it says it is connecting but does not. All the settings are correct and where they always have been, but no matter what I do it just will not work. Anyone have any insights or solutions? I am still using a pre "Even More" plan with My Faves so it's really beneficial to have this all work. Thanks to all...
Just bought my SGS2 yesterday and flashed it to KI8 and rooted it with CF-Root. Didn't actually test it before flashing but for some reason Google Talk keeps losing connection and signs in very often. Has this got something to do with the modem version losing data connection or is it happening because of some power-save setting?
Today I flashed KI4 and Google Talk has dropped offline a couple of times already. Is my device flawed?
Any suggestions on different modem versions and/or firmwares to try out? Maybe a separate GTalk client?
Has anyone had issues like this? I tried to search the forum but most topics cover connection problems via WiFi and not mobile data.
That happens to me when I don't have a strong connection. I say it's probably a carrier issue.
Then it must be a local issue. My friend has the same phone and same operator, but lives about 150km away from me and his GTalk stays connected.
Is there a way to monitor and/or log the data connection with some software?
I have also run into this problem since rooting. I can't even find google talk on my phone to disable it.
mratlndmrk said:
I have also run into this problem since rooting. I can't even find google talk on my phone to disable it.
Click to expand...
Click to collapse
For me it didn't matter if the phone was rooted or not. Wierdest thing is that even if my buddies see me offline, I receive messages immediately when they send one.
Quick update: I found out a way to make signal bars turn green when connected to Google services. Now I can sometimes see that the bars are gray when turning the screen on. So it's clear that my phone disconnects from Google in longer standby.
First, I have searched both here and Google regarding my question but all I’ve turned up are problems with WiFi connections (which I don’t have – my connection is always solid) and reported problems about 8 months ago with payments in general (my problems are with WiFi only).
My problem is that any time I try to purchase an app on Android Market (and now Google Play) using WiFi, the app hangs at the point where it’s trying to authorize payment. It just sits there no matter how long I wait (well… at least 10 minutes or so). If I switch over to the home screen, turn off WiFi so 4G comes back up and then switch back to Android Market/Google Play, payment goes through properly. Once the download starts I can switch back to WiFi and the app will download without issue. This happened several times when I was straight stock using Android Market, at least once when I switched to NRG’s ROM using Android market, and again this morning with Google Play; it isn’t just the new Google Play app.
I wanted to ask whether anyone else has experienced this and whether you found any reason for it or a solution to it. This isn’t the end of the world but it would be nice to have it working correctly so I don’t have to mess around with the connection while trying to download a large app.
Thanks!
gregb882 said:
First, I have searched both here and Google regarding my question but all I’ve turned up are problems with WiFi connections (which I don’t have – my connection is always solid) and reported problems about 8 months ago with payments in general (my problems are with WiFi only).
My problem is that any time I try to purchase an app on Android Market (and now Google Play) using WiFi, the app hangs at the point where it’s trying to authorize payment. It just sits there no matter how long I wait (well… at least 10 minutes or so). If I switch over to the home screen, turn off WiFi so 4G comes back up and then switch back to Android Market/Google Play, payment goes through properly. Once the download starts I can switch back to WiFi and the app will download without issue. This happened several times when I was straight stock using Android Market, at least once when I switched to NRG’s ROM using Android market, and again this morning with Google Play; it isn’t just the new Google Play app.
I wanted to ask whether anyone else has experienced this and whether you found any reason for it or a solution to it. This isn’t the end of the world but it would be nice to have it working correctly so I don’t have to mess around with the connection while trying to download a large app.
Thanks!
Click to expand...
Click to collapse
I was having issues last night buying app from google play, was getting error 403. then this morning I bought another and it went through and I was like wtf!
I refunded the three apps that didn't go through then re bought them and they downloaded perfectly.. lol
not sure if that is the issue you're having but take a look at this thread:http://www.google.com/support/forum...ad?fid=4627bf187632930e0004babe8be00aa0&hl=en
stratax said:
I was having issues last night buying app from google play, was getting error 403. then this morning I bought another and it went through and I was like wtf!
I refunded the three apps that didn't go through then re bought them and they downloaded perfectly.. lol
not sure if that is the issue you're having but take a look at this thread:http://www.google.com/support/forum...ad?fid=4627bf187632930e0004babe8be00aa0&hl=en
Click to expand...
Click to collapse
Thanks for the link, but unfortunately my issue is different. I never got an error of any kind, it just sat there trying to authorize payment until I switched from WiFi back to 4G, then it went through without issue. Afterword, I could download the app on WiFi just fine.
Thanks again.
My payments for apps only work over 4g
well I can confirm it isn't using wifi, it COULD be your router or firewall, or some other settings. I can confirm it because I don't have a data plan, I use wifi for everything and I have bought apps through it.
F033x said:
My payments for apps only work over 4g
Click to expand...
Click to collapse
Hummm, guess that's just the way it works. Thanks for the feedback.
I've been troubleshooting voice recognition issues for a while now dating back to the GS3 before I got the GN2. So this will not be phone specific.
This applies to an unrooted and locked GN2. In other words, full stock. I am running Go Launcher but that should not matter.
Statement of Problem ("Problem"): Google Now voice search, and Google voice recognition from keyboard microphone buttons, will often not connect to Google over 3G/4G with valid data connection, with the screen showing "Initializing" (when on Google Now) for 20 seconds and then "Can't connect to Google" message, or a frozen/suspended microphone icon when attempting voice recognition via keyboard. Note: The Problem does NOT happen when on WiFi.
Analysis: Google Now and Google voice recognition services work fine on wifi. When driving, signal shows 3G or 4G with 2 or more signal bars, however, Problem symptoms appear.I confirm 3G/4G data because web browsers work and Google Play store works.
During troubleshooting, I learned that Google Now and Google voice recognition services require an active internect connection - however I have confirmed I do have an active internet connection via 3G/4G because Google Play works. The stock voice recognition via stock keyboard does NOT require active internet connection. I have confirmed that the mic button on the stock keyboard always works over 3G/4G. I have confirmed the mic on Swift Key keyboard, when Google voice services is selected as input mode, does not work on 3G/4G but does on wifi. But this cant be a Swift Key issue because whenever the mic does not work, Google Now voice recognition does not work.
What I have ruled out: It always works on wifi. Almost always does not work on 3G/4G despite confirmed signal. I turned OFF wifi just in case the code has a bug thinking there should be a wifi signal which is not present. I tried turning OFF Google Now and still have same problems with Google search and Google voice recignition.
What I think i found: I uninstalled the Play Store Update for Google Search to return Google Search to stock version of Google Search App. As soon as I do that, Google Now and Google voice recognition services work again over 3G/4G.
Is anyone else experiencing this problem? If so, can you try and uninstall the Google Search update and go back to the Google Search stock app to see if it works? You can always reinstall the update to compare.
I am out of ideas. I want my Google Now and Google voice recog over 3G/4G in addition to wifi.
Adam
P.S. One last note..... I searched high and low on the internet and cannot find folks with this problem. So that tells me maybe it is a setting on my phone? But I am good at this... I cant figure it out. If my un-installationof the Google Search Update fixes this... I may have found an unreported bug! I am testing this solution now over next 48 hours.
I had the same problem couple times when not on wifi at home. Not big deal for me but will keep it in mind in case it go worst. Thanks
Sent from my SCH-I605 using Tapatalk 2
voice
I notice the problem after I got the Samsung Galaxy Note 2 from Verizon, and updated Google search. The Voice to text stopped working. That first update I believe was on December fifth 2012, and then the update of Google search today, December 13th 2012.
First update: 12/5/2012,
Second update: 12/13/2012.5pm EST
App update of Google Search
The app update downloaded just fine, no issues with the updated download at all.
No error messages at all.
When I install the update, the microphone on voice to text just times out. I can go to Google Now and when I hit the mic there it will time out a few times, but eventually it will light up and work that 1 time. Then have to hit it a few more times to get it again. But with text messaging, won't work at all. If I have already clicked on the mic button, and I get a notification of a new email, which goes to my bluetooth, it will light up and work that one time. Also just noticed that after the update, if I go to settings: bluetooth, and un click media audio, the update mic will then work. I have tried a few different bluetooth earpieces, blueant Q2, jawbone era, Motorola elite flip, and Motorola Silver, all with the same outcome.After update of Google Search, voice mic will not work unless media audio is un-checked, but then I lose navigation and all other messages to the bluetooth.
AdamHLG said:
I've been troubleshooting voice recognition issues for a while now dating back to the GS3 before I got the GN2. So this will not be phone specific.
This applies to an unrooted and locked GN2. In other words, full stock. I am running Go Launcher but that should not matter.
Statement of Problem ("Problem"): Google Now voice search, and Google voice recognition from keyboard microphone buttons, will often not connect to Google over 3G/4G with valid data connection, with the screen showing "Initializing" (when on Google Now) for 20 seconds and then "Can't connect to Google" message, or a frozen/suspended microphone icon when attempting voice recognition via keyboard. Note: The Problem does NOT happen when on WiFi.
Analysis: Google Now and Google voice recognition services work fine on wifi. When driving, signal shows 3G or 4G with 2 or more signal bars, however, Problem symptoms appear.I confirm 3G/4G data because web browsers work and Google Play store works.
During troubleshooting, I learned that Google Now and Google voice recognition services require an active internect connection - however I have confirmed I do have an active internet connection via 3G/4G because Google Play works. The stock voice recognition via stock keyboard does NOT require active internet connection. I have confirmed that the mic button on the stock keyboard always works over 3G/4G. I have confirmed the mic on Swift Key keyboard, when Google voice services is selected as input mode, does not work on 3G/4G but does on wifi. But this cant be a Swift Key issue because whenever the mic does not work, Google Now voice recognition does not work.
What I have ruled out: It always works on wifi. Almost always does not work on 3G/4G despite confirmed signal. I turned OFF wifi just in case the code has a bug thinking there should be a wifi signal which is not present. I tried turning OFF Google Now and still have same problems with Google search and Google voice recignition.
What I think i found: I uninstalled the Play Store Update for Google Search to return Google Search to stock version of Google Search App. As soon as I do that, Google Now and Google voice recognition services work again over 3G/4G.
Is anyone else experiencing this problem? If so, can you try and uninstall the Google Search update and go back to the Google Search stock app to see if it works? You can always reinstall the update to compare.
I am out of ideas. I want my Google Now and Google voice recog over 3G/4G in addition to wifi.
Adam
P.S. One last note..... I searched high and low on the internet and cannot find folks with this problem. So that tells me maybe it is a setting on my phone? But I am good at this... I cant figure it out. If my un-installationof the Google Search Update fixes this... I may have found an unreported bug! I am testing this solution now over next 48 hours.
Click to expand...
Click to collapse
AdamHLG said:
What I think i found: I uninstalled the Play Store Update for Google Search to return Google Search to stock version of Google Search App. As soon as I do that, Google Now and Google voice recognition services work again over 3G/4G.
Click to expand...
Click to collapse
This solved another problem that was driving me nuts. Over Wi-Fi or 3/4G unlocking via personalized voice commands in S Voice (other than "Hi Galaxy") weren't working at least 75% of the time in totally quiet rooms. Uninstalling the Search update reversed the percenteges. Also getting S Voice to properly record the personalized voice commands was a hit or miss mess. That's not an issue now either. Google's got some work to do.
So far after 24 hours the Problem I identified in the first post is solved provided the Google Search update is NOT installed.
AdamHLG said:
I've been troubleshooting voice recognition issues for a while now dating back to the GS3 before I got the GN2. So this will not be phone specific.
This applies to an unrooted and locked GN2. In other words, full stock. I am running Go Launcher but that should not matter.
.
Click to expand...
Click to collapse
This might not even be device specific. I believe this is the same issue I observed on my wife's Galaxy Nexus this weekend. She just got the phone a couple of weeks before me, but doesn't really explore all the features. I was trying to demonstrate how cool Google Now and Voice was.....needless to say, the performance issues as you've noted here pretty much soured her to the idea of even bothering to use Voice search and google now.
I'll see if she has the update and try uninstalling it.
I haven't had any issues with it on my Note 2 however.
Confirmed on my phone that this happens. But I also found out that if I click the mic before waiting for everything to load in Google Now, the issue doesn't occur. Very odd...
Sent from my SCH-I605 using XDA Premium HD app
I can confirm that the after one week of testing, the Problem disappears if the Google Search update is removed. Once I add the update back, the Problem begins again.
There is very little on the internet about this from my searching. It seems others on this thread can confirm the issue. Do you other guys not notice this happening or do you not use Google Now while on 3G/4G and no WIFI. If it's working for you (the majority of the time), do you have the Google Search update installed or is your phone factory stock and you never updated Google Search from the Play Store?
By the way I am not rooted or unlocked.
How do I tell Google about this? I mean someplace real where they'll respond if they know about it or log it for an app update? (yeah right).
Im root but I have not experience any problem. You can post your finding here http://code.google.com/p/android/issues/list
Sent from my SCH-I605 using Tapatalk 2
Uninstalling Google Search did not solve the problem for me!
AdamHLG said:
I can confirm that the after one week of testing, the Problem disappears if the Google Search update is removed. Once I add the update back, the Problem begins again.
There is very little on the internet about this from my searching. It seems others on this thread can confirm the issue. Do you other guys not notice this happening or do you not use Google Now while on 3G/4G and no WIFI. If it's working for you (the majority of the time), do you have the Google Search update installed or is your phone factory stock and you never updated Google Search from the Play Store?
By the way I am not rooted or unlocked.
How do I tell Google about this? I mean someplace real where they'll respond if they know about it or log it for an app update? (yeah right).
Click to expand...
Click to collapse
I have been searching the net to solve this problem and came across your post. This solution did not work on my Note 2. Very frustrating as the ability to speak a text is very convenient and necessary for me. I press the button and can not get the red to appear. When on WiFi it works. Please help with this because not a lot of folks are having the issue as nothing online....this may be the only thing. REALLY NEED THIS FEATURE! HELP!!!!!
Thanks! I'll post the issue to Google using that link.
Sent from my SCH-I605 using Tapatalk 2
Confirming.
Worked when I first loaded a custom rom...then after a week or so, Google search would just initialize. Based on this thread, I went into application manager and saw "Uninstall Update" which I did....now I'm gold again...
THANKS
Hi, my sister's unrooted HTC One on stock 4.4.3 has a phone call issue. She'll call someone but they can't hear her and she can't here them. If this happens, she does a reboot and when she makes a phone call it'll connect. After a certain amount of time the phone call issue will appear again.
Has anyone else experienced this? This also happens on my GF's rooted HTC One running Viper rom.
dragonsamus said:
Hi, my sister's unrooted HTC One on stock 4.4.3 has a phone call issue. She'll call someone but they can't hear her and she can't here them. If this happens, she does a reboot and when she makes a phone call it'll connect. After a certain amount of time the phone call issue will appear again.
Has anyone else experienced this? This also happens on my GF's rooted HTC One running Viper rom.
Click to expand...
Click to collapse
Have your sister copy all of her personal data and files off of the phone and perform a factory reset through Settings. If that doesn't work, then have her download and the run the T-Mobile RUU assuming she is on T-Mobile. Again make sure all of her personal files and data has been removed from the phone.
majmoz said:
Have your sister copy all of her personal data and files off of the phone and perform a factory reset through Settings. If that doesn't work, then have her download and the run the T-Mobile RUU assuming she is on T-Mobile. Again make sure all of her personal files and data has been removed from the phone.
Click to expand...
Click to collapse
Thank you! She is on t-mobile. I will help her with this and report back.
This literally just started happening to me as well. T-Mobile HTC One on ViperROM 7.0.0.
I made a phone call Sunday (12/7) no problem. Now all of a sudden no audio in either direction using the default phone app. But hangouts dialer has no issues.
This just started happening to me as well! When I'm on wifi calling, I'm able to make a phone call without any issues. But 2 times this week when I tried to make a call when I wasn't on wifi, it was a dead call where I couldn't hear the caller and she couldn't hear me.
I have an unrooted t-mobile HTC One.
Any one have any ideas as to what could be the cause of the issue?
EDIT: It appears to be caused by the HTC lock screen on the google play store which was recently updated. Hopefully a fix will be released soon.
jpzsports said:
This just started happening to me as well! When I'm on wifi calling, I'm able to make a phone call without any issues. But 2 times this week when I tried to make a call when I wasn't on wifi, it was a dead call where I couldn't hear the caller and she couldn't hear me.
I have an unrooted t-mobile HTC One.
Any one have any ideas as to what could be the cause of the issue?
EDIT: It appears to be caused by the HTC lock screen on the google play store which was recently updated. Hopefully a fix will be released soon.
Click to expand...
Click to collapse
Where did you hear about this? I'm having the exact same issue. I'm on Viper 7.0.1. Restarting the phone doesn't work but a flashing the rom fixes it again for a little bit. Trying to find the cause of the issue so I can correct it without having to wipe my device again.
Well I ran the new RUU to return my phone to bone stock. Calls work after this no problem. So i started re-installing all my apps via titanium backup and today I get a phone call, same thing no audio either direction. This is on the stock ROM, i never re-installed Viper.
I'm going to do a TWRP back up and do a factory reset and not install any apps to see if the problem comes back.
---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------
jpzsports said:
EDIT: It appears to be caused by the HTC lock screen on the google play store which was recently updated. Hopefully a fix will be released soon.
Click to expand...
Click to collapse
Just noticed the edit. Can you let us know the source of this info please?
More info here: http://forum.xda-developers.com/htc-one/help/m7-mute-calls-please-help-t2921985/page8
HTC is taking responsibility for it, but I don't think it's clear if it's HTC or Google's fault. Either way, HTC pushed an ota for an Australian carrier that fixes the issue, and the venom guys released a flashable fix a little earlier today for their ROM. As far as stock tmobile users, I have no idea nor have heard of a permanent or even a solid temporary fix that normal users could do, i.e. my wife.
Google hangouts dialer does work. I used it today to call people back once they called me and we couldn't hear each other There are other calling apps, but this one is nice cuz you don't have to sign up for anything, it's just Google which we all obviously use already.
Sent from my HTC One using Tapatalk 2
Just got an update from T-mobile to fix this. OTA