Problem getting Cyberon voice dailer working with BT - Wing, P4350 Herald Upgrading

Hi, I've been searching in this forum and tried most of the solution but still can't get it to work. So I hope somebody can help me out.
I'm using Cyberon voice dailer, I can it to work if I press and hold the # 4 button to bring up the voice speed dialer and either speak to the phone or BT for it to dial. However if I just tap the button on the BT it just bring up the normal dial pad. What I'm looking for is the ability to tap the button on the BT then speak the name and it will dial. Is it possible with the Cyberon voice dalier?
Thanks in advance for your help.

Same Issue
I have the same problem. I have been able to use it before, but I don't know if it is the ROM i am using or not. Using Open Touch 3.0 Biggy. Flashed too many ROM's to keep track when it worked and when it didn't.

joking said:
Hi, I've been searching in this forum and tried most of the solution but still can't get it to work. So I hope somebody can help me out.
I'm using Cyberon voice dailer, I can it to work if I press and hold the # 4 button to bring up the voice speed dialer and either speak to the phone or BT for it to dial. However if I just tap the button on the BT it just bring up the normal dial pad. What I'm looking for is the ability to tap the button on the BT then speak the name and it will dial. Is it possible with the Cyberon voice dalier?
Thanks in advance for your help.
Click to expand...
Click to collapse
Hi,
The 4th hold button is mapped to hot voice record.
In the next release I'm including voice speed dial and MS voice command.
Also,
Please try and post issues with my roms in the original thread when possible, doing so will make it easier for me and others to help you.
Regards,

ttran001 said:
Hi,
The 4th hold button is mapped to hot voice record.
In the next release I'm including voice speed dial and MS voice command.
Also,
Please try and post issues with my roms in the original thread when possible, doing so will make it easier for me and others to help you.
Regards,
Click to expand...
Click to collapse
Hi Tran,
Thanks for your reply and sorry if I post in the wrong place but I don't think it's the problem with your rom. Press and hold the 4th button to activate voice dialer work very good with your rom. I think the problem is more on the Cyberon speed dialer than your rom.
What I would like to do is when using bluetooth, press the button on the bluetooth and it'll activate the voice dialer. Rather than press and hold the 4th button on the wing and then speak to the bluetooth.
On the side note, most of my contacts name is in Vietnamese so MS Voice Command really have a hard time recognize those names. That's the reason why I choose Cyberon so I can record the name tag. It work better than the preset one on MS Voice Command.

Related

MS VoiceCommand and the ROM update...

Hey,
I was using VoiceEnable to use MS VoiceCommand and bypass the built-in voice dialer:
http://www.burling.co.nz/Default.aspx?tabid=151
It worked GREAT on my stock TMo MDA (USA)!!
However, I did the ROM update, and this little wonder no longer works! Moreover, the link seems to be dead; I was hoping there was an update.
===========================
(UPDATE)
OK,VoiceEnable did reassign the headset button, but it didn't reassign the button on the device. So I tried to do this manually using DoubleLauncher <http://www.orthancsoftware.com/DoubleLaunch.htm>. But it didn't show up as an option. SO... to make the short story long, I manually pasted a shortcut to voicecmd.exe into \Windows\Start Menu\Programs\. Then DoubleLauncher allowed me to reassign the device button. WHEW. Mission accomplished.
I was looking at this post and wondering if you could tell me what the application voice enable allows you to do. I looked at the link, but it doesn't tell what the applications functionality is.
Rev.Stanley said:
I was looking at this post and wondering if you could tell me what the application voice enable allows you to do. I looked at the link, but it doesn't tell what the applications functionality is.
Click to expand...
Click to collapse
It modifies a registry key so that Voice Command is invoked when you use your BT headset to initiate a call. If you don't run VoiceEnable (or mod the registry key yourself), when you use your BT headset's button to start a call, the phone will invoke the default built-in voice recognition software - NOT Voice Command.
wgary said:
Hey,
I was using VoiceEnable to use MS VoiceCommand and bypass the built-in voice dialer:
http://www.burling.co.nz/Default.aspx?tabid=151
It worked GREAT on my stock TMo MDA (USA)!!
However, I did the ROM update, and this little wonder no longer works! Moreover, the link seems to be dead; I was hoping there was an update.
===========================
(UPDATE)
OK,VoiceEnable did reassign the headset button, but it didn't reassign the button on the device. So I tried to do this manually using DoubleLauncher <http://www.orthancsoftware.com/DoubleLaunch.htm>. But it didn't show up as an option. SO... to make the short story long, I manually pasted a shortcut to voicecmd.exe into \Windows\Start Menu\Programs\. Then DoubleLauncher allowed me to reassign the device button. WHEW. Mission accomplished.
Click to expand...
Click to collapse
I just used the built-in button mapping facility for this! -
Start / Settings / Personal / Buttons...
Now button 3 (upper right) brings up Voice Command...

