I've tested two Voice to SMS Apps (Text By Voice, and Voice Text). The latter uses Google Voice Search for speech recognition. When I have a hands free bluetooth kit in my car connected, both apps listen through the microphone in the phone, not the hands free mic.
Someone in another forum mentioned the BtMono App (not sure why) and in the description for the app it states "Please note - microphone routing is not possible on Samsung phones and may not be possible on GSM phones" ???
So it seems this is a firmware limitation of the S3?!? That's is very disappointing. With all the talk about being safe while driving, I can't believe an app can't be used to do voice to sms via the remote hands free mic. Even more bizarre is I've seen no one else mention this!? I can't believe I'm one of a few that has tried to achieve this?
...finally found a thread about this...
https://code.google.com/p/android/issues/detail?id=34348
Related
My Hermes has never fully integrated with my Ford Focus BT Handsfree kit. Although I could always make and receive calls, it rarely read the Contacts on my Hermes and, when I scrolled to the Contacts on the car hifi, it would say Phonebook Not Available. On those occasions when it would read the Contacts, when I had an incoming call, it would indicate the number of the caller, but not the name. Once the call was answered, it would sometimes deign to show me the name.
The break through came when I flashed the PDACornerProV17 ROM. This must have a new BT utility. As soon as I had paired my Hermes, I got a pop up on the phone saying "Ford Audio wants access to your contacts. Do you accept this? Y/N". I have never had this before and, as soon as I tapped Yes, my contacts appeared on the car hifi. Now, when i receive an incoming call, I can see the name before I answer it, not after! Additionally, the car kit keeps a log of incoming and outgoing calls, another first.
So, if any of you have a Ford BT kit, and haven't got it to work properly, flash the PDA Corner ROM.
thanks for your report and recomendation also.
glad to know this info
thanks and regards...
By ford bluetooth kit, do you mean the Sync found in the focus/Fusion?
This works on my ROM with Pioneer BT stereos too...
jblakk said:
By ford bluetooth kit, do you mean the Sync found in the focus/Fusion?
Click to expand...
Click to collapse
I mean the built-in bluetooth kit, found in all recent UK Ford cars. It is a factory-fitted addition to the normal car audio, giving hands free phone functions and limited voice commands.
is that the BT Phonebook Access Profile (not SIM AP)?
stan23 said:
is that the BT Phonebook Access Profile (not SIM AP)?
Click to expand...
Click to collapse
Sorry, don't know the answer to that. But, if this is a new tool introduced into ROMs, this might explain why I got the message 'Ford Audio is trying to access your phonebook', and why the Hermes contact list is much more accessible through the car hifi.
from what i remember theres these other bluetooth modes, one for sms one for phone book and one other one referred to as profiles
the new roms must have this enabled but not full functionality of new email and sms from the phone i remember a friend saying something about 6.1 has this enabled where as before people needed an app to do it with the first 6 releases?? can someone confirm if this is correct ?
So I just bought a new car, and while hooking my dinc up via Bluetooth I noticed that I cant call out from my phone because I have it set to ask every time I make a call if I want to use Google voice...it gets stuck on that screen and fails to make the call.
Is there a way to prevent the Google voice app from asking when calling out via Bluetooth?
Anyone? I could have sworn it worked Thursday when I picked the car up, that's the weird thing...
I'm not sure exactly where it is but there is an option in the settings somewhere that dictates how Google voice handles calls. It can be set to use Google voice, not use it, or ask.
k_nivesout said:
I'm not sure exactly where it is but there is an option in the settings somewhere that dictates how Google voice handles calls. It can be set to use Google voice, not use it, or ask.
Click to expand...
Click to collapse
I think that's for international calls. But, you phone might be dialing an international prefix before the number. That normally wouldn't matter, but Gvoice will take notice of it. I set mine to never ask because I never call internationally.
Ah yeah, I think loonatik is right. So if you do have 1+ before the number, GV will probably pick that up and that might be what's giving you troubles. Maybe?
No, I have it set to always ask...but I was hoping there was some way to override it if the call is made via Bluetooth. I could have sworn I had it working Thursday, but now it just fails because it gets stuck on the Google voice screen ...
Anyone know of any way to override the setting if making a call thru Bluetooth?
Or, an alternative would be for me to turn it off (or on) for all calls and have an easy way to bypass it...
Possible solutions...
Free, but a pain in the butt:
Drop the Google Voice Settings widget on one of your home screens. The third button (the one that looks like a handset inside of a settings button) toggles call modes for GV:
-Use for all calls
-Do not use
-Use for international
-Ask every time
Free, but I have never tried the app so I can't personally comment:
http://www.androidzoom.com/android_applications/communication/google-voice-callback-free_fpin.html
Looks like you could set this up to perhaps side-step the GV behavior of manually answering every time
I was about to write out how to do it with Tasker and the Locale Google Voice Settings plug-in. But I just realized that it doesn't have the all/none/ask choice as a plug-in setting: only the online stuff like forwarding phones, etc. Bummer - but maybe you could contact the dev about future integration
Google Voice always ask and bluetooth
Did you ever find a good work-around or solution for this?
I just got an S4 today, and I was hoping that the Google Voice app on the Android would be similar to the iPhone one. It's not.
I use google voice to call/text my friends (I ported my original # over to Google) and the main number for work. But when I tried making a call over bluetooth in the car, got the same problem as you, it got stuck on the "Always Ask" prompt. The problem with making it never ask, is there is no dialer to just go to like there is on an iPhone when you do want to make a call using Google Voice. So you have to keep switching the option on that widget before every call. So annoying.
Suggestions?
PLEASE, help me. I've looked around and only found a couple of post within threads that specifically target these two issues. Most people are concerned about voice dialing over bluetooth which is answered by several apps, Voice Command included. But, I'm pretty sure a lot of people have been frustrated by or are curious about this:
It seems REALLY dumb of Samsung to disable or remove the ability for bluetooth voice input in stock apps. I know there's Voice Command, but I have 2 problems with that - 1. it just kinda totally sucks, IMHO; 2. If you launch something like Google Navigation, but it or you get the address wrong, you cannot use voice commands to input the new address within the application, you have to back out an try again. If I tell it to navigate to "Alewife Station" and Navigation comes back with a list of wrong guesses, I have to back out. Also, no voice-to-text once you are in your messaging app. It's fine for the initial message out, but not your reply if the app is open. No 3rd party voice assistant apps. No Google search outside of Voice Command. Essentially, no bluetooth voice input outside of their precious little app that is not as all inclusive as they'd like to make it seem.
My second gripe is using the audio out for only media/notifications, but not phone calls. The audio quality is markedly better when using the audio out on the car dock verses an FM transmitter, especially in the city where it's hard to find an open frequency. But if I receive a phone call while docked the audio switches to the phone's speakerphone. And even with a bluetooth paired it takes the input from the phone (the mic is blocked by the dock) WTF?! So I have to dismount my phone (which is illegal in some states) or fumble through the menus to turn off the audio out setting, then switch my radio to FM and hope I'm in a clear area, just to take/make a call? So much for 'eyes on the road'.
These two decisions seem counter intuitive and odd oversights for a flagship smartphone.
ANY suggestions or solutions are welcome. If you'd like to build an app to address one or both of these issues, I'll test it all day on my phone (that's why I pay $8/month for insurance) and support your development time. I'm sure many, many people would be happy to have this function.
Sorry about the rant, but the fact that this is not a standard function irks me.
I agree. I hate the voice command bull. It never calls the correct person. I say call Ted and it calls pat. I hate that program. And as far as I could tell the only way to get rid of it is if you rename another app and push it to the System folder.
I just want Google voice search over Bluetooth.
No ideas? Please? Anyone?
There's been quite a few posts on this forum pointing out that the Jellybean bluetooth voice dialler is broken.
For those who don't use bluetooth, this is a separate app that pops up when you press the dial button on a bluetooth headset or in a car.
Although it is a separate app to voice search it seems to use the technology and has been updated for JB.
For some people it works, for others it doesn't work.
In the cases where it doesn't work, reverting to ICS or installing a 3rd party dialer fixes the problem.
In my case it seems to really like a small sub-group of contacts and seems to select them no matter what I say into the mic.
Unfortunately installing a 3rd party dialer means google Now/voice search must be completely disabled.
Plus, there are reports that some of the 3rd party apps will not use the headset mic, but instead use the phone mic which makes them useless.
Anyway, I'm wondering if anybody who knows about ROM modding could tell me whether it is possible to make a mod to either:
1. Revert to ICS bluetooth/voice dialler, but keep google now/voice search when not using bluetooth.
2. Allow custom bluetooth/voice dialler to be selected (currently not allowed unless google now/voice searchis completely disabled).
3. Pre-install some other 3rd party bluetooth/voice dialler.
Thanks.
nlemoz said:
There's been quite a few posts on this forum pointing out that the Jellybean bluetooth voice dialler is broken.
For those who don't use bluetooth, this is a separate app that pops up when you press the dial button on a bluetooth headset or in a car.
Although it is a separate app to voice search it seems to use the technology and has been updated for JB.
For some people it works, for others it doesn't work.
In the cases where it doesn't work, reverting to ICS or installing a 3rd party dialer fixes the problem.
In my case it seems to really like a small sub-group of contacts and seems to select them no matter what I say into the mic.
Unfortunately installing a 3rd party dialer means google Now/voice search must be completely disabled.
Plus, there are reports that some of the 3rd party apps will not use the headset mic, but instead use the phone mic which makes them useless.
Anyway, I'm wondering if anybody who knows about ROM modding could tell me whether it is possible to make a mod to either:
1. Revert to ICS bluetooth/voice dialler, but keep google now/voice search when not using bluetooth.
2. Allow custom bluetooth/voice dialler to be selected (currently not allowed unless google now/voice searchis completely disabled).
3. Pre-install some other 3rd party bluetooth/voice dialler.
Thanks.
Click to expand...
Click to collapse
I agree...it's a must have. I am a heavy user of my car bluetooth and keep my nexus paired all the time. after my upgrade to JB, this feature seems to more or less broken and only dial few of my contacts. I need to search my phonebook using the car system buttons, which is not at all convenient in heavy traffic situations.
There seems to be no other option then to revert back to ICS till voice dialing is fixed by the devs.
Like others, I absolutely depend on the voice dialing to work correctly as I use it in two different vehicles with bluetooth head units. At this point I'm willing to sacrifice any other Now/voice search stuff - so what voice dialer is everyone using?
I only see a few listed in the play store and none seem like the obvious winning choice due to limitations stated in the reviews. My simple requirements:
1) voice dial from names in my contact list.
2) be able to deal with name homophones. For example JB/Google voice search cannot dial my wife because it searches contacts for "Kimberly", but her contact is spelled "Kimberley". I'm not about to edit the spelling on the multiple contacts where this is a problem, especially since ICS, Gingerbread, and even my ancient Blackberry 8100 all handled this fine in stock form.
Here's the issue: I have a N7 2013 LTE which I've unlocked/rooted. I've enabled SMS and installed the Google Dialer. Everything works well; I can send/receive SIP calls via the dialer and I can even answer calls with my Bluetooth headset because the SIP calls received by the Google dialer are perceived as actual phone calls by Android.
This falls apart when I want to use a third-party SIP/VoIP app. I can answer native SIP calls with my Bluetooth headset (a double-tap on the headset for the Jawbone ERA), but can't do so with a third-party app. I'm guessing that's because calls answered by the Google dialer are seen as real phone calls whereas those answered by a third-party app are media events, so the Bluetooth headset isn't notified of an incoming call. This even happens with CSipSimple set to integrate with the native dialer.
CSipSimple is a great app, but it suffers the fate of any app when left in memory too long: it gets kicked out. I can watch the SIP registration status at my SIP provider's website while CSipSimple is running in the background. CSipSimple stays registered for a while, then the status switches to disconnected. If I disable CSipSimple, the native dialer registers with my SIP provider and stays registered.
Can anyone confirm or deny any of this? Is there a way to have a third-party SIP/VoIP app act like the Google dialer? Or am I stuck with the native dialer?
Huh. Currently 117 views and nobody has an answer.
The Google dialer is fine, albeit a bit ugly, but it doesn't do landscape amongst other things. It would be great if I could replace it with CSipSimple or one of the many other SIP apps out there. I know I can use any app I like, but the issues in my first post preclude me from doing that. The native dialer stays registered with my SIP provider at all times. It also works well with my Bluetooth headset, allowing me to answer calls without having to touch my N7.
Anyone?