So I got a new car (2016 "facelift" Kia Ceed 4 Tech)... and whilst OK Google Hotword detection over bluetooth sort of works, the
state of the dialler appears quite broken... and I was hoping if anyone could help.
Nexus 5 running Marshmallow paired to the car with Phone & Media Audio selected.. Google Voice Typing settings set to record audio through headset if available.
1) With screen on, say "Ok Google" wait for phone to respond with the first and then second beeps (I guess the second beep is to
signify the phone is then listening over bluetooth)
2) Say "Call xxxxxx mobile/home" etc.
3) Phone responds and starts dialling. Call is answered and the car Infotainment screen gives a prompt to change to "hands free mode", requiring a manual button press..
Not exactly "hands free behaviour".. Not compared to when I pair my wife's Galaxy Note 4, do exactly the same steps and everything goes through seamlessly with
the car automatically going to bluetooth handsfree without requiring me to press the button on the infotainment screen.
Now if you look at the dialler screen on the Nexus 5 whilst the call is going through, you can see the dropdown to manually choose between "Headset" "Speakerphone" "Bluetooth"
and the "Bluetooth" one is indeed selected but clearly the phone and car aren't handshaking to tell the car to automatically default to handsfree. At this point, you can re-select the bluetooth
option but it doesn't do anything, and the car is still waiting for manual confirmation.
More weirdness is, if you start a voice call with OK Google but actually press the phone button to action the call, then it all works fine...
Both Marshmallow and the car are new, so I'm not hopeful that anyone has an answer but given the Note 4 works perfectly, I'm keeping my fingers crossed..
Looks like a known problem since lollipop for nexus and some other phones.. not fixed in marshmallow either.. not sure what to do..LLC.. wait and see I guess
here
Related
Hi all,
Just love the Sensation - but some of the enhancements I have found also have a sting in the tail. Anyone give me any pointers for these?
When riding my motorcycle, I have the Sensation plugged in to crash helmet headset. Found "Not Another Call Manager" to give me phone auto-answer. Normally I have my music on, and when a call comes in it gets auto-answered. Every thing fine - yes, really fine.
Small problem is that when I get kitted up, I turn on the music and slip the phone in my breast pocket. Sometimes as I slip it in, the phone decides to redial the last number, alternatives are music switching off or selecting the next track.
I understand the music oddities - swipe left/right gets you next track and also pause is available - just odd that it does this with the screen turned off. But I don't understand where the phone comes in - I can't find anywhere that you can just swipe the screen in any particular direction to get last number re-dial.
I have now bought a leather wallet to put the sensation in whilst riding, but it didn't stop a "pocket call" first thing this morning, even through the sensitivity seems to be greatly reduced.
All comments, help and guidance welcomed
MrSums
Check in the settings to see if something is enabled that would change the track if you shake the phone.
That seems to be the most likely culprit.
Mrsums said:
Hi all,
Just love the Sensation - but some of the enhancements I have found also have a sting in the tail. Anyone give me any pointers for these?
When riding my motorcycle, I have the Sensation plugged in to crash helmet headset. Found "Not Another Call Manager" to give me phone auto-answer. Normally I have my music on, and when a call comes in it gets auto-answered. Every thing fine - yes, really fine.
Small problem is that when I get kitted up, I turn on the music and slip the phone in my breast pocket. Sometimes as I slip it in, the phone decides to redial the last number, alternatives are music switching off or selecting the next track.
I understand the music oddities - swipe left/right gets you next track and also pause is available - just odd that it does this with the screen turned off. But I don't understand where the phone comes in - I can't find anywhere that you can just swipe the screen in any particular direction to get last number re-dial.
I have now bought a leather wallet to put the sensation in whilst riding, but it didn't stop a "pocket call" first thing this morning, even through the sensitivity seems to be greatly reduced.
All comments, help and guidance welcomed
MrSums
Click to expand...
Click to collapse
i have the exact same problem when riding my bike. the issue is that the phone will pickup the headset connection and freak the **** out and start auto dialing. Mine is worse, it will call and hang up > 3 secs of music > call and hang up > 3 seconds of the next track > loop like this till I pull over and unplug my headset.
The issue is with the headphone jack and somehow its sensing commands as if you have a remote plugged into the line.
i haven't found a way to stop it. Somedays i get by with no problems, while others I will have to pull over 2-3 times on the way to my destination
BrokenWall said:
i have the exact same problem when riding my bike. the issue is that the phone will pickup the headset connection and freak the **** out and start auto dialing. Mine is worse, it will call and hang up > 3 secs of music > call and hang up > 3 seconds of the next track > loop like this till I pull over and unplug my headset.
The issue is with the headphone jack and somehow its sensing commands as if you have a remote plugged into the line.
i haven't found a way to stop it. Somedays i get by with no problems, while others I will have to pull over 2-3 times on the way to my destination
Click to expand...
Click to collapse
Great call! I have had this a few times too, but didn't realise it was the jack connector - I thought it was the act of slipping it into the pocket. Makes a lot of sense as when I use my bluetooth headset (not configured for the bike) everything works perfectly. May have to consider going BT on the bike.
However, once I am up and running I don't think it happens at all.
I have this problem but I don't ride a motorbike - I just get it when I'm walking along with the phone in my trouser pocket.
I made a video of the problem, here is the link:
http://youtu.be/lkwn2CQ-2UU
I have the ibolt xpro car dock running moar 18 rom 4.1.2, did a clean wipe when installed. When i get a call in the car and answer the phone with the answer key on the steering wheel or on the phone itself, the call comes through the earpiece of the phone. At that time the "headset" button shows as if im using bluetooth when its not sending it out through the speakers. Even my display screen shows the elapsed time of the phone call. I then have to turn off the headset button and then hit it again and after that i can hear the other person on my speakers in the car. I had a bluetooth headset that also had this problem and i was told to do a clean install and not to use tibu and restore system apps, that fixed the headset problem but not the car problem. Anybody have a clue on how to fix this?
Just wrote a very simple app called BT GNow, which activates Google Now rather than the default Android Voice Dialer when you hit the hands-free button on your Bluetooth headset. Surprisingly, I can't seem to find another app that accomplishes this simple function. Bluetooth Launch does this to an extent, but the UI is difficult, it requires some configuration, it seems to me to cause wakelock problems, and the instance of Google Now that it starts takes off where Google Now left off (so you are often brought to an old search rather than an opportunity to speak a new voice command).
BT GNow keeps only a limited wakelock, requires no configuration (other than configuring Google Now to accept input from your Bluetooth device and possibly disabling the native Voice Dialer), and starts a fresh instance of Google Now each time.
Here's the Play Store link: https://play.google.com/store/apps/details?id=com.vibaroo.btnow
And the (minimal) website that describes the setup: https://sites.google.com/site/btgoognow/home
Great will try tomorrow
I will try now, great APP man:good:
Fail, my bluetooth now is not working, i tried, factory reset, re-flash system but not working more
Wow, great app. Makes my bluetooth headset and Google Now work as I always expected it would have to begin with.
I noticed that there was a problem with the screen locking and not responding to touches if lockscreen security is enabled and Google Now is interrupted. Solved this problem with the latest version and also improved wakelock control by sticking an icon in the corner of the screen. The icon disappears when the screen is turned off, and the phone is kept awake only as long as the icon is present.
Got rid of the icon that people seemed to dislike (made it invisible).
Donations?
New Feature
Some have reported problems with BT GNow not effectively bypassing the lockscreen. To address this, I've added an option that requires you to say "OK Google" after pressing your handsfree button; this in effect lets Google Now handle the lockscreen itself. You can activate this option by clicking on the app in the launcher and choosing the "OK Google" option.
Note that if you choose this option, you have to make sure that "OK Google" detection is set to work "From any screen": Google Now > Settings > Voice > 'OK Google' Detection > From any screen (checked or set to "on").
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Dzinic said:
Is there a way to use this with non-BT headphones? I have the 3 button control on my headphones and would love to be able to use this app to bypass the voice dialer.
Click to expand...
Click to collapse
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
NYZack said:
I'm not sure. Embarrassing to admit that I don't have a wired headset to try it with. At least one user has reported that it does work with wired headsets, though. Have you tried it?
Click to expand...
Click to collapse
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Dzinic said:
I tried using both of the options but both seem to lead to the voice dialer unfortunately.
Click to expand...
Click to collapse
Did you try disabling the voice dialer (as in the instructions)?
NYZack said:
Did you try disabling the voice dialer (as in the instructions)?
Click to expand...
Click to collapse
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Dzinic said:
I did follow the instructions up to the Voice Dialer point due to not being able to find the Voice Dialer app in the "All" section. I don't know whether I'm blind or lollipop merged it into another application.
Click to expand...
Click to collapse
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
NYZack said:
Hmm. You're right. Since upgrading to Lollipop I don't see it on my phone either. I'll see if I can get a hold of a wired headset to try to troubleshoot it.
You should go Bluetooth!
Click to expand...
Click to collapse
Don't go out and get one just to fix my problem! I just don't use my phone for music enough to justify investing in a bluetooth, haha. Thanks for looking into it.
:thumbup:
Thanks!
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
patientzero said:
Amazing! I'm currently using your app to simulate the MotoX experience on a Nexus 5 (pressing just the button on a Moto Hint to query the Nexus 5). I'm still having a problem with the sound from the headset seeminly not being routed through to the phone after I say "Ok Google" (even though I've got the option enabled within Google Now's settings), but I'll keep working at it.
Click to expand...
Click to collapse
I've noticed that problem if you have more than one bluetooth device connected at once - for instance, if your phone is connected to your car's bluetooth or a stereo headset while connected to your Moto Hint. I'm considering options to try to fix this. In the meantime, perhaps it's better not to use the "OK Google" option and just launch directly from the bluetooth button?
My friend has same thing on his iPhone. I can now use google now with handsfree, when i driving my car. Thanks! The Coolest app on my week!
Wishlist ....
Given the code you have already written here is a little wish from me ... could you implement that the HFP bluetooth headsets just do not launch any application - just volume up and down.
xperia Z, TWIINS bluetooth headset for motorcylce, mono Bluetooth to route Navi output to headset - whenever I press volume down I get the stupid voicedialer or -if disabled- a black screen. I do not want to make any phoncalls on a fast bike!
Thanks in advance.
DrT_Music
I have spoken at length with samsung and plantronics customer support to no avail and would like to see if anyone else has had this issue. Bluetooth and wired headest call volume is extremely loud, much louder than media volume on the same devices. Even with volume set to minimum on both phone and bluetooth headset it hurts my eara and does not seeem safe for longterm use. Devices I have replicated the problem on include Plantronics Voyager Legend, Plantronics Voyager Edge, Jabra Stealth, and some skullcandy wired earbuds. So far both samsung and plantronics state thay they do not guarantee compatability with other manifacturers devices.
I have not had any issues so far and I do have and have used a Plantronics Voyager Legend. I have also used Bluetooth in my car. The only frustrating thing I have had to deal with is the stupid high volume warning you have to bypass to turn the volume up past a certain level. Sorry to hear about your issues.
Speaking of this, I get a pop-up alert when I turn the volume up past a certain threshhold (only happens via blutooth or probably wired headset). The problem is that this happens for each session, rather than just one time only. It's rather annoying because I use blutooth to play music in the car and when I go to raise the volume it stops for the pop-up message, which I have to clear to continue to raise the volume up.
Can this be disabled?
SwordOfWar said:
Speaking of this, I get a pop-up alert when I turn the volume up past a certain threshhold (only happens via blutooth or probably wired headset). The problem is that this happens for each session, rather than just one time only. It's rather annoying because I use blutooth to play music in the car and when I go to raise the volume it stops for the pop-up message, which I have to clear to continue to raise the volume up.
Can this be disabled?
Click to expand...
Click to collapse
That is the same message I am referring to, but it only pops up once per boot for me. As long as I don't reboot, I don't get the message. Each boot, however, I have to deal with the pop up...stupid!
I did extensive searching on this and no help so I thought I would try here.
I had Waze on my old S6 and was able to configure waze to send turn by turn directions and alerts through the phone speaker even if the phone is BT connected to the car by configuring waze settings.
Now that I migrated to the S8, Waze will not put out any sound to the phone speaker or the car speakers whens BT connected. It is totally silent. If not BT connected, it will speak through the phone.
I tried the same procedure I used on the S6 to get the audio through the phone speaker.
Anyone have similiar problems and find a solution?
Thanks in advance.
I haven't tried that yet, I usually let it talk through BT but I'll see if I can get it to work so we know if it's a common problem.
Edit: I checked the slider over to sound to speaker and it worked fine for me, sorry.
Nope i don't have that issue.
Just to be on the safe side (although i bet you did)
Did you :
Settings > Sound and voice > play sound to speaker?
Thank you. Yes, Settings > Sound & Voice > Play sound to speaker has a green, checked button that is swiped to the right. App Volume is set to max. Also Sound it set to "Sound on"
I did some more experimentation.
First, I discovered that under Waze ==> Settings ==> Sound & Voice, you must turn off "Play sound to phone speaker". If you have this on, or green, Waze will NOT provide sound guidance through the phone speakers, BT connected or not. Odd I thought.
Second, with the "Play sound to phone speaker" tuned off, and the phone BT connected to the car, if I put the audio source on the car to BT, the navigation voice does indeed go to the car speakers.
I still have not figured out how to force waze to send the navigation sounds through the phone speakers while the phone is BT connected. I prefer it go through the phone speakers, as I would like to set the car to other audio sources instead of BT.
I'm having the same issue with Google Maps. My S6 was able to send the sounds through the speaker instead of Bluetooth but it seems to longer be possible on the S8... The setting used to be in Google Maps but it's no longer there.
Solution found!
I put in a ticket to Waze support and this absolutely cured it.
1. If you are using a voice (I was) that has including street names under the title, please tap Menu > and type [email protected] in the Search bar. This will clear your cache in Waze and should resolve the issue. To check if you're using this type of voice, tap Menu > Settings > Sound and check which voice you're using underneath Voice Directions.
2. Restart Waze
3. Turn on Settings > Sound and voice > play sound to speaker
Enjoy turn by turn navigation while the phone is BT connected to the car and is playing some other audio source.
This worked for me just now:good: