Odd knocking sound with voice commands. (texting, ok google .. etc) - Android Auto General

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!!

Related

No voice dialer in ICS - what we tried so far and what seems to work best.

Hi everyone.
First post but long time reader.
I have an un-rooted Vivid I updated the other day through the phone dial trick. Everything went fine with the update except all my previous apps appeared except for the voice dialer. I had a shortcut set on one of the screens and the label showed up with the little android guy as the image. When I clicked on it the message said the app is no longer associated. Sure enough I went through all the apps and it was not there.
I tried to install the apk and checked off the box to allow installation of unknown apps. It appeared it was working then I got a message during the install that the it did not install. I tried a few times just to be sure.
I also noticed that I am not able to use my bluetooth ear piece to accept a call or voice dial.
Does anyone have the voice dial app working or was it left out of the update? I tried the google voice app and that doesn't work with bluetooth.
I have a message to HTC regarding this as well. If there is no solution here, I will post what they plan to do if anything.
Edit 4/2/12 see the posts on pages 3&4 for a Voice dialer that works pretty good so far in ICS. There may be others that work just as well but I'm tired of trying to find them. Until (doubtful) google or HTC fixes this issue I'll stick with I have now.
I don't have a solution, but I have the same problem.
My Blueant Q2 headset has a command to activate the phone's voice command. The phone said my phone doesn't support that feature.
That's unfortunate because I use it all the time.
Sent from my HTC PH39100 using xda premium
Over 170 views and only one response.
Does everyone else have the voice dialer like we had in GB? If so can you post the apk?
Using bluetooth without it is very difficult to say the least. It's even more distracting than just picking up the phone and talking except that's not an option in many area I travel through.
vivid x2 said:
Over 170 views and only one response.
Does everyone else have the voice dialer like we had in GB? If so can you post the apk?
Using bluetooth without it is very difficult to say the least. It's even more distracting than just picking up the phone and talking except that's not an option in many area I travel through.
Click to expand...
Click to collapse
Few to try - this was an issue with the Inspire at times too. This is an older apk and probably won't work, but backup and try.
http://forum.xda-developers.com/showthread.php?t=1005228
Some suggestions here:
http://forum.xda-developers.com/showthread.php?t=1314862
Also an app in the market called Hands-free voice dial that might work
After reading your post I tried messing with the voice dialer to see if I could help. It turns out it's not even installed on my phone and its not on the market. Voice actions are supposedly alot better and I wonder if the dialer was done away with in favor of voice actions. One problem with this is on my headset it now does nothing but beep at me when I hit the call button where as it brought up the dialer before. Also I held down search and tried to voice dial through voice actions and it couldn't pick up my voice through the headset. Right after I was messing with it I got a call and the caller could here me fine through my headset. So I dunno what the deal is. Oversight maybe? I'm fine with voice actions replacing the dialer but not if my button on my headset does nothing and i can't use my headset to use it.
Sent from my HTC PH39100 using XDA
Okay, so it was a fluke, voice actions picks up my voice now. However, my call button still doesn't activate it. I have to unlock the phone and hold down search to activate it. I can make calls through it fine however so i think that is the solution. I believe the lack of support of a voice dialer button on a headset is most likely an oversight. Sucks but I hope this at lead helps you out for now.
Sent from my HTC PH39100 using XDA
Okat HTC got back to me and here is their response. It fixed part of the issue but still no voice dialer app. I can now answer an incoming call by pushing the button on the earpiece. So far only half a fix. I'll try to find a decent dialer on the market. The google one sucks.
I can certainly help you with Bluetooth functionality on your HTC Vivid. I essentially want to clear some Bluetooth data from your phone and then see if the issue continues. First let's navigate to home>menu>settings>Bluetooth. Tap on the settings icon to the right of your Bluetooth device's name and let's select unpair.
Now let's return to settings and tap on Apps, then All. Please tap on Bluetooth share and select clear data and confirm. If your Bluetooth headset has an option to clear its partnerships, please do that as well.
We need to restart the phone. To do this let's just hold down power and select restart. When the phone boots back up are you able to pair with and properly use your Bluetooth headset?
yeah I can answer calls, and if I hold it down, it'll redial the last caller in my call log. But yeah if i just hit the button, it makes a beep and does nothing. I actually primarily use my headset for music playback, its a motorola SD-9 stereo bluetooth headset, but it works for calls too. I had to re pair it after the ICS update.
Ours do the same thing. Thanks for confirming I'm not nuts. I hope they didn't rush the update through just to be first with the update to ICS.
I have an older Moto HS850. I'm searching for a decent visor set since I now wear hearing aids. It's a bit tough to hear with the BT earpiece as it is since I have to have an aid out. Until I can get a decent voice dialer app I'll hold off on blowing money for a half assed solution.
Hope HTC comes through and develops a dialer for ICS. At least you'd know it'll be functional. So far I've tried three apps off the market and none have worked for what I need.
I guess I can always switch my phone out with my daughter if I really need to. I told her not to update yet since I was willing to be the guinea pig. She never uses her voice dialer. I would feel like taking a step back but GB was not bad at all.
I agree, gingerbread was great, I was hesistant to update but figured might as well. Hopefully HTC issues a fix for this problem quickly.
Cor-master said:
...Voice actions are supposedly alot better and I wonder if the dialer was done away with in favor of voice actions. One problem with this is on my headset it now does nothing but beep
Click to expand...
Click to collapse
I tried holding down the Search to activate Voice Actions. The Vivid seemed to use my Blueant Q2 mic. However, Voice Actions definitely doesn't work as well as the Voice Dialer for dialing contacts.
I'll be monitoring this thread for solutions.
I found a solution that isn't completely eligant buy works.
I downloaded Vlingo and setup the un-car option to auto listen for commands. Don't leave Vlingo in-car on fulltime else it will drain your battery.
However, when I signal phone commands from my header, it fires up Vlingo. Set it to default to in-car Vlingo. From the you can say "Hey Vlingo..." and speak your command. My Blueant Q2 headset still says "Feature not available" but it works.
Sent from my HTC PH39100 using xda premium
willgill said:
I found a solution that isn't completely eligant buy works.
I downloaded Vlingo and setup the un-car option to auto listen for commands. Don't leave Vlingo in-car on fulltime else it will drain your battery.
However, when I signal phone commands from my header, it fires up Vlingo. Set it to default to in-car Vlingo. From the you can say "Hey Vlingo..." and speak your command. My Blueant Q2 headset still says "Feature not available" but it works.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Vlingo virtual assistant is the best.
Thanks fro the recommendation for vlingo. I haven't tried that one yet. Seems cummbersome to use. The voice dialer app was so easy to use. Everything else so far takes too many steps.
I'm checking out the new Motorola Roadster2. There is a Moto app that is made to use for it. So far all the reviews I read did not say anything about it working with ICS or not working. Most of the gripes were from Iphone users. I may hold off a little while until such reviews start coming in.
The Voice Dialer app we had in GB was an Android app built into GB. I had a version from 2.3.4 on my retired Sony phone that I bluetoothed over to my Vivid. It installed but would not work prpoperly. I tried disabling the voice thingy from ICS and it still didn't work. When I had the GB VD installed ICS was sluggish so I removed it.
Here is the latest response from HTC:
We apologize that you are unable to use the handsfree dialing over Bluetooth. Unfortunately, the Voice Dialer app was removed with the Ice Cream Sandwich update. There is no information available as to when or if this will be added again on the device as it was a change made by Google.
This might fix it,
I took the Bluetooth.apk from a Cyanogenmod and it got my wiimote to connect (see my post: http://forum.xda-developers.com/showthread.php?t=1560647) it should lift any nasty restrictions that HTC's bluetooth version has put on anything.
zacgoesrawr said:
This might fix it,
I took the Bluetooth.apk from a Cyanogenmod and it got my wiimote to connect (see my post: http://forum.xda-developers.com/showthread.php?t=1560647) it should lift any nasty restrictions that HTC's bluetooth version has put on anything.
Click to expand...
Click to collapse
My issue isn't being able to pair my device it has to do with an app that Android left out of ICS that worked so well in GB.
Thanks for the info though. What can you do with the Vivid when it's paired with a wiimote?
vivid x2 said:
Thanks fro the recommendation for vlingo. I haven't tried that one yet. Seems cummbersome to use. The voice dialer app was so easy to use. Everything else so far takes too many steps.
Click to expand...
Click to collapse
I understand vivid x2. I had used Vlingo before but then switched to the native Voice Dialer for the simplicity.
My problem with most 3rd party voice dialers is the only recognize and expect first names. With over 600 contacts, that won't work for me. Vlingo and Voice Dialer did use first and last names.
Sent from my HTC PH39100 using xda premium
Im having another bluetooth related issue. I primarily use my headset for listening to music. Since the ics update my music will go into random skipping sessions. It's not related to 4g or wifi as I mowed my lawn using a regular set of headphones and didn't have any issues. There is almost a pattern to the skipping actually. If kill pandora or Google Music and restart it'll fix the issue for a little bit but it'll start up again eventually. No issues before the update.
Sent from my HTC PH39100 using XDA
Bluetooth Hands-Free Dialing Broken
After reading this thread, I tested my bluetooth hands-free connection in my car. It's BROKEN. My Vivid will connect to the car's audio system via BT, but it will not recognize my voice requests to call a number. It was working last week before I did the ICS "upgrade."
I expected something to not work, but I didn't expect something as critical as a safety feature. I use the hands-free dialing for obvious safety reasons. I have a feeling that HTC is catching heck about this one. They are about to catch some more from me.
I hope this isn't a case of "you got your update now shutup". Hopefully they'll release an update for bluetooth and voice dialing
Sent from my HTC PH39100 using XDA

[CM7] Bluetooth launches voice service when pairing with car's stereo

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 =/!

Bluetooth issue with car radio

I have a 2013 Chevy Spark with bluetooth. It has the voice control activation button on the steering wheel. When I had my Galaxy Note, this would activate S-Talk and I could use voice controls through the car. When I try with the One, an app pops up and quickly closes on the phone, then the radio says voice control isn't supported, but half the time if I start talking, the voice control works anyways. Does anyone know if there is a way to fix this? I am on ARHD, but I had the same issue when I was still completely stock with a locked bootloader. This could be a deal breaker because I do a ton of driving and use voice control a ton.

[Q] Bluetooth headset issue

Hi,
I've bought a "Jabra Stealth" headset and I'm unable to launch Google Now on my Nexus 6 (Android stock 5.0.1, FrancoKernel r8) with the dedicated button although it's a built-in feature of the headset. I assume that this is an issue of compatibility with Android 5.0. Jabra has answered me that I didn't configure vocal commands well but that's false. Has someone encountered the same problem and has a solution for it?
Thanks
xof9999 said:
Hi,
I've bought a "Jabra Stealth" headset and I'm unable to launch Google Now on my Nexus 6 (Android stock 5.0.1, FrancoKernel r8) with the dedicated button although it's a built-in feature of the headset. I assume that this is an issue of compatibility with Android 5.0. Jabra has answered me that I didn't configure vocal commands well but that's false. Has someone encountered the same problem and has a solution for it?
Thanks
Click to expand...
Click to collapse
I have a similar issue. I use a Plantronics Voyager Legend. A couple of issues:
1) press and hold of the action button will bring up "voice dialer" instead of "google now". I dont know if you've ever tried to use voice dialer, but i think its more or less deprecated since the nexus 1 was the new kid on the block.
There is an app for bluetooth on the app store that lets you choose what to launch with that button. however, it didnt work that well for me. lots of lag and it blended together with other bluetooth related issues.
2) Bluetooth never seems to "turn off". I have a smart sensor enabled headset. IE the phone should know if i have the headset on or not, and pipe phone calls and notifications and ringtones to the speaker if i dont have it on and to the headset if i do. instead, the phone constantly pipes EVERYTHING to the bluetooth headset. no fix yet.
3) phone connection to my car's bluetooth makes my audiobook start playing. I have no idea why. it is not a setting in the audiobook app. Seems that the fix is to disable streaming media over bluetooth (contacts/messages only)
From what ive witnessed with issues regarding audio, screen brightness, bluetooth, this is yet another half-baked google product with little to no attempt at a proper follow through. just a crap device rushed to market with tons of potential and a complete crap OS and barely any thought or usability effort put into anything except the home screen.
I also have the N6 with the P Legend. I am having issues where the caller can barely hear me. Do you know if you have this issue at all?
shrimants said:
I have a similar issue. I use a Plantronics Voyager Legend. A couple of issues:
1) press and hold of the action button will bring up "voice dialer" instead of "google now". I dont know if you've ever tried to use voice dialer, but i think its more or less deprecated since the nexus 1 was the new kid on the block.
There is an app for bluetooth on the app store that lets you choose what to launch with that button. however, it didnt work that well for me. lots of lag and it blended together with other bluetooth related issues.
2) Bluetooth never seems to "turn off". I have a smart sensor enabled headset. IE the phone should know if i have the headset on or not, and pipe phone calls and notifications and ringtones to the speaker if i dont have it on and to the headset if i do. instead, the phone constantly pipes EVERYTHING to the bluetooth headset. no fix yet.
3) phone connection to my car's bluetooth makes my audiobook start playing. I have no idea why. it is not a setting in the audiobook app. Seems that the fix is to disable streaming media over bluetooth (contacts/messages only)
From what ive witnessed with issues regarding audio, screen brightness, bluetooth, this is yet another half-baked google product with little to no attempt at a proper follow through. just a crap device rushed to market with tons of potential and a complete crap OS and barely any thought or usability effort put into anything except the home screen.
Click to expand...
Click to collapse
When the caller can barely hear you, check your phone. Sometimes, even though my headset is on, the phone doesn't care and attempts to use the phones speaker or mic.
shrimants said:
When the caller can barely hear you, check your phone. Sometimes, even though my headset is on, the phone doesn't care and attempts to use the phones speaker or mic.
Click to expand...
Click to collapse
That's my current issue...
I can answer the calls with either my truck or ear piece, but both will randomly not have audio. The phone says it's connected BT, but I have to switch the source to speaker or handset and then click back over to BT. The whole time while I'm begging the person on the other end not to hang up and to hold on a second. Not bad when I'm at my desk with earpiece....let's just say it's a bit more nerve-racking on the highway.
scap99 said:
That's my current issue...
I can answer the calls with either my truck or ear piece, but both will randomly not have audio. The phone says it's connected BT, but I have to switch the source to speaker or handset and then click back over to BT. The whole time while I'm begging the person on the other end not to hang up and to hold on a second. Not bad when I'm at my desk with earpiece....let's just say it's a bit more nerve-racking on the highway.
Click to expand...
Click to collapse
Same here. Also have a problem where, when on a call, an incoming call will kill bluetooth. This makes it unusable in my car as it becomes a real safety issue. I have to turn off BT and use the speakerphone which luckily is good enough for the job. Even switching the source and switching back doesn't always work for me.
I regret not sending the phone back for this problem. I'm waiting on v5.1 this month as rumored, hoping that will solve the problem. May just go back to my Lumina 925.
Has anyone tried going into Google settings app -> Search & Now -> Voice and turn on Bluetooth Headset (records audion through bluetooth headset if available).
I have Nexus 5 and Jabra Stealth and I had the same problem. I could solve it thanks to these indications: hackerspace.kinja.com/reassign-your-bluetooth-phone-button-to-open-google-n-1507391132
Same issue with calls not having audio through the car Bluetooth unless I switch to speaker/handset then back. I guess Marshmellow really messed up Bluetooth on a lot of people's phones not just us. Tried different rooms(AOSP, CM, stock) no help even tried updating the radio which helped Bluetooth crashing completely and requiring a restart but the phone issues remain.

