Database Users

Widcomm Phone Edition stack working - get it here!!!

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.

Solution for some people vexed with est a BT AS Partnership

Found a possible "solution" for some people who have been having problems estabishing a BT AS Partnership with their Universal and a host computer running AS. What I found was you may need to edit the registry to fix the problem. Here's what happened to me yesterday:
Morning: Hard reseted my device and installed all my software apps at my work computer via AS in USB mode as a Guest. Note: I have not set up a partnership with any computer (either USB or BT).
Evening: Got in my truck and paired my JasJar to my BT GPS receiver via a BT Serial Port. Used TomTom and navigated home.
Late Evening: Got home. I wanted to set up a BT AS Partnership first so I went through the procedures of pairing my device and my home computer. And guess what, it didn't work. My JasJar would not see that AS was an available option on my home computer (NOTE: Before Hard Resetting my device in the morning, I had previously established a BT AS Partnership with my JasJar so I know my machine supported that profile). What the @?#~! Ok. I did a search of the word "sync" through the registery. Came up with an interesting issue. Under the registry entry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\ActiveSync\
In that directory I saw a folder listed as: 000a3a051d0f (This folder is specific to my device (more below)). I was wondering what this was since I did not have any BT ActiveSync Profiles set up yet. When I looked in it, I realized immediately that this is the Device Profile for my GPS RECEIVER!!!! What the hell was it doing in this directory I asked myself. So I deleted the folder 000a3a051d0f from the directory:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\ActiveSync\
And guess what? I was able to establish a partnership via BT immediately!!!
So the bottom line is....
If you're having problems using the MS BT Stack to set up a BT Sync Partnership, you may want to check this directory and see if the BT Stack accidently put a BT Device in this directory that should not belong there. My guess is that when I paired my BT receiver and set up a communication link via a BT Serial Port, the MS BT Stack thought that it was a device capable of an activesync partnership. Hope this helps some folks.
Justin

Thanks a loooooot.
Tried everything else first, but your solution worked like a charm!

Tytn / Vario II and Pioneer P55BT

Hi all,
I've got a Pioneer P55BT headunit in my car, and it has support for bluetooth to use it as a handsfree, however I cannot connect my Vario II to it, as it doesnt detect it as a phone, so doesnt come up when trying to pair it.
Has anyone managed it? or have any advice?
Cheers

have you tried pioneers tech support on this one? I know its not directly helpful, but if they are not currently aware of a problem they cannot patch the firmware

timbouk said:
have you tried pioneers tech support on this one? I know its not directly helpful, but if they are not currently aware of a problem they cannot patch the firmware
Click to expand...
Click to collapse
Havent no, not yet, always try the forum first.

Solution
Hi,
I've got exacly the same problem with a Vario II and a Pioneer DEH-P75BT. After a lot of email's and phonecalls with pioneer in the Netherlands, they came everytime back with the answer "Your phone is not on the supported models list". Yea i knew that already.
Before my Vario II is always used a SDA without problems. I discovered that when i select hands free from the vario itself, it pairs without problems. The radio just have some problems with discovering the Vario II.
The problem:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.

flue said:
Hi,
I've got exacly the same problem with a Vario II and a Pioneer DEH-P75BT. After a lot of email's and phonecalls with pioneer in the Netherlands, they came everytime back with the answer "Your phone is not on the supported models list". Yea i knew that already.
Before my Vario II is always used a SDA without problems. I discovered that when i select hands free from the vario itself, it pairs without problems. The radio just have some problems with discovering the Vario II.
The problem:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
Click to expand...
Click to collapse
You're a legend... did as you said and all worked perfectly!! well after I remembered what the code was to pair it, lol 1111.
Cheers tho, appeciate it.
Luke

that's got to be worth adding to the wiki!
how's it done?

I would def say so, sure it's a problem on a number of devices (i.e. stereos)

It's also a solution for other devices using a Microsoft BT stack.
Maybe it's worth to make it a general wiki update?

