I recently got a Samsung WEP500 to go with my Cingular 8125. It works great except for one problem: The WEP500 only has a single, big multi-function button. Pressing this button just once while the phone is idle will cause the phone to redial the last number. This is a pain because the button is really easy to accidentally activate when putting the earpiece in or when you just have it in your pocket. It's gotten to the point where I'll call my voicemail just to have that as the last dialed number, so I wont pocket-dial someone I know.
Is there a way to disable the redial functionality of a bluetooth hands-free headset? I'm running a pretty stock Cingular build, with the default ROM of 2.0.25.11 for both OS and radio, which is of course WM5.
I'd be most appreciative for any help. Thanks!
+1
Would be nice to leave my BT radio on all the time.
I am also having the same problem with my Bluetooth. Still waiting for a solution.
WEP500
I aslo have same problem.
Have you tried turning the headset off when putting it in your pocket?
I NEED this too. I have the Scala Rider Q2 for my motorcycle and a single press on the button re-dials ther last number I called, whereas if I hold it, it turns on the radio.
I often find myself trying to listen to my music and end up speaking to someone...
Thanks for the idea of calling my voice mail BTW, never thought of that.
I know this is an old thread, but just in case someone is still interested in this, you may try solving it the way i did for my HTC Polaris. I have no idea if Wizard got similar bluetooth stack or even if WM5 got an option to load audio gateway at commands extensions in general, but, well, it worth a try.
http://forum.xda-developers.com/showthread.php?p=5355333#post5355333
Disable Bluetooth-initiated redial.
Hi I´ve tried your cab file om my HTC touch cruise WM6 with a sony-ericson bluetooth headset device but it did´nt work.
Do You have a alternative solution or maybe an updated cabfile?
Related
Hallo...
I have serious problem and till now I don't know how to fix it. I change the registry to allow the Bluetooth Headset to activate the MS Voice Command, when I click the button on the BT the Voice Command starts fine, but if I want to use it agin, the VC doesn't work anymore, I hear only a "peep" but the programm doesn't respond. I have Qtek 9100 with the last official ROM .
Any idea or solution to fix that ?
I appreciate any comment.
Thomas voicecommand and bluetooth has some issues. Basically, when you use VC the first time it opens the channel with the device, once you have then used it you need to hold the button down on your bluetooth device to close the channel. Then pressing BT again should open voicecommand. There's a number of posst for this problem but hopefully I've given you the basic issue
Thanks for your reply... But no, closing the Voice Channel doesn't solve the problem.. I have tried all that before I post my question, it really works only once and no more, only after restarting my device it will work again for once.
I am starting losing a hope that it can be fixed.
Thomas1234: I started trying to come up with solutions to this a while back but never had time to work on it further yet. Anyways what I came up with so far can be found here. It's not perfect but may work with your headset and make it useable for the most part.
http://forum.xda-developers.com/viewtopic.php?t=49255&highlight=
Note: Scroll down to the bottom of the above thread to get the latest version and you have to be logged in to see the file.
Hi shoey5!
Thanks for trying to help me, but it doesn't work, and it looks like that this file damaged the connection between BT headset and the Voice Command or any Voice calling, even the one by default ( voice calling ) doesn' work anymore now.
I was able before at least to do the voice calling, but now it doesnt work after I changed the registry to default to read from the sddialer.exe file.
Can you please explain me what did the file change so I can change it back if i is possible ?
I did softreset alot, but doesn't help.
Thomas1234: It doesn't modify or change anything, all it does is run resident and resets the Audio Gateway Service after a call has ended if there is a bluetooth device active. Removing it from your startup folder and resetting your device will get rid of it completely.
Are you sure you haven't modifed something else before or after that may have affected your problem. I know this sounds silly but is your volume up, can't tell you how many times I sit there pushing the button and wondering why I don't get anything only to realize my volume is off
BTW, Try this. Leave the program in your startup folder, power off your headset and reset your device, then power on your headset and see if it works from that point on. I've noticed this happens to me with headsets that exhibit this problem the odd time.
Thank you anyway..
I ended up to do a hard reset, because softreset didn't help... It has been worse, I even couldn't dial a number using the BT headset, well I won't say it is 100% because of your file, but I am sure I didn't do anything with the device that can cuse this problems before I applied you file, all this happened just after I installd your file.
I'll use the default Voice dialer then with my BT Headset till maybe Microsoft update its program.
this "ms voice command running only once" happened to me too, with Nokia HS-12W headset.. try using JETware Hands-free Extension for Windows Mobile phones, http://www.jetwaremobile.com/ , and activate ms voice command from its advanced settings.. it worked for me. unfortunately it's not free and it doesn't supply caller names to my hs. hope this helps..
Thanks ozkaya, the program looks useful. I'll try it and see if it does the job correctly.
After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht
Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?
Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.
Changed over to Tytn... works perfectly without any hacks
here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.
Apologies if this is an FAQ, but I've had a quick look and drawn a blank.
I've just got my first Windows mobile phone (Vario II) and one of the things I really miss compared to my old Nokia, is that when I connect my bluetooth headset, I'd like the phone to switch to 'auto answer' and for the volume to be set to max. When I disconnect the headset, I'd like the phone to refert to a 'normal' or 'general' profile.
I require this because I use it on a motorcycle in conjunction with an intercom system, and I need the phone to auto answer after say 2 rings.
Is this possible on a smartphone?
Regards,
Glenn
Join the club mate......
I've been using the Vario2 in combination with a Nolan N-102 with the N-comm BT kit on it.....
I've been #$^&# with it for weeks now and I've made some progression...
First you need a program that allows you to select profiles like Nokia used to have...
I use PocketzenPhone but maybe there are some other(better) programs to do that.....
So then u can swith to a bike profile I've made and enable auto answer....
I've run the cab file to redirect BT sounds to my helmet in stereo (floats somewhere on this forum)
The only thing I can't do at the moment is enable Voicedial from the helmet...
If I press the button designed to start it ........f%ck all happens....
Still working on that but I'm running out of ideas....so any help would be appreciated...
Danny.
Pdanny said:
Join the club mate......
I've been using the Vario2 in combination with a Nolan N-102 with the N-comm BT kit on it.....
I've been #$^&# with it for weeks now and I've made some progression...
First you need a program that allows you to select profiles like Nokia used to have...
I use PocketzenPhone but maybe there are some other(better) programs to do that.....
So then u can swith to a bike profile I've made and enable auto answer....
I've run the cab file to redirect BT sounds to my helmet in stereo (floats somewhere on this forum)
The only thing I can't do at the moment is enable Voicedial from the helmet...
If I press the button designed to start it ........f%ck all happens....
Still working on that but I'm running out of ideas....so any help would be appreciated...
Danny.
Click to expand...
Click to collapse
Hi, the reason you can't activate voice dialing from your headset might be to do with the BT Audio cab you have installed to redirect sound through your headset. If the cab you have installed is the most common one floating around then this actually disables the launch of voice dialing in favour of being able to toggle between sound in the headset and sound on the phone (pressing and holding down the call button for a few seconds on your headset normally).
If you look in the registry HKLM>software>OEM>voicecommand, if launchapenable has a value of 0 then it is disabled. You can enable it again by changing the value to 1 but this will mean that your headset button will now not work as an audio toggle feature because it will launch the voicedial software every time.
Not sure if this is the answer to your problem but it sounds like it might be, hope this helps
Am trying as we speak....thanks for the reply....see wat happens...
D.
Well.....Ive got good news and bad news....
The good news is that I can trigger voicecommand now......
The bad news is that MS voice command 1.6 is not reconizing my accent...(dutch)...
So out of 10 tries it never called the number i wanted.....
So I tried the build in SDdialer.....and that one is doing a better job....
However I can't make the sounds to stick in my helmet........
I mean...
With MSVC by pressing the button on the helmet I could redirect the sound to the helmet and get a voicecommand tone at the same time....
By symply not speaking or saying '"cancel" it would cancel the voicecommand but the sound stayed in the helmet.....
With SDdialer following the same steps as above the sounds does not stay in the helmet but goes back to the speaker......
Any ideas????
BTW is there a dutch version of MS voice command?
If you go back into the registry, in the same location as before, check the value that is in VoiceCmdDuration (This is the amount of time the voice prompt stays active for in seconds) .. the audio cab file usually sets this to 86400 (24 hrs in seconds), if yours is low eg. 10, 20, 30 etc.., set it to 86400 and that may sort out the problem.
Duration is set fort 24 hrs....already..
Funny thing is that MSVC is not cutting out and the sddialer is...
Regsetting stay the same.....
By pressing the button on helmet I just change the exe file.....
Only option is to try and get MsVC to work and get use to my voice....
D.
Hmmm booking slow process.....tryed to call with MsVC and now 2 out 2....
Ordered to play media from helmet......worked..
This is only sitting in the livingroom with helmet on.....looks absolutely silly but thats besides the point
P$ssing with rain here so hoping for better weather to go for a roadtest...
So thing needed for me to get it to work...
-MsVC 1.6
-Bluetooth stereo cab
-Regedit from the MsVC topic..
-PocketzenPhone for designing profiles.....however thinking on removing that...and see how that works.....
D.
I am glad that you are at least part way there to solving the problem
I don't have Voice Command on my phone. On the rare occasion I use voice dialling I use the standard SDdialer program but my sound diversion does not revert back to the handset like yours.
I must have changed something on it to get it working but I am afraid I don't know what because, when I was trying to get it working, I tried absolutely everything and it was quite a while ago now so I have forgotten what I did
It sounds like Voice Command is going to be okay for you though so that is good.
By the way, Phonealarm is also another good profile switching program.
Thanks for the replies guys, but I think I may have accidentally discovered my own solution.
On my T-mobile vario II, if I go to the Phone->Settings and select the 'more' tab (need to scroll along the last tab at the bottom of the screen) there is an option to 'Automatic pickup' which will auto answer a call after x number of rings.
I had always assumed this would kick-in even if no headset was present. However, I've just done some simple testing, and it looks like the auto answer only kicks-in if the phone is currently in comms with a headset (I used a bluetooth one but probably the same for the supplied 'hands free' kit).
So this functions exactly as I want it to.
Oh, and Pdanny, for background info I'm using a Nolan 101 (no bluetooth) with speakers and mic installed. These connect to my 'Starcom' intercom (via an old fasioned curly lead) which allows me to hear directions from my 'TomTom' and also take phone calls via the starcom/phone bluetooth partnership. Down side is that the wife can also talk at me .
As I never want to initiate a call while riding, this setup works just perfect for me. I don't need to remember to change the phone setup either before or after mounting the bike. As soon as the bike ignition is turned on, the intercom partners with the phone. Then if I receive a call, it auto answers and I can take the call. Once the ignition is switched off, the phone reverts to normal non-auto answer.
In my research for this issue I came across an app called 'phonealarm' (from pocketmax.net), it was the manual for this that made me try the above experiment. This looks like a neat app and I may still end up installing it as long as it does not hog the processor.
[edit]OOps sorry Nicky, just noticed you already mentioned phonealarm. I'd be interested in any comments you have about this app, good ot bad [/edit]
Once again, thanks for the replies, and I hope this thread helps someone in the future.
Regards,
Glenn
Phonealarm......give that a try thanks.....
Im also going to test with the buils in auto pick up.....
I knew it was there but i assumed that it would ALWAYS auto pick up...
It seems that that is not the case therefore making the Pocketzenphone and possibly phonealarm obsolete.....
I also get all the sounds over BT in my helmet....incl TT
Also... I don't have a wife .......sounds like a perfect world hey???
Keep you posted on the outcome of the xperiment....
Grtz
Danny
Hi knnelg, glad you managed to sort your problem. I always knew the option for autoanswer was in the settings but like you, I had assumed that it would autoanswer all calls regardless of whether a headset was connected so it is handy to know that it only applies when in headset mode.
You asked about opinions on Phonealarm, I think it is a great program. I have used it on my Vario II and my last phone, an XDA Mini S, and it is has always worked fine, no problems at all.
I really missed having phone profiles when I switched to PDA style phones so Phonealarm was one of the first 3rd party apps I ever bought and I wouldn't be without it now Also, Bruce, the developer of phonealarm, is very good at listening to users input and if enough people make a suggestion about an improvement or tweak to the program, he will implement it in future versions which is really nice.
One of the other programs Pocketmax does, Alarmtoday, is useful too.
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...
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.