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.

Voice Command Over Bluetooth

Voice Command 1.6 seems to be a bit of a nightmare and i have given up on my hermes for now.
My trinity though is almost ok, the only thing that doesnt work is when i push the voice button on the headset the sound comes out the phone speaker.
If i use the button on the phone though the sound comes out the headset.
How can i change the action of the button on the bluetooth headset to do what the button on the device is doing.
Thanks all.
Rob.

rjefferis said:
If i use the button on the phone though the sound comes out the headset.
How can i change the action of the button on the bluetooth headset to do what the button on the device is doing.
Click to expand...
Click to collapse
FYI I use a SonyEricsson stereo BT headset and I don't experience this problem.

Rjefferis, I experience the same problem as you.
I have a Jabra JX10 headset.
Confirmation voice always comes out of phone speaker, not headphone... and irritatingly, it takes microphone readings from the phone body too. Kind of defeating the idea of hands free voice dialling.

FuzzMunky said:
Rjefferis, I experience the same problem as you.
I have a Jabra JX10 headset.
Confirmation voice always comes out of phone speaker, not headphone... and irritatingly, it takes microphone readings from the phone body too. Kind of defeating the idea of hands free voice dialling.
Click to expand...
Click to collapse
Yeah this seems to be the problem on the hermes too. On mine it works correctly if i use the voice dial button on the phone. So the button on the headset and the button on the phone must be calling slightly different functions. All i need to know is what reg key i have to edit to make the headset button do the same as the phone one.
Try yours to see whether it works using the phone button. I think maybe my a2dp is getting involved somewhere as well.

There is an option about Notifications and Bluetooth devices in the Voice command settings... does this solve you problem?

Not for me.
It is set to read only through handsfree. I havent got my headset here, so I will see what happens if I switch it to the opposite like rjefferis implied.

yeah i doesnt make a difference using the options in voice command.
I think maybe when i push the button on the phone it works through the a2dp to the headset which obviously it shouldnt be.
When i use a non stereo headset then i think it always comes out the phone no matter what.

There are a number of threads regarding this issue and some semi-working fixes to get initiating a voice call through a mono bluetooth headset.
The problem seems to be a difference in the trinity passing audio through the audio gateway using a mono bluetooth headset. Not sure if this is a problem with the implentation of Microsoft's bluetooth stack on the TyTn/Trinity but I'm assuming that's the case.
According to Microsoft's Voice Command site, they indicate that the TyTn (put the Trinity in the same situation) passes audio through the device speaker. They also make note that devices running Windows Mobile build prior to 15097.3.0.0 will pass announcements through the device speaker. This leads me to believe that Microsoft fixed audio to a mono bluetooth headset but I've seen lot's of messages from people running roms higher than this version who still have the problem so sounds like HTC hasn't implemented it.
I've sent emails to HTC who indicate that it's a 3rd party program and there is no guarentee they will fix it as it's a Microsoft problem. I haven't been able to get word from Microsoft if it is being fixed but from their website, seems both parties are passing the buck on this one.
Considering HTC's lack of commitment in releasing updates for their branded products and the delay, we probably won't see another rom after their first release for a while if any since they seem more committed to releasing new products increase their bottom line without keeping their current customers happy. So if it's not in their upcoming rom update and Microsoft isn't releasing a fix, we could be waiting a while. I'd recommend anyone who cares about this issue to send an email to HTC Support. You'll get the generic response but hopefully if enough people complain about it, a fix might fall into their update

Tilt, AT&T Stock ROM, Microsoft Voice, and Bluetooth which work - PLZ Recommend

Greetings,
I have reviewed the Bluetooth vs. AT&T Tilt vs. Microsoft Voice threads, and cannot find a specific answer, so I am going to try to ask a narrow question here ...
... does anyone who has (i) AT&T Tilt with (ii) the AT&T ROMs, (iii) Microsoft Voice, and (iv) a Bluetooth Headset have all 4 working perfectly together? I need to buy a bluetooth headset, and the forums are littered with problems with Voice announcing, or problems answering the phone thru the headset, etc.
That's why I am just hoping to hear from someone who has all 4 of these things ... that work together. Any recommendations for the bluetooth headset are appreciated.
Thanks

My Tilt worked great with the stock ROM, MSVC 1.6.17913 and my BlueAnt Z9 worked flawlessly including announcing calls over BT.

Thank you!
I will look into the BlueAnt Z9. Thank you so very much for responding.
Of course ... if anyone else has the combination of stock tilt/voice/bluetooth, please let me/us know what other adapters might also work.

I did not have any issues with the Motorola H700 and MSVC 1.6.17913 on my Tilt.

H700
Andre - I recall seeing some mention of the H700 on other threads. Can you (please) confirm that you can answer the phone thru the bluetooth, and that call announce works?

