Related
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
I think I found a fix for the BT Hands Free not working the way it should.. I can even use call waiting now and it does not kill the mic when I switch back to the first call..
I set the phone settings to automatically pick up after one ring.. No, it will not automatically pick up after one ring but, now I am getting the name to display in the caller ID field of my xLive mp3-BT headset. and it is working consistently.. I HAVE NEVER gotten it to work consistently before.. NEVER. i will try it with my Jabra BT800 later too.
I think it makes a "deeper" or better connection by making the phone try and make the BT headset device automatically answer???
I am using 2.20 OS and it is the only one that I have found to work, (not fully but it does work BETTER), please try this with other Hands Free devices like car kits and HBH660 etc.. Also try this with 2.02 and 2.06
ccrrazzzy said:
I think I found a fix for the BT Hands Free not working the way it should.. I can even use call waiting now and it does not kill the mic when I switch back to the first call..
I set the phone settings to automatically pick up after one ring.. No, it will not automatically pick up after one ring but, now I am getting the name to display in the caller ID field of my xLive mp3-BT headset. and it is working consistently.. I HAVE NEVER gotten it to work consistently before.. NEVER. i will try it with my Jabra BT800 later too.
I think it makes a "deeper" or better connection by making the phone try and make the BT headset device automatically answer???
I am using 2.20 OS and it is the only one that I have found to work, (not fully but it does work BETTER), please try this with other Hands Free devices like car kits and HBH660 etc.. Also try this with 2.02 and 2.06
Click to expand...
Click to collapse
umm. a bit confusing. care to rephrase.
In depth
With 2.02 or 2.06 or the Sin's merged OS, ANY BT headset device or car kit device that needs to use the Hands Free profile, the mic does not work on the device and there is sound that comes out of the XDAII speaker and only the mic on the XDAII works.
People can not hear you when the only mic that is working is on your phone..
Now on the 2.20 translated OS, Hands Free profile does work BETTER. It does not work fully! The caller ID is not displayed right all the time and the most frustrating part is, when the phone receives a call on call waiting, you can switch over to the other call BUT when you switch back, it acts like 2.20-2.06 and the mic only works on the phone, not on the BT device and both the speakers are going giving you a "stereo" affect.
Well, why not just use the Headset Profile you ask???
I LOVE the ability to be able to scroll through my recent call list, see who is calling via the small caller ID display on my BT device and make phone calls... ALL without having to open up my PDA case or look around for my briefcase and find my XDAII.
I have all the power of a regular phone on my ear or around my neck.
BT devices that need to use Hands Free profile are ones like the BT800
http://www.expansys.com/product.asp?code=BT800
or The HBH 660
http://www.expansys.com/product.asp?code=114271
or the new one that has not been released with the only difference of it has a battery life display too.
http://www.expansys.com/product.asp?code=118678
xLive
do a search at http://www.expansys.com/ for xlive.
The xLive MP3 player - Hands Free phone device also allows me to punch in the numbers with the little joy stick and make a call. (It has other bugs though. Wait until a newer version than 1.23c comes out. They still have the old version listed. http://www.alfa-tech.com.hk/index_download.html )
Other devices that require Hands Free profile, are devices like Car Kits..
They require Hands Free profile so the caller ID is displayed and and other more robust feature can be activated.
Headset profile does not support caller ID nor other more powerful features.
My fix...
With the Hands Free profile, and setting the phone to auto answer after one ring, the caller ID is displayed with the name if it is in your contacts AND most importantly, the duel speaker and only mic on the XDAII thing does not happen when you receive another call and switch back to the original call. :lol: :wink:
Hello,
I have stumbled upon the BT problem also, and am having problems since then. I installed BT Tools, and removed the handsfree setting, but still a lot of problems.
I was quite happy seeing your post, so i Removed BT Tools, paired my HBH-660, and used your "fix".
Obervations:
When pairing, the ppc asks to set the headset as handsfree devide, and twice to set is as headset. When clicking Yes for the three, my PPC
does the following: When set not to auto-answer, the phone number is displayed on my headset, when answering, the stereo and mike effect appears.
When set to auto-answer, the phone number is displayed once, when clicking to answer the call on the headset the headset stops, the handsfree icon dissapears on the ppc, the headset icon appears, and a normal conversation is possible, without stereo and mike effect.
When i only select handsfree pofile when pairing, the stereo and mike effect appear with and without auto-answer.
I also never get the name in the display, only the phone number, eventhough the name appears on the PPC, is this a setting somehwere, or just my headset (HBH-660)
Conclusion
What OS are you using?
I am assuming 2.02 or 2.06 with the registry hkey local M, software, Microsoft, Bluetooth, "HandsfreeProfileOn"
On my Jabra BT800, I still only receive a phone number if I do not have their number in the PPC call history or as long as it is not in my Contacts too.. IE.. It only displays if it is a brand new number.
On the Xlive, it displays the number or the name, no matter what.. Well that is until the xLive times out.. Now do not go out and buy one yet, my version 1.23c is the newest OS but it needs an update. It only works for about 10 min and then you have to turn it off and back on and push the BT button 2 times and then it will work again for another 10 min!!!! :evil: :? This also happens on my wife's MPX300 with the latest ROM so it is not a problem with the XDAII software.
Bottom line = With the 2.20 OS and my "fix", The stereo affect is gone on all of my devices.. ANYCOM HS-880, Jabra BT800, Xlive XBM-100, Motorola HS810 and some other Motorola BT headset that has a AAA battery in it..
(Yes, I have bought a lot of them.. I loose things and I was hoping they would work.) :roll:
Now about your 2.02 or 2.06 OS, When you said, "When set to auto-answer, the phone number is displayed once, when clicking to answer the call on the headset the headset stops, the handsfree icon dissapears on the ppc, the headset icon appears, and a normal conversation is possible, without stereo and mike effect. " I would like to know what happens when you set it to answer on 2 or 3 rings, maybe it will display the caller ID longer. Also, I would like to know if the stereo affect comes back when you get another call on call waiting.
I tried it in version 2.06 and it does not work. It can connect the bt earpieces, but no sound. It kills the connection with the original MS bt stack as well.
I believe the OS you are using is 2.20, just wonder is it a Simplified Chinese OS ?
adad said:
I tried it in version 2.06 and it does not work. It can connect the bt earpieces, but no sound. It kills the connection with the original MS bt stack as well.
I believe the OS you are using is 2.20, just wonder is it a Simplified Chinese OS ?
Click to expand...
Click to collapse
If you use OS 2.20 the problem is gone. During pairing select ONLY the first time is asks for Handsfree/headset. Discard the second time. (I Don't know why exactly)
Be aware that no matter how "simple" a headset looks, they have their own set of problems by themselves, not only XDA-II related.
And BT specs for protocol 1.2 is already out there....
:?
Man!!!! I do not know what is up now! :x :? :shock: :evil: :twisted:
On my BT800, I have tried setting it to No Auto Answer, un paring, re pairing with Selecting Yes to Serial, AND YES to both Handsfree/Headset prompts and I can not get it to mess up when another call comes in.
I have tried Selecting Cancel to Serial, Yes to the first Handsfree/Headset prompt and No to the second.. Still no problems.
I have tried only selecting the second Handsfree/Headset prompt and still no problem..
Now, remember, the BT800 sucks! The caller ID is not working BUT that is a Jabra BT800 issue.. It just sucks! Same problem with no caller ID on my wife's MPX300.
The only thing that I can see as my problem was I used to have BT Tools installed and I never could get it uninstalled all the way until I renamed the bthserial.dll. So, I am assuming that BT Tools also had it's own DLL for Headset too???!! Thus that was my problem? I guess.
So, my "fix" is wrong.. I take it back. It makes no difference!
I am sorry.
Looking Glass said:
If you use OS 2.20 the problem is gone. During pairing select ONLY the first time is asks for Handsfree/headset. Discard the second time. (I Don't know why exactly)
:?
Click to expand...
Click to collapse
I noticed NO difference on BT800, or my ANYCOM 880, or from my two Motorola ones.. I do not know if it makes a difference on other devices.
Looking Glass said:
And BT specs for protocol 1.2 is already out there....
:?
Click to expand...
Click to collapse
Could you explain more please?
On my xLive it only has one BT Handsfree/Headset prompt but on the xLive, it lets you select the pairing mode... Hands Free or Headset.
It ALSO has excellent caller ID display! When I may have had a Partial BT Tools installed, I only got caller ID. Now, I get the name too if it is in my contacts list!
I also found out how to use the xLive without all the problems!!!
It took me about 2 hours to do this..
BT headsets...
It looks like the other devices with caller ID on them, HBH-660 and the HBH-220 do not work great and I know for SURE the Jabra BT800 is crap.. (even in Headset Mode it takes up to 9 seconds to answer a call.. In Hands Free mode, it is only 2 seconds but the caller ID does not work)
So, the ONLY solution for those who want caller ID on a handy little device is, the xLive.
I recommend the xLive now. I found that the xLive will screw up if you press certain buttons or for other reasons explained below and if you do not press them or do the other things, it works fine.
I am not sure if People can get A2DP to work on the XDAII, I have seen most say they can't, SO, the next best thing is the xLive! It also supports caller ID and will list the Callers Name if it is in your contact list AND you can DIAL phone numbers with it, all while your XDAII is 30 feet away. You can dial numbers with it through pressing the BT button, selecting "Dial" and using the little joystick to select the numbers and then press the BT button again to dial!
xLive also supports MP3 streaming though a program the give you and a your typical BT device hooked up to your PC. I have one that only cost $39 and it works for about 150 feet. You can get past it's memory limit this way.
How to use the xLive with an XDAII with 2.20 translated ROM.
1. Pair it using “Hands Free” mode, selecting “Pairing Clean”, once, (you do not have to repair again)
2. When you FIRST turn the xLive ON or if you are unable to make call through it or get calls through it, press the Bottom Right Button for 2 seconds to turn it off. Then Turn it back on with the same button. Then Press the BT button on the front left, next to the screen, wait 4 seconds, press it again and wait 6 or 7 seconds until the little BT icon appears then press the Top Left button (A-B and Record, AKA cancel)
3. Never hang up a phone call using BT button! ONLY USE THE “END CALL” function of your phone or wait until the other person has hanged up. If you press it, redo step 2! (the BT button is the one on the left of the screen)
Problems that will cause you to have to turn it Off and then back ON again,,, IE. Repeat step 2.
You can ONLY reject ONE phone call.. After you do, go redo step 2
If you Miss a call, go redo step 2!
If you reboot the XDAII or the two get out of range of each other, you only need to press the BT button and then press the Cancel button after the BT icon appears again.
http://www.expansys-usa.com/product.asp?code=111023 128 $82.95
silver.
http://www.expansys-usa.com/product.asp?code=116333 256 $128.95 Black
http://www.expansys-usa.com/product.asp?code=111492 256 $128.95 White
http://www.expansys-usa.com/product.asp?code=111493 512 meg not out yet.
ccrrazzzy said:
Looking Glass said:
If you use OS 2.20 the problem is gone. During pairing select ONLY the first time is asks for Handsfree/headset. Discard the second time. (I Don't know why exactly)
:?
Click to expand...
Click to collapse
I noticed NO difference on BT800, or my ANYCOM 880, or from my two Motorola ones.. I do not know if it makes a difference on other devices.
Looking Glass said:
And BT specs for protocol 1.2 is already out there....
:?
Click to expand...
Click to collapse
Could you explain more please?
As for you first question: It does a difference to me. Some devices use different functions if they are paired ONLY as headsets or as HANDSFREE. The mess about "what you do in the two step pairing" is probably part of the problem. I've found that the first pairing is best for headsets (HBH 35, HBH 600) and the dual pairing is needed for carkits (at least for my BMW carkit).
Second question: BT specs 1.2 means that there are more profiles and functions that now can be implemented in more devices: SO MORE TROUBLES, and more chances for something to go wrong. There is a lot on information about BT specs out there, you can read about, and wonder what will happen with a device that implements them all.... the HTC/MS way!
And finally, some comments about the "erratic" behaviour of caller ID on your headsets: I've found some remarks noting that depending if your contact info for a certain number is stored in the phone memory OR IN THE SIM CARD, it might change how the info is passed onto your BT headset! So you can see the name, the number or even nothing at all for a few seconds.
:?:
Click to expand...
Click to collapse
Sorry, I have been away from this forum for a while and have decided to come back and try and face my BT issues again.
I am running
ROM 2.06.00WWE
Radio 1.18.00
ExtROM Sin.Merged.v1.0
on an XDA11 with a Blue Ant hands free.
Before upgrading the BT was crap.....long delays in answering, no redialling facility worked and the sound quality was awful.
Since upgrade I really couldnt tell you about the other issues but sound quality appears to be worse. My incoming is fine but out going, the hands free mike is not working and the phone is still receiving on its built in mike. I have tried pairing as "Handsfree" and "headset" with no difference.
Any ideas?
Cheers
Mark
OK,
sat in the car had a beer and tried again. Selecting "handsfree" when prompted and no and no to headset enables the in car mike and allows outgoing calling. But does not allow incoming calls pickup.
Every other config of headset and handsfree combo selections removes the in car mike from working.
Go Figure?
Cheers
Mark
teknophob said:
OK,
sat in the car had a beer and tried again. Selecting "handsfree" when prompted and no and no to headset enables the in car mike and allows outgoing calling. But does not allow incoming calls pickup.
Every other config of headset and handsfree combo selections removes the in car mike from working.
Go Figure?
Cheers
Mark
Click to expand...
Click to collapse
Hi! As said before, you'll be better off with 2.20.
2.0x versions work mostly OK as far as functions, but then you have the dual mic/speaker problems....
Read the forum, there is NO perfect BT solution, in fact, there is not a official version claiming to support HandsFree profile...
Yep,
I hear you, I know the o2 is not handsfree compliant only headset.
The local gurus at Strahfields are trying to sell me the latest Nokia bluetooth hands free.
I quote,
"Its compatible with everything and my mate has got an o2 and it works fantatsically" unquote.
But they where not prepared to give me a demo.
Cheers
Sorry if I am being stupid, I currently use the Diamond 1.2 ROM and have a BT800, so I know all of the problems in trying to get the mic working etc.
Is there an English ROM with 2.20 that's easy to install?
There are so many references and links to various CAB files on here, but as I use my XDA2 for business, as well as pleasure, I don't have time to experiment I would like to find an installer, do that, and then add my own apps, and be up and running within an hour.
I bought the BT800 for the call quality, not the extra features, but now I have a headset that can do so much more, I would like to make use of all the features, but not at the expense of the PDA's stability, although saying that, Diamond 1.2 gives me the hang on reset issues, and random slow down issues too, so it may be better to change to something else anyway.
ccrrazzzy said:
I think I found a fix for the BT Hands Free not working the way it should.. I can even use call waiting now and it does not kill the mic when I switch back to the first call..
I set the phone settings to automatically pick up after one ring.. No, it will not automatically pick up after one ring but, now I am getting the name to display in the caller ID field of my xLive mp3-BT headset. and it is working consistently.. I HAVE NEVER gotten it to work consistently before.. NEVER. i will try it with my Jabra BT800 later too.
I think it makes a "deeper" or better connection by making the phone try and make the BT headset device automatically answer???
I am using 2.20 OS and it is the only one that I have found to work, (not fully but it does work BETTER), please try this with other Hands Free devices like car kits and HBH660 etc.. Also try this with 2.02 and 2.06
Click to expand...
Click to collapse
Hi,
I see you are using Xlive Bluetooth MP3 Player... so I want to know if I can use it with the Motorola HT820 ( http://www.mtekk.com.au/tabid/54/articleType/ArticleView/articleId/641.aspx ) and my xda II whit ROM 2.20 ....
Thanks
I upgraded from the O2 XDA mini to the Orange M3100 and use the same Sony headset and can't get the voice tags to repeat in the headset after they have been recognised. It worked fine with the O2 phone, you pressed the headset power switch briefly, said the name and the phone played the match back to the headset. This new phone simply shows the name on the screen and repeats through the phone speaker. Tried to pair it again but still the same, anyone had this and found a fix?
As an update I was using the voice dial function the other day sat in the car and could hear the recorded name in the headset but it's reall quiet. The previous HTC phone was a lot louder so is there anyway to increase the volume of the spoken voice tag in the headset, I have the headset volume up full but still it's too low to hear properly.
I've seen some other posts on getting stereo headsets working with this Orange device. Can anyone help me find a way of getting the phone to increase the volume of the repeated voice tag in my bluetooth headset please?
Well there are only 263 posts re. Bluetooth and headset problems in this thread
http://forum.xda-developers.com/showthread.php?t=285419
If you can't find any answers there, there are about another 10 threads about headset and bluetooth problems, about 15 threads on Voice Command problems and you combine the two and you have a nightmare
... almost makes you want to use a wired headset and hand dial.
Trust me, I thought this would be easy.........
The previous HTC device I had (Wizard with O2) worked fine, press headset button, speak, phone confirms back and then dials. This one has such a low volume that you can't hear what it says. I read through a load of the posts but they all seem to be trying to solve problems I don't have, for me the headset and phone works, the TomTom GPS v6 also works, the TCP video software is almost there and all of this without having to hack any programes.
I tried it again today and before when I thought it was very quiet it was in fact the speaker on the phone I was hearing on the seat next to me, the headset does not reply the voice tag.
Surely others must be using BT headsets with this phone and use the voice dial tags when driving etc?
Roy_S said:
Trust me, I thought this would be easy.........
The previous HTC device I had (Wizard with O2) worked fine, press headset button, speak, phone confirms back and then dials. This one has such a low volume that you can't hear what it says. I read through a load of the posts but they all seem to be trying to solve problems I don't have, for me the headset and phone works, the TomTom GPS v6 also works, the TCP video software is almost there and all of this without having to hack any programes.
I tried it again today and before when I thought it was very quiet it was in fact the speaker on the phone I was hearing on the seat next to me, the headset does not reply the voice tag.
Surely others must be using BT headsets with this phone and use the voice dial tags when driving etc?
Click to expand...
Click to collapse
I don't have these issues so don't know the exact thread but I have read that many ppl are having the same problems as you. I think they have solved all but incomming notifications - so go looking and you should find.
I use an, admitedly ancient, Icon BT Headset for calls while driving, and all works well with one annoying problem.
With all other phones that I have used this with, the Headset synchronises completely with the phone. By this I mean that once connected, the phone's speaker is disabled and all keypad sounds, tones and other noises come through the Headset. To answer a call I could press "answer" on the phone OR press the button on the Headset, and the same to hang-up. Lovely Jubbly.
However, with the Blackstone, I have to Slide to Answer the Phone and then press the button on the Headset to activate that. Pressing the Button on the Headset alone does not answer the phone but instead tries to activate the Voice Dialling function, whether or not there is an incoming call.
The only noises that come through the headset, except while "in a call" are the ring tones.
Now, I ask, is this a problem with the Headset or, is that just the way things are with the Blackstone and BT Headsets?
If it's just that mine is old and knackered then I will get a new one, but i do not want to shell out for something that is not going to fix the problem.
OK. How about I rephrase the question.
Most of you out there use BT Headsets of some description. Which ones work like a common or garden phone?
Any? None?
Just want some advice before shelling out on trying to fix a problem that may or not be fixable.
Before you go spending money, try this software. It is fully featured and free for 15 days. It is an alternate bluetooth stack for Windows Mobile. See if it fixes your situation.
thanks for the advice.
been away, so only just got the message.
have installed. will report back with how it goes.
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?