In my research it looks like Samsung has disabled okay google trusted voice. In other words, when I say okay google with the screen off nothing happens even though I have trusted voice on. It works fine on my 6p.
My question is has anyone ever found a workaround for this.
It really annoys me they are trying to force me to use svoice to have this Android feature.
Yes, if you go to the Apps - settings - Language & Input - Look under virtual keyboard, there will be a little sprocket. You can click on that and tell it to allow 'ok google' only on the main screen, on any screen or anytime even when the phone is locked it will use your voice to unlock it. ,
I believe that if the screen is off, it must be charging so that is not wasting the battery listening for the command.
rbgCODE said:
Yes, if you go to the Apps - settings - Language & Input - Look under virtual keyboard, there will be a little sprocket. You can click on that and tell it to allow 'ok google' only on the main screen, on any screen or anytime even when the phone is locked it will use your voice to unlock it. ,
Click to expand...
Click to collapse
is there a way for nougat?
Outbreak444 said:
I believe that if the screen is off, it must be charging so that is not wasting the battery listening for the command.
Click to expand...
Click to collapse
It seems like that (may be?) true for the Exynos chip. The SnapDragon chip has the hardware built in (and activated) to 'always listen'. The SnapDragon 810 and later has this, and this phone should be able to do it.
This guy figured it out (somehow or other) - has to be the SnapDragon version, I believe, because it's on Sprint https://www.youtube.com/watch?v=zysh2GwYp9U
I have a european S7 (Exynos). I can wake the Phone with S-Voice by saying "Hello Galaxy" also when not charging.
A few weeks ago this also worked (only when charging) by saying "Ok Google", but this doesnt work anymore. I dont know whats the reason. I also dont have an option in the input settings where i can tell the phone when to listen to my voice. Does anyone know how to fix this with google?
I'm in the same boat as the previous comment. I was able to unlock the phone saying OK Google when the phone was plugged into Power. all settings are on for OK Google. Verizon Note 5 latest up-to-date firmware
The newer Google app updates have broken this feature. If you uninstall all updates of the Google app the original one works just fine with the screen off.
Related
I think about buying the Axon 7, but got one question left and haven't found an answer anywhere:
Is the OK Google Command working without the screen being turned on or the device being charged?
Basically: is it behaving like a Nexus device would? I know many devices only react to "OK Google" if the device is turned on and/or charging.
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Delete
xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
notese said:
This is not true. When charging, I can say ok google and the devices listens to me. Also, if the screen is on and I'm not charging, I can still say ok google and it will listen.
Click to expand...
Click to collapse
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
xxBrun0xx said:
This does not work on the Axon 7. Nexus 6P and Moto phones are the only devices I know of that do this.
Click to expand...
Click to collapse
And the V20 apparently
xxBrun0xx said:
Could be wrong but it sounded like he was asking if off screen voice commands worked while the phone was not charging?
Click to expand...
Click to collapse
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
smuurfi said:
And the V20 apparently
You are right! I got really used to using "OK Google" while the phone is in stand-by, i.e., screen turned off and not charging.
Why are vendors not able to properly implement this? The Snapdragon is technically able to do this.
Click to expand...
Click to collapse
Yeah it really breasts me. I miss that from my Nexus 6p, but that's about the only thing I miss other than camera and nougat. The snapdragon 820 is amazing and battery life on the Axon is better than the 6p.
Sorry to bring up an old thread, but I've missed being able to say Okay Google from when the screen is off like I was able to on the 6P. I've been trying to figure out why and I think maybe one of two things (maybe both) is happening. One is that the power manager automatically screen cleans the Google app. The app isn't in the power management menu so that you can toggle off screen cleaning. The other is that I think the phone turns off the mic when the screen turns off and locks. However, if I just used Google Assistant and turn off the screen, I am able to use Okay Google with the screen off if I say it a split second after I turn off the screen with the power button. Sometimes it works, sometimes I have to enter my PIN, but it always has to be right after using Google Assistant and locking the screen. Throwing this out there with the hopes that someone might be able to figure out how to get around this.
Yep same
Mike
As title suggests, voice recognition has been really unreliable through my daily usage.
If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.
if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.
any of you guys can share their experience?
gilad215 said:
As title suggests, voice recognition has been really unreliable through my daily usage.
If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.
if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.
any of you guys can share their experience?
Click to expand...
Click to collapse
I have the same issue...
Same issue here. I think it's because of Samsung's aggressive management that won't allow Google Now to run in the background when the screen is off.
Sent from my SM-G950F using Tapatalk
Same issue here
I normally have to reboot to get "Okay Google" command to work.
for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?
electric0ant said:
for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?
Click to expand...
Click to collapse
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.
Sikrik said:
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.
Click to expand...
Click to collapse
what difference would re-flashing the software achieve?
flashing stock firmware can be achieved using odin.
and after rooting what can be done to fix this issue?
I don't know why re-flashing it worked but, it did. I also don't care. The phone works perfectly now. I keep seeing the same remedies over and over on forums such as this and NONE of them worked. Now that my phone is working, I shared what I did to get it fixed. I'm not a techie, I'm a truck driver so, if you said that I can flash stock firmware with Odin, you'd be wrong. Besides, why would I? Samsung screwed it up, they can fix it. It was free and it worked.
Hi all, hopefully this has not been discussed. I searched but from the xda app search isn't so great...
Anyway wondering if anyone is having issues with trusted voice. I noticed okay Google was only working when phone was authenticated. And not from secured lock screen. Figured trusted voice was disabled, so I checked and it's just not there. (See image). I'm on 4.5.8 stock not rooted. I have tried clearing data on Google app.
Any suggestions is appreciated.
Thanks!
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
3DSammy said:
I wanted to use Google Assistant so had to use the beta versions of Google app and services. My Smart Lock screen is showing Trusted Voice, Trusted Face, On body, Trusted places, Trusted devices. With that being stated Google Assistant has never worked from my the lock screen which requires Trusted Voice to be enabled. Of course it's enabled on my OP5 but still doesn't work, which is a real pain in the butt.
Current versions:
Google v7.9.18.21.amd64
Google Play Services v11.5.20
I running OOS v4.5.8 with an unlocked bootloader and rooted (SuperSU). Recently I changed from stock to the Franco Kernel but Trusted voice has been available on my OP5 since I first got this device. My replacement of the stock kernel made no difference in this case.
Click to expand...
Click to collapse
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
tsuttie99 said:
That's dumb! Have you tried toggling Smart lock in the trust agents of the security menu?
Also I noticed you're in Canada (eh?), mind if I ask which language you run as primary on your device? English US, Canada?
I started on English US as google assistant wouldnt fire up with Canada, but since then, I'm back to English Canada. Assistant still works, but as mentioned only when phone is unlocked.
Click to expand...
Click to collapse
I'd read that others (UK) switched back to their native language after getting Google Assistant working and all was well. I've left it as US as primary with Canada as a second as it simply doesn't effect me. I like spelling colour as "color" which always made more sense to me.
My real reason for not switching back is that I've done a lot of home automation scripting with Google Assistant/Tasker's Voice Assist/Termux to automate my audio/video equipment and associated lighting. As far as I'm concerned Google Assistant may be in beta for built in functionality but is alpha for any third party integration. Every Google app update seems to break something while fixing other functionality (e.g. macros).
I like the automation I've created enough that I have little interest in rocking the boat at the moment. I had previously retested Trusted voice and the lock screen after updates and will again until it works. Right now I'm using a work around with an app called Caffeine (disables the lock screen timeout when charging) and Screen off (only turns the screen off but does not trigger the lock screen).
Also I may have tried toggling Trusted agents as I did so many tests and retests while working on Google Assistant functionality, I just can't remember.
I think there is something very broken with Smart Lock on this phone's stock OS.... I set up my cars BT as trusted device.... still i need to Authenticate with finger/pattern. Coming from a 6P where this all worked seamlessly it's frustrating.
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
ultramag69 said:
My assisstant works from lock screen with "OK Google".
Stock 4.5.8 with root.
I boot into TWRP instead of flashing the recovery. Still have stock recovery.
Use Magisk v13.3 with Magisk Manager 5.1.1.
Have English (US) as my primary language with English (Australia) as my 2nd.
Click to expand...
Click to collapse
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
3DSammy said:
By the way how do you pull off the trick of "boot into TWRP"? I've never read about how to do that. Also what does it buy you other than maybe the GA working on the lock screen?
Click to expand...
Click to collapse
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
tsuttie99 said:
Just get your phone plugged into your PC and from bootloader you type "fastboot boot recovery <twrp file name>.img
It will just boot from that image instead of writing it to flash
Click to expand...
Click to collapse
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
3DSammy said:
Interesting trick, thanks for the info.
Unfortunately I could not use it as I had to borrow a relatives Win10 PC just to flash TWRP in the first place as I couldn't get around that fastboot file size error multiple people experienced no matter which USB ports (v2 or v3) or adb versions I tried. Going to another computer (same model of motherboard) and TWRP was flashed in a second.
Click to expand...
Click to collapse
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
tsuttie99 said:
No worries, I've never actually used that trick as I can always think of a good reason to just have TWRP installed. But times are weird right now, I'm still 100% stock on this phone aside from oem unlock toggle being set. This is the longest I've gone on a fully stock setup. Aside from this Smart Lock/Trusted Voice issue everything is perfect on the OS.
Click to expand...
Click to collapse
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Rebel7022 said:
I'm on stock oos & I'm using Blu kernel & Blu twrp. Blu kernel was so good on the op3T that OnePlus sent him a free op5 last week. I really like the Blu kernel, so much I switched from RR to oos for the first time. OK Google is working to unlock my phone btw.
Click to expand...
Click to collapse
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
tsuttie99 said:
Thanks for the info. Can you share if you can unlock the phone with OK google with the screen off? Scenario: Your phone is on a nearby table and you are a few feet away from it, the screen is off, the phone is not charging. Can you OK google without touching the phone?
Click to expand...
Click to collapse
There's a xda article on OK Google that has a hack to do that. I tried it it works.. But that was 3 months ago
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Yep, works from lock screen, not screen off...
tsuttie99 said:
Okay so this is weird. I can't believe i didn't try this test. I can yell "okay google" until the cows come home while the screen is off. it wont light up or unlock. However if i wake the screen THEN say okay google, my phone unlocks and assistant begins working. Is this the same for others who claim "everything is working fine for me"?
Click to expand...
Click to collapse
Well fancy that. I just did your test, locked screen with power button, with screen off there's no reaction to "OK Google". I then double tap the screen and the lock screen displays. Now "OK Google" unlocks the phone and Google Assistant is fully functional.
Kind of feels like a sprinter that falls inches before the finish line. What the heck Google or OnePlus? I wonder if custom ROMs have the same issue?
Thanks for noticing this phenomena and posting about it.
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
Can Tasker achieve something like this? I have only returned to Android after a 3 years break, any advice is much appreciated!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have that setting enabled. It works on the lock screen where you can swipe to unlock, but not on the darker lock screen, where it shows the time and the outline of your notifications.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
dancooper93 said:
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
Click to expand...
Click to collapse
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
srdjanLeo said:
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
Click to expand...
Click to collapse
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
MilgeS said:
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
Click to expand...
Click to collapse
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
srdjanLeo said:
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
Click to expand...
Click to collapse
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Okay, I see.
Does charging not stop at 80% for you because you are rooted?
artikle said:
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Click to expand...
Click to collapse
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
srdjanLeo said:
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
Click to expand...
Click to collapse
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
dancooper93 said:
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
Click to expand...
Click to collapse
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
srdjanLeo said:
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
Click to expand...
Click to collapse
I am now rooted
What Note 8 ROM did you use?
dancooper93 said:
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
Click to expand...
Click to collapse
I meant "open" as in on lock screen re your above post, the screen after AOD, sorry for any confusion
Same here works after you swipe but not from AOD, every time tutorial I have seen says the same has to be "open" before it will work.
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
scatterthought said:
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
Click to expand...
Click to collapse
That's not true. It still works on a Google Pixel running stock Android with the screen off and not charging. You never had to have it plugged in or charging for that to work. Samsung is the ONLY Android phone I know of that OK Google doesn't work with the screen off.
Source: I've owned the Nexus 6, Nexus 5x, the Nexus 6P, the Pixel XL, a number of Galaxy phones, and a few Motorola's and a couple LGs.
Hey everyone,
some years ago I had the Nexus One and started digging into Android development, custom ROMs, CyanogenMOD and so on. But since the iPhone 5S I've always been an Apple user.
One of the reasons I still prefer iPhone over Android phones is the convenient usage of Siri with headphones. Sounds awkward? Let me explain:
I use my bike every day, and while I try to find my way through the cars of the early morning traffic in Munich (Germany), I'm able to control the music I'm listening to with Siri.
A long press on my headphone button gives me accesss to Siri:
"Play some funk music".
Or: "Call Veronica."
Or: "Send a message to Peter: I'll be late for the rehearsal, sorry."
Or: "Set my alarm to 3 pm."
Stupid question: Is this possible with Bixby? Or Google Assistant?
Long story short: I don't want to have to fiddle around with my phone on the bike, especially when wearing gloves or anything. I'd love to activate the assistant from my headphones without unlocking the phone or taking it out of my pocket.
This is actually the thing that has kept me away from Android for quite a long time.
Thanks,
Ben
Assistant does all of that, plus much more. I don't use bixby.
Bixby currently is useless wouldn't even recognise my voice to train it as its Korean or US english only.
Google Assistant however is great BUT they've only started allowing assistant to work when the phone is sleeping and locked in the Oreo beta. I can now use voice commands (no button presses) to do anything like listening to music sending texts or calling. Nougat only lets you use the assistant with the screen on (and phone locked/unlocked).
Karlinski said:
Assistant does all of that, plus much more. I don't use bixby.
Click to expand...
Click to collapse
While the screen is off? Oblox said it won't work..
You can do that with "Ok Google" and it should work.
If you are still pending and not sure about switching, then check how this works on an Android in a phone store or get one from a friend.
heisven said:
While the screen is off? Oblox said it won't work..
Click to expand...
Click to collapse
I have not gotten the phone to wake by saying "ok google". but "Hi bixby" does wake the phone from a lockscreen.
what I do is say, "Hi Bixby, open Assistant" - and then Google Assistant launches and is listening.
saying, "Hi Bixby, open GOOGLE Assistant" just launches Google, so be sure leave out the word "Google".
Bixby: your *****'s *****.
As i stated above Samsung only made assistant wake the device in the Oreo beta which should be out in January if all goes to plan.
Ok Google works fine on Oreo to wake the phone so you dont have to mess with Bixby at all.
On Nougat i had to press the power button first then could say OK Google.
Oblox said:
As i stated above Samsung only made assistant wake the device in the Oreo beta which should be out in January if all goes to plan.
Ok Google works fine on Oreo to wake the phone so you dont have to mess with Bixby at all.
On Nougat i had to press the power button first then could say OK Google.
Click to expand...
Click to collapse
right, I think the OP may not have known that the S8 is still on Nougat (7.0) - Oreo (8.0) has been released only in beta form to certain users for testing.
so in other words, if you buy the device now, you will NOT be able to launch Assistant directly from the lockscreen. this feature should become available with the next software update.
but you could, in essence, use the device as you would like, but just have to say "Hi bixby" instead. also, as another user noted, test it for yourself. I have, and it works as advertised, just not as polished as google or Siri (takes training/repetition before you get the full AI experience).
this lockscreen wake capability has been around on android for quite some time. I had it on my 2014 Motorola Droid Turbo - and worked perfectly every time.
jco23 said:
right, I think the OP may not have known that the S8 is still on Nougat (7.0) - Oreo (8.0) has been released only in beta form to certain users for testing.
so in other words, if you buy the device now, you will NOT be able to launch Assistant directly from the lockscreen. this feature should become available with the next software update.
but you could, in essence, use the device as you would like, but just have to say "Hi bixby" instead. also, as another user noted, test it for yourself. I have, and it works as advertised, just not as polished as google or Siri (takes training/repetition before you get the full AI experience).
this lockscreen wake capability has been around on android for quite some time. I had it on my 2014 Motorola Droid Turbo - and worked perfectly every time.
Click to expand...
Click to collapse
Yep although as he's from germany id imagine he might have more issues than me trying to get US bixby to recognise his voice. It wouldn't even complete the training for me an I have a pretty standard UK english accent with no regional accent.
Thanks me later
https://www.youtube.com/watch?v=67PsQAqwoyI