Related
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.
Bluetooth voice dialing was working on the AT&T firmware, but it seems that since updating to the Rogers firmware it doesn't - pressing the call button (1 second press on my Jabra Extreme 2 headset) does nothing at all. Redial (double-tap on the headset) works as you would expect.
Some searching found this thread: http://forum.xda-developers.com/showthread.php?t=1558776
But this doesn't seem to help in my case - I've installed Bluetooth Launch, but the call button still does nothing. Even more strange, if I run "adb logcat" then nothing is logged when I press the call button (I expected to see something from the bluetooth subsystem at least saying it had been pushed, even if it couldn't launch an application to deal with it).
Voice search is installed, and works as you would expect when manually launched.
Any pointers would be appreciated - thanks.
FireFury said:
Bluetooth voice dialing was working on the AT&T firmware, but it seems that since updating to the Rogers firmware it doesn't - pressing the call button (1 second press on my Jabra Extreme 2 headset) does nothing at all. Redial (double-tap on the headset) works as you would expect.
Some searching found this thread: http://forum.xda-developers.com/showthread.php?t=1558776
But this doesn't seem to help in my case - I've installed Bluetooth Launch, but the call button still does nothing. Even more strange, if I run "adb logcat" then nothing is logged when I press the call button (I expected to see something from the bluetooth subsystem at least saying it had been pushed, even if it couldn't launch an application to deal with it).
Voice search is installed, and works as you would expect when manually launched.
Any pointers would be appreciated - thanks.
Click to expand...
Click to collapse
From the previous thread did you disable any security lock on the phone ?
As that was the clincher for me, once disabled security code to unlock/wake up phone the BT button then actually does something when pressed.
Edit: Actually I supposed if the BT button doesn't do anything while the phone is already awake then its something else.
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
Hey all,
So Im running Dirty unicorn 4.4.2 and I got a Bluetooth headset for my motorcycle helmet. Initially when I pressed the voice call button on the BT voice dialer popped up. I wanted Google now insead so I disabled the voice dialer and than it allowed me to select google now. Well here is the issue, I can say "Ok google" and it hears it and begins listening but after that it does not hear anything I say. I have selected to use Bluetooth in G Now settings and have even tried to enable the screen tap sound checkmark (which I head had issues being off) with no luck.
Does anyone have any idea what is causing this? One weird note is while G Now is listening the volume indicator does some weird jumps but it does it when I am not saying anything.
Thanks in advance.
Anyone have any idea? I have a local build of Dirty Unicorns up and running on my computer so I can modify source and kernel but have not found anything that would relate to this problem.
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.