flue said:
It's also a solution for other devices using a Microsoft BT stack.
Maybe it's worth to make it a general wiki update?
Click to expand...
Click to collapse
gets my vote

Vario II working with 55BT
After several tries with 55BT, I have finally managed to connect it.
The way to do that was only by using radio and not PDA. Wherever I tried to pair the devices from PDA, I was getting PIN code screen over and over.
However, after running detection as advised in the manual from the radio side, all was running fine. What might have helped was the pairing with other phone (Motorola RAZR3 to be precise) and pairing on position 2. Magic but was my case Generally, the worst thing with 55BT was the duality if I may say so of the buttons and knobs changing its funcion is different steps of the pairing - simple mistake and you need to start over.
Given the problems, I have tried Sony BT5000 and it worked like a charm, but I was afraid of the sound quality, given the mic is builin in the radio.
Finally I have decided to go Blaupunkt route, but can confirm, when paired, 55BT was working fine, althoug some echo was present during call.

mKotek said:
After several tries with 55BT, I have finally managed to connect it.
The way to do that was only by using radio and not PDA. Wherever I tried to pair the devices from PDA, I was getting PIN code screen over and over.
However, after running detection as advised in the manual from the radio side, all was running fine. What might have helped was the pairing with other phone (Motorola RAZR3 to be precise) and pairing on position 2. Magic but was my case Generally, the worst thing with 55BT was the duality if I may say so of the buttons and knobs changing its funcion is different steps of the pairing - simple mistake and you need to start over.
Given the problems, I have tried Sony BT5000 and it worked like a charm, but I was afraid of the sound quality, given the mic is builin in the radio.
Finally I have decided to go Blaupunkt route, but can confirm, when paired, 55BT was working fine, althoug some echo was present during call.
Click to expand...
Click to collapse
The problem described above is that the radio doesn't detect the PDA. As i understand from your post, is that your radio does find the PDA by default, right? Or have you paired the pda once, and registered on the radio? This shoud work by default.

