Related
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.
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
When I answer my a phone call with my actual phone, the audio comes from the watch. Is there a way to use my gear2 to notify me about incoming phone calls but use my phone to answer them. Samsung Gear 2 paired with HTC One M8.
EDIT: I know how to change the source during phone call but it uses gear2 as a default device, is there a way to change that?
Some question I wish to know as I'm planning to buy Gear S3 Frontier in the future.
For example, I'm using Huawei Mate 9.
1. I'm confused in people saying making call and receiving SMS don't work, and some say work, exactly which one is true? Is it that you can accept call but can't start call from the watch?
2. Any one that uses What's App, Wechat, Hangout, specially Facebook Messenger etc, are you able to do reply to these apps(like in notification area)? Like not only the quick message, to be able to type manually on watch and reply (Voice or Keyboard)?
3.In relation to question 2, how well it work with remote connection?
Thanks.
I have a Pixel and a Pixel XL. I can initiate and answer calls fine on my non-LTE S3. I can start and respond to messages as well. I haven't tried the other apps you mentioned.
I'm on a htc 10, lineage OS and I'm unable to initiate calls or send SMS with s voice
I have HTC ONE M8, answer to both of your questions is yes it's working fine, connected via Bluetooth, phone calls sms replying as well as initiate call or sms. WhatsApp and other can receive and reply but cannot initiate new message.
(Didn't tested when connected to same WiFi network.)
wasim9283 said:
I have HTC ONE M8, answer to both of your questions is yes it's working fine, connected via Bluetooth, phone calls sms replying as well as initiate call or sms. WhatsApp and other can receive and reply but cannot initiate new message.
(Didn't tested when connected to same WiFi network.)
Click to expand...
Click to collapse
Are you on stock rom? When I used a custom sense rom the gear manager keeps crashing however with lineage os it works but I can't initiate calls
wasim9283 said:
I have HTC ONE M8, answer to both of your questions is yes it's working fine, connected via Bluetooth, phone calls sms replying as well as initiate call or sms. WhatsApp and other can receive and reply but cannot initiate new message.
(Didn't tested when connected to same WiFi network.)
Click to expand...
Click to collapse
Ah that's good to know. As for what's app or facebook messenger. Reply is all I need. Hardly initiate message on watch.
Thanks guys. Good to know it's working well with other phone.
Two more things I wish to know.
1. If I accepted a call with watch, can I redirect it to phone directly on watch or I have to manually go to phone and choose to not use Bluetooth in that caller screen?
2. If I have a Bluetooth headset connected to my phone for example. I answer call using watch but can the call go through headset instead? What if i accepted the call using the Bluetooth headset button instead of watch. Will the audio re route properly?
Thanks
raypro112 said:
Are you on stock rom? When I used a custom sense rom the gear manager keeps crashing however with lineage os it works but I can't initiate calls
Click to expand...
Click to collapse
Yes I'm on stock rom (switched back to stock due to same issues)
I am using Xperia Z5 initiate calls works fine from watch by finding contact and tapping phone icon on watch, using s-voice its very hit and miss. Can initiate texts from watch by going to contact and tapping the envelope button, initiating texts with s-voice requires samsung phone ('send text message to xxxx' gives 'sms service is unavailable) can reply to texts, etc but only while notification is present, after notification cleared have to start from scratch. Its all pretty poor overall tbh.
Sent from my SGP621 using Tapatalk
bibiner said:
Two more things I wish to know.
1. If I accepted a call with watch, can I redirect it to phone directly on watch or I have to manually go to phone and choose to not use Bluetooth in that caller screen?
2. If I have a Bluetooth headset connected to my phone for example. I answer call using watch but can the call go through headset instead? What if i accepted the call using the Bluetooth headset button instead of watch. Will the audio re route properly?
Thanks
Click to expand...
Click to collapse
Can't help enough as not tested in detail.
In Bluetooth settings headset gives both options for phone audio and music
But watch gives only phone audio (so music sound can't come from watch, only music control possible)
And
If I select phone and music both for Bluetooth headset, then watch disconnect by itself as it wants phone audio.
veletron said:
I am using Xperia Z5 initiate calls works fine from watch by finding contact and tapping phone icon on watch, using s-voice its very hit and miss. Can initiate texts from watch by going to contact and tapping the envelope button, initiating texts with s-voice requires samsung phone ('send text message to xxxx' gives 'sms service is unavailable) can reply to texts, etc but only while notification is present, after notification cleared have to start from scratch. Its all pretty poor overall tbh.
Sent from my SGP621 using Tapatalk
Click to expand...
Click to collapse
The way notifications reply work seems similar to my pebble. Except I can't type manually on pebble. Thanks for info
bibiner said:
The way notifications reply work seems similar to my pebble. Except I can't type manually on pebble. Thanks for info
Click to expand...
Click to collapse
You can use on screen KB, handwriting recognition (us english only), smileys, canned response or s-voice to reply.
Sent from my SGP621 using Tapatalk
veletron said:
You can use on screen KB, handwriting recognition (us english only), smileys, canned response or s-voice to reply.
Sent from my SGP621 using Tapatalk
Click to expand...
Click to collapse
Btw. When you set the reminder, are you able to set for example. Today February 1. And I wish to remind myself to buy something on February 3. Can I do that? I hear it's strictly within the day only.
How many languages to the watch support tho? Does it support Japanese by any chance?
Does it have auto brightness?
I can say now that I went back to full stock rom, everything is working fine now. I can make and answer calls. I wished someone had told me earlier. I been calling Samsung support for days and they havent been anymore useful then the manual, telling me I needed the lte model to answer calls
On my mate 9, I can Not make a call through the watch neither reply to message text... Things I was able to do with my S6.
Probably due to emui and his special dialer.
But I can read SMS and email anyway
booster33 said:
On my mate 9, I can Not make a call through the watch neither reply to message text... Things I was able to do with my S6.
Probably due to emui and his special dialer.
But I can read SMS and email anyway
Click to expand...
Click to collapse
Oh Dang. The inability to make a call due to mate 9 might be deal breaker. Are you able to view incoming caller name/number and accept call? Had you try third party dailer to see if it work? Since you have mate 9 and gear s3. Are the reply options from notification work? Like manually type or hand writing reply incoming What's app, hangout and Facebook messenger. And also, do the music player remote control work with stock music player? Do it display the current track playing properly?
Thanks
Just to be clear, there are two versions of the Frontier, one has an LTE radio. The LTE model is able to handle calls, texts, and run apps like Spotify without being connected to a phone. The BT model must be tethered to a phone in order to do these functions. Both models need to be connected (via BT or cellular) to a phone in order for notifications (ie. Hangouts, email) to pass through.
Gear S3 with Mate 9
bibiner said:
Oh Dang. The inability to make a call due to mate 9 might be deal breaker. Are you able to view incoming caller name/number and accept call? Had you try third party dailer to see if it work? Since you have mate 9 and gear s3. Are the reply options from notification work? Like manually type or hand writing reply incoming What's app, hangout and Facebook messenger. And also, do the music player remote control work with stock music player? Do it display the current track playing properly?
Thanks
Click to expand...
Click to collapse
I know this question was from weeks ago but as I also have a S3 with a Mate 9, maybe I can help a little bit:
Everything works, including getting all notifications and asnwering them from the watch, and making and receiving calls in the watch. I have the S3 BT only model. My Mate 9 is with stock rom. Samsung Gear Manager working perfectly.
I have just one issue: sometimes, when I make a call using the phone, the call is automatically routed to the watch, without my permission, and it seems there is not any configuration or parameter to force all calls to not be routed to the watch. Of course it is easy to bring the call back to the phone (using the BT button in the dial), but as I initiated the call from the phone, it should not be redirected to the watch at the beginning. And this is something that happens eventually, not allways. It seems to be some kind of bug. I read about the same issue in other threads (S3 with other non-Samsung phones) here in XDA but could not find a definitive solution yet. If somebody can help on this, I would appreciate.
quangtran1 said:
I have a Pixel and a Pixel XL. I can initiate and answer calls fine on my non-LTE S3. I can start and respond to messages as well. I haven't tried the other apps you mentioned.
Click to expand...
Click to collapse
I'm using a Pixel XL as well and I'm planning to buy one. What limitations do you encounter when pair to the Pixel? Samsung Pay is also one of my reasons to buy this. Is it fully functional?
UPDATE:
Samsung Pay fully functional. But there are limitations if you use Gear S3 with non Samsung phone and BT headset (mine is Level U Pro ANC).
1. Call profile could only be activated either on the watch or level u pro, but not both simultaneously. If you choose to keep call profile on BT headset, you can use the headset for calling, but you cannot initiate call or answer call from watch. If you choose to keep call profile on watch, you cannot use BT headset for calling. That's also the case with car BT.
2. You can receive and reply to SMS on watch. But initiating SMS is a different story. No built in SMS so on watch so you can use watchface with messages shortcut to initiate sms, BUT all sms you initiate thru the watch WILL NOT REFLECT on the sms thread on the phone itself (Android Messages).
3. You cannot see your SMS history as well.
Normal phone calls can be answered no problem but when someone tries to call via Facebook Messenger or WhatsApp, the S3 drops the call before it can be answered. It's quite frustrating as I use these messenging apps to make calls lots more than the actual phone app.
Also, I can't make outgoing calls on Messenger while the S3 is connected via Bluetooth. I'm guessing it tries to use it as a bluetooth headset and something goes wrong.
Is anyone else experiencing something similar?
I am uasing my gear s3 with my oneplus 3
I have the same issue and can't find a solution...
I'm not good with Tasker or other automation apps, but is there a way to set a rule to disable bluetooth when there is an incoming or outgoing call? that would be a good temporary solution.