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.
I received a call while I was working, I could not answer. I could not answer because I was busy working. I didnt want to answer because I did not know the number. Not being able to answer, the caller left a voicemail. Which turned out to be a blessing in disguise because Im still able to listen to it via voicemail. If I were to have answered I would have thought someone butt dialed me and thought nothing of it and hung up. But after listening to it, I realized that it was my voice and hers.
At first I thought maybe my girlfriends apartment was bugged for whatever reason. The people shes renting from are very reputable. So we went and checked everywhere. Nothing. However, I thought to myself how would they get MY phone number if it is not affiliated in any way to her apartment or where she lives.
So that leads me to think that something may be on my phone. I have since factory reset my phone. The crazy thing about this whole situation is that the conversation that was recorded was from TWO DAYS ago. Who has my number? How are they able to record me? Do I just wait to see if I receive another call? I wont be putting any sensitive information on the device for fear of it being compromised. If I do get another call, Ive already decided Im destroying this one and buying another phone.
I never opened any weird emails. Never downloaded any weird apps. Never opened any links in any received texts. Im on Android 10 on a One Plus 7.
Any input would be greatly appreciated.
here's a possibility - you and your girlfriend were talking and then you butt-dialed someone and it went to their voicemail. That person decided to call you and playback the voicemail. Look in your call log for an outgoing call that you don't recognise at the time of your conversation with your gf.
lightstream said:
here's a possibility - you and your girlfriend were talking and then you butt-dialed someone and it went to their voicemail. That person decided to call you and playback the voicemail. Look in your call log for an outgoing call that you don't recognise at the time of your conversation with your gf.
Click to expand...
Click to collapse
I hadnt thought of that, I checked the records, and there was no butt dial. I called the number that called me and it said it was no longer in service. Looking at the records on my cell providers site and there was no record of that number ever calling me. Which leads me to believe it was spoofed.