Your SIG lists the 3.35 (Titan) radio and the Altell ROM.
AFAIK, the Altell ROM did not include MS Voice Command. Which version of Voice Command are you working with?
Also, are you able to get confirmation to work, but the volume is low (almost inaudible)? If that is the case and confirmation works and announcement works, but the volume is simply too low to reliably hear what is being confirmed or announced, I am afraid that there really isn't much of a solution available. All of the AudioPara.csv fixes I have seen were for the actual volume and quality of the conversation. I have never seen where an update or change to AudioPara.csv has had a discernable impact on the volume or quality of the confirmation or announcement.
If you have experienced otherwise, please share, as I too would like to learn how to 'fix' this issue.
My hope is that the next release for the Touch/Vogue by HTC/Sprint (Rev.A + GPS) will include MS Voice Command. When this happens, the BlueTooth drivers and/or Voice Command will often receive some massaging in order to get things working properly.
Best regards,
-boggsie
Quote:
Originally Posted by mswlogo
Since I'm near Nirvana now (Everything works great).
I thought I'd ask if there is a true BT Confirmation Volume Fix.
I know all about AudioPara.csv I posted the first one for the Mogul some time ago.
On the Stock Touch it was already a little louder than stock Mogul and I tried quite a while on BT Volume on both Mogul and Touch with no luck. So I just run stock AudioPara.csv. Worried about blowing speakers.
I know there was one posted and I think there was claim to slight improvement on BT Volume (not sure if it was BT Volume [Radio] or BT Confirmation [PDA OS]. Well it needs way more than slight improvement for confirmation.
If it is in AudioPara.Csv does anyone know what the Parameters in (Line and Column in Excel) I don't want to change anything else because I'm happy with it and don't see it worth risking blowing a speaker.
Problem also is I've seen about 5 formats for this file as well. The fix might not be in the AudioPara.csv
So anyone know the full scoop?
Thanks
|