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.
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.
MSVC works great through BT headset on my tilt2 (Energy ROM 21885 december 31 sense 2.5), with the exception of using it to dial. I figured out why: When I would activate MSVC and tell it to say "call home" the command is recognized, and I am askd for a confirmation. So far so good... The troube is that when i answer "yes" , MSVC brings up the MS dialer NOT the HTC dialer, so it tries to dial but never connects to the radio to dial and just goes back to the sense 2.5 home screen. Testing MSVC with other commands, such as open <program> confirms this, since they do work. This occurs whether i initiate MSVC through the headset or through the talk button on the phone
Anyone have any clue how to get MSVC to bring up the HTC dialer when using it through bluetooth headset? MSVC works fine when i am not in handsfree mode.
jgamlieli said:
MSVC works great through BT headset on my tilt2 (Energy ROM 21885 december 31 sense 2.5), with the exception of using it to dial. I figured out why: When I would activate MSVC and tell it to say "call home" the command is recognized, and I am askd for a confirmation. So far so good... The troube is that when i answer "yes" , MSVC brings up the MS dialer NOT the HTC dialer, so it tries to dial but never connects to the radio to dial and just goes back to the sense 2.5 home screen. Testing MSVC with other commands, such as open <program> confirms this, since they do work. This occurs whether i initiate MSVC through the headset or through the talk button on the phone
Anyone have any clue how to get MSVC to bring up the HTC dialer when using it through bluetooth headset? MSVC works fine when i am not in handsfree mode.
Click to expand...
Click to collapse
it seems that the solution has to do with timing. if I wait a acouple of seconds before answering the confirmation of dialing the contact, the software has enough time to open up the contact database and then when i answer in the affirmative to redirect to the dialer. So the key is to wait a couple of seconds before answering yes or not the confirmation prompt
Also, try using, "correct", instead of, "yes". My Verizon Ozone seems to recognize it much easier, especially in a high noise environment. Maybe 'cause it's a longer word?
sixbennetts said:
Also, try using, "correct", instead of, "yes". My Verizon Ozone seems to recognize it much easier, especially in a high noise environment. Maybe 'cause it's a longer word?
Click to expand...
Click to collapse
hi there. it is not an issue of the software not recognizing that i said es, or even correct, it is an aiiuse of that the software needs time to be able to pass the call to the HTC dialer, so if i just wait a couple of seconds and then say correct, it works. no lag issue with the sofwate when not using blue tooth though , so maybe there is a setting to solve that
Or is it just me?
While on a call, a incoming call renders all audio on both calls dead. Regardless if you answer, ignore or let go to VM, neither person can no longer hear any audio.
I have tried this in many different scenarios. I am using T-Mobile in the NYC area.
If anyone else is experiencing this, please respond.
UPDATE!!!!!
The "Viber" app I installed was the cause of the problem. Once I uninstalled it immediately fixed the problem.
me too.
Hi, I have the exact same problem. It is quite frustrating.
The only work around I have found so far is to go in to call settings -->additional settings and turn off call waiting. Which is also kind of annoying.
Does anyone have a more elegant solution? (like having the incoming call sound a beep instead of taking over my entire call and rendering the phone useless!)
zyoeva said:
Hi, I have the exact same problem. It is quite frustrating.
The only work around I have found so far is to go in to call settings -->additional settings and turn off call waiting. Which is also kind of annoying.
Does anyone have a more elegant solution? (like having the incoming call sound a beep instead of taking over my entire call and rendering the phone useless!)
Click to expand...
Click to collapse
hi
and Asslam o Alykum
here is same problem
i have samsung galaxy i9000 if calling via viber incoming voice is well
But out going voice is no this just for me or this is a problem in the settings,
kindly help me expert
Curious is anyone else can replicate this issue I am having. When I receive a phone call, the person on the other end of the line hears a really bad echo . It seems to only happen on incoming calls. If I hang up and call the person back, the echo goes away. I'm on Project Fi. I have weak cell signal so I stay connected to WiFi at home mostly. I'm not using hangouts or anything, just the regular dialer.
To produce the problem:
Receive incoming call over WiFi
Ask the person on the other end if they hear an echo?
If so, hang up call the person back (over same WiFi connection). Does echo go away?
Seems software related since calling the person back makes the echo go away. Thinking about factory reset unless others can verify it happens to them. I am on the most recent November security patch.
In case anyone cares, I contacted Fi support and they believe it is very likely to be a bug. I submitted a couple bug reports after making and receiving calls. Engineers are supposed to contact me back within 48 hours.
The same has happened to me when I call my friend with Discord. I haven't tried calling the person myself, that might fix the problem. I'm using unlocked with Verizon.
@bballjohn32 The same exact problem on first gen pixel (project fi).
Only when someone is calling me over wifi do they hear an echo. Also to note, when either making or receiving a call over wifi the phone says call via "unknown ssid". prior to Oreo 8.1 it used to name my wifi network name. I spent two hours with support and ended by performing a hard reset, that did not fix it either. They are issuing me a refurbished phone which I'm not too happy about...
Hey everyone,
For anyone experiencing this issue, I found a temporary fix until Google releases a patch.
First of all, you need a rooted phone for this to work. I'm NOT going to cover the details here on how to obtain root, but a quick Google search will certainly help you out on this one. If your phone is still under warranty, then this procedure is maybe not for you.
1 - Have a rooted phone that experiences the sound issue where an inbound caller hears himself in an echo.
2 - Install a free app called DeFluence from Google Play.
3 - Open DeFluence and grant Superuser rights to the app.
4 - Tap "Disable Fluency". If it was successful, you will see the message "DeFluence was granted Superuser rights".
5 - Reboot the phone and enjoy inbound calls without the echo issue.
The only drawback I can see from this is that the other person might hear some background noise of wherever you are located, but I think it's still a great temporary solution.
So all in all, this most probably means this is a software issue that slipped into Android Oreo, and hopefully Google will be able to find a solution soon.
What I believe is happening is that the mic used for noise cancellation is picking up the voice of the caller and echoing it back into the call, when it should really just act as a noise cancelling microphone and not a regular mic.
If you have any questions, feel free to ask.