flue said:
Hi,
I've got exacly the same problem with a Vario II and a Pioneer DEH-P75BT. After a lot of email's and phonecalls with pioneer in the Netherlands, they came everytime back with the answer "Your phone is not on the supported models list". Yea i knew that already.
Before my Vario II is always used a SDA without problems. I discovered that when i select hands free from the vario itself, it pairs without problems. The radio just have some problems with discovering the Vario II.
The problem:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
Click to expand...
Click to collapse
flue,
I have the HTC Prophet pda and the pioneer DEH P75BT and have just changed the value in the registry as you suggested (haven't had chance to test it yet though) but I trust it will work.
Have you used the BT Audio function on the stereo to stream music from your pda to the stereo yet?
My experience is that it's a painful process to pair but the quality of music once paired is second to none. I eventually gave up with it though because of the dreadful pairing process.
Could this be to do with the COD? I mean is there a seperate COD code for a wireless stereo?

neomagik said:
flue,
I have the HTC Prophet pda and the pioneer DEH P75BT and have just changed the value in the registry as you suggested (haven't had chance to test it yet though) but I trust it will work.
Have you used the BT Audio function on the stereo to stream music from your pda to the stereo yet?
My experience is that it's a painful process to pair but the quality of music once paired is second to none. I eventually gave up with it though because of the dreadful pairing process.
Could this be to do with the COD? I mean is there a seperate COD code for a wireless stereo?
Click to expand...
Click to collapse
Hi,
I don't really know if the prophet has a different stack of modified stack for a2dp because i don't use that phone.
I've got the universal and tytn phone here. I never figured out how to get the universal working without stuttering. My conclusion was it's a lack of processor power.
The vario II does work better with a2dp, especially after a soft-reset.
I never got pairing problems with both of them for a2dp. The radio connects fine and directly after choosing "set as wireless stereo" on the phone.
This does have nothing to do with the COD. Even with the COD set to the default value (pda), and you set your radio as headset/wireless-stereo from the phone, is should work without problems. Even registering on the pioneer should be possible then.
The only thing it doesn't with the default COD is automaticly connecting to the bluetooth headset when powering on the pioneer device.
I seems that the pioneeer deh-b75bt does not have the funcionality to auto-connect a2dp, such as the headset does. Too bad

Thanks for the info flue.
I've now had chance to see if the phone will auto connect with the new COD and can confirm that it does. So well done that man!!!!
I can also confirm that both times I tried "set as wireless stereo" it paired with no problems and I was able to listen to mp3's on my phone through my car speakers in almost perfect quality!
BTW I installed the Tornado A2DP hack in order to get A2DP working as the Prophet isn't capable of it without it.

this procedure don't function with my TyTn on mercedes Benz Bluetooth kit.
It recognized the phone with a 16 numbers code but don't pairing. Someone have the same problem ?

Hi guis!I've got an HTC MTeor smartphone and pioneer bluetooth car stereo.Excuse me for the stupid question, but I couldn't understand how to change my phone COD from PDA to smartphone.Where do I have to type this code?Or what settings I have to change? Thank you in advance

I have a DEH-75BT as well. Have anyone found out how to get adress book transferred to the radio?
/Kasper

StoianZh,
The MTeor is a smartphone and its COD will by default already be set to smartphone. No changes are required.
Kasper_m
Use outlook on your PC
First do a Select All on your contacts* You may have more than 1000 contacts and if so may wish to break this up into one or two attempts to provent overloading the PC.*
Then choose Action->Forward as VCard
On the mail that appears choose File-> Save Atachments.
Save the VCFs to a folder and move them to your phone.
In the car use SmartExplorerEN or Resco Explorer and Select All the VCFs. Choose Send Files Via Bluetooth and the Headunit will appear in the list. Send them all to the HU

flue said:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
Click to expand...
Click to collapse
Hi,
I have a HTC TyTN and a Pioneer DEH-P4900IB
I have the same problem as described. If I pair the phone with the Pioneer it will work fine, but as soon as either the car-stereo or the phone's bluetooth has been switched off, it will not automatically connect.
I can either re-pair it, or alternatively choose the Pioneer radio in the list of paired devices on my TyTN, click update, re-choose "Handsfree" and click save.
I have now tried your solution, and unfortunately it hasn't solved the problem.
I still have exactly the same problem. When I turn on my car, the radio will search for bluetooth devices but ends up displaying "NO TEL".
Can anyone help with a solution to this problem?
Thank you in advance.
/Erik

Hi, I have a Pioneer P75BT. I've used the COD hack, which works very well. Thanks to the original poster.
I've found that I have to leave the Vario II in discoverable mode in order for the P75BT to connect to it automatically, even though the P75BT has the Vario II registered. I can also connect it manually.
I don't like the idea of leaving my Vario in discoverable mode all the time, but it looks like thats the only way to automatically connect each time, unless someone has found another solution. Perhaps its not so much of a problem as I tend to turn off bluetooth on the Vario II when i'm not using it.

Bluetooth pairing diagnostics?

Hi all,
I am unable to pair my XV6800 to my Pioneer DEH-P980BT car stereo. The phone detects the stereo and requests the PIN, but fails after I enter the PIN with a 'Cannot Connect, connection failed or pin is wrong' error. I have used this stereo with my xv6600 Blue Angel for over a year (Can you say Widcomm stack?).
Anyway, I have been unable to come up with fruitful answers or even a next good step by searching the forums or general internet searching. I am wondering if there is some kind of Bluetooth tool that would allow me to determine what actual error is occurring?
Any help would be greatly appreciated.

I had the exact same problem with the same head unit. Here's what I did to correct it:
Code:
The vario II identifies itself as a PDA bluetooth device. The pioneer modules are searching
for a phone or smartphone, so it just ignores the Vario II.
Solutions:
Change the COD (Class of Device) from a PDA device to a smartphone device.
This can be done this way:
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my vario II does have the value: 1048852 (decimal)
Change this to: 5374476 (decimal).
3. Soft restart your device
4. Voila! Your device now identifies itself as a smartphone, and my pioneer unit finds it without problems.
That SHOULD work for you. Please let me know if does, because when I do it, the stereo finds the handset fine, but I can't hear any conversation coming out the speakers. It's like it is on permanent mute. This also happens with my BT headset - all controls work, but I can't hear anything nor can people hear me. Plus, my Mogul's speaker cracks and pops when I try using it with another BT device. I think it may be a bad unit. I want to know if you have better luck with the Mogul and 980BT.
I am using the newest ROM (2.17) and radio. The same thing happens to me with the older 2.09 ROM also.
sup191

Eureka!
It worked! I had tried this COD change before and had tried initiating pairing from the stereo, but had not tried both at the same time. I am able to connect the phone and bluetooth stereo simultaneously, and both are working with excellent sound quality. That's leap and bounds from where I was yesterday. Thank you very much!
Regarding your problems, I am not experiencing them at all. I can hear both sides of a conversation as can the other side. As it stands I think I will have to manually pair every time I get in the car (a pain, but I will work on it).
I am not sure what differences exists between the Hermes and Titan, but I would be happy to investigate for you wherever I can. My ROM is version 2.09 and my radio is version 1.30.
Thanks again. Feel free to post or PM me if I can help you figure your issues out.

Thanks for the offer to help. I think my first step is going to Sprint and showing them that BT is crap on my Mogul and see if they'll swap it for me. I'm also going to try pairing my headset there on the demo and see if it works. If it does, my unit it broken. I'll let ya know what happens.
sup191

Connecting to Ford Audio

There are other car connection threads but I thought I would post this thread to provide a search hit for anyone with a Ford Bluetooth Radio. It combines bits from a couple of threads and should enable you to successfully connect to your Ford car. Thanks to all of the other posts whose work I have cobbled together here. This is confirmed as working with the HTC 1.66 WWE ROM.
Out of the box the HD2 does not initiate auto connection with the Ford, refuses to pair with the Sony radio and hangs the radio at the end of a call so...
Using Resco or similar registry editor..
1. Modify the HandsFree plug-in: HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change DWORD SupportedFeatures to 45 (was 1379)
ii. Create binary value HFBDA , set to same value as LastConnectedBda
iii. Create DWORD HFDeviceType (Dec) 2
2. Modify the WIDCOMM bluetooth general settings: HKLM\Software\WIDCOMM\BtConfig\General
i. Change binary Value bdaddr to (no value) delete the existing key value, was 00 23 76 74 2c d5
ii. Change DWORD DisableReopenAudio to 0 (default is 1) I didn't have this registry key so I created it with DWORD value (dec)0
3. Reboot device (soft reset or long press off until power off option).
These above mods make the handshaking between car and HD2 much less prone to lockups!
Go to car, check that radio has bluetooth enabled.
HD2 wil find car (Ford Audio), send a random keycode - pairing fails but this will wake up radio which displays another keycode. Re-enter this correct keycode and pair device.
If a Ford built in radio then accept incoming connections and phonebook download when prompted.
If the Sony radio (Galaxy, S-Max etc) then you must also accept the stereo music connection else it will not work.
On HD2 go to settings, menu, all settings, bluetooth and 'add knickname' to your Ford Audio connection, check that 'accept all connections' box is ticked on this page.
Only bug so far is that by accepting the stereo audio connection the music player starts playing whenever you connect to the Sony radio. The music cannot be heard as the Sony does not accept incoming streams - however if you do not enable it at the connecting stage then the phone connection subsequently fails and refuses to work again. If anyone can get around this annoying problem then please post below.

Huge thanks for pulling this together
I'd about given up hope of getting the HD2 working with my S-Max. Still not perfect, but at least now usable.
Great stuff.
Interstingly the current S-Max seems to be generally less compatible than the one from a couple of years ago.