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.
Related
Sorry if you have already read this but I am still having a problem!!
I got the new Bluetake iphone mini stereo headphones for christmas and was hoping to use them with my MDA Pro (running the new O2 ROM).
I have them paired as a "Hands Free" device...
I know that I can't use the stereo features until the new A2DP patch come out (hopefully soon!), however what I want to be able to do is use voice command to initiate calls etc. However when I press the call/power or Play/Pause button all I hear is a beep from the headset and nothing hapens on the PDA...
However I can use the button to answer and hangup a call (as long as I answered it with the handset...) If I initiate the call on the MDA then I can't hangup with the headset...
Am I doing something wrong or does it sound like something is faulty??
Any advice?
Thanks
Andy.
I actually had an oportunity to try out the voice levels and sound is awful! I also tried to connect it to my SE T610 and it refused and it did the same when I tried to connect it to my Toshiba M200 tablet PC as in both cases it never asked for the passkey...
I am begining to think that they must be faulty??
But becuase I have never had a BT headset before so I'm not sure if I am doing something stupid!
Andy
I have managed to try a SE BT headset with my MDA Pro and it did work and activate voice command. So it would seem that the headset is faulty. Does anyone have any ideas before I send it back?
Andy
Please!! Is there anyone here who can comment on whether they think these are broken or if I am just incompetent!
If they are broken then I need to send them back really soon...
FWIW, my Jabra BT330 and the SE HBH-662 just need a single quick click to activate the voice dial, but these Plantronics Pulsar 590A things I just got (which are fandabidosi by the way!) need a prolonged press to do the same.
Have you tried keeping your finger on the button for a while?
Ferg.
andykemp said:
Sorry if you have already read this but I am still having a problem!!
I got the new Bluetake iphone mini stereo headphones for christmas and was hoping to use them with my MDA Pro (running the new O2 ROM).
I have them paired as a "Hands Free" device...
I know that I can't use the stereo features until the new A2DP patch come out (hopefully soon!), however what I want to be able to do is use voice command to initiate calls etc. However when I press the call/power or Play/Pause button all I hear is a beep from the headset and nothing hapens on the PDA...
However I can use the button to answer and hangup a call (as long as I answered it with the handset...) If I initiate the call on the MDA then I can't hangup with the headset...
Am I doing something wrong or does it sound like something is faulty??
Any advice?
Thanks
Andy.
Click to expand...
Click to collapse
Just looked at the instructions for the bluetake i-phone (bt450rx),
(got them myself for xmas)
and it does not say that you can connect to the phone for voice control,
however you should be able to hang up from the headset.
i have got the k-jam (wizard) and can dial from the k-jam and hangup from the headset.
voice control may not be available because the new bluetooth stereo headset's are ready for AVRCP (Audio Video Remote Control Profile).
the older bluetake headset bt420rx can be used for voice control but do not have AVRCP function.
I hope i am wrong, but it may be the answer you have not been looking for.
Hmm... That sounds bad...
I only have a few days left to return it and don't know whether to get a replacement or to go for a different headset?
i like the idea of being able to play/pause/f-foward/rewind via the headset(when bt v2 upgrade is available), because music playback is more important to me than voice dial.
of course if you can send it back, then perhaps just wait until bt v2 is available, and then buy a headset for the uses you require it for.(wish there was an emotion with cross eyes) LOL
I know what you mean but I would still be able to use voice command!!
Does anyone else have the 450Rx and a universal and could test it for me?
if you do prove me wrong (and i hope you do) please let me know.
answering this problem further,
the bluetake i-phono mini headset cannot be used for voice command,
however the motorola ht820 can be used for voice control.
Had similar issues with my headset (not the same type). In the end, I had enable secure mode on the universal, pair the devices, select serial port and then immediately initiate the voice dial, otherwise it didn't work.
Gareth
I decided to play it safe and returned it back to Expansys for a refund. When someone else gets a set of stereo headphones and A2DP is out... and crucially they can confirm it works! Then I'll buy a new one!
Cheers
Andy
one good thing with motorola ht820 is that they can be used with a detatchable cable, so whilst i'm using them bluetooth for the phone side, i can still hear good quality music.
also i know from trying them with my wife's qtek s110 that you can control windows media player as well.
you may have already tried this, but just in case you haven't,
install and run the three files for either "bt off", "bt on", or "bt toggle",
this will switch all audio to the bt headset or away,
of course quality is not good, but at least no cables.
ps. if the headset is switch off and you put bt on, you will get an on screen error message.
aliendad said:
one good thing with motorola ht820 is that they can be used with a detatchable cable, so whilst i'm using them bluetooth for the phone side, i can still hear good quality music.
also i know from trying them with my wife's qtek s110 that you can control windows media player as well.
Click to expand...
Click to collapse
Do they come with this cable as standard?
EDIT: Did a search, and they do.... might just buy them now and sell my Sony EX-71's.... would they we at least the same in terms of sound quality? It's the thing people talk about least with these devices!
So lemme see if I got this right.... even before I get A2DP installed on my Exec, I can listen to perfect music using the cable, and also use the hphones as a bluetooth headset as well? Will the music still pause etc when a call comes in?
Just bought a pair of HT820's on Ebay there.... £38, not too bad. Should get about £25-30 for two pairs of existing headphones, so well please.
anyone got this working on the tytn
I use it with a Jabra BT250...
it used to work with my plantronics 320 on the wizard but wont work on the tytn is there any special settings you had to do
I also tried to make it works and it doesn't I assume that is due to the different headset plug.
Waiting for a version for TYTN
the prog will open a connection to the earpiece i can hear the static just wont forward any of the audio to it. works with the phone of course for making calls
I have the same problem with my Tytn (BTaudio seems to work because it stops the radio - I use it with a parrot car kit) but the audio still goes through the phone speaker...
did you find a solution?
gb
BTAudio On does not work, you have to turn it on via button press on the headset. BT Off works fine of course...
Rather annoying, but that's the way it is...
Sorry but I am afraid not to understand... the bt car kit is working properly and is paired to the qtek
could you please be more specific?
thks!
Sorry, you stepped into a rather cryptic response... I assumed you were talking about the file BTAudioOn.exe that worked on the 8125 but not the 8525/TYTN.
Search this forum for mono audio - there's a big thread. Also check the wiki.
attached. This cabs works great. To activate it, start playin music, then push and hold the button on your BT headset for about 1 second, it should beep and then music comes through. Only problem is you can't use MS VC through your headset, but it doesn't break VC.
BTaudio cab works
I have used the Gotland cab file and still had problems, until I began to think like a technician... Once I installed the cab file, I performed a soft reset and then repaired my Jabra JX10... It has been working fine ever since... I can hear music (either streaming or static) and voice... I have not tried tackling the voice commander problem though...
I have just upgraded the firmware on my headset using the software that is not posted on Jabra's site, but through a link in another post, I was able to do it... had to reinstall the Gotland cab again though.... May tackle Voice Commander later in the day... Who knows...
I'm using Bluemusic 2.0 and it worked with music to BT headset. Also using installed the BT VC fix cab in this forum at it worked fine with VC 1.6 - except incoming anouncements. ( Installation Hint: after installed both - you must delete existing device and then re-pairing the BT again).
I just made a thread, here http://forum.xda-developers.com/showthread.php?t=306363
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.
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 :-/
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?