Voice Dial via Wired handsfree

Is there a way to activate voice dial via the call pick up button on a wired headset? I thought I had seen a post that a fix for this... but can't seem to find it now. Any help? Thanks.
Is this the thread you're referring to?
New application: Talk Button Detector 0.3
Wow thanks...
Thanks for the quick reply. Yes it was this...

open touch 2.4 and bluetooth profile problem (resolved)

I installed open touch 2.4 and LOVE IT.. it makes windows mobile so much useful..
one thing i found problamatic was the bluetooth profile. The problem is when I press the call button on my bluetooth headset it doesn't trigger the voice speed dial. It just launches the dialler which shows the keypad.
That kind of defeats the purpose of 'hands free' if I need to press the voice speed dial on the phone and then use the headset.
Any solution ? Or any other package I can install to get the full functionality of voice speed dial with bluetooth.
I have the same problem, and it effects the ability for me to use MS Voice Command. I wish someone would help, but I made a post about this and got no replies.
beowolf said:
I have the same problem, and it effects the ability for me to use MS Voice Command. I wish someone would help, but I made a post about this and got no replies.
Click to expand...
Click to collapse
guys,
I'm working on v2.5 and will try to resolve this issue if possible.
I need more details as to what is happening.
Also,
I did not see any of this nature posted in the original v2.2 post.
Who else is having this issue?
hoolahoous said:
I installed open touch 2.4 and LOVE IT.. it makes windows mobile so much useful..
one thing i found problamatic was the bluetooth profile. The problem is when I press the call button on my bluetooth headset it doesn't trigger the voice speed dial. It just launches the dialler which shows the keypad.
That kind of defeats the purpose of 'hands free' if I need to press the voice speed dial on the phone and then use the headset.
Any solution ? Or any other package I can install to get the full functionality of voice speed dial with bluetooth.
Click to expand...
Click to collapse
Just to cover all basis, did you setup the button 5 options?
Remember that I left the 5th button free for people to choose either voice record or voice speed dial.
Going forward, please do not create new post, instead post your issues in the original thread.
Thanks,
I'm pretty sure that what your dealing with is a registry problem. When i switched to touchit 2.3 i had to reconfig to the following:
1 Use registry editor to edit the following entries on your Wing:
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: LaunchAPEnable, Value Data: 1
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: VoiceCmdEnable",Value Data: 0
2. Wait about 30 sec, then soft-reset
Try it and let me know how it goes. I dont get credit for this it is from a previous post. This did work for me tho. I can prompt the voice speed dial from the bluetooth.
ttran001 said:
guys,
I'm working on v2.5 and will try to resolve this issue if possible.
I need more details as to what is happening.
Also,
I did not see any of this nature posted in the original v2.2 post.
Who else is having this issue?
Click to expand...
Click to collapse
Thanks ttran for responding. I have great respect for you for putting together this great ROM.
The issue is..
I am pairing my bluetooth headset (motorola h850) with the phone. After paring, if I press the call button on my bluetooth, it is supposed to invoke the voice dial app in the phone and call the voice tag I spoke. However it just brings the phone dialler screen and does nothing.
My diagnosis
For an incoming call (when paired), I can pickup the call using bluetooth headphone's button. So I know bluetooth instrument is working.
Secondly when I directly invoke voice speed dial from phone (i mapped a hardware button to voice speed dial) it works fine too.
Only problem is I can not invoke voice speed dial from bluetooth headset.
Do not confuse this issue with the hardware button mapping since I am trying to invoke voice speed dial from bluetooth headset (not from hardware button on phone. that works fine)
Please let me know if you need any futher information. I will happy to provide any additional details.
BTW thanks again for putting together such a great ROM.
Hi,
Thanks for clearing that up.
Please try what mrmikemcguire posted:
1 Use registry editor to edit the following entries on your Wing:
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: LaunchAPEnable, Value Data: 1
Under: \HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\, Add DWord Value: VoiceCmdEnable",Value Data: 0
2. Wait about 30 sec, then soft-reset
And let us know if it works for you, I don't use blue tooth so I can not test it for you.
Also,
Let me know if it fixes your issue so that I can add it to the next release.
Thanks folks,
sorry didn't work for me..
Ok.... First, thank you mrmikemiguire . Now hoolahoous .. did we make progress? The Audio gateway should be opening now... Verify that the registry modifications are correct in your device, then power cycle..... there may be another piece to the puzzle but those changes should work.
Edit: Final piece... Verify HKLM,"SOFTWARE\OEM\VoiceCommand "Path" = \Windows\SDDialer.exe
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
hoolahoous said:
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
Click to expand...
Click to collapse
Hi,
That reg fix has been added to v2.5 and yes Voice speed dial is included but not voice command since it takes about 4mb of space.
hoolahoous said:
Okay.. thanks for everyone's help.. I finally got it to work... One thing incorrect in above settings was
\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A udioGateway\, Modify Value data: OEMAGEX.dll to BTAGExtModule.dll
the default entry was VCBTHAG.DLL not OEMAGEX.dll , I missed that..
however when I changed VCBTHAG.DLL to BTAGExtModule.dll , it started working..
ttran001, maybe you can include these entries in 2.5.
I know you are not planning to include voice speed dial or voice command in 2.5, I personally feel that you should include atleast one of them. My vote would be voice speed dial since it works for everyone but voice command works only for subset of people. When I say work, I mean software being able to recognize what a person is saying.
but thanks to everyone including mrmikemcguire to get it to work for me.
Click to expand...
Click to collapse
Yep sorry about that.. I realized that when i did it, same occurance, but forgot to mention it! Sorry about that, but at least you got it squared away. Glad I could at least point you in the right direction.
mrmikemcguire said:
Yep sorry about that.. I realized that when i did it, same occurance, but forgot to mention it! Sorry about that, but at least you got it squared away. Glad I could at least point you in the right direction.
Click to expand...
Click to collapse
Either way thanks for providing feed back so to help resolve this issue.
I am using 2.5 slim and cannot get audio from realplayer, skype, etc.
I push the button and all I get is some wrong application, try again later errors....
Please help.
It all worked perfectly with the Clean ROM so may be someone with know-how can look at the registry differences between them and tell me if this is fixable, or i have to install the clean again...
Thank You!
#13 said:
I am using 2.5 slim and cannot get audio from realplayer, skype, etc.
I push the button and all I get is some wrong application, try again later errors....
Please help.
It all worked perfectly with the Clean ROM so may be someone with know-how can look at the registry differences between them and tell me if this is fixable, or i have to install the clean again...
Thank You!
Click to expand...
Click to collapse
Is this with bluetooth or the actual headset, or headphones?
And is anybody else having this issue?
Yes, BT.
Sorry i didn't mention this important detail.

