I've come across many threads related to the following issues, but it my perusing experience, it seems that some topics are only slightly covered, but each thread seems to create more questions.
So, I thought I'd take some time to aggregate the collection of knowledge out there for Car Integration with a GS3.
This thread is based on my personal experience with the Sprint GS3. I will note where I can with knowledge about different carriers and/or different models.
It's interesting to note that the Sprint website and Owner's Manual pdf for the GS3 does NOT have a 'Car Mode' or 'Driving Mode' listed when doing a search of the document.
I will update this thread with feedback from the community as some additional knowledge/specifics trickle in (and when I have more time). If this seems useful to you, let me know, and down the road I'll update this thread with some links to some of the other threads too. (I can't post outside links yet, new poster here, will do when obtained access).
Request to Sticky?
Please Give a 'Thanks' if this Help you.
Car Mode:
What is does - It is supposed to automatically open the default 'Car Home' app. Which could be anything that has this code tagging build into the app. In my case, it's the 'CarHome Ultra' app by TheSpinningHead. There are other general 'Car Home' apps in Google Play. Many of them are titled with the exact words 'Car Home' in them. Some examples are Car Home by Google, Samsung Car Home, Custom Car Home. All are 'Car Home' apps.
I'm under the impression that 'Car Mode' is only engaged via a properly programmed TecTile (or any NFC tag), or via a specific app (see Note #2 below)
The main app that many are using for programming their NFC tags is NFC Task Launcer (by Samsung). There are others out there in Google Play Apps
Some threads/people have wondered/noted that 'Car Mode' is the same as 'Driving Mode' in multiple threads. I'm under the impression that these are definitely NOT the same.
See below for more info related directly with NFC Task Launcher integrating 'Car Mode'.
Additional Note #1: There are some phones out there where a physical car dock will launch or engage things. One example of this is the Galaxy Nexus and it's official Google dock. I'm under the impression that this theoretically could be done with the Spring GS3, but to date, no dock exists that can automatically trigger Car Mode?
Addtional Note #2: There's an App or two in Google Play that can toggle Car Mode: 'Car Mode Control' and 'Car Mode On'/''Car Mode Off'
This might not be 100% correct here, after talking with the developer of NFC Task Launcher,. who mentioned that the Car Mode will launch S-Voice, by default, and then potentially be trumped by the install of a car app. See additional notes below in 2nd post
Driving Mode:
What it does - I'm under assumption it engages voice TTS services (text to speech), to read aloud who is calling, for voicemail, and for text messages notification.
Some carriers have toggling ability for this directly in their status bar pulldown menu options. An example of this presently is Verizon.
However, for Sprint, the only ways to turn this on/off presently are:
1) Toggling in Setting -> Language and Input -> Text-to-Speech Output -> Driving Mode
2) via S-Voice toggling, saying "Turn Driving Mode On" or "Turn Driving Mode" off.
I'm under the impression that there's no way to tell if one has this engaged or not except by deduction via one of the two above methods.
Lingering Questions related to Driving Mode:
1) There's a Google TTS service and a Samsung TTS service. Which one is used for what? and which one works with Driving Mode?
2) For the life of me, I can't get this function to work on my phone at all. I can engage driving mode via both methods. However, I can never get the phone to announce call, voicemail, or text message notifications. I'm under the impression that this might only work with other carriers or models right now. It appears that I'm not alone in this. If you've had this issue and have figured out how to get it to work, please list here. I'm under the impression Sprint has not engaged this functionality (hence, why Driving Mode does not appear in the Notifcation pulldown headers). So, waiting around for this on Sprint?
Home Mode or other:
As best I can tell, this is an erroneous term that has no basis, but has been added to some threads when peeps have been talking about all this stuff (I believe only outside of xda forums, haven't seen it here)
Bluetooth Integration:
There's a handfull of factors going on here that might affect bluetooth integration with your vehicle. I'll list the 'facts' that I'm familiar with...
Some cars have Bluetooth built into their car radio. Some of these radios use v2.0, some use v4.0
Some cars have a USB connection to their car radio. This allows some moder car docks to both use the battery charge and audio output via their usb connection on the GS3.
Some cars have an audio input jack (3.5mm)
Some cars have an audio only integration potential in their car radio (for music only)
Some cars have audio + other goodies in their car radio (music plus contacts)
If your radio has no USB , but it does have an audio input jack, there are a few products on the market that allow a BT add-on product. (I personally use a Blackberry BT Stereo Gateway). I believe any product you get has to have the A2DP protocol (aka 'stack') built into it, or it will not work
Here's where more fun begins:
The GS3 uses Bluetooth protocol 4.0 (this is the most recent as of now).
The implementation of BT coding in the GS3 has some hiccups as noted by many threads. Some have found work arounds, some have not. Some of the workaround include clearing the BT connection history in the vehicle and then repairing with the device. Other workaround tweaks are out there also.
Many cars that have bluetooth integration (whether built in, or add-on), might have a car that uses BT v2.0
It's been noted that, even though your GS3 might have paired to the v2.0 BT, it may still not auto-connect. (I personally have 2 x BT 2.0 devices in my car and the GS3 only autoconnects to one of them, a Parrot phone integration).
It's a known issue (let's hope that Samsung has it high on their priority list)
Hopefully, a future update by Samsung and/or carrier patch will fix this. (This is probably the most frustrating thing I'm waiting to get 'fixed' with my GS3)
Tools/Apps to help Car Integration:
NFC Task Launcher App:
In this app, there's an 'action' called 'Car Dock' (and an equivalent 'Desk Dock')
When an NFC tag has this action embedded in it, to turn on 'Car Dock'... 'Car Mode' is enabled on the phone. (Isn't it great having all this confusing labelling? It's a Samsung app and Samsung phone. Why different?)
A 'Car mode' notification icon appears in the status bar (a steering wheel) and also remains as a full entry slot in the 'Ongoing' notifications until one presses the notification to turn 'Car Mode' off (or disables via a toggling function via 2nd tap of an NFC tag. The 'NFC Task Launcher' can set TecTiles (tags) to toggle functions on repeated taps).
It is supposed to automatically open the default 'Car Home' app. Which could be one of a handful of 'Car Home' apps, such as the 'CarHome Ultra' app.
Google has their own Car Home app too.
CarHome Ultra App:
This is one of the various general 'Car Home' apps available in Google Play. I can't talk to much here on a comparison versus other apps in the marketplace, but I'll highlight a few tidbits that seem to be nice, and might provide some insight as to what a 'Car Home' app can do for you. Features: Big Icons to easily press while in your vehicle, icons that are shortcuts to any app you want or system setting, custom color creation for both day and night modes, speed and weather info, location alerts, orientation lock or sensor based, media volume setting, and a coupling/decoupling setting to couple to the 'Car Mode' function discussed above (in case a dock does the launching by itself vs via the 'Car Mode' engaging from other methods).
Also, if one doesn't have any NFC tags, then this app can 'make up' for tag function with additional setting mods. The app can automatically turn on off both wifi, gps, AND bluetooth via setting ticks when launched. Good Stuff.
Car Mode Widget: If you want to only use local speakerphone while in 'Car Mode' (and coupled to your car stereo), then this might work to engage for incoming or outgoing calls. Just search the marketplace for it.
Car Mode Control App: As noted above in the 'Car Mode' section, this app is a simple launcher icon that can toggle Car Mode on/off.
Other System Settings (that might be important to you):
(settings that might affect how your device behaves for car integration)
These are all accessible in System Settings (aka Settings):
1) Language and Input -> Voice Commands for Apps (allows 4 separate topcis to recognize voice: calls, alarm, camera, music). Music and Calls, I assume, would be of best interest to use in an automobile
2) Dock -> Audio Output Mode This allows use of external speakers when device is docked.
With this 2nd item, how does the GS3 recognize it's in a 'dock'? Does it solely check that a usb connection is made? Does it check to see that it's connected to a 'modern' car stereo that has both usb power and audio input via usb too? Or other?
Thanks for any responses, and I'll integrate when I have time.
After further learning and intergration while dealing with my GS3 car integration, I've come across some more notes.
(Sine the original post, I'm now using JB 4.1.1 leak from Sprint, installed via Odin)
Text to Speech (TTS) Notes:
So, there are a few threads out there that talk about having problems with getting TTS (text to speech) to work for phone call and text messages, while in Driving Mode.
Some say had it working, but can't anymore, or can't turn it off, etc.
I had the same issue, but couldn't figure out the exact settings.
But, this does the job:
System Settings - Language and Input, Under the Speech header, go into the 'Text-to-speech output' line and configure your preferences (google vs samsung engines, speech rates, etc)
But, here's the partially non-intuitive kicker...
MAKE SURE you click on the 'Driving Mode' line, NOT the ON/OFF toggle, but the the actual line entry.
That should open up a list of tickboxes for what Driving Mode with read out loud for you.
Incoming Calls
Message
New Emails
New Voicemail
Alarm
Schedule
Unlock Screen
Therefore, if you want something read, make sure there's a checkmark in the appropriate box
Also, another big kicker...make sure that in the 'Voice recognizer' line, under the Speech header, you set it to the Samsung Vlingo setting, NOT the google setting. Selecting the Samsung entry vastly changes the options for the 'Voice search' line item.
Make sure that after you select 'Voice search', scroll down to the Message header where there's a tickbox for 'Show body of message', and place a check there.
That's Soooo Intuitive, isn't it?
Why would I tick 'show body of message' to get it to read something. Makes sense, huh?
(although it does mention the phrase Driving Mode here, to play devil's advocate)
Anyways, I'm guessing this should allow all people to hear FULL text messages read out loud to them.
If the last tickbox mentioned above wasn't checked, you only get the "New message from 'person X' " voice.
If the last tickbox mentioned above was checked, you get "New message from 'person X', The message says 'body of text message' "
(I can't remember if the settings were exactly the same in ICS vs JB, some system settings menus got tweaked between the 2 roms)
And after all of this above fun, I still can't get the TTS to read any of the New Emails count number that it's supposed to read. Hmmmpf.
Additional Driving Mode Notes:
So, for 'driving mode', there's a few ways to turn it on.
1) The system settings menu to toggle it on/off (make sure to click on the 'bar' for this item to get access to many checkboxes
2) The Driving Mode Widget that you can download from Google Play
3) my NFC Task Launcher app can turn on/off/toggle Car Mode and also couple 'Driving Mode' to it. (note the original NFC Launcher app did not do the Driving Mode thing) (Also of note, Driving Mode can not be manipulated by itself, it must be coupled to the Car Mode on/off/toggle function)
4) S-Voice that can turn driving mode on or off
5) Non Sprint users might have it in their notification bar
6) I talked with the Developer of NFC Task Launcher, and he mentioned, that engaging Car Mode opens S-Voice on the Samsung GS3, by default, and could be trumped by another Car Mode app installed, therefore opening, for example CarHome Ultra, instead of S-Voice (vs AND S-Voice). The reason I mention this, is that it might be involved with why Driving Mode won't turn on sometimes. It could be that both S-Voice has to be opened in the background also, to get this to work. Testing to follow soon. This is what helped me find the solution below. Thanks NFC Task Launcher author/authors!
So, if you've had problem with the above, you've probably noticed items like this:
I've noticed a difference between items 2, 3, and 4
When I solely turn DM on via 2, it DOES NOT allow TTS to work
However, when I got to turn on DM via 4, then it DOES allow it to work
Then, when I go back to toggling DM on/off via 2, it will toggle the functionality of DM accordingly with TTS.
What the heck?
So, not being a programmer, but just simple tweaker, I can only assume that turning on DM via S-Voice turns on an additional service/task/activity or some android equivalent.
This is Usually how it goes for me. Ive had instances where this exact flow doesn't happen all the time
Can anyone help me out here? I'd love to know exactly what S-Voice turns on in the background when starting DM vs just starting via the the DM Widget.
Solution Found for TTS! This should work for ALL who are having Problems:
I had been using Car Mode for so long, I had forgotten one simple fact.
When Android sees multiple apps that can meet a request to open a new app, you have the binding options (This Time Only vs Always).
Well, when Car Mode started for me, it always opened my Car app (CarHome Ultra). I had forgotten that it gave the choice of CarHome Ultra OR SVoice.
So, I immediately tried launching Car Mode (and therefore CarHome Ultra), AND independently having my NFC tag programmed to open SVoice prior to launching CarMode (order of operations important, since launching CarMode also triggers DrivingMode ON....but SVoice has to be open already).
I've been using for a while now, and it seems good. 100% TTS fucntion ON and OFF with NFC Task Launcher
Does anyone know how to get the audio for phone calls to go through the car speakers using the iBolt car dock?
The audio for everything except phone calls goes though the usb connection to the aux port in my car and works beautifully, but when I make/receive a phone call, it changes to speakerphone.
I know I could run another wire from the headphone jack, but that seems silly when all the other audio goes through the USB connection just fine.
Currently I am rooted and running the latest JB leak for my Verizon GS3, but I had the same problem on stock ICS as well.
I tried the app called "Setting Profiles", but I could not get that to help any. I also tried manually turning off the speakerphone, but then I heard nothing.
Thanks for the help!
Nino
ninosidari said:
Does anyone know how to get the audio for phone calls to go through the car speakers using the iBolt car dock?
The audio for everything except phone calls goes though the usb connection to the aux port in my car and works beautifully, but when I make/receive a phone call, it changes to speakerphone.
I know I could run another wire from the headphone jack, but that seems silly when all the other audio goes through the USB connection just fine.
Currently I am rooted and running the latest JB leak for my Verizon GS3, but I had the same problem on stock ICS as well.
I tried the app called "Setting Profiles", but I could not get that to help any. I also tried manually turning off the speakerphone, but then I heard nothing.
Thanks for the help!
Nino
Click to expand...
Click to collapse
I haven't come across this specifically, but wondering if you're using a standard USB cable to run from your phone to the car radio or a USB OTG cable? I'm under the impression that i can only get audio going with an USB OTG spec'd cable. Not sure if this is involved with music vs phone audio, but there's the chance. The OTG USB cable are only a few dollars, but definitely are recognized by the GS3s as a different kind of connection. There's always the chance each of the GS3 flavors would then deal with things slightly differently (such as Sprint not having a Driving Mode toggler in their Notification pulldown). I think I've come across some mentioning audio out of the usb workes with regular usb connections, and sometimes needs an OTG connection.
I feel your pain. I finally resorted to Tasker to get this functionality (mostly because JB doesn't seem to have Driving Mode at all!). Setting it up was surprisingly easy and it works every time without any (more) headaches. Basically I created a variable and a couple tasks to toggle the value. I then set up a profile that reads any incoming texts if the variable is set to "on". NFC Task Launcher calls the appropriate task to toggle the value.
The Driving Mode Widget you mentioned also works with Tasker if you don't want that ugly green dot on your homescreen. But, again, this is only relevant to ICS. If you want this functionality on JB then Tasker is the only option I know of.
Great writeup thanks going to save me alot of time and headaches figuring this out. I've got a Note 2 7105 UK model and all the checkboxes were already enabled for the TTS stuff although it was set to google instead of samsung. I'm going to get some NFC tags and use tasker, then choose a suitable driving app, or just create a home page screen with all the stuff on I use for driving: nav, spotify, speed cam locator etc.
I found a tip for NFC, if you dont have any tags yet you can use a bank card if it has a NFC chip in it, good for testing at least.
New insight?
I talked with the Developer of NFC Task Launcher, and he mentioned, that engaging Car Mode opens S-Voice on the Samsung GS3, by default, and could be trumped by another Car Mode app installed, therefore opening, for example CarHome Ultra, instead of S-Voice (vs AND S-Voice). The reason I mention this, is that it might be involved with why Driving Mode won't turn on sometimes. It could be that both S-Voice has to be opened in the background also, to get this to work. Testing to follow soon.
(info inserted into OP also)
I Finally figured it out how to get TTS to work with an NFC tile and CarMode!
I had been using Car Mode for so long, I had forgotten one simple fact.
When Android sees multiple apps that can meet a request to open a new app, you have the binding options (This Time Only vs Always).
Well, when Car Mode started for me, it always opened my Car app (CarHome Ultra). I had forgotten that it gave the choice of CarHome Ultra OR SVoice.
So, I immediately tried launching Car Mode (and therefore CarHome Ultra), AND independently having my NFC tag programmed to open SVoice prior to launching CarMode (order of operations important, since launching CarMode also triggers DrivingMode ON....but SVoice has to be open already).
I've been using a few days and it works every time. Yay!
-will edit original posts
I just wish that there was an option to turn driving mode on/off automatically when it paired with certain Bluetooth devices.
Eg, when I get in my car the phone will connect to the car's BT, which would then trigger Driving Mode to turn on. When I turn the car off, the BT disconnects which would trigger Driving Mode to turn off.
ajobbins said:
I just wish that there was an option to turn driving mode on/off automatically when it paired with certain Bluetooth devices.
Eg, when I get in my car the phone will connect to the car's BT, which would then trigger Driving Mode to turn on. When I turn the car off, the BT disconnects which would trigger Driving Mode to turn off.
Click to expand...
Click to collapse
For those wondering, there are a few app in the Play store that do just that.
One of them that I've been using during all of this troubleshooting is:
https://play.google.com/store/apps/...=W251bGwsMSwxLDEsImRlLmJ1bGxpbmcuc21zdGFsayJd
SMS, my Car and Me has a whole bunch of settings in it that work well.
If you look at the 'App Screenshots' you'll notice that there's automatic connection settings that will turn things on via this app when connected to a 'specific' BT device. Yay!
I hope this helps.
Smartphone Integration
If you want to integrate your smartphone into any car, 'App Your Car' is the answer.
App Your Car is a small and clever gadget, which, combined with your smartphone, is everything you need.
Our crowdfunding campaign already raised 30% of the needed funds. It would be amazing if you could help us to spread the word to the the community.
Please have a look at our website or campaign:
Website: www [dot] appyourcar [dot] com
Indiegogo: igg [dot] me/at/appyourcar
Before this last week, I was able to connect my Galaxy Nexus (GSM model) to my XPLOD car deck, select BT Audio on the deck, press the button, and receive a voice prompt to make a call. It was very convenient for when I had to make a call while driving.
Some time during this last week, the feature stopped working. When I press the button on the deck to initiate a call, the screen flashes gray (like the background of the voice dialer prompt), then returns to the previous screen and I hear no audio prompt.
When I try to make a call using my Bluetooth headphones (LG HBS700), the phone does the same thing (flashes the Voice Dialer, returns to previous screen--like a force close), but I still hear the prompt and can respond and make a call. But when I try to make a second call, there's no response--no flash of gray, no prompt, nothing.
I installed the TeamSpeak open beta app recently, but thought I had made a call using my car audio deck after. It's worth noting that the TeamSpeak app includes permissions to pair with Bluetooth devices. Unfortunately, even after uninstalling the TeamSpeak app, I still experience the same issue.
I can't think of any other changes I've made that might affect voice dialing and all my searches (the last 45 minutes) don't turn up anything related to my issue.
Could someone here offer a fix or point me in the right direction?
Using the Voice Dialer prompt while driving is a wonderful convenience (and a major safety feature as well) and I really, really, really don't want to have to wipe and reload my phone to get it back.
Okay, so it turns out that a recent (April 3) Google Search update is at fault.
I uninstalled Google Search updates (Settings > Apps > Google Search > Uninstall Updates) and it fixed the issue (though it reverted it to the buggy but less buggy version of Google Search that came installed with my phone).
I had the same issue but nobody chimed in on my thread. At least I know I'm not the only one with Google search update issue with Bluetooth. Thanks for posting your issue. I ended up uninstalling update as you did. I actually ended up going back to stock ROM before I figured out it was search and not the ROM.
Sent from my Galaxy Nexus using xda app-developers app
I've got similar issues. Pressing the button on my earpiece results in the Voice dialer prompt but only through the phone's earpiece and not through the Bluetooth earpiece. Voice commands can only be spoken to through the phone's mic also and not the Bluetooth mic. If you have your phone in your pocket and you shout loud enough, the phone's mic will pick it up and the call will subsequently work through Bluetooth when it connects.
Things were fine before but something screwed it up.
I just tried uninstalling the Google Search/Now update like the OP and it works again. So definitely Google Search/Now is the culprit.
I love Android, but very often I also hate it. Recently I was interested in getting this Bluetooth receiver for my car. The ideal scenario would be to be able to make calls, play songs, and navigate to an address by only pressing the button on this device on my dash and speaking, not touching the phone at all. Sounds great, right? And isn't this what Google Now and its voice actions are all about?
Well, seeing what a sorry state Bluetooth is in on my GNex, I think a device like this would be just about worthless. I have experienced no less than FIVE separate issues in attempting to get this scenario to work with the regular Bluetooth headset I currently own.
1) Bluetooth device disconnects every time I turn screen off. So when I turn screen back on, I have to re-pair the device.
2) The basic functionality of using Google voice actions over Bluetooth at all only works once. After that, it beeps, and then reverts to the handset mic and speaker. If you force stop Google Search, it will work again, but only once.
3) Pressing the button on the Bluetooth device activates old-school voice dialing instead of Google Now voice search. What's the point of this now that Google Now exists? I believe I have fixed this with the Bluetooth Launch app, but we'll have to see if it keeps working.
4) Music quality sucks, as we all know.
5) Google Now voice actions themselves are spotty. Sometimes advertised voice actions just result in regular searches instead. Sometimes it keeps listening for more input even though I've stopped talking, a force stop is required to fix this.
About the only thing that does work over Bluetooth is just regular calls that you initiate via the phone.
Which of the above issues do you experience, and can you share any workarounds? At this point, I honestly don't know what justification Google could give me to use this junk over an iPhone. I seriously believe they do not test anything, and do not care at all about their customers' experiences.
I have my Gnexus running 4.1.2 connected directly to my car's Bluetooth. I use it mostly for music and GPS, then calls sometimes, but rarely Google Now.
1) Doesn't happen to me ever. My phone stays connected until I turn the engine off and pull the key out of the ignition. I heard Bluetooth connection issues started with 4.2, hence why I haven't updated.
2) Not sure about this one. Google Now has always been spotty in my car (takes over 30 seconds to start up) and I'm not sure if it's because of Bluetooth or T-Mobile.
3) I think that's normal. Pushing the call button on my car's steering wheel activates my car's voice recognition system, not the phone's.
4) I use BT most often for music via Pandora and it sounds sounds fine to me. Occasionally there is a subtle skip, which I attribute to the wireless nature of Bluetooth. I would say the quality is 90% compared to wired.
5) Agreed. That seems unrelated to Bluetooth though.
I don't think there is a Bluetooth command for starting Google Now. Don't forget Bluetooth is a generic technology that is supposed to work with all phones, not just Android ones. I used to connect a Sony Ericsson phone for calls.
Except for accepting incoming calls and changing tracks/volume, I still have to initiate most actions by touching my phone. It sucks. Let me know if you find a good solution.
Sent from my Transformer TF101
Yeah, it seems at least some of these issues (the disconnecting, music quality) started in 4.2. #3 might be "normal", but is definitely not how it should be. You mention Bluetooth is a generic technology - this is true, but there doesn't need to be a special command for Google Now, the phone can just choose to respond however it wants to the standard "call" button/command. For example, with an iPhone, pressing the button on the Bluetooth device will activate Siri. Then you can speak any command or query you wish. There's no reason Android couldn't activate Google Now voice search in the same way, instead of the voice dialer.
I've been doing things same as you, doing everything via the phone except for answering calls or redialing the last number. I finally realized how useful voice commands could be when able to be summoned via Bluetooth. A couple simple updates to the Google Search app, and an improved Bluetooth situation in 4.3 could easily clear all this up. But after the many mistakes they've made, I'm not exactly holding out hope.
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Sent from my Galaxy Nexus using xda app-developers app
tshelby73 said:
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah....all the issues I stated above are with that option checked.
xdp said:
Yeah, it seems at least some of these issues (the disconnecting, music quality) started in 4.2. #3 might be "normal", but is definitely not how it should be. You mention Bluetooth is a generic technology - this is true, but there doesn't need to be a special command for Google Now, the phone can just choose to respond however it wants to the standard "call" button/command. For example, with an iPhone, pressing the button on the Bluetooth device will activate Siri. Then you can speak any command or query you wish. There's no reason Android couldn't activate Google Now voice search in the same way, instead of the voice dialer.
Click to expand...
Click to collapse
Ah yeah, that's different then. None of the buttons on my car will activate any sort of voice recognition on my phone, because of the voice system in the car itself. Which sucks, because although it may have been advanced in 2009, smartphone voice tech has surpassed it by leaps and bounds, whereas my car software will never get updated.
So I think there's a better chance for an update to make this work for your setup than mine.
Sent from my Transformer TF101
tshelby73 said:
The newest Google search has an option to listen over Bluetooth in settings not sure what it does.
Click to expand...
Click to collapse
Thanks for the tip!
I also added a Google now voice command short cut to my lock screen and launcher, so when I'm in the car I can quickly (hopefully) say a command.
Kind of sucks still that the call button doesn't do this, even my old school slider Nokia launched voice commands over Bluetooth.
LOL
I use mine and will do voice commands by pressing button. It will not search though just make calls. On CM based ROM'si have to freeze the voice dialer the ROM comes with or the cm dialer is default. I don't have the listen over Bluetooth checked. Maybe that checked would give me search feature using button.
Sent from my Galaxy Nexus using xda app-developers app
I've been having issues with my S3 (sprint) for a little while now. Most of the time it's no big deal, but now that I want to play with Tasker AutoVoice, utter!, and voice commands in general, it's growing. I am running the 8/13 nightly of CM 10.1, but the issue has been going for a while now.
Here be the problems.
First, if I make a call, I have to use the speaker phone to be able to hear, the ear piece and mic don't seem to work quite right. BUT, if I get a call, there isn't a problem. Headphones with an inline mic work perfectly though.
Second, I cannot use the voice comands, Google Now, AutoVoice, or the like and I have ben talking directly into/at the microphone on the bottom of the phone. The phone doesn't register like it should, where the microphone flashes and shows that it "hears" you. The Google Sound Search lockscreen widget wil occassionally pick up sounds to identify the song, but that's hit or miss.
Third, the speaker doesn't work for media. YouTube, Play Music, what have you doesn't play from the speaker on the device. Well, I take that back, it has once, but only once. Headphones work perfectly though.
Now, I got my S3 from Best Buy and this is actually a replacement, and things worked out of the box. I don't know if it is a refurbished unit (my guess is that it is), so that could have something to do with it too. I'm tending to lean towards a software issue, maybe I just need to flash something to get those issues resolved? Any help I can get to resolve this, that would be awesome. I'd like to get it fixed rather than replaced as it takes forever to get a replacement, but I haven't removed that option. Thanks in advance and I'll try my best to offer up any and all information I can.
I have a Plantronics BT headset that I've been using for years.
It has a "main button" that, when long-pressed, starts a voice dialing dialog with the phone, even when the phone is locked.
Or it did, from the original Captivate running Froyo all the way to my Kit-Kat GS3.
This no longer works on the G4. I get the beep indicating that the long press was registered by the headset, but nothing happens on the phone.
I know I can use "OK Google" to call Google's Voice Search and then tell it to dial, but that only works when the phone is unlocked and the screen is on, which defeats the whole point of hands-free operation.
LG's Voice Mate simply sucks, at least through my Plantronics. It doesn't capture voice input, it interrupts it half a second after it starts listening... It is unusable.
Does anyone have an idea how to enable the good old voice dialing through a BT headset? OK, it was ugly and idiotic with its stupid "Select 1 for mobile..." prompts, but it worked.
It doesn't have to be that. As long as I can voice-initiate a call without fiddling with the phone, I'll be happy.
The G4 turned out to be a great phone, but this particular issue is irritating to me.
I have the same problem with my company-issued Rugby Pro running Jelly Bean. Samsung's S Voice is hit-and mainly miss. My old Rugby II flip was always ready to dial or answer if Bluetooth was on. I use it on a motorcycle, so no button pressing on the phone is possible. I have been trying utter! (still in Beta) the last few days, and it is the most promising that I've found, although it has way too many other things it tries to do. Otherwise, I'll have to try and swap this phone with someone for a i(don't even want to start using these)phone, or go back to the flip and just carry the Pro for use via wifi to get company email.
Voicemate is garbage.
Go into apps under settings and disable as many Voicemate related items as possible.
This will cripple Voicemate and Google voice search will launch on Bluetooth press. It works beautifully.
All the commands I've tried work. One of my favorites is "play <song name>" if you have Google music all access.
http://www.greenbot.com/article/2359684/a-list-of-all-the-ok-google-voice-commands.html
Sent from my LG-H810 using XDA Free mobile app