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.
Hi
Anyone found any software that offers reliable voice dialing? The MDA Pro comes with somet called "Voice Speed Dial" Its sh1te!
Has a habit of trashing the voice tags of its own accord, and often does not respond when I press button on bluetooth headset.
When the device is closed and off and you press the button on headset nothing happens (PPC is starting up etc) several presses are usually required before you can actually call the contact.
I just tried a trial version of microsoft voice command 1.5 (this I believe is what imate is shipping) unfortunately it cannot understand a word I say!! (could be the devonian accent).
I said 'call work' it said 'calling 999' I managed to hit it with a brick before it actually did call 999 !!!
Anyone suggest something that actually works (flawlessly). I dont mind training it if that means its gonna work!
Nigel
"microsoft voice command" all the way.
Thing is that it doesn't support dutch, but it does support english, german and american, so if you speak any of these languages you will have to get this program.
Dunno about the trial version, but the full version requires you to pronounce right. You can test this by letting someone call you first so you can hear how the program expects you how to pronounce it. (I have dutch names and they are completely different when pronounced by the voice command)
Hope this helps.
I've flashed my MDA Pro with the I-Mate JASJAR rom, and the standard voice dial on that works like a charm!
It even work from my Jabra BT800!
Grrrrr
I'm a native English speaker and it dont ruddy understand me!!
Sounds like many people here have gone for the JasJar rom on their devices. I guess I will give this a go - I just dont want to end up with a useless brick.
Nigel
MS Voice Command - works for me on my jas jar via my moto BT headset even in the car when driving (i.e. with plenty background noise).
If you follow the tips on the MS VC website it makes it even more reliable.
The HTC voicedial program works great for me, and complies with my HS810 headset without any issues whatsoever. In fact it's even recognised my commands with music running in the background. I've tried MSVC in the past on other XDA's and found it to be rather cumbersome.
Ant
I found that Microsoft Voice command when started via bluetooth headset does not turn the link off when it's finished.
The way i got this to work with BT was to replace the file sddialer.exe in the windows folder with the voicecmd.exe file from MS VC.
Does anyone else know a better way of doing this to allow for the BT headset to be turned off automatically once listening is finished ?
Voicedial works, I just find it really slow. It is 100% reliable on the recognition front though.
What I noticed with voice command was an instant response. Press the button and speak, no wait of any kind for the 'beep'.
Voice command simply sticks an icon on the task bar, it does not have to load some monster gui before you can speak. Ditching the gui would be a step forward for the built in voicedial.
Nigel
steverae said:
I found that Microsoft Voice command when started via bluetooth headset does not turn the link off when it's finished
Click to expand...
Click to collapse
Hi
How did you get voice command to respond to the bluetooth headset in the first place?
With VC installed, the button on my BT headset is still starting the old HTC voicedial software.
Is there some registry setting somewhere to tell it what to launch?
Nigel
Yes there is a simple registry hack, it's posted else where in these forums but here it is again
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
This works for me and everyone else who has tried it AFAIK
Hi
How did you get voice command to respond to the bluetooth headset in the first place?
With VC installed, the button on my BT headset is still starting the old HTC voicedial software.
Is there some registry setting somewhere to tell it what to launch?
Nigel
Click to expand...
Click to collapse
I simply replace the file sddialer.exe with the voicecmd.exe and renamed the voicecmd.exe to sddialer.exe. After a softreset that's it.
Still can't fathom out a way to close the BT link though without doing it manunally from the headset.
Also does anyone have Fonix Voice Central installed on their Universal, i always get an error saying unsigned program or summit like that when i try to install the trial.
voicedial
I am italian mother tongue. Cyberon voicedial works incredibly well. I tried vito's program in the past. Average it could recognize 10%.
The cyb's software is awsome. I use it with a Jabra BT800 headset and recognize voice even in noisy environment.
Must tell that I am very satisfied with my JJ. Absolutely no problems in any way.
Installing unsigned apps on WM5
Trying to install Fonix Voice Central 3.0 Trial on my new Universal but keep getting an error stating unable to install as it is from a untrusted source or is an unsigned program.
Please help
Hi
OK, so its more reliable when using the bluetooth headset - it even understands devonian! BUT and this is a big but... why the heck does it not work when the device is closed (screen inside) and switched off??
Nuts... I get the beep from voice command after pressing button on the headset, but it ignores what I say. Performing the same thing with the screen open laptop or pda style (with device switched off) works fine, but not with the ruddy screen closed.
Anyone else experienced this?? Screen closed it how my device stays most of the time.
I see what people have been saying about it leaving the bluetooth channel open after as well - mad!
Nigel
Voice command does not respond when unit closed
Hi
Voice command not responding when unit closed (screen inside), and using button on BT headset.
Has no-one else found this, and if it works for them can they post rom versions. Certainly does not work on MDA Pro shipped rom!
When unit open, or screen folded outside PDA style, VC does respond to BT headset fine. Just not when its closed.
Nigel
I have imate JJ italian rom.
Works perfectly with Jabra BT800 and device switched off (screen closed down).
No problem at all!
Thanks - looks like a bug in the ancient MDA Pro software.
I was holding off flashing it with imate roms case I heard a rumour that t-mobile are about to release a new rom soon which may be newer again I suppose.
Nigel
Well, I put the imate rom on there and that did not solve it. Voice command does not work from bluetooth headset when unit closed. It gives me the beep prompt to say its listening, but it never responds. Open screen and all is well.
Save me some money anyway, no point in buying Voice Command if it does not work properly!
Nigel
veletron said:
Voicedial works, I just find it really slow. It is 100% reliable on the recognition front though.
What I noticed with voice command was an instant response. Press the button and speak, no wait of any kind for the 'beep'.
Voice command simply sticks an icon on the task bar, it does not have to load some monster gui before you can speak. Ditching the gui would be a step forward for the built in voicedial.
Nigel
Click to expand...
Click to collapse
Ive just been using the bog standard voice recognition. No problems at all, even works with background noise.
Im guessing that some people havent read instructions properly
The HTC software that comes with the device does work (reliably) its just too slow to be of any use.
10 secs to respond when unit is off/closed. If I dont get a prompt response i'll press the button on the headset again which seems to confuse the hell out of it.
This is my reason for trying voice command... Response time from voice command (from unit off) is 2 secs max. Unfortunately it does not ruddy well work when lid is closed (no matter whether unit is on/off).
Nigel
Hallo...
I have serious problem and till now I don't know how to fix it. I change the registry to allow the Bluetooth Headset to activate the MS Voice Command, when I click the button on the BT the Voice Command starts fine, but if I want to use it agin, the VC doesn't work anymore, I hear only a "peep" but the programm doesn't respond. I have Qtek 9100 with the last official ROM .
Any idea or solution to fix that ?
I appreciate any comment.
Thomas voicecommand and bluetooth has some issues. Basically, when you use VC the first time it opens the channel with the device, once you have then used it you need to hold the button down on your bluetooth device to close the channel. Then pressing BT again should open voicecommand. There's a number of posst for this problem but hopefully I've given you the basic issue
Thanks for your reply... But no, closing the Voice Channel doesn't solve the problem.. I have tried all that before I post my question, it really works only once and no more, only after restarting my device it will work again for once.
I am starting losing a hope that it can be fixed.
Thomas1234: I started trying to come up with solutions to this a while back but never had time to work on it further yet. Anyways what I came up with so far can be found here. It's not perfect but may work with your headset and make it useable for the most part.
http://forum.xda-developers.com/viewtopic.php?t=49255&highlight=
Note: Scroll down to the bottom of the above thread to get the latest version and you have to be logged in to see the file.
Hi shoey5!
Thanks for trying to help me, but it doesn't work, and it looks like that this file damaged the connection between BT headset and the Voice Command or any Voice calling, even the one by default ( voice calling ) doesn' work anymore now.
I was able before at least to do the voice calling, but now it doesnt work after I changed the registry to default to read from the sddialer.exe file.
Can you please explain me what did the file change so I can change it back if i is possible ?
I did softreset alot, but doesn't help.
Thomas1234: It doesn't modify or change anything, all it does is run resident and resets the Audio Gateway Service after a call has ended if there is a bluetooth device active. Removing it from your startup folder and resetting your device will get rid of it completely.
Are you sure you haven't modifed something else before or after that may have affected your problem. I know this sounds silly but is your volume up, can't tell you how many times I sit there pushing the button and wondering why I don't get anything only to realize my volume is off
BTW, Try this. Leave the program in your startup folder, power off your headset and reset your device, then power on your headset and see if it works from that point on. I've noticed this happens to me with headsets that exhibit this problem the odd time.
Thank you anyway..
I ended up to do a hard reset, because softreset didn't help... It has been worse, I even couldn't dial a number using the BT headset, well I won't say it is 100% because of your file, but I am sure I didn't do anything with the device that can cuse this problems before I applied you file, all this happened just after I installd your file.
I'll use the default Voice dialer then with my BT Headset till maybe Microsoft update its program.
this "ms voice command running only once" happened to me too, with Nokia HS-12W headset.. try using JETware Hands-free Extension for Windows Mobile phones, http://www.jetwaremobile.com/ , and activate ms voice command from its advanced settings.. it worked for me. unfortunately it's not free and it doesn't supply caller names to my hs. hope this helps..
Thanks ozkaya, the program looks useful. I'll try it and see if it does the job correctly.
I am very sorry in advance if this issue has been raised elsewhere on the site, but after spending quite some time searching for an answer by both the forum search and google search, I am going round in circles and haven't found a solution.
I have a UK Tmobile Vario 2 (Hermes) running its original Rom (I have been too scared to flash it in case I break the phone as I don't really know what I am doing) and I have a Motorola S705 A2DP headset. I love the feature on VC 1.6 which reads out new text messages in full but can't find any way of routing the audio for this feature through my bt headset. The incoming call notification works through the headset but every time an SMS comes through it pauses A2DP, reads it via the phones loudspeaker, then diverts sound back to the headset again?!?
I went on the WIKI and found the Voice Command section. I tried installing the patch/program it suggests and did the tweaks it said to the registry , but it didn't make any difference on this problem.
I just wondered if this is an unfixable problem, or if there is anything I can do to get it working because this feature would be incredibly useful to me (I ride a motorbike and to get texts read through my headset when riding would be excellent).
Thanks in advance for any help guys. Sorry again if I am raising a known issue, if I am, if you could point me in the right direction it would be much appreciated.
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
bapski said:
have you tried this? i know this .cab file worked on my jawbone but i dont/have not used VC 1.6.
Click to expand...
Click to collapse
Thanks Bapski, I have just installed it but unfortunately it hasn't helped thank you anyway though, it was definitely worth a try
Well, I have had a good read through the threads on Voice Command and all the fixes for the headset button but it seems nothing yet solves the problem of routing the SMS notification through the headset which is a shame, it would have been so useful.
Well, hopefully, when I get my nice new Kaiser upgrade (whenever that may be ) .. I will have more luck with the bluetooth audio
Don't buy a phone with a MS BT stack because they will never fix the problem..MS has known about this for so long its just sad..The next phone I get will have a widcomm bt stack.
Yeh, got to say that the bluetooth hasn't been particularly great ... especially when trying to get it working on A2DP.
If only I hadn't stumbled across VC 1.6 I would be none the wiser and wouldn't even know it is possible to have SMS messages read out oh well
it doesnt work dont even bother, I loved it on my wizard, but there is a hardware problem with the heremes or whatever the problem is the last revision of the BT stack doesnt fix it and its never worked. all the patches and fixes only work for awhile then just stop and rquire a cryptic series of hacks to make them half work again. your better off buying a thai slave to read your messages to you.
I used to use MSVC 1.6 on the Tytn2 on WM6.5 (see sig) and the confirmation notifications when you called someone always used the bluetooth headset. Since running it on the Leo MSVC seems to use the loudspeaker on the handset instead of the bluetooth headset even though every setting is marked as "Announce notifications using Bluetooth hands free only"
Anyone else having this issue as I did a search and couldn't find anyone.
Edit: Just had it working once but then the other end couldn't hear me when the call connected. Then I tried again and it had reverted back to not working.
I went to Bluetooth settings, Advanced, Audio and ticked the box then rebooted the phone...
I have this same problem! Its annoying... you want to make a call and the prompts/confirmation come from the phone... Please, can someone figure this out?
Bumping thread as it should be resolvable
Starfury said:
Bumping thread as it should be resolvable
Click to expand...
Click to collapse
IT isn't... I have done more research..
The Leo (and the TouchPro2) use a Widcomm BT stack as opposed to the usual MS stack. Sadly, this means the BT won't play nice with a lot of different apps/equipment. This isn't something that can be swapped out easily as NRG has pointed out. Touch Pro 2 users are still facing the same problems even though that phone was released much earlier. Some however have reported some success when using certain custom ROMS... how its working with some ROMS and not others is still a mystery it seems
I would watch the ROM Development thread carefully to see if a ROM what works with our MSVC shows up....
Hello,
Is there a workaround... ?
Thanks in advance for any info,
Jean-Jacques
I have the same problem. I'm using an old phone when I need to use hands-free. After spending a lot of money on my HD2, I'm not impressed.
I there a particular combination of headset and software that does work, especially for voice dialing?
have you tried this?
I would, but I don't know if I even have voice command on my phone.
http://forum.xda-developers.com/showthread.php?t=634494
DrATty said:
I there a particular combination of headset and software that does work, especially for voice dialing?
Click to expand...
Click to collapse
Does not work with my helmet bike with scala-rider Q2, but does with does with Philips SH9000 stereo headset...
Mono/Stereo seems to matter.
Any workaround would be veryyyy appreciated
Jean-Jacques
Workaround
Hi,
for this following workaround seems the only way to get it runnin:
My BT-Headset has the ability to be set as a Stereo-Device. When I establish a connection to this Stereo-Device, I can use it (my BT Headset) to give Commands and recieve "answers" from the VC. In case I want to start a phone-Call, my headset changes the connection automatically from "Stereo-Device" to "Handsfree-Device" and back, after finishing the Call.
This may be the Reason, why someone here already got it running with a BT-Stereo-Headset.?
Sorry for my bad english...