Just got my 4 XL and I let everything update. Once everything updated I found it impossible to hit the mic button and dictate text. It takes a good 3 or 4 seconds to actually work. I uninstalled the update and it seems to be working again but I think I am missing the native voice transcription that they went on about.
Anyone else having issues if they updated Gboard.
Gboard mic is working fine. The Recorder app is working too.
Sent from my Pixel 4 XL using Tapatalk
Related
Brand new motox on vzw and the hotword detection and touchless controls don't work the mic on the homescreen is hollowed out and doesn't respond . Phone is brand new and I just updated it last night thinking that would fix it but it didn't still doesn't work . Ive tried changing the country in the settings that doesn't work either K...anyone know how to fix this considering this is the main reason I got it ?
Have you trained it yet? How did that go?
Tbbo514 said:
Brand new motox on vzw and the hotword detection and touchless controls don't work the mic on the homescreen is hollowed out and doesn't respond . Phone is brand new and I just updated it last night thinking that would fix it but it didn't still doesn't work . Ive tried changing the country in the settings that doesn't work either K...anyone know how to fix this considering this is the main reason I got it ?
Click to expand...
Click to collapse
You need to turn on google now as well for it to work. and of course update the google apps. hope that fixes your issue!
Solutions Etcetera said:
Have you trained it yet? How did that go?
Click to expand...
Click to collapse
Yes it's trained still cannot activate it
Sent from my HTC One using xda app-developers app
drago10029 said:
You need to turn on google now as well for it to work. and of course update the google apps. hope that fixes your issue!
Click to expand...
Click to collapse
I've updated Google apps including the Motorola apps the hotword detection didn't work even when I turned it on first day. I downloaded Google's launcher and the detection works fine but on Motorola's home never works . I let the update come through and now I'm on android 4.4.2 and it's still broken also the launcher doesn't look like the kit Kat launcher it still looks like jelly beans/ics I'm not sure if that's relevant or not also phone is not rooted
Sent from my HTC One using xda app-developers app
Tbbo514 said:
I've updated Google apps including the Motorola apps the hotword detection didn't work even when I turned it on first day. I downloaded Google's launcher and the detection works fine but on Motorola's home never works . I let the update come through and now I'm on android 4.4.2 and it's still broken also the launcher doesn't look like the kit Kat launcher it still looks like jelly beans/ics I'm not sure if that's relevant or not also phone is not rooted
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
My bad, correction it should work without google now activated. I just tested it out. 3 words of advice:
1. Launcher has nothing to do with that bro lol
2. [[USING VOICE COMMANDS]] when voice training, your room needs to be like dead silent, enunciate but talk normally.
3. When voice training comes up, do 2 from arms length and one up close. That gets it for me every time.
***EDIT
just realized you said homescreen was grayed out, you should be using the homescreen button. moto voiceless controls should work with the phone completely locked and asleep.
Let me know how that goes.
Tbbo514 said:
I've updated Google apps including the Motorola apps the hotword detection didn't work even when I turned it on first day. I downloaded Google's launcher and the detection works fine but on Motorola's home never works . I let the update come through and now I'm on android 4.4.2 and it's still broken also the launcher doesn't look like the kit Kat launcher it still looks like jelly beans/ics I'm not sure if that's relevant or not also phone is not rooted
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Did the training again got the green checkmarks again and it still doesn't work . Not on the lock screen or home screen . I wonder has anyone else had this issue with the vzw model ?
Sent from my HTC One using xda app-developers app
Anyone else having this problem?
Using nexus 6p fully stock running 6.0.1 on the latest android auto.
Problem is when a new message comes in and it is read or replied to, it still shows new message. So when you get lets say 5 messages from the same person it keeps reading them all from the beginning. So I have to hear the whole conversation every time.
I have looked at all the permissions and all in the 6p but nothing works.
Thanks
+1 on this. I'm also having the same issue. Also with a nexus 6p stock 6.0.1
Sent from my Nexus 6P using Tapatalk
hah. I was hoping this thread was longer and had an answer as I'm having the same issue.
I have a Nexus 6P w/ 6.0.1 stock but rooted. Phone works fine and I use it with a Pioneer 8100NEX w/ the 1.05 firmware. I'm not sure if it's Messenger that is at issue or the version of Android Auto currently out but I had to listen to 12 messages from the wife to get to the new one before I lost my patience and unplugged the phone from the head unit .. marked the messages as read through Messenger and reconnected it.
Are you folks using Google Messenger, Hangouts or another app? Is Android Auto just not able to mark the messages as read in the message db? I'm not sure what the issue is.
I'm using Google messenger. I contacted google about the issue and they said they are aware of it and are working on a fix from there end. I can see an update to android auto soon with the issue resolved
Sent from my Nexus 6P using Tapatalk
wallacerp said:
I'm using Google messenger. I contacted google about the issue and they said they are aware of it and are working on a fix from there end. I can see an update to android auto soon with the issue resolved
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I wonder if this bug is also present when using Hangouts as the SMS/MMS client or if it's AA accessing the sqlite db where the messages are being kept. Any idea?
Wow
Enviado desde mi H60-L04 mediante Tapatalk
aergern said:
I wonder if this bug is also present when using Hangouts as the SMS/MMS client or if it's AA accessing the sqlite db where the messages are being kept. Any idea?
Click to expand...
Click to collapse
No idea but if I had to guess I'd say it's to do with AA accessing messages. I've also noticed when you give AA notification access it automatically turns if off again so I'm guessing that's also part of the issue. I also asked if google planned to implement the ability to use "ok google" instead of pressing the voice button. The AA team replied saying it's also something they are looking at. I think this would be a great feature then you wouldn't have to take your hands off the wheel at all
Nn
I'm not sure if that's better or worse than what is going on now.. Only the first received van be read, the rest it seems like it's reading but stays silent.
Ok so I've managed to get Google assistant working. It's so much better than Google now. But I can't get the always on part of it to function correctly.
It always asks to relearn my voice.
Is there any combination of zips or custom ROMs where Google assistant works as it should?
This seems like such a great feature. I'd love to be able to use it as intended, obviously without having to fork out for a pixel.
Play Store app called chop assistant, gets rid of that training screen
Sent from my Pixel XL using Tapatalk
Not on play store that I can see but here...
https://labs.xda-developers.com/sto...m.chopassistant?_e_pi_=7,PAGE_ID10,7181064431
Ahh it is one word
here:
https://play.google.com/store/apps/details?id=choplabalagun.blogspot.com.chopassistant&hl=en
Sorry for the late reply.
Cheers guys. That's working great.
Now if I can find a way for it to operate even when the screen is off, I won't have a reason to change to a pixel at my next upgrade. Lol
Cheers again.
Pixel 2 XL - Stock
Pioneer HU (don't have the model right now)
Problems:
1) Voice commands no longer route to Waze and I have not been able to get it to work anymore by having Waze open first.
2) Google maps voice guidance. The sound quality is attrocious. I've changed a few settings bit nothing has fixed it.
Anyone have ideas?
Hi,
For your first issue you need to change the default navigator from the unit by clicking twice in the bottom bar icon and selecting Waze.
For the second not many things you can do with Google TTS.
You may try installing a different engine but i haven't tried myself.
Brgds
Sent from my LG-H870 using Tapatalk
ypsmav said:
Hi,
For your first issue you need to change the default navigator from the unit by clicking twice in the bottom bar icon and selecting Waze.
For the second not many things you can do with Google TTS.
You may try installing a different engine but i haven't tried myself.
Brgds
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
Thanks
For 1) Tried that and it no longer works. But know it did in the past. Also removed maps but that's a nogo as well
2) I tried a different TTS engine but it doesn't work wothaps, it still uses Google.. guess I am screw on this one.
Just downloaded an old version of Waze. Working now
Worked once and now stopped.
Bumped like a bumper car
Waze issue happened to me with my OEM headunit (sync 3), the same days it was happening to you.
I was getting horrible voice to text and the sentences did not even make sense grammatically either.. total nonsense. Words like air came out are and are came out our that is how bad it was they did not even sound the same. I finally figured out under manage keyboards there was an extra option enabled Google Voice Typing! That was the culprit disabled it and wow what a difference in my voice to text no matter if I am using gboard or Swifty keyboard it made a difference in both.
Trying this on my Pixel 3 XL. It has been terrible for me since the 'improved' voice to text started a few weeks ago.