Database Info

WM6.1 + MSVC = Announcing Caller Names???

Does anyone know if the Kaiser is working with MSVC? I really am mainly looking for the caller's name feature...
Anyone?

inneyeseakay said:
Does anyone know if the Kaiser is working with MSVC? I really am mainly looking for the caller's name feature...
Anyone?
Click to expand...
Click to collapse
I have not experimented with this as of yet....but I will as soon as my phone is done flashing.

inneyeseakay said:
Does anyone know if the Kaiser is working with MSVC? I really am mainly looking for the caller's name feature...
Anyone?
Click to expand...
Click to collapse
It works....it requires replacing some files, you'll find it on a search

did you get the names read out when people call ok? Any tips?
This is a feature of the nokia phones which i'd like on my wm device

There's a cab listed somewhere around here for the MSVC1.6 install that doesn't require any file changing. It just works. Of course you do need to soft reset after the install to get to the VC settings so you can turn on call announce. You'll probably also want to change your button mappings. The cab remaps the PIE button by default.

jarek91 said:
There's a cab listed somewhere around here for the MSVC1.6 install that doesn't require any file changing. It just works. Of course you do need to soft reset after the install to get to the VC settings so you can turn on call announce. You'll probably also want to change your button mappings. The cab remaps the PIE button by default.
Click to expand...
Click to collapse
I didn't have to use a cab with Dutty's 6.1 just changed the Settings in Voice Command to Announce Calls and SR and poof it worked. No swapping of files or reg hacks needed. I did have to do it with all the 6.0 roms however.

It's working for me as well, and nothing extra was done. stereo BT headset from jabra.... sweet!

MC VC v1.6.17913 woks flawlessly....google is your best friend...

It's working for me EXCEPT that it doesn't announce incoming calls. I have the Jawbone BT earpiece that's excellent as far as reception and vocal quality. The BT earpiece rings as normal, but there's no voice letting me know there's a call coming in. I have the AT&T Tilt.
Any ideas what could be wrong? I have the VC settings set to "Announce thought the Bluetooth only" so that I make sure it's correct.
I wonder if it's an AT&T thing? Hopefully not since I can announce the outgoing call name and it works fine.
I'm confused...

maiahsdad said:
It's working for me EXCEPT that it doesn't announce incoming calls. I have the Jawbone BT earpiece that's excellent as far as reception and vocal quality. The BT earpiece rings as normal, but there's no voice letting me know there's a call coming in. I have the AT&T Tilt.
Any ideas what could be wrong? I have the VC settings set to "Announce thought the Bluetooth only" so that I make sure it's correct.
I wonder if it's an AT&T thing? Hopefully not since I can announce the outgoing call name and it works fine.
I'm confused...
Click to expand...
Click to collapse
You need the latest version (at least one of the later builds). The older ones don't announce properly.

speakerphone!
maiahsdad said:
It's working for me EXCEPT that it doesn't announce incoming calls. I have the Jawbone BT earpiece that's excellent as far as reception and vocal quality. The BT earpiece rings as normal, but there's no voice letting me know there's a call coming in. I have the AT&T Tilt.
Any ideas what could be wrong? I have the VC settings set to "Announce thought the Bluetooth only" so that I make sure it's correct.
I wonder if it's an AT&T thing? Hopefully not since I can announce the outgoing call name and it works fine.
I'm confused...
Click to expand...
Click to collapse
I thinkj he means announcement through speakerphone not bluetooth!!

maiahsdad said:
It's working for me EXCEPT that it doesn't announce incoming calls. I have the Jawbone BT earpiece that's excellent as far as reception and vocal quality. The BT earpiece rings as normal, but there's no voice letting me know there's a call coming in. I have the AT&T Tilt.
Any ideas what could be wrong? I have the VC settings set to "Announce thought the Bluetooth only" so that I make sure it's correct.
I wonder if it's an AT&T thing? Hopefully not since I can announce the outgoing call name and it works fine.
I'm confused...
Click to expand...
Click to collapse
Go into MSVC and select PHONE > OPTIONS > Announce Incoming Calls. This is where most people have problems. They don't realize you can highlight the item beside the check box and, in some cases, the OPTIONS box will be selectable. This also works for the Calendar to announce reminders.

