Database Users

XDA EXEC WITH MICROSOFT VOICE COMMAND ------PLS HELP!!!!!!!

I have an XDA Exec and am using it with a Sony ericsson HBH 662 Bluetooth headset. They work absolutely great together and i can voice dial from my bt headset perfectly using the inbuilt Voice dialing.
However, i was attracted to Microsofts version of this, MS Voice Command, because it will verbally anounce the name (or number) of the caller. This, i thought would be simply perfect to use with the HBH 662, as it would save me from having to take the thing off my ear every time to see whos calling. (still much simpler than opening up the Exec!!)
I have installed the demo version of MS Voice Command and find that the caller id announcement only works on the device itself and NOT the BT headset. This defeats the object of me getting it, so i would really really like to know if anyone has a solution to this at all?
Please someone out there help me as if i could get this to work then im a very happy bunny!

Hi Goonerfish
you need to follow this thread:
http://forum.xda-developers.com/viewtopic.php?t=29837&highlight=
best,
mikey mike

Hi Mikey Mike,
Thanks for that. I had seen that thread but was unsure whether that would also allow the caller id announcements to be heard on the headset?
I know that with that thread you are able to voice command from the headset, but it is unclear as to whether the device sends the sound (incoming caller id) to the headset?
Have you tried this and can you confirm that it will work?
Also, i have noticed that the caller id alert is coming out pretty quiet? You had the same problem and do you know a way around that?
Many thanks
Goonerfish

hi goonerfish
no - the incoming caller id doesn't go to the headset - no idea how you do that - sorry.
the caller id alert conflicts with the ringtone so tends to be drowned out a bit - i find it really clear for appointments.
mikey mike

Bluetooth headset / answering calls

Hi,
So when you have a Bluetooth headset connected it's a fair expectation for calls (audio) to be routed through to it, right?
When making a call this happens as per expect.
However if you ANSWER a call via the handset itself (hard button or slider) then the call is kept local to the handset, it's only if you answer the call via your button on your Bluetooth headset that the call is routed to there.
Now you can once in the call select the "Handsfree On" from the menu to transfer it to the headset once you've realised your mistake, but surely this is a bit of a pain.. no?
I for one will most of the time physically pick up the handset and take a look who is calling before answering it (unless driving etc), so would like to just press the answer button and away I do.
Ideas anyone?
(Thanks!)

SimonW500 said:
Hi,
So when you have a Bluetooth headset connected it's a fair expectation for calls (audio) to be routed through to it, right?
When making a call this happens as per expect.
However if you ANSWER a call via the handset itself (hard button or slider) then the call is kept local to the handset, it's only if you answer the call via your button on your Bluetooth headset that the call is routed to there.
Now you can once in the call select the "Handsfree On" from the menu to transfer it to the headset once you've realised your mistake, but surely this is a bit of a pain.. no?
I for one will most of the time physically pick up the handset and take a look who is calling before answering it (unless driving etc), so would like to just press the answer button and away I do.
Ideas anyone?
(Thanks!)
Click to expand...
Click to collapse
I have the same on my iPhone using my In-car bluetooth.
If I answer using the bluetooth answer button it goes thru the car speakers. If I use the handset answer button, it uses the iPhone itself, though I can then select to change it to the bluetooth from the iPhone.
I haven't received my Brodit cradle for my HD2 yet, so I've not set it up in the car yet, but I'm expecting the same arrangement I guess.

greatcapp said:
I have the same on my iPhone using my In-car bluetooth.
If I answer using the bluetooth answer button it goes thru the car speakers. If I use the handset answer button, it uses the iPhone itself, though I can then select to change it to the bluetooth from the iPhone.
I haven't received my Brodit cradle for my HD2 yet, so I've not set it up in the car yet, but I'm expecting the same arrangement I guess.
Click to expand...
Click to collapse
Hmm, I guess it's a case of personal preference - while you and I seem to agree I guess other may like the way it is. The answer is therefore a way to CONFIGURE this behaviour - anyone know if this is possible?

Same thing happens on my Topaz... didn't happen in my Omnia though.
I would like to know a way to alter it as well.

Has anyone tried the Car Kit Mode bluetooth option on the HD2 in the Sense UI 'Settings' tab then 'Other' at the bottom of the list, where you can tick or untick the box for autoconnect? I haven't but would like to know if it works for you.