jdmba said:
Andre - I recall seeing some mention of the H700 on other threads. Can you (please) confirm that you can answer the phone thru the bluetooth, and that call announce works?
Click to expand...
Click to collapse
I keep my unit on vibrate and ring and this is the way I tested it. I first placed a call using my office phone to my mobile handset in the "vibrate only" and "vibrate and ring" modes. When my mobile handset was on vibrate the notification came through to my headset with audible tones and my mobile vibrated, but no voice announce from MSVC was heard. When I switched the handset to normal vibrate and ring mode (assume this works on ring w/o vibrate as well) MSVC announced the caller through the headset and nothing audible was heard through the handset. I would say this headset is 100% compatible with the Tilt and MSVC.

Bought the Z9
My Z9 arrived today, and it does answer the phone, engage in voice command, etc.
Pretty nifty (but expensive) bluetooth.
Thanks!

Glad you like it. I hope you give us a nice reveiw after you play with it for a while. I am contemplating moving up because I have had this same type of headset for years now HS810, HS820, HS850, and the H700.

I've got AT&T Tilt, Stock ROM, MS Voice Command 1.6.17913 and Samsung WEP200 all working together.
Also, in MS Voice Command, there are options to select the source the phone calls are made from.
Go to "Start" > "Settings" > "Voice Command"
Click. "Notifications" button and the options that come up are...
-Announce notifications using Bluetooth hands free only
-Announce notifications using Bluetooth hands free if available
-Announce notifications through device speaker or wired headset only.

v 1.6 nad jabra
i still cant get it all to work on my tilt like my 8125...8126 was the bomb with vc. tilt is so nice but not with vc

I tried out a plantronics 665 the seemed to work well, but I didn't care that much for the headset. Returned it and got a nxZen nx9000, and it doesn't seem to work with voice command. Not sure why one works and not the other. Anyone care to speculate, or state with authority, why the 2nd headset doesn't work? Thanks.

Anybody knows how Logitech Mobile Pro Headset works with this combo?
Thanks
http://www.logitech.com/index.cfm/webcam_communications/mobile_phone_headsets/devices/536&cl=roeu,en

Is the Jawbone working with all this? I broke my last Jawbone, but would definatele get another, assuming it would work.

My Jawbone works with my Tilt with the stock ROM. Make sure you install VC before you pair your phone with the headset. If you already paired, delete the pairing and re-pair after the install.

Thank you much.
Now I've got another issue, somebody said "BLUEant" and I saw went looking... I like Blue
Trying to decide between the Z9 or another Jawbone. Comparitively they're about the same with the Z9 being the smaller and more "attractive" of the two, and it also costs alot less. Not to mention it's firmware can be update.
But the big plus for me is that it's BT 2.0 BT 2.0 + Firmware upgradeability make it a serious contender in my book. The Jawbone is in it's prime... whereas the Z9 could get better.
Can't decide at the moment...

I also have the Tilt and Jawbone working together but does anyone know if it is possible to issue the voice commands via the headset. I can only talk into the phone to make it dial a name and then the call is directed to the bluetooth headset.
has anyone got this to work all through the headset.

I couldn't imagine it not being possible... I managed to use the Jawbone with the RAZR V3 in or to use voice dialing and it worked decently.

Jawbone and voice dial
Have had a Jawbone paired with my tilt since I bought it. Works perfectly except calls are not announced through the bluetooth, but important e-mail subjects are read through the headset when they arrive.
The Jawbone is sometimes awkward because it gets loose on your ear/cheek if you move your head alot and then sounds like your talking through a long tube.
Thinking about trying blueant, but haven't heard any glowing reports yet.