thanks. I did some soft resers and it started to respond with announcing calls.... depending....
If I don't have the phone on "ring", the calls won't be announced. I can hear the BT earpiece become activated, but no call is announced. BUT, if I turn the ringer ON, then I can hear the announcement through the BT. I have set it to announce via BT only. When I am in meetings, I really don't want my phone to ring, but would still like to hear the call announced. When I downloaded this from Microsoft, I was told that it would still "whisper" the call. Well it's whispering too darn low! Like none at all!
Any ideas?

Quiet sound...
maiahsdad said:
thanks. I did some soft resers and it started to respond with announcing calls.... depending....
If I don't have the phone on "ring", the calls won't be announced. I can hear the BT earpiece become activated, but no call is announced. BUT, if I turn the ringer ON, then I can hear the announcement through the BT. I have set it to announce via BT only. When I am in meetings, I really don't want my phone to ring, but would still like to hear the call announced. When I downloaded this from Microsoft, I was told that it would still "whisper" the call. Well it's whispering too darn low! Like none at all!
Any ideas?
Click to expand...
Click to collapse
Have an sound file that is quiet. Switch to the quiet sound file for the ringer while in meetings. The announcement will come over your headset just fine. The only problem is when you have a contact with their own ring tone set.
Works for me. MSVC is just great for me. Voice commander is too flakey and depends on your pitch.
good luck!

tomsenna said:
Have an sound file that is quiet. Switch to the quiet sound file for the ringer while in meetings. The announcement will come over your headset just fine. The only problem is when you have a contact with their own ring tone set.
Works for me. MSVC is just great for me. Voice commander is too flakey and depends on your pitch.
good luck!
Click to expand...
Click to collapse
Thanks. I actually have MSVC 6.1 . where can I find out how to make a silent sound file? Or, is there onw somewhere that I can download it now?
Thanks for any and all help.

If you've chosen to have calls announced over BT only, then it will only ring thru you BT headset and NOT the device speaker. It is true that setting your ringer to vibrate doesn't work, but you shouldn't have to do this if your BT headset is turned on since there shouldn't be any sound coming from the device speaker.

Delta_flyer said:
If you've chosen to have calls announced over BT only, then it will only ring thru you BT headset and NOT the device speaker. It is true that setting your ringer to vibrate doesn't work, but you shouldn't have to do this if your BT headset is turned on since there shouldn't be any sound coming from the device speaker.
Click to expand...
Click to collapse
Thanks, I will try that setting. But the reason I turned it off was because it rang out loud. I'll turn the settings back on and try that with someone calling me OUT of a meeting. Next, should it announce the incoming text messages as well? I notice that this doesn't happen.

jjh430275 said:
MC VC v1.6.17913 woks flawlessly....google is your best friend...
Click to expand...
Click to collapse
Hi all,
I ame looking for that stuff too.
I have the thuffir V6b rom and MSVC 1.60.4622
It was working fine on IPAQ 6915 WM5; but with the Kayser WM6.0 rom I don't have the call annoncement working (through speaker as well as bt).
I tried some file replacement, but MSVC refuse to start after all; I need to reinstall it!
The big thing is that I use a frech MSVC!!!!
Anybody has a clue to make it work?!
Or, if it is supposed to work with a WM6.1, which 6.1 french rom can I install?

