Dell BH200 Bluetooth 2.0 EDR Stereo Headset
Hi, i'm unable to use the Dell BH200 Bluetooth 2.0 EDR Stereo Headset to make or receive calls. The A2DP i.e: stereo funtionality works beautifully. The issue im facing is when i have it configured as handsfree and i make or receive a call im unable to hear what the other person speaks, the head set turns off after about 7 to 10 seconds of making or receiving the call. The best part is during this 7 to 10 seconds if i speak, the other person can hear.
I have tried with different WM phones and smartphones with no luck. The headset works great with Nokia and Sony non WM phones.
This is surely problem with WM software itself, any help is appriciated.
The phone im using is an HTC Touch (Elfin) and the Bluetooth headset is Dell BH200 Bluetooth 2.0 EDR Stereo Headset.
All Replies
Cooldnkid wrote: This is surely problem with WM software itself, any help is appriciated.
I don't think that is the case Coolnkid. I would tend to believe it is the bluetooth software they have used is not compatible with the bluetooth that HTC used on the Touch. It is not a Windows Mobile issue.
I will tell you that I have had great experiences with BlueAnt bluetooth products if you are looking for a reccomendation.
Help_Line wrote: Cooldnkid wrote: This is surely problem with WM software itself, any help is appriciated.
I don't think that is the case Coolnkid. I would tend to believe it is the bluetooth software they have used is not compatible with the bluetooth that HTC used on the Touch. It is not a Windows Mobile issue.
I will tell you that I have had great experiences with BlueAnt bluetooth products if you are looking for a reccomendation.
Thanks for your reply and reccomendation !!
I have not only tried with HTC phones, i have also tried with 1 of my friends HP iPaq still the same. Based on these senarios it made me belive that its the problem with WM software.
Its almost the same issue if not exact which users are facing in this thread
http://forums.microsoft.com/windowsmobile/ShowPost.aspx?PostID=2334616&SiteID=65
Yeah, I agree. It is unfortunate but there are some devices that use different bluetooth software that is not compatible which is the case I believe with the car kit described in the thread you referenced.
How old is that Dell headset?
The Dell headset is brand new, may be a week old.
Also to mention that i was looking at the registory in WM, and found some settings of well known Bluetooth headsets, dint find any for Dell Bluetooth (or Alcatel who is the manufacturer of this Dell's headset)..
Is there any patch / update / any settings (like registory entry) i need to make ?
Not that I know of Coolnkid. I would return it because it is so new.
I'm not sure what kind of headset you are looking for but check out the X5 at BlueAnt:
http://blueant.com.au/x5_stereo_bluetooth_headset_headphones_a2dp.htm
I did a review on them here:
http://experiencemobility.com/wordpress/?p=1752
- Marked As Answer byMaryAliceCMSFT, OwnerThursday, March 26, 2009 8:46 PM
- Unmarked As Answer byMaryAliceCMSFT, OwnerThursday, March 26, 2009 8:47 PM
Help_Line wrote: Not that I know of Coolnkid. I would return it because it is so new.
I'm not sure what kind of headset you are looking for but check out the X5 at BlueAnt:
http://blueant.com.au/x5_stereo_bluetooth_headset_headphones_a2dp.htm
I did a review on them here:
http://experiencemobility.com/wordpress/?p=1752
I don't wanna return it as it has good Bass for my streaming audio (the main reason why i picked it up), also returning the product is just a workaround for the issue and not the solution.
It would be great if you can pass this message across to your WM software developement team if they can come up with any patch to fix this issue.
If at all they do then you will have many happy WM users.
Help_Line wrote: Not that I know of Coolnkid. I would return it because it is so new.
I'm not sure what kind of headset you are looking for but check out the X5 at BlueAnt:
http://blueant.com.au/x5_stereo_bluetooth_headset_headphones_a2dp.htm
I did a review on them here:
http://experiencemobility.com/wordpress/?p=1752
Well there seems to be more an issue with WM 6 / 6.1 as far as my understanding goes. The Device while being used on WM 5 HTC Gene - 3400 seems to work for a fairly longer duration but yet cuts out. The headset has been designed to work with A2DP v2 and is backward compatible as well. To add to cooldnkid, the device is been working fine on other OS mobile phones - Symbian / Linux. (Nokia & Motorola Rokr). Please find detailed information about the device as below,
http://support.dell.com/support/edocs/acc/P130684/
To top this, would want reiterate that this is a forum with resolution to queries as a back drop. Suggestions to return the product or an exchange might just not feel just for this forum. Request you to kindly relook at options and provide details of the device drivers being supported by MS WM for Bluetooth A2DP. Please confirm if this an additional driver addition to the radio the Dell BH200.
Appreciate all youre help, Thanks.
DreamCaster wrote: the device is been working fine on other OS mobile phones - Symbian / Linux. (Nokia & Motorola Rokr). Please find detailed information about the device as below,http://support.dell.com/support/edocs/acc/P130684/
Which would indicate that they were designed to work with the bluetooth stacks for those devices. I have never tried that headset but those that I have used (Motorola, BlueAnt, Etymotics, JawBone to name a few) have all worked ... flawlessly.
DreamCaster wrote: Request you to kindly relook at options and provide details of the device drivers being supported by MS WM for Bluetooth A2DP. Please confirm if this an additional driver addition to the radio the Dell BH200.
I think that would be better addressed by Dell support. They would be aware of drivers that might be available for their devices.
- I should also point out that they used the Toshiba bluetooth drivers (rather than the Microsoft drivers) which may be the cause for the issue with some Windows Mobile devices.
Help_Line wrote: I should also point out that they used the Toshiba bluetooth drivers (rather than the Microsoft drivers) which may be the cause for the issue with some Windows Mobile devices. WHen you mean they, are you referring to Dell or HTC ?
My guess is the Dell device. I've never had an issue connecting any bluetooth device with my HTC devices.
I think I would contact Dell support of the connection issue
- I have an ATT palm 750W running windows mobile 5 with the Dell BH200 headset that for an entire year worked flawlessly for the entire time. Until i upgraded to WM6. Now i can use the headset for music but not for calls since the upgrade. Im certain the headset didnt change, but i know the Windows Mobile software did. I am almost inclined to revert back to WM5 but that was too buggy on my phone and caused my phone to lock up alot even without added software. So yes, with WM5 the headset worked great. but now the only thing that has changed was the OS and it doesnt work for calls anymore. I wouldnt call dell, its not their problem. It has something to do with the OS software on your device. Ive been searching for a fix for a few months now with no luck either.
I would have to assume that the WM6 upgrade uses different drivers than what your headset used for WM5. Upgrades do bring with them changes ... maybe there is an upgrade available for the headset to make it work the way it did for WM6 the way it worked for WM5.
- I have a similar problem as described in this forum and yet it has a twitch.
I have a HTC TYTN II and a Motorola S9 stereo headset. When using WM6 it always paired automatically and there were never any problems with sound nor picking up calls.
With WM6.1 however I can pair it once or twice and the all of a sudden there are no longer connection. If I reinstall WM6.1 then it can be discovered again and can be used for an amount of time 1-2 weeks and then it happens again. It's like it's being ignored by the OS or something.
Anybody got an idea about what to do about it. Quite annoying to keep on reinstalling the OS.I have no intention of going back to WM6 as the phone as such runs much more smoothly with WM6.1.
Thanks It might be an issue specific to the S9 and how it uses the drivers on the TYTN II. Have you asked Motorola if there is an issue and if so, will there be a firmware upgrade?
- I got my brand new htc touch hd with WM6 and I experience the same issues pairing it with BH200 headset.
Is there any development going on regarding this issue?
Hi I am also facing the issue with my new SE Xperia X1 ... Contacted Dell and they confirmed the issue is with the OS (WM 6.1) Hope only MS can help us....
- See if this device wizard from Dell helps: http://support.dell.com/support/dsn/dsnsearchresult.aspx?c=us&cs=rc956904&l=en&s=hied&Query=QkgyMDA=&SystemID=&ServiceTag=&contenttype=-1&os=-1&component=-1&lang=-1&customersearch=False
- Proposed As Answer byMaryAliceCMSFT, OwnerTuesday, April 28, 2009 9:46 PM
- Would love to know if the device wizard from Dell addressed anyones issue with these headsets...
See if this device wizard from Dell helps: http://support.dell.com/support/dsn/dsnsearchresult.aspx?c=us&cs=rc956904&l=en&s=hied&Query=QkgyMDA=&SystemID=&ServiceTag=&contenttype=-1&os=-1&component=-1&lang=-1&customersearch=False
didn't help... hope ms comes out with a patcheSee if this device wizard from Dell helps: http://support.dell.com/support/dsn/dsnsearchresult.aspx?c=us&cs=rc956904&l=en&s=hied&Query=QkgyMDA=&SystemID=&ServiceTag=&contenttype=-1&os=-1&component=-1&lang=-1&customersearch=False
didn't help... hope ms comes out with a patche- Try setting the registry value:
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\UseESCO = DWORD:0
Then reboot the phone, pair to the headset, and see if that works around the problem.- Proposed As Answer byAlkalined Tuesday, October 27, 2009 10:12 AM
Try setting the registry value:
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\UseESCO = DWORD:0
Then reboot the phone, pair to the headset, and see if that works around the problem.
Wow, I was already desperate that a solution existed at all, but this seems to be actually working.
Thanks a lot!
What exactly does this setting do, if you don't mind my curiosity?
Could there be any side-effects?
Try setting the registry value:
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\UseESCO = DWORD:0
Then reboot the phone, pair to the headset, and see if that works around the problem.
Wow, I was already desperate that a solution existed at all, but this seems to be actually working.
Thanks a lot!
What exactly does this setting do, if you don't mind my curiosity?
Could there be any side-effects?
There are 2 types of connections that are used for the voice connection from phone to headset, SCO and ESCO. An ESCO connection provides higher quality voice audio than SCO. This registry setting will disable the use of ESCO and force the voice connection to use SCO. The only side effect will be lower voice quality.
WM6.x ESCO connections work fine with most headsets. With a few (such as the Dell BH200) there is a problem which is now understood and we have a fix for future releases. The registry setting is a temporary workaround.
