Related
Hi Guys: I have got the Widcomm Phone edition stack working on my unit.
It seems to be fine but I have not fully tested all aspects of the software - so if any little bits don't work, let me know...
You need to install the official widcomm 1-4-1-59 version
Then you can upgrade it using the cab file I have made.
The 1.4.1.59 version file I got from the following topic
http://forum.xda-developers.com/viewtopic.php?p=57550#57550
thanks go to mamaich for the file.
the upgrade file consistes of the PE edition files and the required registry entries.
Let me know how you all go on with it - but I am not really a hacker so any serious probs I will not be able to fix...
if anyone else can improve on the installation be my guest
any news about which profiles it support that ms or the old one dont support ?
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
I can't garauntee it works perfectly, so I suggest everyone make a backup of their system before use.
has anyone tested any BT headset with this new stack?
I've got it installed and it all seems to work well exept for the handsfree/headset profile, I have set up my headset ok it is discovered and bonds fine but when I try to connect from the xda2 the connection fails after "waiting for device" for some time. tried with a motorola hs 810 and a neovoice usb, same with both. Anyone got any ideas?
BT headset
I have a 6315 and an XDA 2, I haven't tried the BT Stack on the XDA 2 yet but I found when I bondeded my HBH-30 to my 6315 once it made the connection my BT Headset shut off for some reson. This caused the bonding to fail, but as soon as I turned my headset back on (while it was trying to discover services) it completed the process and worked on my 6315. I'm not sure if this will be the same, but it's worth a shot.
Brandon
Test results
Hi fellows
Here is little bit of my testing of this new BT Stack, which we all awaiting for..
Proc…
1. Installed as per instructions 1.59 without any problem. During installation was prom to override .dll files – agreed to do that. For good or for bad – will see later.
2. Installed .cab file provided by icarusbop (big thanks to him for doing this) without any problem. Screen shots will be attached below.
3. Reset it as requested upon installation and got Widcomm BT working instead of MS BT..
4. Paired it with my BlueTrek G2 within 3 seconds (which took usually 10 sec with MS BT)
5. BT recognized G2 as device with Headset/Hands-Free profiles and asked to use as default… I said yes…
Here comes Cons part ;(
1. Unfortunately even after paring – my I-Mate can not get connected with G2 (see screen shot)
2. As you can see in another screen shot – there is Hands Free menu – it can not be accessed, or can be accessed ONLY while connection is established.
3. AND the last L … So, this new BT is not working now… I decided to go back to MS BT… SURPISE!!! I am getting message that BT HARDWARE IS NOT INSTALL ON THIS UNIT…. L Assumption - .dll files were overwritten (see Proc 1)
Here is my 2 cents in this jorney… I am hoping that described problems can be fixed and we can make it working (without doing hard reset on my device )
Paul
thanks guys! for testing hands-free/headset profile. by now everything seems to work fine with this new stack except for hands-free/headset profile.
New comments to my testing
1. I tried what NeoCole recommended - didn't work for me
2. As soon as new BT is OFF - MS BT is working fine .....uf
LETS FIX THE HEADSET PART PLEASE
I posted this is another thread - but in case someone does not read that thread . . . it is relevant here as well.
If the intent of this is to get voice dialing without touching the device, that is by only pressing a button on the headset to initiate a voice-dial program to make the call, there is no evidence this works with this BT stack either.
I have been reading other forums with people who have the H6315 already (mine is in the mail to me now) and none of them have been able to make this work. Nor is there any mention of this capability in any of the literature and/or documentation for this device. It seems that if this was a feature of this phone, it would be prominently displayed!
Voice Command
Okay.. on my 6315 I press the headset button, it beeps, sound and voice is now transfered to the headset. I do this before I initate voice command. Now all I do is press a button that activates Voice Command on the PPC and walla, I'm speaking and listening through my BT Headset. This is a huge step forward from using the MS Stack, and I feel that since the Phone Edition of the Widcomm is 1.0.0 I'm sure that they'll associate a hardware button with the headset button in future releases. Anyhow.. I think that the functionality of the Widcomm BT Stack is well worth the work. The XDA 2 would be a lot better device if the BT Stack worked 100% of the time and was fully compatibile.
I also have not got it working.
the Hp 6315 is well know to still require a hardware button press (not on the headset) to activate voice command. They can still not do with any nokia or SE phone can do easily.
Surur
VoiceCommand
That would be correct... One press of the HW Button does it all on a Regular phone.
The 6315 has brought it closer to allow you to interact with programs using your BT Headset, but yes you must still activate the programs on your handset before you can use them with your headset.
So.. to sum it up...
1. You can't interact with Voice Command using MS BT Stack on an XDA 2
2. You can interact with Voice Command using Widcomm Stack on 6315, but you have to activate the headset first, then start VoiceCommand on the PPC by using the HW Button.
Hopefully through this thread we'll be able to give the XDA 2 the same functionality as the 6315.
And maybe if Widcomm provides an update to allow the headset to activate a HW button, we'll be to the one step solution.
I do not want my comments to be read as stating that this is not a worthwile endeavor. I simply meant to make sure that someone does not go to the trouble of installing this new stack (particularly those who might be considered novices) with the mistaken impression that by doing so they will have that "one step" voice dialing solution.
This is by all means a worthwile endeavor, but it is merely a step down the road . . . not the final destination.
Y'all are doing good work - keep on blazing that trail!
hm.. I would think that it is more of MS Voice Dial functionality than BT - to recognize signal sent from headset as request for voice dialing.
When MS released first version of Voice Dialing they did not expect new functionality to have BT headset with hands-free profile connected to the device.
paired with my Jabra 250 = ok
connected to my Jabra 250 = failed
No luck with Moto headset
Eveything else seem to be working. No problems with detecting and working with BT access point
rehman said:
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
Click to expand...
Click to collapse
Hi Rehman,
i tried to install and uninstall, for the very first time i didn't have to get a Hard-Reset done. the volume didn't disappear. so i believe trying it wont be a harm, but yet i would recommend to get a full Backup first.
Trying to figure this out
Okay, I looked through the whole registry. I can't find anything out of the ordinary. Only thing I can think of is the sound driver. Does anyone know what DLL that is? I bet it's a different version.
If someone that knows more about which DLL does what. Let's get all the DLL's that could pertain to Sound and Phone and compair the 6315 DLL's with the ones on the XDA2.
After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht
Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?
Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.
Changed over to Tytn... works perfectly without any hacks
here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.
A2DP is not working well.. when i use ad2p headset the audio fails VERY Much. If i turn off A2DP wmp plays well the music.
Is there any patch?
Thank's!
Fix!
I found this patch! It's not 100% good (sound fails ONLY time to time and drains battery ), but is almost, i think that with some work could get there...
lets make it 100% good...
http://forum.xda-developers.com/showthread.php?t=284974
this patch is not really working for me :/ i tried tons of patches but no go as of yet...
Is WM6 and ad2p no go? does it work better under WM5? or some issues? >.>
Or am i doing something wrong? Has anybody succesfully fixed thier ad2p under WM6?
if yes, what rom, what fixes? maibe radio rom? etc..
Thanks in advance
btw; tried Xplode's rom and now using Helmi's..
radiorom 1.13.. (not sure if that has anything to do with bluetooth >.>)
Xplode's i actualy ran perfectly once.. but never managed to recreate that after repairing my bt620s
thought I fixed it but nope.. softreset and no way to get it workin again..
Anyone mind posting thier registery settings, rom etc if they have no skipping with ad2p? >.>
Twistit said:
thought I fixed it but nope.. softreset and no way to get it workin again..
Anyone mind posting thier registery settings, rom etc if they have no skipping with ad2p? >.>
Click to expand...
Click to collapse
Use a registry editor and add the following to your BA registry:
HKLM/Software/Microsoft/Bluetooth/Devices
Add a new DWord: DefaultMTU with the Hex value of 2a0
Capitalization counts in te DWord.
BTW, I posted this 2 days ago in this same forum under the "muppet" thread. Search is your friend.
Thanks ^^ ill try it when i get home.. forgot my bt620s today >.>
Geh i did search ^^ but i never figured the Muppets would have anything to do with ad2p *grins* So many random topics in this forum it feels like searching for a needle in a haystack
No devices under bluetooth, only device.. and under bluetooth/ad2p there is a map devices.. under device and ad2p/devices it didnt do the trick
wait wait.. hard reset.. and it worked.. now to see where it helped.. i stuck the key in 3 places.. lol
Jup just another soft reset killed it again (without removing one of the keys).. seems my ad2p only works right after a hard reset.. and then dies again.. no matter what fix..
Nother funny thing, before adding my bt headset it sees my laptop bluetooth.. after connecting the headset it sees no devices..
HmHm.. going to flash pdaviet on it in a sec radiorom 1.15.. try that.. maibe try the helmi's broadcom bluetooth stack..
My solution with pdaviet and radio 1.15 ^^ connect the wireless stereo.. startup mediaplayer and listen how sucky it sounds..
hit pauze.. turn off bluetooth.. turn on bluetooth.. go back to the mediaplayer and make sure it listens to your bluetooth headset.. (play and pause if it the mediaplayer responds its OK ^^) And then turn on wireless stereo again.. its a hassle after every softreset.. but hey.. it works ^^
Twistit said:
No devices under bluetooth, only device.. and under bluetooth/ad2p there is a map devices.. under device and ad2p/devices it didnt do the trick
wait wait.. hard reset.. and it worked.. now to see where it helped.. i stuck the key in 3 places.. lol
Jup just another soft reset killed it again (without removing one of the keys).. seems my ad2p only works right after a hard reset.. and then dies again.. no matter what fix..
Nother funny thing, before adding my bt headset it sees my laptop bluetooth.. after connecting the headset it sees no devices..
HmHm.. going to flash pdaviet on it in a sec radiorom 1.15.. try that.. maibe try the helmi's broadcom bluetooth stack..
My solution with pdaviet and radio 1.15 ^^ connect the wireless stereo.. startup mediaplayer and listen how sucky it sounds..
hit pauze.. turn off bluetooth.. turn on bluetooth.. go back to the mediaplayer and make sure it listens to your bluetooth headset.. (play and pause if it the mediaplayer responds its OK ^^) And then turn on wireless stereo again.. its a hassle after every softreset.. but hey.. it works ^^
Click to expand...
Click to collapse
check this page:
http://translate.google.com/transla...arch?q=KB831722&hl=en&rls=com.microsoft:en-us
for some reason this KB article is only in Japanese but google translates it well. This is where I got my information and I can tell you I never have the difficulties yoiu are describing. Try the following steps and let me know if it working:
1. Connect the headset
2. open the media player of choice
3. start playback
4. pause playback
5. wait a couple seconds
6. resume playback
at this point it should play without any pauses/skips (works fine for me, but my BT range blows so bad, and my S9 headset is so uncomfortable I hardly ever use it. (If anyone wants to buy a nearly new S9 heatset let me know)
BTW It seems to be a known issue with BA + WM6 that headset disables all other BT connections. I would love to be able to use my GPS and headset together, but alas it disconnects the GPS everytime the headset is connected. Drop the headset and the GPS reconnects immediately.
One final note. All my testing has been done with the MS BT Stack. I read that Widcomm has no hands free support so I didn't try it.
Helmi's Broadcom Bluetooth Stack 1.7
I could never get the MS BT Stack to work right. Helmi made this test cab. It works well with my BA using WM6 and my Motorola S9 headset. The range is about 1 meter but the sound is good.
The BT manager format is accessed through the BT icon on the bottom toolbar.
I cannot upload the .cab file. Search for this file: HELMI_BA_WM5_BT1.7_TEST for great quality BT on BA WM6.
One way to solve the BTA2DP problem & it supports stereo. You can find these by the following link http://www.teksoftco.com/index.php?section=freeware & this software works too http://www.trianglepowers.com/PPC/ViewApp.aspx?ID=52 (have to register to download). I prefer Teksoft freeware as I am using it. Sometimes it takes a while after a few toggle u get it right
thanks alot trying the teksoft one and so far it works fine ^^ maibe ill see if its possible to skin the buttons tho
@kasush That method doesnt work for my headset, the Jabra BT620 can be a real ***** even on my laptop at times.. so i really need to turn off the wireless stereo.. So gues the S9 isnt that bad apart from the fact its not so comfortable.. the BT620 is great.. when it works ^^ just turning off the bloody blue rings on the headset everytime is anoying *grins* people think ufo's landed when i ride around with those on.
(Lol, just noticed there is a firmware upgrade available for my BT620s :O.. lets see how that works out ^^)
Mogul Widcomm stack
Has anyone successfullly installed the widcomm stack on their mogul. My pioneer Avic D3 hates the Mogul's MS Bluetooth stack. Keep me posted hackers! I love this site btw. I'm it's *****.
I just recently acquired a stereo bluetooth headset from dell model number BH200 and so far the stereo music quality is superb, but the moment a call comes in or I pick up a call it immediately disconnects itself. My question would be if any of you guys have any experience with this issue. the Stereo bluetooth and handsfree profile are both set to active. Any suggestions or hints?
I'm going to go on a limb here and assume that you guys haven't had access to the aforementioned bluetooth and i'm short out of luck here... right?
p.s. SAY IT AINT SO!!!!
Hi, I also have the same headphones and the same problem - only on HTC Universal flashed with WM6.
I search a bit on Google and it seems that the problem is with MS Bluetooth stack - it was working correctly for WM5 (but no A2DP), now in WM6 A2DP works, but handsfree does not.
Right now I'm testing alternative BT stacks - started with UniBT (it's Broadcomm stack modified for Universal) - now A2DP works flawlessly (before that, it didn't), but handsfree/headphones mode does not. At least trying to receive the phone call doesn't turn the headphones off.
i tested my fuze with a jabra bt2010 and it works fine. I'd prefer to not carry 2 bluetooth devices so i'm trying to find a way for it to work. I've been suggested to use a widcomm bluetooth stack as well but i dont know how to change my stack. If anyone here does know how to do it, please do enlighten us.
It's been nearly a month so I'm going to bump this thread in hopes of someone might possibly have some insight into this.
Push/bump.
I got the S9 now, it works for both functions but craps out completely when i'm outside, really bad signal reception as well as "muffled sounds" according to my audiophilic and audiophobic friends.
I think it has to be something to do with the actual firmware inside the bh200 that is wreaking some unknown havoc.
Dell bluetooth headset BH200 not working with Sony Xperia X1i
I have a Dell Bluetooth headset model BH200 and in A2DP mode, works flawless but the moment it is used with handsfree mode for call, the connection is broken and the headset switches off itself. This headset works very well with other non WM6.1 devices. Any clues with anony one what should be done in this case, some people have suggested JETware Hands-free Extension , any one tried on this.
I actually gave up on the bh200 and got myself a jabra bt8010. it works like a charm and the sound is just as good as the bh200
Indeed... i used to have a WM device (Mio A501) and I had the WM6.1 Pro..
I bought this BT at that time and it didn't work on WM6.1 (it even didn't asked me the PIN to pair it) but, when I tried with WM5.0, everything worked great, great sound on call's music, etc.. now I have a Sapphire and I'm not able to make calls on it (music works), but since I'm not driving and people used to look like "what a crazy guy speaking in English alone, no cables, it must be a mp3 or something.. hmmm" when I was on a call, it doesn't make a huge difference
i have yet to try this on wm6.5 but I highly doubt there would be a change..i'll give an update when I do charge up the bh200
i charged the bh200 up completely and tested it out.. it was a failure.. looks like 6.5 did not do anything to help...
Maybe windows mobile 7 will work.......... maybe.
You can use BH200 on call by this way only(I tested)
1. Turn on BT
2. Accepted call(However just Turn on your BT after accept call is OK)
3. Turn on BH200
4. Pair ur PDA w/ BH200
5. Done
IS this thead still active? I have a solution
Guys..
Use Reg edit and make the following modifications in your WM device by creating a new DWORD value 0 with the parameter UseESCO. Check out the path
HKLM\SOFTWARE\Microsoft\Bluetooth\AudioGateway\UseESCO = DWORD:0 (Dont use space between UseESCO)
Then restart the phone and delete any previous BT devices on your phone, start up the paining process and get it to work.
worked flawlessly on my Dell BH200
Thanks,
Raj.
seriously????
the fix is in one freaking registry tweak????
I'll have to wait 2 months before i can test this since i left the damn thing to rot in the US while i'm here in thailand..-_-
mputtr said:
seriously????
the fix is in one freaking registry tweak????
I'll have to wait 2 months before i can test this since i left the damn thing to rot in the US while i'm here in thailand..-_-
Click to expand...
Click to collapse
Of course Bro. I waited for 6 months myself too.. and finally found it in a microsoft forum.. well at last got it to work and my 200 sounds better than ever with its new functionality..
All the best
Raj
sweet! thanks a bunch man!
prudviraj said:
Of course Bro. I waited for 6 months myself too.. and finally found it in a microsoft forum.. well at last got it to work and my 200 sounds better than ever with its new functionality..
All the best
Raj
Click to expand...
Click to collapse
Heya, Finally got back ot he US and tested out the BH200 with the fix you mentioned. it works!!!!!
although, i'm wondering if you're having problems with the bh200 not wanting to connect to the phone automatically.
Need help for the same problem in android
I am having similar issues on my Nexus one. Dell BH200 works for music playback but stops functioning when a call is made or received. Even the connection between the phone & BH200 gets lost.
I would be really glad to get some help on this.
Is it possible and if so, can any of the chef's here cook a ROM which includes the Microsoft bluetooth stack over the Widcomm one??
Cheers
+1
I know each has it's merits and problems, but I'm having more problems with the WIDCOMM stack than I did with the MS one on the HD, so I'd like to see this in a cooked ROM as well...
Agree. A good idea.
+1
I really hope this can be done... chefs, please help us out!
It cant be done easily. The bluetooth chips in these phones (TP2, HD2, etc) dont work with the microsoft BT stack because the drivers supplied by HTC, don't work with it. They're designed to only interface with the widcomm stack and software :/ God knows I hate the widcomm stack on my TP2 as well, especially the crappy quality of the A2DP protocol, but unless some very bright mind comes along that can hack/rewrite a driver to work with the MS stack.. we're out of luck :/
NRGZ28 said:
It cant be done easily. The bluetooth chips in these phones (TP2, HD2, etc) dont work with the microsoft BT stack because the drivers supplied by HTC, don't work with it. They're designed to only interface with the widcomm stack and software :/ God knows I hate the widcomm stack on my TP2 as well, especially the crappy quality of the A2DP protocol, but unless some very bright mind comes along that can hack/rewrite a driver to work with the MS stack.. we're out of luck :/
Click to expand...
Click to collapse
Thanks....and bugger
NRGZ28 said:
It cant be done easily. The bluetooth chips in these phones (TP2, HD2, etc) dont work with the microsoft BT stack because the drivers supplied by HTC, don't work with it. They're designed to only interface with the widcomm stack and software :/ God knows I hate the widcomm stack on my TP2 as well, especially the crappy quality of the A2DP protocol, but unless some very bright mind comes along that can hack/rewrite a driver to work with the MS stack.. we're out of luck :/
Click to expand...
Click to collapse
Thanks for the explaination NRG. You managed to get MSVC to play nice with your Energy ROM for the TP2... was that because of a updated or perhaps an older Widcomm stack?... MSVC not playing nice with my BT headset HD2 is killing me. I use it all the time when driving... Your TP2 ROM and perhaps another were the only ones that worked at all with MSVC
I emailed HTC to voice my "opinion" of the Widcomm stack... not that I expect anything to change
Thats very dissapointing to hear!
It´s very important for me to dial contacts using my bluetooth headset SE HBH-PK740 !
Hi there,
I have a Sony Ericsson HBH-DS980 and it can access the addressbook/last calls without any problem on HD2. Is there any chance you might have missed the permission screen before first access attempt?
Also compared to Cruise, Diamond and HD (all bt tweaks applied) HD2 seems to have the best quality stereo output out of the box with these headphones. The bass is great and there is no background noise at all.
I friend of mine uses TP2 with Sony Ericsson HBH-DS220 and the stereo audio quality is also superior to MS stack both on WM and Vista/Win7.
I think it would make sense to open an thread to highlight incompatible BT hardware so that at least users planning to buy new ones will get the right headphones.
sproxy said:
Hi there,
I have a Sony Ericsson HBH-DS980 and it can access the addressbook/last calls without any problem on HD2. Is there any chance you might have missed the permission screen before first access attempt?
Also compared to Cruise, Diamond and HD (all bt tweaks applied) HD2 seems to have the best quality stereo output out of the box with these headphones. The bass is great and there is no background noise at all.
I friend of mine uses TP2 with Sony Ericsson HBH-DS220 and the stereo audio quality is also superior to MS stack both on WM and Vista/Win7.
I think it would make sense to open an thread to highlight incompatible BT hardware so that at least users planning to buy new ones will get the right headphones.
Click to expand...
Click to collapse
PLEASE explain us how you access adressbook?Voicedial?
I have SonyEricsson HBH-PV740 and Motorola HT820 and no way to dial adressbook.
I can dial last number by touching headset button twice but there´s no way to dial any person from adressbook without holding HD2 in my hands.
Hi there,
I have paired the device as usual. Then two profiles were selected by default. (stereo audio and handsfree).
1 Connect to your bluetooth device. You will see the services (image 1)
2 Select your device and then press properties button on the bottom left. (image 2)
3 Check the box where it says "Connections authorised"
If you dont perform step 3, next time the headset tries to access addressbook, you will see a promt on your phone and you will need to allow it. If you miss this screen, the functionality will not work.
When you press addresbook button or call history button on your headest, you will see that a new service is added to the list of services (image 4) named Phone Book Access. This will only show when you are accessing the addressbook or call history.
I can see both the names and numbers on the screen of the BT headset.
Also, in ms stack I would only see a number for the incoming calls on my headphones. Now I can see the name as well. So this was another improvement of the new BT stack.
Regading voice dialling, since I have a small screen on my headphones(980), did not need it. I think MS voice command would do the job well. The only issue I remember from previous WM devices was you needed to get the right DLL associated so that you could trigger it with the dial button on the headphones.
These theads might be a good starting point regarding MS voice Command
http://forum.xda-developers.com/showthread.php?t=304224
http://forum.xda-developers.com/showthread.php?t=281977
you might find more up to date resources if you searh the forums deeper.
Hi there,
is there anyone know why the bluetooth was downgrade from 2.1 in WM6.1 to 1.9.3 in WM6.5 in T-Mobile TP2? Any way to upgrade it back to 2.1?
I have a Sony Ericsson HBH-IS800 headset that requires Bluetooth2.0+ in order to use the volume control on TP2. There is no volume control on the headset.
Thanks.