Bixby voice wake-up on one UI - Samsung Galaxy S9 Questions & Answers

Hi everyone.
After updating to one UI I can't use voice commands to take a picture because it gives me a warning that I can't enable voice control when Bixby voice wake-up is turned on.
However, contrary to what happened in the previous versions of Bixby, I can't disable voice wake-up.
Is anyone else experiencing this problem?

sirsomething said:
Hi everyone.
After updating to one UI I can't use voice commands to take a picture because it gives me a warning that I can't enable voice control when Bixby voice wake-up is turned on.
However, contrary to what happened in the previous versions of Bixby, I can't disable voice wake-up.
Is anyone else experiencing this problem?
Click to expand...
Click to collapse
its works fine

sirsomething said:
Hi everyone.
After updating to one UI I can't use voice commands to take a picture because it gives me a warning that I can't enable voice control when Bixby voice wake-up is turned on.
However, contrary to what happened in the previous versions of Bixby, I can't disable voice wake-up.
Is anyone else experiencing this problem?
Click to expand...
Click to collapse
I was unable to do it since oreo, nothing new... You still can disable voice wake up in bixby settings.

sirsomething said:
Hi everyone.
After updating to one UI I can't use voice commands to take a picture because it gives me a warning that I can't enable voice control when Bixby voice wake-up is turned on.
However, contrary to what happened in the previous versions of Bixby, I can't disable voice wake-up.
Is anyone else experiencing this problem?
Click to expand...
Click to collapse
If you bixby voice wake up turned on, you can't use Camera voice control to take a photo. Alternatively, what you can do is call bixby and tell it to capture a photo. I tried it this way (in oreo though, not tried it in pie yet) and it worked fine

Related

[Q] Camera forceclose - No lastpass - Only updated

Hello everyone,
I am having some troubles with stock Camera. It randomly forcecloses when launched.
It doesn't happen always, it actually happens rarely, but sometimes it did while I was in need of a quick pic.
It happens both in landscape and in portrait mode, even if launched with quick setting (volume down button).
I've looked for similar issues around xda and the web; most of them were solved in Lastpass settings, which I don't have.
This is happening recently; before Christmas I updated my firmware to 3.28.401.7 and flashed Android Revolution 22.1 and everything works fine since then except, occasionally, camera.
How can I fix this?
Thank you
Couple folks have reported camera force closed issues due to the "Ok Google" being enabled for any screen, conflicting with the Sense camera.
In the Google app, tap the 3-line menu button (upper left), go to Settings>Voice>"Ok Google" Detection, and verify the "From any screen" option is OFF.
Could be something else causing the issue, but this is what came to my mind.
redpoint73 said:
Couple folks have reported camera force closed issues due to the "Ok Google" being enabled for any screen, conflicting with the Sense camera.
In the Google app, tap the 3-line menu button (upper left), go to Settings>Voice>"Ok Google" Detection, and verify the "From any screen" option is OFF.
Could be something else causing the issue, but this is what came to my mind.
Click to expand...
Click to collapse
The option is already OFF and I've had this issue since before I updated the Google app.
Thank you for your support though.
I thought that this could fix with the first eventual update. It did not.
Any tips?
Please!

"Ok Google" vs camera voice control since Lollipop

