This is what I have observed when the screen is off.
When I engage voice dial on my BT headset, I will hear the confirmation beep , the screen will turn on showing the lock screen and then it will either turn off the screen or just sit there doing nothing. S-Voice will not show up or response to my voice command.
I have tried this with a Jawbone Icon and my plantronic voyager pro both behaving the same way.
The work-around so far I found is to turn on the screen to at least showing the lock screen and it will work like it should.
Is this what you guys are experiencing?
My car has built-in bluetooth support for speakerphone and I've noticed when my phone is paired with the car, s-voice does not pick up anything. Even with the phone unlocked and on the s-voice screen.
Usually, when you tap the microphone button, and the button lights up blue (like an EQ) when it's recording your voice, but with bluetooth paired, it stays flat, like it's not picking up any sound. I manually disabled bluetooth, and s-voice went back to working as normal.
Sounds like there are more symptoms to this BT/S-Voice bug than what I have experienced so far.
I spent a whole day today with my SIII and I have to say that I miss my Samsung Focus (WP7).
With my Focus I can do everything via the BT headset and the speech recognition for names is so much better than the SIII (I have tried both Google and Vlingo speech recognition). In average I had to try 5 or more times before the correct name is recognized. I drive a full size SUV and was using a Jawbone Icon headset, noise should not have been an issue.
I hope these bug will be worked out ion future updates.
I have had teh s voice completely ignore my BT headset. I fixed it by unpairing and then repairing (pun optional) the headset. This feature is weak.
Related
Brought a jabra bt8010 and all is working fine, the only issue i have is that the screen will not go off.... Even when you press the off button quickly to turn it off it comes straight back on. This only happens when the Jabra is connected to it.
Anyone one got any ideas
Problem solved, it appears that there was a tweak i had applied to not go to sleep when within a call, when the Jabra is connected it must think that it is always in a call so the screen never goes off. Just reversed this tweak and now the screen goes off and stays off.
Well, I don't have a BT headset but never seen people having this issue. I think reversing that tweak is just a workaround, there must be another way to make it turn off automatically. Hopefully someone better informed will answer to this.
Anybody got any other suggestions ? Not an ideal fix but a fix none the less.....
I use the 8010 and I had that problem. I deleted the connection in both devices, and paired them again at a greater distance. The phone always communicate with the headset, like sometimes, the headset will come on for no reason. I look at the headset and the music icon disappear, then reappear. I still cant figure out why. Love the headset though. It doesn't come on that much no more, but staying on, no..
already tried deleting it on both ends and pairing, just does the same thing.
caller ID is now working though with the Jetware fix which is really handy.
I'm sure I'm being very dim but I thought Froyo supported Bluetooth voice dialling. Just tried with my BlueAnt headset, press the button on the headset and I get the low beep that means it can't do anything. I can receive calls on the headset fine.
Should this work and what am I doing wrong?
TIA
norm
I too had some issues with this, especially after installing skype. I finally got it to work by setting up the phone dialer as the default and pressing the bluetooth button twice insted aod the usual once.
It seems that some firmwares have this disabled. not sure why.
Anyone see this behavior? My voice dialing worked before but just stopped. I have wiped the phone and its still doing this. Bone stock, not rooted.
When I "long press" on my Plantronics headset I get the beep like its going to go into the voice dial and a the screen flashes grey but then gets "minimized" immediately. Then the prompt from the lady comes from the phone headset instead of my bluetooth headset. Also nothing shows up on the screen (where it used to have text matching what the text-to-speech voice said). When i say something in the headset the phone doesnt hear it.
I used to use this regularly so its a bit of an annoyance that it doesnt work. I searched but most people are reporting different issues like recognition, general bluetooth bugs, etc.
In case any archaeologists find this thread it appears something was wrong in some cache somewhere. I ran Clean Master to clear all caches and it magically started working normally again.
Hi everyone,
First off, I'd like to start by wishing to everyone happy Holidays!
I have been literally searching all over the Internet for any information regarding the issue I am about to describe in detail and since no solutiuon was found, there's nothing left for me to do but ask for help, and hopefully get the right answer. That's why I want to be as specific and informative as I can.
The problem I am having is this; I recently purchased a new Jabra Motion bluetooth headset and decided to start using the voice dialing function on my Galaxy S4, since it works very well (when it works) and is really a breeze, especially while driving.
In short, the problem is that the S4 completely loses audio (other party hears nothing as well) after initiating a call, via voice dial commands through any bluetooth headset (I'll get to that). When that happens, the phone has no in-call audio whatsoever (with headset on or off, with speakerphone or earpiece on), no matter how many times I start or receive a call and nothing brings audio back, except a reboot from the i9505's power button menu. All other audio works, like videos, unlock sounds, ringtone, music, even the little chirp right before the other party's phone starts ringing and the hangup chirp can also be heard. The worst part is, that it occurs completely at random, it can happen on the 1st time I voice dial or the 10th time, for example. The problem has not shown itself, when initiating a call normally or picking up with a headset connected, before audio gets lost.
Before purchasing the Jabra Motion I've been using an earliest model Jawbone Icon and had never even tried the voice dialing feature on any previous phones or the S4. After encountering this problem I tried to test whether or not it would happen when using that headset, the result was yes, so it is safe to say it will happen when using any bluetooth headset, with the same randomness.
This is what both headsets launch on the phone, when attempting to voice dial:
View attachment 2474439
The phone itself is a completely stock and un-rooted 16GB Galaxy S4 i9505, running the latest available Jelly Bean 4.3, build: XXUEMJ7.
The headsets are always connected to 2 devices simultaneously (in case that might shed some light)
What I've tried so far (no difference made, at all):
- Toggled bluetooth off and on
- Tried unpairing and re-pairing both headsets on both phones, or only on i9505
- Tried factory resetting both headsets
- Tried to toggle, while in call, between speakerphone, earpiece, headset, turning off headset and all possible combinations
- Removed Jabra companion app and services app, then reinstalled, then tried without the apps installed.
- Cleared cache from both Jabra apps.
- Cleared cache from system apps such as dialer, bluetooth and Google Search.
- Contacted support of both Samsung and Jabra (huge waste of time)
Sorry for the very long post, but I want to be clear and comprehensive as possible. Any help would be highly appreciated.
Please no factory reset suggestions, I am aware of that possibility, but do not want to go through all the trouble to set up tons of apps and stuff again.
Thanks in advance to anyone willing to help!
Anyone?
Please?
I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.
I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted
Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.