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.
I have this problem. When unit is in powersafe mode, when I press main buttom on my BT headset, device doesn't wake up. That makes impossible to use voice dialing while device in the the sleep mode.
I've tried:
GG Telecom
HBH-610
HBH -608
Moto H500
Anyone else?
As I only use the headset in the car its not a problem as I always charge in the car so the unit is always on. I have noticed though that it does not wake the device. I think I-mate make a refernce to it somehere as a fix pending
I have exactly the same issue. In other posts it has been mentioned that people have replaced teh built in voice dial facility with Microsoft Voice Command. I wonder if the same problem persists when using MS Voice Command?
yes its true blue tooth does not wake up our wizards. but considering before when most of us had jams and we where trying to hack our way to bluetooth dialing . this should be a small hill to climb. all we have to do is wait for one of the developers from this site to get one of these beauties and we should be ok
Voice Command 1.5 does not wake it up either. Plus it causes other weird stuff to happen like keeping your bluetooth connection up until you power off your headest or restart the bluetooth service on the handheld. Moreso depends on which headset you have.
BTW, Latest T-Mobile ROM fixed this porblem. Voice dialing works now and wakes up device.
I have a solution to the bluetooth wake up
I have created a fix for this problem. Thus far it works with the default Voice Speed Dial and can be modified to accomodate something else like Voice Command or other.
I have only tested this on a Qtek 9100, but am sure it will work with other Windows Mobile 5.0 devices if they have the same problem.
This will require the Microsoft Compact Framework 2.0 to be installed. Aside from that it is a single executable and registry entry that will fix the wakeup problem.
I developed this myself so if anyone is interested please let me know.
I will not be giving this away, but anyone intested can let me know and I will work out details and modify program for you to accomodate whichever application you are using for voice dial.
Thanks
I have a solution to the bluetooth wake up
I have created a fix for this problem. Thus far it works with the default Voice Speed Dial and can be modified to accomodate something else like Voice Command or other.
I have only tested this on a Qtek 9100, but am sure it will work with other Windows Mobile 5.0 devices if they have the same problem.
This will require the Microsoft Compact Framework 2.0 to be installed. Aside from that it is a single executable and registry entry that will fix the wakeup problem.
I developed this myself so if anyone is interested please let me know.
I will not be giving this away, but anyone intested can let me know and I will work out details and modify program for you to accomodate whichever application you are using for voice dial.
Thanks
This problem does not exist in newer roms.
No need for any fix - simply install a new rom.
I have heard
I have seen the posts. However I am still unable to get an update for my Qtek 9100 WWE. I don't know where to get the updates. On the xda-developers FTP site I don't see any update for WWE except for T-Mobile UK which is not for me. I bought this phone here in the US (not from a carrier) with the typical first release versions. For me all is well aside from the bluetooth wakeup which I have read has been fixed with newer ROM updates. This would be more intended for people in my same situation. If you know where the update can be obtained I'm sure you will help a bunch of other people trying to get the Qtek 9100 updates for WWE. Also I have read that that T-Mobile update on the FTP doesn't have a radio update and also doesn't have AKU2 which is what I am awaiting Microsoft to release.
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.
Hi all,
I know there are plenty of threads about the TyTN bluetooth issues, but my questions differs in two ways which I have yet to come across:
I do NOT have M$ VoiceCommander installed (and don't want to install it)
My bluetooth issue relates to my car's handsfree feature - my TyTN randomly connects and disconnects. Apparently Audis, VWs, BMWs, and Acura's all suffer from this this problem.
The situation:
When I start my car, the phone will successfully merge with my TyTN. Approximately 30 to 60 seconds later, the connection will be lost. Shortly after that the connection will re-establish itself, then it will disconnect itself a short period later. This pattern repeats endlessly.
I've tried each of the following Tweak programs but none have helped.
jetwaremobile
Tweak2k
HTweakC
I've heard that there is some kind of registry tweak that will prevent the bluetooth stack from disconnecting from my car's handsfree feature, but after looking for about 2 days now, I can't find it. Can anyone help?
thanks.
jm
Yep, got exactly the same on my BMW 630....
Can t find any tweak but....
I am a heavy email user (thru BlackBerry connect) and I noticed that
the higher the number of messages stored, the higher disconnections appears.
At the same time, the TyTn is slower and slower....so my idea that this is related to some timeouts somewhere....
For your complete info, the MS bluetooth stack in my previuos S100 have able to.....immobilize my 630 !!!!!!!!! yes, incredible...
The MS stack messed up with the BMW bt ...and this later would stay ON for ever...even after switching car s power off.
This was sucking the car s battery untill the car would start !...
BMW could not reset the BT module unless disconnecting battery....but...then the active steering had to be re adjusted with the proper BMW computer...
This is a real story.
johnmclean said:
Hi all,
I know there are plenty of threads about the TyTN bluetooth issues, but my questions differs in two ways which I have yet to come across:
I do NOT have M$ VoiceCommander installed (and don't want to install it)
My bluetooth issue relates to my car's handsfree feature - my TyTN randomly connects and disconnects. Apparently Audis, VWs, BMWs, and Acura's all suffer from this this problem.
The situation:
When I start my car, the phone will successfully merge with my TyTN. Approximately 30 to 60 seconds later, the connection will be lost. Shortly after that the connection will re-establish itself, then it will disconnect itself a short period later. This pattern repeats endlessly.
I've tried each of the following Tweak programs but none have helped.
jetwaremobile
Tweak2k
HTweakC
I've heard that there is some kind of registry tweak that will prevent the bluetooth stack from disconnecting from my car's handsfree feature, but after looking for about 2 days now, I can't find it. Can anyone help?
thanks.
jm
Click to expand...
Click to collapse
I have the same problem with a CK3100 kit, don't have a solution, but would like one, didn't have this problem with a Jasjar nor Wizard
TyTN bluetooth | random disconnect when using car handsfree - more details
Thanks for the replies so far.
Although the following thread did not help me with my problem, it might help one of you. If you're having problems mostly related to issuing voice commands using M$ VoiceCommander, I think there *might* be a solution in that other thread for you.
Just to reiterate my problem; my TyTN keeps randomly connecting and disconnecting from my car's built-in hands free bluetooth device.
There was a time when if i managed to made a call after first starting the car - before the first random disconnect - the phone would remain connected until the next time I started the car. That no longer appears to be the case.
-jm
I solved the BT problem with my Orange SPV M3100 by setting it to never switch off the display automatically (only switching off the backlight after 20 seconds or so). I also use an in-car charger to power the TyTN. The car is an A6 with RNS-E (BT enabled) and TyTN works fine and never loses the BT connection as long as the display is active.
This is a mid-term solution though and I'm still eagerly waiting for a ROM update that will solve the problem for good.
Has anyone tried a ROM with aku 3.3?
jasonrhcastle said:
Has anyone tried a ROM with aku 3.3?
Click to expand...
Click to collapse
Yes.
And on my CK3100 I now no longer get disconnects. I did have to uninstall jetware as it wasn't reliable. My TyTN now connects perfectly and no longer drops.
One thing I did find is that the TyTN hates it when more than one handsfree device is in its trusted list. Make sure that the ck3100 is the only handsfree device paired.
http://forum.xda-developers.com/showthread.php?t=247520&highlight=bluetooth+keeps+disconnecting
ajax007 said:
I solved the BT problem with my Orange SPV M3100 by setting it to never switch off the display automatically (only switching off the backlight after 20 seconds or so). I also use an in-car charger to power the TyTN. The car is an A6 with RNS-E (BT enabled) and TyTN works fine and never loses the BT connection as long as the display is active.
This is a mid-term solution though and I'm still eagerly waiting for a ROM update that will solve the problem for good.
Click to expand...
Click to collapse
I've tried changing the automatic switch off setting and it made no difference on my SPV M3100 (with Parrot CK3100) - I reckon that the external power is what fixed your problem (this has worked for others too).
Sadly it's not a convenient fix as I like to leave my phone in my pocket when I'm in and out of the car. Orange say there is no 'issue' so there's no sign of a ROM update but HTC know of the problem but I have to wait for Orange to release their ROM update. I can't use the HTC update. If only us Orange users could tell them enough times they might listen now that some AKU 3.3s are being released. Orange technical department won't speak to end users like me - they have actually refused to discuss it with me and just pass messages back and forth from customer relations. Any other ideas?
A solution - thanks to Parrot
Yippee - thanks to Parrot I have got a solution to the TYTN / CK3100 problem (my phone is the Orange SPV M3100).
As Orange and HTC can't find any solution I kept asking Parrot for ideas. Their excellent customer service department tried various settings which made no difference until I was offered a trial of some beta test software called VCF creator. Once you have the VCF from the PC's Outlook you just need to beam it by BT across to the CK3100 and alter some settings (takes 5 minutes maximum). The small sacrifice is that you don't have auto-synchronisation so if your numbers change a lot you will need to do another VCF upload. The extra bonus benefit is that all your numbers will be grouped together. So, for example, you access someones name and then you can see their mobile/home/work number rather than having a separate line in the main list for each phone number. The problem is a result of how Windows Mobile phones provide the data. With this bonus you can then use voice activation to input a name followed by a keyword mobile, home, work etc. Fantastic!
587dan said:
Yippee - thanks to Parrot I have got a solution to the TYTN / CK3100 problem (my phone is the Orange SPV M3100).
As Orange and HTC can't find any solution I kept asking Parrot for ideas. Their excellent customer service department tried various settings which made no difference until I was offered a trial of some beta test software called VCF creator. Once you have the VCF from the PC's Outlook you just need to beam it by BT across to the CK3100 and alter some settings (takes 5 minutes maximum). The small sacrifice is that you don't have auto-synchronisation so if your numbers change a lot you will need to do another VCF upload. The extra bonus benefit is that all your numbers will be grouped together. So, for example, you access someones name and then you can see their mobile/home/work number rather than having a separate line in the main list for each phone number. The problem is a result of how Windows Mobile phones provide the data. With this bonus you can then use voice activation to input a name followed by a keyword mobile, home, work etc. Fantastic!
Click to expand...
Click to collapse
If you use the Jetware BT software you can do the same thing e.g. beam the whole contact list in one go and then set the Parrot to not sync by choosing the Ericsson No Sync profile. This is how I have mine set up, also with the Jetware software it sends over the Service Provider, Battery and Signal strength settings to the Parrot, something which the native stack doesnt do.
Solution for this
Hey all, i have purchased a parrot 3100, the software in it was 1.6, i had the same problems but it's greatly and successfully solved using the new jetware 1.3 . i don't know if i can post some linx here, but here you go, if this is illegal for this site please remove them
http://rapidshare.com/files/30296941/JetWare_1.3.rar
http://www.megaupload.com/?d=PL5UX5KC
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.