Ever since the Lollipop upgrade, the only way I can get "Ok Google" recognition to work from all screens is to disable S Voice. But when I do that, I can no longer voice-control the built-in camera app (it tells me I have to enable S Voice).
Is there a way to fix this, or are we now forced to abandon one of these two useful features?
Gary02468 said:
Ever since the Lollipop upgrade, the only way I can get "Ok Google" recognition to work from all screens is to disable S Voice. But when I do that, I can no longer voice-control the built-in camera app (it tells me I have to enable S Voice).
Is there a way to fix this, or are we now forced to abandon one of these two useful features?
Click to expand...
Click to collapse
Are you sure you have that option activated in the camera under settings?
Also, I'm not a s/voice user myself, but I don't have it disabled. I just removed it from being activated from the home button.
Kamau54 said:
Are you sure you have that option activated in the camera under settings?
Click to expand...
Click to collapse
It turns off when I disable S Voice. If I try to turn it back on, it tells me I need to enable S Voice first.
Also, I'm not a s/voice user myself, but I don't have it disabled. I just removed it from being activated from the home button.
Click to expand...
Click to collapse
And does that let you use "Ok Google" recognition from all screens (including the lockscreen)? For me, that option in the Google Now settings is greyed out unless I disable S Voice.
No. Disable Svoice, activate ok google detection. Open your camera app and turn on voice. It will ask to enable Svoice. Enable it. Ok google voice still works on all screens and voice recognition works in the camera app as well.
Exactly correct.
erick161 said:
No. Disable Svoice, activate ok google detection. Open your camera app and turn on voice. It will ask to enable Svoice. Enable it. Ok google voice still works on all screens and voice recognition works in the camera app as well.
Click to expand...
Click to collapse
Works great. Thank you!
Ok Google Fix
This may help those who updated to 5.0.1 on the At&t Note 4. It may work for other note 4's. This applies if you already had Google Now set to work on all screens along with various other settings and now they are greyed out. If you never could get Google Now to work on all screens in 4.4.4 that is a different problem.
1. Disable S Voice, the Samsung voice control. Simply go to apps and disable it.
2. Either Restart your Phone, or Power it Off then turn it back on.
3. Try the settings in Google Now Voice again. The first setting which probably worked before - "From The Google App" should still be able to be toggled on and off.
The Second setting, "From Any Screen" May now work and let you train your voice. A clue is the very bottom of the screen "Train Voice Model" and "Delete Voice Model" should no longer be greyed out.
If the second setting gets you to the next screen now where you say Google Now three times but nothing happens, go to the next the step.
4. Put your Note 4 into safe mode. You will not be looking for any programs that might be blocking Google Now as you might expect. I know what is blocking it, it's S Voice that even though is turned off is still blocking it.
If you do not understand safe mode, or have any reservations doing it, don't. Though I feel it is a safe thing to do, I am not going to give instructions how to do it, you can find it online easily. I take no responsibility if you find how to do it then make a mistake somehow and screw up your phone.
5. Once in safe mode, and staying in safe mode and when the phone has loaded everything it is going to load, go to the Google Now settings again and you should see all settings available now. In the second setting "From Any Screen" toggle it on and when it takes you to the voice training do the three steps of Google Now voice training.
At that point you are done. Remember, there are other settings that may affect the use of Google Now but if you had it working before the Lollipop upgrade those settings should not have changed.
6. Simply restart the Note 4 and Google Now should work from any screen again.
7. You should be able to restart S Voice at this point if you need it, primarily for the camera voice commands. I decided to leave mine disabled since I rarely to never use the camera voice commands. You do not need S Voice to be active to use Google Now.
tampa8 said:
This may help those who updated to 5.0.1 on the At&t Note 4. It may work for other note 4's. This applies if you already had Google Now set to work on all screens along with various other settings and now they are greyed out. If you never could get Google Now to work on all screens in 4.4.4 that is a different problem.
1. Disable S Voice, the Samsung voice control. Simply go to apps and disable it.
2. Either Restart your Phone, or Power it Off then turn it back on.
3. Try the settings in Google Now Voice again. The first setting which probably worked before - "From The Google App" should still be able to be toggled on and off.
The Second setting, "From Any Screen" May now work and let you train your voice. A clue is the very bottom of the screen "Train Voice Model" and "Delete Voice Model" should no longer be greyed out.
If the second setting gets you to the next screen now where you say Google Now three times but nothing happens, go to the next the step.
4. Put your Note 4 into safe mode. You will not be looking for any programs that might be blocking Google Now as you might expect. I know what is blocking it, it's S Voice that even though is turned off is still blocking it.
If you do not understand safe mode, or have any reservations doing it, don't. Though I feel it is a safe thing to do, I am not going to give instructions how to do it, you can find it online easily. I take no responsibility if you find how to do it then make a mistake somehow and screw up your phone.
5. Once in safe mode, and staying in safe mode and when the phone has loaded everything it is going to load, go to the Google Now settings again and you should see all settings available now. In the second setting "From Any Screen" toggle it on and when it takes you to the voice training do the three steps of Google Now voice training.
At that point you are done. Remember, there are other settings that may affect the use of Google Now but if you had it working before the Lollipop upgrade those settings should not have changed.
6. Simply restart the Note 4 and Google Now should work from any screen again.
7. You should be able to restart S Voice at this point if you need it, primarily for the camera voice commands. I decided to leave mine disabled since I rarely to never use the camera voice commands. You do not need S Voice to be active to use Google Now.
Click to expand...
Click to collapse
Used to
Worked at stage 3. Reenabling S Voice rebroke OkGoogle. RE Disabled S Voice. All that's changed is either the screen must be on or it must be plugged in. Like my Note Pro. Used to just need to be on..screen off and all.
That's a change with Lollipop and not a "problem." (now it is screen on or charging) It appears Ok Google no longer works with the screen off by design, at least on the Note 4.
I can keep S Voice on after doing the steps. (Though I have since turned it off) Try doing all the steps and while in safe mode turn off then on the settings. It's possible this makes Ok Google the "default" over S Voice.