so now that we all have froyo...

one of the biggest features for me was voice dialing over bluetooth. has anyone figured out how to initiate it?
eric b
im pretty sure you just open the voice dialer app with Bluetooth connected then talk it through the mic.
What did YOU tried e-dub?
EDIT: Sorry, I thought this was a thread to discuss the new features. My bad.
NexusDro said:
Any improvements in the camera and video quality?
Click to expand...
Click to collapse
Wrong thread?
purely by accident... i discovered with my bluetooth (jabra extreme) that if i pressed the action button once, it opened the voice dialer! it's not quite as good as microsoft voice command (winmo people, you remember this), but it's pretty nice.
erix b
e-dub said:
purely by accident... i discovered with my bluetooth (jabra extreme) that if i pressed the action button once, it opened the voice dialer! it's not quite as good as microsoft voice command (winmo people, you remember this), but it's pretty nice.
erix b
Click to expand...
Click to collapse
So solved.
Thx for posting the answer
Yes it works BUT, at least for me the voice dial app doesn't pick up the right name and it FCs right after all the time.
Sent from my Nexus One using XDA App
On my Jawbone Prime, I just long press the talk button. Works great!

[Q] Voice Dialer

What are you using for Voice Dialing on the Galaxy S?
Here is what I want to do ...
(1) Press my bluetooth hands-free button to start up the voice dialer
(2) Phone should ask me to say a command.
(3) I tell it to "Call So and So"
(4) Phone confirms name with me
(5) I say "yes" or "no"
(6) And bingo bongo it dials the number for me.
So you notice there is no touching of the phone ... this is a must ... since where I live its illegal to do.
So far I see there are 3 programs that do voice dialing:
(1) Google Voice Command
(2) Vlingo
(3) Choice Dialer Plus
I have tried them all, but none seem to work right or do all the steps above. Any tips on getting this to work and which app is best on this phone?
Have you tryed Cyberon Voice Commander?
I not have it, but on the net I have read which work well.
Have a good day!
tilallr1 said:
So you notice there is no touching of the phone ... this is a must ... since where I leave its illegal to do.
Click to expand...
Click to collapse
Really....
Hi,
I use Cyberon Voice Dialer (in spanish). It works perfectly with call control button on my Parrot hands-free, and exactly how you want it.
Great ... I will give it a try and see how it goes.

Categories

Resources