Hi all,
I've recently installed a Sony XAV-5000 in my car and having issues with it responding with voice commands (hey google, ok google etc).
I can press a button and it beeps and away I go with my command but using a command to consistently 'wake' the assistant is a no go.
I have updated to latest firmware, cleared cache, cleared data and it works the first time but then doesn't respond.
The interesting thing is, when I do say 'Hey Google' after clearing data/cache the screen does a slight refresh so it seems to be hearing me but not opening the assistant, it does this every time.
Any idea what's going on? It feels like a permission or something else is blocking it from opening but I've been through everything multiple times.
Google Assistant works flawlessly just on my phone.
Any help would be greatly appreciated!
Cheers Jack
Jack2022 said:
Hi all,
I've recently installed a Sony XAV-5000 in my car and having issues with it responding with voice commands (hey google, ok google etc).
I can press a button and it beeps and away I go with my command but using a command to consistently 'wake' the assistant is a no go.
I have updated to latest firmware, cleared cache, cleared data and it works the first time but then doesn't respond.
The interesting thing is, when I do say 'Hey Google' after clearing data/cache the screen does a slight refresh so it seems to be hearing me but not opening the assistant, it does this every time.
Any idea what's going on? It feels like a permission or something else is blocking it from opening but I've been through everything multiple times.
Google Assistant works flawlessly just on my phone.
Any help would be greatly appreciated!
Cheers Jack
Click to expand...
Click to collapse
I am having the same issue mate. It has been like that since the last firmware update on my Samsung Galaxy S20 ULTRA 5G. Have you figured anything out yet
PSYCHO-TERMINATR said:
I am having the same issue mate. It has been like that since the last firmware update on my Samsung Galaxy S20 ULTRA 5G. Have you figured anything out yet
Click to expand...
Click to collapse
It's a known issue and Google are aware of the problem and working on a solution
Jack2022 said:
It's a known issue and Google are aware of the problem and working on a solution
Click to expand...
Click to collapse
Thanks Jack. I know you shouldn't have too but for the time being uninstall the google updates and turn off auto update. It works a dream.
PSYCHO-TERMINATR said:
Thanks Jack. I know you shouldn't have too but for the time being uninstall the google updates and turn off auto update. It works a dream.
Click to expand...
Click to collapse
Thanks man, this is a link to the thread
Hey Google causing issues / not responding - Android Auto Community
Looks like the last working version is 13.38.11.29
Hopefully we don't lose too many features downgrading so far back.
Related
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Having that same issue. Not only does not "Ok Google" work, even after enabling it in the watch's settings, even when pressing down the crown, the whole thing is extremely slow. Furthermore, for sending a message, the "Ok" doesn't time out after a couple of seconds in order to send the message automatically. It requires me to tap the screen.
All in all, its looking more like a downgrade for me. The whole system feels sluggish and incoherent from a usability standpoint of view.
Edit: Didn't factory reset the watch after update
I have an another problem. Google Assistant isn't launched in Czechia yet and there isn't Google Now in Android Wear 2. So, I lost any speech control.
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Mr.Caution said:
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Click to expand...
Click to collapse
So another issue is that even after going to the stupid settings where you actually have to enable Ok Google from any screen on your watch, it STILL wont work. I can only get it to work by using the power button which has a huge delay and then only when I am connected on Wifi. For some reason it no longer works when on my normal cellphone connection.
The phone is super laggy, battery dies fast...its a MESS.
Basically my watch is useless now for all the things I need it to do daily
Mine only works if i go and disable Bluetooth and enable WiFi else it complains it can't contact Google. Play store is the same too. Slow lagging assistant is not good especially sending txts with no auto send
Sent from my Moto G (4) using Tapatalk
Same issue here. "OK Google" is the most important feature...
You need to give permissions for the OK Google to work. Didn't notice about it until I read this thread (I think most particularly Phone access)
shaolin95 said:
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Click to expand...
Click to collapse
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
venzislav said:
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
Click to expand...
Click to collapse
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
shaolin95 said:
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
Click to expand...
Click to collapse
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
venzislav said:
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
Click to expand...
Click to collapse
I want to find out as its annoying to see the upgrade message over and over
shaolin95 said:
I want to find out as its annoying to see the upgrade message over and over
Click to expand...
Click to collapse
Pfff this 2.0 is a big s**t !!!
Doesn't lag on mine using the 2 core or 4 core kernel
almostthere said:
Doesn't lag on mine using the 2 core or 4 core kernel
Click to expand...
Click to collapse
Does OK Google work with voice commands and when not connected to Wifi???
shaolin95 said:
Does OK Google work with voice commands and when not connected to Wifi???
Click to expand...
Click to collapse
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
almostthere said:
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
Click to expand...
Click to collapse
Would you look at that! It works but WTH is google making it so complicated now for users? Most people dont hang around XDA to know these things. Like for instance apps now need to be downloaded on the phone as its not autmotically done, etc.
Really weird approach.
Thanks for the tip!
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Isham.padron said:
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Click to expand...
Click to collapse
Responses time is horrible on the initial due to it running on single core at lower clock speeds and on conservative core governor.
Therefore you'll have to give it sometime for it to settle down or if you can't deal with it, you'll have to unlock the bootloader and flash in the dual or quad core enabled kernel file
Running in quad core kernel, battery life seems decent and response real snappy
Well that's just stupid because it worked fine on the previous android wear build. This is dumb on LG's part.
I have tried everything to get 'Voice Wakeup' for Bixby working without success. Cleared Cache, Data and uninstalled and re-installed updates all to no avail. Also Registering my voice is a nightmare. Constantly had to repeat 'Hi Bixby' an excessive number of times before it registered. I am beginning to think that my S8 has a microphone issue. Noticed that on occasion 'Ok Google' doesn't work and I have to re-boot the phone to get it working. Re-booting does nothing for Bixby, however. Anyone here have any ideas, suggestions or opinions on what's going on?
toggling Bixby voice wake-up & voice unlock settings fixed it for me after updates
joekiv said:
I have tried everything to get 'Voice Wakeup' for Bixby working without success. Cleared Cache, Data and uninstalled and re-installed updates all to no avail. Also Registering my voice is a nightmare. Constantly had to repeat 'Hi Bixby' an excessive number of times before it registered. I am beginning to think that my S8 has a microphone issue. Noticed that on occasion 'Ok Google' doesn't work and I have to re-boot the phone to get it working. Re-booting does nothing for Bixby, however. Anyone here have any ideas, suggestions or opinions on what's going on?
Click to expand...
Click to collapse
Toggling Bixby voice wake-up & voice unlock settings off/on fixed it for me after Samsung updates temporarily made it stop working. Also, increasing sensitivity of voice wake-up and using earbuds w/in-line mic might help as well.
joekiv said:
I have tried everything to get 'Voice Wakeup' for Bixby working without success. Cleared Cache, Data and uninstalled and re-installed updates all to no avail. Also Registering my voice is a nightmare. Constantly had to repeat 'Hi Bixby' an excessive number of times before it registered. I am beginning to think that my S8 has a microphone issue. Noticed that on occasion 'Ok Google' doesn't work and I have to re-boot the phone to get it working. Re-booting does nothing for Bixby, however. Anyone here have any ideas, suggestions or opinions on what's going on?
Click to expand...
Click to collapse
If you can dictate to your keyboard (speech input) without issues, then there is nothing wrong with your mic.
jhofseth said:
Toggling Bixby voice wake-up & voice unlock settings off/on fixed it for me after Samsung updates temporarily made it stop working. Also, increasing sensitivity of voice wake-up and using earbuds w/in-line mic might help as well.
Click to expand...
Click to collapse
Sorry for long delay in responding back. Samsung told me that a new update would fix the problem., I waited on it. Got the update last week. It did nothing. Tried your suggestion - didn't work.
Dr. Fed said:
If you can dictate to your keyboard (speech input) without issues, then there is nothing wrong with your mic.
Click to expand...
Click to collapse
Tried your suggestion and I can dictate to keyboard.
There are some other post about this but it only works after setting up the alarm for the first time after that.... nothing. Thats my experience anyway.
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
fredphoesh said:
I've just upgraded from Pixel XL to Note8 and mostly I am very pleased, but for the very disappointing lack of proper implementation of Google Now/Assistant.
When the screen is off, I say OK Google, and the screen comes on ready for my command. Then I ask something and I get "Can't reach Google at the moment." This is absolute nonsense. I am sitting at my desk, 1m from my fibre optic router and I get 60mb download speeds. I am also connected to 4g from my desk, and if I run any app using the net, it works fine. I always get my emails, WhatsApp, Duo, Allo etc... so no problem there.
Other variations, things that sometimes happen:
1/ "OK Google" with screen off - the phone makes it's listening sound, but the screen stays off, then a minute later when I switch the screen on manually, I get the answer to my question!
2/ "OK Google" with screen off - the phone makes two sounds, the listening one then the cancelling one almost simultaneously
3/ "OK Google" with screen of - no response at all.
Anyone know what is going on here?
Thanks,
Mark.
Click to expand...
Click to collapse
they broke ok google about a year ago, very sad.
SOLUTION!
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
fredphoesh said:
Hello again all.
After much searching, I tired something suggested back in 2015 by someone... an obvious suggestion, but not something EE tech support or Samsung had suggested.
Go to Settings>Apps>Google
Then go to Storage
Clear Cache
Clear Data
Reboot.
The suggestion was to try force close Google app, but that would not work, I tried a few times, but then just cleared Cache and Data, rebooted and it works perfectly, just like my Pixel XL
Woo hoo!!
Mark.
Click to expand...
Click to collapse
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
I had this problem, disabled Bixby, works properly now.
Sent from my SM-N950U using Tapatalk
Liface said:
This doesn't work for me. Even after clearing cache and data, rebooting, starting Assistant and running through the setup again, I get the same behavior with the screen off, a message that says "Can't reach Google at the moment."
Click to expand...
Click to collapse
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Mine get borked every time I toggle between power saving modes. I like to use Extreme power saver for overnight and Medium mode at work.
Medium mode straight up breaks OK Google. Not sure if this is by design or a bug, but it just will not hear me.
Coming out of either mode (and extreme is the worst) and neither "Hi Bixby" or "OK Google" work until I do another full reboot. Sometimes I have to reboot then go back into Google voice setting to switch the option back on manually. If I try to do this before the reboot the option is greyed out and I can't move it. Sometimes just the reboot is enough.
It's random as hell and extremely annoying. I have submitted the bug to Samsung via the feature in the Samsung Members app, but that was over two weeks ago and has seen no response.
Interesting post. My wife's OK Google voice doesn't work but mine does. Both USA T MO version. With works I'm referring to having the Google widget on home screen and saying the sentence OK Google. Mine responds and hers doesn't. With screen ON.
Sent from my SM-N950U using Tapatalk
fredphoesh said:
Check that your battery saving modes are not killing the Google app from running in the background. This is the most likely scenario, that the app isn't running at all.
Click to expand...
Click to collapse
That's not it, I rarely use battery saving mode and this happens 100% of the time.
Ok google for me just does not work.
Anyone get a fix for this?
"Ok Google" works when screen is on, but if I say it while the screen is off, it makes the noise and I get edge lighting indicating it's listening, however it doesn't respond and when I manually turn on the screen assistant is open saying "can't reach Google at the moment."
Power saving mode is off, tried disabling Bixby, clearing cache, nothing.
Hellothere37 said:
clearing cache, nothing.
Click to expand...
Click to collapse
so clearing cache of Google app and rebooting did not help at all?
bizarre, that fixed it for me...
I have a UK version.
I'd phone Samsung!
I'm frustrated too because I can't figure out how to use it while in power saving mode. I thought I added it correctly in the optimized battery usage apps (disabled google, ok google enrollment and voice assitant there). I can't see it as an option to select under unmonitored apps. Any idea what I'm missing?
Thanks for any help
This is strange to hear. Mine has worked flawlessly, as good as my pixel XL. Screen off and locked or not. I say ok Google, phone unlocks, and then I ask it whatever. Only thing ive done is disabled bixby by way of BK disabler.
Sent from my SM-N950U using Tapatalk
May be coincidental but I have not the slightest problem, and yeah, I uninstalled the Bixter. One thing I have read somewhere or other is that the OK Goog command is also subject to the level you set for Bix. In other words with sensitivity turned down for Bix it's also turned down for Goog. I never tested that one but might be worth looking at...
gingi999 said:
they broke ok google about a year ago, very sad.
Click to expand...
Click to collapse
So two things I wanted to mention the first one was my old phone case actually covered one of the microphone holes. Meaning the cut-out wasn't there so I used a drill and made a hole and it fixed part of the problem.
I have to be honest with you the Note 8 solved all the OK Google problems that I was having the past. For example the lockscreen didn't used to work and it works now I mean it was really a piece of trash with my Galaxy S7 Edge and now I can't imagine living without it.
Having problems like the first post where google assistant/ok google is non responsive all around. I've noticed that if I clear cache and data it falls back to just "ok google" and it work all the time. If I activate the google assitant with ok google it fails immediately. Who can fix this?
My google assistant doesn't hear me anymore. When going into settings and stopping the google service and re-enabling it, makes it work again for a short while, but stops working again after a while.
Furthermore, ok google wont work ever, and is also greyed out in settings.
Is there a fix for this?
Did you ever get this fixed?
I have just started having this issue with my p30 pro where the google assistant is not listening to me, i have tried uninstalling/reinstalling assistant, and clearing cache, but it seems that google on my phone at least is determined not to listen.
I am hoping that there is a solution this is quite frustrating
Thank you
Jason
jsbagshaw said:
Did you ever get this fixed?
I have just started having this issue with my p30 pro where the google assistant is not listening to me, i have tried uninstalling/reinstalling assistant, and clearing cache, but it seems that google on my phone at least is determined not to listen.
I am hoping that there is a solution this is quite frustrating
Thank you
Jason
Click to expand...
Click to collapse
im having the same problem on my p30 pro as well, i have factory resetted my phone but the problem is still there. WTF!!!!
same problem here for a week or so.
I must add that the voice recorder app works correctly but when making a call the other person starts hearing me after some seconds, as if the mic takes time to be online.
Tried removing all permission to the mic from apps other than Google to no avail.
Seems to works correctly when wired to headphones
Also, voice search/dictation in google apps (gboard, youtube...) has the same problem
Anyone else? P4xl
Only works after I've opened the app
Occasionally when I unlock my phone after being asleep it won't respond to ok Google...
Battery opt is off
Cleared cache with no luck
virtyx said:
Anyone else? P4xl
Only works after I've opened the app
Occasionally when I unlock my phone after being asleep it won't respond to ok Google...
Battery opt is off
Cleared cache with no luck
Click to expand...
Click to collapse
A few reports of the same on Aussie Whirlpool. I wonder if it's language setting bug.
Mine is fine so far, but I'm still stuck on the old Assistant due to having a GSuite account on the P4XL.
xdatastic said:
A few reports of the same on Aussie Whirlpool. I wonder if it's language setting bug.
Mine is fine so far, but I'm still stuck on the old Assistant due to having a GSuite account on the P4XL.
Click to expand...
Click to collapse
Noticed it since moving onto the new assistant
I have the same issue. need to open open first before it works. i think it started to happen on dec build for me
Same here since running custom roms...
Any known fix? Pretty annoying not being able to use a feature properly
Weird, I have the opposite problem. It's overly sensitive for me, it'll just randomly go off in my pocket when I'm having a conversation
Sent from my Pixel 4 XL using Tapatalk