W_P_L said:
Have had a Jawbone paired with my tilt since I bought it. Works perfectly except calls are not announced through the bluetooth, but important e-mail subjects are read through the headset when they arrive.
The Jawbone is sometimes awkward because it gets loose on your ear/cheek if you move your head alot and then sounds like your talking through a long tube.
Thinking about trying blueant, but haven't heard any glowing reports yet.
Click to expand...
Click to collapse
There are plenty of fantastic reviews for the BlueAnt Z9. It seems to me to be just the same as when I was researching the Jawbone. You'll either love it, or you'll hate it.
The big plus to me with the BlueAnt is that it's warranty is fantastic (2 years compared to the Jawbone's very specific 1 year warranty), it's BlueTooth 2.0 Stereo (should result in better sound quality as I plan to use my Kaiser as my MP3 player as well), and the big plus for me is that its firmware can be updated. Thanks to the firmware, the Z9's limitations are moreso a limit of it's firmware than it's hardware, whereas the Jawbone is fixed.
With that said, I loved my Jawbone... and I'll still be using my current one while it's still functioning (it's falling apart... Jawbones aren't very well built I'll say that) and comparing it to my Z9 when it gets here.

URPREY said:
My Tilt worked great with the stock ROM, MSVC 1.6.17913 and my BlueAnt Z9 worked flawlessly including announcing calls over BT.
Click to expand...
Click to collapse
Hi URPREY - I have the same setup (with the official ATT ROM update 1.62.502.0) working, but instead of announcing the callerid info, I'm hearing "please answer or not at home" through my Blueant Z9 via my Tilt. Any ideas?

VC 1.6 and Bluetooth, revisited...

Hi Again,
RE: the old Voice Command issue with the Touch....When I am using my bluetooth, I hit the call button on the earpiece and get the tone. I say, for ex., "call home", and get the usual voice response, "Call Home?", to which I respond yes. Then i just get the end tone. It doesn't dial the number. Works fine without ther bluetooth. My understanding was VC didn't work at all with BT, but now that I'm this close, I'm wondering if there is a fix...Also, not to beat a dead horse, but anything new on voice notifications, especially Email and appointments. I really miss that from my old BlackJack with VC 1.5....
Thanks all,
Gary

Bluetooth and Voice Command 1.6 work perfectly on my Touch Cruise. (Although, it might be causing an issue with A2DP...I have to investigate to make sure though.). Eitherway, the point of my post was to let you know that VC 1.6 does over bluetooth, with not only commands, but also voice notifications coming over properly. So maybe the problem is your Radio ROM? Have you tried any others? Do the Radio ROMs from the MSM7200 models work for you guys with the MSM7500? If so, the most upto date Touch Cruise Radio ROM could do the trick for you.

Similar problem here.
With my stock touch, VC1.6 works better then with previous devices, but still not 100%.
I can initiate calls by pressing the button on my headset and, unlike devices of the past, notifications can be heard via the headset.
Where I have a problem, is in VC recognizing my response to confirmations. Anotherwords, if I have confirmations turned on for voice dialing, and say "dial Michele at home", VC will come back and confirm "dial Michele at home?". But when I acknowledge and say "yes", it does not recognize this, and times out.
If I turn confirmations off completely, everything works fine.

You can actually hear the confirmations lol? When I tried it I could barely hear the confirmations.

Dew.man,
How do you turn off confirmations? I can see the check boxes for voice enabling, and calendar reminders, but nothing about disabling the confirmations. (I have ver. 1.60.4622, is there a newer one?) Also, (for mindfrost) regarding the volume thru the bluetooth, there is a fix for that which works great. I'm at work and I'd have to look for it, but it is probably on this site . And the ever popular "audiopara" fix works GREAT for all other volume issues. Just drop the folder in the phone's windows directory. It is available on this site as well.
Gary

garpt said:
Dew.man,
How do you turn off confirmations? I can see the check boxes for voice enabling, and calendar reminders, but nothing about disabling the confirmations. (I have ver. 1.60.4622, is there a newer one?) Also, (for mindfrost) regarding the volume thru the bluetooth, there is a fix for that which works great. I'm at work and I'd have to look for it, but it is probably on this site . And the ever popular "audiopara" fix works GREAT for all other volume issues. Just drop the folder in the phone's windows directory. It is available on this site as well.
Gary
Click to expand...
Click to collapse
I would love to know the fix for the BT issue, please post.

After months of tweaking (including Jetware, that doesn't even have direct support for Touch), I did finally get MS VC working well on my Touch, even with voice confirmation and all. But it would take out my A2DP stereo capability time and time again. I implemented every other tweak and tip out there. Besides A2DP being unusable, it would also take out being to listen to Sprint TV over a BT headphone, which was a real bummer.
About 3 months ago I finally gave up VC. I had to ask what were my must haves, and they were rock solid A2DP to play my Rhapsody to-go tracks on the memory card with my two BT stereo headphones, and listening to SprintTV over the BT mono or stereo. Voice command was third on the list, and I'd just had to survive with the mickey-mouse voice dialing that came with the Touch... I uninstalled the MS VC for good.
Now everything is rock solid, and I much regret the literally hundreds of hours of my life I wasted on VC, not to mention my $40 bucks.

For those of us who don't use stereo bluetooth.. ie, myself I'd love to know what the fix was for getting the confirmation volume corrected. It'd make voice dialing in noisy places (such as while driving, in airports, etc) a whole lot easier. If anyone in this thread recalls, what was the solution to that?

Modus 3500 AD2P Bluetooth and Voice Search in 2.2

Ive noticed something very strange with this headset. When I use the button on my Samsung Modus 3500 to either launch voice dial, redial or to hang up a call, Google Voice Search wont use any microphones on the phone and wont work. If disconnect from bluetooth and reconect it works again.
I tried to use a mono blueant headset and eveything functions the way it should, never a glitch. Im thinking it might have something to do with either the AD2P profile or the voice dialer taking over, honistly I dont know, I just want to know if anyone else has noticed anything like this.
And yes, i understand that Voice Search dosent work thew the headset, but the mic on the phone should ALWAYS activate when Voice Search is used.
Im using Macnut 13 right now, but I have tried this on evey Froyo ive installed including JK2 and JK6. Same results on TWO diffrent vibrants. Right now the workaround is to use the Bow Tie app fromt the market, but I would rather get the stock mic working right and consitant.
To test you headset:
1. Connect you headset to the phone
2. Hold down the button on the headset to redial, or just press it to bring up the dialer
3. Use the button to hang up
4. Try to use Google Voice Search by talking into the handset.
Post results here with your headset model and if it is AD2P capable. This may be a problem unique my model. If its not, then its something that the devs should look at. Chances are its a simple fix somewhere.
Read more: http://eb-productions.proboards.com...lay&board=vibrantacc&thread=129#ixzz17gWk3YRF