Setting SA to "On" stops Google Now from talking
3 posters
Page 1 of 1
Setting SA to "On" stops Google Now from talking
Galaxy Note 4
After restart, using Bluetooth headset, can do the "OK Google!" prompt and get spoken answers. ("What time is it?" / "9:02 PM")
If I set SA to "ON," Google Now stops talking, and just displays responses.
If I set SA back to "OFF" Google Now still refuses to talk until I restart the phone.
After restart, using Bluetooth headset, can do the "OK Google!" prompt and get spoken answers. ("What time is it?" / "9:02 PM")
If I set SA to "ON," Google Now stops talking, and just displays responses.
If I set SA back to "OFF" Google Now still refuses to talk until I restart the phone.
DavidRSF- Posts : 3
Join date : 2016-02-06
Re: Setting SA to "On" stops Google Now from talking
Running into the same issue. Call Volume becomes the only thing the volume rockers can control as well when that (or music) plays until the next restart or I force close everything.
NXLTrauma25- Posts : 2
Join date : 2016-02-12
Re: Setting SA to "On" stops Google Now from talking
What version of Android are you using?
How do you initiate the Google Now to prompt when using a Bluetooth headset?
How do you initiate the Google Now to prompt when using a Bluetooth headset?
Re: Setting SA to "On" stops Google Now from talking
5.1.1 (When I first posted this, it might have been 5.1.0)
By saying "Hello Google!"
I reinstalled SA to test this. Restarted phone.
Set SA up for Bluetooth. Restarted phone.
After a restart, SA came up active, with all audio routed to bluetooth earpiece (edge)
Google Now responded with a spoken answer - once. Then it went to silent mode, even after I turned SA turned off.
Restarted phone, Google Now consistently responded with spoken answers. I could close it repeatedly and summon it repeatedly with OK Google!. Each time, it gave a spoken answer to the query.
Turned SA back on.
Google Now responded to a time request with a spoken answer.
Closed Google Now (with return button).
Summoned it again, and it was back in silent mode.
So I seem to get one good interaction with it after SA has been activated. Once I close the Now window, I can't get a spoken response again, until I restart the handset.
Thanks!
By saying "Hello Google!"
I reinstalled SA to test this. Restarted phone.
Set SA up for Bluetooth. Restarted phone.
After a restart, SA came up active, with all audio routed to bluetooth earpiece (edge)
Google Now responded with a spoken answer - once. Then it went to silent mode, even after I turned SA turned off.
Restarted phone, Google Now consistently responded with spoken answers. I could close it repeatedly and summon it repeatedly with OK Google!. Each time, it gave a spoken answer to the query.
Turned SA back on.
Google Now responded to a time request with a spoken answer.
Closed Google Now (with return button).
Summoned it again, and it was back in silent mode.
So I seem to get one good interaction with it after SA has been activated. Once I close the Now window, I can't get a spoken response again, until I restart the handset.
Thanks!
DavidRSF- Posts : 3
Join date : 2016-02-06
Re: Setting SA to "On" stops Google Now from talking
OK, so you have Google Now to constantly listen for "Google Now" command. You are keep the phone in Bluetooth (mono) mode using the SoundAbout "Media audio" setting to "Bluetooth (mono)".
When you say "silent mode" does that mean Google Now isn't responding or the phone is going into vibrate/silent mode?
When you say "silent mode" does that mean Google Now isn't responding or the phone is going into vibrate/silent mode?
Re: Setting SA to "On" stops Google Now from talking
Yes, it is set to listen for Google Now at all times.
This time, I had Media Audio on the main panel set to "Let App Decide."
I had Connectable Devices | Bluetooth settings | Media audio behavior set to "Bluetooth (A2DP).
I'm sorry, I don't remember how these were set when I originally started the post. This how they are set now.
I meant that it was not vocalizing anymore. It had switched back to only showing card-style responses to any query.
The voyager edge is using the PLT hub app. It is a mono headphone, but it accepts both mono and A2DP-directed audio.
Thanks very much!
(My goal is that when a Bluetooth device is connected, no audio will come from the phone, and all normal audio will route to the Bluetooth earpiece or other Bluetooth device.)
This time, I had Media Audio on the main panel set to "Let App Decide."
I had Connectable Devices | Bluetooth settings | Media audio behavior set to "Bluetooth (A2DP).
I'm sorry, I don't remember how these were set when I originally started the post. This how they are set now.
I meant that it was not vocalizing anymore. It had switched back to only showing card-style responses to any query.
The voyager edge is using the PLT hub app. It is a mono headphone, but it accepts both mono and A2DP-directed audio.
Thanks very much!
(My goal is that when a Bluetooth device is connected, no audio will come from the phone, and all normal audio will route to the Bluetooth earpiece or other Bluetooth device.)
DavidRSF- Posts : 3
Join date : 2016-02-06
Re: Setting SA to "On" stops Google Now from talking
OK, I see what happened.
Google Now had Settings / Voice / Bluetooth Headset turned on.
When you use a headset that is both Bluetooth A2DP media and Bluetooth SCO (mono) phone, SoundAbout was only turning on the Bluetooth A2DP media channel. Google now is trying to send the audio to Bluetooth SCO (mono) because "Settings / Voice / Bluetooth Headset" is turned on.
If you turned that off, then the audio would go to the Bluetooth headset via Bluetooth A2DP.
Instead, I've found a way to allow both.
New versions have just been uploaded to Google play that will fix this issue.
You can get them now from the Beta section located here (need a login to the message board). There is also Betas for SoundAbout and SoundAbout Pro.
https://soundabout.forumotion.com/f8-download-beta-versions
Google Now had Settings / Voice / Bluetooth Headset turned on.
When you use a headset that is both Bluetooth A2DP media and Bluetooth SCO (mono) phone, SoundAbout was only turning on the Bluetooth A2DP media channel. Google now is trying to send the audio to Bluetooth SCO (mono) because "Settings / Voice / Bluetooth Headset" is turned on.
If you turned that off, then the audio would go to the Bluetooth headset via Bluetooth A2DP.
Instead, I've found a way to allow both.
New versions have just been uploaded to Google play that will fix this issue.
You can get them now from the Beta section located here (need a login to the message board). There is also Betas for SoundAbout and SoundAbout Pro.
https://soundabout.forumotion.com/f8-download-beta-versions
Similar topics
» Google Navigator stops after 5 or 6 directions
» TALKING NAVIGATION DOESNT WORK THROUGH speakers when listening to radio or cd only through bluetooth channel
» Soundabout randomly stops working
» Bluetooth stops when headphone jack is used
» Soundabout Pro key stops the main app from launching!
» TALKING NAVIGATION DOESNT WORK THROUGH speakers when listening to radio or cd only through bluetooth channel
» Soundabout randomly stops working
» Bluetooth stops when headphone jack is used
» Soundabout Pro key stops the main app from launching!
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|