my friend has an xda II & he bought a Jabra 250 BT headset, he have no idea how to use it & moreover i never had BT in any of my phones so both are ignorant regarding BT, now he asked me a question, "How can i dial a contact from my Headset without the use of the phone, is their any SW i need to use?" i tiold him, i have no idea but i will forward his question to this forum, so could someone answer this question pleaaaaaase ?
the point is the right BT profile ... the headset profile doesn't work except during a phone call ... what you need is a "hands free" profile which will deal with all types of system "sounds" ... then you can use MS voice commands s/w ... however, I didn't try this myself, but in theory it should work
I have this combination. I've not checked the groups recently but from personal experience you cannot dial from the headset with the exception of a bolt-on (name escapes me) that will allow you to use the headset button to redial the last number.
I also have Microsoft voice thingy which works well but you need to initiate the call from the pda and then switch it over to the headset once connected. This little bolt on does manage the operation of the bluetooth radio and disables it to save battery after one minute. If you want to initiate a call like this then it is best to kick the bluetooth off first otherwise there is a delay before the headset links up and the person you just called is left hanging around whilst you frantically try to transfer the call to the headset!
Having said that and with all its limitations the two do work well together. One thing I did do based on various comments on this web site was to update my firmware to latest version.
Hope this helps
Anybody have any hints for using voice recognition with a headset? It knows I'm trying to talk to it, but it doesn't seem to know what I'm saying so it keeps telling me to try again instead of dialing.
I've been experimenting and if I use the Voice Search application on the phone everything appears to work except that somehow sound coming and going is completely cut off.
Voice Dialer doesn't work with the headset or without.
I can use Voice Search to place the call and then turn on my headset and switch over, but I get an error on the screen that the communication app has failed. The error being on screen doesn't interfere with the call though.
Odd effect is that the volume control buttons got stuck on bluetooth in-call volume. I had to restart the phone to clear it.
I assume you are referring to voice dialing from a bluetooth headset. As far as I can tell from reading the forums it never worked but has been fixed in the new 351 update (Android 2.2.2). It didnt work for me on the 318 build but now does on the 351 build. I dont believe voice search works from a bluetooth headset though as far as I know.
mid_life_crisis said:
Anybody have any hints for using voice recognition with a headset? It knows I'm trying to talk to it, but it doesn't seem to know what I'm saying so it keeps telling me to try again instead of dialing.
I've been experimenting and if I use the Voice Search application on the phone everything appears to work except that somehow sound coming and going is completely cut off.
Voice Dialer doesn't work with the headset or without.
I can use Voice Search to place the call and then turn on my headset and switch over, but I get an error on the screen that the communication app has failed. The error being on screen doesn't interfere with the call though.
Odd effect is that the volume control buttons got stuck on bluetooth in-call volume. I had to restart the phone to clear it.
Click to expand...
Click to collapse
i use cyberon voice speed dial, it works but u have to shout loud the names
tried with different bt headsets
I'm hoping someone here has some *real* ideas or answers regarding this issue.
I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS “locked” I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system… are we back in the smartphone dark ages?? I might as well take up texting and driving while I’m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is “locked” it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don’t need these draconian measures this is just plain stupid and potentially unsafe.
I've already rooted my phone. I've tried other ROMs like the latest builds of UnNamed, ICS'd Out, and CyanogenMod. None of these allow Bluetooth operation while the phone is locked (and in fact all of them introduced other issues). I've searched the forums but most similar posts go unanswered or contain nonconstructive replies (flames, unrealistic answers, etc).
I can't and won't disable ALL security. I won't give up making phone calls while driving - I'm on the road a decent amount and need to use that time productively. What are my other choices? Go buy an iPhone or a Windows Mobile unit which work "right"?? Seems like a crazy oversight by Google/Samsung/AT&T if those are my only options!
I would suggest using the official samsung Car dock, as the USB port on there has a special impedance that tells the phone to go into driving mode, which once you unlock the phone, it stays unlocked until you either lock it, or take it off the dock. It also charges your phone at the same time. However if you have a case, this will not work for you. You would need to solder up your own usb plug that has a certain impedance over some pins (theres a thread somewhere about that, its like a jig, but with different impedance) and just plug that in when you're driving, but you still have to unlock the phone at least once with it plugged in.
My clarion cz500 car stereo has no issues making or receiving calls via Bluetooth while my phone is locked.
Sent from my GT-I9100 using xda premium
My biggest gripe with Android is that BT calling does not work as well as it did with WinMo's Voice Command (which works really well considering how poorly much of WinMo worked). Initiating calls via BT is my main gripe with Android. I wish Google would get it right already. That said, I have no problems answering calls via BT even when the phone is locked.
My phone is paired with the built-in BT in my car and I have no issue with making/taking calls while the phone is locked. Maybe its a compatibility issue with your particular hands-free device?
I also have no BT problem when locked, using the standard BT in my Toyota Avalon, 2011. Running rooted, UnNamed ROM, Entropy's DD 120811 kernel.
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Miami_Son said:
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Click to expand...
Click to collapse
Sgs2 does this stock with no problems via samsung/vlingo voice command app. Seems hit or miss on some custom roms. As long as device has bt turned on and had been prior paired with a headset, just have to turn headset on then hit the button on the headset. Voice prompts over headset ensue
Sent from my SGH-I777 using XDA App
I'm headed into the AT&T store tomorrow to do some definitive tests but so far I'm skeptical people who say it's working for them truly have their phone locked. The Bluetooth unit in question is a Parrot CK3100 LCD - a bit dated (3 years old) but it works flawlessly with several WinMo phones, several non smartphones (mostly Nokia's), and we just tried a friend's iPhone 3GS and iPhone 4. In all cases phonebook and voice dialing not only worked excellently it worked when the phones were truly locked and the screen off.
On the other hand the 3 Android devices I've tried all have the same problem - they won't dial out either by phone book entry or voice recognition unless you unlock the device first. The 3 devices are: Samsung Galaxy S II (AT&T), Samsung Galaxy S (Verizon), and EVO 3D (T-Mobile).
Unfortunately I don't have any other Bluetooth headsets to try out, hence my planned trip to AT&T. I plan on walking out of their either with a Bluetooth device that works or an iPhone Thanks for the replies.
I hear you. I have a Motorola FINITI bluetooth headset and it will not voice dial with the screen locked on my AT&T Galaxy SII.
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Some roms give you a quick toggle in your status bar called secure mode, this should do it.
I'm on villain rom with jaykay mod quick toggles and i have that options.
Sent from my GT-I9100 using xda premium
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
GeorgeP said:
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
Click to expand...
Click to collapse
Are you using a pattern/pin lock? Or just the slide to unlock.
Just slide to unlock.
It works very well and very straightforward. I just press and hold the call button on my headset (while the phone is locked), and then after the tone say, "call John Doe on mobile" and it works.
Something for OP to consider in troubleshooting why he is unable get this work:
The BT voice dial works through the older pre-installed Vlingo (version 2.x). Even though I have the newer version (3) of Vlingo installed, the phone still launches the older preinstalled version of Vlingo for BT voice dial. So it seems the BT voice dial function is in some way hardcoded to that version of Vlingo.
Perhaps OP is using a custom ROM in which the older pre-installed Vlingo is removed(?). I know that is the case with some of the custom ROMs for the Int'l SGS2.
If I were to freeze or remove the older version of Vlingo, that might impact BT voice dial. Although I wouldn't expect it to affect the use of my phone through my car's build in BT.
Try it with a pattern lock or some kind, I believe that is what the OP has and its what "locks" the phone from using BT dialing, whether its voice based, or address book based from a headunit.
OK, if OP means that type of lock, then, no you cannot make a call when locked.
Although, it is not clear to me why one would want BT to bypass the lock in this manner. It seems the PIN or pattern lock would be pointless. If the phone is stolen (or lost) the person who stole it (or found it) could have access to your phone's contents through bluetooth. Am I missing something?
Definitely missing something. He wants the phone to be able to make calls while the phone is locked which is why i suggested to keep it unlocked by enabling driving mode through the mount.
My point was that allowing bypassing the lock through BT creates a exposure many would not want. The simplest solution might be keeping it unlocked either using a mount as you suggest, or using one of the profile apps that lets you create a profile to keep the phone unlocked when plugged in. He could then plug it into the car power adapter.
I use a pattern lock, and can make calls through the built-in BT in my car when the phone is locked. I can dial on the car's touch screen (disabled when the car is in motion, except for pre-set speed dials), or tell it to call someone by pressing a button on the steering wheel and saying the name. The car BT compares the spoken name with the list of contacts from my phone that have been BT-loaded into the car's contact list. Nevertheless,the call is made though the phone, since the vehicle BT is not itself a phone. Has anyone noticed that we have not heard again from Rajah, the originator of this thread? Rajah, are you there? Were your issues resolved?
I'm not sure what's causing this. It seems to have started when I first rooted the phone. Voice recognition isn't working. When I try to use google search the circle around the microphone icon will move, but the icon doesn't turn red as it does when it recognizes voice. If I cup my hands around the microphone on the phone and pretty much yell, sometimes I can get it to work. Other times I can't. Tried another test, downloaded a voice recording app and when I recorded, I could hear my voice but it was INCREDIBLY quiet. I couldn't make out what I was saying at full volume. I have had no complaints about my voice when on phone calls. Does anyone have any idea what this is, or what a fix would be? I'm rooted currently, have tried multiple different roms with the same outcome. Am I just missing a setting somewhere?
When I make a call the phone almost freezes but does make the call after several seconds. But then there is no audio, I can't hear the other person and they can't hear me. When someone calls me sometimes it takes so long for my S5 to answer that it goes to voicemail. When the phone does answer, there is no audio either way and the phone is extremely slow to end the call and close the dialer app.
The sim card works fine in other phones.
Alternate dialer apps do the same thing.
I get the same results on several different roms/android versions including Nougat, Marshmallow, Kit Kat.
Every other function of the phone works great (LTE, Text, audio, etc..).
I've completely wiped the phone several times trying different roms, etc..
Does anyone have any suggestions for a fix?
replace motherboard and speaker