Problem with Voice Search in AA and S20U - Android Auto General

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

Related

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

[Q] AT&T Galaxy S4 Active - Bluetooth device kills audio during phone calls

Hello everyone! I have been trying to track down a problem with my Galaxy S4 Active that has been driving me nuts for a while. I figured that making a new thread would probably be best because I did not find my particular issue listed.
Basically, what happens is that I will make a call over Bluetooth and everything will be fine. Once this call has ended, all audio related to phone calls dies. The phone still behaves as if it is making and receiving calls, but nobody can hear me and I cannot hear them. Not over Bluetooth, through the earpiece, nor over the loudspeaker. It’s all dead. I also cannot hear it ringing if I dial out, but the phone itself still rings.
I have tried turning the Bluetooth device on and off, disabling Bluetooth and turning it back on, going into Airplane mode and back out again, turning speakerphone on and off, muting and unmuting the call, and muting and unmuting the phone itself. The only thing that fixes this situation is restarting the phone.
I recall this situation first started presenting itself after updating to the ML2 firmware, but it didn’t happen all the time. It became much more apparent after updating to the NE3 firmware. At that point I spent some more time looking into it and became able to readily duplicate the issue.
I have gone so far as to reflash the NE3 firmware with Odin 3.07 to see if the issue remained. Interestingly enough, this appeared to correct the issue until I started updating and reinstalling a few apps. So now I’m trying to track down exactly what did it.
I suspect that it may be the “OK Google” hotword scanning from Google Search because I had it set to detect “From any screen” as well as “From lock screen”. Although I did not have the “Bluetooth headset” setting enabled because I wanted to take that out of the equation. Once I turned off “From any screen”, the Bluetooth appears to be working normally.
Another possibility is that I had frozen S-Voice because it got in the way of the normal voice dialer. This has been restored. I also have to mention that the voice dialer appears to be more stable after disabling “From any screen” as well.
I also can’t say for sure, but it also seems to happen more frequently when charging. Although that may just be a coincidence as I normally do charge my phone when I connect it to Bluetooth. Also I have duplicated the issue when not charging and gotten it to work fine while on the charger. So it is probably just a coincidence.
Here is what I’m working with:
AT&T Galaxy S4 Active (SGH-i537) reflashed back to I537UCUCNE3 Android 4.4.2 stock firmware.
Jabra SP700 - Main device I’m testing with. Old Bluetooth 1.1 speakerphone that clips on a visor. Supports A2DP for an FM transmitter to stream music, but I have Media disabled on it. I tested with and without this setting and it made no difference. It worked great back when I was on MF3, but started having problems since I upgraded to ML2 that are easily replicated now on NE3.
Jabra BT620s - Secondary device that I tested with that also demonstrated the same problems. Although I haven’t tested as much as the SP700. This is a pair of stereo headphones that uses Bluetooth 1.2 and A2DP for streaming music. Also worked better with older firmwares, but I haven’t used it much lately save for testing this problem.
Installed/Updated Programs:
Facebook
Facebook Messenger
Google Authenticator
Google Chrome
Google Maps
Google Play Newsstand
Google Play Services
Google Play Store
Google Search
Google Voice
Google Hangouts
Jift
SuperSU
Titanium Backup
Titanium Backup PRO
towelroot
YouTube
Other apps that I updated and then I rolled back to get things working:
AllShareCase Dongle S/W Update
Amazon Kindle
ANT Radio Service
ANT+ Plugins Service
Antivirus & Security | Lookout
Beaming Service for Samsung
Beats Music
Blurb Checkout
Gmail
Google Drive
Google Play Books
Google Play Games
Google Play Movies
Google Text-to-Speech
Google+
GROUP PLAY
HP Print Service Plugin
Lux
myAT&T
Samsung Link
Samsung Print Service Plugin
Samsung Push Service
Samsung WatchON (Video)
Samsung WatchON (On TV)
YP - Yellow Pages local search
I also tested it quite a bit right before and after rooting it and it was working fine at the time, so I don’t believe that it’s related to root.
I would like to know if anyone else has encountered similar issues or can duplicate what I’m seeing?
Thanks!
After spending some more time testing it, I can verify that it IS in fact the “OK Google” hotword scanning from Google Search 3.6.14.1337016.arm. When it is set to detect “From any screen” and well as “From lock screen”, the audio will die after the first call over Bluetooth. Once I turned off “From any screen”, the Bluetooth works normally.
Now that I've finally found it and can easily replicate it, I'm still curious if other people can replicate it or if this is something isolated to my phone and/or Bluetooth devices. Would anyone be interested in testing this with me?
I'm planning on writing up some feedback on it once I have a better idea of how big an issue it is. I think it would also help anyone else that runs into this problem. I've been fighting with this off and on for over a month because it seemed so random.
Thanks.
I am having the exact same issue with the 2 s4's that I own. I suspected it was either svoice or Ok google, I will try to turn off the from any screen setting and see if it fixes the issue on mine as well. That is a shame because I really like using the ok google feature from any screen.
I've been having the same issue, but did not realize it was ok google from any screen. I've turned it off now, let's see if it works. Thanks for the heads up.
It looks like a recent Google Search update re-enabled the "From any screen" OK Google hotword detection setting. This still is not fixed and it killed all call audio while I was trying to lead another vehicle. I didn't find out until I parked that it was turned back on.
I have sent feedback to Google on the Search app and recommend that everyone else who has had this problem do the same. If this continues to happen, I will resort to negative reviews if I must. Please help get the word out if you are having the same issue. Thanks!
EDIT:
There are apparently several other people having the same problem on other Samsung devices (particularly Galaxy S4's):
https://productforums.google.com/forum/#!msg/websearch/mEhHyCs6F5o/HVArojlzIrAJ
http://forums.androidcentral.com/sa...-sound-phone-calls-after-using-bluetooth.html

[Q] Headset Button opening Google Now

I am unable to use any of my wired headsets with the Nexus 6. The middle button launches Google Now during a call. On the Nexus 5, the same headsets toggled Mute with that button. I have tried apps to reprogram the button (like Headset Button Controller) but they can not override the Google Now function.
Is anyone else seeing this? Any ideas?
Same problem here! Can't find a way to reassign the button to media control or something else. It always starts Google Voice Search.
If pressed when phone is locked I get a message telling me I have to unlock the phone to use Google Voice Search!
Headset Button ControllerTrial did not work!
play.google.com/store/apps/details?id=com.kober.headset
Does turning of Bluetooth headset in Settings, Search & Now, Voice do anything to correct this problem?
stevemw said:
Does turning of Bluetooth headset in Settings, Search & Now, Voice do anything to correct this problem?
Click to expand...
Click to collapse
It's off as default. Benn off the whole time.
Bought SUPRA NiTRO earbuds, problem solved.

Why do apps lock with android auto?

I like android auto when it works. Its great to use for waze and listen to music. Here is where I feel it fails and idk if its a real issue or I need to learn to use it properly.
For example with Waze: If I have my phone plugged in and android auto active, i can't put in a new address or search for a gas station. Waze on my car has no option to type or search for gas stations. If I try to open waze on my phone it won't open. The only way i can do is to unplug get what i need done in waze and plug it back in. I get frustrated and it makes it so unsafe. How do I fix this issue?
There's nothing wrong with your AA, this is how is meant to work for safety reasons. There is no search box during drive, you have to stop and then you can search for a new address. Or, you can do a voice search, by pressing the microphone button on car's screen. Take a look here: https://support.google.com/waze/answer/7580507?hl=en
Sent from my SM-N975F using Tapatalk
informative. thanks

Android Auto few problems

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:

Categories

Resources