Related
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.
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?
Dear all,
I have a Parrot CK3100 carkit and I am running Bepe's 0.61 WWE and Radio 1.58.25.14.
BT pairing and sync is (more os less) seamless but I found that when I initiate the call with the phone's green button the call goes through the phone's loudspeaker. When I initiate the call with either by clicking on the contact's picture or action button on the name or voice dialing by Parrot everything works fine.
I know that I can turn the Parrot carkit's loudspeaker on by clicking menu->"turn headset on" but it is so dangerous to chek it and activate it while driving.
Is this the expected behaviour? Is this a Radio stack related problem? Anything I could do about making the external speakers work all the time the headset profile is activated? Anyway, it used to work as I expected with the original ROM.
Thanks, Z
zoltansz said:
Is this the expected behaviour?
Click to expand...
Click to collapse
Yes, instead of pushing green button on phone use the call button on Parrot and everything works fine.
Sascha
You mean I've got to search for the contact on the phone or on the Parrot? Because I prefer the phone's T9 dialer. Would it work if I chose the contact on the phone and pressed the green button on Parrot? Will play with that tomorrow.
And once we're talking about Parrots...
I have 1015 contacts to sync. BT sync is okay (I use "Windows CE" when pairing), but quite a few of my numbers do not go to the carkit. (I don't have to tell there are my mom, sister, kids etc. All my customers are on the carkit.) Can I do anything about that? I can send them one by one, but OBEX is not working according to my experiences. It says it was okay, but I cannot find the contact afterwards.
Any idea is highly appreciated. Thanks
Get MS Voice Command, and never browse your phone book again. Trust me its a well worthwhile investment, I can't think of a single person that bought it and regretted it.
Look at this, perhaps it can help.
http://www.jetwaremobile.com/
robjo
zoltansz said:
Would it work if I chose the contact on the phone and pressed the green button on Parrot?
Click to expand...
Click to collapse
Yes, that is precisely what I meant.
sonus said:
Get MS Voice Command, and never browse your phone book again.
Click to expand...
Click to collapse
Doesn't work for me since my car apparently is too noisy (at least while running).
Sascha
As far as the noise is concerned, the trick is that you have to record the names while driving so that noise would be on the records as well. Fortunately, I have a Civic and that makes perfect background noise for this operation
Anyway, I have VC enabled but I am using only to narrate my upcoming appointments while headset profile is on and the calendar is free. Do not use that for dialing or navigating the shell.
zoltansz said:
the trick is that you have to record the names while driving so that noise would be on the records as well
Click to expand...
Click to collapse
Since when do you have to record names in order to use MS voice command?
It's a speech recognition software which is user independant.
Sascha
Hi, as I said, I do not use VC for dialing. I use Parrot for that and I am basically very satisfied with that. The only problem is that, for some peculiar reason, not all my contacts gets sync-ed there.
no matter how I try to make it work, I cannot get voice dialing to work over my bluetooth headset. Anyone having this problem?
guyjack said:
no matter how I try to make it work, I cannot get voice dialing to work over my bluetooth headset. Anyone having this problem?
Click to expand...
Click to collapse
I think EVERYONE
the moment comes with nuance, is there any way to rip that out and add it to the hero?
For some reason, I find it easier to use the Voice Search app instead of the Voice Dialing app. If I say, "Call Dennis at Home" it works every time. BTW, I'm using a Jawbone Icon Rogue earpiece, which now supports A2DP. I do have to initiate the Voice Search by tapping the icon on the phone, though.
Bluetooth voice dialing
I would love to see one of the devs tackle this one. I have had true tap your BT device and voice dial since I started carrying a smartphone, UNTIL I switched to Android a few months ago.
Please devs, someone tackle this one. Even my old MotoQ with Winmo did it perfectly. I know you guys can do it better. Look how good Google Voice is with the keyboard and search now.
I have tried to get Nuance Voice from the Moment to work on the hero, and the phones are just too different and Nuance is to integrated to the moment. It works great though. Thats the ONLY good thing about that damn phone.
finally fixing blue tooth
Saw a recent post on phandroid that this will be fixed in android 2.2 (froyo)
And I quote:
" •Voice dialing over Bluetooth
•Ability to share contacts with other phones
•Support for Bluetooth enabled car and desk docks
•Improved compatibility matrix with car kits and headsets "
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