Hotword not working, DND mode auto triggering

I've been posting regularly in Google Android Auto forums, but nothing has been happening. I thought maybe someone here would be of more help.
I use Android Auto (just updated again today, version 4.2.591444-release) on my OnePlus 5 (Android 9, OxygenOS Beta 30) with a Bluetooth FM Transmitter in my car. Same setup as I've had for a while (apart from updates to the OS or the app, of course.)
There are three issues here.
1. The hotword doesn't trigger anything to happen. Sometimes it does right after an uninstall/reinstall, but once and only once and only if it's not connected to my FM transmitter via Bluetooth. I have tried uninstall/reinstall, deleting and retraining my voice model, giving AA every permission it asks for. The hotwords trigger with no problem when it's not in AA mode.
2. AA auto triggers Do Not Disturb mode. This means it doesn't give any audible notification for phone calls/texts/hangouts/weather alerts/job notifications. Doesn't matter what the app is, it doesn't trigger. I only know I'm getting a call if I happen to look at my phone. I can go in and manually turn off DND mode, but I have to touch "turn off" twice every time for it to work.
3. It's set to autolaunch when it connects to my FM transmitter. It often doesn't. It pairs to my transmitter with no problem, but doesn't launch. The AA icon is in my notification shade, but when I pull it down, it's saying that it's launching with the little progress bar. I have to actually launch it myself.
All of these issues are new within the last few months. Before all of this, I'd jump in to take kids to school, my phone would autoconnect to my transmitter, and the kids would proceed to ask Google to play their favorite songs. Awesome. Sometimes I'd get a notification that a job was available (I'm a substitute teacher) and I could accept it. Now...none of this happens.
Any thoughts you all have? I've not seen threads here describing this issue, but in Google's forums, it seems to be happening both with head units and the app, no matter what kind of phone/auto combo it is.
I have the same issues (2 & 3) and I'm pissed

Categories

Resources