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.
Related
Hi Guys: I have got the Widcomm Phone edition stack working on my unit.
It seems to be fine but I have not fully tested all aspects of the software - so if any little bits don't work, let me know...
You need to install the official widcomm 1-4-1-59 version
Then you can upgrade it using the cab file I have made.
The 1.4.1.59 version file I got from the following topic
http://forum.xda-developers.com/viewtopic.php?p=57550#57550
thanks go to mamaich for the file.
the upgrade file consistes of the PE edition files and the required registry entries.
Let me know how you all go on with it - but I am not really a hacker so any serious probs I will not be able to fix...
if anyone else can improve on the installation be my guest
any news about which profiles it support that ms or the old one dont support ?
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
I can't garauntee it works perfectly, so I suggest everyone make a backup of their system before use.
has anyone tested any BT headset with this new stack?
I've got it installed and it all seems to work well exept for the handsfree/headset profile, I have set up my headset ok it is discovered and bonds fine but when I try to connect from the xda2 the connection fails after "waiting for device" for some time. tried with a motorola hs 810 and a neovoice usb, same with both. Anyone got any ideas?
BT headset
I have a 6315 and an XDA 2, I haven't tried the BT Stack on the XDA 2 yet but I found when I bondeded my HBH-30 to my 6315 once it made the connection my BT Headset shut off for some reson. This caused the bonding to fail, but as soon as I turned my headset back on (while it was trying to discover services) it completed the process and worked on my 6315. I'm not sure if this will be the same, but it's worth a shot.
Brandon
Test results
Hi fellows
Here is little bit of my testing of this new BT Stack, which we all awaiting for..
Proc…
1. Installed as per instructions 1.59 without any problem. During installation was prom to override .dll files – agreed to do that. For good or for bad – will see later.
2. Installed .cab file provided by icarusbop (big thanks to him for doing this) without any problem. Screen shots will be attached below.
3. Reset it as requested upon installation and got Widcomm BT working instead of MS BT..
4. Paired it with my BlueTrek G2 within 3 seconds (which took usually 10 sec with MS BT)
5. BT recognized G2 as device with Headset/Hands-Free profiles and asked to use as default… I said yes…
Here comes Cons part ;(
1. Unfortunately even after paring – my I-Mate can not get connected with G2 (see screen shot)
2. As you can see in another screen shot – there is Hands Free menu – it can not be accessed, or can be accessed ONLY while connection is established.
3. AND the last L … So, this new BT is not working now… I decided to go back to MS BT… SURPISE!!! I am getting message that BT HARDWARE IS NOT INSTALL ON THIS UNIT…. L Assumption - .dll files were overwritten (see Proc 1)
Here is my 2 cents in this jorney… I am hoping that described problems can be fixed and we can make it working (without doing hard reset on my device )
Paul
thanks guys! for testing hands-free/headset profile. by now everything seems to work fine with this new stack except for hands-free/headset profile.
New comments to my testing
1. I tried what NeoCole recommended - didn't work for me
2. As soon as new BT is OFF - MS BT is working fine .....uf
LETS FIX THE HEADSET PART PLEASE
I posted this is another thread - but in case someone does not read that thread . . . it is relevant here as well.
If the intent of this is to get voice dialing without touching the device, that is by only pressing a button on the headset to initiate a voice-dial program to make the call, there is no evidence this works with this BT stack either.
I have been reading other forums with people who have the H6315 already (mine is in the mail to me now) and none of them have been able to make this work. Nor is there any mention of this capability in any of the literature and/or documentation for this device. It seems that if this was a feature of this phone, it would be prominently displayed!
Voice Command
Okay.. on my 6315 I press the headset button, it beeps, sound and voice is now transfered to the headset. I do this before I initate voice command. Now all I do is press a button that activates Voice Command on the PPC and walla, I'm speaking and listening through my BT Headset. This is a huge step forward from using the MS Stack, and I feel that since the Phone Edition of the Widcomm is 1.0.0 I'm sure that they'll associate a hardware button with the headset button in future releases. Anyhow.. I think that the functionality of the Widcomm BT Stack is well worth the work. The XDA 2 would be a lot better device if the BT Stack worked 100% of the time and was fully compatibile.
I also have not got it working.
the Hp 6315 is well know to still require a hardware button press (not on the headset) to activate voice command. They can still not do with any nokia or SE phone can do easily.
Surur
VoiceCommand
That would be correct... One press of the HW Button does it all on a Regular phone.
The 6315 has brought it closer to allow you to interact with programs using your BT Headset, but yes you must still activate the programs on your handset before you can use them with your headset.
So.. to sum it up...
1. You can't interact with Voice Command using MS BT Stack on an XDA 2
2. You can interact with Voice Command using Widcomm Stack on 6315, but you have to activate the headset first, then start VoiceCommand on the PPC by using the HW Button.
Hopefully through this thread we'll be able to give the XDA 2 the same functionality as the 6315.
And maybe if Widcomm provides an update to allow the headset to activate a HW button, we'll be to the one step solution.
I do not want my comments to be read as stating that this is not a worthwile endeavor. I simply meant to make sure that someone does not go to the trouble of installing this new stack (particularly those who might be considered novices) with the mistaken impression that by doing so they will have that "one step" voice dialing solution.
This is by all means a worthwile endeavor, but it is merely a step down the road . . . not the final destination.
Y'all are doing good work - keep on blazing that trail!
hm.. I would think that it is more of MS Voice Dial functionality than BT - to recognize signal sent from headset as request for voice dialing.
When MS released first version of Voice Dialing they did not expect new functionality to have BT headset with hands-free profile connected to the device.
paired with my Jabra 250 = ok
connected to my Jabra 250 = failed
No luck with Moto headset
Eveything else seem to be working. No problems with detecting and working with BT access point
rehman said:
I hope unintall won't mess up my volume as in case of original bluetoothgps.cab
Click to expand...
Click to collapse
Hi Rehman,
i tried to install and uninstall, for the very first time i didn't have to get a Hard-Reset done. the volume didn't disappear. so i believe trying it wont be a harm, but yet i would recommend to get a full Backup first.
Trying to figure this out
Okay, I looked through the whole registry. I can't find anything out of the ordinary. Only thing I can think of is the sound driver. Does anyone know what DLL that is? I bet it's a different version.
If someone that knows more about which DLL does what. Let's get all the DLL's that could pertain to Sound and Phone and compair the 6315 DLL's with the ones on the XDA2.
Hi,
i can't use the BTAudioToogle Tool for my XDA trion.
Someone the same problem ?
or better:
Someone with a solution here ?
Same for me. I have enabled BTaudiotoggle, I can hear the headset (Motorola HS850) go live but the audio either from WM player or TCMP still comes from the speaker and not the headset.
Hope someone comes up with the answer soon.
Rob
Got the same problem. No sound from BT.
Had something similiar to this with my old unit, to fully enable it I would hit the headset button (which now starts up voice command, let it time out, and then play whatever music i wanted to. I would verify that now but i am at work, and don't think they would appreciate the music blaring if i am wrong on this one
When I hit the button on the headset, it starts the Voice Dialer, the audio cuts in for a second or two, then drops back to the device speaker.
It nearly works, hope someone can hack this soon, just whats needed for podcasts and the like. No good for music tho!
Rob
I would also be very interested in a solution to this problem as I used to use BTaudiotoggle to listen to Tomtom commands in the car (normally have the music too loud to hear the commands through the loudspeaker ).
Worked great with my XDA Mini S but doesn't work with my new MDA Vario II and I didn't really want to have to buy stereo headphones, just wanted to be able to use my standard mono bluetooth headset like before.
If there is no way of using this program, are there any other programs that will send all audio to a mono BT Headset?
yep would really like an updated version of BTaudio too so i can listen to some audio books via my mono headset
You should test the trial version of bluemusic from teksoftco.
www.teksoftco.com . It gives ou a full help file on how to use the software and you have 30 sec to test that it working. I know that it works on the devices having TI Omap processors so it should work for all of you guys.
Cheers,
Raul
Just tried it out. It does the same thing that the other sotware does, mainly enable the headset where you can hear a hiss out of it, but still kees playing out of the back speaker.
My experience is a rassah's. All the Bluemusic software appears to do on my Vario II is cause the bluetooth headset to hiss slightly (whilst sound is still blasted out of the phone's speaker).
Also FWIW the teksoftco site doesn't appear to work too well on the PIE browser - defaulting to a no frames version with just a login box as far as I can see.
Needless to say I have uninstalled the software again.
Rufus.
@RufusA and @rassah guys you should check if you don't have the same problem as ulischultz in this thread :
http://forum.xda-developers.com/viewtopic.php?t=61739
We already tested the software with him on his treo device and as you can see in the thread " after pressing the button on the headset, the sound was redirected". This is mentioned in the help section of the software. ( on the universal/exec for example this step is not needed)
@RufusA - thanks for visiting the ppc version of the webpage (which is still under construction) - even though the subject is irelevant in this topic. I will send you a PM when its finished and tell me your opinion then (even though you have to admit that not many companies have a ppc version of their website - not to mention the smaller ones like ours).
If the problem still persists there is an opened thread on the forum :
http://www.teksoftco.com/forum/viewtopic.php?t=162
Please submit all the malfunctionality and we will fix them.
Cheers,
rain
I downloaded the trial too and had the same problem as before unfortunately.
I did get a little further in so much as, if I pressed the call button on my BT Headset as per the instructions, I could get the music/audio transferred to the headset for approx. 5 seconds but then it would revert back to the phones loudspeaker. I couldn't get the 30 seconds that the trial software advertises
Fingers crossed someone will be able to work out a fix for this soon.
Thanks Nicky for the input. As i see the problem of bt headset being disconnected after 5-10 sec is a general one (and unfortunatelly is a problem in the RUU). We are trying to find a workarround with ulischultz but wouldn't want to get to driver level as clearly it will be fixed by HTC in the next RUU release if they don't want this devices smashed to their heads.
I will keep you updated if we find a solution for the interrupt issue.
Regards,
Raul
Solution
I have identified a solution to this which is working nearly perfectly for me. However, if you do use this then using the BT headset to trigger the voice dial/voice command/voice commander will no longer work.
Acquire a copy of of the BTAudioToggle software inc. BTAudioOn.exe
Copy this to a location on the phone.
Using a registry editor amend the following entries from
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Path = location of BTAudioOn.Exe
e.g. Path = \Program Files\BTAudio\BTAudioOn.Exe
VoiceCmdDuration = 86400 (DEC) = 24 hours
This says for how long (in seconds) the audio will be passed to the headset for before timing out.
This however, will timeout earlier if no audio is coming through. I am not sure what will happen if something like TomTom is running but not speaking for a while. I have not performed timings as yet.
To activate audio through headset, press the main control button of the headset as if answering call/activating voice command etc. To deactivate, just press the button again.
Voice control apps will still work, but must be triggered from the phone itself, but voice will be picked up by the BT headset.
There appear to be some small bugs with this, such as after a phone call, using headset or not, the audio will stop being passed after hangup.
Please let me know if this work for you!
Looks an interesting solution. I've installed BTAudioOn on my storage card, and changed the VoiceCommand Path entry.
However I couldn't find a VoiceCmdDuraion entry under
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
so I've added a new DWord of that name with the value 86400.
Yet this doesn't appear to have made a significant difference i.e. Pressing talk button on Jabra headset produces 10 secs of sound before "timing" out.
Have I made a mistake, or do I need to have something else installed to get this to work?
TIA - Rufus.
I was going to try and make the suggested changes to the registry but I don't know how and am not sure what program I need to do it.
Could someone please let me know what program I need to install to be able to change the registry?
Thanks
Vs1979:
IT REALLY WORKS!!!!!!!!!
I can't tell you how happy I am!!!!
I did it the way you described it. However I also did not have an entry "VoiceCmdDuration" I created the DWORD-entry and it works now!
Great!
Thanks very much for that great solution!
@RufusA
As i gave you the link to the other thread you're not the only user experiencing this. There are several others complaining about this RUU bug.
@Nicky
You need to install a ppc 2005 regeditor (for example Resco Explorer has one built in, or you can find one on buzzdev site).
RufusA said:
Looks an interesting solution. I've installed BTAudioOn on my storage card, and changed the VoiceCommand Path entry.
However I couldn't find a VoiceCmdDuraion entry under
HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
so I've added a new DWord of that name with the value 86400.
Yet this doesn't appear to have made a significant difference i.e. Pressing talk button on Jabra headset produces 10 secs of sound before "timing" out.
Have I made a mistake, or do I need to have something else installed to get this to work?
TIA - Rufus.
Click to expand...
Click to collapse
Hi,
Did you Soft reset your device?
I made the registry change only, have not installed BTAudioOn and all my Voice command Audio etc... now comes through the headset and does not time out after a few seconds. I did find though that decreasing this value to lets say 60, would actually time the audio feed out even if not in use so I have stuck in a huge figure, will still need to do more testing to see if drains the battery any quicker and see if I can find another stirng which will do more for me.
Hi,
it work not for me
i have changed the path to \xx\BTAudioOn.EXE
i have add the VoiceDuration = 86400 (DWord DEC)
but it is the same problem, after 2 seconds the sound goes back to PPC.
Nice to see this new Sable forum and hope it grows with time.
Has anyone achieved VC 1.6 initiation from their Bluetooth earpiece?
I can't. Running WM5 5.1.195 on HP 6915, and guess that is the problem.
No ROM update as far as I'm aware, but please correct me!
Am I flogging a dead horse trying to find a fix?
Alternatively, has anyone got VC 1.5 running properly with the reg hacks? It worked just fine on my old Universal.
$9.99 to downgrade....not such a great deal in my book! Could someone look to see if I have "idiot" written on my forehead?
I have a hw6955 and version voice command 1.6 and I've tried the hack (which starts vc1.6 when the headset button is pushed) that's been used on other wm5 devices and it doesn't work.
Voice command 1.6 is great and I still use it, I've assigned the side button to start vc 1.6.
Trouble is, the device turns off after a few minutes anyways and it seems to lose connection to my BT headset. You have to turn the device on and then press the side button to start vc. If a call comes in, I have to press the button on the headset to reconnect to the device anyways. Not sure if this is normal, because hardly anyone has sables.
Could pressing the button on a headset, turn the device back on and start voice command? That would be awesome. Anyways, the 6955 is a great device, just needs a few more people hacking for it.
1500 and 3000ma batteries for out for it, the 300 gives 4 days of use, which is amazing. The 1500 provides 25% more power then the OEM battery and is the same form factor (and weight).
I don't have the cut-off problem at all.
In the hands-free setting (Bluetooth Manager/Handsfree Connection/HandsFree Settings) I've ticked the box for Standard Audio as well as Telephone Calls - perhaps that makes a difference. Mine (Moto) stays on and I also get all my TomTom instructions through it. Voice recognition through the BT headset is pretty poor though.
Where did you get your batts? I've got the 2500 from eBay - larger size with back cover that is a different colour to the PDA and not a terribly good fit. £15 from Hong Kong - but I can live with that! Found a nice case from US that takes the larger battery.
I have a logitech one, I'm not sure if it's all the great. I may try a moto one. If I turn on both telephone and all sounds in the bluetooth menu, then I find that there is a lot of background static on the headset. People have mentioned that it sounds like I am standing by a jet taking off! Anyways, I think it's the implementation of bluetooth on the hp models and not the headset, but until I try another one, then I don't know.
Have you read the thread here about activating voice dial with the headset button? It's really good.
any more information on this? BTW, all 6940/45/50/55 ipaq users should be using microsoft voice command 1.6. It works amazing for voice dialing. No training, it just works.
If someone could get the bluetooth headset button to initiate the voice command software on the ipaq, that would be ideal.
A lot of smartphone, pda users are attempting to get voice dialing working with bluetooth headsets. There are various posts on here about it.
Obviously, there isn't a huge following for the 6900 series... That is not good.
Battery life would be the most obvious reason!
I have MS Voice Command 1.6 UK Version running fine on my PDA (fair enoughitsan Orbit / Artemis / P3300) but everythingworks fine, announcing calls /messages / BT headset button / voice dailling the lot.
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...