Hi guys,
I noticed that some days I can only reject the call and not to accept it.
maybe since I updated my lg g3 a lollipop but not sure. is this normal? what can I do?
I've not toyed with using it to answer, I've only rejected but it would make sense to me that if you have a Bluetooth headset attached, then the answer should appear. If you don't, then only reject should appear. I don't know if that's how it works but seems most logical. I don't understand the necessity to have the ability to answer on the 360 when you're gonna have to pick up the phone anyway?
Chris_c81 said:
I've not toyed with using it to answer, I've only rejected but it would make sense to me that if you have a Bluetooth headset attached, then the answer should appear. If you don't, then only reject should appear. I don't know if that's how it works but seems most logical. I don't understand the necessity to have the ability to answer on the 360 when you're gonna have to pick up the phone anyway?
Click to expand...
Click to collapse
Imagine you are driving. Phone is connected to Bluetooth in your car. Phone is also connected to your moto on the wrist. You get a call and moto360 vibrates and then you would like to answer it. I don't want to fiddle around to pick up the phone. I should be able to swipe on moto to answer the call.
You used to be able to do this.
Since I've upgraded to Lollipop it has not worked. I'm not sure if it's Lollipop or the Android Wear upgrade that has disabled it.
(Moto 360 4.4W2 KNX01S, Nexus 5 Android 5.0 LRX210, AW 1.0.4.1580939)
Can't Answer Phone on 360 Since Lollipop Upgrade
ulakala said:
Hi guys,
I noticed that some days I can only reject the call and not to accept it.
maybe since I updated my lg g3 a lollipop but not sure. is this normal? what can I do?
Click to expand...
Click to collapse
Just wanted to let you know that I too have not been able to answer ANY calls since my Nexus 5 upgraded (OTA) to Lollipop. I have seen a scattering of similar messages but I guess not enough 360's with Lollipop yet to make a dent. I can decline calls but definitely no way to answer (The green "blob") is not shown
Fingers crossed for update soon!
metaldood said:
Imagine you are driving. Phone is connected to Bluetooth in your car. Phone is also connected to your moto on the wrist. You get a call and moto360 vibrates and then you would like to answer it. I don't want to fiddle around to pick up the phone. I should be able to swipe on moto to answer the call.
Click to expand...
Click to collapse
if your phone is connected to the bluetooth of your car, then your car speaker will ring and display the call with an option to answer or reject. usually there is a button on the steering wheel to do exactly that...don't even need to bother swiping the watch
maximus96 said:
if your phone is connected to the bluetooth of your car, then your car speaker will ring and display the call with an option to answer or reject. usually there is a button on the steering wheel to do exactly that...don't even need to bother swiping the watch
Click to expand...
Click to collapse
Then AW shouldn't even give an option to pickup for reject on the watch as you can answer and reject using the steering wheel buttons . AW should give answer/reject option or nothing altogether.
I've set it up in a way that any inbound call is accepted automatically after x seconds (being the time to reject it manually).
Issue is with lollipop... Never had the issue on my Note 2 with touchwiz roms... Had this issue on my phone with CM12 lollipop rom
Sent from my GT-N7100 using Tapatalk 2
Related
Hi. I want to know how to get the iphone 5 headset to work on my galaxy s3? I'm aware the volume control will never work but assumed everything else does. Some have said they have managed to get it working on their galaxy s3 either through specific software or ROM changes?
Right now I can make calls to other with the headset working perfectly, but when I receive calls from others I cannot hear them nor can they hear me. So the problem only occurs when I RECEIVE calls. The mic is really important to me.
Any help would be really appreciated.
OK. I've narrowed down the problem. The headset stops working when I press the middle button to receive calls. In other words, if I answer a call using the actual phone, the headset works fine. If I do press the middle button to receive a call, I can no longer hear the other person nor can they hear me through the headset.
Does anyone use the iphone 5 headset with the galaxy s3? Does the headset work for you?
AbZ__ said:
OK. I've narrowed down the problem. The headset stops working when I press the middle button to receive calls. In other words, if I answer a call using the actual phone, the headset works fine. If I do press the middle button to receive a call, I can no longer hear the other person nor can they hear me through the headset.
Does anyone use the iphone 5 headset with the galaxy s3? Does the headset work for you?
Click to expand...
Click to collapse
Same issue. It does not work for me either.
mexigga said:
Same issue. It does not work for me either.
Click to expand...
Click to collapse
The workaround I'm using now is to have auto-answering enabled while a headset is connected. Now i'm trying to find away to reject calls with a single click but after trying various apps I've not been able to do so.
AbZ__ said:
The workaround I'm using now is to have auto-answering enabled while a headset is connected. Now i'm trying to find away to reject calls with a single click but after trying various apps I've not been able to do so.
Click to expand...
Click to collapse
How to set the auto-answer when using the headset ?
thanks
What is the benefit of accepting a call with the Moto 360?
Lets say my phone is in my pocket book, and a call comes in.
My watch buzzes and lets me know a call is coming in. I accept the call, and then I try to get into my pocketbook, find, my phone and speak before the person on the other end hangs up???
fibroman said:
What is the benefit of accepting a call with the Moto 360?
Lets say my phone is in my pocket book, and a call comes in.
My watch buzzes and lets me know a call is coming in. I accept the call, and then I try to get into my pocketbook, find, my phone and speak before the person on the other end hangs up???
Click to expand...
Click to collapse
this happened to me, though im always using a bluetooth headset aswell so, everytime I answer the call using the moto360, it pops up in my ears the person who is calling, so pretty awesome. no need to check the phone who's calling
lyrad12 said:
this happened to me, though im always using a bluetooth headset aswell so, everytime I answer the call using the moto360, it pops up in my ears the person who is calling, so pretty awesome. no need to check the phone who's calling
Click to expand...
Click to collapse
O.K. but wouldn't it be great if the Moto 360 could have answered the call directly. It already has the Mic. It is just missing the speaker I think.
Maybe the next version (Moto 720) will have that!!! lol
fibroman said:
O.K. but wouldn't it be great if the Moto 360 could have answered the call directly. It already has the Mic. It is just missing the speaker I think.
Maybe the next version (Moto 720) will have that!!! lol
Click to expand...
Click to collapse
God I hope not..we will be back to the Nextel days.
I don't use it when my phone is in my pocket. I look at my wrist to see who it is though and to decline it if I choose. If I happen to have a corded earbuds with mic in, I'll use my watch to answer and I use it in my car as well. For me its a situational feature.
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.
I just switched from an LG G5 to an S7 Active... phone calls worked perfectly on my watch with the G5, but I can't seem to figure out how to turn on the feature on the S7... Anyone have any experience doing so?
When you first launch the dialer, it should ask for permissions. Once you give it permissions, it should be as simple as pushing the person you want to call. If you, for instance, pick up a phone call on your phone and want to switch to your watch, tape the bluetooth icon and it'll swap it over if that's what you have paired.
I don't use any other headsets, so i'm not sure how it might interfere if you do, but I do have an S7.
I'll be happy to answer any more questions if this doesn't help.
Phone call on watch? I'm confused guys. This ain't no gear s. How do you make phone calls on the watch?
I keep having phone calls where I can't hear the other person and vice versa. Seems to be related to my Bluetooth connection to a Gear S3 as disabling Bluetooth usually fixes it (but then sometimes it randomly sides itself with Bluetooth on and I haven't done detailed testing).
I'm on Fi, but have been for awhile and never had this problem with my previous phone... I am using the software sim.
Anyone else experiencing similar, or know anything about it?
rbrenart said:
I keep having phone calls where I can't hear the other person and vice versa. Seems to be related to my Bluetooth connection to a Gear S3 as disabling Bluetooth usually fixes it (but then sometimes it randomly sides itself with Bluetooth on and I haven't done detailed testing).
I'm on Fi, but have been for awhile and never had this problem with my previous phone... I am using the software sim.
Anyone else experiencing similar, or know anything about it?
Click to expand...
Click to collapse
Make sure under the phone app that the hearing aid accessibility option is off
S0UTHPAWK1LLA said:
Make sure under the phone app that the hearing aid accessibility option is off
Click to expand...
Click to collapse
It's off. I should add, there's not even the sound of the ring, just dead silence and the timer starts, then eventually a disconnect. That's making me think the audio is being sent somewhere besides the speaker (even though the icon says speaker).
rbrenart said:
It's off. I should add, there's not even the sound of the ring, just dead silence and the timer starts, then eventually a disconnect. That's making me think the audio is being sent somewhere besides the speaker (even though the icon says speaker).
Click to expand...
Click to collapse
I get that to from time to time. It's as if the audio is routed to my watch but nothing actually comes out of the watch.
Sent from my Pixel 2 XL using Tapatalk
rbrenart said:
It's off. I should add, there's not even the sound of the ring, just dead silence and the timer starts, then eventually a disconnect. That's making me think the audio is being sent somewhere besides the speaker (even though the icon says speaker).
Click to expand...
Click to collapse
If your not connected to anything (Bluetooth) and the volumes are maxed out and you have nothing, it's RMA time. Have you tried the good ol' factory reset? Last resort
S0UTHPAWK1LLA said:
If your not connected to anything (Bluetooth) and the volumes are maxed out and you have nothing, it's RMA time. Have you tried the good ol' factory reset? Last resort
Click to expand...
Click to collapse
Interesting thought, though it definitely feels like software to me so I'm not rma'ing just yet.
rbrenart said:
I keep having phone calls where I can't hear the other person and vice versa. Seems to be related to my Bluetooth connection to a Gear S3 as disabling Bluetooth usually fixes it (but then sometimes it randomly sides itself with Bluetooth on and I haven't done detailed testing).
I'm on Fi, but have been for awhile and never had this problem with my previous phone... I am using the software sim.
Anyone else experiencing similar, or know anything about it?
Click to expand...
Click to collapse
I legit have the EXACT same issues. I also have a Gear S3. It only happens the first time I call, and then, if I hang up and call the number right back, it's a normal phone call. Have you figured out a fix yet? It's really a nuisance. Thanks in advance!
packfan4 said:
I legit have the EXACT same issues. I also have a Gear S3. It only happens the first time I call, and then, if I hang up and call the number right back, it's a normal phone call. Have you figured out a fix yet? It's really a nuisance. Thanks in advance!
Click to expand...
Click to collapse
Seems better after the last two Tizen updates, but honestly I don't make enough phone calls to be certain.
Go to Bluetooth setting and choose ur watch setting and disable phone calls should fix it,i have huawe watch 2 and same problem.