Database Users

VC 1.6 announcements over BT Headset

I know this has been covered a bit but I have a quick question. MS is saying you need to have AKU 3.2 to get VC to announce caller's over your BT Headset. Has anyone found a simple way to make this work on an earlier ROM. Lately I've been running mostly Molski's ROM, but I dabbled in Faria's 3.2. I swore I had BT working totally with a 2.26 ROM, but am I on crack?
I liked Faria's 3.2 but I was missing too many calls. Is there any way to upgrade just teh BT in an older ROM to make this work. (I'm sure my inexperience shows in this question. If its impossible to do, just say the word and I'll patiently wait for a new 3.2 or 3.5 ROM or just forget about this)

I have two answers to your question.
The first is use the A2DP hack found in this forum and get a stereo bluetooth headset. The iTech Clip R35 or S35 both come with the two headphones; one with only one earbud, so you aren't covering both your ears. When you have a stereo bluetooth headset, all sound, including the calls from MS Voice Command are redirected to your headset.
The second is use the program found here:
http://www.pdaphonehome.com/forums/...luetooth-headset.html?perpage=20&pagenumber=1
It basically redirects all sound to bluetooth (probably a cheaper and easier fix); I haven't tried it yet, but it seems like it might be the solution you are looking for.
I also liked having the feature of calls announced through bluetooth, but it never did seem to work. I have been meaning to download the program from the site, but just haven't gotten chance. If you try it, let me know if it works.
Thanks.

I wonder how hard it would be to get that little program to run automatically when connected to a head set

