Hi all !
I have a very strange problem with BT headset.
The activation of Cyberon Voice Commander was working fine, but i do not like it and decided to replace it with old-good Cyberon Voice Dialer 1.1.
Uninstalled Voice Commander, installed VoiceDialer, tweaked all registry keys for the button and all works fine.... except... Sddialer activation with BT headset button - when i push it, the Phone dialer starts... strange... Anybody had this kind of problem ?
Please, advice !
Sounds like you put in the wrong value somewhere in the registry, but it could be the most obvious problem, in the buttons configuration the button is set to "Phone". If you haven't checked the button assignments check that, if that's not it, it should be in the registry, I can't remember the key right now, but check around and see.
masr1979 said:
Sounds like you put in the wrong value somewhere in the registry, but it could be the most obvious problem, in the buttons configuration the button is set to "Phone". If you haven't checked the button assignments check that, if that's not it, it should be in the registry, I can't remember the key right now, but check around and see.
Click to expand...
Click to collapse
The HW Hermes button assignement is fine. It shows all fine in Button Settings as well as it works fine. Strange thing is that the SDDIALER starts when i push the button on my BT headset, but nothing is transmitted via BT (both ways).
In that case check in the registry in "HKLM\SOFTWARE\OEM\VoiceCommand" and check to see what it says there, but just to make sure am I right in assuming what you mean is that when you press the button on your BT headset, the regular phone dialer comes up? I hope I didn't missinterpret the situation.
My registry looks like:
HKLM\SOFTWARE\OEM\VoiceCommand
(Default) (value not set)
LaunchAPEnable 0x1(1)
LaunchByExe 0x0(0)
Path \Windows\SDDialer.exe
VoiceCmdDuration 0x78 (120)
VoiceCmdEnable 0x0 (0)
With inbound calls everything is fine - i push the button on BT gheadset and all works.
With pushing the button on my TyTn it is all fine - the Cyberon Voice Speed Dial starts and works fine (using internal TyTn microfone)
With pushing (and holding) the button on BT headset i have the Phone application starts (the one that you have when press the green phoneset button on the device) and nothing happens after.
What could be the reason ?
It's strange as everything seems to be right, and usually the problems are that if you press the talk button on the headset the phone will not recognize it, I had yet to hear of the phone dialer popping up. Well I'll try looking for something if I have time since curiosity is my weakness. You should also try looking thru threads that deal with voice command and bluetooth headsets. What type of headset are you using by the way. If all else fails mayb you should consider doing a hard reset.
I would like to do that too
How to get the old voice speed dial?
Tx
Eric
Eric Duprat said:
I would like to do that too
How to get the old voice speed dial?
Tx
Eric
Click to expand...
Click to collapse
Take it from here - ftp://xdaupload:[email protected]:21/Universal/CVSD/Cyberon Voice Speed Dial v1.1 build 507271.rar
Then
1. uninstall the current Cyberon Voice Command
2. Install Cyberon Voice Speed Dial
Good luck... I still cannot use it via BT.
Related
as abov has anyone found a way of doing this in running in basic mode using a jabra bt 250v and would like to get the tt5 voice through the headset im probably missing something very simple
Is that supposed to work?
I've found the following works, but it is a bit of a bodge. Replace the VoiceDialler registry entry with the one that loads MS Voice Command (see elsewhere in this forum). When you press the button, Voice Command will startup with its double beep noise. However, unlike the VoiceDialler software, Voice Command does not release control back to the EXEC until you press the headset button a second time. And if you don;t release control, all the EXEC's audio will play through your headset.
I'm not even sure you would need Voice Command, you could probably enter a nonsense path in the registry.
Give it a go and see what happens.
Voice dialing from bluetooth works fine while my K-Jam is on, but when it goes into standby mode it doesnt work. I press the button on the headset and I get the headset beep indicating it has connected, but I never hear the speed dail beep. If I bring the K-Jam out of standby mode, I can see the speed dial program is on teh screen, but it seems stuck. Maybe any ideas?
Thanks, John
All Wizards suffer from this; currently no known way around it, hopefully a update will cure this issue or someone will find a way.
A little more digging and I have seen where others have tried to find a work around. Here is what I am doing for now. I am turning off automatic standby and using the "device lock" to keep buttons from accidentally being pushed instead of putting it in standby by pushing the power button. I am not sure what the battery usage will be now, but I will test it for awhile and see. By the way, does anyone know how I can assign one of the hard buttons to device lock? Is there an exe somewhere or can someone point me to a registry entry for this?
Thanks
haven't found keylock yet, but found "power off"
may create a short cut in programs?
My Qtek does not have this problem.
I'm using voicedial from my bluetooth headset. It works perfect even when the phone is in standby mode! It wakes up and makes the call perfectly!! I have a Qtek 9100 and a SonyEricsson HBH-662.
same here with my dopod 838 and HBH-662 it seems to work nicely even if the device is in standby. Is this because of the headset?
::adit
No problem here either...
Dutch MDA Vario + HBH-662 headset - works like a charm standby or not.
By the way... why bother installing MS Voice when the Wizard comes with it's own voice dialing utility?
lisa1982 said:
By the way... why bother installing MS Voice when the Wizard comes with it's own voice dialing utility?
Click to expand...
Click to collapse
Probably because MS Voice Command is based on speaker independent recognition. So, you don't record a voice tag for the few contacts you dial most often, you just say 'call <contact> at|on mobile|home|work' and it will try and recognise the contact from your entire list.
Also pretty cool for casually pressing the button and asking 'what appointments do I have today' and having the details and locations read out to you...
Dox
lisa1982
OEM voicedial does not allow you to dial by digits 5-5-5-1-2-3-4 etc OEM voice dial is limited to voice tags MS Voice Command allows you to dial any contact in you're list also the ability of MS VC to announce upcoming appointments etc.
There are more these are only a few examples.
Can you guys that are able to make BT calls from standbye mode post what rom etc you have installed?
Thanks, John
Question for all you guys with the SE HBH-662 headsets. Does the caller ID on the Headset work? Meaning when you get an incoming call does it scroll the phone number only or does it display the name of the contact (if you have them in your contacts)? And how is the battery life of the headset ? I've got a Motorola HS850 which I love but I'm having the same problem with voice dialling from Standby and am willing to buy another headset if it works.
Thanks.
Hi firas,
Only the number is displayed in a scrolling fashion and it has a good battery life. Highly recommended
I have the HBH-600 but dont think it would work any different with another headset. My K-Jam receives the signal, and beeps, but seems to get stuck after that. When I take it out of standbye after trying it, I see the voice app is open, but seems to be stuck. If another headset will fix the problem, I would gladly buy it.
John
techspy
My HBH-660 does the same thing as your's I may go ahead and get the HBH-662 and try it thogh, if it will fix the issue that would be great.
marka2k said:
All Wizards suffer from this; currently no known way around it, hopefully a update will cure this issue or someone will find a way.
Click to expand...
Click to collapse
One method that does work is to use the "redial" function on your headset. On my HS850 it's press and hold the call button. The Wizard _will_ wake up and start dialling your last used number. Just tap the headset button again to cancel the call, and you're ready to use Voicedail.
Initiating a redial then cancelling it to get the phone to wake up is a work around but not a fix. I hope they resolve this or if the HBH-662 does work I wonder what the difference is?
marka2k said:
Initiating a redial then cancelling it to get the phone to wake up is a work around but not a fix.
Click to expand...
Click to collapse
Thanks for your constructive input and for stating the obvious :roll: I was simply correcting your statement that there is "currently no known way around it" which is not true. All it takes is two extra button presses.
Tried my new Wizard last night with my old Plantronics M3000 bluethooth headset, Device was in stanby and when i pressed the button on the headst it woke up and voice dailed no problems.
I am using the standard T- Mobile roms with the MDA Vario as it is only a day old.
Hope this helps
Hello, Anybody succeded in activating voice command by pushing on the standard talk button of the QTEK headset? i understand there is a solution for bluetooth devices, but i tried with the standard headset and apparently it doesn't work...i am using the fantastic 2.8 ROM....
i am also intresseted to do that.
Did anyone found a solution?
It seems that the standard "Talk" button on Qtek's headset is only good for picking up incomming calls. It is not similar to voice button on the device. I've desperatly searched for registry keys to change that.
Did anyone have any luck?
Thanks,
Rostylsav
This didn't work for me, but it's easy to roll back. Pasted from Howard Forum.
Originally Posted by tbrown801
I have seen several posts about accessing Voice Command over your Bluetooth headset. I have been able to do this succefully with just a couple of steps.
First:
goto "HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path". Change the default value from "\Windows\SDDialer.exe" to "\Program Files\Voice Command\VoiceCMD.exe".
Now you should be able to activate Micrsoft Voice Command by pressing the connect button on your bluetooth headset. My Scala headset beeps twice when it's ready for the Voice Command. My husbands Motorola headset beeps once when it's ready for the Voice Command.
Then you can also enable your bluetooth headset to receive music and other sound from your MDA by running the tweak "Enable Bluetooth Receive" using the Registry Wizard Program.
@glee719: This paste you did is about using Bluetooth headset for voice-dial.
The question is about the standard headset that goes with the Wizard . . . .
afaik the push-button on the headset works similar to the 'hook' buttons (green & red). Those do not trigger voicecommand either . . . .
glee719 said:
This didn't work for me, but it's easy to roll back. Pasted from Howard Forum.
Originally Posted by tbrown801
I have seen several posts about accessing Voice Command over your Bluetooth headset. I have been able to do this succefully with just a couple of steps.
First:
goto "HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path". Change the default value from "\Windows\SDDialer.exe" to "\Program Files\Voice Command\VoiceCMD.exe".
Now you should be able to activate Micrsoft Voice Command by pressing the connect button on your bluetooth headset. My Scala headset beeps twice when it's ready for the Voice Command. My husbands Motorola headset beeps once when it's ready for the Voice Command.
Then you can also enable your bluetooth headset to receive music and other sound from your MDA by running the tweak "Enable Bluetooth Receive" using the Registry Wizard Program.
Click to expand...
Click to collapse
Sorry to tell, it is not working for me, if i create a shortcut with "\Program Files\Voice Command\VoiceCMD.exe", and click on it, the voice command will lunch, however, putting the path in the reg, soft reset, press on buletooth handset doesn't work, any idea ?
By the way, how can we Set the microphone gain on the Wizard ? and how can we set the voice command to talk more and more louder ???
Yeah i'm interested to know how to make full use of the given headset, as i use it to listen to mp3 alot. The 'talk' button looks useless other than answering calls, unlike the w800i headset.
@rookery, this is NOT about the BT headset to activate VoiceCommand
Oh Sorry, did you mean the 2.5mm handfree, I don't have it in hand, does it work by the changing the reg key ???
hi to All,
useless to say i already tried the registry change for BT, and it didn't work for the STANDARD headset that is connected through the 2.5 mm jack. maybe, it is simply not possible.....
Is there a key for Talk button in the registry?
Does anyone know if there is a key for "Talk" button function in the registry?
We know there is one for BT headsets, but what about the conventional headset which comes with the device?
Anyone figure this out yet????????
Thanks
I use a SonyEricsson Bluetooth Headset HBH-PV705 with the TyTN.
It works fine so far, when using the phone.
But I want also all sounds to be played via the headset, so that I can use Skype with the headset.
Therefore I disabled the voicedialing-software (Cyberon Voice Dial) with the BLUETOOTH VOICE COMMAND OFF Hack.
The Voicedialing does not start anymore, when I push the button on the headset and I can here, that audio is completly redirected to the headset.
However after 10 seconds the headset disconnects again and audio is played via the speaker again.
I tried several headsets already!
Does anybody have an idea whats going wrong here?
Thanks so much!
I haven't searched through hear yet, but I have a similar problem, just lasts longer then 10 seconds before it switches back. and for some reason voice command doesn't initialize (though i haven't tried the whole process again)
Does really no one know that problem? Does redirection of audio to a headset work on your TyTN?
BT stereo earphones & annoying voice command bug
Check this post:
http://forum.xda-developers.com/viewtopic.php?p=354050&highlight=#354050
ulischultz, I found the reg hack for voice command didn't work to correct this either. This BT/A2DP situation is a known bug, hopefully to be fixed with ROM update.
Hi guys can you make a test with the trial version of this software and se if it solves the problem:
www.teksoftco.com and download the trial version of BlueMusic from the product section. A detailed description on how to install and how to use it on the website.
Cheers,
Raul
That looks very nice, but does not have any effect!
After 10secs the sound is switching back to the speaker!
The problem is than at a lower level so i think it should be fixed with the next RUU .
This means that it worked on your tytn?( i mean that it routed corectly the voice)
Cheers,
Raul Tinca
No, it did not. It seemed to activate the headset somehow, because I was able to hear some noise, but the sound was still played via the speaker. Only after pressing the button on the headset, the sound was redirected, but only for 10secs.
Where can I get the RUU-Update, and how will I be informed about it, when it arrives?
"the sound was redirected, but only for 10secs"
this is what i wanted to hear
Seems like if they fix the bug in the rom the software would run on the tytn also (after pushing once the headset button - as presented in the help file there are devices that need it to be pushed and some that don't).
Cheers,
Raul
use the btagext.dll extracted from the dopod 9000 wwe ext rom and copy it over the original one in the windows dir, then soft reset...
That solved the problem for me.
topogigi: Where can I get that file? I will give it a try!
rain: I have a original HTC TyTN in german language! Is there any place where I can check for a new software by my self?
For btagext.dll you should give it a search here on xda-dev or ask an Dopod device owner to extract it for you.
For software the hardware configuration is not that much different from the Wizard or Prophet so any software that works on this device will have to work on yours also. pocketgear, mobihand, pocketland.de to give a few examples of websites where you can look for software and download free trial versions. There are also freeware websites. Just google as there are plenty of them at the moment
Cheers,
Raul
So is there anyone who can send me that file? So that I can test it?
Thanks very much!
Here it is...
Hi,
Am having the same issue, I copied over the file but it has not helped, were there any other files you copied over. (I did reset)
Cheers.
A solution is finally found!!!
http://forum.xda-developers.com/viewtopic.php?t=59918
Thanks for the post but I do not really think this is a solution to the overall issue. It may help in just listening to audio but it takes away some functionality, that being able to initiate voice command or voice dialling.
[EDIT]
Here is what I found;
Adding the DWORD string "VoiceCmdDuration = 86400" (86400 = 24hrs) under
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
passes the audio stream to the headset, for my issue where Voice Command was timing out on me before finishing what it was saying etc... this has worked fine, also, if not using Voice command a single press on the headset button passes Audio to it, second press disconnects.
I also changed this to value to 60 (seconds) after which the audio timed out and did not seem to start form zero again once initiated but I will need to test this some more. In the mean time I have entered some ridiculous figure to keep it running as I want, again, more testing and time will tell if this drains the battery any quicker.
I did NOT install BTAudioOn as mentioned in the other thread.
Hi cieplowski - how did your testing go? I got my V1605 on Friday and think I have the same issue with Voice Command. When I press & hold the button on my bluetooth headset it starts Voice Command and accepts my voice tag but almost immediately the sounds revert to the PDA speaker and I hear the response through the PDA and not my headset.
If your hack works and doesnt drain the battery then I'm extremly greatful
Thanks
Hi coe62,
Well, I used it over the weekend and it worked fine, I did not notice any abnormal battery drain etc....
Remember, all I have done is add
DWORD string "VoiceCmdDuration = 86400" (86400 = 24hrs) under
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Nothing else, no additional programs etc....
This tweak works by basically not disconecting the audio feed to the headset until the button is pressed again or the set time runs out. I am pretty sure that the time set runs from a soft reset so I have left mine as a huge value, 6000000 (I think)
Other findings are;
After voice call the Audio stream swithces back to the phone, this is great for me as I do not have to remember to press the button again to disconnect it hence saving battery power on the headset itself.
TomTom passes all Audio to the headset also.
Let me know if it works on yours.
Hi cieplowski - no joy I'm afraid. made the reg change and then reset but after this the headset pairs ok but all commands still come through the V1605 speaker and not the headset.
Only thing I can think is that I used the wrong DWORD value - should it be a hex or decimal value ?
thanks
OK ... I got a program for the X2a that works for voice calling -- Vito's Voice Dialer ... but I don't want to have use the screen to initiate the voice reconition ...
I am using the Aliph Jawbone 2 which has a "Initiate Voice Dialing" button, but the x2a needs to know to initiate Vito when it is pushed. Is there a way to map the Jawbone button to the Vito program ... I looked at the registry, and didn't see anything that was obviously the right spot ... it there a program that can be used to connect the 2?
When I tried MS Voice Command it seemed to have the connection between the 2, but it had other problems that didn't work ... so it is gone. SO my beliefe is that it is possible, I just am in the dark as to how the get it done ...
Thanks in advance ....
did you find a way to initiate a call via the bt headset call button?
Not I haven’t … but here is what I have tried ….
1. Used AEBPlus to map the phone key to the VoiceDialer …
2. Changed the registry to map the VoiceCommand entry to VoiceDialer …
Non of these worked … it seems as though the button used for voice calling on the jawbone calls cprog directly … I thought about changing / renaming cprog … but it is always being used by Winmo .. so I can’t rename it …
I tried to rename the Phone.lnk … which didn’t help …
Also, the BT headset did not seem to be connected to the phone when the “voice dialing” button was pushed … the BT headset was not the active microphone … I tried a different BT headset with A2DP … didn’t help …
I haven't given up, but I don't have any solutions either.