Related
Hello everyone,
I have tried the two reg patch by Sin () to add the Handsfree profile to my Qtek 2020 (with WM2003SE). I use the very good Bluetooth headset by Globalsat BTH-808, and I have seen these things:
- When in Headset mode: the blu BT Led on the Globalsat flash one time per second. If one call incomes, an icon on the top bar light on in my Qtek and I can use the Globalsat to answer the call, or I can transfer audio back to Qtek and use it to answer the call.
- When in Handsfree mode: the blu BT Led on the Globalsat flash three time per second (awful). An icon noticing the HF Profile is ever on the top bar (with or without a call incoming, and this is not good, i think). If one call incomes, I can use at the same time the Globalsat or the Qtek (audio comes out from the Qtek and from the Globalsat).
Where is the good useful way of this? Why do I need the Handsfree profile too? to make voice dialing (adding relative software)? I didn't liked it and I disabled back the HF profile...
Can someone explain to me how the Hadsfree profile is good?
Thank's
facts
Hands free mode is great when using the right OS.
hands free is more robust. It offers caller ID, etc.
Headset will not do caller ID but I believe it may offer better battery life.
Also with your 2.02-2.06, you will notice while in hands free that the mic on the headset does not work, only the one on the phone.. Even though you can hear sound on the headset!!
If I am wrong, please tell me.
One OS that supports Hands free is the 2.20 translated or in original Chinese. But the caller ID is not consistent on some if not all devices. The caller ID will not be displayed if you have already received the call or if it is in your contacts. It also has some bugs when someone calls on the call waiting and you switch over to it, you will loose the sound on both the headset and the phone until you turn off hands free and then back on.
The other OS, 2005, is GREAT with the Hands free and the phone program, no bugs AT ALL with bluetooth and the phone, BUT, the contacts, email and calendar database are different so it will not work with many programs and the memory size is messed up and small.
I am switching back to my 2.20 translated today.
I wish someone wuld fix it.
Re: facts
ccrrazzzy said:
Hands free mode is great when using the right OS.
hands free is more robust. It offers caller ID, etc.
Click to expand...
Click to collapse
Hmmm, no... with my device (Qtek 2020, aka XDA II/MDA II and WM2003 SE 2.06) the CallerID works great with either Headset profile and Handfree Profile...
ccrrazzzy said:
Headset will not do caller ID but I believe it may offer better battery life.
Click to expand...
Click to collapse
Yes this is real: Headset is more light for battery life cause it lets BT headset to go online only during call incoming...
ccrrazzzy said:
Also with your 2.02-2.06, you will notice while in hands free that the mic on the headset does not work, only the one on the phone.. Even though you can hear sound on the headset!!
If I am wrong, please tell me.
Click to expand...
Click to collapse
According to me you are wrong, cause my device have the headset mic working in either Headset and Handfree profile. The only practic difference between the two profiles are that HS goes idle and come online only during call incoming, instead HF is online not stop.
ccrrazzzy said:
One OS that supports Hands free is the 2.20 translated or in original Chinese. But the caller ID is not consistent on some if not all devices. The caller ID will not be displayed if you have already received the call or if it is in your contacts. It also has some bugs when someone calls on the call waiting and you switch over to it, you will loose the sound on both the headset and the phone until you turn off hands free and then back on.
Click to expand...
Click to collapse
Again... with my device all works fine, but I don't like the headset all time in waiting/online modem with its led blinking speedly and the boring icon on the top bar (so if you miss a call or receive a sms, you see the baloon tooltip to advice you that more than 1 alert are waiting). I don't know about your bugs cause I never tested these cases
ccrrazzzy said:
The other OS, 2005, is GREAT with the Hands free and the phone program, no bugs AT ALL with bluetooth and the phone, BUT, the contacts, email and calendar database are different so it will not work with many programs and the memory size is messed up and small.
Click to expand...
Click to collapse
I am yet not happy about the WM2003SE 2.06WWE speed on booting and its stability... so I will not go further on with Magneto/WM2005... When I will be able to do, I will buy a new device with Magneto natively working...
ccrrazzzy said:
I am switching back to my 2.20 translated today.
I wish someone wuld fix it.
Click to expand...
Click to collapse
Good flashing and have a nice weekend!
The difference between the two right now using WM2k3SE is:
Handsfree allows you to redial the last number using your BT headset (hold headset button for 2-3 secs).
Headset allows to use the BT headset to talk on the phone.
Other than that they don't do anything else with the current OS (at least for me)
tesking
I am using a Jabra BT800 and I have talked to people who are using Erickson HBH200 and HBH660 and one guy who is using an xLive. The people I have talked to using 2.02 or 2.06 or Sin's 2.02-2.06 merge, all said these devices are not having the caller ID working and the Hands Free would give them the stereo affect.
You are the first.
I have tried 2.02, 2.06 and the Sin's combined one. All would not display properly with the caller ID on my BT800. And even with the addition of the reg key, hkey local machine, software, Microsoft, Bluetooth, "HandsfreeProfileOn", I would get the caller ID, only if the number was not in my contacts and it was not already in my call history of the BT device.
I have also tried BT tools, I have tried every patch and tried all the widcomm stuff too.
I am very curious to know what you have for a ROM and any BT additions or patches and I am very interested to know what caller ID BT device you have.
Maybe you misunderstood what I was saying as well, please know that I was talking about caller ID being displayed upon the BT device, not the phone.
One other thing that Hands free does is allows for the possibility of BT activated voice dial. Like the the voicesignal program on my MPX300.
There has to be a hardware specific driver for each device so when you press the button, it transfers the audio and Mic to the BT headset and starts the voice recognition program. Other wise, we would have had BT voice dial on our HTC devices by now. http://forum.xda-developers.com/viewtopic.php?t=15191&start=50
ccrrazzzy
I misunderstood the BT device you're using for caller ID (I don't have such device, I was talking about the phone itself).
As far as redialing using the Headset, I am using the Motorola HS850 and I was able to use it to redial the last number. However I end up turning the Handfree off when I don't need it in order to avoid the Mic issue on the headset. When I paired the headset, I chose headset profile only. When ever I need the handfree capability, I normall go under Start/Settings/Connections/Bluetooth/Devices hold my stylus on the device (HS850) then choose "Set as Hands-free" on the pop menu.
For Crrrrraaaazzzyyy:
For Crrrrraaaazzzyyy:
Sorry for your device... I can tell you that with the Globalsat BTH-808 (see the ebay link below), it works smooth in headset Profile (1 or 2 seconds and I can answer from the headset button), and it works smooth in Handfree profile (but as I said, i don't like the behaviour): you can buy the headset from here
http://cgi.ebay.it/ws/eBayISAPI.dll?ViewItem&item=6334980179
Have a nice day!
BT
Sorry I was not clearer at first. I was speaking about the caller ID on the BT headset or in a BT car audio system.
Hands free is needed to have features like caller ID on the BT device and voice dial and to be able to scroll through the BT device's caller ID history and make calls from that while leaving your cell phone safely tucked in your briefcase or hip case.
With my MPX300, because it supports BT voice dial through the BT headset, and with my caller ID on my Jabra BT800 BT headset, I can have all the power of my phone on my ear; being able to make calls through the caller ID history and through dialing via voice dial by speaking the phone number OR speaking the contacts name AND be able to see who is calling me, all while my cell phone-PDA is about 30 feet away!
I just wish we had this on the XDAII because I hate my MPX300; small screen and low memory make it useless.
Through the 2.20 OS, I am able to get caller ID functioning somewhat, but I have to disable call waiting. However to get BT voice dial to work, we will need someone to make a driver like the one that is in the MPX300 and use software like FONIX or www.voicesignal.com
Here is how we can make voicedial work on BT.
http://forum.xda-developers.com/viewtopic.php?t=19233&highlight=
XDAII-TSM500 and Jabra BT800 incompatibility ???
I cannot use neither the microphone nor the headphone of the BT800 instead of the XDAII for listennig mp3 files or recording notes.
When I use headset mode, I can speak and hear throuhg BT800 and it is possible to use the buttons to answer and hang during a phone calling, but is not possible to dial, see the caller number and other features.
When I use handsfree mode, I can get most of features but the BT800 microphone does not work and I have to use the one of the PDA.
Any way, only it is possible to use the BT800 in phone mode, not in PDA mode. However it works perfectly whit my IPAQ.
Could anybody give me any idea ?
BT
Please read everything.
Again,
With a caller ID device like the BT800, it needs Hands Free mode to work right. 2.02 and 2.06 do not do Hands Free well.
Only 2.20 and 2005 but 2005 has other bugs. In 2.20 you must disable call waiting or live with clicking upon Tools, Hands-Free Off, then Tools, Hands-Free On to resume the sound on the BT headset when you try to switch back to the first call. You will have to do this even if you ignore a call.
2005 works VERY well with BT and the phone but there are other bugs like lack of memory and database not compatible with third party programs.
I am sorry ccrrazzzy
I did not mention I have two other poblems:
One is that I am a beginner whith these machines, less than two weeks working whith them, and some concepts are confusing to me.
The other is, my short english (obvious ?) make me misunderstand things and to explain them is even worse.
I understood that all problems appear using the phone and not using the PDA for listening mp3 files, for example. When I use the BT800 whith my IPAQ 5500 (headset only) works like a wired headphones and I thought that it should work in the same way whith the XDA, forgeting the phone features.
I will try whith 2.20.
Many thanks for your answer and excuse me.
mp3 will not work unless you get http://www.bluetake.com/products/BT420EX.htm or the HP one.
While using Headset profile, in 2.02, 2.06 and 2.20, The BT800 will work but I experienced an 8 or 9 second delay before call is transfered to the headset when someone call me. Calling out is OK.
Hands free and 2.20 is only good way with BT800.
No audio on BT headset on the XDAII, no matter what OS... Like the mono audio on your other pda, it will not work on xdaii.
I am trying the xLive now, will post results. It has built in MP3 player and is BT cell phone Hands free. Only $90.
These will not make you look like you are from outer space
http://www.itechdynamic.com/html/border22.htm
Support HiFi audio, stereo but I doubt they will work on the XDAII.
You could make them work with the widcomm stack but that stack does not work with Hands Free and I forget if it works with Headset.
If this thing had caller ID and worked for sure with the XDAII, I would get it.
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 just bought an MEX-BT2500 and had it installed - all at Circuit City, for the Americans on this forum.
Since I literally *just* got it, I will give an initial impression and then update this in a few days probably with some more info.
INITIAL IMPRESSION
Well, it looks nice. The buttons have blue LEDs. But that's not very important. Pairing it with the Hermes was pretty painless, you just turn it off and then hold the Equalizer/Bluetooth button >7 seconds. The passcode is, of course, 0000. It has three separate Bluetooth icons - one for it being off/on/discoverable, one for hands-free being connected, and one for A2DP being connected.
When re-pairing after turning it off or something, the A2DP mode does not reconnect automatically. I've tried pressing 6 (Pause) and that made it reconnect. Maybe there are other ways of doing it, I don't know.
I am still experimenting with the A2DP settings to figure out what sounds best - I am using the Microsoft stack, so I'm not expecting miracles here - so far, it sounds OK at BitPool/MaxBitPool = 58 and Joint Stereo = 1. Contrary to popular belief, Joint Stereo is NOT mono, but I have yet to determine whether the Microsoft stack thinks that. I just need to play the right song. I read somewhere on this forum that increasing BitPool/MaxBitPool to 72 while keeping Joint Stereo on sounds good, so I'll try that later.
I will try the hands-free mode later on as well. Updates to follow.
UPDATE 1: More on A2DP (and a bit of hands-free)
I set both of the BitPool values to 72 and enabled Joint Stereo. It works well. The sound is most definitely stereo, and the quality is a lot better than what it was with a lower BitPool and Joint Stereo off. I've never tried the Widcomm stack, so I can't compare it to that. I also tried hands-free calling, but it did not work at all. That turned out to be an issue with the ROM (because it no longer worked with my HT820 either), which has since been resolved by flashing a different ROM. One extremely disappointing thing is that it looks like, for making calls, you can only initiate a redial from the device. I haven't looked into that too much yet.
UPDATE 2: Hands-free
I still haven't been able to make it do anything but redial for initiating calls, but the call quality appears to be quite good, both for the person on the other end and for me. I have to say, I'm impressed by that, especially since the Parrot MK6000 apparently has a huge separate dual microphone that you have to mount in order to get clarity.
One thing that has started to annoy me is the beeping when I turn off my car. Apparently it's to remind me to take off the faceplate, but I don't always want to do that and it pretty damn annoying. I don't believe there is a way to turn that off. You can turn off other beeps, but not that one.
UPDATE 3: A2DP again
The wireless stereo really does work well! The Hermes is able to handle receiving Internet radio streams (www.di.fm in my case) and piping them through A2DP just fine using MortPlayer. Speaking of which, AVRCP works well. Play/pause, previous, and next buttons all work, but with a slight (<1 sec) delay, which is caused by something other than the BT2500 because the same delay occurs with the Motorola HT820. It's either an issue with MortPlayer or the Microsoft stack - I don't know which one since that is the only combination I've used that supports AVRCP.
One thing I have yet to try is receiving a call while listening to music. I will try to do it tomorrow and see what happens.
I've had the MEX-BT5000 (the BT2500's predecessor) since January & use it with my Wizard. I haven't had any issues with A2DP connections -- I've paired it only once when I installed the headunit.
The only time I have to reconnect is if the Sony powers up without my Wizard in range -- the next time I power up the Sony, it'll connect to the Wizard's hands-free profile, but not in A2DP. To reconnect A2DP, open up the Wizard's BT connections screen, select the MEX-BT5000 device, and right-click "Set as Wireless Stereo".
3waygeek said:
I've had the MEX-BT5000 (the BT2500's predecessor) since January & use it with my Wizard. I haven't had any issues with A2DP connections -- I've paired it only once when I installed the headunit.
The only time I have to reconnect is if the Sony powers up without my Wizard in range -- the next time I power up the Sony, it'll connect to the Wizard's hands-free profile, but not in A2DP. To reconnect A2DP, open up the Wizard's BT connections screen, select the MEX-BT5000 device, and right-click "Set as Wireless Stereo".
Click to expand...
Click to collapse
Im fitting a BT5000 today in my new car. What car did you install yours in?
Ive fitted a new head unit to a vauxhall corsa before but never needed to use the smart cable for steering whell controls...is it dead easy?
P.S: the new car is a 2003 vauxhall astra
Does the BT5000 let you do voice dial through the Hermes/Wizard, or does it also just support last number redial? So far, I haven't been able to get it to do anything but redial for call initiation.
mrvanx said:
Im fitting a BT5000 today in my new car. What car did you install yours in?
Ive fitted a new head unit to a vauxhall corsa before but never needed to use the smart cable for steering whell controls...is it dead easy?
P.S: the new car is a 2003 vauxhall astra
Click to expand...
Click to collapse
Mine is a 2002 Mitsubishi Diamante -- I had to get a $60 translation unit to interface the steering wheel controls to the headunit. Installing the translation unit took some doing -- they're a bit tricky to program.
Trancecoder said:
Does the BT5000 let you do voice dial through the Hermes/Wizard, or does it also just support last number redial? So far, I haven't been able to get it to do anything but redial for call initiation.
Click to expand...
Click to collapse
Haven't tried voicedial -- I've got Voice Command 1.6 installed on the Wizard, so I think it'd work. I'll give it a try tomorrow.
Quick report back, had a right bastard of a time installing it LOL!
Vauxhall cables are deliberatly CRAPPY, i had to swap over two of the wires because the unit was not keeping the time or radio stations when i switched off the ignition. I also purchased a smart lead to enable the steering wheel controls.
Finally got it working, works an absolute DREAM with both A2DP and handsfree.
I am also thinking of getting the BT2500, but my big problem with it is the 'redial' problem. Apparently the BT5000 can download and store 50 numbers but doesn't allow for voicedial, (I've heard anyways)...
Trancecoder: Did you ever find something to trick the phone into launching voicedialing when a bluetooth redial was activated? What about the 1-6 buttons, can they be programmed for speeddials like the BT5000 ??
JamesManios - I don't believe the BT2500 downloads any contact info whatsoever, so those keys won't be able to be programmed. As for the redial vs voice dial issue, I haven't experimented much with it, so if there is a way to make it speed dial, I haven't found it yet.
Trancecoder: Thanks for the reply, how are you liking the unit now that you've had it for a while.
As an idea for dialing I was thinking of making an app to maybe accomplish it, but some of it I don't know how to do yet...
My idea was, have the app pole every 200msec or so and see if the phone has started dialing (that I pretty much know how to do), then see if you are connected to the bluetooth handsfree (don't know how to do that just yet)... then the program can assume that if you are dialing AND in the car (because you are connected), then you must be using the redial... STOP the redial and launch the VoiceDialing app...
It leads to some questions, like would the Stereo drop the BT connection and therefore the voice prompt would be from the phone speaker and using the phone mic and NOT the stereo...
I currently have this (which works very well), but not as clean as the stereo ... but I'm not sure I want to lose CallID and VoiceDial... to buy this unit.
http://www.vitebo.com/ny00050/produ...betiew&MenuID=28&BClassID=9&SClassID=0&PID=13
ive had a bmw m3 and the bluetooth sucks in it my infiniti much better. i always use my jawbone though. I may need to pick this one up.
JamesManios said:
Trancecoder: Thanks for the reply, how are you liking the unit now that you've had it for a while.
As an idea for dialing I was thinking of making an app to maybe accomplish it, but some of it I don't know how to do yet...
My idea was, have the app pole every 200msec or so and see if the phone has started dialing (that I pretty much know how to do), then see if you are connected to the bluetooth handsfree (don't know how to do that just yet)... then the program can assume that if you are dialing AND in the car (because you are connected), then you must be using the redial... STOP the redial and launch the VoiceDialing app...
It leads to some questions, like would the Stereo drop the BT connection and therefore the voice prompt would be from the phone speaker and using the phone mic and NOT the stereo...
I currently have this (which works very well), but not as clean as the stereo ... but I'm not sure I want to lose CallID and VoiceDial... to buy this unit.
http://www.vitebo.com/ny00050/produ...betiew&MenuID=28&BClassID=9&SClassID=0&PID=13
Click to expand...
Click to collapse
The unit's pros outweigh its cons, at least for me personally. I receive a lot more calls than I make while driving, so the dialing issue is not a big deal for me. The person on the other end can definitely hear background noise, but they can still hear me pretty well when I have my windows open and driving ~50MPH. The unit also plays MP3 CDs, which is nice because I have some from when I was using my old MP3 CD player. A2DP quality is good, although occasionally there is a drop out for about half a second. Sometimes it happens 20 minutes into driving, sometimes not at all, so I have no idea what's causing it. Overall, I'm satisfied with it.
One thing I noticed is that when I press the Hermes button 5 (mapped to Cyberon Voice Commander) while fully connected to the BT2500, the "Say command" prompt goes out through the Hermes' speaker and not the BT2500. That may cause additional problems if you want to try and create a software fix for the auto-redial.
That Vitebo website is full of Engrish! "THE FRESH PET OF CAR ARTICLE" - what does that mean?
Ya, that website is pretty brutal, unfortunately the manual is similar but I got it finally figured it out (I hope)
I decided against the Sony and bought a none BT headunit, thanks for all the info though.
Had mine for 8 months now...
Excellent unit. I had BMW factory fit bluetooth in my old car, this is much clearer (VW Passat).
I used mune with an Artemis, and now an Elf/Touch...
It doesn't download a phonebook, so the only dialing it can do is redial last number - but just use PocketCm and dial with your finger!
Quality is good - I have found, however, that A2DP streaming breaks up unless I use Coreplayer, which is 100% perfect... and yes, pressing '6' a coupl eof times toggles on the bluetooth stereo on the device, which is good, because otherwise, I wouldn't be able to hear tomtom instructions if I had the radio on!
Sound quality all round is excellent - just a shame it dosn't have a steering-wheel mounted remote instead of the useless IR one...
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've had the Note (AT&T) since not too long after it hit the market with AT&T. The Gingerbread release worked quite well, but I had heard "great things" about ICS. The day that ICS became available, I loaded it and was ready to be seriously impressed.
Instead, I'm quite let down. The additional "bloat" put into ICS to provide some changes to TOUCHWIZ are simply not worth it to me. What's worse the Bluetooth stuff has been changed enough, and in certain ways, to make it problematic for me now.
I have a vehicle with an integrated Bluetooth system. My phone is always paired when I'm in it, and I never make use of the audio profile for playing music through the stereo (but it's connected anyway). Under 2.3 / Gingerbread, everything worked fine. With the 4.0.4 / ICS software, audible notifications while paired to the system sound "choppy" (can't think of another way to describe it). The sounds stutters when the phone is attempting to notify me of, say, an incoming email message.
When the phone is not paired to anything, the notifications are fine.
I had an opportunity today to pair the handset to a completely different device and find that the issue follows it. It is absolutely not a hardware problem because it worked fine with GB. The issue is also not my vehicle because, again, it worked fine when the phone was running GB.
What I learned today, with the new BT device, is that the phone is actually attempting to provide the audible alert through BOTH the phone's speaker AND the audio profile / BT. On the device I had paired today, the sound through the speaker is the same sort of choppy notification it has been, but the sound through BT seems smooth.
There are no settings in the BT area to tell the phone to not use Bluetooth for audio. Does anyone know about this issue? More importantly, does anyone have a fix?
I too have that issue. Maybe a développé une ould look into this.
Sent from my SGH-I717M using xda app-developers app
I use both the audio and phone BT profiles on my car stereo. It took me a very long time to enable audio. I have no clue what worked. I do know that you can see what is enabled by tapping the gear icon next to the paired item in the paired item list.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
PaulF8080 said:
I use both the audio and phone BT profiles on my car stereo. It took me a very long time to enable audio. I have no clue what worked. I do know that you can see what is enabled by tapping the gear icon next to the paired item in the paired item list.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
The problem isn't in getting both working... The issue is HOW the phone works when both are enabled. There's almost certainly a bug in the ICS code that needs to be corrected.
ember1205 said:
The problem isn't in getting both working... The issue is HOW the phone works when both are enabled. There's almost certainly a bug in the ICS code that needs to be corrected.
Click to expand...
Click to collapse
My mistake. I shouldn't have mentioned my troubles. They masked the fact that I mentioned how to disable individual profiles by tapping the gear. You can uncheck audio there.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
PaulF8080 said:
My mistake. I shouldn't have mentioned my troubles. They masked the fact that I mentioned how to disable individual profiles by tapping the gear. You can uncheck audio there.
Click to expand...
Click to collapse
Yep. That works to correct the problematic issue of "it sounds funny when both are enabled", but it emphasizes the fact that there's an issue with the way that Samsung's ICS for the AT&T Note treats the Media audio profile whether it's active or not...