Voice Command Caller Anouncement over BT - Page 7

drurc8 · #61 (**permalink**) 09-23-2009, 04:43 PM

I use PHM RegEdit to change this:
HKCU/ControlPanel/Sounds/TTSAnnounce
change ab Category to Ring instead of Vocecommand1

**amw1972** · #62 (**permalink**) 09-23-2009, 05:09 PM

You all may want to try the cab listed in the post below...

http://forum.ppcgeeks.com/showthread...ghlight=BTAwm6

its the BTAwm6 cab

30Glock · #63 (**permalink**) 09-23-2009, 06:03 PM

caller ID through the BT is a hit or miss, However I get everything else through the BT w/o failure. If the call ID does not go through the BT I can Still hear it through the hand set, ie Call from 5551212 or call from jane doe. Mine works perfect, Using Jawbone 2, and yes VC is perfect through BT. you guys are missing something.

haus · #64 (**permalink**) 09-23-2009, 08:01 PM

Quote:

Originally Posted by amw1972

Settings>>Comm Manager>>Bluetooth>>(the gears tab) Advanced Settings>>Audio

then make sure you have checked "Play system sounds on remote hands-free device"

This has been discussed before (I believe earlier in this very thread). What you have done is to pipe all audio to your headset, which repeatedly opens and closes the audio gateway (or leaves it open if you play music, etc.) - this will wear your headset battery down very rapidly if you're not careful. Just FYI. That step is normally not required for caller ID over bluetooth with voice command.

Gotta love all the varying reports here with some people saying it's working and others saying they're on crack. How many years has bluetooth been around, and they still can't get it right. What a joke.

JZ* · #65 (**permalink**) 09-23-2009, 10:58 PM

Quote:

Originally Posted by haus

This has been discussed before (I believe earlier in this very thread). What you have done is to pipe all audio to your headset, which repeatedly opens and closes the audio gateway (or leaves it open if you play music, etc.) - this will wear your headset battery down very rapidly if you're not careful. Just FYI. That step is normally not required for caller ID over bluetooth with voice command.

Gotta love all the varying reports here with some people saying it's working and others saying they're on crack. How many years has bluetooth been around, and they still can't get it right. What a joke.

No kidding...it works so well with everything...except the phone ringer (for me anyway...and no, Im not on crack

) I really like some the new features..But I would give them all away for my ringers back...I have many customs and used to know who was calling without looking...now I don't...

BenC · #66 (**permalink**) 09-24-2009, 01:20 AM

Same with mine. Everything goes to the headset (Motorola H751) except the phone ringing - goes to both the headset and is audible through the speaker. So other than phone calls, one never hears from my TP2.

helix139 · #67 (**permalink**) 09-24-2009, 11:08 AM

Don't know why they switched to the Widcomm stack when the MS stack worked pretty much perfectly for anyone who doesn't have a Nissan with nav system.

BenC · #68 (**permalink**) 09-24-2009, 01:52 PM

I just checked the settings again and yes, the send to headset is enabled - everything goes to the headset and when a call comes in, the ring goes to the headset and the device speaker.

Quote:

Originally Posted by haus

This has been discussed before (I believe earlier in this very thread). What you have done is to pipe all audio to your headset, which repeatedly opens and closes the audio gateway (or leaves it open if you play music, etc.) - this will wear your headset battery down very rapidly if you're not careful. Just FYI. That step is normally not required for caller ID over bluetooth with voice command.

Gotta love all the varying reports here with some people saying it's working and others saying they're on crack. How many years has bluetooth been around, and they still can't get it right. What a joke.

yznhmr · #69 (**permalink**) 11-05-2009, 12:50 AM

IM not seeing the newest .cab msvc 1.6.21052 this is the one on the stock Sprint TP2.. does anyone have it?

raysilk · #70 (**permalink**) 11-06-2009, 11:26 AM

I have a HTC Titan and this is what worked for me I was not getting any announcement through my BT and I tried this and it seemed to work..

HKCU\ControlPanel\Sounds\TTSAnnounce\Script
change from as5p to v0p (that's v-zero-p) - for vibrate & ring, or p (ring only)

Then Went to
HKCU\Control Panel\Sound Categories\Voice Command1

And then I Set AttenuationCategory to 1
And Init Vol to 11 and that turned up the volume and I get all my announcement through my BT not a miss yet.

It is important to note that if your value under AttenuationCategory is not a DWORD meaning there is a blue D instead of a (ab) you need to delete it and make it a Dword Value.. I hope you understand that LOL..