Database Users

Microsoft Voice Command

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

MSVC 1.6 notifications - help (Microsoft Voice Commander)

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

Bluetooth Voice Dialing for the Android OS

Does anyone know if there will be any progress getting bluetooth headsets to voice dial with the Android OS? From what I've seen, Google has been very lax in pushing forward with this much needed capability. They have not even added it in version 2.1.
Is there any way that a workaround can be implemented? I have been holding off getting an Android phone for this very reason.
I apologize if this topic has been posted elsewhere.
Alex

Try Voice Dialer HF. Not perfect but works very well.
http://www.dfxmobile.com/voicedialerhf

blazingwolf said:
Try Voice Dialer HF. Not perfect but works very well.
http://www.dfxmobile.com/voicedialerhf
Click to expand...
Click to collapse
Interesting, but i'm not able to found it in market...... any ideas?
Tia
Idk

The Verizon Devour and the Canadian Droid on Telus, called the Milestone, have Bluetooth initiated voice dialing by a company called Nuance. The built-in Android/Google voice recognition has had it's BTVD disabled because it only doesn't perform well with a Bluetooth headset but is apparently adequate with the phones mic. I wish someone would use the ROMs from those phones to add this feature to the Droid or Incredible but so far no one has. It'd even be cool to see if someone could compile a ROM for Android that flips the switch in the code just so people can try it out. Or better yet, fix whatever problem there is with the quality of Bluetooth voice so that the built-in Android voice recognition could handle it. Man, I want to get rid of my Devour but I can't until I can safely use these killer phones in my car.

The built-in Android/Google voice recognition has had it's BTVD disabled because it only doesn't perform well with a Bluetooth headset but is apparently adequate with the phones mic.
Click to expand...
Click to collapse
This whole issue is like deja vu for those of us that were old-timers with Windows Mobile, which also didn't support VD via the BT headset. And ironically, the excuse given by Microsoft was exactly the same: that voice quality wasn't good enough for voice recognition when using a BT headset. However, MS somehow managed to magically solve this -- voice dial via BT is now supported in WM and works great.
So I have to think that Google's bright engineers could do the same thing if it became a priority. It's obviously not, and won't be unless users really start complaining loudly enough. That's exactly what it took to get action from MS, too.
Sent from my Droid using Tapatalk

[Q] Bluetooth issues with Froyo

So I flashed to a froyo ROM over the weekend and have found someone posted a fix for the gps issues, but I'm having BT issues as well. Has anyone else experienced this: I can pair certain BT accessories but not others, and even when paired the devices cannot connect without multiple connection requests.
My specific issue is that I have motorola rockr bt earbuds, and a Jabra car kit, and they both pair with the phone (after a few trys) but neither will automatically connect to the phone once they're turned on. With the earbuds I have to manually try to connect 6 or 7 times in a row before they'll connect, and even then they may only connect with the phone audio only. This wasn't an issue with the stock ROM so I'm assuming its the bt radio library for Froyo thats the problem?
I'm not new to development, but I'm kinda new to development on Android. I've been trying to learn more about the radios and how they're configured within the OS but I haven't found a lot of good documentation on it. I'd be happy to work this out for myself and post any improved radio to the forum but it would be helpful if someone could send me a link to some learning material? If someone has an improved Epic Froyo BT radio to flash that would be helpful as well

yes bluetooth issues as well, but different in that only when i turn bluetooth on it foreclose's. the bluetooth is otherwise not affeceted. only on the initial start up.

I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!

Delta1Fox said:
I've been having issues as well, but also mine a different. If I walk away from my phone and it get disconnected I manually need to re-establish the connect. Also sometimes the A2DP stops working requiring a reboot. And I've NEVER been able to get Bluetooth voice dialing to work on Froyo for the Epic. I had 2.2 running on my Hero before I switched phones and it worked great.
I am in no way a developer, but I do prowl this site everyday, so unfortunately I can't help with fixing it. More power to you and I hope you (or somebody) gets it worked out!
Click to expand...
Click to collapse
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.

revjtanton said:
I had the Hero before the Epic as well and but I never tried 2.2 on it. I had BT issues with the Hero, but I didn't bother too much with it.
I had the same BT issues with the stock ROM when walking away, having to reconnect after coming back. Voice dialing never worked with BT either. I was hoping for an improvement with the upgrade, but I'd settle for what it was before. I'll start tinkering but I'm not sure what I'm doing with the radios....I'm a developer, but not an Android developer.
Click to expand...
Click to collapse
I noticed that too with the stock 2.1. However, Bluetooth voice dialing is a feature built into 2.2. I've read that some people having it work great, but other's like myself, are not having it work at all. Oh well. I'll live for now. Hopefully if it isn't fixed beforehand then it'll be fixed with the "official" release. LOL.