Google Assistant - No audible acknowledgement

If the screen is not visible, when I say "OK Google" there is no audible tone to say she is listening, is there a setting to turn this on?
I just experienced the same today.
Sent from my Pixel XL using XDA Premium HD app
Are you sure you are not connected to a bluetooth device?
That was the only time I had this issue... When in my car, bluetooth connected, I would not get any audio feedback. Realized it was coming via bluetooth and disconnected.
Good luck and let us know!
Scott said:
Are you sure you are not connected to a bluetooth device?
That was the only time I had this issue... When in my car, bluetooth connected, I would not get any audio feedback. Realized it was coming via bluetooth and disconnected.
Good luck and let us know!
Click to expand...
Click to collapse
That would be it. Never thought of that being the issue. No big deal to me.
Sent from my Pixel XL using XDA Premium HD app
No, I have Bluetooth turned off. The only feedback I get from Assistant is a very slight vibration and the on-screen animation of the 4 colored dots. What sort of notification do you get?
Thanks.
This is normal and frankly welcomed lol the crackling beep that would previously sound off was not appealing.
Sent from my Pixel XL using XDA-Developers mobile app
peejayw said:
No, I have Bluetooth turned off. The only feedback I get from Assistant is a very slight vibration and the on-screen animation of the 4 colored dots. What sort of notification do you get?
Thanks.
Click to expand...
Click to collapse
Ran into the same exact problem.... when I first got the phone it would make a noise to notify you it's listening after saying "OK google". For some reason even with the volume all the way up and everything turned on (voice set to 'on', rather than hands-free) it no longer makes any noise or responds, only a slight vibrate.
I called tech support and they told me this is not normal (duh), and had me factory reset... same thing, it persists... so they are mailing me a new phone.
peejayw said:
No, I have Bluetooth turned off. The only feedback I get from Assistant is a very slight vibration and the on-screen animation of the 4 colored dots. What sort of notification do you get?
Thanks.
Click to expand...
Click to collapse
It's a bug. If you go to Settings>Accessibility>Switch Access> and turn it ON the audible tone will return. I've talked with support and gotten nowhere.
N3V3RS3TTL3 said:
It's a bug. If you go to Settings>Accessibility>Switch Access> and turn it ON the audible tone will return. I've talked with support and gotten nowhere.
Click to expand...
Click to collapse
Wow your my hero, was so irritated by this.... what the hell is switch access? The settings for it don't really explain what it does..
sulpher said:
Wow your my hero, was so irritated by this.... what the hell is switch access? The settings for it don't really explain what it does..
Click to expand...
Click to collapse
Yep, It drove me crazy too. I do know that activating switch access solved the audible notification issue, but it adds another. Check out your camera while switch access is activated. There are added zoom and 5 second burst options. I just hope they get this bug worked out.
N3V3RS3TTL3 said:
Yep, It drove me crazy too. I do know that activating switch access solved the audible notification issue, but it adds another. Check out your camera while switch access is activated. There are added zoom and 5 second burst options. I just hope they get this bug worked out.
Click to expand...
Click to collapse
So I figured out if you disable the talkback app it kills both talkback and switch access under accessibility, which seems to fix it as well!
And that explains those buttons in camera lol.. was wondering why those randomly kept popping up. Even with switch access disabled I was randomly getting them...
EDIT- Nevermind, it only works after you disabled talkback if switch access was on when you disabled talkback, and only until you reboot. So it must leave a service running even after disabling talkback. So I guess we're stuck with it on...
---------- Post added at 11:55 PM ---------- Previous post was at 11:19 PM ----------
lol gdi... now it ding's twice if you say 'ok google' when the screen is off....
THESE ARE STUPID PROBLEMS TO HAVE GOOGLE...
After first day of using my phone I noticed that assistant wasn't making confirmation tone after I would say Okay Google.
Today someone on the pixel Facebook group just happened to mention it and offered Google advice on how to fix it.
Go to settings > accessibility > enable "switch access".
Mine works now, how about yours?
From what I've read on other forums, enabling Switch Access also puts play controls on your YouTube screen (it is an accessibility helper after all). I'd rather have no Assistant acknowledgement tone than put up with those controls on my screen.
Has anyone found an actual solution to this problem yet? Its been a few months now.
Ok, we need to get this straight. The beep was removed by Google intentionally, so it's not a bug. Since they consider this a "feature", there will not be a way to "fix" it. Next, the Switch Access is NOT a fix. It's a workaround. And, just like many workarounds, it solves one problem and gives you another -- in my case, my volume control no longer work.