SimonW500 said:
So when you have a Bluetooth headset connected it's a fair expectation for calls (audio) to be routed through to it, right?
(...)
However if you ANSWER a call via the handset itself (hard button or slider) then the call is kept local to the handset, it's only if you answer the call via your button on your Bluetooth headset that the call is routed to there.
(...)
this is a bit of a pain.. no?
Click to expand...
Click to collapse
Not really. A carkit is also a bluetooth headset. When I'm in the car and not driving, I can always choose to answer with the carkit - then everyone in the car can join in the conversation - or answer it on the device, which I prefer when my wife is driving and the kids are in the back. Even though I've made the mistake of using the slider when I really wanted the call on the carkit, I find having the choice a pretty good deal actually.
And besides, when using a headset, who's gonna take the phone out of their pocket to answer the call when all you need do is touch your headset - or better still set it to auto answer on headset calls. And if you really *need* to know who is calling first, why not install MSVC to have the phone tell you who is calling? Seriously, what's the point in using a headset if you're gonna take the phone out of your pocket anyway?

HD2 Tmobile USA will pay 100.00 for Voicecommand announce through bluetooth

I have tried to get Microsoft VoiceCommand to announce incoming calls through bluetooth but have had no success. I will be happy to pay anyone 100.00 who can come up with a solution. Will pay by paypal once confirmed working.

You can keep your money, but I can try to help. Did you already go into the Voice Command settings and select "announce notifications using bluetooth hands free only" or there is another option that says"announce notifications using bluetooth hands free if available"

