I own the SW3 for a while now, and I was wondering, maybe I am missing the point, but why is het possible to deny or answer a call via the watch? You need your phone to talk with the person that is calling, so what is the added value? OK, when I left my watch in the other room I can deny the call, that is handy, but I don't get the answer function, but as I already mentioned, maybe I am missing something here.
Think of BT headset connected to your phone. Phone in jacket or coat.
A wired headset should work as well.
Related
Does anyone else have this problem...?
I've just got an HBH-662 for the Universal and it pairs fine and can make calls, but answering calls it doesn't work properly.
The headset recognises incoming calls and rings okay, but when you press the button to answer the call, it doesn't put the sound through the headset, only through the phone.
Maybe it's a setting I'm missing, but it's a tad annoying!
F.
I'm not sure I can help much, but I have no problems with my HBH-662 and my Jasjar.
Brett
I too have no problems with the HBH-662 and answering calls.
Will give it loads of testing later and see if i can get it to act the same as yours
I have been using HBH-662 with JJ for few weeks and in general I have no problem. I just wish that the Caller ID issue (the ability for the JJ to send contact name to the BT headset instead of number only) is resolved very soon.
I've not had any problem answering calls. The only problem I've experienced with this headset is an apparent clash with programs like GSPPocketMagic, MagicButton and HandyMenu. With either of the three apps running, my headset drops the connection after 20-30 seconds and I have to press the button on the headset to pick up the call again, which it drops 20-30 seconds later, etc. The moment I uninstall these apps it works fine again.
How strange. It seems to have sorted itself out!
I paired my old BT330 to compare it, it worked fine, so I removed the Akono and re-paired it and it seems to be working.
Thanks for the comments folks, it's useful even though you didn't get the same probs!
Now the next issue is how to reconcile the fact that SE say this thing provides "Caller ID", which I took to mean the NAME of the person, with the fact that it doesn't do anything of the sort... only the number.
And who really remembers the numbers of their friends these days?!
F.
fergusstrachan said:
Now the next issue is how to reconcile the fact that SE say this thing provides "Caller ID", which I took to mean the NAME of the person, with the fact that it doesn't do anything of the sort... only the number.
Click to expand...
Click to collapse
It does provide CallerID name... but only with certain phones WM phones being among those that don't provide name information. It's my understanding that the problem lies in the bluetooth stack on the phone and not with the headset. I did see a post a short while back that suggested the issue was being worked on and would be resolved in a ROM update, so I have hope... but I'm not holding my breath.
Brett
Hehehehehehehe.
Microsoft 'working on' the bluetooth stack...
hehehehehehehehe. Sorry. I just find that really funny. The idea that MS are actually working on anything to do with the BT stack on WM!
I don;t really understand why it takes so long to program a bit of BT to provide something like that (or, say A2DP!). I mean, how hard can it be?
Well I'm not a programmer so I won't moan.
F.
Splatt! said:
I've not had any problem answering calls. The only problem I've experienced with this headset is an apparent clash with programs like GSPPocketMagic, MagicButton and HandyMenu. With either of the three apps running, my headset drops the connection after 20-30 seconds and I have to press the button on the headset to pick up the call again, which it drops 20-30 seconds later, etc. The moment I uninstall these apps it works fine again.
Click to expand...
Click to collapse
Any more comments if Sony Erickson Akono BT headset HBH662 really clashes with magic button and handy menu?
I'm sorry if this has been asked in the past, but I was wondering what happens to your navigation screen when a phone call comes in or when you need to place a call? Now it would be nice not to be doing several things at one time, but if a call comes in while you are trying to navigate, doesn't the call menu come on screen? How do you suppress that? Just wondering as I am looking to get a TP2 via AT&T. Thanks.
Dunno about other kit, but my copy of TomTom6 produces a popup on my iPAQ hw6915, and all I hace to do is answer the call (I use a BT headset with it when driving to stay roadsade as much as possible). The voice directions from TomTom remain muted while the call is in progress, by the way.
hi
While using GPS (GARMIN XT), the phone screen appears in case of incoming call.
I always use my bluetooth earphones while using GPS.
GPS voice will be thru the speaker and call on bluetooth.
After the call, the screen turns back the the GPS view automatically.
On my TP2, if a call is coming in and I have the bluetooth headset turned on, the headset will pick up the call only if I answer by pressing the headset answer button. If I answer by sliding the on-screen bar over the green "answer" button, the speaker in the phone itself comes on instead.
Is there a way to change this behavior such that the sound always comes through the headset if it is connected to the device, even if I answer on the phone itself?
I would be interested in this too, as I have a bluetooth car kit, if I accept the call from the car screen it is ok, if I accept it on the phone it routes through the phone.
I'm having a similar issue, but a little more complex it sounds like... When the phone rings and using my bluetooth headset (Jawbone2), I have to:
Press the answer button on the Jawbone2
Ringtone sound now comes through the headset
Remove phone from pocket and Slide2Answer with S2U2
Call is now connected through bluetooth
With my Kaiser, all I had to do was press the bluetooth answer button and the call would automatically pick up. No removing the phone, no pressing buttons or sliding to answer!
If I Slide2Answer on the phone when ringing without "transferring the call to bluetooth" first, the handset picks up the call. Useful in many cases, especially if I can't find the bluetooth after putting it down or in my jacket pocket for the time being. If I use the phone to make a call from the handset with bluetooth connected, it always transfers the sound directly to bluetooth. The problem lies with answering the phone with a bluetooth headset - the 4 steps above need to be completed instead of just #1 like it should be!
if you don't want it to go to the phone you need to answer with the device you want to talk with. thats how bluetooth on phones work, tp and tp2
You stole Boo Boo's Name said:
if you don't want it to go to the phone you need to answer with the device you want to talk with. thats how bluetooth on phones work, tp and tp2
Click to expand...
Click to collapse
I get that, If I try to answer the phone on the headset though, just the sound of the ringtone comes through the headset - the phone is still not answered, and is still ringing, just now in my ear! I STILL have to actually answer it via the phone's controls, which is pretty hard to do if you have your hands full........
For the OP Boo boo is correct. Answer the call on the device you want to use.
For Garcia25 the problem is S2U2. I ended up removing it and going back to the built in lock + LockDevice + built-in slide-to-answer.
S
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?