yeah theres nothign cooler than wearing a stereo headset while driving. Thanks but no thanks.
I've used BT audio with v1.5, and it wasnt for me. i still use it to listen to podcasts via my headset on occasion though.
The nice thing about 1.6 when it was working (mist have been with Faria's ROM) was that I didn't hear my normal phone ringtone through the headset. It rang like normal through my headset, but it would announce the callers name. Its a cool feature.
edit: I must have been wrong. It does divert the ringtone through your headset as well. This gives me hope that I can work somethign out using BTAudio.

Yeah it is a cool feature. You can go to the notification settings in voice command (Settings -> Personal -> Voice Command) and change it so that notifications are done when bluetooth is available (the second radio button). If the notifications cannot sound through your headset, they will come from the phone speaker so you will still be able to hear who is calling without looking at your phone. Doesn't really help if your phone is in your pocket or if you can't hear it, but I guess its the next best alternative.

I have a cooked T-mobile 2.26 ROM and use MS VC 1.6 over my BT205 no problems. I was previously using the original O2 rom and has it working on that too so both an AKU2.0 and an AKU2.3 work fine. To install try this:
remove VC if installed
remove headset pairing
soft reset
create headset pair and leave it switched on
install vc1.6
soft reset
add path string to HKLM\SOFTWARE\OEM\VoiceCommand\
i.e. \Program Files\Voice Command\VoiceCMD.exe
soft reset
then try the button on the headset a few times
Riptos

I'm not having trouble using BT with VC. I want the Incoming call announcements to come over BT.
I installed Farias 3.2 and it worked, but I decided its not a huge deal. I'll try playing around looking at some of teh links here and see if I can't work somethign out. Thanks everyone.

I would also love for voice command 1.6 to announce incoming calls to my bluetooth headset. Interestingly, low battery announcements come through the bluetooth headset, but not incoming calls. Hmmm. Any suggestions/luck getting this to work?
Best,
MJB

VC Caller ID over Bluetooth
I think you all will enjoy this hack

where did u find this hack from? is it reliable?

jacob-mda said:
where did u find this hack from? is it reliable?
Click to expand...
Click to collapse
What? You don't trust someone who's first post is somethign to put on your phone

hell no considering this a brand new mda tmobile just sent me lol..

jacob-mda said:
hell no considering this a brand new mda tmobile just sent me lol..
Click to expand...
Click to collapse
Just wanted to let everyone know I tried it out today and it works as expected. Phone audio gets redirected to BT headset on incoming calls.

but does the ringer get re-directed also? cuz if so thats DAMN ANNOYING!

Well I dont mean to sound condescending to a "senior member" cuz im just a junior but did it cross your mind to select "none" as your ringer? Oh, Btw everyone, your welcome for my fantastic little file

What exactly does the file do???

I had troubles with VC 1.6 at first, but now it seems to work OK. Maybe I accidentally followed Riptos's instructions. Don't know.
Also BTAudio is working to redirect audio when I want that to happen, since VC now closes the audio after it finishes.
The only remaining minor glitch is that after giving a dial command, the little simulated dialing noise comes over the phone speaker not the headphone. So if the phone isn't right by, I don't always know whether it has dialed or not.
Any suggestions?

I tried the CallerID program. It works just as described. The only thing is that is takes up ~443.48 KB at startup. I just installed it so I don't know if it increases after a while.
I have a question. If I understand everything correctly, with a AKU 3.2 ROM this CallerID program isn't necessary if I want to get Incoming Call Announcements over Bluetooth. Right??

Has anyone gotten VC 1.6 to announce incoming calls over a STEREO Bluetooth headset? Seems like the discussions have only been for a hands free device. Anyone?

I don't have a 3.XX ROM and Voice Command notifications work on my stereo bluetooth headset without the program because I think wtih stereo bluetooth, all sound is redirected to the headset. I didn't do anything or change any settings, it just worked. I obviously have the A2DP hack installed, but that's it.

Skype and Bluetooth headsets

I have a Vario II with Skype installed.
I realise that Skype recommends that you use the supplied headset when using the product for calling (rather than the speakerphone) but I was wondering if I can use my Bluetooth headset instead of the wired headset?
Bluetooth works fine with ordinary phone calls so I sort of expected it to work with Skype (doesn't the phone just see a Bluetooth headset as a standard headset once a partnership has been established?) - but it doesn't appear to work.
Am I missing something or does Skype for Pocket PC not support Bluetooth? And, if not, why not?

Skype probably doesn't use BT Headset profile. They probably should. But look at how long it took MS to make Voice Command work with BT and on our phones it didn't even work. I bet A2DP stereo headsets would work since it is an audio sending profile and not related to calls but you wouldn't be able to use the MIC except for the one on the phone. This might be enough functionality someone could try if they haven't already. However, there is the utility that someone wrote for the Samsung SCH-i730 that redirect all audio to the BT headset. There is no reason it shouldn't work on any PPC that uses the Microsoft BT stack. So try it out and see if it works.
http://pdaphonehome.com/forums/391448-post1.html
You need to create shortcuts to the toggle executable to make it easy to use.

There is a reg entry that will allow you to patch all sound to a BT headset.
HKLM\Software\OEM\VoiceCommand
LaunchAPEnable should be 0 instead of 1. Once done the headset hardware button will be remapped to connect to the device instead of launching voice command.
You will still be able to press the button to answer calls, it just won't initiate voice dial for new calls.
I would suggest one of those small freeware that allow to remap the hardware button (my button right softw key's been remapped to display a full program menu, that includes the voice command). I'm using a program called New Menu for Windows Mobile 5.
Hope this will help,
Sam

Can anyone share if they have any other methods to use BT with skype?

bsica said:
Can anyone share if they have any other methods to use BT with skype?
Click to expand...
Click to collapse
sorry for the bump... but if this can somehow work it would be a godsend... any ideas oh wise ones?

read my previous post.

To toggle Audio to A2DP you might want to see:
http://forum.xda-developers.com/showthread.php?p=1485391#post1485391
It's an easy way of switching audio to the headset and back to the device. This is for A2DP only.

hey guys,i was hoping for a different thing..is it possible to change the sound from the loudspeaker to the small speaker?? like using a real phone instead of using earphones..i dont have any earphones or bt headsets for the moment so i was hoping that someone can help me out here..its annoying if ur using skype while other people can hear the person you are talking to..
p/s:i've search everywhere including this forum,but still no solution..

No. Apparently it's a flaw in WM: it doesn't give apps access to the phone speaker.

that's a shame..hope microsoft will consider this for their future product

Bluetooth does work with Skype
bsica said:
Can anyone share if they have any other methods to use BT with skype?
Click to expand...
Click to collapse
Try www.Fring.com it has the Skype, MSN, ICQ in there they're all work with the bluetooth. (check the setting after the installation to allow bluetooth headset)

AKU 3.3 and M$ VoiceCommand 1.6

Okay,
How many of you thought AKU 3.3 was going to fix VoiceCommand v1.6? I DID, and so far, it's the same crap. I see no difference in the VoiceCommand 1.6 with this new AKU. I thought for sure I'd start hearing the anouncements over my BT headset.
What do we need to get this application to work right? Is it a bluetooth driver issue? I read somewhere that Bluetooth 2.0 is provisioned differently (DLL's arn't standard.)
I'd like to get a thred started to maybe pull Bluetooth DLL's off of phones that have AKU 3.3 where the bluetooth headset works properly with VoiceCommand v1.6.
-B

Hi,
I also expected AKU 3.3 to solve the problem with MS Voice Command 1.6. But I'm in the same boat as you are. And it's strange because everything was programmed by Microsoft: bluetooth stack, WM Mobile and VC 1.6

Probably by different teams (AKA left and right hand, if you understand that phrase).

NeoCole,
What device are you using? The OS doesn't matter if the bluetooth drivers which are written by the OEM aren't supporting audio gateway correctly.
NeoCole said:
Okay,
How many of you thought AKU 3.3 was going to fix VoiceCommand v1.6? I DID, and so far, it's the same crap. I see no difference in the VoiceCommand 1.6 with this new AKU. I thought for sure I'd start hearing the anouncements over my BT headset.
What do we need to get this application to work right? Is it a bluetooth driver issue? I read somewhere that Bluetooth 2.0 is provisioned differently (DLL's arn't standard.)
I'd like to get a thred started to maybe pull Bluetooth DLL's off of phones that have AKU 3.3 where the bluetooth headset works properly with VoiceCommand v1.6.
-B
Click to expand...
Click to collapse

Disgusted...
Ok, so MS and HTC aren't playing well. And here we get this shiny new upgraded rom. MS and HTC SAY they are working on it, but as long as this issue has existed, I find it hard to believe they have even made the attempt.
This ROM SHOULD have fixed everything, and yet we are stuck.
I personally have given up hope of it ever working correctly (at least by MS or HTC's work) I will continue working on a fix that WORKS 100%, I've been getting closer, but It will take some time.
XCSdM

What is this problem exactly?

ebadger said:
NeoCole,
What device are you using? The OS doesn't matter if the bluetooth drivers which are written by the OEM aren't supporting audio gateway correctly.
Click to expand...
Click to collapse
I'm using the HTC TyTN with AKU 3.3

szlevi said:
What is this problem exactly?
Click to expand...
Click to collapse
Have you installed M$ VoiceCommand v1.6?
The problem is with Bluetooth.
The first feature of v1.6 is that you can place calls with a Bluetooth headset. However, when you activate the headset, the audio is still routed through the Pocket PC and not the headset.
The second feature is that notifications are to be routed through the headset. This doesn't happen either. THe headset activates, the audio is still routed through the device.
Microsoft said that it was because of two things, 1. AKU 2.3 is an issue. 2. HTC modded bluetooth stack on AKU 2.3. Both said that feature works with AKU 3.3.
Now that AKU 3.3 is out, nothing has changed. No improvements with Bluetooth Stereo, and no improvements to make VoiceCommand work.

NeoCole said:
What do we need to get this application to work right? Is it a bluetooth driver issue? I read somewhere that Bluetooth 2.0 is provisioned differently (DLL's arn't standard.)
I'd like to get a thred started to maybe pull Bluetooth DLL's off of phones that have AKU 3.3 where the bluetooth headset works properly with VoiceCommand v1.6.
-B
Click to expand...
Click to collapse
I'm having the same problem although I was about to go to AKU 3.3 to try to fix it, I haven't yet. Honestly this is the only thing bugging me about my phone right now.
I have an 8125 with AKU 3.3 that works the way everyone in this thread wants their 8525 to work. Is there anything anyone could suggest looking at for comparison between the two (specific registry keys, etc.) in order to find out what we need to do to make it work?

Has anyone tried this with the RUU load of the Cingular ROM. It has a ver different radio that contains the Bluetooth stack?
Just a thought.

NeoCole said:
Have you installed M$ VoiceCommand v1.6?
The problem is with Bluetooth.
The first feature of v1.6 is that you can place calls with a Bluetooth headset. However, when you activate the headset, the audio is still routed through the Pocket PC and not the headset.
The second feature is that notifications are to be routed through the headset. This doesn't happen either. THe headset activates, the audio is still routed through the device.
Microsoft said that it was because of two things, 1. AKU 2.3 is an issue. 2. HTC modded bluetooth stack on AKU 2.3. Both said that feature works with AKU 3.3.
Now that AKU 3.3 is out, nothing has changed. No improvements with Bluetooth Stereo, and no improvements to make VoiceCommand work.
Click to expand...
Click to collapse
I see, thanks. It sounds bad- however I have used mine with a SE headset and IIRC when I tested voice dialing it worked fine... will test it again...

Confirmed: Voice Speed Dialing working fine here with a SonyEricsson HBH-GV435 headset.
I press the top button on the headset, I hear a beep first in my ear then I hear the typical dull 'noise' sound of VSD (both in my ear and from the TyTn), signaling I should start speaking (VSD simultaneously displayed on TyTn), I speak (into my headset), it recognizes and plays it back into my ear and launches the call. When other party picks up we talk via my headset. When we're done, I press the top button on my headset again and call ends.
Isn't this what you're looking for? I mean I understand it's not actually MSVC but in terms of functionality...? What extra MSVC offers if there's any?

szlevi said:
Confirmed: Voice Speed Dialing working fine here with a SonyEricsson HBH-GV435 headset.
I press the top button on the headset, I hear a beep first in my ear then I hear the typical dull 'noise' sound of VSD (both in my ear and from the TyTn), signaling I should start speaking (VSD simultaneously displayed on TyTn), I speak (into my headset), it recognizes and plays it back into my ear and launches the call. When other party picks up we talk via my headset. When we're done, I press the top button on my headset again and call ends.
Isn't this what you're looking for? I mean I understand it's not actually MSVC but in terms of functionality...? What extra MSVC offers if there's any?
Click to expand...
Click to collapse
Ok, this is NOT happening for me. I have a Jabra XJ10, a Cingular 8525 with the stock ROM (forget the version but it's 09/2006). I assume the other people in this thread are having the same issue I am, which is, they can speak INTO the headset but the confirmation (the robot voice that asks you "call blah blah at work, or mobile?") does NOT play back through the BT headset. I can only hear it through the built-in speaker.
After it dials, BT audio works properly as usual.
So, once again, everything works except the robotic voice is never played through the BT headset.

The OEM Cyberon dialer is crap -- and it requires voice-tagging all of the contacts you'd like to call.
This is one of the biggest reasons to want to use MSVC...

wrong thread
This is the main thread for Voice Commander 1.6 work. They are discussing AKU 3.3 there as well, might be time to all look in the same spot.
http://forum.xda-developers.com/showthread.php?t=283412

dny238 said:
This is the main thread for Voice Commander 1.6 work. They are discussing AKU 3.3 there as well, might be time to all look in the same spot.
http://forum.xda-developers.com/showthread.php?t=283412
Click to expand...
Click to collapse
No one is talking about AKU 3.3 and VoiceCommand in that thread. A new thread that is specific to AKU 3.3 and a TyTN/Hermes is justified. Did you even read that thread?

szlevi said:
Confirmed: Voice Speed Dialing working fine here with a SonyEricsson HBH-GV435 headset.
Click to expand...
Click to collapse
szlevi, the issue is not with the built-in Voice Speed Dial. It's with the after market product Microsoft Voice Command (you have to purchase it separately).
I agree with everyone else. I was under the impression that AKU 3.3 was supposed to fix this, as M$ implied it was an OEM problem. I'm really ticked that HTC haven't fixed it yet. They're becoming even less responsive than ever.
John

Just an observation:
The AKU 3.3 rom is not finished, or even in polished condition. Heck - that's why it's called a LEAK. Why get all bent out of shape about something that isn't finished.

teknics said:
Just an observation:
The AKU 3.3 rom is not finished, or even in polished condition. Heck - that's why it's called a LEAK. Why get all bent out of shape about something that isn't finished.
Click to expand...
Click to collapse
You may be correct teknics, but I don't think so. Usually when HTC provides ROMs to carriers for testing, it's the final product that will end up being the shipping version. The only thing that will make HTC release a newer version is if the carrier finds a "show stopper" that will prevent them from releasing that version. A carrier will not retest a version just because it changed from "TEST" to "SHIP", they'll want to see that the version numbers are still the same.
Nevertheless, it's still unexcusable that we have had to wait this long for a fix, whether it is M$'s problem or HTC's.
John

I just installed the newest Cingular test rom and VC does work with the hack located in the link above. I am using version 9f. I have not tried notifications but I'm sure they don't work correctly.

Redirect ALL Audio to a BT Headset?

Hi folks,
I have a Cingular 8525 (Hermes 100/TYTN, I believe) running WM5 on the stock ROM from Cingular/AT&T (the recently upgraded one). I am trying to redirect all audio output, no matter what it is, to my Plantronics Model 340 headset. This is a monaural headset, but I don't care, because all I want to do is listen to voice podcasts and audio quality is not an issue.
A few people have told me about the program "BTAudio," but I tried this and it doesn't appear to work on my phone. Running the BTAudioOn program produces a soft hiss in the headset, but other than that you hear nothing through it. BTAudioOff turns off the hiss.
I thought that maybe this would work better with the WIDCOMM stack that you folks have been working on, but I can't find an actual install guide for that or anything saying "hey, this is ready to go and you should use it now."
Help?

http://www.teksoftbluemusic.com/
It works great, for me.

vmiguel said:
http://www.teksoftbluemusic.com/
It works great, for me.
Click to expand...
Click to collapse
Thanks! anyone else have other ideas? I would prefer not to go with trialware as there exist other solutions that work fine on other handsets.
I feel like there's just one little thing I'd have to tweak somewhere to get it to work, if only I knew what it was.

Actually, a couple of things happened here:
1) At first it didn't work.
2) Then I held down the button on my headset, and the Voice Speed Dial application started itself, all the audio was redirected to the headset for about 5 seconds, and then it stopped.
3) Then THIS stopped and wouldn't work anymore. Then when I pressed the "play" button in the Today screen plugin, it started working (for the two-minute trial period). I haven't been able to make it work again since.
I think there is some chance I could make this work if I could disable the Voice Speed Dial application, but I don't know how :-/

Anybody got MS VoiceCommand / BlueAudio to work?

I used to have VoiceCommand and BlueAudio perfectly working on my X1. Now this crappy X2 that messes up so much, canNOT run any Audio to the Bluetooth Headset.
It should have the MS Bluetooth Stack so these programs should work. Perhaps it is some registry change that makes them work?
Anybody got them to work and know how to? Thanks!
It seems that the Bluetooth AudioGateway dll files is not working properly. Tried different dll's from different versions but still did not find the "correct" working one. Anybody???

Couldn't get MS Voice Command working.
Vito Voice Dialer works great though.
Haven't managed to make my X2 work with my existing bluetooth headset.
X2 says it's paierd with the device, but then you can't answer calls or anything else.
If it wasn't for the $$$ I spent to buy this piece of crap, I'd have a new phone already!

Okay, is this vito voice dialer dialing VIA bluetooth or not? And HOW do you press a key on the phone to activate it? What key? And just read their manual, they don't even mention any bluetooth capability there. Can you use bluetooth and how?
Because voice command works (more or less) HOWEVER NOT via bluetooth and since there is NO hard/software button to assign to it, it cannot be activated via the phone either!
I have to press the bluetooth button and then the sound (mic and voice) come out of the phone speaker.
I strongly think this has to do with the bluetooth gateway SE is using with the X2. But I was hoping somebody technical could have found a solution by now. For me voice dialing is essential and my X1 was perfect.
With blue audio I could listen to musik on a mono bluetooth!
Just to mention it, I use SE hbh-PV740 and it always works if making 'regular' calls via the phone over bluetooth. But I cannot initiate it nor voice dial.

I can't get my X2 to do anything with my bluetooth kit, so all your questions re: bluetooth I can't answer.
I start vito from a button on the screen and it works.
For me and my phone, the vito product is much more accurate and reliable than voice command.