now that you mention it, i had this problem too doing some bluetooth file transfers between my buddy and I's phones last night. it struggled to connect multiple times but after the first successful transfer it seemed to stop having problems for a little. I'm moving back to 2.1 until we get some non-beta custom roms for froyo because i use bluetooth and gps everyday. just out of curiosity though, for those who are having problems, which rom and modem are you using?

I put the DI18 modern on there and that has seemed to fix the gps more or less. I think I'm going to go back as well. Maybe I didn't flush data enough times but layar can't find the camera, neither can the bar code scanner...it's close, but Froyo just isn't ready for the Epic yet.
Sent from my SPH-D700 using XDA App

Still having Bluetooth problems with official Froyo release on Epic 4G
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...

I am using the new official Froyo release from Samsung/Sprint. having the same buggy issues I had with the old leaked version.

donkeysauce said:
I was also having glitchy issues with BT oo my Epic running the leaked build of Froyo. I ended up flashing back to 2.1. The problem I was having was when I turned on my Motorola Finity, it worked fine.. for one call...) Then it wouldn't work again unless I turned the headset off and back on again. To make matters worse, after using BT one time, All sounds including ringers and media, came out of the earpiece instead of the actual ringer/speaker on the back of the phone.. Strange, huh? I had to reboot the phone to make it normal agian. Now to my surprise, after installing the newly released official Froyo build, I am having the same problem. Is anyone else having an issue like this with the official software? I am going to try the headset on another Epic at work, maybe its just a compatibility issue with my particular headset, but its very strange...
Click to expand...
Click to collapse
I can confirm these issues still exist in the official release.

I'm having the same problem, but when I use bluetooth in my car, it insists on transmitting sounds to my car's bluetooth, even when I repeatedly uncheck Use for media audio. I don't have an option in my car to disable A2DP. My only complaint with Eclair, other than speed (I'm using Bonsai4All, and previously, Syndicate) was that I was running out of space for software (was using EpicExperience). Sometimes, bluetooth won't connect at all, necessitating a phone reboot, or going into airplane moe and then back out. So I'm gathering that this is across the board, regardless of Froyo build? Syndicate didn't work at all with my car.

Is There Any Fix for the Bluetooth Voice Dialing Crash Issue?

I've never seen a dedicated thread on this but I've seen people make off-hand comments about this issue from time to time. I think it started happening in Tytung R9 and higher kernels.
I am using a BlueAnt T1 Bluetooth headset. It pairs just fine and I can use it generally without any issue.
The problem comes when I use voice dialing to initialize a call from the Bluetooth headset. It connects to the phone and I get the normal Android "Speak now...." I speak my command "Call <person> on <service>...." It states the command back like normal and then _as soon as_ it switches to the phone app (eg, com.android.phone process) it locks up the phone and the only way to recover is to pull the battery.
If, instead, I go to the phone app, find the person, and call them that way (even with Bluetooth paired) it _always_ works without any problems. This isn't a long-term solution for me because I need to use voice dialing when I'm in my car.
Now that GPS looks to be fixed and CLK data over PPP is much more stable, this Bluetooth issue is the last thing standing between me and treating the HD2 as my full-time native Android phone (currently I tinker on the HD2 but use my Nexus One as my daily driver).
I've tried multiple different ROMs, from HyperDroid-CM7, HyperDroid-GBX, Typhoon CM7, and Nexus-HD2-Gingerbread. They all have the same issue though Nexus-HD2 appears to be worse than the others (that is, the problem happens more often there).
I've used the infamous audio.conf update as well as the various no-wonk and libaudio patches and none of them help this issue.
Anyone else experienced this and have any feedback on how you overcame it?

I have the same kind of problem and tried a lot of different ROMs - not help.
I tried Blueant ST3, Motorola t305.
Phone book copied to blueant very well, but voice dial has same simptoms like yours - even if phone does't hang sound goes away from phone permanently(needs reboot). Is there any other ROM which works well with bluetooth hadsfree?
Any one?
P.S. Looks like it is real problem, but non of developers pay attention to it - they just don't have handsfree maybe

Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...

clio94 said:
Ι think that sense roms doesnt have this issue.But unfortunatelly they have other issues...
Click to expand...
Click to collapse
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....

This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).

svet-am said:
I've not actually tried a SENSE-based ROM but I understand from my research that they don't have the BT issue. Maybe it's possible to look into their architecture to understand what is different.
I expect that it's something in the kernel....
Click to expand...
Click to collapse
I think it is not the kernel, same kernel will crash in CM7 but no in CM6. I think the problem is related to the libaudio.so and other libs in system/lib.

robrob777 said:
This is a very common issue. if it helps, BTvoice command works Fine in Froyo.. at least CM6 (I tested).
Click to expand...
Click to collapse
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"

svet-am said:
are the Froyo-based builds still being maintained. I ask that from the perspective of "could I just use a Froyo build as my daily driver instead?"
Click to expand...
Click to collapse
I'm using it as my daily driver (CM6), I came back just bc of the calling issues in Gingerbread.
the build that I'm using has not been updated since Jan 7, however I applied around 10+ patches and now it works as good as the new builds.

