Hi guys for the last 2 weeks i'm dealing with these problems:
- the "android auto" lock screen doesn't appear on my Galaxy S10 anymore after i plug it to the usb cable
- the button on steering wheel stopped to activate the Voice Assistant (it starts the car voice one only) so it starts only if I say "hey google"
- The assistant write my whatsapp messages but doesn't read them anymore
- some commands are borked for example if i say "play playlist MIX" doesnt react anymore, it works only if i say "play Mix"
Please help me :crying:
Related
Hi all,
I have an O2X and a JVC KD-X50BT digital receiver installed on my car. With this setup I'm supposed to be able to play my phone's music through car's speakers using the bluetooth from both devices and also answer or make phone calls, everything without the need of getting my phone out of my pocket. Since I installed CM7.2 a few days ago every time I pair both devices I get a message in the receiver "WAIT VOICE Optimus 2X" and I can't do anything, it seems like the receiver is waiting for me to say something. If I click "Back" button (it's the only button I can click =S) in the receiver the message disappears but the music won't play even if the player in the phone shows the music is playing. The only thing I've found that I can do is go to the properties of the BT pairing connection in the phone and disable the "phone" profile leaving only "Media" profile enabled. By doing this I'm able to listen to my music but I lose the phone capabilities in the receiver. If I enabled again the phone profile the music mutes and the "WAIT VOICE" message appears again.
With CM7 comes installed the Voice Dialer app. which if I open it while paired with the receiver the message "WAIT VOICE Optimus 2X" appears and if I close it the message disappears. I have tried uninstalling this app. and also TTS Service and Pico TTS but nothing works. I really don't need and don't want to have voice commands, for that I have the receiver which comes with a microphone and a lot of options for calling.
This never happened before with the stock ROM and yesterday I tested with a second Android phone with stock ROM and it paired with no problems and with both "phone" and "media" profiles, no "WAIT VOICE" messages or anything like that, everything just perfect, music, phone calls, messages, everything.
So, before CM7 everything was perfect, any ideas? maybe a service running in the background that launches some kind of app or something when it pairs? an app that makes the receiver think that I entered in "talk" mode so it is waiting for me to say something?
Right now I have a piece of useless technology installed in my car that I can't use and I'm not going to sacrifice phone or music capabilities =/!
I get this odd tapping/knocking sound when Ok, Google is listening for a command. It does NOT go away after I send a text via voice until I tap the mic icon again and tell it something like stop or **** off. It then says ok or whatever and the knocking noise that pulses with the mic listening .. will actually go away. It started after I updated Google App. I'm on the beta testers list.
I removed the Google App a cache and retrained the voice recognition again ... to no avail.
I'm using a Nexus 6P. It's got stock Android but is rooted with systemless root. Phone works fine except when attached to AA.
Beta testers list for what ?
I think "OK Google" on the phone is not intended to be compatible with AA.
When in AA you are expected to tap the headunit mic icon, or use the steering wheel control for mic to send a voice command through AA.
If "OK Google" works at all while in AA mode, that's more accidental than intentional.
mikereidis said:
Beta testers list for what ?
I think "OK Google" on the phone is not intended to be compatible with AA.
When in AA you are expected to tap the headunit mic icon, or use the steering wheel control for mic to send a voice command through AA.
If "OK Google" works at all while in AA mode, that's more accidental than intentional.
Click to expand...
Click to collapse
oops. Sorry. I meant tapping the icon and saying "Text <person>" .. the mic pulsates and makes this tapping or knocking sound. It was getting stuck. It like OK, Google seem to require a decent network connection to even function properly. I went back outside after I made this post and it worked fine. It still made the little annoying sound but didn't get stuck. I was driving down Highway 280 here in Northern California which runs between 2 mountain ranges and has always kicked me down to 3G/H from LTE. I think this was it but I'm not sure since the voice search is pulled from the phone through AA and it's done by Google App. And like I said .. I use the current beta so I thought maybe it was releated to the update for Google App from yesterday. I simply don't know. It was just irritating and I was hoping it wasn't just "oh .. you have a **** network connection in places so it's going to work kinda janky sometimes."
Thanks!!
I recently purchased a new VW car and have been using Android Auto on the built in display. The first time I used it it all worked perfectly, since then it hasn't. My Android Auto no longer gives me notifications when I receive texts. And if they do show up on the home screen and I click the play button to read them, it shows the four dots as if its thinking but nothing happens and I have to cancel out of it.
Additionally, I've noticed that my bluetooth smart lock doesn't seem to be working at all. Every time I connect it asks if I want to add my car to my trusted devices. Each time I say yes but it NEVER seems to save it. It will then later sometimes prompt for permission to read my messages. To this I again say yes but it doesn't seem to make the message issue go away even after I do this. I am not sure if these two issues are related (I'm hoping they are).
Can anyone tell me why the hell my smart lock can't seem to register and remember my car? And why wont android auto read my messages properly? (Pixel XL. Phone calls and navigation all are working properly)
Same issue here
You have to give Android Auto all permissions it asks for at the first start. And be sure to use a very good cable. There are many USB C cables on market which are not fully supporting USB C features and the system do expect them.
I'm in the same situation with my VW Atlas. Problem is with both my Pixel (running Android O) and my wife's Nexus 6p (running Nougat). I have given it all permissions, including some that it didn't ask for. I also have been using the little 4 inch cord that came with the 6p, so the cable or its length should not be an issue. In addition to the above, my car also forgets its bluetooth pairings if I try to connect the AA cable before the bluetooth has connected. I've been learning to do that but sometimes I forget. It's got to be an issue with the VW software.
I have come across these issues myself in a Golf Mk7 both with a Motorola Droid Turbo and now with a Google Pixel 3 XL.
In the case of getting Android Auto to read/send messages where you just get the four dots bouncing up and down and doing nothing else, that's a setting with the Google Assistant app. Go into that app on your phone (the round G icon) and drill into settings and under Voice >> Voice Match, make sure "OK Google" detection is turned on. Even though you might not be actually using it, it has to be turned on for this to work. Totally lame and non-intuitive, but that's what fixed that for me.
As for the car falling out of your Smart Lock and for repeatedly prompting you for permission to access your text messages, I have only had this issue with AA in my VW and not in other cars, so it's a VW-specific issue and something to do with the bluetooth hardware. I do not have a fix for it but the workaround is you must have BT turned on on your phone first and let it connect fully to your car OUTSIDE of AA. Make sure at that point you permit text message access (if prompted) and check your Smart Lock and add your car to it if needed. Then going forward whenever you connect to your car you MUST let BT connect fully first before you plug in and fire up AA. It's unfortunate that you can't just plug in and go w/o waiting for BT first but that's the only way I've gotten this to work without re-prompting me for SMS access permissions and Smart Lock.
Good luck!
Since some of recent updates I lost the voice control over my Parrot bluetooth car device. When I use my magic word PHONE or click the activation button of the Parrot, Note 9 screen shows 2 options - BIXBY and Google Assistant. And somehow does not return the command to the car device.
The calls work fine, but I used to make voice commands to make calls with voice commands.
Thank you in advance for any help.
I have a problem with freshly rooted my S20U, unfortunately after connecting the phone to the car and turning on, for example, google maps and pressing the microphone, the music mutes, but the voice search does not work, the application responds to the word Ok google, please help