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
So I got my hands on a newer version of VC and it work really well on my xv6800 except that its does not announce callers. Isn't VC supposed to do that?
Any idea how to get it to work?
I think mine works, but the voice in general for announcements is VERY quiet! I wish audiopara would also get this loud as well.
Sorry, but I can only tell you thats is extra quiet... Did you ensure that the proper options are checked in the config?
I believe that all the proper options are checked, but I'll look again to make sure. I don't think that the options are independent. I mean if I have notifications going to my BT for appointments and the like, I would think that all notifications would follow the same path. Still, I will definitely check again.
One thing odd is in some of the older versions of Voice Command there was a separate program that was called Voice Command BT which had some setting for bluetooth. I don't see that with this version of Voice Command, but again, I am getting some of the notifications through BT, so I'm sure it has the ability to communicate with the BT.
Can you tell what version of VC it is. I have had mostly success with it but the latest DCD Rom seems to have issues especially if I install the pay for package that I paid for. If I cook it in it seems to work most of the time. Sometimes I have to reboot to get it to recognize my commands.
Voice Command after MR1 update
After I updated using the MR1 release, voice command seemed to work better than ever. What I noticed though is that now it will not announce incoming calls. Announces everything else, but refuses to work on calls. I ended up installing a ripped version (19214) and just need to perform the bluetooth volume regedit.
I have a paid version that I bought 2 years ago to use with my 6700.
It did NOT work at all with the MR1 update or with the 6800 before the update.
I looked online and found a version 19209 and tried that one. All works perfectly!
except one thing. It will not read sms msgs anymore, but I can live with that. Notifications works (except sms), confirm works through bt, it is loud enough to hear who is calling....
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
I have a problem and have't been able to find any information on it. I have a TMoUS HD2. I had an original Jawbone lying around so I paired it and it works perfectly. I decided to pick up a Jawbone 2. I paired it, but it developed a problem. While outgoing calls are no problem, I cannot answer calls with it, nor can I initiate voice dialing with it. Incoming calls are routed through the handset. I deleted the pairing, and re-paired it to no effect. I also tried the original Jawbone again and it again worked fine. What I don't understand is why it initially worked properly, then developed this problem (with no changes to the phone).
Any ideas?
me too
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
mcc2905 said:
Same problem with Proplantronics headset, new to me handset formerly T-Mobile just loaded this ROM:-
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
If I find the answer I will let you know.
Click to expand...
Click to collapse
well, it was probably me. I was answering with the handset rather than the earpiece. it didn't matter with the old one, but it does with this one. chalk it up to unfamiliarity with the newer unit. either that or the phone woke up in a better mood today.
sorted
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
mcc2905 said:
Yes, thanks for that, pressing the call control on the headset is the answer, also found the autoanswer option which should also fix it. Lots of stuff seems to be hidden away on 6.5.
Still learning after all these years.
Click to expand...
Click to collapse
Glad my fumbling around with this thing was able to help someone.
Anyone have any way of making calls via bluetooth on Froyo yet or is this not gonna happen for us epic owners??? WTF is the deal with this???
Anyone? am I the only person that misses this basic function??. lol..
HELP!!!!
After installing newest voice search (voice actions) in DK17, this worked for me... however, after upgrading to DK28 it no longer works. WTF?
Yeah my jawbone also doesn't work for voice dialing, but worked fine on my old pos "dumb" phone.
Sent from my SPH-D700 using XDA App
Please post questions in General section.
greezestain said:
Yeah my jawbone also doesn't work for voice dialing, but worked fine on my old pos "dumb" phone.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I am having the exact same problem. I called Jawbone, and they have had problems with samsung. my jawbone worked with voice dial on my EVO with 2.2 no problem. I am wondering if there is a fix for this that the devs can tackle.
I hope someone gets this fixed. Its really annoying that a phone so "advanced" cant do what my old ass pos flip phone could do like 8 years ago. lol.
obrienmd said:
After installing newest voice search (voice actions) in DK17, this worked for me... however, after upgrading to DK28 it no longer works. WTF?
Click to expand...
Click to collapse
I never had this working even with the voice update. I have the Plantronics Voyager PRO Headset. Has anyone else ever had voice dialing working???
xeonbuilder said:
I never had this working even with the voice update. I have the Plantronics Voyager PRO Headset. Has anyone else ever had voice dialing working???
Click to expand...
Click to collapse
It worked for me on DK17 (Quantum before 2.0) but not on DK28 (Quantum 2.0 & 2.1 - haven't tested newer yet). I asked in the Quantum thread if any known changes may have affected it (& audio out from the Samsung docks) but got no response.
xeonbuilder said:
I never had this working even with the voice update. I have the Plantronics Voyager PRO Headset. Has anyone else ever had voice dialing working???
Click to expand...
Click to collapse
I have a Voyager Pro and I use Vlingo for voice dialing over BT.....that's the simplest solution I have found so far.....
I would also be interested in getting this working in froyo, or at least understanding what makes it work in DK17. Anyone having this issue I promise you its not your headsets, it the roms.
I pulled all the bluetooth apks and the voice dailer apk from the /system/app in quantums 1.5(working BT-voice dailing), and then pushed them to /system/app in various dk28 roms I had installed, with no luck. It didn't brake anything, but it didn't enable BT-voice dailing.
My guess is there is a lib file missing, dk17 has a bluetooth apk that isn't present in any dk28 roms, "BluetoothPBAP.apk" in /system/app. Its the apk that I think may need a lib or other associated files.
I ended up going back to di18 for now due to the current froyo bug causing failed call connects. I make calls all day long(i know its strange, but I for one use my phone as a phone =D), and I was getting 15-20 failed call connects a day on froyo and it was driving me crazy.
Perhaps someone else can push the dk17 files to a dk28 roms, do some debugging and see if its a missing dependency and if so, which one.
PS, interesting that vlingo allows voice dailing over BT, i'll have to try this one di18, would love to have that functionality.
ps
Here the download link for quantum rom 1.5(the last dk17 verson)
http://www.nomie.mobi/roms/QuantumRomv1.5.zip
cheers
PS, interesting that vlingo allows voice dailing over BT, i'll have to try this one di18, would love to have that functionality
Click to expand...
Click to collapse
I thought is was strange also, later i'm going to look in Vlingo and see what's in it I can make it work on Viper Rom. (best out there, thanks to Viper team) As I said i'll report back when I get time to do it.