I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.

robrob777 said:
I just tested again voice command.
No problems
During the voice command call I can switch from BT to speaker to audio piece, back to BT etc, no problems. Audio doesn't crash after call.
And no 60ma battery drain. it is around 5ma after the call with BT on.
Click to expand...
Click to collapse
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.

i just verified the problem exists in MIUI as well. I tested MIUI since it's allegedly a "clean room" type of build environment.

svet-am said:
just for clarity for other folks reading this thread, I assume that you're talking about a Froyo-based ROM.
Click to expand...
Click to collapse
Yes, I tested successfully in a Froyo based ROM.
I went back for a moment to CM7 and tested...sound couldn't return to the phone after calling with BT, also during the call I was not able to switch to speaker phone like I do in the froyo based ROM.

Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.

zcdg said:
Tested with Tytung 1.9G Froyo - BT works just fine in all ways. Just need to keep GPS off(when not used) to avoid 60 ma current draw.
Tytung says BT Voice dail is just GBread problem.
Click to expand...
Click to collapse
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.

svet-am said:
It works fine on my Nexus One on Gingerbread, so I don't see how it can be a "gingerbread problem." If it was a "gingerbread problem" other devices would be seeing this as well.
Click to expand...
Click to collapse
Yes you are right. It is just what Tytung said(i asked in his thread). Probably he meant GB for HD2....Soon or later they will figure it out i think...
For now will use Froyo 1.9G....

tytung said:
I don't have any Bluetooth headset.
AFAIK, some people have the sound issues, e.g. causing the phone app FC, since using Gingerbread 2.3.4.
But it doesn't affect all people, I don't know why.
No solution so far. To use Gingerbread 2.3.3 instead if you are one of them.
Click to expand...
Click to collapse
I finally found Tytung's exact quote as to why he won't look into the issue. It can be seen in context over here: http://forum.xda-developers.com/showthread.php?t=905060&page=524#
So, it might not be Froyo that's the fix but rather older versions of Gingerbread as well.

i have found a workaround fix for this bug.I tried it in tytung`s v2.9 rom and in dorimanx cm7 light rom with driztee v2 libaudio file.For bt voice commands i am using cyberon voice commander because google app doesnt support yet greek language
i connect my bt headset (motorola h300) and then i use super bt mono froyo free app https://market.android.com/details?id=com.steven.supermonofroyofree&feature=search_result to send audio to bt headset.
After pushing the bt headset button cyberon voice starts and i can give the command i want.After giving the command, audio goes back to the phone (you will hear a beep from phone speaker).The weird thing is that the audio is in extremely low level for hearing music but when you receive a call it is in normal level.
If i close super bt mono froyo app,audio returns to phone in normal level.
But if i accidentally (after i close the app) push the button for voice bt command,audio will disappear.
If the app is on and you receive a call,all audio will go again to bt headset and to return it to phone speaker after end call, i push bt headset,cyberon voice starts and i dont give any comand.After cyberon ends,audio goes back to phone with low level for media hearing.
Sure this isnt the perfect solution,but the important thing for me is that with this way,audio is not go away and i can give bt voice commands.
Also i tried bt mono app http://forum.xda-developers.com/showthread.php?t=950472 and it have a little different behaviour.I cant start from bt headset cyberon voice comander,but only from the phone and after giving a command,audio returns to bt headset if you have enable the setting "restart after call".So i think it maybe be helpful to people who want to have audio all time in a bt carkit.

Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.

zcdg said:
Tested all 2.3.3 from Tytung - last working with r8.3 kernel. r9 and up not working.
So NexusHD2 v2.5 NAND(GB 2.3.3) with r8.3 latest working with BT voice dial ROM.
Click to expand...
Click to collapse
thanks for that follow-up and testing. I was wondering if whether or not it might be a "fault" in the VoiceDialer.apk or even in the Phone.apk. I have been using my Nexus One for daily stuff. I might try replacing VoiceDialer and/or Phone.apk in a newer ROM (eg AOSP 2.3.5 or so) with the old version and see if it works.

Ive wondered about this as it is to me the last issue I have with my HD2. Here is a search link for some entries in Tytungs rom & kernal thread...
http://forum.xda-developers.com/search.php?searchid=86308155
Also here is a comment from the man himself...
http://forum.xda-developers.com/showpost.php?p=15996942&postcount=5953
and here is a post in reply that talks about the same issue being replicated using Bluetooth...
http://forum.xda-developers.com/showpost.php?p=15997234&postcount=5956
Some more chat about the sound issues...
http://forum.xda-developers.com/showpost.php?p=16113973&postcount=6045
Another thread with logcats on it...
http://forum.xda-developers.com/showthread.php?t=1060486