PDA

View Full Version : Microsoft Voice Command 1.6 - ISSUES!


spanky310
19th November 2006, 06:28 PM
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?

skygear
19th November 2006, 10:30 PM
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

spanky310
19th November 2006, 11:16 PM
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

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!

goestoeleven
20th November 2006, 02:05 AM
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...

spanky310
20th November 2006, 05:18 AM
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...

I see. Thanks for the info. Hope the patch will be available soon!

jcrompton
22nd November 2006, 02:32 AM
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".

goestoeleven
22nd November 2006, 03:13 AM
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?

mrderby
22nd November 2006, 05:04 PM
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?


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 :p

Mark (NL)
22nd November 2006, 05:21 PM
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 :p

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!

MickKnatterton
23rd November 2006, 09:25 PM
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...;)

digitalfx
23rd November 2006, 10:30 PM
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...;)

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.

jcrompton
23rd November 2006, 10:40 PM
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?

goestoeleven
24th November 2006, 02:35 AM
@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.

RikR
24th November 2006, 04:22 AM
VC 1.6 works fine on my MDA with Motorola BT headset.

adisor19
24th November 2006, 06:25 AM
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!

Seriously, why dind't any OEM use the Widcomm stack instead of the crappy MS one ?! :mad:

If only there was a way to hack the Widcomm stack and replace the MS one like they did with the Dell axims..

Adi

ercave1
25th November 2006, 01:56 AM
@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.

Has anyone tried this... (look for the cab)

http://forum.xda-developers.com/showthread.php?t=283412&page=5

URPREY
25th November 2006, 03:17 PM
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.

rsolomon
25th November 2006, 04:02 PM
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.

Wow! Have you done any registry hacks? I'd love to see what your Voice Command keys look like....

TIA,
Richard

xcsdm
26th November 2006, 06:04 AM
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)

johnburn
26th November 2006, 03:22 PM
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.


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.



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!!



John

jasjamming
26th November 2006, 03:34 PM
Seriously, why dind't any OEM use the Widcomm stack instead of the crappy MS one ?! :mad:

If only there was a way to hack the Widcomm stack and replace the MS one like they did with the Dell axims..

Adi

http://forum.xda-developers.com/showthread.php?t=284329

rsolomon
26th November 2006, 04:04 PM
I have an 8525 also, and 1.6 works as MS says it does.

AFAIK, MS only "said" that BT headset support equalled use of the built-in mic and speaker on the Hermes *AFTER* customers determined that bug existed. On other platforms, I understand BT headset support works as any normal human being would expect - using the BT mic and speaker for recognition *AND* for the call.

Folks from Handango have implied a patch, many folks here have wished for a patch, but I've seen nothing official from Microsoft or HTC indicating any such patch is in the works. I certainly HOPE Microsoft will fix the problem, but I'm not personally going to hold my breath!

Richard

rsolomon
26th November 2006, 04:06 PM
Anyone know if MS Reader works with WM5 yet?

FWIW, I have MS Reader v2.4.1 downloaded in the last week or two from the MS site running on my 8525, so I'm gonna go with "yes" on this one ;)

Richard

xcsdm
29th November 2006, 06:30 PM
A patch is available that helps MS VC 1.6 work with the Hermes series devices

http://forum.xda-developers.com/showthread.php?t=283412

Check around Page 8/9
Version 0.8a is currently the latest

Zeekone
15th December 2006, 02:45 PM
Guys is there a registry to loud the voice command sound in my jasjar ive the VC 1.6 Please Guys Help

esene
21st May 2008, 11:07 AM
I have also VC 1.6 I used to use 1.5
I have installed to my HTC touch cruise and use it with Motorola H700.

You may use the button with changing the following string in registry;
edit the registry with resco reg.editor:
HKEY_LOCAL_MACHINE\Software\OEM\VoiceCommand
if there is a string named "path" already change the string to ;
\program Files\Voice Command\voiceCMD.exe
or if you do not have this string named "path" then just simply add the the string and name it "path" with the values just given above.

After doing this you will be able to have the voice at your BT headset as well as you will command through your BT head set but neverthe less it does not work perfectly depending on your BT headset.

Having BT button working do not solve every thing; I have just learned that the BT sets are 8Khz and the voice command is 16Khz. therefore it does not work properly or works only for a while then stops. please check the link;

http://blogs.msdn.com/windowsmobile/archive/2006/02/03/524289.aspx?

so I am re-installing VC 1.5 today if it is ok let you know?