VC 1.6 using a headset
Voice command's announcements are dependent on the announcements volume, not the ringer volume (the two options when you click on the sound icon on the top bar). Therefore, if you don't want it to ring but do want the announcement, set the ringer to "vibrate" in the phone options but leave the announcements volume on - instead of selecting "Vibrate" on the sound icon.
This works great for me in the office environment. I also use the Notification Option: Announce notifications using Bluetooth hands free if available" to provide the ringtone when I am driving or otherwise have the ringer set to "Ring" in the phone options, and I get both the custom ringtone (if set) and the caller's name announced.
Dean
ATT 8900 No Camera

Delta_flyer said:
Go into MSVC and select PHONE > OPTIONS > Announce Incoming Calls. This is where most people have problems. They don't realize you can highlight the item beside the check box and, in some cases, the OPTIONS box will be selectable. This also works for the Calendar to announce reminders.
Click to expand...
Click to collapse
Thank You Very Much

[PROB] Bluetooth issue on the fuze- can't hear incoming caller

I asked this in the Raphael Software area, but I'm posting it here as it really isn't a software that someone made..
OK, I'm pretty sure BT worked on the phone. Now, any time I answer from a BT device, the incoming caller is muted. He can hear me, I can't hear him.
If I transfer the caller to the phone (which btw I can hear him on the phone) and back again to the BT device, I can then hear him. If I answer the incoming call from the phone buttons, I can hear the caller on my BT device.
I must've spent like 30 calls to my phone (I'm ticked as I'm sure each one counted on my minutes) thinking of different ways to fix this.
I thought it was my BT headset, but it works on my Tilt. So I tried it in my car BT. It can't hear the caller either. So something is wrong.
Here's how I COULD fix it:
If I turn off MS Voice Command "announce incoming calls" my phone itself will play my ringtone while I hear a beep tone in my BT earpiece. If I answer it form my headset, it works!
UPDATE:
I had my unit bloat free by following the "How to skip the bloat! (Fuze)" thread. I did another HARDREST and did the same bloatfree. Right off the bat, I synced my BT and I can't hear the incoming caller. Something is messed up.
One other person has this issue so far. Can anybody else check it? Voice Command is one of the best things there is for this phone. Just make sure its checked to announce incoming calls. Don't worry if you don't hear the incoming call being announced(you might hear a bell sound behind your normal ringtone) as thats a different issue you'll get untill you patch it. Just answer the call from the headset and see if you can hear the incoming caller.

Same Deal
I'm having the same problem. I just unchecked the 'announce incoming calls' and we'll see how that works. I'm on a work conference call so I can't try it till later.

it should work with it unchecked, but that defeats one of the best features on the voice command. Another thing, if you have ring&vibrate set, it you uncheck that feature, the phone will ring and vibrate. so other people around you will know your phone is ringing. In a library, I liked to use the announce feature because my ear piece would ring but the phone would only vibrate.

Here is what worked for me today -and I have been on the verge of sending the phone back to ATT...
1. I deleted all my pairings
2. I paired my JawBone2 first
3. Then, I paired my Plantronics A2DP thing (I had paired this one first before because I had it with me when the phone arrived in the office).
Funny thing: First time I paired my Plantronics 855 I got 2 options under "Advanced" at the end of the pairing procedure: 1. "Stereo Headset" 2. "Handsfree" I checked both. When I re-paired (after pairing with the JB2) I only got the "Stereo" option (which I checked). So now, all works fine. I can hear folks at the other end on either headset (actually, I have added a V1 as well) regardless of whether I or they initiated the call.
We'll see what the future brings here. But, for today, this is working.

I tried hard resets. Still no go.grrr... I dunno about you, but it just drains me to redo all my contracts and settings on the phone after every hardreset.
Hopefully your BT will stay working. Someone else here reported that it worked then stoped working after a while.

I have the same issue called HTC support last week and they where able to replicate this issue. If more people call HTC they may fix this problem faster.