Google Assistant

Hi, recently bought my M20X and I can't seem to wake my device with HEY (OK) Google with the screen off. Cannot seem to locate in settings on how to make it work
Does anyone else have the same issue? Is it a bug or normal that it doesn't work? Or is there a workaround?
Thank you.
Doesn't work with the screen off, you can only use Huawei's build in assistant with the screen off
And you have an idea how to set up a Google Assistant permanently. I made a button on the screen but every time I have to indicate it as an assistant application because it loses the settings.

Question Anyone know of a quick way to enable/disable "Hey Google"?

As the title suggests, anyone know of a quick way to achieve this?
I'd love something like a quick toggle or widget.
It may be possible to add a shortcut to the activity, via a custom launcher like Nova, to bring up the Google Assistant settings menu. Which would offer some speed compared manually navigating there.
Though if someone knows of a widget or quick toggle addition which I've not been able to find, let us know!
Also similarly, how do find the battery hit, if any, by having "Hey Google" voice activation running all the time?
Goggle Assistant is one of the first packages I disable. Temporarily disabling Google play Services might kill it too... lol, I run like that most of the time. You need to disable find my device as a Administrative Assistant first probably to do that.
Package Disabler allows you to set a widget to toggle selected package on/off real time. It's primarily for Samsung phones but there's a version for other phone manufacturers. I never tested that variant. They respond to emails.
blackhawk said:
Goggle Assistant is one of the first packages I disable. Temporarily disabling Google play Services might kill it too... lol, I run like that most of the time. You need to disable find my device as a Administrative Assistant first probably to do that.
Package Disabler allows you to set a widget to toggle selected package on/off real time. It's primarily for Samsung phones but there's a version for other phone manufacturers. I never tested that variant. They respond to emails.
Click to expand...
Click to collapse
Hmm but if I disable it then it'll indeed be completely disabled.
Perhaps I should have been more explicit, its the "Hey Google" voice detection I'd like to quickly toggle on/off.
I have Google speakers at home, but for example, it'd be great to be able to toggle my phone to respond to the voice command with the flick of a switch (home screen widget perhaps) rather than go through the settings, which of course would be pure laziness and save me a few seconds. But, this is Android after all, anything is possible
cd993 said:
Hmm but if I disable it then it'll indeed be completely disabled.
Perhaps I should have been more explicit, its the "Hey Google" voice detection I'd like to quickly toggle on/off.
I have Google speakers at home, but for example, it'd be great to be able to toggle my phone to respond to the voice command with the flick of a switch (home screen widget perhaps) rather than go through the settings, which of course would be pure laziness and save me a few seconds. But, this is Android after all, anything is possible
Click to expand...
Click to collapse
Problem is Google is a vampire of a data miner and not to be trusted. Do you really want it to have mic or camera access at all?
Especially in your home?
I've never explored toggling it, just killing it.
Samsung's bixby is another one, after reading its eula it was so disabled
blackhawk said:
Problem is Google is a vampire of a data miner and not to be trusted. Do you really want it to have mic or camera access at all?
Especially in your home?
I've never explored toggling it, just killing it.
Samsung's bixby is another one, after reading its eula it was so disabled
Click to expand...
Click to collapse
I certainly understand peoples hesitancy with Google and such privacy concerns, but I for one aren't that fussed.... I have my speakers listening and it doesn't bother me....
Each to their own though and yeah I can see why you and others choose to disable such features entirely
it already has a tile in quick settings called Mic Access for me. does exactly what you want.
Are you talking about the short press on power button that activates Google Assistant? Or am I misunderstanding your question?
Az Biker said:
Are you talking about the short press on power button that activates Google Assistant? Or am I misunderstanding your question?
Click to expand...
Click to collapse
No, they're talking about the ability to say "Hey Google" or "Okay Google" to get their phone to start listening. The previous poster's suggestion about the Mic access Quick Tile might be the best answer.
The OP is looking for a way to temporarily turn off it's ability to be woken up by voice command, and to just as easily re-enable it.
thisbewhatido said:
it already has a tile in quick settings called Mic Access for me. does exactly what you want.
Click to expand...
Click to collapse
This is kind of a solution, though this would also disable all mic access presumably and not just per-app, so I'd need to toggle it back on to make phone calls etc.
I probably just need to not be lazy and manually go to the setting when needed lol
Az Biker said:
Are you talking about the short press on power button that activates Google Assistant? Or am I misunderstanding your question?
Click to expand...
Click to collapse
Thanks, though specifically I'd like to be able to toggle the hey Google voice detection. Eg it not listening all the time, but at the flick of a switch, listen for it and activate the assistant
cd993 said:
Thanks, though specifically I'd like to be able to toggle the hey Google voice detection. Eg it not listening all the time, but at the flick of a switch, listen for it and activate the assistant
Click to expand...
Click to collapse
Maybe a combination of Tasker and Auto Voice will work? Idk, but check out the thread below where someone talks about an "always listening" mode. May be too much effort for the result though.
https://android.stackexchange.com/q...t-to-toggle-ok-google-detection-always-on-off
Lughnasadh said:
Maybe a combination of Tasker and Auto Voice will work? Idk, but check out the thread below where someone talks about an "always listening" mode. May be too much effort for the result though.
https://android.stackexchange.com/q...t-to-toggle-ok-google-detection-always-on-off
Click to expand...
Click to collapse
Thanks for this, will have a look into it.
Appreciated!

Categories

Resources