My At&t Samsung Galaxy S3 automatically picks up incoming calls and enables the speaker while it's sitting on my desk. I will have the phone on silent, and all of a sudden at 7:00 in morning, I hear a telemarketer saying "HELLO?, HELLO?"...I know this sounds strange, because I have only read about a handful of people with this issue, but it is a valid issue that needs to be resolved... Hopefully with your help.
I am not new to smartphones or Android, so I tried whatever you can imagine. I know that Android has a few auto-answer features available, so I made sure all of the settings that have to with automatically answering calls are disabled.
Anyone else experiencing similar issues, or willing to help with this issue, please post. Thanks guys!
(fyi..I have Hard Reset the device twice)
Settings - language and input - voice cmd for apps off.
ATT Samsung S3
Thank you. You are a genius lol
I missed that.
-----------------------------
SGH-i747
make sure and tap the thanks button for Tlo218.
tomtommy306 said:
make sure and tap the thanks button for Tlo218.
Click to expand...
Click to collapse
Yes! Do much i see someone reply thanks and not hit the button. It's so much simpler and says so much more. I normally don't say anything, but since you already have. +1 +1 +1
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm confused. What do voice commands for apps have to do with calls being automatically answered?
the1stSecond said:
I'm confused. What do voice commands for apps have to do with calls being automatically answered?
Click to expand...
Click to collapse
You can say "Answer" to pick up incoming calls.
-----------------------------
SGH-i747
hacknet07 said:
You can say "Answer" to pick up incoming calls.
-----------------------------
SGH-i747
Click to expand...
Click to collapse
Not only saying "answer" but most background noise will pick up an incoming call. It's pretty sensitive and there's lots of background noise that could actually "answer" the phone and cause it to pick up/connect. Nice feature, but it's too sensitive for my liking. Had to disable it even though I frequently used it for the camera app. (saying cheese, or shoot will take pictures)
Samsung s3
Yeah, that was my problem. I didn't say answer or anything like it, and it would just pick up the call. The shoot feature can still be enabled without enabling the answer option, I use it quite often. Thanks
-----------------------------
SGH-i747
Thank you!
Tlo218 said:
Settings - language and input - voice cmd for apps off.
ATT Samsung S3
Click to expand...
Click to collapse
Had the same problem! Hopefully, this works. It was periodic so I was concerned about going into store and not being able to replicate. Given this proposed solution, I'm amazed that other forums indicated ATT customer service is asking people to send back their phones for inspection?!!
SGH-i747
SGSIII is answering calls automatically.
SGSIII is answering calls automatically.
My phone does not have this setting: Originally Posted by Tlo218
Settings - language and input - voice cmd for apps off. ATT Samsung S3
What my settings are:
From the Phone Settings menu: Call Settings - Accessory Settings for Call:
Automatic Answering IS selected (“Only operates with a connected headset)
Problem is the phone is answering when NO headset (wired or bluetooth) is connected (bluetooth is off).
When I turn off the settings the phone does not answer automatically - However, when I'm driving I like using a wired headset and the autoanswer feature works great then. Just wne I unplug the headset the phone continues with auto answer.
Something that may be related - I have a PayPal credit card reader. It does not work with the phone. I called PayPal tech support to sleuth out the problem and they thought the read was faulty, sent me another, and I have the same result: phone does not recognize the device. My wifes phone is the same Samsung SIII and that headset jack does not work correctly with the reader.
However, the Square D reader does work.
I would fix permissions
I just ran into a guy who was having this same exact issue with his S3, and I went into these settings and toggled it ON, and that got it to stop. He had it off the whole time, but it was still doing it. I turned cmd on, and it stopped it. Very strange.
JCtheWizard said:
SGSIII is answering calls automatically.
My phone does not have this setting: Originally Posted by Tlo218
Settings - language and input - voice cmd for apps off. ATT Samsung S3
What my settings are:
From the Phone Settings menu: Call Settings - Accessory Settings for Call:
Automatic Answering IS selected (“Only operates with a connected headset)
Problem is the phone is answering when NO headset (wired or bluetooth) is connected (bluetooth is off).
When I turn off the settings the phone does not answer automatically - However, when I'm driving I like using a wired headset and the autoanswer feature works great then. Just wne I unplug the headset the phone continues with auto answer.
Something that may be related - I have a PayPal credit card reader. It does not work with the phone. I called PayPal tech support to sleuth out the problem and they thought the read was faulty, sent me another, and I have the same result: phone does not recognize the device. My wifes phone is the same Samsung SIII and that headset jack does not work correctly with the reader.
However, the Square D reader does work.
Click to expand...
Click to collapse
You got Voice cmd for apps when you press s-voice and settings from menu softkey.
Related
Had some issues with the touch tones not working correctly with the speakerphone enabled. Didn't find any threads here on XDA but found a few over on a couple other android forums.
Basically it seems that when using the touch tones with speakerphone enabled, the mic picks up the speaker phone and the receiving end hears each touch tone twice.
I had the issue when trying to call verizon wireless to enter my passcode, as well as trying to setup my voice mail. I have 3 separate Galaxy Nexus phones in my family, and the issue can be replicated on all 3 phones.
Also noticed lowering the volume on the speakerphone can alleviate the issue too, but it's just kind of annoying as I don't want to hold the phone up next to my ear when I'm trying to enter things on the dial pad.
I've also tried switching the DTMF setting between long and normal, the problem still exists
Hoping with a firmware update they can filter out the touch tone, or just not make the touch tones audible to ourselves. (I'm assuming
this is because the speaker is so close to the mic on the GN)
Anyway, I don't think there's a fix for it yet, but I'm just posting here to see if anyone else is experiencing the same issue, and to make people aware of it.
Also found the issue on google support here:
http://code.google.com/p/android/issues/detail?id=24467
Bump,
Anyone else run into the same issue? Or have some secret fix I don't know about? (Other than turning off the speaker lol)
Sent from my Galaxy Nexus using XDA App
This explains the problems I was having the other day trying to join a Go-To-Meeting - would not accept my pin.
I was on speaker phone too - ty for this !
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
_Gir_ said:
I've had this problem on the GN and other devices as well. Sometimes I'll hit mute because it helps but also I don't want people/computer listening in.
Click to expand...
Click to collapse
Just realized this before I came to post, thanks for pointing it out too! Mute FTW!!!
i too noticed this as well when i first got it and think that it ridiculous that it wasnt thought out better.
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
ConanOBrien said:
Another fix: Simply turn off audible touch tones in the settings menu.
Drawback is there's no feedback for the dialpad, anyone know of a way to get the vibrate on for the dialpad?
Click to expand...
Click to collapse
This is the workaround I've been using for about a month now with no issues. I had the same issue where the conference call service wasn't getting my pass code entered correctly.
Only issue now is the headset echo heard by connected parties, which has been reported and hope to be fixed soon. I've tried several workarounds here but none have been bulletproof.
Hi,
I have the Rogers version Galaxy S Glide (Android 235), non-rooted as not allowed in order to use it for work email.
Using Motorola S10-HD stereo bluetooth headset.
When paired and connected, pressing the BT Call button does nothing.
Holding the BT Call button performs a redial of the last number.
I've read for other devices with Android 2.2 or higher that the Google Voice Dialer should start when holding the Call button but it doesnt. It will only start if I hold the search button on the phone itself.
Any confirmation from others or suggestions to make it work?
Thanks.
Maruzko said:
Hi,
I have the Rogers version Galaxy S Glide (Android 235), non-rooted as not allowed in order to use it for work email.
Using Motorola S10-HD stereo bluetooth headset.
When paired and connected, pressing the BT Call button does nothing.
Holding the BT Call button performs a redial of the last number.
I've read for other devices with Android 2.2 or higher that the Google Voice Dialer should start when holding the Call button but it doesnt. It will only start if I hold the search button on the phone itself.
Any confirmation from others or suggestions to make it work?
Thanks.
Click to expand...
Click to collapse
I am using a Nokia BT headset but working fine, can you check on Settings > Wireless and network > bluetooth settings > [Moto S10-HD] > tap and hold, and see if it's connected with "Phone" and "Media"
gabby131 said:
I am using a Nokia BT headset but working fine, can you check on Settings > Wireless and network > bluetooth settings > [Moto S10-HD] > tap and hold, and see if it's connected with "Phone" and "Media"
Click to expand...
Click to collapse
Yes, both "Phone" and "Media" are listed in the BT settings and both are ticked.
Have tried repairing with no change.
Maruzko said:
Yes, both "Phone" and "Media" are listed in the BT settings and both are ticked.
Have tried repairing with no change.
Click to expand...
Click to collapse
okay good, now check if you have Voice Search and/or Google Voice app....if you have it, try updating it from Play Store......
gabby131 said:
okay good, now check if you have Voice Search and/or Google Voice app....if you have it, try updating it from Play Store......
Click to expand...
Click to collapse
Yes, already updated it from the Play store.
Voice Search v2.1.4
Sent from my SAMSUNG-SGH-I927R using XDA
Do you have access to another Bluetooth headset you could try with the phone? Maybe there's something wrong with your current headset.
Maruzko said:
Yes, already updated it from the Play store.
Voice Search v2.1.4
Sent from my SAMSUNG-SGH-I927R using XDA
Click to expand...
Click to collapse
clpo13 already mentioned....try to delete other bluetooth headset connections you have....
clpo13 said:
Do you have access to another Bluetooth headset you could try with the phone? Maybe there's something wrong with your current headset.
Click to expand...
Click to collapse
I just tried a Nokia BH-104 but it also doesn't start Voice Search/Dial.
It also acts slightly differently to the S10-HD.
Call button press - nothing
Call button long press - nothing
Call button double press - last number redial
Sent from my SAMSUNG-SGH-I927R using XDA
Maruzko said:
I just tried a Nokia BH-104 but it also doesn't start Voice Search/Dial.
It also acts slightly differently to the S10-HD.
Call button press - nothing
Call button long press - nothing
Call button double press - last number redial
Sent from my SAMSUNG-SGH-I927R using XDA
Click to expand...
Click to collapse
Oh now this is becoming a real challenge. I also have Nokia BH-104 and I will, in all my best, try and replicate your issue and see.
EDIT: Positive! The call button on both my Nokia Headsets does not trigger Voice Search.....I can only redial my recent called contact via double press.
gabby131 said:
Oh now this is becoming a real challenge. I also have Nokia BH-104 and I will, in all my best, try and replicate your issue and see.
EDIT: Positive! The call button on both my Nokia Headsets does not trigger Voice Search.....I can only redial my recent called contact via double press.
Click to expand...
Click to collapse
I gather we are stuck?
Is there an app that allows remapping the BT call key to start another app, even though this function should work standard to start Voice Search?
Sent from my SAMSUNG-SGH-I927R using XDA
Maruzko said:
I gather we are stuck?
Is there an app that allows remapping the BT call key to start another app, even though this function should work standard to start Voice Search?
Sent from my SAMSUNG-SGH-I927R using XDA
Click to expand...
Click to collapse
I believe voice dial/search does that, don't know what google did....
On google phones (Nexus One/S), I believe, the voice dial app pops out once call key on BT headset is pressed.....but I wanna search further....
gabby131 said:
I believe voice dial/search does that, don't know what google did....
On google phones (Nexus One/S), I believe, the voice dial app pops out once call key on BT headset is pressed.....but I wanna search further....
Click to expand...
Click to collapse
I have a Motorola T505 in the car and it works well just that it does not work if the phone is at the lock screen. Needs to be unlocked for the call button to work. I assume you already made sure the phone was not at the lock screen. Just wondering is their anyway to make it work with the lock screen still active?
gabby131 said:
I believe voice dial/search does that, don't know what google did....
On google phones (Nexus One/S), I believe, the voice dial app pops out once call key on BT headset is pressed.....but I wanna search further....
Click to expand...
Click to collapse
Did a bit more testing.
I installed Vlingo, then something changed.
Instead of nothing happening when pressing the BT call button (Motorola S10-HD), now I get a choice:
Vlingo
Vlingo In-Car
but still no Voice Search option
I then found this App in the Play Google Store called Bluetooth Launch.
It allows you to assign any function to launch when the BT headset call button is pressed.
Now I get:
Bluetooth Launch
Vlingo
Vlingo In-Car
I set Bluetooth Launch to start Voice Search and it works!.
Vlingo is not a bad option either since it can be set to start listening on launching.
However, I realized all this only happens when the phone is in wake mode.
If its asleep, nothing happens, so you still have to touch and wake up the phone then press the BT button.
So still not totally hands free.
Asleep or locked the phone does not respond which is quite annoying when driving. My old phone (Windows Mobile 6.1) alloud voice dialing even though it was locked. I loved being paired with my Bluetooth as I still could do everything via Bluetooth. Sucks that Android which is so powerful does not work well with BT.
dudejb said:
Asleep or locked the phone does not respond which is quite annoying when driving. My old phone (Windows Mobile 6.1) alloud voice dialing even though it was locked. I loved being paired with my Bluetooth as I still could do everything via Bluetooth. Sucks that Android which is so powerful does not work well with BT.
Click to expand...
Click to collapse
Did some more searching and it appears that the move from Froyo to Gingerbread changed the way BT call wake up works.
When the phone is secured with a pin or pattern to unlock, the BT call button wont wake it up..
I did have a pattern lock enabled, which I've since turned off.
Now pressing the BT call button while the phone is in standby wakes it up and runs Vlingo straight into listening mode waiting for a command.
So seems to work OK, just that I cant have a secured lock enabled.
Maruzko said:
Did some more searching and it appears that the move from Froyo to Gingerbread changed the way BT call wake up works.
When the phone is secured with a pin or pattern to unlock, the BT call button wont wake it up..
I did had a pattern lock enabled, which I've since turned off.
Now pressing the BT call button while the phone is in standby wakes it up and runs Vlingo straight into listening mode waiting for a command.
So seems to work OK, just that I cant have a secured lock enabled.
Click to expand...
Click to collapse
Ya I have seen that it works as you mentioned but I like having the lock pattern and was hoping there was a way to get Bluetooth call button to work even though the phone is locked. Kind of sucks if there is no way around this. The whole point to the Bluetooth is that the phone can stay in my pocket locked so as not to press any buttons by accident and I can make calls from my Bluetooth device.
Looking to see who else out there is using Groove IP and what settings you have found to work the best. I can't seem to pin down the right combo so I am going to try crowdsourcing.
http://snrblabs.com/snrb/grooveIp.aspx
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
Are you having issues w/ sound distortion over WiFi?
The default settings work fine on most devices, and the changes I've made are minor.
Using version 1.2.21:
-Allow 3G/4G calling
-Accept calls on answer
-turned off DTMF feedback under Audio/Echo settings
-turned on Keep Screen On and Sync Voice under Troubleshooting
What are your Speaker and Mic gain settings? I am only calling over WiFi
Phillip Fry said:
What are your Speaker and Mic gain settings? I am only calling over WiFi
Click to expand...
Click to collapse
Speaker vol: 10
Mic gain (bluetooth as well): 0
Echo Cancellation: On, with Auto Detect
I haven't noticed any issues on my end by tweaking these settings, but can also say things worked fairly well on default.
Phillip Fry said:
What are your Speaker and Mic gain settings? I am only calling over WiFi
Click to expand...
Click to collapse
What kind of issues are you running into? Defaults should be good for the Galaxy Nexus. One thing to watch out for is by default the Galaxy Nexus puts the wifi into a power saving state when the screen turns off. You can change that from the android settings->wifi settings->advanced wifi settings, or enable Keep Screen Alive in GrooVe IP.
I get noticeable lags using Groove IP on my Galaxy Nexus. The extent varies - it's sometimes less than half a second, but often close to two seconds. Happens both incoming and outgoing. I am using the default settings except for the volume. If this matters, the lag is there both on Wi-Fi and 3G.
Phone: Galaxy Nexus (GSM Unlocked)
Carrier: T-Mobile
Region: Seattle
Any advice would be appreciated.
daihard said:
I get noticeable lags using Groove IP on my Galaxy Nexus. The extent varies - it's sometimes less than half a second, but often close to two seconds. Happens both incoming and outgoing. I am using the default settings except for the volume. If this matters, the lag is there both on Wi-Fi and 3G.
Phone: Galaxy Nexus (GSM Unlocked)
Carrier: T-Mobile
Region: Seattle
Any advice would be appreciated.
Click to expand...
Click to collapse
Few things can cause lag. First would be latency on the data connection. Apps running on the device that use cpu or data...or battery manager or task killer apps could also cause problems with calls. We are also working on a new update that should improve the in-app delay for audio. On our Galaxy Nexus it seems to work pretty good so far. I think we'll have a beta for it ready sometime this weekend. We'll likely be posting it on our facebook page when it's ready. Oh, something on the device going into a power saving state would also cause delay. Keep Screen Alive can help with that.
snrb Labs said:
Few things can cause lag. First would be latency on the data connection. Apps running on the device that use cpu or data...or battery manager or task killer apps could also cause problems with calls. We are also working on a new update that should improve the in-app delay for audio. On our Galaxy Nexus it seems to work pretty good so far. I think we'll have a beta for it ready sometime this weekend. We'll likely be posting it on our facebook page when it's ready. Oh, something on the device going into a power saving state would also cause delay. Keep Screen Alive can help with that.
Click to expand...
Click to collapse
Thanks for the update! I will await the new beta version. I'll keep an eye out on your FB page.
Besides the Keep Screen Alive option, are there other options that may help reduce the lag? I see things like Synchronize Voice and Mic Buffer. For instance, will it reduce delay if I change the Mic Buffer size from medium (default) to small?
Thanks again!
daihard said:
Thanks for the update! I will await the new beta version. I'll keep an eye out on your FB page.
Besides the Keep Screen Alive option, are there other options that may help reduce the lag? I see things like Synchronize Voice and Mic Buffer. For instance, will it reduce delay if I change the Mic Buffer size from medium (default) to small?
Thanks again!
Click to expand...
Click to collapse
Synchronize Voice can help, I don't really use it on the Nexus. Changing the mic buffer to small should also help, that's one of the things we're changing. Small seems still too large. So we're going to be adjusting small to be smaller and make it the default.
snrb Labs said:
Synchronize Voice can help, I don't really use it on the Nexus. Changing the mic buffer to small should also help, that's one of the things we're changing. Small seems still too large. So we're going to be adjusting small to be smaller and make it the default.
Click to expand...
Click to collapse
Thanks! I will make adjustments to those settings to see how it goes.
I wonder if there is plan to support more than one google voice login in Grooveip soon? Something that we can switch from one to another quickly?
testrider said:
I wonder if there is plan to support more than one google voice login in Grooveip soon? Something that we can switch from one to another quickly?
Click to expand...
Click to collapse
Might not be soon but it is something we're working on. Right now you can switch users pretty quickly by going into the menu and pressing change user. But that's not the same as supporting multiple accounts. Battery life is also an issue with multiple sign ins, still working on it.
Hey is this beta or new version addressing the latency available yet? I have an Epic Touch 4G & have tried everything (spoken to support repeatedly over email - thanks!) & still get 1-2 second delay. Difficult to have a normal conversation as we keep cutting each other off as we think we're done speaking.
snrb Labs said:
Might not be soon but it is something we're working on. Right now you can switch users pretty quickly by going into the menu and pressing change user. But that's not the same as supporting multiple accounts. Battery life is also an issue with multiple sign ins, still working on it.
Click to expand...
Click to collapse
elcidroyale said:
Hey is this beta or new version addressing the latency available yet? I have an Epic Touch 4G & have tried everything (spoken to support repeatedly over email - thanks!) & still get 1-2 second delay. Difficult to have a normal conversation as we keep cutting each other off as we think we're done speaking.
Click to expand...
Click to collapse
The latest version on the market has all our improvements for latency. There will still be latency from your network or from the device. Stopping apps running in the background can improve the device latency.
Well I downloaded that version and most of that lag seems to be gone. Yippee!
elcidroyale said:
Well I downloaded that version and most of that lag seems to be gone. Yippee!
Click to expand...
Click to collapse
Glad that improved things. Thanks for the update.
I just purchased this after months of debate. Are there any settings to reduce the static on the other caller's end? I did some test calls with a friend's phone, except I was holding both devices in each hand. It doesn't matter who initiates the call, but they'll hear a static noise that doesn't happen if the call is made via mobile network. Could very well be Google Voice itself because people have mentioned it to me before before I purchased Groove IP, but I just want to be sure.
Also, sending and receiving bluetooth calls do work through my car stereo. But if I'm receiving a call, something is missing to tell the radio to pause/mute the music and start the ringer. The phone itself still rings and vibrates, but it's easy to miss a call if the music is loud enough. Is there an additional setting I'm missing? The function works properly if I'm using the regular phone app.
binglejellsx2 said:
I just purchased this after months of debate. Are there any settings to reduce the static on the other caller's end? I did some test calls with a friend's phone, except I was holding both devices in each hand. It doesn't matter who initiates the call, but they'll hear a static noise that doesn't happen if the call is made via mobile network. Could very well be Google Voice itself because people have mentioned it to me before before I purchased Groove IP, but I just want to be sure.
Also, sending and receiving bluetooth calls do work through my car stereo. But if I'm receiving a call, something is missing to tell the radio to pause/mute the music and start the ringer. The phone itself still rings and vibrates, but it's easy to miss a call if the music is loud enough. Is there an additional setting I'm missing? The function works properly if I'm using the regular phone app.
Click to expand...
Click to collapse
The static could be because both phones were in close proximity to each other. Have you tried it with normal calls?
For incoming calls were you using the native music app or another app like pandora? We broadcast that a call is being made or received, the native music app should detect that, but an app like pandora may not since the app isn't the same as the native phone system.
snrb Labs said:
The static could be because both phones were in close proximity to each other. Have you tried it with normal calls?
For incoming calls were you using the native music app or another app like pandora? We broadcast that a call is being made or received, the native music app should detect that, but an app like pandora may not since the app isn't the same as the native phone system.
Click to expand...
Click to collapse
You mean to a landline? I haven't. I did try with another person a few hundred feet away with the same results. I also talked to someone else for a few seconds, but the only thing they asked was if I was whispering. After I had posted on here, I changed my settings to the ones recommended from the "other" forum: http://rootzwiki.com/topic/32464-voip-apps/page__st__10#entry902020. My voice was probably just low due to the low mic gain setting, but I'll leave things the way they are until I get more comments from people's calls.
As for the bluetooth issue, I'm not using my phone to play music. The music is through the radio, which utilizes bluetooth to make phone calls. Normal operation of incoming calls cuts the audio and rings through the car speakers until I pick up. With Groove IP calls enabled, only the phone is ringing and the music/car audio is still playing (which is usually louder than the phone's ringer). Hope that clears things up a little.
Happy Holidays!
I'm on the road a lot and use a bluetooth headset all the time. On my HTC Amaze I was able to voice dial from my bluetooth headset but on the GN2 I can't get past the lock screen and when I do (get past the lockscreen) I have to use S voice. All I'm trying to do is use the voicedialing without ever picking up my phone. Unfortunately I've searched everywhere and can't find or figure it out. Is anyone else having this issue/know of a fix?
Simply pair your headset to your phone. Then with the phone on and you unlocked it, activate your BT headset while watching the screen. You'll need to accept a waver to activate it. Once it is actvated, you can use your BT headset. Youll hear a chime ti promt you to speak.
Sent from my SGH-T889 using xda premium
I gave that a try but unfortunately I still have to unlock the phone in order to use voice dialing. I use face recognition/pin & I'm using a Jawbone Icon.
The thing that annoys me is that I can do a redial(double press the call button) and it works without me having to touch the phone.
Sent from my SGH-T889 using Tapatalk 2
Having the same problem with BlueAnt Q1 and Q2. They both worked as such on my HTC G2:
(after all paired up and connected)
Push button on BT
Say "phone command"
BT responds "activating your phone's in-built voice commands on the connected phone"
G2 says "speak now"
I say "call Fred"
Phone dials Fred
On my SGN2:
(after all paired up and connected)
Push button on BT
Say "phone command"
BT responds "activating your phone's in-built voice commands on the connected phone"
Nothing happens
If I unlock the phone, S Voice is activated
I have some other BT devices, I'll see if they fare any better, maybe it is an issue with BlueAnt?
Queue515 said:
Having the same problem with BlueAnt Q1 and Q2. They both worked as such on my HTC G2:
(after all paired up and connected)
Push button on BT
Say "phone command"
BT responds "activating your phone's in-built voice commands on the connected phone"
G2 says "speak now"
I say "call Fred"
Phone dials Fred
On my SGN2:
(after all paired up and connected)
Push button on BT
Say "phone command"
BT responds "activating your phone's in-built voice commands on the connected phone"
Nothing happens
If I unlock the phone, S Voice is activated
I have some other BT devices, I'll see if they fare any better, maybe it is an issue with BlueAnt?
Click to expand...
Click to collapse
This is the same problem I have with the GN2, I've switched to a pattern lock and now I unlock my phone before using the Bluetooth. It defeats the purpose of being hands free. Once I get a car dock I'll go back to face unlock but this isn't very good. Luckily it's an easy work around and is probably one of the biggest problems I have with the phone. lol
Go to S Voice settings > check wake up in lock screen > set wake up command. ( i didn't do this part as i don't have pattern lock)
Open dialer > go to call settings > Accessory settings > Outgoing call conditions > Select Even when device locked.
Don't know if this helps but I can make calls no prob with my jawbone Icon. To activate S Voice you only need to press and hold the end call button on your headset and it should start up by itself. Once in a while you will not hear the special sound S Voice makes when it's activated (Don't know about headsets that don't support A2DP), that means it is not working properly. All you have to do is press the end call button on your bluetooth again and you will hear the end call sound. Then press and hold the end call button again to reactivate the s Voice, it should work again!
Thanks for your response.
I didn't have the Svoice set as you described, but the call setting was already set. Still not working. Can you try with screen lock set to "Secured with PIN"? That is the security setting required by my employer. I have tried it with and without "With swipe lock" checked. My BT is A2DP.
Queue515 said:
Thanks for your response.
I didn't have the Svoice set as you described, but the call setting was already set. Still not working. Can you try with screen lock set to "Secured with PIN"? That is the security setting required by my employer. I have tried it with and without "With swipe lock" checked. My BT is A2DP.
Click to expand...
Click to collapse
With the Pin enabled I cannot open S voice either.. That's kind of expected though because that's a security breach if I am able to bypass the lock screen just by opening SVoice. For company phones I guess security comes before convenience.
Thank you for confirming. Unfortunately, the workaround (putting the phone in car mode and leaving it open) is much less secure than letting me make a call from a paired device. Oh well.
sent from my phabulous phablet using xda premium
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.