Database Users

Bluetooth Shuts Itself Off

I have experienced a strange problem with my JasJar bluetooth radio. The bluetooth radio seems to turn itself off from time to time. I think it is somehow related to WM2005, because I had the same issue with a Himalaya running WM2005 (thanks to Buzz). What is weird is that the blue light continues to blink. If you go to the wireless manager applet, it sometimes shows the bluetooth as on and sometimes as off, but if you go to the bluetooth setting, it shows the radio as off. Turning it on, with the applet, or in the bluetooth settings, is only sometimes successful in actually getting it working again. Ressetting the device works every time. No need to re-pair.
Any suggestions?
TIA
Panabax

INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!

craigiecraigie4 said:
INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!
Click to expand...
Click to collapse
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.

Edit: i've made a mistake in the registry... found by ekapco. THANX.
uploaded new cab below...
buzz

Buzz, you're a legend!
Trying it right now, will report back tomorrow.
Can u not help us on all our other problems (http://forum.xda-developers.com/viewtopic.php?t=28343)? Your posts on Buzzdev.net indicate that you're far more technically savvy than most ppl here.

Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.

ekapco said:
Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.
Click to expand...
Click to collapse
BlueAngel? I think, this is a Universal fix.

BlueAngel? I think, this is a Universal fix
Click to expand...
Click to collapse
So ????
Registry is almost the same on this issue.

ekapco said:
In your headset fix shouldn't reg setting be hds1: instead of hds1 ?
Click to expand...
Click to collapse
of course... i'm so stupid... sorry...
should be hds1:
THANX ekapco...
buzz

ThExSenatoR said:
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.
Click to expand...
Click to collapse
WOW!
That was a helpful post. Thanks.
Buzz; can you explain what your fix actually does? I don't have a cab extractor here to look at the contents.

fix sets hds1: = dword:0 for 'unattended' system power state.
hds1: is headset device identifier.
bkl1: is backlight
wav1: is wave device
dsk1: is block/disk device
etc...
let's have some fun with those power settings...
open your regeditor and change
[HKLM/system/currentcontrolset/control/power/state/on]
"bkl1:"=dword:4
and
[HKLM/system/currentcontrolset/control/power/state/backlightoff]
"bkl1:"=dword:0
after changing the regs, press power button to off and on again. that will flush and apply new settings.
ok. the above settings will REVERT backlight's behaviour. I mean, when device is on, backlight is off. after inactivity timeout, light goes on.
well... funny experiment...
that proves, that devices could be powermanaged from here.
if you've had enough fun, revert those settings to normal. ;o)))
now set in:
[HKLM/system/currentcontrolset/control/power/state/unattended]
"bkl1:"=dword:0
that SHOULD turn the backlight on, when you leave the device untouched for a longer time (when the display goes off) or if you press the power button.
so leave it untouched and watch the display to see what's gonna happen on the 'unattended' state.
after approx. 5 minutes (never measure that), just when the display is about to off itself, BACKLIGHT FLASHES for a second and goes OFF.
why? we just said, bkl1:=0 (ON)?
so our settings are overriden. maybe that 'flags' settings?
lets see later, but exactly the same happens with BT connection even if we say ON, it goes off...
I have to sleep now in 'unattented' state, but meanwhile you can look at msdn, coz I saw those flags description there.
good night
buz

Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?

EyeOfTheStorm said:
Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?
Click to expand...
Click to collapse
Please follow my last post here or you have to tell me your wifi device handle.

I try to find the device ID
In "HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Power/Interfaces" i fount this 4 IDs
{8DD679CE-8AB4-43c8-A14A-EA4963FAA715} Power-manageable block devices
{98C5250D-C29A-4985-AE5F-AFE5367E5006} Power-manageable NDIS miniports
{A32942B7-920C-486b-B0E6-92A702A99B35} Generic power-manageable devices
{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1} Power-manageable display
Does this help? Or am I wrong?

O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?

craigiecraigie4 said:
O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?
Click to expand...
Click to collapse
...stupid question, but:
does it actually have MS BT stack??
buzz

there is another problem, it seems that my mobile doesn't accept any connection from any nokia mobile, it says to them (unable to connect), i don't know why???????????

I too am experiencing Bluetooth problems with my O2 Exec and a Motoroa HS810 headset. I use voice tags quite a bit and for the most part this works well however sometimes the EXEC fails to respond to the button press on the headset.
I first noticed this when I did the reg hack to make MS Voice Command the default Voice dialler and presumed that maybe there was a problem with MS VC so went back to VoiceDialler. However the same thing happens with VoiceDialler. To get it working again i have to turn off bluetooth in the Wireless Settings panel and then turn it on again. After this it starts to work again (but not ideal if your driving).
I think this might be the same problem mentioned above, i.e. bluetooth says it is on, the blue led flashes on the phone, but in reality it has switched itself off. I did some more testing while the headset was not initiating voice dialling and called the Exec. After a short time, the headset icon appeared on the "Incoming Call" message area and my headset burst into life. This would make sense I suppose because doesn't Headset mode start bluetooth up when a call is received (presuming it is off)?
Looked at Buzz's reg hack for Bluetooth but didn't really understand it

Here's what didn't fixed it for me.
After more reading today I realize I was way wrong.

Re: Here's what fixed it for me.
I can confirm that these registry settings work perfectly on the blueangel Great job.

MS Voice Command and Jabra BT200 Headset

Are they compatible?
I've changed the registry to use the voicecmd.exe file instead of the inbuilt Voice Dialer (which I must admit, I never tested with the Jabra!)
But when I press the Jabra button, I hear a noise in my ear but it doesn't seem to activate anything on the MDA Pro itself...
What am I doing wrong?

Have you got the lid closed? If the screen is closed it doesn't work.

This is mad.
If I press the button on my Jabra, I now hear that the voice path is activated but saying "help" into the Jabra mike doesn't do anything. No "mike" icon on the device (lid is open) and nothing happens.
However, with this voice path open, if I then press the voice command button on the device, everything works through BT. I hear the woman and can speak to her.
However, pressing buttons on each device seems a very silly way of doing it.
I should be able to press JUST the headset button, right?

I use the same hardware without issue
I find some commands dont work so well over bluetooth - but call seems to work OK!
I find the built-in mike is better to practice with first THEN try with the headset
I use DIAL <name> at HOME or on mobile etc and this seems OK
My only ***** is than on both BT and the device the VC voice is too low!!
While I remember to 200 Headset supports two profiles - I find the basic one works better with VC (that way you dont accidentally redial if you double tap the button!)

Found the problem. I reinstalled the VC software with no joy, so checked the reg entry. I was missing the space between "Voice" and "Command", so no wonder it wasn't working...
I would have expected an error of some kind instead, maybe... but at least it is solved now.

I got VoiceCmd to not Hang after call with some BT Headsets!

Hi,
Was playing around with a way to get my Motorola H700 to not hang after the first use. I don't know how to code (at all) but I wrote a little VB app that Monitored the State and Notification PhoneCallTalking to see when a call was initiated, then monitored to see when the call ended at which point I executed BTAudioOn.Exe from BTUtils causing the channel to open again so I push the button and that's it, I could make call after call just like my old HS850. This will probably work with any headset that hangs after the first call.
Only problem, like I was saying, I can't program, I did all this in Do While Loops so it's pretty unusable since it kills the processor. I don't know how to work with Events or Registering for notifications.
Anyways, if there is anyone who can code and is looking for something to do, maybe you could make something similar (this way or a better way) that can run resident and monitor for the end of a phone conversation and then execute BTAudioON.exe or I guess if you know how to program the MS Bluetooth Stack, open the channel again.
If not, I guess I'll keep learning and try to figure out how to do it properly by handling the notification trigger and wait for it without killing the CPU

I've been looking for something like this! Keep us updated if you find a way to do it without putting too much of a load on the CPU.. I'm getting into WM programming but I have no idea how to capture call/notification states yet.

Re: I got VoiceCmd to not Hang after call with some BT Heads
shoey5 said:
Hi,
Was playing around with a way to get my Motorola H700 to not hang after the first use. I don't know how to code (at all) but I wrote a little VB app that Monitored the State and Notification PhoneCallTalking to see when a call was initiated, then monitored to see when the call ended at which point I executed BTAudioOn.Exe from BTUtils causing the channel to open again so I push the button and that's it, I could make call after call just like my old HS850. This will probably work with any headset that hangs after the first call.
Only problem, like I was saying, I can't program, I did all this in Do While Loops so it's pretty unusable since it kills the processor. I don't know how to work with Events or Registering for notifications.
Anyways, if there is anyone who can code and is looking for something to do, maybe you could make something similar (this way or a better way) that can run resident and monitor for the end of a phone conversation and then execute BTAudioON.exe or I guess if you know how to program the MS Bluetooth Stack, open the channel again.
If not, I guess I'll keep learning and try to figure out how to do it properly by handling the notification trigger and wait for it without killing the CPU
Click to expand...
Click to collapse
Good luck and keep us posted. One "use case" to keep in mind is if you initiate VC which doesn't lead to a phone call since VC supports other commands.
I tried something similar to what you are trying to do and it's just too complex because of the different outcomes of initiating VC

I think it'd probably be best to just fix the dialing part - I don't really care about the launching of the apps, etc.
Some of the voice commands, like "What day is it" didn't seem to break the voice channel anyway.
I hate to say it, but it's probably best to just fix the simple stuff and wait for a BT enabled version from Microsoft to fix the rest.

VCBTFixer - My First Attempt
Hey guys here's what I came up with so far. It's not much but it works, been using it all day without ever taking my Wizard out to reset the headset
When running in the background, it will monitor for a hangup (the point where your headset usually crashes after the first call) It will wait a second and then open the BT Audio Gateway, just press the BT headset again to turn it off, and then press it one more time and you'll hear VoiceCommand waiting for you again
Ok remember this is my first attempt at programming so use it at your own risk And remember it's not 100%, I still have to check for a failed call or if you terminate before the call actually starts, check to see if the headset is being used before trying to turn on the audio gateway ect.
I'll probably get rid of the dialog or keep it, I don't know, I was thinking it could be useful to configure a sound that can be played when the audio gateway opens again, this way you get reminded to press the headset button again to turn off the BT Audio Gateway Maybe display and allow you to select which headsets (if you have more than one) this program should work with if some work and some don't, all that kind of crap.
Anyways, let me know if it works.

Im no WM programmer but cant u open the BT channel then close it again pro grammatically, or will that cause the same type of "crash"? I would love to see this work because I WANT my damn H700 back, till then I'm stuck with this hs850.
Thanx; Lew

lewcamino: Tried that but it still hung, only way I could get it to work is to open the chanel and then close it. Anyways I tried this program with my H700 and it worked, give it a try, you have to be logged in to see it.
I'm no programmer either, maybe someone could write a much better version. I think the best way (if it's possible) would be to close the BT Audio Gateway just before VoiceCommand started dialing (the phone should open the Audio Gateway when the call starts and then it should be good (I think) but I don't know if that's even possible to detect.
So for now, until someone figures out a better way or Microsoft releases a new version with BT support, I guess this works. Used it all day with my H700 didn't have to push any buttons on the device between calls which is what I wanted.

Thanks shoey5! Your program works great with my H700.
Do you have any updates? Also, how did you create the .exe? What tools did you use? Are you willing to give up your source code? I would love to dig into it, modify it, upgrade it.
Again, thanks for the great program.

Congrats on getting something to work. What happens if you close the boom of the H700 after a call? What if you use VC to check your battery signal or ask what time it is?
Looking forward to seeing future versions - once it's good and ready I can go back to my H700. Using the HS850 for now.

Ok Second Attempt, if learning VB.Net for the first attempt wasn't bad enough, had to start learning C++ for the second
This one is a lot better though it's late so I haven't been able to test and it needs some error checking but it's much more useable. Ported it to C++ so now only takes 3.90K as apposed to the 200K VB.Net (Sucks) version was taking so it's acceptible to have it running in the background. Also uses a different method of refreshing BTAG after a call though I'd like to find a better way. Also got rid of the UI so you can throw it into \Windows\Startup to have it running when device loads.
Let me know how well or how bad it works.

Cool - thanks a lot! This seems to work!

Doesnt work with german rom... are there any paths hardcoded which may be named different in other languages? (Programs for example)

Hi Shoey5,
Just for your information I have a O2 XDA Mini S WM5 and it does not work as intended, works once after that it needs a soft reset.
I send you a PM with contact details.

Shoey,
your little app works really well! Only occasionaly will there be some kind of hiccup between the MDA and the headset, and I will have to reset the MDA.
It also seems that you have to be alittle patiend between calls to give the headset/MDA time to be ready to respond.
I can make repeated voice commands and even activate redial with a double tap on the headset button.
I would encourage you to keep working on this program so the VCBT functionality can be made even more stable!

Shoey,
your little app works really well! Only occasionaly will there be some kind of hiccup between the MDA and the headset, and I will have to reset the MDA.
It also seems that you have to be alittle patiend between calls to give the headset/MDA time to be ready to respond.
I can make repeated voice commands and even activate redial with a double tap on the headset button.
I would encourage you to keep working on this program so the VCBT functionality can be made even more stable!

Voice Commands - Make It Even More Awesome?

I've recently been having a play with the Voice Tag function on my Wizard. I can call any of my contacts by voice, and I can perform a plethora of functions on my phone by voice (helped by the added hardware button functions that Pocket+ provides). Now i'm wondering if I can do even MORE by voice, i.e. a spoken password, dialing by saying each number, that kind of thing?

Yeah,
Dump the cheezy Cyberon Voice Dial and get Microsoft Voice Command or Cyberon Voice Commander.
Both allow you to access PDA functions such as launch programs, access calander etc.
Additionally they allow "Dial 444 555-1234"
In my opinion MS Voice Command is better.
I've played with Cyberon Voice Commander because it will read e-mail and text messages but I've found it to be useless. Also Cyberon has too much of a delay from activation to ready for voice input for my tastes.
Oh yeah, neither of these requires "Voice Tags", they work by recgonizing your spoken voice!
Cyberon Voice Commander costs about $20,
MS Voice Command is about $40.
Both can be purchased at Handango.com

Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?

Danny-B- said:
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Click to expand...
Click to collapse
Maybe that's why none of these products supports it!!

I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.

jimmyhauser said:
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
Click to expand...
Click to collapse
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.

JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.

JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Same for me. Sometimes the recgonition isn't the same over bluetooth, but I never have to try more than twice. I use my VC for everything.

jimmyhauser said:
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
Click to expand...
Click to collapse
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.

VC Usage Vs. VS VC Memory Usage
I've had VC on and off of my 8125 since I bought it in April.
The main problem I have with MSVC is whether its use (or lack there of) validates the amount of memory it uses.
For someone that makes calls primarily off of his recent call list, I find that the usability benefit does not outweigh the memory usage.
Wish there was a way to disable / enable the functionality, as to release that memory for other applications.

JNGold said:
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
Click to expand...
Click to collapse
Believe me, I am not an expert on this, I am just trying to figure things logically. But I would bet it has to do with the fact that you are probably using a different bluetooth handsfree device than I am. Maybe that was what you were referring to when you said it was a bluetooth issue. Or maybe it is the fact that you have a different model of phone.
What I am saying is that it cant be the bluetooth software on my phone, because the cyberon voice dial works fine over bluetooth, where the MS voice command does not.
And I have voice command on the phone also. All my programs are. I only keep music and videos on the storage card.
And voice command works great when using on the phone itself. I am amazed at how well and how quickly the recognition works. It just doesnt respond well to my Nokia car kit. And maybe that is the problem.
My wife's car has the same bluetooth kit as my car, I am going to try it in her car one of these days to see if I have the same problems there. She has a Nokia 6682, and her bluetooth voice dialling works great.
And also, does VC really use that much memory? If so, I think may take it off the phone. (I use it a little when not in the car) But if it is considerable, then I agree that it is not worth it.

the problem is that without any BT headset i can't get the microsoft voice command to work.
i installed it, dedicate the button. the problem is that when i press it the mic sign appers, i hear the bip and if i say "HELP " it does absolutly nothing.
NOTHING
it just stands there, then another bip comes and the mic sign disappears .
what should i do?

did you turn your mic auto-gain off like the instructions said?

problem solved.
don't know how ...soft reset and bam ! it worked.
the problem is that it hardly recognizes 0 ( zero )
well...i think the old voice dial would do the trick for me...

Keys to success:
1. Load in main memory. (Yes, it's a hog, but to me it's worth it.)
2. Be patient. Sometimes it takes a moment or two to activate.
3. Make sure your volume is not muted. (I admit it, I often walk out of a meeting and get frustrated with why it isn't working... oh, volume is off.)
4. Experiment. Watch the phone while you are playing.
Here are my results with Motorla hs850 .
1. Usually I push once to open the gateway and a second time to activate VC. (Note, I only wear my headset when I need it.)
2. Sometimes the gateway is open for whatever reason and I'll get an immediate bong. So after the first press, I give it a second to see if it will come up.
3. Otherwise, I may get into three presses. One which I think is opening the gateway but is actually opening VC before the bong sounds. A second which I think is activating VC but apparently is closing it. The third press usually then does the trick, but sometimes I'll even have to go to number 4.
So my strategy is:
1. Push button.
2. Wait a slow count for response.
3. Go back to #1 until success is achieved.

Reprogram Bluetooth headset button

I have a Cingular 8125 (2.17 ROM, I believe) and recently got a Motorola HS850 BT headset. It's setup and works great, but I want to know if there is a way to reprogram the call button on the headset so that when you hit it instead of opening the Voice Dial on the phone it can instead open Voice Command (which I use for everything else.) I tried poking around on the boards and didn't see anything specific, any help (or just knowing it's not possible) would be greatly appreciated!
Thanks!
Doug

Found it
I found the answer with a little more searching. It turns out to be a registry entry for Voice Command - and it DOES work with Bluetooth (even though MS' description says it does not.)
Just change this registry key: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path
change the value from \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
Soft reset the phone and voice command will work when you hit the connect button on your phone.
Credit to HowardForums where I found it: http://wiki.howardforums.com/pocket...ice_Command_via_Bluetooth_(HTC_WM5.0_Devices)

I heard that it does not close the audio gateway however when you are done with the call...
is this true?

thanks a lot man, this was buggin the hell out of me! quick forum search and i found ur post. thx for doing the leg work

I placed a call with it and when the call was done used the button on the headset to terminate the call...it seemed to work okay.

i just tried it and it seemed to work just fine. the only thing i don't like, and it probably has to do with my headset, is how long i have to hold down the button for...but i can deal with that, so that i don't have to take out the phone!

I guess that the issue is with the regular voice dialer, you can just press the button to dial out, and when the caller hangs up, the audio gateway closes, you dont have to hit the button to close it.
I'm gonna give this a shot to see if I like it.

I did notice that it seems like I have to hit the call key twice in order for it to recognize the key press....maybe the first is to close the old channel and the second opens a new one? I don't have enough knowledge to say for sure, but there is no visual indication on the phone that the voice channel has not been closed.

That's probably what's happening. If you forget to close the voice channel after your call, you'll run down your headset's battery faster. I can tell that the channel is open because I can hear very faint hissing.
Of course, the point is moot for me because on my device (like many others) this trick only works until a call has been placed and ended. After that the button no longer triggers voice command. :-|