I called ATT about it. Not aware. Of course they tried it and worked. It seems to be random on when it quits working. I know mine worked for a while. I just don't know what caused it to quit. And now that it did quit working, I can't get it to transmit the incoming caller to my BT. He can hear me though.
If it wasn't an hour job to restore it back to the way it was, I would hard reset it again. Tired to that at the moment.

I'm having the same issues on my Fuze. I unchecked 'announce incoming caller' and now it works just like my previous phone. My question is, what does announce incoming call actually do? Is it supposed to say who is calling through the bluetooth headset?

I too have this issue in my car (I haven't tried it yet with regular headsets, but I imagine the result would be the same). I have made the tweaks to the registry to get the Fuze to announce incoming calls, but the announcement is so soft, I can hardly hear it. I also have the issue of not being able to hear the person calling me (outgoing calls are fine).
I just did some experimenting and was wondering if others can duplicate this.
With Announce incoming calls on, when a call comes in and you answer it with the button on the headset (or the answer button in the car), you can't hear the person on the other end even though they can hear you.
Now try having an incoming call answered by hitting the Answer button on the phone itself (I only tried it with the on-screen Answer button, I didn't try it with the phone's hard button). You can now hear the person on the other end and they hear you. I was able to duplicate this numerous times.

Same issues...
With Announce Caller on in Voice Command, I cannot hear the caller if answering via the bluetooth headset. I'm not even sure it's is announcing the caller, but the custom ringtone is playing. If during the call you switch off the handsfree (via phone menu), then turn it back on, you can once again hear the caller.
If I turn off the Announce Caller function in Voice Command, I only get beeps in the headset, but I can hear the caller.
AT&T Fuze

Yes. I'll say the callers name if its in your contacts, or it'll say the phone number if it isn't. real helpful if you don't want to take out your phone.
DaRealGMan said:
I'm having the same issues on my Fuze. I unchecked 'announce incoming caller' and now it works just like my previous phone. My question is, what does announce incoming call actually do? Is it supposed to say who is calling through the bluetooth headset?
Click to expand...
Click to collapse

Err isn't that was I said in the original post? I mean about how its answering from the BT device that causes the incoming caller to be muted.
jglev said:
I too have this issue in my car (I haven't tried it yet with regular headsets, but I imagine the result would be the same). I have made the tweaks to the registry to get the Fuze to announce incoming calls, but the announcement is so soft, I can hardly hear it. I also have the issue of not being able to hear the person calling me (outgoing calls are fine).
I just did some experimenting and was wondering if others can duplicate this.
With Announce incoming calls on, when a call comes in and you answer it with the button on the headset (or the answer button in the car), you can't hear the person on the other end even though they can hear you.
Now try having an incoming call answered by hitting the Answer button on the phone itself (I only tried it with the on-screen Answer button, I didn't try it with the phone's hard button). You can now hear the person on the other end and they hear you. I was able to duplicate this numerous times.
Click to expand...
Click to collapse

Yup. That's the issue. It's only if you have VC to announce the incoming caller on, and you answer the the incoming call from the BT device.
DerralVL said:
With Announce Caller on in Voice Command, I cannot hear the caller if answering via the bluetooth headset. I'm not even sure it's is announcing the caller, but the custom ringtone is playing. If during the call you switch off the handsfree (via phone menu), then turn it back on, you can once again hear the caller.
If I turn off the Announce Caller function in Voice Command, I only get beeps in the headset, but I can hear the caller.
AT&T Fuze
Click to expand...
Click to collapse

starstreak said:
Yes. I'll say the callers name if its in your contacts, or it'll say the phone number if it isn't. real helpful if you don't want to take out your phone.
Click to expand...
Click to collapse
that's what I thought. But even when the announce option is checked, I don't hear anything except ringing on my bluetooth headset.

That's a different issue. But fixable. Do a search for microsoft voice command call announcement.

starstreak said:
I dunno about you, but it just drains me to redo all my contracts and settings on the phone after every hardreset.
Click to expand...
Click to collapse
Are you serious? Have you tried to back up your PIM info with the Sprite Backup that AT&T includes free on the phone? Or even sync it with your desktop?

Err yes. But when it didn't fix the BT issue, I had to hard reset. And resyncing to the computer takes a while, so is trying to redo all the edits you previously made before the issue happened that forced a hard reset.
motionmind said:
Are you serious? Have you tried to back up your PIM info with the Sprite Backup that AT&T includes free on the phone? Or even sync it with your desktop?
Click to expand...
Click to collapse

I just got off with HTC support as well. The other poster that talked to the guy that confirmed it. That tech said he could get it work on the phone itself but not using BT. They have sent some thing to MS to try and get a hotfix for it. Once they get it they will post under the support for the Fuze.
Right now no fix for it.

Does anyone know if there has been a fix to this? On my fuze if I make a call with by BT headset I can't hear the caller when they answer.

are you guys answering the phone on your handset or on your phone? because if you answer a call with bluetooth paired on your phone directly the sound will come out of the phone's earpiece. if you answer the call on your bluetooth headset's answer/hang up button then the sound will come through the headset.

Fuze - Bluetooth - Answering Incoming Calls

Hey Guys,
I have an issue with my Fuze and am hoping there is a simple setting that may help me out.
I have an Xlink Bluetooth gateway in my home, and have a Jag XK with bluetooth. Previously I had an 8525 where the bluetooth worked well.
I got the Fuze and I thought all was well. But for the last week, when I get an incoming call the blue tooth rings (houseline on XLink or XK Radio), but when I connect the call I get dead silence.
I can make outgoing calls via bluetooth and both devices work fine.
On the Fuze, if when ringing i hit answer on the phone, rather than the car stereo occassionally it connects.
Since I have the same issues (silent connection) when connecting via Xlink or XK I figured it must be an issue with the phone.
Any thoughts or ideas ?
Thanks
Dave

The issue is with Voice Command not with phone. If you update Voice Command to 1.6.19209 it will fix your issue. The other option is to turn off Announce incoming Calls option.

Update Voice Command
The phone has version 1.6.19971 --- So that would be a downgrade not an upgrade....
Does that still make sense ?
Dave

You've tested that specific version and it works? NATF said he tried his version from his Tilt and it didn't work. Please confirm!

Nice work!
You guys are really on it! I started noticing this problem today after enabling 'announce incoming calls' yesterday... didn't even occur to me. So I disabled it as per your suggestion, and it's working fine. Thanks very much for that. If I wanted to roll back to that earlier version, where could I find it? I still have my Tilt which I upgraded to 6.1 (battery's probably dead)... could I get the .cab off of it? Do we know for certain the earlier version works? Thanks again.

We were on it for a long time. You'll see multiple posts about that.

Incoming Skype calls while locked

Whenever I get a Skype call, I can't get my phone out of my pocket without hitting one of the answer buttons. This is probably a Skype specific problem, but I'm wondering if anyone knows a trick to get it to use an unlock device like the incoming voice call screen.
Suggestions would be appreciated!

Change behavior of motorcycle helmet BT

Hey all,
Sorry if posted in wrong section. Wasn't sure where's best. Please move or del if necessary.
I recently bought a FreedConn Bluetooth system for my helmet and it has a button on it that when held makes your paired phone dial the last number in your dial list.
This is pretty useless to me and I'd love to instead have it launch Voice Search so can easily send texts and make calls.
I googled a bit and found no way to adjust this on the device itself and looked at Tasker but don't believe it can do what I need.
I'm looking for a way to await the signal from the Freedconn and adjust what action it triggers. Or await an attempt to dial the last number dialed and launch a diff action.
Any advice on this is appreciated. Thank you.

I found a mini workaround having my own number as the last dialed and creating conditions (if calling myself w/ specific BT connected, hang up and run voice search) it works but hoping for a cleaner way. Any ideas?