BT headset sencitivity to Voice Command
I've found over the years that the reading incoming voicemail via Voice command can often depend on the BT headset you have. I went thru several different models until I found a family that seems to work very well. At the moment I have a TMOUS Hd2 and I'm using a Motorola 710 bt headset. It works just about every time.
Previously I had a HTC TYTN II with a Motorola 700 and then the 710 and these both worked with the purchased copy of Voice command 1.6 (don't recall the release but it was pretty current via upload)
Try going to a store that carries the 710 that offers a return policy, give it a try.

Tried these suggestions no luck
MirasHD2 I tried the settings for both announcing incoming calls and unchecked only during free time.
AndyClay I have a Motorola 710 headset no good. My problem is with incoming caller ID announce. I have tired a Jabra, Motorola 710 and Jawbone Prime all with no luck. Can get them to announce messages but no caller ID through bluetooth.
Thank you both for your suggestions.

You mean on BT "Call from 999-999-9999"? Yeah, if you find a answer let me know. Anything that initiates from the phone won't goto the headset. But anything I tell it from the headset will come back to the headset.
So incoming calls and appointment notifications won't work on my headset. But everything else seems to work.

I have the Blue Ant Q1 and it announces the incoming caller's phone number and handles voice commands very well. I just can't seem to get ringtones to play through the headset. NOTE: Blue Ant has a newer model coming called T1 that is supposed to announce calls by name. But I cannot confirm this.
The Q1 does it for me so far but I REALLY would like to have ringtones/ringerIDs to play through the headset.......

I have a motorola T505 in car speaker and it works great, plus I can also listen to slacker through my car sterio with this unit. New Egg sells them for about $60

It will announce appointments
Starstreak, I have got it to announce my appointments. This is what I did. Enable the settings in the VoiceCommand app to announce appointments and uncheck only during free time. Then go to settings, on the bottom of the device it will say menu, click on menu then all settings this opens several selection icons. select bluetooth go into settings which is the gears on the top left, choose advanced then audio, check box to play system sounds on remote handsfree device. I have my device set to announce appointments 15 minutes before the time. when this happens a tone alert starts, this opens the audio channel to my bluetooth headset, I hear a little of the tone then I hear the voice announcement telling me what the appointment is. Doing this will also send system sounds to the headset but I don't mind that too much.

It palys music
Jdwme, I can play music through the headset also. It is caller ID announce I can't get working. Does your Motorola announce the incoming callers name or number. None of the devices I have tried will announce caller ID at all only through the phone speaker no bluetooth.

guardm said:
I have the Blue Ant Q1 and it announces the incoming caller's phone number and handles voice commands very well. I just can't seem to get ringtones to play through the headset. NOTE: Blue Ant has a newer model coming called T1 that is supposed to announce calls by name.
Click to expand...
Click to collapse
If youre willing to try another headset

waiting for the new Blueant
I looked up the Blueant and I am waiting for the new model which will announce the name of the caller. I was hoping someone would know of or figure out a registry hack or mod to get this to work on a regular bluetooth headset. Thanks for the tip on the Blueant

polera257 said:
I looked up the Blueant and I am waiting for the new model which will announce the name of the caller. I was hoping someone would know of or figure out a registry hack or mod to get this to work on a regular bluetooth headset. Thanks for the tip on the Blueant
Click to expand...
Click to collapse
No problem Polera. According to Blue Ant, the T1 is due out in May 2010 and should be $79-$99. I will probably get one too.

I thought I tried that one... I'll try that again.
polera257 said:
Starstreak, I have got it to announce my appointments. This is what I did. Enable the settings in the VoiceCommand app to announce appointments and uncheck only during free time. Then go to settings, on the bottom of the device it will say menu, click on menu then all settings this opens several selection icons. select bluetooth go into settings which is the gears on the top left, choose advanced then audio, check box to play system sounds on remote handsfree device. I have my device set to announce appointments 15 minutes before the time. when this happens a tone alert starts, this opens the audio channel to my bluetooth headset, I hear a little of the tone then I hear the voice announcement telling me what the appointment is. Doing this will also send system sounds to the headset but I don't mind that too much.
Click to expand...
Click to collapse

It's not the HD2, It's a bug with MSVC when being used with WM versions past 6.1. I too have been looking for a fix for several days. I also had the Treo Pro where the Announce Incoming Caller worked with the same BT that I am using now.
I supposed now that MS is on to WM7, they could care less if they fix this or not.

That's why I posted here
MadLinx, That is why I posted the offer for someone here to maybe look into a registry hack or modification to get the caller Id over bluetooth working.. I have managed to get all the other voice functions operating.....still hoping someone here can help.

mine works just fine, i'm using a moto h710 and plantronics 975. go to bluetooth settings, advanced, audio, and make sure "play system sounds on remote hands-free device is checked. then go to voice command, make sure it's enabled. then highlight phone, hit options. check all the boxes, including announce incoming calls and select annouce notifications using bluetooth if available. if you guys need more help, just holler .

Ok checked the box to move all audio to headset. Well, now I seem to get mostly everything but stuff that the unit initiates(sp) itself. Like the incoming caller ID/name if it's my address book. But so far it works the best.
MS should just pay someone to FIX this program. Hell, if it worked like how it's supposed to, I'll pay$29.95 for an app like this.

mr8820 said:
mine works just fine, i'm using a moto h710 and plantronics 975. go to bluetooth settings, advanced, audio, and make sure "play system sounds on remote hands-free device is checked. then go to voice command, make sure it's enabled. then highlight phone, hit options. check all the boxes, including announce incoming calls and select annouce notifications using bluetooth if available. if you guys need more help, just holler .
Click to expand...
Click to collapse
thanks for the suggestion, but it didn't change anything on my end. the announce works, but it still announces through the phone loud speaker.

Yesterday, I upgraded from a Dash (non-3G) to the HD2. On my Dash, I had performed the registry hack to enable the voice command messaging/caller ID announcements over the handsfree bluetooth, and had no problems. Now using the same Plantronics Voyager Pro headset with the HD2, I am receiving calendar and messaging notifications, but I too am not getting the caller ID announcements on the headset. The incoming call information that should be heard on the headset is played through the handset speaker which should be muted. However, I have no problem placing calls using the headset with voice command. So, if a problem exists with the bluetooth stack, I am not sure why it would work sometimes and other times not. I too have verified all of the settings mentioned in this thread to remedy the situation with no success. I have factory reset the HD2 and reconfigured everything, again without success. I am not sure where to go next.

http://pocketnow.com/how-to/how-to-disable-htc-messaging-on-the-hd2
Can someone try this? He claims "One of the great things about HTC Sense on the HTC HD2 is that it's such a heavy redesign of Windows Mobile. Unfortunately, this can cause problems with some other applications. For me, HTC's text messaging application replacement disabled Microsoft Voice Command's ability to read my incoming text messages to me over a Bluetooth headset."
So I'm wondering if doing what he claims will allow the caller ID to be sent to BT? I would try this, but can't at the moment.

[Q] Are there any SIP programs for the Snap?

There are programs for windows mobile but I can't find any for windows smartphone 6.5 . I'm also looking for stock quotes software... one that can use stocks from non US markets.

I managed to get incoming VoIP/SIP working with a native app but it was a bit messed up. Basically I installed this package: http://forum.xda-developers.com/showthread.php?t=596682
and followed this guide: http://forum.xda-developers.com/showthread.php?t=299950
I can't get outgoing to work, but incoming works.

Wow you got it working? Which device do you have? I tried with the HTC Maple (called Mobilicity Snap here) and could never get the audio to come through the earpiece.
Anyway, the two programs I've tried that DO work are AGEphone and fring.

On the Mobilicity HTC Snap I got it working, yes. The question was not about using the earpiece, it was about using the native VoIP client. In fact, I did manage to get the VoIP calls through the earpiece but it has a very bad negative effect: the ringer also goes through the earpiece after a few seconds, thus making the ring on incoming calls very quiet. In my opinion, it is much better to use the headset for VoIP calls as it provides excellent quality, no echo and no problems with the ringer.
The problem with outgoing calls is in the way WinMo's VoIP places the calls. They work with Voxalot but not PBXes. I am assuming everybody can just use Voxalot as a middleman between the HTC Snap and the voip provider if there are any problems with outgoing calls.

That's funny, as I could never get it working with the headset. Outgoing calls worked, but only over the speakerphone, while incoming calls had no audio at all. The mic didn't even work; I could press the keypad and get a DTMF tone, but that was it.
Could you tell me exactly which steps you took to get the audio to come out of the earpiece? I kind of gave up and am using fring, but it would be interesting to see how you did it.

xenyz said:
That's funny, as I could never get it working with the headset. Outgoing calls worked, but only over the speakerphone, while incoming calls had no audio at all. The mic didn't even work; I could press the keypad and get a DTMF tone, but that was it.
Could you tell me exactly which steps you took to get the audio to come out of the earpiece? I kind of gave up and am using fring, but it would be interesting to see how you did it.
Click to expand...
Click to collapse
Sorry, apparently I was wrong, even with the earpiece hack (I tried both of them) the most you can achieve is to get the ringer to go through the earpiece but once the call connects it goes back to the speaker.
The only solution is to use the headset. I tried for outgoing only and I am able to dial, send DTMF and speak, so the mic works well.
With the native client on the HTC Snap VoIP works only with headset. Overall, I have been using WinMo for about a week and I can say that I hate it more than any other OS I have used. I wish we could get Android to boot but seems like the CPU on the Snap is messing up the effort.
Fring is also garbage on WinMo. It often fails to connect and when it does connect the call quality (over WiFi) is much worse compared to Fring on S60 or iOS. It eats the battery like a monster, something that doesn't happen on S60. There is no way to change/silence the ringtone with Fring on WinMo and if a call comes over the GSM line while you are on a call with Fring your Fring call goes through the speaker, very embarrassing.
I got my Snap for 100$ from Mobilicity and I think the hardware is worth it, but Microsoft should be paying me for being stuck with their useless OS.

Announce caller name from phone contacts in bluetooth headset

Has anyone been able to do this on our Lavender phones? If so, please provide instructions on how this is done and what headset you are using.
I work outside and my hands are usually full or dirty, so it would be great to hear the name of the person who is calling me through my Bluetooth headset. At the moment I only hear the phone number, even when the person calling me is in my phone contacts, so I have to take out my phone and look at the screen to see who is calling.
I've been Googling for ages and tried several apps but still can't get it to work over Bluetooth. Actually, I've never been able to do this on any Android device but I'm sure it's possible!
I'm currently on the latest Pixel Experience custom ROM and I've tried with several headsets, including Jabra, Sony and cheap Chinese Bluetooth 5.0 devices.
Any help would be greatly appreciated!

Anyone?

Solved!
OK.
So, in case anyone's also interested in this....
I eventually found a solution using Tasker and BlueTask plugin.
I can confirm this definitely works on Lavender Android 10 custom ROM and a cheap Chinese Bluetooth 5.0 headset.
My headset announces the phone number of the caller automatically and this can't be turned off, so I've set a delay in Tasker of a few seconds so the caller name is announced after the number.
The ROM I'm using (Pixel Experience) supports Bluetooth in-band ringing, so I'm not sure if that makes a difference, but in theory this solution should work on any decent ROM and Bluetooth headset or car kit. :good:

I have installed tasker and bluetask...please explain how to do this