After upgraded to WM2003SE, My XDA2's bluetooth doesn't connecting well with my Motorola HS810, it only works for outgoing calls but unable to receive phone calls. Wonder what problems could it be. :?:
hmm...
I don't know that what version of wm2003se you have done, but I used to have the same problem with you coz my headset is HS810 the same.
Anyway, this attached file helps and you should give it a try, it gives a bit different performance from normal headset function but quite well.
Or... another suggestion.... try a translated rom version 2.20.07 this one works very fine with HS810 and you can also use HS810 with handfrees profile.
Good luck!
Re: hmm...
Vedas said:
I don't know that what version of wm2003se you have done, but I used to have the same problem with you coz my headset is HS810 the same.
Anyway, this attached file helps and you should give it a try, it gives a bit different performance from normal headset function but quite well.
Or... another suggestion.... try a translated rom version 2.20.07 this one works very fine with HS810 and you can also use HS810 with handfrees profile.
Good luck!
Click to expand...
Click to collapse
Thanks Vedas:
After downloaded this attached file to my Xda2, my bluetooth is back to normal again and with more features thn b4, very usefull thanks dude.
cool!
A bit mor additional information that you should be aware....
Warning:
While using this Pocket Bluetooth Tool you can pick up call waiting and you still can swap between 2 calls but whenever one of them ends you will lose signal between your headset and ppc, the remain call will still in progress but you cannot talk at all then must end up with hang up the call.
Solution:
Just disable Call Waiting in Phone>Tools>Option>Services>Call Waiting.
This is the downside of this program with HS810 that I has encountered.
If you still want to use Call Waiting, I suggest 2.20.07 and you may love it.
Good luck!
Re: cool!
Vedas said:
A bit mor additional information that you should be aware....
Warning:
While using this Pocket Bluetooth Tool you can pick up call waiting and you still can swap between 2 calls but whenever one of them ends you will lose signal between your headset and ppc, the remain call will still in progress but you cannot talk at all then must end up with hang up the call.
Solution:
Just disable Call Waiting in Phone>Tools>Option>Services>Call Waiting.
This is the downside of this program with HS810 that I has encountered.
If you still want to use Call Waiting, I suggest 2.20.07 and you may love it.
Good luck!
Click to expand...
Click to collapse
Thanks again Vedas
I still haven't try the call waiting feature yet. But for any interuption like you said, i think i'll have a try the 2.20.07 as you written above. But how and where do i get this upgrade?
Same thing happen to me .. where to get the patch ?
Now my BT is chuck in my drawer . Funny thing is that HS850 got not problem ..sighhh ..
thanks
Related
Hi,
I am thinking of buying this software to run on my qtek 9100.
It is running a T-Mobile 1.6 rom with the blackberry connect.
Will it work OK?
Is it worth buying?
Would you recommend it?
Thanks,
Dave
i use it and love it. only wish it would work with bluetooth headsets. it's nice to hear who is calling by a nice female voice rather than ringtones. the voice recognition is great as well.
I would recommend it.
The voice dialing works much better than the standard built in voice dialing (even though it has actually sampled your voice FFS).
bl117 said:
i use it and love it. only wish it would work with bluetooth headsets. it's nice to hear who is calling by a nice female voice rather than ringtones. the voice recognition is great as well.
Click to expand...
Click to collapse
It works great with bluetooth headsets. There's a couple of tweaks you need to do though. You can probably find it with a search.
bl117 said:
i use it and love it. only wish it would work with bluetooth headsets. it's nice to hear who is calling by a nice female voice rather than ringtones. the voice recognition is great as well.
Click to expand...
Click to collapse
if only she didnt sound like a chinese robot!
gregski said:
It works great with bluetooth headsets. There's a couple of tweaks you need to do though. You can probably find it with a search.
Click to expand...
Click to collapse
Unfortunatly, the reg hack tweak for BT VC only works once. It stops working after you end a call.
dangerous_dom said:
Unfortunatly, the reg hack tweak for BT VC only works once. It stops working after you end a call.
Click to expand...
Click to collapse
Huh? I've never experienced this. Every time I push the button on my headset, Voice Command activates. No matter how many calls I've had. It might be a matter of the headset as well. I could never get my Jabra BT500 to work reliably...sold it. But my Tekkeon ET3000 works flawlessly.
dangerous_dom said:
gregski said:
It works great with bluetooth headsets. There's a couple of tweaks you need to do though. You can probably find it with a search.
Click to expand...
Click to collapse
Unfortunatly, the reg hack tweak for BT VC only works once. It stops working after you end a call.
Click to expand...
Click to collapse
I never had this problem. Here is the tweak I use:
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. Reset device.
When it stops working, does that registry value still show the right value?
works fine here
VC works great with my Cardo Scala 500. Sounds better too since they gave me free silicone caps. I can hear ringtones, notifications, etc. all through the headset.
Re: works fine here
j007w said:
VC works great with my Cardo Scala 500. Sounds better too since they gave me free silicone caps. I can hear ringtones, notifications, etc. all through the headset.
Click to expand...
Click to collapse
How did you enable ring tones? Mine doesn't do that by default and I haven't figured out how to enable it.
I don't think that anyone can say that Voice Command works flawlessly over bluetooth.
The fact that pressing the button on the headset opens the audio gateway and it has to be closed before it can be opened again is a bug, not a feature. The audio gateway should close itself and doesn't.
The software has been out since January '05, I believe, so some bugs with Windows Mobile 5.0 are expected.
That being said, I love Voice Command despite its issues. Once Microsoft decides to release a new version that works better over bluetooth, I'll love it even more. It's presently still worth buying, definitely.
it's a great program, but needs to be updated for WM5. It should support activation from Bluetooth headset out of the box.
Some people seem to have it working, but with my Sony Ericsson HBH-662 it only works once after each reboot.
Mine also works only once through bluetooth - i got the latest Rom/Radio Rom (the Mr Clean one) installed, perhaps that has got something to do with it?
Deep DooDoo
Hey Guys,
I installed voice command on my Tmo Wizard and the midst of uninstalling it, it gave me a message that it wasnt uninstalled correctly. It left a shortcut in the settings section. Ever since then when i try reinstalling it, it gives me a msg that another version is already installed. How do i remove the already installed one short of hard resettin my phone? Any help will be deeply appreciated. Any role for removing it via reg edit?
Thanks in advance.
:?:
It's a great piece of software. It has a few quirks which annoy me a little but hopefully they'll be sorted in the update if it ever comes.
When voice dialing a number e.g. dial 282 456... it insists on putting a zero infront of the number i.e. it will dial 0282 456.... I'm using the UK version BTW. I tried the US version up it didn't recognise my voice as well.
Also, the volume of the voice when annoucing this could be louder. there is no way to increace the volume.
It wold be nice if they expanded the command library to include more functions.
Re: Deep DooDoo
I finally fixed it a couple of soft resets later and trying to install the updated version 1.5 before installing version 1.0 and then uninstalling both and installing 1.0 and 1.5 together it finally worked!! Its a nice piece of software.
Email me if anyone wants detailed info.
XNG
nice_xtremely said:
Hey Guys,
I installed voice command on my Tmo Wizard and the midst of uninstalling it, it gave me a message that it wasnt uninstalled correctly. It left a shortcut in the settings section. Ever since then when i try reinstalling it, it gives me a msg that another version is already installed. How do i remove the already installed one short of hard resettin my phone? Any help will be deeply appreciated. Any role for removing it via reg edit?
Thanks in advance.
:?:
Click to expand...
Click to collapse
I just got the Microsoft Voice Command 1.6 (refer to as VC from here on) this morning and so far it has been quite disappointing.
I am using it on a Cingular 8525 with a Sony Ericsson HBH-GV435 headset (both are BT 2.0).
Right after the installation I noticed that the talk button on the headset did not trigger the VC so I did a power cycling.
After the power cycling the button will now trigger the VC as if I pushed the VC button on the phone but the problem is that it is not picking up my voice command via the headset but it is still listening from the phone's mic.
Any thoughts on this?
hjkl;' why no delete?
skygear said:
did you try to go under your d\settingd to chsnge the buttons? i think you have to reg edit the files for ear pice mic
Click to expand...
Click to collapse
I didn't know that.....I'm going to try and search for it. Can you maybe post a linky for the info on how to do that?
thx!
Version 1.6 at present time DOES NOT WORK properly with the TyTN. You should go back to V1.5 and wait for a patch...
goestoeleven said:
Version 1.6 at present time DOES NOT WORK properly with the TyTN. You should go back to V1.5 and wait for a patch...
Click to expand...
Click to collapse
I see. Thanks for the info. Hope the patch will be available soon!
What is the probelm with the ver 1.6 and the TyTn? Is it just the TyTN rom or does it not function with the JasJam or the 8525 either?
Dp you guys know this by experience or is it posted somewhere?
PocketPCThoughts list the 8525 as a "compatible device".
The problem will affect all Hermes devices, and it will probably require a patch / a new dll and/or a registry hack to make things work properly. It should work, but it doesn't, and this goes to show you what a poor job of testing was done before product release.
If the single biggest additional feature/function (ie, bluetooth support) doesn't work properly, why was it shipped?
goestoeleven said:
The problem will affect all Hermes devices, and it will probably require a patch / a new dll and/or a registry hack to make things work properly. It should work, but it doesn't, and this goes to show you what a poor job of testing was done before product release.
If the single biggest additional feature/function (ie, bluetooth support) doesn't work properly, why was it shipped?
Click to expand...
Click to collapse
Come on folks... This is MS we are talking about...
If it had been a software package with a little penguin or a devil on it we would be just fine
mrderby said:
Come on folks... This is MS we are talking about...
If it had been a software package with a little penguin or a devil on it we would be just fine
Click to expand...
Click to collapse
Or maybe we should start to look at HTC... Their implementation of the whole bluetooth "feature" is crap too... AD2P anybody? well let's hack the crap out of the register, and than try to be happy with songs that hickup every 30 secs or so... neah great!
First: Hermes generally does not work with BT2.0, I guess, especially my MDAvario2 does not...
I'm using a BT Headset HBH608, which was perfectly working with every phone I've ever tried...
Second: VC1.6 could not be installed on Vario2' and Hermes Devices at all, getting an error message...
VC1.5 (engl.) works, not perfect, but it usually works...
MickKnatterton said:
First: Hermes generally does not work with BT2.0, I guess, especially my MDAvario2 does not...
I'm using a BT Headset HBH608, which was perfectly working with every phone I've ever tried...
Second: VC1.6 could not be installed on Vario2' and Hermes Devices at all, getting an error message...
VC1.5 (engl.) works, not perfect, but it usually works...
Click to expand...
Click to collapse
What do you mean it cant be installed. I have it installed on a TyTn and it works perfectly. I am not using a BT headset, so cant comment on that.
I've got v1.6 on an 8525 and it seems to working fine.
what exactly are the problems others are having with Hermes devices?
@DigitalFX: Hermes does support Bluetooth 2.0, but not Enhanced Data Rate.
@JCrompton: MSVC 1.6 does not route sounds/commands properly through a Bluetooth headset on the Hermes. You may be able to initiate a call with your headset button, but you'll be using the mic/speaker on the Hermes to complete it. Also, sounds/announcements are not working as advertised. HTC and M$ are working on a patch.
VC 1.6 works fine on my MDA with Motorola BT headset.
Mark (NL) said:
Or maybe we should start to look at HTC... Their implementation of the whole bluetooth "feature" is crap too... AD2P anybody? well let's hack the crap out of the register, and than try to be happy with songs that hickup every 30 secs or so... neah great!
Click to expand...
Click to collapse
Seriously, why dind't any OEM use the Widcomm stack instead of the crappy MS one ?!
If only there was a way to hack the Widcomm stack and replace the MS one like they did with the Dell axims..
Adi
goestoeleven said:
@DigitalFX: Hermes does support Bluetooth 2.0, but not Enhanced Data Rate.
@JCrompton: MSVC 1.6 does not route sounds/commands properly through a Bluetooth headset on the Hermes. You may be able to initiate a call with your headset button, but you'll be using the mic/speaker on the Hermes to complete it. Also, sounds/announcements are not working as advertised. HTC and M$ are working on a patch.
Click to expand...
Click to collapse
Has anyone tried this... (look for the cab)
http://forum.xda-developers.com/showthread.php?t=283412&page=5
My 8525 works fine with 1.6 and my SE662 BT headset. Calls can be activated over BT using headset button, and audio routes to my headset throughout my call.
URPREY said:
My 8525 works fine with 1.6 and my SE662 BT headset. Calls can be activated over BT using headset button, and audio routes to my headset throughout my call.
Click to expand...
Click to collapse
Wow! Have you done any registry hacks? I'd love to see what your Voice Command keys look like....
TIA,
Richard
I have an 8525 also, and 1.6 works as MS says it does.
The headset button activates voice command, the Beep occurs on the 8525, and the mike on the 8525 listens for input. If I say, Dial ... or Call... then the call works fine on the BT headset like expected.
I know a patch is in the works to fix this issue, and when they do, 1.6 is superior to 1.5 for voice interpretation.
However, for now, I have 1.5 working perfectly fine. All features work, and all I had to do was enter/change 2 registry keys (only 1 was necessary)
xcsdm said:
I have an 8525 also, and 1.6 works as MS says it does.
The headset button activates voice command, the Beep occurs on the 8525, and the mike on the 8525 listens for input. If I say, Dial ... or Call... then the call works fine on the BT headset like expected.
Click to expand...
Click to collapse
So how loud do you have to shout for the mike on the 8525 to hear you if the phone is in the next room, or in your purse or you're driving? It might be the way MS intended it to work, but I doubt it.
[RANT]
I can't believe that MS wouldn't have caught this problem during beta testing. Speaks volumes (pun intended) for the current state of software development and testing at MS. Anyone know if MS Reader works with WM5 yet? How about full multi-user support for ActiveSync? Win XP has been around for years now with this funtionality. And while I am on my rant, how about SP3 for Win XP? Currently we would have to download and install over 70 (!) critical patches to SP2 just to get our computers to the dynamic state they are at today. Come on MS, enough is enough. Get your s#!* together!!
[/RANT]
John
Hi All
I just installed MS Voice Command 1.6 (US) and so far its been working almost perfect. I say almost perfect because somehow when a call comes in, it announces the name of the caller through the phone speakers even though I specifically tell it to announce only through BT handsfree set. I thought that maybe my headset did not support it but the weird thing is that it would automatically read incoming messages through the BT headset. Is there any tweak that I need to do so that I can hear who is calling through the BT headset?
I am currently using an AKU2.X ROM (Dopod's latest) with a Plantronics 640E BT headset. Any help rendered is much appreciated.
I can at least tell you that a Crossbow ROM won't help...
I still get this irritating issue
Sounds like a MS Bluetooth Stack issue
Funnily this is the symptoms described on Microsoft page :
http://www.microsoft.com/windowsmobile/voicecommand/default.mspx
But for HTC Hermes & Palm Treos
Thanks to a forum member I found my mistake !!
Check this post : http://forum.xda-developers.com/showpost.php?p=1112405&postcount=369
sebbes said:
Funnily this is the symptoms described on Microsoft page :
http://www.microsoft.com/windowsmobile/voicecommand/default.mspx
But for HTC Hermes & Palm Treos
Click to expand...
Click to collapse
I guess my problem is listed as "Older WM5 Devices" where the notifications for calls would be routed to the speakers. No fix there I guess.
With the PDAviet ROM it works ok !
Routed to the headset, and even the incoming calls get notified in the same manner
sebbes said:
With the PDAviet ROM it works ok !
Routed to the headset, and even the incoming calls get notified in the same manner
Click to expand...
Click to collapse
Could you tell me more about this PDAviet that you are talking about?
it's a crossbow ROM (beta of course)
Thanks for the headsup. Unfortunately I need the functions of a proper phone and thus unable to use the ROM. Thanks for the heads up.
I see, in fact this unofficial ROM is pretty ok (just a few times when you'll have to reset before it boot up successfully)
Else the phone part is really nice, with a great smartdial (like you have on smartphones, qtek8310 etc) but you're right, it's for people that are not scared by few minor problems
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...